Messages in this thread | | | Subject | Re: [RFC] binary firmware and modules | From | Marcel Holtmann <> | Date | Tue, 18 Apr 2006 16:25:27 +0200 |
| |
Hi Jon,
> > The attached patch introduces MODULE_FIRMWARE as one way of 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. I've also > > given an example via the QLogic gla2xxx driver. > > Ok. If nobody shouts today I'm going to suggest this go into 2.6.17. I > think more ellaborate schemes will come up later, but we also need > something usable out there now.
I like to see this in 2.6.17, too. I also think that it would be a good idea if we can add a description to each firmware file. Like we do with the module parameters.
> As others have pointed out, cunning schemes to hack how > request_firmware et al work are all very well and good, but often we > just don't know what firmware we'll need until runtime. Unless or > until there's a good way to address that, I think modules will need to > advertise every firmware and distros will have to package all possible > firmwares, just in case.
And remember that request_firmware() is also used for overriding CIS tables for PCMCIA cards.
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/
| |