On Thu, Aug 19, 2010 at 13:42, Tejun Heo <tj@xxxxxxxxxx> wrote: > What I was curious about is what > happens if some of them are already in the kernel but not all of them. > udev would still be invoked the same and modprobe too but device - > driver matching can and is probably likely to happen before modprobe > finishes loading all the drivers, right? Or is there a mechanism to > hold off device - driver matching before the udev finishes handling > the event for the controller? The compiled-in drivers have matched and bound and blocked-out any other driver of the device long before udev is even started load the other drivers. The matching compiled-in drivers will always win over the modules, regardless of their priority. Is that what you mean? :) Kay -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
