Messages in this thread | | | Subject | Re: [PATCH] MODULE_FIRMWARE for binary firmware(s) | From | Marcel Holtmann <> | Date | Wed, 30 Aug 2006 15:49:57 +0200 |
| |
Hi Greg,
> > > 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@redhat.com> > > > > Signed-off-by: Marcel Holtmann <marcel@holtmann.org> > > Since your tree will depend on this change, you can add it there and > add: > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> > > from me to the patch.
do we consider this 2.6.18 or 2.6.19 material? For the Bluetooth subsystem I can easily write a patch that makes use of it.
Regards
Marcel
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |