Hi everybody,

Recently, I have been working with NICs and had to compile the drivers
to work with and I found that make produces two files: <bindriver>.ko
and <bindriver>.o. The installation procedure mentioned that, in order
to use the card, (or whatever) it was necessary to do

insmod <bindriver>.ko

So, the <bindriver>.o was left over.

What is the .o file for? why i cannot insmod the .o, only the .ko file?

Regards

Marco

--------------------
Freedom is not a permission for chaos

["Followup-To:" header set to comp.os.linux.setup.]
On 30 Aug 2006 08:45:07 -0700, Marco A. Cruz Quevedo
<macruzq@myway.com> wrote:
> Hi everybody,
>
> Recently, I have been working with NICs and had to compile the drivers
> to work with and I found that make produces two files: <bindriver>.ko
> and <bindriver>.o. The installation procedure mentioned that, in order
> to use the card, (or whatever) it was necessary to do
>
> insmod <bindriver>.ko
>
> So, the <bindriver>.o was left over.
>
> What is the .o file for? why i cannot insmod the .o, only the .ko file?
>
..o files are used to build the kernel and modules. Modules for the 2.6
kernel are .ko files.

--
Andrea's Admonition:
Never bestow profanity upon a driver who has wronged you.
If you think his window is closed and he can't hear you,
it isn't and he can.