John Crispin 787120e3a3 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> SVN-Revision: 47850		2015-12-11 15:05:30 +00:00
..
imagebuilder	imagebuilder: store package lists in cache directory	2015-09-14 16:57:03 +00:00
linux	lantiq: fix led setup after switch to uci-defaults-new.sh	2015-12-11 15:05:30 +00:00
sdk	sdk: provide explicit CONFIG_MODULES kconfig symbol	2015-07-27 23:45:15 +00:00
toolchain	toolchain: respect CONFIG_VERSION_FILENAMES and add host system suffix	2015-02-07 21:01:37 +00:00
Config.in	toolchain: add support of ARC architecture	2015-11-10 12:03:59 +00:00
Makefile	target: do not make target/*/install depend on target/*/compile - removes one redundant kernel build dir call on target/install	2012-06-06 17:24:05 +00:00