Skip to contentSkip to conversation

Binary modules for 2.6

DISCUSSION Dumitru Stama 2 participants 2 messages Sep 3, 2003

lore
Share & tools
lore
#0 lore raw

Hello all
Everything i write in the next lines can be considered as a question also since this is what i come to find out studying the latest 2.6 kernel.
With the current layout of the kernel modules there will be no way of distributing binary kernel modules anymore. Considering the structures that combine to describe the way module works and the alignement of those depending on the processor type even if that processor is i386 compatible. Personally i think this is a good move for open source community but what are we gona do with the proprietary drivers that do not have the sources available ?
If i am mistaken by any chance please enlighten me.

Thanks
Dumitru Stama

#1 lore raw

On Wed, 2003-09-03 05:40:40 +0200, Dumitru Stama <[email protected]> wrote in message <[email protected]>:

Quoted 2 lines

With the current layout of the kernel modules there will be no way of distributing binary kernel modules anymore. Considering the structures

No? If it were like this, I'd say I'd really like that:)

Quoted 3 lines

that combine to describe the way module works and the alignement of those depending on the processor type even if that processor is i386 compatible. Personally i think this is a good move for open source

Well, Linux aims towards source compatibility. If you want to ship binary modules, you've got to do *lots* of compilation.

You've to compile for all and any large distributions, and additionally, some people will ask you to compile with their very personal kernel tree (thay might have added loads of patches) and their .config file.

Quoted 2 lines

community but what are we gona do with the proprietary drivers that do not have the sources available ?

If it's like that, vendors of binary modules may face a lot of recompilation then...

However, such things are usually done in another way. If you encounter such situations, you'll write a binrary-only core module plus some glue code which will compiled on the client's system. You hardcode your binary interface, the customer compiles Linux' source-comparible interface. That'll resolve the problem.

However, you see that it's a PITA to live with binary-only modules. It's easier to release sources:)

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));