[OpenWrt-Devel] [LEDE-DEV] LED uci policy for not actively used LEDs

Karl Palsson karlp at tweak.net.au
Thu Nov 10 15:16:03 EST 2016

Mathias Kresin <dev at kresin.me> wrote:
> 2016-11-10 16:41 GMT+01:00 Jo-Philipp Wich <jo at mein.io>:
> > 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 the wireless LED [0]. The wireless led is
> populated to sysfs only after the ath9k driver is loaded. This
> might take some time, since the ath9k EEPROM needs to be loaded
> from flash first to fixup an invalid PCI vendor and device id.
> Long story short, changing the START param might lead to a
> start of the led init script before all referenced leds are
> available in sysfs. At the moment I see this issue already on
> the TDW-8980 on first boot. And yes, I know that a propper fix
> would be some kind of hotplug script.

hehe, it's almost like a pile of shell scripts is a problematic
way of ordering startup, and we should build something that can
handle dependencies of interrelated items or something....

hang on...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP Digital Signature
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20161110/3699faed/attachment.sig>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list