Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts

[Patrick Mansfield <patmans@us.ibm.com>]

On Tue, Feb 22, 2005 at 02:51:10PM +0300, Roman Kagan wrote:

> BTW one more item to track the dependencies for (in case you don't have
> enough :) is the firmware files.  You can identify which modules may
> need firmware by checking their dependency on firmware_class, but I see
> no way of knowing which firmware files they are going to request.  To
> make it worse, firmware is the (only) kind of hotplug events which can
> be neither delayed (due to limited timeout) nor postponed to be replayed
> later on.

Hi -

Maybe we need in module.h:

#define MODULE_FIRMWARE(_firmware) MODULE_INFO(firmware, _firmware)

And use it for any module that can generate a call to request_firmware().
(Too bad we can't hook right into request_firmware(), since some callers
pass variables as the name.)

Then the *rd generator queries the modules and copies any "firmware" file
from /lib/firmware into the initrd/ramfs.


Why is there no file system reader (like grub has)? So the initrd could just
copy files off of a file system as needed without mounting them.  There
are probably device naming / slippage problems with using a physical path
especially for scsi: usb mass storage, SAS/SATA, SPI, FC etc. But are
those bad enough to reject such an approach?

-- Patrick Mansfield


-------------------------------------------------------
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