From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: linux-kernel@vger.kernel.org
Subject: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy
Date: 10 Jan 2003 14:45:00 +0100 [thread overview]
Message-ID: <1042206299.1694.12.camel@paragon.slim> (raw)
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
next reply other threads:[~2003-01-10 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 13:45 Jurgen Kramer [this message]
2003-01-10 15:14 ` [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy Alan Cox
2003-01-10 15:10 ` Jurgen Kramer
2003-01-10 16:15 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1042206299.1694.12.camel@paragon.slim \
--to=gtm.kramer@inter.nl.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.