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
Hi everyone,
Here's a patch against the mesa_3_2_dev branch that updates the .cvsignore
files to ignore the generated files. It also adds some new ones. I got
tired of seeing all those '?' lines when I did an update. ;)
One caveat: One of the more common things left out was the "Makefile". I
On Wed, 24 Nov 1999, Brian Paul wrote:
The mesa_3_2_dev branch still thinks it's 3.1, and our configure script
reports it as such.
It's correct as-is. The mesa_3_2_dev branch will end with the release
of Mesa 3.2 but the Mesa 3.1 release is also pending on this branch.
3.2 will be the
Hello all,
Over on the glx list, we've been seeing reports from users confused about
mesa versions. We're currently tracking 3.2 cvs, and no doubt all this
will go away when 3.2 is actually released. However, aside from those who
don't read our documentation, two things seem to be confusing
On Mon, 25 Oct 1999, Stephen J Baker wrote:
I'm curious about the status of the Mesa-is-not-OpenGL issue. I've gotten
the impression that things are a little more relaxed with the library name
change, etc.
How about just "the package provides libGL"...it's only words
after all.
Hmm. It
Hi,
I'm curious about the status of the Mesa-is-not-OpenGL issue. I've gotten
the impression that things are a little more relaxed with the library name
change, etc.
Specifically, this came up in the context of adding the mga GLX module to
Debian. Currently there are two conflicting Mesa
