Commit graph

3 commits

Author SHA1 Message Date
John Crispin
1a392636a5 ramips: use consistent naming scheme for LEDs
The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach.
The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target:
 * fixes wrong indentation
 * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body)
 * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files)
 * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds)

Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>

SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
John Crispin
553fea9f19 ramips: fix indentation and other mistakes in .dts{, i} files
The following patch fixes:
 * wrong indentations
 * doubled gpio-keys-polled nodes (DIR-300-B7, DIR-320-B1, DIR-610-A1)
 * duplicate spacings
 * empty lines at end of files and after last child nodes
 * trailing and leading whitespace
 * unnecessary and commented-out code
 * missing empty lines between nodes and between properties and nodes
 * unnecessary empty lines between nodes properties [1]

in .dts{,i} files, for ramips target.

[1] Some of empty lines in SOCs dtsi files were left untouched, because they seem to be there for a reason (readability?).

Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>

SVN-Revision: 46613
2015-08-17 05:57:18 +00:00
John Crispin
3618391514 ramips: Buffalo WZR-AGL300NH target support
I got work with this patch.
Ethernet switch (includes VLAN), WiFi connected via PCIe, LEDs, buttons.

In mtd partion map of DTS file, I renamed Linux firmware regions (kernel + root squashfs) to “firmware”because it allows kernel to split kernel and roots and rootfsdata.

signed-off-by: ngc@ff.iij4u.or.jp
——
——

SVN-Revision: 44470
2015-02-16 21:19:18 +00:00