Robert Manchester writes:
> * Jeremy Brown (mee@xxxxxxxxxxxxxxxxxx) [010412 17:12]:
> > Of course, this whole problem goes away if your driver is open-source. :)
>
> Not really. The reason I would like to have a binary module is so my
> users don't have to know how to compile it. So many people have
> problems getting the right header files, compiler, etc, that it is
> easier for them if everything just works. Distributing the module as a
> binary doesn't mean that I don't want to distribute the source code with
> it, I just want to minimize the user from screwing up and ultimately
> being turned off from running my code because it is too hard to install.
>
> another reason would be I want to run two 2.4.3 kernels one with devfs
> and one without devfs using the same modules for both kernels.
It's not just devfs where you'll have this problem. It's a range of
other CONFIG_ options. The obvious one is CONFIG_SMP. That's just
doubled the number of binaries you need to ship. Every config option
that changes the driver ABI will multiply the number of binaries you
need to ship.
You're better off giving up on trying to ship binaries for all/most
configurations, and instead ship source code. Or at least a source
wrapper to a binary library (if your management is still under the
illusion that you have IP worth hiding:-).
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|