ExternalVendorCode/openwrt
1
0
Fork 0
mirror of https://github.com/openwrt/openwrt.git synced 2024-12-24 07:46:48 +00:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity
cc285dc2b6
openwrt/target/linux/x86/base-files/etc/board.d/01_leds

35 lines
1.2 KiB
Plaintext
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
#
# 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 support for Meraki MX100 This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2021-10-01 14:38:56 +00:00
cisco-mx100-hw)
ucidef_set_led_usbport "usb" "USB" "mx100:green:usb" "1-1-port2"
gpio-cdev: re-add nu801 userspace driver This reverts commit 80b7a8a7f5a0a88fde6dd19f097df4d7cac9ff04. Now that 5.10 is the default kernel for all platforms, we can bring back the NU801 userspace driver for platforms that rely on it. Currently it's used on the MX100 x86_64 target, but other Meraki platforms use this controller. Note that we also now change how we load nu801. The way we did this previously with procd worked, but it meant it didn't load until everything was up and working. To fix this, let's call nu801 from boot and re-trigger the preinit blink sequence. Since nu801 runs as a daemon this is now something we can do. Signed-off-by: Chris Blake <chrisrblake93@gmail.com> (removed empty line, currently only MX100 uses it so: @TARGET_x86) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
2022-03-19 22:13:42 +00:00
ucidef_set_led_default "diag" "DIAG" "mx100:green:tricolor" "1"
x86: add support for Meraki MX100 This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2021-10-01 14:38:56 +00:00
;;
x86: Add APU6 board support for startup detection The APU6 is similar to the APU4 except for eth0 having an SFP cage instead of RJ45. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
2022-12-30 18:17:10 +00:00
pc-engines-apu1|pc-engines-apu2|pc-engines-apu3|pc-engines-apu4|pc-engines-apu5|pc-engines-apu6)
x86: add led driver for PC Engines APU1 This driver adds the LED support for the PC Engines APU1. This integrates the Linux kernel driver and includes a patch to support newer firmware versions. Also the default LED configuration is updated to use the correct devices. Signed-off-by: Andreas Eberlein <foodeas@aeberlein.de>
2020-06-23 20:59:26 +00:00
ucidef_set_led_netdev "wan" "WAN" "apu:green:3" "eth0"
ucidef_set_led_netdev "lan" "LAN" "apu:green:2" "br-lan"
ucidef_set_led_default "diag" "DIAG" "apu:green:1" "1"
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
;;
x86: base-files add support for Sophos 135r3/135r3w The Sophos SG/XG-135 revision 3 has odd numbering of eth ports where the WAN port (as marked on the case) is: `eth6` and `eth0`, `eth1`, `eth2`, `eth3`, `eth5`, `eth7`, `eth8` are LAN ports. Port `eth4` seems to be the SFP port. Also add the missing LED definition for supported Sophos devices. Original discussion at: https://forum.openwrt.org/t/openwrt-on-revision-3-of-sophos-desktop-appliances/152912 Signed-off-by: Stan Grishin <stangri@melmac.ca>
2023-02-27 00:04:33 +00:00
sophos-sg-105wr1|sophos-sg-125wr1|sophos-sg-135wr1|sophos-xg-105wr1|sophos-xg-125wr1|sophos-xg-135wr1)
ucidef_set_led_netdev "wlan" "WiFi" "ath9k-phy0" "phy0tpt"
;;
base-files: x86 fix 01_leds Syntax error Cezary Jackiewicz reported: | Syntax error in line /etc/board.d/01_leds#L22 - missing "\" Fixes: c191c2d46f00 ("x86: base-files add support for Sophos 135r3/135r3w") Reported-by: Cezary Jackiewicz <cezary@eko.one.pl> Signed-off-by: Stan Grishin <stangri@melmac.ca> (buffed up commit message) Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 4b8b2f4f978d6df586dd7ce4dcc3e1286b93bd48)
2023-05-28 04:48:26 +00:00
sophos-sg-105wr2|sophos-sg-125wr2|sophos-sg-135wr2|sophos-xg-105wr2|sophos-xg-125wr2|sophos-xg-135wr2|\
x86: base-files add support for Sophos 135r3/135r3w The Sophos SG/XG-135 revision 3 has odd numbering of eth ports where the WAN port (as marked on the case) is: `eth6` and `eth0`, `eth1`, `eth2`, `eth3`, `eth5`, `eth7`, `eth8` are LAN ports. Port `eth4` seems to be the SFP port. Also add the missing LED definition for supported Sophos devices. Original discussion at: https://forum.openwrt.org/t/openwrt-on-revision-3-of-sophos-desktop-appliances/152912 Signed-off-by: Stan Grishin <stangri@melmac.ca>
2023-02-27 00:04:33 +00:00
sophos-sg-105wr3|sophos-sg-125wr3|sophos-sg-135wr3|sophos-xg-105wr3|sophos-xg-125wr3|sophos-xg-135wr3)
ucidef_set_led_netdev "wlan" "WiFi" "ath10k-phy0" "phy0tpt"
;;
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 New Issue Copy Permalink