lkml.org 
[lkml]   [2003]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: firmware separation filesystem (fwfs)
From
Date
On Iau, 2003-04-17 at 02:23, David Gibson wrote:
> > But so would loading it from hotplug via ioctl. It might be we want
> > a clean hotplug way to ask for 'firmare for xyz'.
>
> True, but ioctl()s are horrid. And the driver needs to set up a
> suitable device to which the ioctl() is applied, and deal with binding
> the right image to the right instance, which can get messy in some

You are ignoring the main issue of discussion. I don't care if its
ioctl, tcp/ip over carrier pigeon or a pipe.

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.

Catting the firmware to a device node also works fine for me as an
API, but keep the firmware in userspace.



Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:34    [W:0.073 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site