On Tue, Jul 6, 2010 at 13:28, Lee Jones <lee.jones@xxxxxxxxxxxxx> wrote:
>> Only some devices have a driver bound. Only "bus" devices, "class"
>> devices never have a driver.
>>
>> It's just the symlink "driver" in /sys in the device directory.
>>
>> Your platform device may just be a plain registered device, and not
>> probed and bound by a driver in that sense. Usually only enumeratable
>> buses have drivers that create devices when they are discovered.
>
> I guess I'd better tell you the full story then.
>
> I am working on a driver (module) that provides a direct link "CPU <-> Video Codec", which I believe is non-discoverable.
>
> I figured that I'd be able to send the uevent by registering the device as a platform one in architecture specific code.
>
> A uevent is sent, but it is missing the DRIVER parameter.
>
> This is the generic parameter which is used in the udev rules.
>
> /lib/udev/rules.d/80-drivers.rules, DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe -b $env{MODALIAS}"
What do you mean? This rule is skipped only if DRIVER is set. This is
to prevent calling modprobe for devices which already have a driver
bound and looking-up and loading another module would not do anything
to this device. If you don't have a driver this rule will always run.
:)
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
