linux-kernel - Re: linux-firmware tree

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 for Android: free password hash cracker in your pocket

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

Message-ID: <33956.1304374925@localhost>
Date:	Mon, 02 May 2011 18:22:05 -0400
From:	Valdis.Kletnieks@...edu
To:	Mike Waychison <mikew@...gle.com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-firmware tree

On Mon, 02 May 2011 14:40:33 PDT, Mike Waychison said:

> 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?)

MODULE_FIRMWARE tags in the drivers, combined with (possibly)
the CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR
Kconfig variables if the needed bits aren't in /lib/firmware?

Content of type "application/pgp-signature" skipped