On Mon, May 14, 2012 at 12:27:11PM -0400, Dave Reisner wrote:
On Mon, May 14, 2012 at 06:19:11PM +0200, Thomas Bächler wrote:
Am 14.05.2012 17:59, schrieb Dave Reisner:
I'm more inclined to think that this is module specific than udev specific. Either way, probably best to leave the udev startup where it is and just move out the cleanup. Boooo.
Have it your way and introduce early hooks.
I thought about that briefly, and can't see a use for it beyond starting udev. It's low overhead, but I'm not convinced there's enough need for it.
Maybe someone can prove me wrong.
d
So, I'm going back on this and implementing early hooks anyways. I'm going to take some time to see if I can optimize this at all so that we can avoid rereading the same N files 4 times. Same user who reported the radeon fail confirmed that udev as an early hook works well with loading radeon in early userspace, but I guess we knew already that it would work. d