Re: firmware separation filesystem (fwfs)

[Alan Cox]

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 ?