[2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy

• Next message: Adrian Bunk: "[2.5 patch] #include interrupt.h in epca.c and generic_serial.c"
• Previous message: Ivan Kokshaysky: "Re: [patch 2.5] 2-pass PCI probing, generic part"
• Next in thread: Alan Cox: "Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy"
• Reply: Alan Cox: "Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

While trying to use the e1000 as a module with kernel 2.4.20 it gives
me a unresolved symbol while trying to insmod the module. The offending
symbol is _mmx_memcpy. When the driver is compiled into the kernel
there's no problem.

I am running the kernel on a VIA Eden with 800MHz C3. Does this have
something to do with the fact that kernels for the VIA C3 are now
compiled with i486 optimisations (so maybe no MMX support?)?

Cheers,

Jurgen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Adrian Bunk: "[2.5 patch] #include interrupt.h in epca.c and generic_serial.c"
• Previous message: Ivan Kokshaysky: "Re: [patch 2.5] 2-pass PCI probing, generic part"
• Next in thread: Alan Cox: "Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy"
• Reply: Alan Cox: "Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:33 EST