On Friday, 12. November 2004 09:14, Matthew Dillon wrote:
> But it doesn't sound like all that big a problem to me... in fact it
> would be fairly trivial to have the Makefile for the module check for
> the existance of the firmware file in various standard places and
> simply not build the module if the firmware file cannot be found,
> or build a dummy module that simply reports that the firmware was not
> available.
How about building two modules? One with the real code which requires the
firmware module. And a script which builds the firmware module (maybe even
without kernel source?): just a shared (kernel) objects that contains two
symbols: start and end of the firmware or firmware and size.
cheers
simon