aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/base-files
Commit message (Collapse)AuthorAgeFilesLines
...
* lantiq: show xdsl line init status on shared dsl/internet ledMathias Kresin2017-06-172-8/+35
| | | | | | | | | | | | | On boards which don't have a distinct internet and dsl led, use the shared LED to indicate the xdsl line state and any traffic that is send/received via the netdev. This traffic doesn't necessarily need to be internet traffic. Rename the shared LED of existing configs to "dsl", to match the new defaults. The configuration of the to be renamed LED is identical with the new defaults. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: restore netdev trigger of dsl led on line upMartin Schiller2017-06-171-1/+14
| | | | | | | | Allows to use a single LED for line init status indication and to show any rx/tx activity on a synchronized dsl line. Signed-off-by: Martin Schiller <ms@dev.tdt.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Allnet ALL0333CJ supportTino Reichardt2017-06-032-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Allnet ADSL2+ Modem ALL0333CJ. Specifications: - SoC: Amazon-SE - RAM: 16MB - Storage: 4MB NOR FLash - LEDs: Power, Ethernet, DSL (Sync) - Buttons: 1x Reset Button (not currently supported, will be done) - 1x Ethernet-Port: 1x RJ45 10/100BaseTX - 1x WAN-Port: AnnexB & J, G.992.1(ADSL), G.992.3(ADSL2), G.992.5(ADSL2+) Installation: - can be done via telnet+tftp or serial console - default passwords: - via telnet (root:admin) - via webinterface http://172.16.1.254:8235/ (admin:coolwhite) Installation via telnet / tftp: host: # your own host must have an tftpd daemon, then do this: host: ifconfig eth0:172 172.16.1.1 up host: # telnet to allnet modem, root:admin host: telnet 172.16.1.254 modem: # kill this daemon, it spams your console modem: killall dsl_cpe_control modem: # change to some place in ram: modem: cd /ramdisk/tftp_upload modem: # load lede-lantiq-ase-ALL0333CJ-squashfs-sysupgrade.bin alias uImage modem: tftp -g -r uImage 172.16.1.1 modem: # load these extra tools from your tftpd via: modem: # source: https://github.com/mcmilk/uboot-utils/releases/download/0.1/mips32.tar.gz modem: tftp -g -r flashwrite 172.16.1.1 modem: tftp -g -r fw_setenv 172.16.1.1 modem: tftp -g -r fw.conf 172.16.1.1 modem: ln -s fw_setenv fw_printenv modem: chmod +x * modem: ./fw_setenv disable_recovery y modem: ./fw_setenv kernel_addr 0xb0010000 modem: ./flashwrite /dev/mtd/1 uImage 0 Installation via serial line at uboot: uboot: # erase everything exept bootloader uboot: protect on b0000000 +10000; protect on b03f0000 +10000 uboot: erase all uboot: # get new firmware via tftp: uboot: tftpboot 0x80100000 uImage; setenv kernel_addr 0xb0010000 uboot: # copy to flash: uboot: cp.b 0x80100000 $(kernel_addr) $(filesize) uboot: # disable proprietary image checking: uboot: setenv disable_recovery=y; saveenv uboot: # reboot with LEDE ;) uboot: reset Ethernet works as expected, DSL syncronization does not work properly currently, I am working on this issue. Signed-off-by: Tino Reichardt <milky-lede@mcmilk.de>
* lantiq: modified lantiq_dsl.sh status output of latencyHelge Mader2017-06-021-1/+1
| | | | Signed-off-by: Helge Mader <ma@dev.tdt.de>
* lantiq: fix lantiq_dsl.sh status and lucistat outputHelge Mader2017-06-021-12/+12
| | | | Signed-off-by: Helge Mader <ma@dev.tdt.de>
* treewide: fix device tree path in scriptsMathias Kresin2017-05-261-1/+1
| | | | | | | | The device tree is at /proc/device-tree/ without a base subdir. Fixes: da472e5b30f6 ("treewide: access device tree from userspace via /proc/") Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: access device tree from userspace via /proc/Mathias Kresin2017-05-261-1/+1
| | | | | | | Access the device tree via /proc/device-tree/ is the documented way to access the properties. Everything else might not work in future. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix avm fritz box mac addressesMathias Kresin2017-05-052-6/+10
| | | | | | | | | It has been shown that the Fritz boxes have the correct mac address set in the wireless calibration data/eeeprom. Use this mac address as base for the ethernet and xdsl interface increment/decrement the address to match the values stored in the tffs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: improve DGN3500 LED definitionsKevin Darbyshire-Bryant2017-04-211-0/+54
| | | | | | | | | | | | | | | | Add red:internet led on gpio 30 previously claimed as missing. Wifi led was claimed as blue however there are no blue leds on the board at all. Actually there are two wifi leds, green & amber so add definitions for those. Make the newly discovered green wifi led gpio 14 the default. There is no amber power led on this board. The mention of the amber power led in the manual means power red and power green at the same time. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> [removed unnecessary aliases, add migration script] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove lantiq_board_model, it is unusedFelix Fietkau2017-03-221-9/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: remove lantiq_board_name, use the generic function insteadFelix Fietkau2017-03-226-18/+5
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: move lantiq_board_detect() to 03_preinit_board.shFelix Fietkau2017-03-222-10/+10
| | | | | | It is only used there Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: Shortcut non-pppoa interfaces in dsl_notifyOswald Buddenhagen2017-03-171-6/+8
| | | | | | No need to query 'up' and 'auto' when they are not going to be used. Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
* lantiq: use the P2812HNUF* wan port as wanMathias Kresin2017-03-111-1/+1
| | | | | | | The port is labeled as wan and was only used as lan port because of the "tx ring full" issues fixed with 8f02f7c. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: xrx200: use vlan for ethernet wan portMathias Kresin2017-03-111-3/+3
| | | | | | | | | | | | | | | | | | | | | | | Using the lantiq,wan device tree property for one interface node and the lantiq,switch device tree property for another interface node at the same time was never intended/isn't supported at the moment. The property is meant to be used in two phy operation mode where one phy is assigned to an interface without lantiq,* device tree property and the other phy is assigned to an interface with the lantiq,wan device property to have two netdevs. If both properties are used at the same time, the lantiq,wan interface is shown as independent netdev but not able to operate independent. The port needs to be managed via swconfig. These dependency is not obvious and fooled already a lot of users. Add a default WAN vlan for xrx200 devices having an ethernet WAN port and remove the lantiq,wan device tree property. Leave it up to the user to set the ethernet WAN port as default WAN interface or to use this port as additional LAN port. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add support for the Alpha ASL56026Alex Maclean2017-03-081-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ASL56026 is a VDSL2 router with dual 100mbit ethernet, also known as the ECI B-FOCuS V-2FUb/I. CPU: Lantiq XRX268 v1.1 at 333MHz Modem: Lantiq VRX208 RAM: 32MiB DDR2 at 167MHz Flash: 8MiB NOR, Spansion S29GL064N90TF04 UART is at JP1: Pin 1 TX Pin 2 GND Pin 3 +3.3V Pin 4 NC Pin 5 RX Boot selection pins are exposed via several resistor jumpers: boot_sel0 is at J15, on the rear of the board. Default is high. boot_sel1 is at J3, next to the flash - it is also the flash CE# pin. Default is low. boot_sel2 is at J12, directly below the SoC. Default is low. boot_sel3 is at J16, on the rear of the board. Default is low. The boot_sel pins should never be shorted, the jumper must be moved or a lower value resistor used to change the pull (existing resistors are 4k7, 1k should work) To install with the stock bootloader you must break the built in image selection process which uses at least the following vars: f_upgrade_addr, f_upgrade2_addr, loadaddr, kernel_addr, activeregion, committedregion This is done by setting loadaddr and both f_upgrade_addr vars to the same address: VR9 # setenv loadaddr 0xB0040000 VR9 # setenv f_upgrade_addr 0xB0040000 VR9 # setenv f_upgrade2_addr 0xB0040000 VR9 # saveenv Then flash the firmware image: VR9 # tftpboot 0x81000000 lede-lantiq-xrx200-ASL56026-squashfs-sysupgrade.bin VR9 # erase B0040000 +${filesize} VR9 # cp.b 0x81000000 0xB0040000 ${filesize} Signed-off-by: Alex Maclean <monkeh@monkeh.net>
* lantiq: fix warning if ltq_atm modules are missingMathias Kresin2017-02-181-2/+1
| | | | | | | | | Fixes the following warning on first boot if the ltq_atm modules are not included in the image: ls: /lib/modules/4.4.49/ltq_atm*: No such file or directory Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: set the internet led interface according to wan interfaceMathias Kresin2017-02-181-0/+1
| | | | | | | | Use the nas0 interface for the netdev trigger as default. Use the ptm0 interface for xRX200 boards to match the default wan interface set in 02_network. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: introduce lantiq_is_vdsl_systemMathias Kresin2017-02-182-1/+5
| | | | | | | Move the code to check if the current system is a system with vdsl support to a dedicate function to make it reusable. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix ARV7519RW22 switch port indexingMathias Kresin2017-02-181-1/+1
| | | | | | Fixes FS#454. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix patching the wifi mac address on BTHOMEHUBV3AMartin Blumenstingl2017-02-131-1/+1
| | | | | | | | | | | | | | | | | | | The firmware hotplug script tries to read the mac address from a partition with the name "uboot-env" which does not exist (instead it's name is uboot_env). This broke calculation of the new checksum (after patching the mac address) which resulted in ath9k refusing to use the EEPROM data. The original error reported by ath9k was: PCI: Enabling device 0000:00:0e.0 (0000 -> 0002) ath: phy0: Bad EEPROM checksum 0x2523 ath: phy0: Unable to initialize hardware; initialization status: -22 ath9k 0000:00:0e.0: Failed to initialize device Fixes: a20616863d32d9 ("lantiq: use ath9k device tree bindings binding/owl-loader") Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: simplify ath9k eeprom extraction scriptMathias Kresin2016-12-081-11/+16
| | | | | | | | | | | Add an extra function to patch the mac and fixup the checksum afterwards. Calculate the checksum position automatically. The offset to the mac address is the same for all checksum protected EEPROMs. No EEPROM requires a byte swapped mac address. The mac byte swap code was required due to an bug in the script that is now fixed. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix ath9k EEPROM data swapping for some devicesMartin Blumenstingl2016-12-081-14/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The EEPROM data in the flash of the ARV7518PW, ARV8539PW22, BTHOMEHUBV2B and BTHOMEHUBV3A is stored byte-swapped (swab16), meaning that for example the ath9k base_eep_header fields "version" (high and low byte), "opCapFlags" and "eepMisc" are swapped (the latter ones are just 1 byte wide, thus their position is swapped). The old "ath,eep-endian" property enabled the corresponding swapping logic in the ath9k driver (swab16 in ath9k_hw_nvram_swap_data, which is based on the magic bytes in the EEPROM data which have nothing to do with the calibration data - thus this logic should not be used anymore). Since we have switched to the upstream ath9k devicetree bindings there is no binding anymore which enables swab16 in ath9k (as this logic is not recommended anymore as explained above), leading to ath9k initialization errors: ath: phy0: Bad EEPROM VER 0x0001 or REV 0x00e0 (this shows that the version field is swapped, expected values are VER 0x000E and REV 0x0001) Swapping the ath9k calibration data when extracting it from the flash fixes the devices listed above (all other devices do not require additional swapping, since the position of the fields is already as expected by ath9k). This allows ath9k to read the version correctly again, as well as the more important "eepmisc" field (which is used for determining whether the data inside the EEPROM is Big or Little Endian which is required to parse the EEPROM contents correctly). Fixes: a20616863d3 ("lantiq: use ath9k device tree bindings binding/owl-loader") Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: fix image validation errorsMathias Kresin2016-12-042-4/+4
| | | | | | | The boards did not have the name set that is expected during metadata validation on sysupgrade. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use BT HomeHub 5 Type A OEM partition layoutMathias Kresin2016-11-293-20/+22
| | | | | | | | | | | | | | | | | | | | This way the on nand bad block table is preserved and used. Add support for nand OOB ECC checksums as well. It should fix all reported ubi errors, which were all related to bad nand blocks and a purged on nand bad block table. The existing ubi partition will be reused, which eliminates the need to touch the caldata during initial install. The BT u-boot has support for loading a kernel from an ubi volume. It isn't necessary any longer to replace the BT u-boot with a custom compiled one to use LEDE. It is required to restore the BT Firmware and install LEDE from scratch to switch to the new partition layout. An image for restoring the BT firmware and installing LEDE is provided at https://github.com/mkresin/lede/releases. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use ath9k device tree bindings binding/owl-loaderMartin Blumenstingl2016-11-291-0/+140
| | | | | | | | | | | | | | | | | This moves the extraction of the eeprom/calibration data to a hotplug firmware script. Additionally it modifies all .dts to configure ath9k directly from within the .dts. The owl-loader approach enables support on devices with exotic eeprom data locations (such as unaligned positions on the flash or data inside an UBI volume). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> [add ath9k caldata mac address patcher] [fixes DGN3500 wifi mac] [fixes BTHOMEHUBV3A wifi mac] [set invalid mac for BTHOMEHUB2B, FRITZ3370, FRITZ7320 & FRITZ7360SL to restore previous random mac behavior] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove device specific sysupgrade image checksFelix Fietkau2016-11-201-22/+1
| | | | | | Replaced by image metadata Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: append metadata to imagesFelix Fietkau2016-11-191-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: fix port indexing for WBMR-300Felix Fietkau2016-11-141-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: use the device tree bindings from rt2x00 driverMathias Kresin2016-11-091-60/+0
| | | | | | | | | | | | | Set a device specific wireless mac address for ARV7506PW11, VGV7519 and VGV7510KW22. The one from the EEPROM is a generic one and the same on all boards. Use the wifi@0,0 label and the pci0,0 compatible string for the ARV7519PW and ARV7525PW since the pci vendor and device id is unknown. It should work anyway since the compatible string isn't evaluated (yet). Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix VGV7519 and VGV7510KW22 mac addressesMathias Kresin2016-11-091-2/+3
| | | | | | | | | | | | | | | | | The VGV7510KW22 stock firmware uses the following mac-addresses: lan (ifno 1): AA:BB:CC:DD:EE:60 wlan (ifno 2): AA:BB:CC:DD:EE:61 atm0 (ifno 3): AA:BB:CC:DD:EE:62 atm1/wan (ifno 4): AA:BB:CC:DD:EE:63 The VGV7519 stock firmware uses the following mac-addresses: lan: AA:BB:CC:DD:EE:EF wlan: AA:BB:CC:DD:EE:EF wan: AA:BB:CC:DD:EE:EE Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: rework VG3503J imageMathias Kresin2016-10-191-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the new image build code and remove the lzma loader. The lzma loader was used to cheat the signature validation of the bootloader and I found another way to do this. To migrate boards already using LEDE/OpenWrt to the new image the following steps need to be done once: VR9 # run reset_uboot_config VR9 # reset VR9 # setenv ethaddr AA:BB:CC:DD:EE:FF VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The mac address is printed on the label at the bottom of the case. The following steps are need to be done during first install: VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The image uses the uImage firmware splitter now instead of hardcoded kernel and rootfs partitions. The firmware partition size was extended to use flash space that was reserved for partitions required only by the ECI firmware. Due to the changes an upgrade to a later LEDE revision from a running LEDE is supported now. A default switch config was added and the device uses the same MAC addresses as the ECI firmware now instead of the same for all VG3503J. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use wpad-mini for WBMR boardsMathias Kresin2016-10-151-16/+0
| | | | | | | | | | The WBMR boards are the only ones in the whole tree selecting the wpad and hostapd-utils package by default. Remove the wps uci-default script as well, there is no obvious reason why the wps config need to be set only for this board. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix lantiq-dsl output spamMathias Kresin2016-10-111-1/+1
| | | | | | | | | | | | | | | | | In case the adsl/vdsl service is disabled intentional, the output is cluttered with the following message multiple times if the status of the dsl line is queried: killall: vdsl_cpe_control: no process killed If the dsl line status is queried by LuCI, the logfile is spammed with the message. Fix the issue by using killall in quite mode. In quite mode killall still returns a non-zero value if the to be killed process can not be found so that existing logic based on the return value still works. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use aliases device tree node for ledsMathias Kresin2016-10-051-1/+1
| | | | | | The chosen node is clearly the wrong place for aliases. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: cleanup led handling functionsMathias Kresin2016-10-053-19/+22
| | | | | | | | | Use a more generic name for the lantiq_get_dt_led_chosen function. Drop the lantiq_is_dt_led_chosen function. The lantiq_get_dt_led function can be used to achieve the same. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: apply alphabetical order to led fileMathias Kresin2016-10-051-12/+12
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: remove bad local shell variable declarationsJo-Philipp Wich2016-09-241-6/+1
| | | | | | | Local variable declarations outside of functions are illegal since the Busybox update to v1.25.0, therfore remove them from the appropriate places. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* lantiq: do not "local" variables outside of a functionMartin Blumenstingl2016-09-242-5/+5
| | | | | | | | | Older busybox versions allowed using the local keyword outside of functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not allow this anymore (leading to the following error when executing the script: "file: local: line nn: not in a function"). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* cleanup ucidef_set_interface* usageMathias Kresin2016-09-101-2/+2
| | | | | | | | - quote the interface name - remove call of not existing function - remove the proto if it's the default proto Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: apply alphabetical orderMathias Kresin2016-09-101-43/+43
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: cleanup default switch configMathias Kresin2016-09-101-32/+19
| | | | | | | | | | | | | | | | Add or fix the physical port number of switch ports to allow LuCI to display the ports in physical order. Remove the physical port number in case bridge port and physical port order are the same. Reorder the ucidef_add_switch parameter to be aligned with the switch port number. Remove board settings which are covered by the default case and remove comments. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: generate switch configuration for BTHOMEHUBV2B.Sigurd Hogsbro2016-08-201-1/+8
| | | | | | | Split from HH3A as it appears to have a different switch. https://en.wikipedia.org/wiki/BT_Home_Hub#Models_and_technical_specifications Signed-off-by: Sigurd Hogsbro <sigurd@hogsbro.org>
* lantiq: board.d: set lan mac address only where necessaryMathias Kresin2016-08-101-16/+8
| | | | | | | Do not set the lan mac address for boards which having the lan mac address already set in device tree source file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix switch configuration for EASY80920Hauke Mehrtens2016-07-281-0/+7
| | | | | | | | The device tree description misses some Ethernet ports and there was no model specified for this board. In addition there was no switch specific default configuration created. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: fix WBMR-300HPD switch port assignmentFelix Fietkau2016-07-281-4/+5
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: fix network in failsafeMathias Kresin2016-06-221-9/+1
| | | | | | | | | | So far the network in failsafe is setup only for one board. Use the eth0 interface as lan interface for all boards for now. If a board has its lan interface(s) on another eth, a special handling based on the board name can be added. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add support for ARV7506PW11 (Alice/O2 IAD 4421)Oswald Buddenhagen2016-06-223-1/+12
| | | | | | | | | | | | | | | | | | Ethernet, ADSL2+ and LEDs are fully functional. Supporting the two TAE ports and SIP gateway was not attempted. The WiFi is unreliable, due to experimental support for rt35xx family devices by the rt2800pci driver. Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de> [rebase to LEDE HEAD] [switch to normal image instead of brnboot image] [remove not required pinmux child nodes keys, leds, ebu, exin, pci_in and pci_out] [remove switch_rst pinmux child node (no support for hw reset in driver/setting a default GPIO value in DT] [enable usage of the wireless LED] [fixup mac address configuration] Sgned-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove gr7000 supportJohn Crispin2016-06-221-4/+0
| | | | | | this seems to have never worked as the wrong SoC is selected Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: diag - switch off the power led on failsafeMathias Kresin2016-06-201-0/+4
| | | | | | | | | | | | | | This patch is a follow up to commit 4cf3fd4 "add support for indicating the boot state using three leds". At the time of writing the patch, I wasn't aware that it's possible to switch info failsafe after boot (factory reset). Enabling the failsafe led without disabling the running led causes an unexpected led colour on devices using a single multicolour led to indicate the boot state. Signed-off-by: Mathias Kresin <dev@kresin.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 01:56:54 +0000