netdev
[Top] [All Lists]

Re: ipw2100: firmware problem

To: Andi Kleen <ak@xxxxxx>
Subject: Re: ipw2100: firmware problem
From: Olivier Galibert <galibert@xxxxxxxxx>
Date: Thu, 9 Jun 2005 23:12:42 +0200
Cc: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev list <netdev@xxxxxxxxxxx>, kernel list <linux-kernel@xxxxxxxxxxxxxxx>, "James P. Ketrenos" <ipw2100-admin@xxxxxxxxxxxxxxx>
In-reply-to: <m1is0nvdkw.fsf@muc.de>
Mail-followup-to: Olivier Galibert <galibert@xxxxxxxxx>, Andi Kleen <ak@xxxxxx>, James Ketrenos <jketreno@xxxxxxxxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev list <netdev@xxxxxxxxxxx>, kernel list <linux-kernel@xxxxxxxxxxxxxxx>, "James P. Ketrenos" <ipw2100-admin@xxxxxxxxxxxxxxx>
References: <20050608142310.GA2339@elf.ucw.cz> <42A723D3.3060001@linux.intel.com> <m1is0nvdkw.fsf@muc.de>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
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.

  OG.

<Prev in Thread] Current Thread [Next in Thread>