From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy
Date: 10 Jan 2003 16:10:59 +0100 [thread overview]
Message-ID: <1042211459.2706.9.camel@paragon.slim> (raw)
In-Reply-To: <1042211643.31612.2.camel@irongate.swansea.linux.org.uk>
Thanks, I was thinking along the same lines after
discovering that a lot of other modules had the same problem...:-)
After a mrproper everything is working OK now.
But just to get a complete picture, does it mean that
a) a kernel build for a VIA C3 doesn't use MMX, userspace programs can
still use it
or
b) Both kernel and userspace can't use MMX any more
If option b) would be true a lot of people who are using the VIA Eden
platform to view Divx and other multimedia material will be probably be
hurt performance wise. If the MMX implementation on the C3 is any good.
Greetings,
Jurgen
next prev parent reply other threads:[~2003-01-10 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 13:45 [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy Jurgen Kramer
2003-01-10 15:14 ` Alan Cox
2003-01-10 15:10 ` Jurgen Kramer [this message]
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=1042211459.2706.9.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.