Hello,
On 08/19/2010 02:52 PM, Kay Sievers wrote:
> If the device we are currently handling has already a driver bound,
> udev will not call modprobe.
> It's:
> DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe -bv $env{MODALIAS}"
> which means:
> !DRIVER && MODALIAS -> modprobe
Okay, thanks for the explanation.
>> is
>> there a mechanism to hold off device - driver matching before
>> modprobe is finished? Probably not, right?
>
> What does 'modprobe finished' mean? The modprobe called for this
> specific device? The first driver loaded and initialized will win. If
> multiple drivers are loaded with the same modprobe call, the later
> ones will never see the device.
Yeap, you're right. Loading all drivers is for cases where
controllers supported by different drivers share the same PCI ID (some
of hpt's need this). So, the priority thing is mostly broken except
for pretty simple cases. :-( Oh well, it has worked well enough till
now. Let's leave it alone for now.
Thanks.
--
tejun
--
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
