|
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
. /lib/functions/uci-defaults.sh
|
|
|
|
|
|
|
|
|
|
set_wifi_led() {
|
|
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "${1}" "${2:-wlan0}"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
board=$(board_name)
|
|
|
|
|
boardname="${board##*,}"
|
|
|
|
|
|
|
|
|
|
board_config_update
|
|
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
|
3g-6200n)
|
|
|
|
|
set_wifi_led "$boardname:amber:wlan"
|
|
|
|
|
;;
|
|
|
|
|
3g-6200nl|\
|
|
|
|
|
skylab,skw92a|\
|
|
|
|
|
wnce2001)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
br-6475nd|\
|
|
|
|
|
mzk-w300nh2)
|
|
|
|
|
set_wifi_led "$boardname:amber:wlan"
|
|
|
|
|
;;
|
|
|
|
|
ai-br100)
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:blue:wan" "eth0.2"
|
|
|
|
|
set_wifi_led "$boardname:blue:wlan"
|
|
|
|
|
;;
|
|
|
|
|
air3gii)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
alfa-network,ac1200rm)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan2g" "wlan1"
|
|
|
|
|
;;
|
|
|
|
|
alfa-network,awusfree1)
|
|
|
|
|
set_wifi_led "$boardname:blue:wlan"
|
|
|
|
|
;;
|
|
|
|
|
all0256n-4M|\
|
|
|
|
|
all0256n-8M)
|
|
|
|
|
ucidef_set_rssimon "wlan0" "200000" "1"
|
|
|
|
|
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"
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
ar670w|\
|
|
|
|
|
ar725w|\
|
|
|
|
|
awapn2403)
|
|
|
|
|
set_wifi_led "rt2800soc-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
asl26555-8M|\
|
|
|
|
|
asl26555-16M)
|
|
|
|
|
ucidef_set_led_netdev "eth" "ETH" "asl26555:green:eth" "eth0"
|
|
|
|
|
set_wifi_led "asl26555:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
bdcom,wap2100-sk|\
|
|
|
|
|
hiwifi,hc5861b)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan2g"
|
|
|
|
|
;;
|
|
|
|
|
broadway)
|
|
|
|
|
set_wifi_led "$boardname:red:wps_active"
|
|
|
|
|
;;
|
|
|
|
|
c108)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:green:lan" "eth0"
|
|
|
|
|
ucidef_set_led_netdev "modem" "modem" "$boardname:green:modem" "wwan0"
|
|
|
|
|
;;
|
|
|
|
|
c20i)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:blue:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:blue:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_wlan "wlan" "wlan" "$boardname:blue:wlan" "phy0radio"
|
|
|
|
|
;;
|
|
|
|
|
c50)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "wlan2g" "$boardname:green:wlan2g" wlan1
|
|
|
|
|
set_wifi_led "$boardname:green:wlan5g"
|
|
|
|
|
;;
|
|
|
|
|
cf-wr800n)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:white:ethernet" eth0.1
|
|
|
|
|
set_wifi_led "$boardname:white:wifi"
|
|
|
|
|
;;
|
|
|
|
|
d240)
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
;;
|
|
|
|
|
dcs-930l-b1)
|
|
|
|
|
ucidef_set_led_netdev "wifi" "WiFi" "$boardname:blue:wps"
|
|
|
|
|
;;
|
|
|
|
|
dir-300-b1|\
|
|
|
|
|
dir-600-b1|\
|
|
|
|
|
dir-620-a1)
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
dir-300-b7|\
|
|
|
|
|
dir-320-b1|\
|
|
|
|
|
dir-610-a1|\
|
|
|
|
|
esr-9753|\
|
|
|
|
|
hlk-rm04|\
|
|
|
|
|
sl-r7205|\
|
|
|
|
|
v11st-fe|\
|
|
|
|
|
w306r-v20|\
|
|
|
|
|
wt1520-4M|\
|
|
|
|
|
wt1520-8M)
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
dir-615-d|\
|
|
|
|
|
dir-615-h1)
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
dir-620-d1|\
|
|
|
|
|
dlink,dwr-116-a1|\
|
|
|
|
|
mzk-ex300np)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
dlink,dwr-118-a1)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1f"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x20"
|
|
|
|
|
set_wifi_led "$boardname:green:wlan2g" "wlan1"
|
|
|
|
|
;;
|
|
|
|
|
dlink,dwr-118-a2)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x0e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
set_wifi_led "$boardname:green:wlan2g" "wlan1"
|
|
|
|
|
;;
|
ramips: add support for DLINK DWR-922-E2
Very similar to the DWR-921-C1, except has a telephony/RJ11 port (not
sure if supported, I didn't try), wireless router with QMI LTE embedded
modem is based on the MT7620N SoC.
Specification:
* MediaTek MT7620N (580 Mhz)
* 64 MB of RAM
* 16 MB of FLASH
* 802.11bgn radio
* 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN)
* 2x external, detachable (LTE) antennas
* UART header on PCB (57600 8n1)
* 6x LED (GPIO-controlled)
* 1x bi-color Signal Strength LED (GPIO-controlled)
* 2x button
* JBOOT bootloader
The status led has been assigned to the dwr-922-e2:green:signalstrength
(lte signal strength) led. At the end of the boot it is switched off and
is available for lte operation. Works correctly also during sysupgrade
operation.
Installation:
Apply factory image via d-link http web-gui, or via recovery interface:
How to recover/revert to OEM firmware:
1.) Push and hold the reset button and turn on the power. Wait until all
LEDs start rapidly blinking (~10sec.)
2.) DHCP should give you an IP in the 192.168.123.0/24 subnet, or set
one manually
3.) Upload original factory image via JBOOT http interface at IP
192.168.123.254
4.) If http doesn't work, it can be done with curl command:
curl -F FN=@XXXXX.bin http://192.168.123.254/upg
where XXXXX.bin is name of firmware file.
5.) You can optionally telnet to 192.168.123.254 before or during the
upload and it will report the flashing status, memory address etc.
6.) Once web UI and/or telnet says "Success", power cycle the router, or
type "reboot" into the telnet session.
Signed-off-by: Simon Quigley <squigley@squigley.net>
[squashed commits, word wrap commit message, rename signal strenght led
name to match what is used for the DWR-921-C1 since they share the led
configuration, add label referenced in the aliases node]
Signed-off-by: Mathias Kresin <dev@kresin.me>
5 years ago
|
|
|
dlink,dwr-921-c1|\
|
|
|
|
|
dlink,dwr-922-e2)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x0f"
|
ramips: add support for DLINK DWR-922-E2
Very similar to the DWR-921-C1, except has a telephony/RJ11 port (not
sure if supported, I didn't try), wireless router with QMI LTE embedded
modem is based on the MT7620N SoC.
Specification:
* MediaTek MT7620N (580 Mhz)
* 64 MB of RAM
* 16 MB of FLASH
* 802.11bgn radio
* 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN)
* 2x external, detachable (LTE) antennas
* UART header on PCB (57600 8n1)
* 6x LED (GPIO-controlled)
* 1x bi-color Signal Strength LED (GPIO-controlled)
* 2x button
* JBOOT bootloader
The status led has been assigned to the dwr-922-e2:green:signalstrength
(lte signal strength) led. At the end of the boot it is switched off and
is available for lte operation. Works correctly also during sysupgrade
operation.
Installation:
Apply factory image via d-link http web-gui, or via recovery interface:
How to recover/revert to OEM firmware:
1.) Push and hold the reset button and turn on the power. Wait until all
LEDs start rapidly blinking (~10sec.)
2.) DHCP should give you an IP in the 192.168.123.0/24 subnet, or set
one manually
3.) Upload original factory image via JBOOT http interface at IP
192.168.123.254
4.) If http doesn't work, it can be done with curl command:
curl -F FN=@XXXXX.bin http://192.168.123.254/upg
where XXXXX.bin is name of firmware file.
5.) You can optionally telnet to 192.168.123.254 before or during the
upload and it will report the flashing status, memory address etc.
6.) Once web UI and/or telnet says "Success", power cycle the router, or
type "reboot" into the telnet session.
Signed-off-by: Simon Quigley <squigley@squigley.net>
[squashed commits, word wrap commit message, rename signal strenght led
name to match what is used for the DWR-921-C1 since they share the led
configuration, add label referenced in the aliases node]
Signed-off-by: Mathias Kresin <dev@kresin.me>
5 years ago
|
|
|
ucidef_set_led_netdev "signalstrength" "signalstrength" "$boardname:green:sigstrength" "wwan0" "link"
|
|
|
|
|
ucidef_set_led_netdev "4g" "4g" "$boardname:green:4g" "wwan0" "tx rx"
|
|
|
|
|
;;
|
|
|
|
|
dir-860l-b1)
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:green:net" "eth0.2"
|
|
|
|
|
;;
|
|
|
|
|
edimax,br-6478ac-v2)
|
|
|
|
|
set_wifi_led "$boardname:blue:wlan"
|
|
|
|
|
;;
|
|
|
|
|
ex2700|\
|
|
|
|
|
wn3000rpv3)
|
|
|
|
|
set_wifi_led "$boardname:green:router"
|
|
|
|
|
;;
|
|
|
|
|
ex3700)
|
|
|
|
|
ucidef_set_led_netdev "wlan5g" "ROUTER (green)" "$boardname:green:router" "wlan0"
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "DEVICE (green)" "$boardname:green:device" "wlan1"
|
|
|
|
|
;;
|
|
|
|
|
f5d8235-v1)
|
|
|
|
|
set_wifi_led "$boardname:blue:wireless"
|
|
|
|
|
;;
|
|
|
|
|
fonera20n)
|
|
|
|
|
set_wifi_led "$boardname:orange:wifi"
|
|
|
|
|
;;
|
|
|
|
|
gnubee,gb-pc1|\
|
|
|
|
|
gnubee,gb-pc2)
|
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "$boardname:green:lan1" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "$boardname:green:lan2" "switch0" "0x10"
|
|
|
|
|
;;
|
|
|
|
|
gl-mt300a|\
|
|
|
|
|
gl-mt300n|\
|
|
|
|
|
gl-mt750)
|
|
|
|
|
set_wifi_led "$boardname:wlan"
|
|
|
|
|
;;
|
|
|
|
|
gl-mt300n-v2)
|
|
|
|
|
set_wifi_led "$boardname:red:wlan"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x1"
|
|
|
|
|
;;
|
|
|
|
|
hc5661|\
|
|
|
|
|
hc5661a)
|
|
|
|
|
ucidef_set_led_netdev "internet" "internet" "$boardname:blue:internet" "eth0.2"
|
|
|
|
|
set_wifi_led "$boardname:blue:wlan2g"
|
|
|
|
|
;;
|
|
|
|
|
hc5761|\
|
|
|
|
|
hc5861)
|
|
|
|
|
ucidef_set_led_netdev "internet" "internet" "$boardname:blue:internet" "eth0.2"
|
|
|
|
|
ucidef_set_led_netdev "wifi5g" "wifi5g" "$boardname:blue:wlan5g" "wlan0"
|
|
|
|
|
ucidef_set_led_netdev "wifi2g" "wifi2g" "$boardname:blue:wlan2g" "wlan1"
|
|
|
|
|
;;
|
|
|
|
|
hg255d)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
ucidef_set_led_netdev "internet" "internet" "$boardname:green:internet" "eth0.2"
|
|
|
|
|
;;
|
|
|
|
|
hpm)
|
|
|
|
|
ucidef_set_led_netdev "eth" "ETH" "$boardname:green:eth" "eth0"
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
ht-tm02)
|
|
|
|
|
ucidef_set_led_netdev "eth" "Ethernet" "$boardname:green:lan" "eth0"
|
|
|
|
|
set_wifi_led "$boardname:blue:wlan"
|
|
|
|
|
;;
|
|
|
|
|
kimax,u35wf)
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
ucidef_set_led_netdev "eth" "ETH" "$boardname:green:eth" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
kn|\
|
|
|
|
|
nbg-419n2)
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
kn_rc|\
|
|
|
|
|
kn_rf|\
|
|
|
|
|
kng_rc)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
lava,lr-25g001)
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "WiFi 2.4GHz" "$boardname:green:wlan2g" "wlan1"
|
|
|
|
|
ucidef_set_led_netdev "wlan5g" "WiFi 5GHz" "$boardname:green:wlan5g" "wlan0"
|
|
|
|
|
;;
|
|
|
|
|
linkits7688)
|
|
|
|
|
ucidef_set_led_wlan "wifi" "wifi" "linkit-smart-7688:orange:wifi" "phy0tpt"
|
|
|
|
|
;;
|
|
|
|
|
m2m)
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
ucidef_set_led_netdev "eth" "Ethernet" "$boardname:green:wan" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
mikrotik,rbm11g)
|
|
|
|
|
ucidef_set_rssimon "wlan0" "200000" "1"
|
|
|
|
|
ucidef_set_led_rssi "rssilow" "RSSILOW" "$boardname:green:rssi0" "wlan0" "1" "100"
|
|
|
|
|
ucidef_set_led_rssi "rssimediumlow" "RSSIMEDIUMLOW" "$boardname:green:rssi1" "wlan0" "20" "100"
|
|
|
|
|
ucidef_set_led_rssi "rssimediumhigh" "RSSIMEDIUMHIGH" "$boardname:green:rssi2" "wlan0" "40" "100"
|
|
|
|
|
ucidef_set_led_rssi "rssihigh" "RSSIHIGH" "$boardname:green:rssi3" "wlan0" "60" "100"
|
|
|
|
|
ucidef_set_led_rssi "rssiveryhigh" "RSSIVERYHIGH" "$boardname:green:rssi4" "wlan0" "80" "100"
|
|
|
|
|
;;
|
|
|
|
|
miniembplug)
|
|
|
|
|
set_wifi_led "$boardname:red:wlan"
|
|
|
|
|
;;
|
|
|
|
|
mir3g)
|
|
|
|
|
ucidef_set_led_switch "wan-amber" "WAN (amber)" "$boardname:amber:wan" "switch0" "0x02" "0x08"
|
|
|
|
|
ucidef_set_led_switch "lan1-amber" "LAN1 (amber)" "$boardname:amber:lan1" "switch0" "0x08" "0x08"
|
|
|
|
|
ucidef_set_led_switch "lan2-amber" "LAN2 (amber)" "$boardname:amber:lan2" "switch0" "0x04" "0x08"
|
|
|
|
|
;;
|
|
|
|
|
mlw221|\
|
|
|
|
|
mlwg2)
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
;;
|
|
|
|
|
mr-102n)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
mr200)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:white:lan" "eth0.1"
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:white:wan" "usb0"
|
|
|
|
|
set_wifi_led "$boardname:white:wlan"
|
|
|
|
|
;;
|
|
|
|
|
mtc,wr1201)
|
|
|
|
|
ucidef_set_led_switch "eth_link" "LAN link" "$boardname:green:eth_link" "switch0" "0x0f"
|
|
|
|
|
;;
|
|
|
|
|
mzk-ex750np)
|
|
|
|
|
set_wifi_led "$boardname:red:wifi"
|
|
|
|
|
;;
|
|
|
|
|
netgear,r6120)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x0f"
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "WiFi 2.4GHz" "$boardname:green:wlan2g" "phy0tpt"
|
|
|
|
|
ucidef_set_led_wlan "wlan5g" "WiFi 5GHz" "$boardname:green:wlan5g" "phy1tpt"
|
|
|
|
|
;;
|
|
|
|
|
oy-0001)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
gehua,ghl-r-001|\
|
|
|
|
|
pbr-m1)
|
|
|
|
|
ucidef_set_led_netdev "internet" "internet" "$boardname:blue:internet" "eth0.2"
|
|
|
|
|
;;
|
ramips: add support for newifi d2
Previously Newifi D2 could only use PandoraBox M1's firmware.
It works fine, but LED GPIO is different.
As a result, a separated DTS file for this device should be implemented.
Hardware spec:
* CPU: MTK MT7621A
* RAM: 512MB
* ROM: 32MB SPI Flash
* WiFi: MTK MT7603+MT7612
* Button: 2 buttons (reset, wps)
* LED: 3 single-color LEDs (USB, WiFi 2.4GHz, WiFi 5GHz) &
2 dual-color LEDs (Power, Internet)
* Ethernet: 5 ports, 4 LAN + 1 WAN
Installation method:
Same as Newifi D1, users may need to request unlock code from the device
manufacturer. Otherwise, a SPI flash programmer may be necessary to get
the firmware flashed. After the device is unlocked, press and hold reset
button before power cable plugs in. Then go to http://192.168.1.1 to
upload and flash the firmware package.
Signed-off-by: Jackson Ming Hu <huming2207@gmail.com>
7 years ago
|
|
|
d-team,newifi-d2)
|
|
|
|
|
ucidef_set_led_switch "internet" "internet" "$boardname:amber:internet" "switch0" "0x10"
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "WiFi 2.4GHz" "$boardname:blue:wlan2g" "wlan0"
|
|
|
|
|
ucidef_set_led_netdev "wlan5g" "WiFi 5GHz" "$boardname:blue:wlan5g" "wlan1"
|
|
|
|
|
;;
|
|
|
|
|
psg1208)
|
|
|
|
|
set_wifi_led "$boardname:white:wlan2g"
|
|
|
|
|
;;
|
|
|
|
|
px-4885-4M|\
|
|
|
|
|
px-4885-8M)
|
|
|
|
|
set_wifi_led "px-4885:orange:wifi"
|
|
|
|
|
;;
|
|
|
|
|
r6220|\
|
|
|
|
|
netgear,r6350)
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:green:wan" eth0.2
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
re350-v1)
|
|
|
|
|
ucidef_set_led_netdev "wifi2g" "Wifi 2.4G" "$boardname:blue:wifi2G" "wlan0"
|
|
|
|
|
ucidef_set_led_netdev "wifi5g" "Wifi 5G" "$boardname:blue:wifi5G" "wlan1"
|
|
|
|
|
ucidef_set_led_netdev "eth_act" "LAN act" "$boardname:green:eth_act" "eth0" "tx rx"
|
|
|
|
|
ucidef_set_led_switch "eth_link" "LAN link" "$boardname:green:eth_link" "switch0" "0x01"
|
|
|
|
|
;;
|
|
|
|
|
rp-n53)
|
|
|
|
|
ucidef_set_led_netdev "eth" "Network" "$boardname:white:back" "eth0"
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
;;
|
|
|
|
|
rt-ac51u)
|
|
|
|
|
set_wifi_led "$boardname:blue:wifi"
|
|
|
|
|
;;
|
|
|
|
|
rt-n12p)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:green:lan" eth0.1
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:green:wan" eth0.2
|
|
|
|
|
set_wifi_led "$boardname:green:air"
|
|
|
|
|
;;
|
|
|
|
|
rt-n14u)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:blue:lan" eth0.1
|
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "$boardname:blue:wan" eth0.2
|
|
|
|
|
set_wifi_led "$boardname:blue:air"
|
|
|
|
|
;;
|
|
|
|
|
tama,w06)
|
|
|
|
|
ucidef_set_led_netdev "wan" "WAN" "$boardname:green:wan" "eth0"
|
|
|
|
|
ucidef_set_led_wlan "wlan" "WLAN" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
;;
|
|
|
|
|
tew-714tru)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
tiny-ac)
|
|
|
|
|
set_wifi_led "$boardname:orange:wifi"
|
|
|
|
|
;;
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
7 years ago
|
|
|
tl-wr840n-v4)
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "wlan2g" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
7 years ago
|
|
|
;;
|
|
|
|
|
tl-wr841n-v13)
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "wlan2g" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "$boardname:green:lan1" "switch0" "0x2"
|
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "$boardname:green:lan2" "switch0" "0x4"
|
|
|
|
|
ucidef_set_led_switch "lan3" "lan3" "$boardname:green:lan3" "switch0" "0x8"
|
|
|
|
|
ucidef_set_led_switch "lan4" "lan4" "$boardname:green:lan4" "switch0" "0x10"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
7 years ago
|
|
|
;;
|
|
|
|
|
tplink,c2-v1)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch1" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch1" "0x01"
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,c20-v1)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:blue:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:blue:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "wlan2g" "$boardname:blue:wlan2g" "wlan0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,c20-v4)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_netdev "wlan2g" "wlan2g" "$boardname:green:wlan2g" "wlan0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,c50-v3)
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "wlan2g" "$boardname:green:wlan2g" "phy0tpt"
|
|
|
|
|
ucidef_set_led_wlan "wlan5g" "wlan5g" "$boardname:green:wlan5g" "phy1tpt"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wa801nd-v5)
|
|
|
|
|
ucidef_set_led_wlan "wlan" "wlan" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:green:lan" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-mr3020-v3)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
ucidef_set_led_netdev "lan" "LAN" "$boardname:green:lan" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-mr3420-v5|\
|
|
|
|
|
tplink,tl-wr842n-v5)
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "wlan2g" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x1e"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr902ac-v3)
|
|
|
|
|
ucidef_set_led_wlan "wlan2g" "wlan2g" "$boardname:green:wlan" "phy0tpt"
|
|
|
|
|
ucidef_set_led_switch "lan" "lan" "$boardname:green:lan" "switch0" "0x10"
|
|
|
|
|
;;
|
|
|
|
|
u25awf-h1)
|
|
|
|
|
set_wifi_led "u25awf:red:wifi"
|
|
|
|
|
ucidef_set_led_netdev "eth" "eth" "u25awf:green:lan" "eth0"
|
|
|
|
|
;;
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
7 years ago
|
|
|
u7628-01-128M-16M)
|
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "u7628-01:green:lan1" "switch0" "0x2"
|
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "u7628-01:green:lan2" "switch0" "0x4"
|
|
|
|
|
ucidef_set_led_switch "lan3" "lan3" "u7628-01:green:lan3" "switch0" "0x8"
|
|
|
|
|
ucidef_set_led_switch "lan4" "lan4" "u7628-01:green:lan4" "switch0" "0x10"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "u7628-01:green:wan" "switch0" "0x01"
|
|
|
|
|
set_wifi_led "u7628-01:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
vocore-8M|\
|
|
|
|
|
vocore-16M)
|
|
|
|
|
ucidef_set_led_netdev "eth" "ETH" "vocore:orange:eth" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
w502u)
|
|
|
|
|
set_wifi_led "rt2800pci-phy0::radio"
|
|
|
|
|
;;
|
|
|
|
|
wavlink,wl-wn570ha1)
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
ucidef_set_rssimon "wlan0" "200000" "1"
|
|
|
|
|
ucidef_set_led_rssi "wifi-low" "wifi-low" "$boardname:green:wifi-low" "wlan0" "1" "49"
|
|
|
|
|
ucidef_set_led_rssi "wifi-med" "wifi-med" "$boardname:green:wifi-med" "wlan0" "50" "84"
|
|
|
|
|
ucidef_set_led_rssi "wifi-high" "wifi-high" "$boardname:green:wifi-high" "wlan0" "85" "100"
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
ramips: Add support for ZBT WE1026-5G
The ZBT WE1026-5G
(http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up
to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the
ZBT WE826 image could be used. However, as the name implies, the -5G
comes equipped with a 5GHz wifi radio. As the WE826 only has a 2.4GHz
radio, the addition of 5GHz means that a separate image is needed for
the WE1026-5G. I suspect that this image will also work on the previous
WE1026, but I don't have a device to test with.
The WE1026-5G has following specifications:
* CPU: MT7620A
* 1x 10/100Mbps Ethernet.
* 16 MB Flash.
* 64 MB RAM.
* 1x USB 2.0 port.
* 1x mini-PCIe slots.
* 1x SIM slots.
* 1x 2.4Ghz WIFI.
* 1x 5GHz wifi (MT7612)
* 1x button.
* 3x controllable LEDs.
Works:
* Wifi.
* Switch.
* mini-PCIe slot. Only tested with a USB device (a modem).
* SIM slot.
* Sysupgrade.
* Button (reset).
Not working:
* The 5GHz WIFI LED is completely dead. I suspect the issue is the same
as on other devices with Mediatek 5Ghz wifi-cards/chips. The LED is
controlled by the driver, and mt76 (currently) does not support this.
Not tested:
* SD card reader.
Notes:
* The modem (labeled 3G/4G) and power LEDs are controlled by the
hardware.
* There is a 32MB version of this device available, but I do not have
access to it. I have therefor only added support for the 16MB version,
but added all the required infrastructure to make adding support for the
32MB version easy.
Installation:
The router comes pre-installed with OpenWRT, including a variant of
Luci. The initial firmware install can be done through this UI,
following normal procedure. I.e., access the UI and update the firmware
using the sysupgrade-image. Remember to select that you do not want to
keep existing settings.
Recovery:
If you brick the device, the WE1026-5G supports recovery using HTTP. Keep the
reset button pressed for ~5sec when booting to start the web server. Set the
address of the network interface on your machine to 192.168.1.2/24, and
point your browser to 192.168.1.1 to access the recovery UI. From the
recovery UI you can upload a firmware image.
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
7 years ago
|
|
|
we1026-5g-16m)
|
|
|
|
|
ucidef_set_led_netdev "lan" "LAN" "we1026-5g:green:lan" "eth0"
|
|
|
|
|
set_wifi_led "we1026-5g:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
wl-wn575a3)
|
|
|
|
|
ucidef_set_rssimon "wlan1" "200000" "1"
|
|
|
|
|
ucidef_set_led_rssi "wifi-low" "wifi-low" "$boardname:green:wifi-low" "wlan1" "1" "49"
|
|
|
|
|
ucidef_set_led_rssi "wifi-med" "wifi-med" "$boardname:green:wifi-med" "wlan1" "50" "84"
|
|
|
|
|
ucidef_set_led_rssi "wifi-high" "wifi-high" "$boardname:green:wifi-high" "wlan1" "85" "100"
|
|
|
|
|
;;
|
|
|
|
|
wrh-300cr)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:green:ethernet" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
xzwifi,creativebox-v1)
|
|
|
|
|
ucidef_set_led_switch "internet" "internet" "$boardname:blue:internet" "switch0" "0x10"
|
|
|
|
|
;;
|
|
|
|
|
y1)
|
|
|
|
|
ucidef_set_led_netdev "wifi" "WIFI" "$boardname:blue:wifi" "wlan1"
|
|
|
|
|
ucidef_set_led_netdev "wifi5g" "WIFI5G" "$boardname:blue:wifi5g" "wlan0"
|
|
|
|
|
ucidef_set_led_switch "lan" "LAN" "$boardname:blue:lan" "switch0" "0x03"
|
|
|
|
|
;;
|
|
|
|
|
y1s)
|
|
|
|
|
ucidef_set_led_netdev "wifi" "WIFI" "$boardname:yellow:wifi" "wlan1"
|
|
|
|
|
ucidef_set_led_netdev "wifi5g" "WIFI5G" "$boardname:blue:wifi" "wlan0"
|
|
|
|
|
ucidef_set_led_netdev "wan" "WAN" "$boardname:blue:internet" "eth0.2" "tx rx"
|
|
|
|
|
;;
|
|
|
|
|
youhua,wr1200js)
|
|
|
|
|
ucidef_set_led_switch "internet" "INTERNET" "$boardname:green:wan" "switch0" "0x01"
|
|
|
|
|
;;
|
|
|
|
|
zbt-ape522ii)
|
|
|
|
|
ucidef_set_led_netdev "wlan2g4" "wlan1-link" "$boardname:green:wlan2g4" "wlan1"
|
|
|
|
|
ucidef_set_led_netdev "sys1" "wlan1" "$boardname:green:sys1" "wlan1" "tx rx"
|
|
|
|
|
ucidef_set_led_netdev "sys2" "wlan0" "$boardname:green:sys2" "wlan0" "tx rx"
|
|
|
|
|
;;
|
|
|
|
|
zbt-wa05)
|
|
|
|
|
set_wifi_led "$boardname:blue:air"
|
|
|
|
|
;;
|
|
|
|
|
zbt-we2026)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
;;
|
|
|
|
|
zbt-we826-16M|\
|
|
|
|
|
zbt-we826-32M)
|
|
|
|
|
set_wifi_led "zbt-we826:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
zbtlink,zbt-we1226)
|
|
|
|
|
set_wifi_led "$boardname:green:wlan"
|
|
|
|
|
ucidef_set_led_switch "lan1" "LAN1" "$boardname:green:lan1" "switch0" "0x01"
|
|
|
|
|
ucidef_set_led_switch "lan2" "LAN2" "$boardname:green:lan2" "switch0" "0x02"
|
|
|
|
|
ucidef_set_led_switch "wan" "WAN" "$boardname:green:wan" "switch0" "0x10"
|
|
|
|
|
;;
|
|
|
|
|
zbt-wr8305rt)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
;;
|
|
|
|
|
zorlik,zl5900v2)
|
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "$boardname:green:lan" eth0
|
|
|
|
|
;;
|
|
|
|
|
zyxel,keenetic-extra-ii)
|
|
|
|
|
set_wifi_led "$boardname:green:wifi"
|
|
|
|
|
ucidef_set_led_switch "internet" "internet" "$boardname:green:internet" "switch0" "0x01"
|
|
|
|
|
;;
|
|
|
|
|
youku-yk1)
|
|
|
|
|
set_wifi_led "$boardname:blue:air"
|
|
|
|
|
ucidef_set_led_switch "wan" "wan" "$boardname:blue:wan" "switch0" "0x10"
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
|
|
|
|
|
board_config_flush
|
|
|
|
|
|
|
|
|
|
exit 0
|
