linux-kernel - Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the kernel.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 May 2008 11:27:50 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Jeff Garzik <jeff@...zik.org>,
	David Woodhouse <dwmw2@...radead.org>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org,
	James.Bottomley@...senpartnership.com,
	David Miller <davem@...emloft.net>
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the
	kernel.

On Thu, 2008-05-29 at 23:17 +0200, Peter Zijlstra wrote:
> > 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.


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