Date: Thu, 30 Mar 2000 12:46:03 -0800 (PST)
From: Ralph Giles [EMAIL PROTECTED]
X-Sender: giles@localhost
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
MIME-Version: 1.0
Subject: [utah-glx-dev] 3Dnow asm broken on the K6-III?
X-Mailman-Version: 1.1
List-Id: utah-glx-dev.lists.sourceforge.net
X-BeenThere: [EMAIL PROTECTED]
Hello all,
We've received several reports lately on the Utah-GLX list about the 3Dnow
asm code not working for people with K6-IIIs. It shows up under software
fallback, so our guess is that it's a problem in the Mesa code. (that, and
I don't think we have any 3Dnow in our drivers--just mmx for texture
conversion)
In particular see:
http://lists.sourceforge.net/pipermail/utah-glx-dev/2000-March/001914.html
And the associated screen shot for the fun effects on the projection
matrix. :)
I didn't see a report of this in the list archives, so I wanted to bring
it to your attention. I don't know if this is a bug in the new processors,
or if they've changed the instruction set somewhat. Can any experts
comment?
I'm having no trouble, and I've just verified that the 3DNow! functions are
being used (at least in software Mesa). I also have a K6-III, but just
purchased pretty recently (February). The errata show no corrections though.
I think it's possible that people that are having problems are using an old
version of Mesa. It's easy to forget to update that as well if you're working
on glx, but I assume there are bugfixes in the Mesa 3.2 tree as well from time
to time.
Anyway, it can't hurt to update Mesa as well from time to time. I'd suggest
that those who are having problems do this and see if anything changes.
Justin A. Kolodziej
This .signature intentionally left blank
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
