[lkml]   [2003]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: request_firmware() hotplug interface, third round.
Am Freitag, 16. Mai 2003 20:49 schrieb Jean Tourrilhes:
> On Fri, May 16, 2003 at 05:53:17PM +0200, Oliver Neukum wrote:
> > > Hotpluggability is not required, it is the same for any module, which
> > > gets loaded while the system is running. Drivers don't even need to be
> > > aware of hotplug.
> >
> > In that case they can contain the firmware and mark it __init.
> > They need no RAM. They can even mark the code needed to put
> > firmware into the device as __init.
> I think you missed a lot of the previous discussion. Many high
> level kernel developpers (Jeff, Alan, Greg) have said 'niet' to binary
> firmware linked with the kernel (unless there is source code
> available). Please assume that all drivers currently including
> firmware blobs in the kernel will need fixing and therefore should not
> be taken as example.
> The threads :
> Yes, that's a lot to read, but this will explain the full
> complexity of the situation.

It seems to be a whole lot of laywering not technical discussion IMHO.

> > An awful lot of overhead.
> It's not like we have a choice on this issue. The embedded
> people are already grumbling.

Please explain. Either firmware is in RAM or it is not.


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

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