From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Kagan Date: Tue, 22 Feb 2005 20:03:58 +0000 Subject: Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts Message-Id: <20050222200358.GK11284@katya> List-Id: References: <20050217210620.A20645@banaan.localdomain> In-Reply-To: <20050217210620.A20645@banaan.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Feb 22, 2005 at 11:26:09AM -0800, Patrick Mansfield wrote: > 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. > > 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.) That's the problem here as well: you'll have to manually keep MODULE_FIRMWARE in sync with what you actually pass to request_firmware(). > 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. Alternatively grub can perhaps be taught to use its filesystem reader and generate initramfs on the fly from /bin, /etc, /lib, /sbin of the actual root filesystem. This may be slow, though... Roman. ------------------------------------------------------- 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_id396&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