* Asynchronous driver initialization and request_firmware/post
@ 2005-03-11 19:07 Jon Smirl
2005-03-11 19:38 ` Jon Smirl
0 siblings, 1 reply; 2+ messages in thread
From: Jon Smirl @ 2005-03-11 19:07 UTC (permalink / raw)
To: linux-hotplug
BenH and I have been emailing about how to load a driver that needs
firmware or posting. He wants to do this asynchronously to support
things like suspend/resume. It looks like the current synchronous
request_firmware() is going to have trouble with resume.
Is there a mechanism for letting the driver load and probe with the
probe function doing nothing but triggering the firmware/posting event
and then mark the driver off-line somehow? The problem is, you load
the driver and the firmware or post program is mission or set up
wrong, how do you inform the user of the error? Shouldn't this be done
in a standard way?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-11 19:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-11 19:07 Asynchronous driver initialization and request_firmware/post Jon Smirl
2005-03-11 19:38 ` Jon Smirl
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).