compiling two modules from separate directories out of kernel tree

2005-02-18 Thread Olivier Smeesters
Dear all,
I'm currently developping two kernel modules that I'm compiling outside 
of the kernel tree. One is a device driver and one is a pseudo-network 
device driver (encapsulating network packets).
The output of the encapsulator is supposed to go to the device driver. 
For this reason, the device driver exports a "send_packet" function 
which the encapsulator calls.

When loading the encapsulator module, the kernel reports a 'no version 
for "send_packet" found' and goes in tainted mode.
It seems that this is caused by the fact that the two modules are 
compiled in different directories (there is no CRC for the send_packet 
function in the encapsulator module, only for the kernel functions it 
calls).

One solution is to put all the modules in one directory. When this is 
done, a CRC is present in the encapsulator module as expected by the 
module loader and there is no warning anymore.
But as the two drivers are not definitely related (the device driver can 
be used without the encapsulator), I would like to keep them in separate 
directories.
This situation ressembles to the situation of the PLIP and the parport 
driver.

Is there a way to avoid the warning (and tainted mode) while still 
compiling them outside of the kernel tree and in separate directories ?

Thanks in advance,
Olivier Smeesters
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


compiling two modules from separate directories out of kernel tree

2005-02-18 Thread Olivier Smeesters
Dear all,
I'm currently developping two kernel modules that I'm compiling outside 
of the kernel tree. One is a device driver and one is a pseudo-network 
device driver (encapsulating network packets).
The output of the encapsulator is supposed to go to the device driver. 
For this reason, the device driver exports a send_packet function 
which the encapsulator calls.

When loading the encapsulator module, the kernel reports a 'no version 
for send_packet found' and goes in tainted mode.
It seems that this is caused by the fact that the two modules are 
compiled in different directories (there is no CRC for the send_packet 
function in the encapsulator module, only for the kernel functions it 
calls).

One solution is to put all the modules in one directory. When this is 
done, a CRC is present in the encapsulator module as expected by the 
module loader and there is no warning anymore.
But as the two drivers are not definitely related (the device driver can 
be used without the encapsulator), I would like to keep them in separate 
directories.
This situation ressembles to the situation of the PLIP and the parport 
driver.

Is there a way to avoid the warning (and tainted mode) while still 
compiling them outside of the kernel tree and in separate directories ?

Thanks in advance,
Olivier Smeesters
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/