[...]
> ok, i've to deal with development version of hardware, which means there a
> some firmware releases expected during driver development. this means i have
> to recompile the driver every time i've to download a new firmware.
> AND it will bloat the module itself. so otherwise i'd just pass it from the
> file directly to the hardware.
Why? You could split the module in two: The driver itself (loaded on
demand) and the firmware (loaded once from the init function of the driver)
dumps its payload and vanishes. Or put the firmware stuff into init_data
for the driver, it should go away once the module is initialized.
> ok, if everyone agrees including the firmware into the module at compile time
> would be the ultimative solution, i will quit my questions of how to do it
> my way - i will use the classical way.
Has the advantage that it's not possible to load the wrong file, or get
stuck because the firmware isn't there.
Good luck!
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu