> I've written a driver for an intelligent multiport serial card.
> I've got the firmware for the card in a separate file.
> For "inside" the kernel, I should declare the firmware initdata and
> it will get freed after booting.
> For the module, I could link everything together (that's what I'm
> doing right now), but this means I'm wasting a few tens of
> kilobytes of unswappable kernel memory just for the firmware.
> What I'd like to do is to have the "firmware" as a separate module
> that can be unloaded after initializing the main driver.
Why not have the 'firmware' as a separate file on disk that gets read
in by your module when it loads, then you avoid that sort of problem
completely...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/