Mathias Kresin <d...@kresin.me> wrote: > 2016-11-10 16:41 GMT+01:00 Jo-Philipp Wich <j...@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...
signature.asc
Description: OpenPGP Digital Signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
