Firmware class breaks udev

[Hannes Reinecke <hare@suse.de>]

Hi Kay,

The current implementation of the firmware class breaks a fundamental
assumption in udev: that the physical device can be initialised fully
prior to executing the next event for that device.

As the firmware is indeed _required_ to initialise the device we wait
until the timeout is triggered and the try to execute the fimware event,
which of course will fail.

If you have a look at the firmware class you'll see exactly what happens:
The class insists on sending their own firmware events during
initialisation. This code is typically executed during device probing,
so the modprobe for this device will still be running when the firmware
event is triggered.

Which is also why you're seeing this only when using the events
themselves, as when executing modprobe directly udev is only started for
 the firmware event, which will succeed as no physical device event is
in the queue.

For now I'll be putting in a quick exit for firmware events (ie not wait
for the devices initialisation to finish) but this is nevertheless _nasty_.

Currently the firmware class is definitely not compliant to the driver
model. So either we should fix the firmware class or extend the driver
model to allow for such beasts; Kay, your kobj hotplug extension might
be a way to go.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux AG				S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel