| 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
| ||
|
Date: Mon, 02 May 2011 20:38:15 +0100 From: David Woodhouse <dwmw2@...radead.org> To: Mike Waychison <mikew@...gle.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: linux-firmware tree On Mon, 2011-05-02 at 19:57 +0100, Mike Waychison wrote: > Hi David, > > I'm trying to understand the purpose of the linux-firmware tree. > Forgive me if this is a stupid question, but the only information > about it I could find was your original post back in 2008: > https://lwn.net/Articles/294308/ > > Will the Linux kernel sources always continue to have the firmware > blobs and the linux-firmware tree is only for those users of distros > that strip the firmware out? No, the legacy firmware images from the kernel tree are going to be removed. They were only kept for backward compatibility. The linux-firmware tree has a lot of things that were never included in the kernel source; no *new* firmware images are being (or at least should be) added to the kernel source itself. Everyone should be using the linux-firmware tree by now. -- dwmw2 -- 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/
Powered by blists - more mailing lists