Re: Rework of request firmware

[David Zeuthen <david@fubar.dk>]

Hey Kay,

On Sun, 2005-03-20 at 14:37 +0100, Kay Sievers wrote:
> before we start hacking on it. The current request_firmware() is a
> not-so-nice example for doing it that way. All that stuff needs to play
> with hotplug, initramfs/bootup, suspend/resume. And we should come up
> with something that fits _all_ the needs and move the current
> request_firmware-users over to it.

On that topic, one of the things I'd like a future scheme to do is not
only emitting the request_firmware() event, but also emitting events
like someone_uploaded_firmware() and timeout_waiting_for_firmware().
Plus some state in sysfs to keep track of the state. All but
request_firmware() probably don't need hotplug events; kobject_uevents
would be fine for me, since I'd want some daemon to listen to it anyway.

All that probably needs to be changed to fit in with what Jon is doing;
the idea here is that we want to notify the user, in the desktop
session, that the firmware/initialization needed is not available. Then
the user can take appropriate action. 

Thanks,
David



-------------------------------------------------------
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=click
_______________________________________________
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