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.even...@gmail.com>
---
target/linux/x86/base-files/etc/board.d/01_leds | 2 +-
target/linux/x86/base-files/etc/board.d/02_network | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/x86/base-files/etc/board.d/01_leds
b/target/linux/x86/base-files/etc/board.d/01_leds
index 04e11705ac..25dc4aeeb1 100755
--- a/target/linux/x86/base-files/etc/board.d/01_leds
+++ b/target/linux/x86/base-files/etc/board.d/01_leds
@@ -8,7 +8,7 @@
board_config_update
case "$(board_name)" in
-pc-engines-apu|pc-engines-apu2)
+pc-engines-apu|pc-engines-apu2|pc-engines-apu3)
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"
diff --git a/target/linux/x86/base-files/etc/board.d/02_network
b/target/linux/x86/base-files/etc/board.d/02_network
index bea696d8ff..c6e381b946 100755
--- a/target/linux/x86/base-files/etc/board.d/02_network
+++ b/target/linux/x86/base-files/etc/board.d/02_network
@@ -9,7 +9,7 @@
board_config_update
case "$(board_name)" in
-pc-engines-apu|pc-engines-apu2)
+pc-engines-apu|pc-engines-apu2|pc-engines-apu3)
ucidef_set_interfaces_lan_wan "eth1 eth2" "eth0"
;;
traverse-technologies-geos)
--
2.14.1
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
