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

422 lines
11 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
all: drop old uci-defaults.sh Replace former uci-defaults.sh implementation with the uci-defaults-new.sh one and update all users accordingly. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47867
2015-12-11 15:26:06 +00:00
. /lib/functions/uci-defaults.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: unify etc/board.d/01_leds configuration Introduce an optional parameter at the local set_usb_led and set_wifi_led function such that they can take a triggering device. If no parameter is passed, behaviour is unchanged. Signed-off-by: P.Wassi <p.wassi@gmx.at>
2016-07-26 17:18:53 +00:00
ucidef_set_led_usbdev "usb" "USB" "${1}" "${2:-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: unify etc/board.d/01_leds configuration Introduce an optional parameter at the local set_usb_led and set_wifi_led function such that they can take a triggering device. If no parameter is passed, behaviour is unchanged. Signed-off-by: P.Wassi <p.wassi@gmx.at>
2016-07-26 17:18:53 +00:00
ucidef_set_led_netdev "wifi_led" "wifi" "${1}" "${2:-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: use destinct 11AC NAS board name Use a distinct board name even if the board is near to identical to the WeVO W2914NS v2. To make sure that a 11AC NAS image can not be installed on a WeVO W2914NS v2, both board need to use different names. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-12-23 07:21:31 +00:00
11acnas|\
all0239-3g|\
ramips: add support for Afoundry EW-1200 This device features both a 2.4 and 5Ghz radio, and supports 802.11a/b/g/n/ac modes. It has 5 Gb-Ethernet ports and a USB 3.0 host port. It is powered by the Mediatek MT7621 SoC, and the MT7602E and MT7612E wifi chipsets, together with 128MB of RAM and 16 MB of SPI Flash. The stock firmware is in fact based on some openwrt barrier breaker, with a mediatek SDK kernel, and an afoundry custom made web interface (not LuCI based). Firmware update page on the stock web interface can not accept sysupgrade images, it bricks the device. At this point, the only working solution I found was to connect to the serial console port (available on J4 header) and to use opkg to install dropbear. Then scp the sysupgrade file in the device's /tmp and run sysupgrade from console without preserving configuration files. Signed-off-by: Francois Goudal <francois@goudal.net>
2017-02-27 20:59:50 +00:00
ew1200|\
ramips: use destinct 11AC NAS board name Use a distinct board name even if the board is near to identical to the WeVO W2914NS v2. To make sure that a 11AC NAS image can not be installed on a WeVO W2914NS v2, both board need to use different names. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-12-23 07:21:31 +00:00
hw550-3g|\
mofi3500-3gn|\
sap-g3200u3|\
sk-wb8|\
w2914nsv2|\
wf-2881)
set_usb_led "$board:green:usb"
;;
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|\
ramips: improve edimax 6200n/nl support Assign the reset functionality to the wps/reset buttons. Use the wlan switch of the 6200n to enable/disable wlan. Add the internet led of the 6200nl and use the led for boot status indication Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-27 05:16:16 +00:00
wnce2001)
set_wifi_led "$board:green:wlan"
;;
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
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
;;
ramips: add support for Planex CS-QR10 CS-QR10 is MT7620A based IP Camera. the camera and sound does not work with kernel 4.4. - camera chip is sn9c291. - sound chip is wm8960. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49234
2016-04-26 11:43:01 +00:00
a5-v11|\
cs-qr10)
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: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
all0256n-4M|\
all0256n-8M)
ar71xx, ramips: reduce CPU load and flickering on devices using rsslieds Polling every 40ms causes more than 10% CPU load on weak devices. An interval of 200ms is much more reasonable. Signed-off-by: Martin Weinelt <martin@darmstadt.freifunk.net> [Matthias Schiffer: adapt OpenWrt patch; add ramips; extend commit message] Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
2016-11-02 15:10:44 +00:00
ucidef_set_rssimon "wlan0" "200000" "1"
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
ucidef_set_led_rssi "rssilow" "RSSILOW" "all0256n:green:rssilow" "wlan0" "1" "40" "0" "6"
ucidef_set_led_rssi "rssimedium" "RSSIMEDIUM" "all0256n:green:rssimed" "wlan0" "30" "80" "-29" "5"
ucidef_set_led_rssi "rssihigh" "RSSIHIGH" "all0256n: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"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
asl26555-8M|\
asl26555-16M)
ucidef_set_led_default "power" "POWER" "asl26555:green:power" "1"
ucidef_set_led_netdev "eth" "ETH" "asl26555:green:eth" "eth0"
set_wifi_led "asl26555:green:wlan"
set_usb_led "asl26555: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
;;
ramips: Improve TP-Link Archer C20i support Improve / finalise TP-Link Archer C20i support. Signed-off-by: P.Wassi <p.wassi@gmx.at>
2016-07-26 04:44:19 +00:00
c20i)
ucidef_set_led_switch "lan" "lan" "$board:blue:lan" "switch0" "0x1e"
ucidef_set_led_switch "wan" "wan" "$board:blue:wan" "switch0" "0x01"
set_usb_led "$board:blue:usb" "2-1"
ucidef_set_led_wlan "wlan" "wlan" "$board:blue:wlan" "phy0radio"
;;
ramips/base-files: Add support for Archer C50 Signed-off-by: Henryk Heisig <hyniu@o2.pl>
2016-06-12 21:43:51 +00:00
c50)
ramips: Archer C50 cleanup - setting read-only flag to important partitions - enabling PA to improve 2.4 GHz signal strength - add missing leds - rename colour led - add mac adress to 5GHz wlan interface - included <dt-bindings/input/input.h> and <dt-bindings/gpio/gpio.h> Signed-off-by: Henryk Heisig hyniu@o2.pl
2016-10-13 19:00:06 +00:00
ucidef_set_led_default "power" "power" "$board:green:power" "0"
ucidef_set_led_switch "lan" "lan" "$board:green:lan" "switch0" "0x1e"
ucidef_set_led_switch "wan" "wan" "$board:green:wan" "switch0" "0x01"
set_usb_led "$board:green:usb"
ucidef_set_led_netdev "wlan2g" "wlan2g" "$board:green:wlan2g" wlan1
set_wifi_led "$board:green:wlan5g"
ramips/base-files: Add support for Archer C50 Signed-off-by: Henryk Heisig <hyniu@o2.pl>
2016-06-12 21:43:51 +00:00
;;
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 Sanlinking D240 The Sanlinking Technologies D240 (http://www.sanlinking.com/en/29-dual-4g-wifi-router.html) is basically the same device as the ZBT WE826, so adding support for it in LEDE is straight forward. The differences is that the D240 has two mini-PCIe slots (instead of one), blue LEDs and supports PoE. Specification: * CPU: MT7620A * 1x 10/100Mbps POE (802.3af/802.3at) Ethernet, 4x 10/100Mbps. * 16 MB Flash. * 128 MB RAM. * 1x USB 2.0 port. * 2x mini-PCIe slots. * 2x SIM slots. * 1x 2.4Ghz WIFI. * 1x button. Wifi, USB, switch and both mini-PCIe slots are working. I have not been able to test the SD card reader. The device comes pre-installed with an older version of OpenWRT, including Luci. In order to install LEDE, you need to follow the existing procedure for updating OpenWRT/LEDE using Luci. I.e., you need to access the UI and update the firmware using the sysupgrade-image. Remember to select that you do not want to keep existing settings. The default router address is 192.168.10.1 and username/password admin/root (at least on my devices). If you brick the device, the procedure for recovery is the same as for the WE826. Please see the wiki page for that device for instructions. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-02-04 20:28:52 +00:00
d240)
set_wifi_led "$board:blue:wifi"
set_usb_led "$board:blue:usb"
;;
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: Add support for D-Link DCH-M225 D-Link DCH-M225 is based on Mediatek MT7620 with 64MB ram, 8MB flash, 3.5mm audio out support. but no ethernet and usb ports. so you must default enable wifi. Signed-off-by: Michael Lee <igvtee@gmail.com>
2016-05-02 03:57:40 +00:00
dch-m225)
ucidef_set_led_default "power" "POWER" "$board:geeen:power" "1"
ucidef_set_led_default "status" "STATUS" "$board:red: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
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-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|\
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
wt1520-4M|\
wt1520-8M)
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"
;;
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"
;;
ramips: add support for Planex MZK-EX300NP MZK-EX300NP is MT7620A based wifi repeater. Built-in power supply. 64MiB RAM, 8MiB SPI Flash, non Wired Ethernet. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49235
2016-04-26 11:43:06 +00:00
dir-620-d1|\
mzk-ex300np)
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|\
ramips: fix support Planex MZK-750DHP. fix script for Planex MZK-750DHP. modification of the GPIO definition. add Profile. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49205
2016-04-20 17:19:05 +00:00
mzk-750dhp|\
ramips: add support for Planex VR500. SOC: MT7621A RAM: 256MiB NOR: MX25L51245G Non Wireless Router. Issue: soft reboot problem. SPI Flash do not exit 4byte address mode. Signed-off-by: Yuhei Okawa <tochiro.srchack@gmail.com>
2016-10-10 01:24:42 +00:00
mzk-dp150n|\
vr500)
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"
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 button support and make LEDs known to userspace for DIR-860L B1 Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> Reviewed-by: Jo-Philipp Wich <jo@mein.io>
2016-06-30 13:18:03 +00:00
dir-860l-b1)
ucidef_set_led_netdev "wan" "wan" "$board:green:net" "eth0.2"
;;
ramips: add support for Netgear WN3000RPv3 This patch adds support for the Netgear WN3000RPv3 http://www.netgear.com/support/product/wn3000rpv3.aspx Specifications: - SoC: MediaTek MT7620A (580MHz, ramips) - RAM: 32MB DDR - Storage: 8MB NOR SPI flash - Wireless: builtin MT7620A, 2x2:2 with u.FL connectors - Ethernet: 1x100M - Serial: JP1 header, 57600-8N1 - Stock firmware based on OpenWRT Kamikaze Like the EX2700, the bootloader expects a secondary image signature, see https://forum.openwrt.org/viewtopic.php?pid=312577#p312577 This is why the same fakeroot image is used for the WN3000 Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
2017-01-18 10:34:56 +00:00
ex2700|\
wn3000rpv3)
ramips: Add support for Netgear EX2700 This patch adds support for the Netgear EX2700 and builds an approriate sysupgrade image. What's missing is the option to build a factory image flashable via the router's stock web interface, but this approach is hindered by the fact that u-boot operforms an additional integrity check, which expects a uImage header in the last 64 bytes of the "kernel" partition, which the bootloader expects to be 960k, a size exceeded by the standard OpenWrt kernel. Signed-off-by: Joseph C. Lehner <joseph.c.lehner@gmail.com> SVN-Revision: 48698
2016-02-12 08:29:33 +00:00
ucidef_set_led_default "power_r" "POWER (red)" "$board:red:power" "0"
set_wifi_led "$board:green:router"
;;
ramips: add support for Netgear EX3700 Specifications: * SoC: MT7620A * RAM: 64 MB DDR * Flash: 8MB NOR SPI flash * WiFi: MT7612E (5Ghz) and builtin MT7620A (2.4GHz) * LAN: 1x100M The -factory images can be flashed from the device's web interface or via nmrpflash. Co-authored-by: Paul Oranje <por@xs4all.nl> Signed-off-by: Paul Oranje <por@xs4all.nl> Signed-off-by: Joseph C. Lehner <joseph.c.lehner@gmail.com>
2017-03-03 14:36:51 +00:00
ex3700)
ucidef_set_led_netdev "wlan5g" "ROUTER (green)" "$board:green:router" "wlan0"
ucidef_set_led_netdev "wlan2g" "DEVICE (green)" "$board:green:device" "wlan1"
;;
ramips: improve F5D8235 V1 support This fixes the partition name for the firmware splitter, the cfi address and adds the mtd-eeprom address for wmac. It adds additional LEDs and make use of them in diag.sh and 01_leds. Please note that the ":blue:wired" LED is used because the ":blue:router" behaviour is unpredictable for failsafe indication. The issue with the router LED is that you have two states only. "off" is steady on and "on" blinks. Therefore the wired LED is more suitable. Furthermore it reuses the correct switch configuration definition to reflect the device ports and numbering. Additionally fixes the issue that the default configuration is not applied as no port 6 exists on this device. Signed-off-by: Tobias Wolf <github-NTEO@vplace.de>
2016-12-01 14:08:22 +00:00
f5d8235-v1)
ucidef_set_led_default "lan" "lan" "$board:blue:wired" "0"
set_usb_led "$board:blue:storage"
set_wifi_led "$board:blue:wireless"
;;
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
;;
ramips: Add support for GL-MT300N This patch adds support for GL-MT300N. GL-MT300N is powered by MT7620N with 16MB flash, 64MB RAM, 2 LANs, USB, UART, GPIO and PoE support. SVN-Revision: 48993
2016-03-10 19:12:04 +00:00
gl-mt300a|\
ramips: Add support for GL-MT750 This patch adds support for GL-MT750. GL-MT750 is powered by MT7620A and MT7610e, dual band 802.11ac, 2.4G 300Mbps and 5G 450Mbps. It has 5 LANs, MMC interface, USB, a lot of IOs and PoE support. SVN-Revision: 48994
2016-03-10 19:12:10 +00:00
gl-mt300n|\
gl-mt750)
ramips: Add support for GL-MT300A This patches adds support for GL-MT300A. GL-MT300A is powered by MT7620A. It has 16MB flash, 128MB RAM, Two LANs, USB, UART and MMC daughter board. SVN-Revision: 48992
2016-03-10 19:11:57 +00:00
set_wifi_led "$board:wlan"
;;
ramips: add support for HiWiFi HC5661A HC5661A is almost the same as HC5661 but MT7628AN is used instead of MT7620A. - MT7628AN - 128 MiB DDR2 RAM (W971GG6KB-25) - 16 MiB SPI NOR flash (W25Q128) - SD slot (not work yet) - 1+4 x 100M Ethernet - 802.11 b/g/n Wi-Fi - 3 x LED - 1 x button - UART pad on PCB (JP1: TX, RX, GND, 3.3V) The factory flash layout seems different from HC5661. "hwf_config" is renamed to "oem" and its size changes to 0x20000. It is modified accordingly in the dts file. 0x000000000000-0x000000030000 : "u-boot" 0x000000030000-0x000000040000 : "hw_panic" 0x000000040000-0x000000050000 : "Factory" 0x000000050000-0x000000160000 : "kernel" 0x000000160000-0x000000fc0000 : "rootfs" 0x000000bb0000-0x000000fc0000 : "rootfs_data" 0x000000fc0000-0x000000fe0000 : "oem" 0x000000fe0000-0x000000ff0000 : "bdinfo" 0x000000ff0000-0x000001000000 : "backup" 0x000000050000-0x000000fc0000 : "firmware" To install LEDE, enabled the "developer mode", which will *void your warranty* and open the SSH server at port 1022. sysupgrade -n -F lede-ramips-mt7628-hc5661a-squashfs-sysupgrade.bin SD slot: - Tried to add modules kmod-sdhci kmod-sdhci-mt7620, and corresponding dts block. - It will block WAN + 3xLAN ports, only one LAN works. - I'm not sure why, everything else works fine. Signed-off-by: Wang JiaWei <buaawjw@gmail.com>
2017-02-24 23:19:15 +00:00
hc5661|\
hc5661a)
ramips: Add base-files for HiWiFi HC5x61 models HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rssnsj@gmail.com). I ported the patch to trunk and submitted it here with his approval. v3 fix 1: Fixed model order 2: Remove manufacturer name from model name 3: Use a hacky but prettier way to get mac address. Signed-off-by: Xiaoning Kang <kangxn@163.com> SVN-Revision: 47111
2015-10-05 10:25:47 +00:00
ucidef_set_led_default "system" "system" "$board:blue:system" "1"
ucidef_set_led_netdev "internet" "internet" "$board:blue:internet" "eth0.2"
set_wifi_led "$board:blue:wlan2g"
ramips: remove indentation in etc/board.d/01_leds Remove indentation at end of line in base-files/etc/board.d/01_leds Signed-off-by: Paul Wassi <p.wassi@gmx.at>
2016-07-23 14:25:38 +00:00
;;
ramips: Add base-files for HiWiFi HC5x61 models HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rssnsj@gmail.com). I ported the patch to trunk and submitted it here with his approval. v3 fix 1: Fixed model order 2: Remove manufacturer name from model name 3: Use a hacky but prettier way to get mac address. Signed-off-by: Xiaoning Kang <kangxn@163.com> SVN-Revision: 47111
2015-10-05 10:25:47 +00:00
hc5761)
ucidef_set_led_default "system" "system" "$board:blue:system" "1"
ucidef_set_led_netdev "internet" "internet" "$board:blue:internet" "eth0.2"
set_wifi_led "$board:blue:wlan2g"
ucidef_set_led_netdev "wifi5g" "wifi5g" "$board:blue:wlan5g" "rai0"
;;
hc5861)
ucidef_set_led_default "system" "system" "$board:blue:system" "1"
ucidef_set_led_netdev "internet" "internet" "$board:blue:internet" "eth0.2"
set_wifi_led "$board:blue:wlan2g"
ucidef_set_led_netdev "wifi5g" "wifi5g" "$board:blue:wlan5g" "rai0"
ucidef_set_led_default "turbo" "turbo" "$board:blue:turbo" "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
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"
ramips: hg255d: replace ucidef_set_led_interface() with ucidef_set_led_netdev() Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47657
2015-11-26 12:46:04 +00:00
ucidef_set_led_netdev "internet" "internet" "$board:green:internet" "eth0.2"
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
;;
ramips: add new device ZyXEL Keenetic as kn This device exactly same as NBG-419N but with USB port and USB Led. Specification: - SoC: Ralink RT3052 (MIPS24Kc) @384MHz - RAM: 32 MiB - Flash: 8 MiB - WLAN: WiSoC 2T2R/300Mbps (2.4GHz) - LAN: 4x100M - WAN: 1x100M - USB: 1x2.0 Installation via serial console (57600 8N1) from TFTP server - rename the firmware to something shorter, for example "sysupgrade.bin" (max. 32 chars) - copy firmware TFTP server's directory - when you power on device, and see U-Boot log, immediatly push "2" once. - You will see this message: 2: System Load Linux Kernel then write to Flash via TFTP. Warning!! Erase Linux in Flash then burn new one. Are you sure? - Push "y", and enter: device IP, then TFTP server's IP, and then image firmware file name. The firmware will be downloaded within ~30 seconds and flashed to the device (It will take about 2 minutes). Signed-off-by: Alexey Belyaev <spider@spider.vc> [squash commits, compact commit message, fix compatible string, remove superfluous pinmuxes] Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-27 18:02:05 +00:00
kn|\
nbg-419n2)
set_usb_led "$board:green:usb"
set_wifi_led "rt2800pci-phy0::radio"
;;
ramips: add support for ZyXEL Keenetic Omni / Omni II Factory image can be installed via Zyxel WebUI. Signed-off-by: Vitaly Chekryzhev <13hakta@gmail.com>
2016-11-28 18:41:51 +00:00
kn_rc|\
kn_rf|\
ramips: add support for ZyXEL Keenetic Viva Factory image can be installed via Zyxel WebUI. Signed-off-by: Vitaly Chekryzhev <13hakta@gmail.com> [removed linux,modalias parameter from flash node in dts] [removed sdhci node from dts; no sd card slot here] Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-10-29 12:26:58 +00:00
kng_rc)
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
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
;;
ramips: Xiaomi MiWiFi Nano: fix status led - add status led for Xiaomi MiWiFi Nano - revert https://github.com/lede-project/source/commit/af1e70b4a730e91ce1668d506ebc5c1c8cf5abf5 , this should not be added. Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
2016-09-28 17:08:38 +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
;;
ramips: Add support to TP-Link Archer MR200 CPU: MT7620N 580MHz Flash: 8MB RAM: 64MB build-in modem 3G/4G four ethernet port 10/100Mbps Signed-off-by: Henryk Heisig <hyniu@o2.pl>
2016-09-24 19:41:43 +00:00
mr200)
ucidef_set_led_default "power" "power" "$board:white:power" "1"
ucidef_set_led_netdev "lan" "lan" "$board:white:lan" "eth0.1"
ucidef_set_led_netdev "wan" "wan" "$board:white:wan" "usb0"
set_wifi_led "$board:white:wlan"
;;
ramips: add support for Planex MZK-EX750NP. add support for Planex MZK-EX750NP. MZK-EX750NP is MT7620A and MT7610E based 11ac wifi repeater. Built-in power supply. 64MiB RAM, 8MiB SPI Flash, non Wired Ethernet. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49268
2016-04-29 11:34:56 +00:00
mzk-ex750np)
ucidef_set_led_default "power" "power" "$board:red:power" "1"
set_wifi_led "$board:red: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
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 : add support for Newifi D1 Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-09-27 06:25:04 +00:00
;;
newifi-d1)
set_usb_led "$board:red: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
;;
ramips : add support for PandoraBox D1 Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-09-27 06:23:27 +00:00
pbr-d1)
set_usb_led "$board:orange: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
pbr-m1)
ramips: Fix support for PBR-M1 board The PBR-M1 support in current OpenWrt is for the early demo board and it doesn't work on the final board.This patch fixes the support for it. The LED called pbr-m1:buzzer is a beeper connected to GPIO26 so I used gpio-beeper instead of gpio-leds. Signed-off-by: 郭传鈜 <gch981213@gmail.com> SVN-Revision: 47844
2015-12-11 15:03:50 +00:00
ucidef_set_led_netdev "internet" "internet" "$board:blue:internet" "eth0.2"
ucidef_set_led_default "power" "power" "$board:blue:power" "1"
ucidef_set_led_default "sys" "sys" "$board:blue: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
;;
ramips: Add support for Phicomm PSG1208 This patch adds support for Phicomm PSG1208.This is a router with MT7620A SoC with 8M flash and 64M ram. The WPS led is uesd as status_led because the power light can't be controlled with GPIO. It seems that the 5g wifi led is connected to MT7612E and it can't be controlled with GPIO too. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> SVN-Revision: 48721
2016-02-15 18:45:22 +00:00
psg1208)
set_wifi_led "$board:white:wlan2g"
;;
ramips: fix syntax error in board.d/01_leds Fixes the following error: syntax error: unexpected newline (expecting ")") Fixes: FS#739 Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-27 07:38:25 +00:00
psg1218a|\
ramips: rename PSG1218 to match label Fix previous commit to be less ambigous: PSG1218 rev.A = 5 ports, external PA, heatsinks PSG1218 rev.B = 4 ports, internal PA, no heatsinks Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2017-04-21 00:47:44 +00:00
psg1218b)
ramips: fix PSG1218 LEDs Signed-off-by: Xuefu Lin <xuefulin@gmail.com>
2016-10-21 09:06:39 +00:00
ucidef_set_led_netdev "Network" "Network" "$board:blue:status" "eth0"
ucidef_set_led_default "status" "STATUS" "$board:yellow:status" "0"
ramips: Add support for Phicomm K2 PSG1218 - CPU: MT7620A 580MHz - Flash: 8MB - RAM: 64MB - External PA+LNA on both WLAN2.4 and WLAN5 - 4x LAN ethernet and 1x WAN ethernet Signed-off-by: Xuefu Lin <xuefulin@gmail.com>
2016-09-30 11:41:12 +00:00
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
px-4885-4M|\
px-4885-8M)
set_wifi_led "px-4885:orange:wifi"
set_usb_led "px-4885: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
;;
ramips: add support for Netgear R6220 This patch adds support for the Netgear R6220, aka Netgear AC1200 and R6220-100NAS. Specification: - SoC: MediaTek MT7621ST (880 MHz) - Falsh: 128 MiB (Macronix MX30LF1G08AA-TI) - RAM: 128 MiB (Nanya NT5CB64M16FP-DH) - Wireless: MediaTek MT7603EN b/g/n , MediaTek MT7612EN an+ac - LAN speed: 10/100/1000 - LAN ports: 4 - WAN speed: 10/100/1000 - WAN ports: 1 - Serial baud rate of Bootloader and factory firmware: 57600 Installation through telnet: - Copy kernel.bin and rootfs.bin to a USB flash disk, plug to usb port on the router. - Enable telnet with link: http://192.168.1.1/setup.cgi?todo=debug (login if required, default: admin password) - You will see "Debug Enabled!" - Telnet 192.168.1.1 and login with "root" - ls /mnt/shares/ to find out path of your USB disk. 'myUdisk' for example. - cd /mnt/shares/myUdisk - mtd_write write rootfs.bin Rootfs - mtd_write write kernel.bin Kernel - reboot nmrpflash can be used to recover to the netgear firmware if a broken image was flashed. Signed-off-by: Hanqing Wong <hquu@outlook.com>
2017-03-11 07:44:33 +00:00
r6220)
ucidef_set_led_netdev "wan" "wan" "$board:green:wan" eth0.2
set_wifi_led "$board:green:wifi"
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
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
;;
ramips: Add support for TEW-714TRU Signed-off-by: Jimmy Zhong <mb300sd@mb300sd.net>
2016-08-03 17:58:01 +00:00
tew-714tru)
set_usb_led "$board:red:usb"
set_wifi_led "$board:green:wifi"
;;
ramips: add support for Dovado tiny AC Add support for Dovado tiny AC wifi router. Soc: mt7620a ram: 64MB flash: 8MB 1x usb 2.0 two gigabit lan ports 5ghz wlan is not supported on this board since there is no gpl driverfor mt7610e wifi chip. Signed-off-by: Andrej Vlasic <andrej.vlasic0@gmail.com> SVN-Revision: 47348
2015-11-02 10:17:51 +00:00
tiny-ac)
set_wifi_led "$board:orange:wifi"
set_usb_led "$board:green:usb"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
vocore-8M|\
vocore-16M)
ucidef_set_led_netdev "eth" "ETH" "vocore:orange:eth" "eth0"
set_wifi_led "vocore: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
;;
ramips: add support for VoCore2 This patch adds support for the VoCore VoCore2 and its complementary "ultimate" dock. Specifications: - SoC: MediaTek MT7628AN (580MHz, ramips) - RAM: 128MB DDR2 166MHz - Storage: 16MB NOR SPI flash onboard + microSD slot on dock - Wireless: Built into MT7628AN (mt76) with 1T1R firmware on VoCore2 boards with onboard 1x chip antenna - Ethernet: 1x100M (port0) on dock, 1x100M (port2) on PCB header - Dock hardware: - USB 2.0 socket - MicroSD socket - 100Mbps Ethernet x1 - 3.5mm headphone jack (TRRS) connected to Everest Semi ES8388 I2S DAC/ADC (support WIP) - Micro USB for power and console (UART2) Initial installation: - VoCore2 comes preinstalled with a fork of OpenWrt CC and AP on SSID "VoCore2" - Connect to VoCore2 by Ethernet or Wi-Fi - `ssh root@192.168.1.1` (password is "vocore") - scp/wget/etc. LEDE sysupgrade.bin to VoCore2 - `sysupgrade -n <your image>.bin` (don't keep old config, as the original firmware uses Ralink SDK Wi-Fi drivers and not mt76+mac80211) - after sysupgrade completes, Wi-Fi will be disabled by default so use Ethernet or the micro USB console to configure Wi-Fi again Signed-off-by: Andrew Yong <me@ndoo.sg>
2017-01-08 06:30:10 +00:00
vocore2)
set_wifi_led "$board:fuchsia: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
;;
ramips: Add support for Wavlink WL-WN575A3 This commit adds support for the Wavlink WL-WN575A3, a dual-band wall-plug wireless router with the following specifications: - CPU: MediaTek MT7628AN 580MHz - Flash: 8MB - RAM: 64MB - Ethernet: 2x 10/100 Mbps (switched) - 2.4 GHz: 802.11b/g/n SoC, MIMO 2x2, 20 dBm - 5 GHz: 802.11a/n/ac MT7612E, MIMO 2x2, 20 dBm - Antennas: 4x external (2 per radio), non-detachable - LEDs: 4 programmable + LAN, WAN, POWER - Buttons: reset, WPS Flashing instructions: Factory U-boot launches a TFTP client if WPS button is pressed during power-on. Rename the sysupgrade file and configure a TFTP as follows: - Client (WL-WN575A3) IP: 192.168.10.101 - Server IP: 192.168.10.100 - Filename: firmware.bin Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2016-11-06 12:00:38 +00:00
wl-wn575a3)
ar71xx, ramips: reduce CPU load and flickering on devices using rsslieds Polling every 40ms causes more than 10% CPU load on weak devices. An interval of 200ms is much more reasonable. Signed-off-by: Martin Weinelt <martin@darmstadt.freifunk.net> [Matthias Schiffer: adapt OpenWrt patch; add ramips; extend commit message] Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
2016-11-02 15:10:44 +00:00
ucidef_set_rssimon "wlan1" "200000" "1"
ramips: Add support for Wavlink WL-WN575A3 This commit adds support for the Wavlink WL-WN575A3, a dual-band wall-plug wireless router with the following specifications: - CPU: MediaTek MT7628AN 580MHz - Flash: 8MB - RAM: 64MB - Ethernet: 2x 10/100 Mbps (switched) - 2.4 GHz: 802.11b/g/n SoC, MIMO 2x2, 20 dBm - 5 GHz: 802.11a/n/ac MT7612E, MIMO 2x2, 20 dBm - Antennas: 4x external (2 per radio), non-detachable - LEDs: 4 programmable + LAN, WAN, POWER - Buttons: reset, WPS Flashing instructions: Factory U-boot launches a TFTP client if WPS button is pressed during power-on. Rename the sysupgrade file and configure a TFTP as follows: - Client (WL-WN575A3) IP: 192.168.10.101 - Server IP: 192.168.10.100 - Filename: firmware.bin Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2016-11-06 12:00:38 +00:00
ucidef_set_led_rssi "wifi-low" "wifi-low" "$board:green:wifi-low" "wlan1" "1" "49" "0" "1"
ucidef_set_led_rssi "wifi-med" "wifi-med" "$board:green:wifi-med" "wlan1" "50" "84" "0" "1"
ucidef_set_led_rssi "wifi-high" "wifi-high" "$board:green:wifi-high" "wlan1" "85" "100" "0" "1"
;;
ramips: add support for ELECOM WRH-300CR ELECOM WRH-300CR is MT7620N based very small Wi-Fi router with 64MiB DDR2 SDRAM, 16MiB SPI Flash, one fast ethernet port, and (internal but easy-to-access) UART. it also has internal USB hub and USB card reader which provide one USB port, one SD card slot, and one microSD card slot. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> Signed-off-by: FUKAUMI Naoki <naobsd@gmail.com> SVN-Revision: 49211
2016-04-21 19:46:59 +00:00
wrh-300cr)
set_wifi_led "$board:green:wlan"
ucidef_set_led_netdev "lan" "lan" "$board:green:ethernet" "eth0"
;;
ramips: Add support for the Netgear WNDR3700v5 https://wiki.openwrt.org/toh/netgear/wndr3700 wndr3700v5 uses the single-core dual thread MediaTek MT7621S SoC. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> SVN-Revision: 49247
2016-04-26 11:43:53 +00:00
wndr3700v5)
ucidef_set_led_default "power" "POWER" "$board:green:power" "0"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
wt3020-4M|\
wt3020-8M)
ucidef_set_led_default "power" "power" "wt3020: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: Fix led init script for Lenovo Y1/Y1s This commit fix the led init script for Lenovo Y1 and Y1S due to the manual and dts file. Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-12-02 01:33:23 +00:00
y1)
set_usb_led "$board:blue:usb"
ucidef_set_led_netdev "wifi" "WIFI" "$board:blue:wifi" "wlan1"
ucidef_set_led_netdev "wifi5g" "WIFI5G" "$board:blue:wifi5g" "wlan0"
ucidef_set_led_netdev "lan" "LAN" "$board:blue:lan" "eth0.1" "tx rx"
ucidef_set_led_netdev "wan" "WAN" "$board:blue:internet" "eth0.2" "tx rx"
;;
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
set_usb_led "$board:blue:usb"
ramips: Fix led init script for Lenovo Y1/Y1s This commit fix the led init script for Lenovo Y1 and Y1S due to the manual and dts file. Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-12-02 01:33:23 +00:00
ucidef_set_led_netdev "wifi" "WIFI" "$board:yellow:wifi" "wlan1"
ucidef_set_led_netdev "wifi5g" "WIFI5G" "$board:blue:wifi" "wlan0"
ucidef_set_led_netdev "wan" "WAN" "$board:blue:internet" "eth0.2" "tx rx"
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 suport for ZBT APE522II The ZBT APE522II is a dual-radio outdoor CPE based on the MT7620a SoC. It has 64 MB RAM, 8 MB flash, 2 Fast Ethernet ports via internal switch (one with 802.3af 48V PoE support), a 802.11b/g/n SoC 2.4 GHz radio and an 802.11a/n/ac MT7612E-based 5 GHz radio. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2016-06-23 08:58:08 +00:00
zbt-ape522ii)
ucidef_set_led_netdev "wlan2g4" "wlan1-link" "$board:green:wlan2g4" "wlan1"
ucidef_set_led_netdev "sys1" "wlan1" "$board:green:sys1" "wlan1" "tx rx"
ucidef_set_led_netdev "sys2" "wlan0" "$board:green:sys2" "wlan0" "tx rx"
;;
ramips: Add support for ZBT-CPE102 - CPU: MT7620N 580MHz - Flash: 8MB - RAM: 64MB - build-in minipcie slot for modem 3G/4G - one ethernet port 10/100Mbps Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
2016-09-25 19:09:31 +00:00
zbt-cpe102)
ucidef_set_led_default "power" "power" "$board:green:4g-0" "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
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
;;
ramips: add support for Zbtlink ZBT-WE2026 This patch adds support for the Zbtlink ZBT-WE2026. Specification: - SoC: MediaTek MT7620N (580MHz) - RAM: 64 MiB - Flash: 8 MiB SPI - LAN: 4x100M - WAN: 1x100M Installation through bootloader webserver: - With the power unplugged press and hold reset button. - Plug power and hold reset button until LED starts to blink. - Install sysupgrade image using web interface on 192.168.1.1. Signed-off-by: Vaclav Svoboda <svoboda@neng.cz>
2017-03-15 08:37:05 +00:00
zbt-we2026)
set_wifi_led "$board:green:wlan"
;;
ramips: add ZBT-WE826 32MB variant The ZBT-WG826 is available with 16 or 32 MByte of flash. Split the device tree source file, rename the currently supported 16 MByte version and add the 32 MByte variant. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-12 05:53:56 +00:00
zbt-we826-16M|\
zbt-we826-32M)
set_wifi_led "zbt-we826:green:wifi"
set_usb_led "zbt-we826:green:usb"
ramips: Added support for ZBT-826 / ZBT-1026 Support for these MT7620-based routers: https://wiki.openwrt.org/toh/zbt/we-826 Based on Oskari’s patches found here: https://dev.openwrt.org/ticket/19996 Signed-off-by: Jamie Stuart <jamie@onebillion.org> SVN-Revision: 48865
2016-03-01 09:17:06 +00:00
;;
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: add support for Youku YK1 Changes since V1: I resend this patch for current trunk.The former V1 patch is for CC branch. Signed-off-by: Shonn Lu <countrysideboy@qq.com> SVN-Revision: 47617
2015-11-24 18:29:02 +00:00
youku-yk1)
ucidef_set_led_default "power" "power" "$board:blue:power" "1"
set_wifi_led "$board:blue:air"
set_usb_led "$board:blue:usb"
;;
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