From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: ipw2100: firmware problem Date: Thu, 09 Jun 2005 19:13:50 -0400 Message-ID: <42A8CD2E.7020504@pobox.com> References: <20050608142310.GA2339@elf.ucw.cz> <42A723D3.3060001@linux.intel.com> <20050609211242.GA30319@dspnet.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andi Kleen , James Ketrenos , Netdev list , kernel list , "James P. Ketrenos" Return-path: To: Olivier Galibert In-Reply-To: <20050609211242.GA30319@dspnet.fr.eu.org> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Olivier Galibert wrote: > On Thu, Jun 09, 2005 at 03:56:15PM +0200, Andi Kleen wrote: > >>I guess at some point we will need a file system in there, but - oops - >>we already have one, dont we? :) > > > Well, you could put .config in it too. > > Frankly, a filesystem that: > - can be somehow linked with vmlinux and not separate like an initrd > > - editable post vmlinux-linking > > - gives files that can be accessed from request_firmware, acpi and > friends even rather early in the boot process (i.e. well before any > userland is allowed to exist) > > - accessible post-boot through mounting of a special fs and/or /proc or something > > would be quite useful. This exists. It's called initramfs. Read the kernel code :) Jeff