Binary Kernel Interface
50 -----------------------
51 Assuming that we had a stable kernel source interface for the kernel, a
52 binary interface would naturally happen too, right? Wrong. Please
53 consider the following facts about the Linux kernel:
54 - Depending on the version of the C compiler you use, different kernel
55 data structures will contain different alignment of structures, and
56 possibly include different functions in different ways (putting
57 functions inline or not.) The individual function organization
58 isn't that important, but the different data structure padding is
59 very important.
60 - Depending on what kernel build options you select, a wide range of
61 different things can be assumed by the kernel:
62 - different structures can contain different fields
63 - Some functions may not be implemented at all, (i.e. some locks
64 compile away to nothing for non-SMP builds.)
65 - Memory within the kernel can be aligned in different ways,
66 depending on the build options.
67 - Linux runs on a wide range of different processor architectures.
68 There is no way that binary drivers from one architecture will run
69 on another architecture properly.

blood: I ovaj clanak ide u korist linuxa?

sto je to linux - linux je super svi crackeri ga koriste - linux je kupus tako kazu moji stariji prijatelji"

71 Now a number of these issues can be addressed by simply compiling your
72 module for the exact specific kernel configuration, using the same exact
73 C compiler that the kernel was built with. This is sufficient if you
74 want to provide a module for a specific release version of a specific
75 Linux distribution. But multiply that single build by the number of
76 different Linux distributions and the number of different supported
77 releases of the Linux distribution and you quickly have a nightmare of
78 different build options on different releases. Also realize that each
79 Linux distribution release contains a number of different kernels, all
80 tuned to different hardware types (different processor types and
81 different options), so for even a single release you will need to create
82 multiple versions of your module.