Messages in this thread | | | Date | Wed, 22 Feb 2006 21:57:07 +0100 | From | Diego Calleja <> | Subject | Re: 2.6.16-rc4: known regressions |
| |
El Wed, 22 Feb 2006 11:54:10 -0800, Andrew Morton <akpm@osdl.org> escribió:
> Yes, I tend to think that insmod should just block until all devices are > ready to be used. insmod doesn't just "insert a module". It runs that > module's init function.
However, in current systems a device is ready only iff the corresponding sysfs tree has been created or a hotplug event has be launched, and that's the one sane place where userspace can wait for "something". Drivers need to setup the name of the sysfs classes, so if modules could <crack smoking> export some of that info to insmod maybe insmod could be taught to do wait for things in userspace or wait for events coming from the $FOO.ko module
(ok, maybe ugly but sounds somewhat cleaner than just adding a "sleep(magicnumber)" to insmod) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |