Re: [Mesa-dev] headers for src/asm_mmx.c

1999-06-11 Thread Jon Taylor
Stephen J Baker wrote: > > On Thu, 10 Jun 1999, Jon Taylor wrote: > > > > 1. Linux (Unix) and Windows are, by far, the most popular platforms for > > > Mesa/OpenGL. The GLX and WGL interfaces are very well established. > > > Nobody will use a Mesa-specific interface instead of GLX/WGL since > >

Re: [Mesa-dev] headers for src/asm_mmx.c

1999-06-11 Thread akin
Jon Taylor wrote: |... If the new generic interface can be implemented using a | dynamic library based system, it would not necessarily have to be | Mesa-specific. It could be implemented directly or as a wrapper layer | around the GLX/WGL/etc interfaces, whether those interfaces are

Re: [Mesa-dev] conformance update

1999-06-11 Thread akin
Brian wrote: | | Allen Akin's "glean" is a new OpenGL testing framework. I haven't | had time to try it out yet. It would be nice if someone | volunteered to test Mesa with glean. You can get it via the | developer page on the Mesa web site. I'll be adding tests to glean, but fairly graduall

Re: [Mesa-dev] headers for src/asm_mmx.c

1999-06-11 Thread Stephen J Baker
On Thu, 10 Jun 1999, Jon Taylor wrote: > > 1. Linux (Unix) and Windows are, by far, the most popular platforms for > > Mesa/OpenGL. The GLX and WGL interfaces are very well established. > > Nobody will use a Mesa-specific interface instead of GLX/WGL since > > they'd be limiting themselves to Me

RE: [Mesa-dev] 3dnow code is now in assyntax, in the mainstream

1999-06-11 Thread Thomas Tanner
On 11-Jun-99 Holger Waechtler wrote: >> It doesn't detect my MMX capable Celeron. > Did you specified -DUSE_MMX_ASM ?? Yes, but the latest experimental branch seems to detect it. > btw: work the (mmx/3dnow) binutil checks in the configure script ?? Not yet, but I'm working on it. Thomas

Re: [Mesa-dev] headers for src/asm_mmx.c

1999-06-11 Thread Brian Paul
[EMAIL PROTECTED] wrote: > However, looking at Make-config, I don't see -DMMX or -DUSE_MMX_ASM > anywhere, nor in the lower-level Makefiles. Am I missing something? > We can work around all this by disabling mmx entirely (and I guess we > won't be missing anything :) but it would be nice to get t