| 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: <200806051207.50556.arekm@pld-linux.org> Date: Thu, 5 Jun 2008 12:07:50 +0200 From: Arkadiusz Miskiewicz <arekm@...-linux.org> To: David Woodhouse <dwmw2@...radead.org> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware() On Thursday 05 June 2008, David Woodhouse wrote: > Ignoring the set of 'make fw->data const' patches which have mostly > been already posted and are fairly trivial, this is the current content > of the firmware tree at git.infradead.org/users/dwmw2/firmware-2.6.git > > It starts by giving a way to build arbitrary firmware blobs into the > kernel while letting request_firmware() find them there, and then sets > about converting drivers to use request_firmware() instead of static > data blobs, now that we can do that without forcing the users to > actually satisfy the firmware requests from userspace. Will there be a way for userspace to know what firmware file is needed by which driver? So for example geninitrd/mkinitrd will be able to put only required firmware files into initrd/initramfs (without a need to maintain separate database with driver <-> firmware file name mapping). -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ -- 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