KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/target/linux/ramips/base-files/etc/board.d/01_leds

254 lines
5.8 KiB
Text
Raw Normal View History

ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
#!/bin/sh
ramips: make use of the new board detection layer Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 42186
2014-08-18 13:09:20 +00:00
. /lib/functions/uci-defaults-new.sh
ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
. /lib/ramips.sh
set_usb_led() {
ramips: use the generic uci-default functions for initial LED setup SVN-Revision: 31993
2012-05-29 16:39:18 +00:00
ucidef_set_led_usbdev "usb" "USB" "$1" "1-1"
ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
}
ramips: add support for the Senao/EnGenius ESR-9753 board Signed-off-by: Artur Wronowski <arteqw@gmail.com> SVN-Revision: 29603
2011-12-23 14:27:10 +00:00
set_wifi_led() {
ramips: use the generic uci-default functions for initial LED setup SVN-Revision: 31993
2012-05-29 16:39:18 +00:00
ucidef_set_led_netdev "wifi_led" "wifi" "$1" "wlan0"
ramips: WAN LED for D-Link DIR-300-B1 Add led devices for D-Link DIR-300-B1 WAN LED. Note that the GPIO state is also ANDed with the esw switch port 4 LED state, which is why I've set the amber LED to default-on. Closes: https://dev.openwrt.org/ticket/11326 Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de> [ juhosg: - fix comment style in mach-dir-300-revb.c, - remove the PPP specific LED setup, not everyone uses a PPP connection on the WAN interface] SVN-Revision: 31989
2012-05-29 16:39:03 +00:00
}
ramips: make use of the new board detection layer Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 42186
2014-08-18 13:09:20 +00:00
ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
board=$(ramips_board_name)
ramips: make use of the new board detection layer Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 42186
2014-08-18 13:09:20 +00:00
board_config_update
ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
case $board in
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
3g150b|\
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
3g300m)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:blue:3g"
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
;;
3g-6200n)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:amber:wlan"
set_usb_led "$board:blue:3g"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
3g-6200nl|\
br-6475nd|\
mzk-w300nh2)
set_wifi_led "$board:amber:wlan"
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
;;
a5-v11)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "POWER" "$board:red:power" "1"
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
;;
ai-br100)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "wan" "wan" "$board:blue:wan" "eth0.2"
set_wifi_led "$board:blue:wlan"
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
;;
air3gii)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:green:wlan"
set_usb_led "$board:green:mobile"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
all0239-3g|\
hw550-3g|\
mofi3500-3gn|\
sap-g3200u3)
set_usb_led "$board:green:usb"
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
;;
all0256n)
ucidef_set_rssimon "wlan0" "40000" "1"
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_rssi "rssilow" "RSSILOW" "$board:green:rssilow" "wlan0" "1" "40" "0" "6"
ucidef_set_led_rssi "rssimedium" "RSSIMEDIUM" "$board:green:rssimed" "wlan0" "30" "80" "-29" "5"
ucidef_set_led_rssi "rssihigh" "RSSIHIGH" "$board:green:rssihigh" "wlan0" "70" "100" "-69" "8"
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
set_wifi_led "rt2800pci-phy0::radio"
;;
ar670w|\
ar725w|\
awapn2403)
set_wifi_led "rt2800soc-phy0::radio"
;;
asl26555)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "POWER" "$board:green:power" "1"
ucidef_set_led_netdev "eth" "ETH" "$board:green:eth" "eth0"
set_wifi_led "$board:green:wlan"
set_usb_led "$board:green:3g"
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
;;
bc2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:blue:usb"
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
;;
br-6425)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:orange:wlan"
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
;;
broadway)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:red:diskmounted"
set_wifi_led "$board:red:wps_active"
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
;;
cf-wr800n)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "lan" "lan" "$board:white:ethernet" eth0.1
set_wifi_led "$board:white:wifi"
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
;;
cy-swr1100)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "wps" "WPS" "$board:blue:wps" "0"
set_usb_led "$board:blue:usb"
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
;;
d105)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "POWER" "$board:red:power" "1"
set_usb_led "$board:green:usb"
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
;;
ramips: add support for Planex DB-WRT01 This patch add support for Planex DB-WRT01. DANBOARD route on the MT7620A SoC with two Ethernet port and a 802.11n 2.4 GHz radio. DANBOARD is Cartoon character. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 46918
2015-09-14 20:08:55 +00:00
db-wrt01)
ucidef_set_led_default "power" "power" "$board:orange:power" "1"
;;
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
dcs-930l-b1)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "POWER" "$board:red:power" "1"
ucidef_set_led_netdev "wifi" "WiFi" "$board:blue:wps"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
dir-300-b1|\
dir-600-b1|\
dir-600-b2|\
dir-620-a1)
ucidef_set_led_default "wan" "WAN LED (amber)" "$board:amber:wan" "1"
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
set_wifi_led "rt2800pci-phy0::radio"
;;
dir-300-b7|\
dir-320-b1|\
dir-610-a1|\
esr-9753|\
hlk-rm04|\
sl-r7205|\
v11st-fe|\
w306r-v20|\
wt1520)
set_wifi_led "rt2800pci-phy0::radio"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
dir-615-d|\
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
dir-615-h1)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "status" "Status LED (amber)" "$board:amber:status" "0"
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
set_wifi_led "rt2800pci-phy0::radio"
;;
dir-620-d1)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:green:wifi"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
dir-810l|\
mzk-dp150n)
ucidef_set_led_default "power" "power" "$board:green:power" "1"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
f5d8235-v1|\
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
f5d8235-v2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:blue:storage"
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
;;
fonera20n)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:orange:usb"
set_wifi_led "$board:orange:wifi"
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
;;
hg255d)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:green:wlan"
set_usb_led "$board:green:usb"
ucidef_set_led_interface "lan" "$board:green:internet"
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
;;
hpm)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "POWER" "$board:orange:power" "1"
ucidef_set_led_netdev "eth" "ETH" "$board:green:eth" "eth0"
set_wifi_led "$board:green:wifi"
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
;;
ht-tm02)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "eth" "Ethernet" "$board:green:lan" "eth0"
set_wifi_led "$board:blue:wlan"
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
;;
m2m)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:blue:wifi"
ucidef_set_led_netdev "eth" "Ethernet" "$board:green:wan" "eth0"
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
;;
miniembplug)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:red:wlan"
set_usb_led "$board:green:mobile"
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
;;
miwifi-mini)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:red:status" "1"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
mlw221|\
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
mlwg2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:blue:wifi"
ucidef_set_led_default "system" "system" "$board:blue:system" "1"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
mpr-a1|\
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
mpr-a2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:blue:system"
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
;;
mr-102n)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:green:wlan"
set_usb_led "$board:green:usb"
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
;;
na930)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:blue:status"
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
;;
nw718)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:amber:usb"
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
;;
oy-0001)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:green:power" "1"
set_wifi_led "$board:green:wifi"
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
;;
pbr-m1)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "internet" "internet" "$board:green:internet" "eth0.2"
ucidef_set_led_default "power" "power" "$board:green:power" "1"
ucidef_set_led_default "sys" "sys" "$board:green:sys" "1"
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
;;
px-4885)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:orange:wifi"
set_usb_led "$board:blue:storage"
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
;;
re6500)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:white:power" "1"
ucidef_set_led_default "wifi" "wifi" "$board:orange:wifi" "1"
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
;;
rp-n53)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "eth" "Network" "$board:white:back" "eth0"
set_wifi_led "$board:blue:wifi"
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
;;
rt-n14u)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:blue:power" "1"
ucidef_set_led_netdev "lan" "lan" "$board:blue:lan" eth0.1
ucidef_set_led_netdev "wan" "wan" "$board:blue:wan" eth0.2
set_wifi_led "$board:blue:air"
set_usb_led "$board:blue:usb"
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
;;
vocore)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_netdev "eth" "ETH" "$board:orange:eth" "eth0"
set_wifi_led "$board:green:status"
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
;;
w502u)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:blue:usb"
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
set_wifi_led "rt2800pci-phy0::radio"
;;
wcr-150gn)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_usb_led "$board:amber:user"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
whr-1166d|\
whr-300hp2|\
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
whr-600d)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:green:power" "1"
ucidef_set_led_default "router" "router" "$board:green:router" "1"
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
;;
wnce2001)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:green:wlan"
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
;;
wt3020)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:blue:power" "0"
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
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
y1|\
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
y1s)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:blue:power" "1"
set_usb_led "$board:blue:usb"
set_wifi_led "$board:blue:wifi"
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
;;
zbt-wa05)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:blue:power" "1"
set_wifi_led "$board:blue:air"
set_usb_led "$board:blue:usb"
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
;;
zbt-wr8305rt)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ucidef_set_led_default "power" "power" "$board:green:sys" "1"
set_usb_led "$board:green:usb"
set_wifi_led "$board:green:wifi"
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
;;
zte-q7)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
set_wifi_led "$board:blue:status"
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
;;
ramips: combine led setup for all boards in one file This removes unnecessary duplication and simplifies led setup for new boards. It would be a one line change most likely. Signed-off-by: Alexander Gordeev <lasaine@lvk.cs.msu.su> SVN-Revision: 28569
2011-10-24 21:49:31 +00:00
esac
ramips: use the generic uci-default functions for initial LED setup SVN-Revision: 31993
2012-05-29 16:39:18 +00:00
ramips: make use of the new board detection layer Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 42186
2014-08-18 13:09:20 +00:00
board_config_flush
ramips: use the generic uci-default functions for initial LED setup SVN-Revision: 31993
2012-05-29 16:39:18 +00:00
exit 0
Reference in a new issue Copy permalink