From: Roman Kagan <rkagan@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
Date: Tue, 22 Feb 2005 20:03:58 +0000 [thread overview]
Message-ID: <20050222200358.GK11284@katya> (raw)
In-Reply-To: <20050217210620.A20645@banaan.localdomain>
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_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
next prev parent reply other threads:[~2005-02-22 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 20:06 [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts Erik van Konijnenburg
2005-02-17 21:50 ` Jeff Garzik
2005-02-17 22:50 ` Roman Kagan
2005-02-19 2:00 ` Erik van Konijnenburg
2005-02-22 11:51 ` Roman Kagan
2005-02-22 17:48 ` Harald Hoyer
2005-02-22 19:26 ` Patrick Mansfield
2005-02-22 20:03 ` Roman Kagan [this message]
2005-02-22 21:25 ` Erik van Konijnenburg
2005-02-22 21:48 ` Erik van Konijnenburg
2005-02-22 22:57 ` Erik van Konijnenburg
2005-03-17 8:26 ` Werner Almesberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050222200358.GK11284@katya \
--to=rkagan@mail.ru \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).