ok, i know ... but it would be IMHO the cleanest solution.
> Config data should be in a modules.conf-friendly
> format (command-line options) and firmware should be linked directly into
> the module.
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.
> It's fairly simple to write a tool that translates an
> arbitrary binary file into an equivalent C array declaration...
yup, i know them - Alan mentioned it.
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.
greetings
++dent
PS: never use netscrap mail ... i completely shot my loc;al maildir, so i got this
reply out from the news. :(
... now using good old pine for the next few years.
-- Thomas Mirlacher Student of ComputerScience, University of Salzburg dent@cosy.sbg.ac.at http://www.cosy.sbg.ac.at/~dent
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu