2.4.21-pre6: mmx_memcpy not properly exposed to modules with Athlon

Jonathan Abbey (jonabbey@arlut.utexas.edu)
Sun, 30 Mar 2003 04:47:21 -0600

This is a MIME-formatted message. If you see this text it means that your
E-mail software does not support MIME-formatted messages.

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I've had a good deal of trouble this evening trying to compile
2.4.21-pre6 for the Athlon processor. It appears that when the
kernel's bzImage is built all is well, but building modules (for USB)
results in unresolved references to _mmx_memcpy in the modules.

=46rom looking at the System.map file and nm vmlinux, it appears that
the _mmx_memcpy symbol is present and presumably thereby linkable.
I'm not certain why that symbol is not being resolved when I try to
depmod or insmod the USB modules.

I was able to work around the problem by building the bzImage for
Athlon, then doing a make config to switch the processor type to
PIII/Coppermine before building the modules, so that memcpy is not
#define'd to refer to _mmx_memcpy, but this is not a terribly
satisfying workaround.
Jonathan Abbey jonabbey@arlut.utexas.edu
Applied Research Laboratories The University of Texas at Au=
Ganymede, a GPL'ed metadirectory for UNIX http://www.arlut.utexas.edu/g=

Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Version: GnuPG v1.2.1 (SunOS)