diff options
| author | John Crispin <blogic@openwrt.org> | 2015-12-11 15:05:30 +0000 |
|---|---|---|
| committer | John Crispin <blogic@openwrt.org> | 2015-12-11 15:05:30 +0000 |
| commit | 0b185fc4c8ab80d00f5646693c259f5478fc5ab2 (patch) | |
| tree | 1bcd185565c22f9204fcd4437d92ef7ee2f4ba19 /target/linux/lantiq/xrx200 | |
| parent | a049351ee0f82e9e88ea54c940f560de0f18ee52 (diff) | |
| download | master-187ad058-0b185fc4c8ab80d00f5646693c259f5478fc5ab2.tar.gz master-187ad058-0b185fc4c8ab80d00f5646693c259f5478fc5ab2.tar.bz2 master-187ad058-0b185fc4c8ab80d00f5646693c259f5478fc5ab2.zip | |
lantiq: fix led setup after switch to uci-defaults-new.sh
The switch to uci-defaults-new.sh revealed a bug in the former used
uci-defaults.sh, which failed to add leds with colons in the led name.
This bug isn't any longer present in uci-defaults-new.sh and therefore
all via DT defined leds will be added to /etc/config/system with their initial
on/off state, regardless whether they are already added by the board specific
led mappings.
This results for a BTHOMEHUBV5A into the following led configuration:
- soc:blue:power is added as led_power with the initial state "switched on"
- soc:blue:power is added as led_soc_blue_power with the initial state "switched off"
With the final result of a switched off power led after boot.
The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47850 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/lantiq/xrx200')
0 files changed, 0 insertions, 0 deletions