On Tue, Jul 15, 2008 at 04:26:41PM -0400, Jeff Garzik wrote:
quoted text
> To be extremely concrete, firmware-in-module is
> 
> 	* add Kconfig option (kernel-wide or per-driver, dunno) asking
> 	  "build firmware into drivers, as before?"
> 
> 	* tweak build process to build firmware into foo.ko output,
> 	  probably in a specially marked ELF section
> 
> 	* get request_firmware() to automatically notice that the
> 	  MODULE_FIRMWARE() was built into this driver, and to
> 	  look at the special ELF section for its data

Jeff, just thinking, wouldn't it be slightly easier to move the firmware
in a separate module on its own and just add a dependency, so that foo.ko
automatically loads foo-fw.ko ? I know it will be slightly differente, but
would not change in-site deployment workflows nor installed scripts.

Regards,
Willy

--
unsubscribe notice
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/