Mathias Kresin wrote:
> 2016-11-10 16:41 GMT+01:00 Jo-Philipp Wich :
> > Hi Karl,
> >
> > I think there is not much speaking against making the led init script
> > run earlier. I think it would make sense to have it START=11, right
> > after /etc/init.d/boot.
>
> I've a TDW-8980 here, where the
2016-11-10 16:41 GMT+01:00 Jo-Philipp Wich :
> Hi Karl,
>
> I think there is not much speaking against making the led init script
> run earlier. I think it would make sense to have it START=11, right
> after /etc/init.d/boot.
I've a TDW-8980 here, where the ath9k driver acts as GPIO controller
for
Hi Karl,
I think there is not much speaking against making the led init script
run earlier. I think it would make sense to have it START=11, right
after /etc/init.d/boot.
~ Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.
Given that the current leds init script only looks for some
explicit values, I've done the following to have a led _listed_
in the UCI file, and available to leds.sh, but not actually
touched by the init script...
> ucidef_set_led_default "etactica" "etactica" "eg200:red:etactica" "ignored"
It
Hi Sven,
imho it is preferable to have usable, but inactive LEDs available by
default in the system configuration.
~ Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
