| 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
| ||
|
Message-ID: <1304373414.6400.23.camel@macbook.infradead.org> Date: Mon, 02 May 2011 22:56:54 +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 14:40 -0700, Mike Waychison wrote: > I don't see anything in the build (looking at scripts/Makefile.fwinst > in particular) that allows the build to enumerate out-of-tree firmware > files required by drivers. Do you have any thoughts on how this could > be enumerated? (if it isn't already?) Using the MODULE_FIRMWARE tags of the drivers which are built. This is actually the reason we haven't removed the legacy firmware from the source tree yet; it's waiting for me to implement that bit. It shouldn't be hard to post-process the modules and list the firmware blobs that they reference. We'd just want to make it do the same for built-in drivers too. -- 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