On Thu, 2008-05-29 at 23:17 +0200, Peter Zijlstra wrote:
quoted text
> > If the firmware has a compatible license and is required for critical 
> > operations like booting the machine, built-in firmware should remain an 
> > option.  For certain embedded cases, I could certainly see that 
> > in-kernel firmware being the best method for firmware distribution, for 
> > both $Platform's users and $Platform's developers.
> 
> I certainly agree, pushing more and more into initrd just annoys the
> hell out of me.
> 
> I'd argue to include everything needed to build (and esp cross build) an
> initrd into the kernel - up until that point initrds are useless.

Us kernel hackers tend to like self-contained netbootable kernels
that have everything needed to boot a machine all the way to a shell
prompt :-)

David's proposal however do provides for storing the firmwares in
the kernel image, so I have no objection there.

Ben.


--
unsubscribe notice
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/