ramips: don't hijack the status led

Don't hijack the status led to indicate the wireless state. If we don't
have a dedicated wireless led, it's as simply as the wireless status
can't be indicated.

Such a led misuse should be set by the user and not shipped by default.

Signed-off-by: Mathias Kresin <dev@kresin.me>
master
Mathias Kresin 6 years ago
parent c074239c79
commit b07b3ddaad
  1. 14
      target/linux/ramips/base-files/etc/board.d/01_leds

@ -221,10 +221,6 @@ mlw221|\
mlwg2)
set_wifi_led "$boardname:blue:wifi"
;;
mpr-a1|\
mpr-a2)
set_wifi_led "$boardname:blue:system"
;;
mr-102n)
set_wifi_led "$boardname:green:wlan"
;;
@ -363,13 +359,6 @@ u7628-01-128M-16M)
vocore-8M|\
vocore-16M)
ucidef_set_led_netdev "eth" "ETH" "vocore:orange:eth" "eth0"
set_wifi_led "vocore:green:status"
;;
vocore2)
set_wifi_led "$boardname:fuchsia:status"
;;
vocore2lite)
set_wifi_led "$boardname:green:status"
;;
w502u)
set_wifi_led "rt2800pci-phy0::radio"
@ -428,9 +417,6 @@ zbt-wr8305rt)
zorlik,zl5900v2)
ucidef_set_led_netdev "lan" "lan" "$boardname:green:lan" eth0
;;
zte-q7)
set_wifi_led "$boardname:blue:status"
;;
zyxel,keenetic-extra-ii)
set_wifi_led "$boardname:green:wifi"
ucidef_set_led_switch "internet" "internet" "$boardname:green:internet" "switch0" "0x01"

Loading…
Cancel
Save