Re: Kernel Firmware Loading

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

On Mon, Oct 31, 2005 at 03:41:59PM +0100, Duncan Sands wrote:
> > > > 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.
> > > 
> > > But isn't the problem different: the request did not get lost: it reached
> > > the script (or whatever), the script couldn't find the firmware file and
> > > cancelled the load?  This has nothing to do with timeouts and events
> > > getting lost...
> > 
> > Well, just check with the firmware script and never cancel a request
> > if you are in initramfs.
> 
> But who will do the actual firmware loading when the root filesystem is
> mounted?

The usual event replay we do for all other devices too. "Coldplug" or
whatever you can call it. The thing we did with old hotlug *.rc scripts and
we tried with udevsysnthesize and do now with the "uevent" triggers in sysfs...

> And how will they know that the filesystem is mounted?

Well its not magic, you mounted it, right? So you should know it. :)
Get it from the fs itself, get it from /proc, remember the state, put a
different script in initramfs, ...

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