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

25 lines
593 B
Text
Raw Normal View History

x86: Add configuration back for Traverse Geos When we merged all the Geode boards into one generic target, the default network and LED configuration was lost. Put it back. Fixes: 9e0759ea2653 ("x86: merge all geode based subtargets into one") Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2017-02-10 11:41:30 +00:00
#!/bin/sh
#
# Copyright © 2017 OpenWrt.org
#
. /lib/functions/uci-defaults.sh
board_config_update
treewide: use only board_name function to get name Do not parse /tmp/sysinfo/board_name, /proc/cpuinfo or the device tree compatible string directly. Always use the board_name function to get the board name. The admswconfig package still reads /proc/cpuinfo directly. The code looks somehow broken and the whole adm5120 which uses this package looks unmaintained. Leave it as it is for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-07-09 11:00:36 +00:00
case "$(board_name)" in
x86: Add APU3 reference to x86 board.d There is a new APU-model available, APU3. The device is configured in the same way as the APU1 and APU2, so the same LED/network setup can be used. I considered changing the case to pc-engines-apu*, but I chose to follow the existing pattern and add the full board name. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2018-03-15 12:30:27 +00:00
pc-engines-apu|pc-engines-apu2|pc-engines-apu3)
x86: Add board configs for the PC Engines APU2 This adds the default LED and network settings for the PC Engines APU2 when running under the x86 target. [dwmw2: Change Ethernet port setup] Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-02-13 08:01:14 +00:00
ucidef_set_led_netdev "wan" "WAN" "apu2:green:led3" "eth0"
ucidef_set_led_netdev "lan" "LAN" "apu2:green:led2" "br-lan"
ucidef_set_led_default "diag" "DIAG" "apu2:green:power" "1"
;;
x86: Add configuration back for Traverse Geos When we merged all the Geode boards into one generic target, the default network and LED configuration was lost. Put it back. Fixes: 9e0759ea2653 ("x86: merge all geode based subtargets into one") Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2017-02-10 11:41:30 +00:00
traverse-technologies-geos)
ucidef_set_led_netdev "lan" "LAN" "geos:1" "br-lan" "tx rx"
ucidef_set_led_netdev "wlan" "WiFi" "geos:2" "phy0tpt"
x86: Enable DIAG LED on Geos Based on a patch from Chris Blake <chrisrblake93@gmail.com>, except let's do it by using the LED configuration instead of hard-coding it for each board type. And try using /bin/board_detect to do the default behaviour, on the first boot where the config hasn't yet been generated. Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2017-02-13 13:38:33 +00:00
ucidef_set_led_default "diag" "DIAG" "geos:3" "1"
x86: Add configuration back for Traverse Geos When we merged all the Geode boards into one generic target, the default network and LED configuration was lost. Put it back. Fixes: 9e0759ea2653 ("x86: merge all geode based subtargets into one") Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2017-02-10 11:41:30 +00:00
;;
esac
board_config_flush
exit 0
Reference in a new issue Copy permalink