Re: firmware separation filesystem (fwfs)

From: Alan Cox (
Date: Sat Apr 19 2003 - 16:52:44 EST

On Sad, 2003-04-19 at 21:41, Manuel Estrada Sainz wrote:
> > fwfs is a broken idea because it leaves the data in kernel space. On
> > a giant IBM monster maybe nobody cares about a few hundred K of cached
> > firmware in the kernel, but the rest of us happen to run real world
> > computers.
> Many drivers currently include this same data in kernel space, in in
> headers, what I am trying to do is make it easy for them to support
> fwfs (or whatever it becomes in the end).

So what is the value in changing them to this, then changing them again
to put the firmware in userspace ? Surely you'd be better off writing
a generally usable request_firmware() hotplug interface ?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:26 EST