| 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: Tue, 29 Aug 2006 15:13:34 +0200 From: Marcel Holtmann <marcel@...tmann.org> To: James Bottomley <James.Bottomley@...elEye.com> Cc: Greg KH <greg@...ah.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] MODULE_FIRMWARE for binary firmware(s) Hi James, > From: Jon Masters <jcm@...hat.com> > > Right now, various kernel modules are being migrated over to use > request_firmware in order to pull in binary firmware blobs from userland > when the module is loaded. This makes sense. > > However, there is right now little mechanism in place to automatically > determine which binary firmware blobs must be included with a kernel in > order to satisfy the prerequisites of these drivers. This affects > vendors, but also regular users to a certain extent too. > > The attached patch introduces MODULE_FIRMWARE as a mechanism for > advertising that a particular firmware file is to be loaded - it will > then show up via modinfo and could be used e.g. when packaging a kernel. this patch was debated, but we never came to a final conclusion. I am all for it. It is simple and can improve the current situation. > Signed-off-by: Jon Masters <jcm@...hat.com> Signed-off-by: Marcel Holtmann <marcel@...tmann.org> Regards Marcel - 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