Re: Kernel Firmware Loading

[Kay Sievers <kay.sievers@vrfy.org>]

On Mon, Oct 31, 2005 at 11:59:05AM +0100, Duncan Sands wrote:
> It would be nice if the driver was more helpful here,
> by trying to load the firmware more than once.  It's
> a bit tricky though.  For example, you could say: "if
> the firmware wasn't found, then try to load it when
> someone opens a connection".  Unfortunately, while this
> is possible with the speedtch modem, this isn't possible
> with the connexant access runner: you can't correctly create
> an ATM device unless the firmware was already loaded into
> the modem, which means it's impossible to even try to
> open a connection before the firmware is loaded.  Another
> possibility is to try to load the firmware every couple
> of seconds.  I could certainly do that, but it's not very
> elegant.
> 
> In any case, I too am interested in hearing what the hotplug
> people have to say.

I like to see the stupid timeout in the request_firmware to completely
go away. It doesn't make any sense. The drivers should use the async
version of request_firmware() anyway and the so called syncronous version
should be removed.
If the kernel sends the request out and it gets lost during early boot,
you can just fulfill it any time later by looking at the outstanding
requests in sysfs.
If you manage it in 10 seconds from kernel init to the mounted root, you
may be able to do this today... :)

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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