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]

Message-ID: <483F1C17.8040207@linux.intel.com>
Date:	Thu, 29 May 2008 14:11:51 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	David Miller <davem@...emloft.net>
CC:	greg@...ah.com, dwmw2@...radead.org,
	James.Bottomley@...senPartnership.com,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the
 kernel.

David Miller wrote:
> Arjan, by definition the firmware has to be tied to the kernel somehow.
> THe datastructure and other aspects are often tied directly to
> the firmware version loaded.

agreed that there are cases like this, and I have no personal objection to having
those in the kernel.

> If debian or whoever else have these concernes and want to rip the
> firmware out, it is one hundred percent their problem to patch things
> out of the kernel tree they use.

I don't care at all about the argument from that camp.


My aim was more the opposite: be able to get MORE firmware easily used/loaded,
not less. Right now it's a royal pain for users to get all the right pieces of
firmware.... having ONE place to put all that would go a long way of making that
side of things easier.

If you want to argue that that should be in the kernel tarbal itself, you won't
hear me complain. But others will... and for that a 2nd tarbal might well be the answer.
Just we shouldn't need 100 tarbals.
--
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/