On 7 Jun, Holger Waechtler wrote:
> Hi Ralph,
Thanks for the response! I'm having another go now that the new asm
stuff has moved into the main branch.
> The asm_???.c /.h /.S files are not used at this time. Take a look into
> the files in src/X86 instead (prefer the experimental-1 CVS branch
Brian Paul wrote:
>
> Thomas Tanner wrote:
>
> > I don't see why you're objecting to this idea.
> > I just want to implement support for dynamically loadable
> > drivers which requires replacing the old "kludges"
> > with another - in your opinion - "kludge".
>
> I see the point you're tryin
> I'm interesting getting Mesa compliant with GLU 1.3. Anyone else
> interested please e-mail me so we can begin cooridnating this project.
I've rewritten the polygon tessellator to be compliant with the GLU 1.3
spec, including all winding rule support. I'm pretty much done, just need
to test i
I've checked in an updated CONFORM file which has the results
of running the OpenGL conformance tests on the current Mesa
code (not the experimental branch).
The summary is:
Conform failed.
Transformation Normal test (Test number #7) failed.
Line Stipple test (Test number #35) failed.
On Wed, 9 Jun 1999, Thomas Tanner wrote:
>
> On 09-Jun-99 Holger Waechtler wrote:
> > I just committed some 3dnow and x86-asm related changes, which have been
> > before only in the experimental-1 branch.
>
> I can't compile mmx_blend.S:
>
fixed. GAS2assyntax does not knows all possiblititi
On Thu, 10 Jun 1999, Thomas Tanner wrote:
>
> On 09-Jun-99 Holger Waechtler wrote:
> > you should not try to compile the ggi stuff, if no ggi was found.
>
> That's what the autoconf script actually does.
> Unfortunately some of Jon's GGI fixes broke it yesterday :(
> but it's fixed now.
>
Philip Streck wrote:
>
> I'm interesting getting Mesa compliant with GLU 1.3. Anyone else
> interested please e-mail me so we can begin cooridnating this project.
Gareth Hughes ([EMAIL PROTECTED]) has been working on a GLU 1.2
polygon tessellator and I just recently had someone express
interest
Thomas Tanner wrote:
> I don't see why you're objecting to this idea.
> I just want to implement support for dynamically loadable
> drivers which requires replacing the old "kludges"
> with another - in your opinion - "kludge".
I see the point you're trying to make. I guess the problems, a
On 10-Jun-99 Stephen J Baker wrote:
>> > 2. There is the public interface which connects OpenGL/Mesa to the
>> >OS / window system. This interface, by definition, is unique to
>> >each system. These are the GLX, WGL, OS/Mesa, SVGA, Glide, etc
>> >interfaces.
>> Yes. That's what I w
On 10-Jun-99 Brian Paul wrote:
>> Okay, but that should be documented, IMHO.
> An competant programmer should know better than to pass invalid data
> to a function. The OpenGL documentation clearly defines the expected
> inputs to all functions.
Yes, but someone who tests Mesa might think it'
I'm interesting getting Mesa compliant with GLU 1.3. Anyone else
interested please e-mail me so we can begin cooridnating this project.
thanks,
Philip Streck
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-d
Thomas Tanner wrote:
>
> On 09-Jun-99 Brian Paul wrote:
> >> demos/drawpix exposes a bug in Mesa (experimental-1 branch, X11):
> >> press 'W' or 'P' for some seconds and look at the first line
> >> press 'H' -> random garbage on the top
> >> press 'R' until you can't see the picture any more
On Thu, 10 Jun 1999, Thomas Tanner wrote:
> > 2. There is the public interface which connects OpenGL/Mesa to the
> >OS / window system. This interface, by definition, is unique to
> >each system. These are the GLX, WGL, OS/Mesa, SVGA, Glide, etc
> >interfaces.
>
> Yes. That's what
On 09-Jun-99 Brian Paul wrote:
>> demos/drawpix exposes a bug in Mesa (experimental-1 branch, X11):
>> press 'W' or 'P' for some seconds and look at the first line
>> press 'H' -> random garbage on the top
>> press 'R' until you can't see the picture any more -> segfault
> I wouldn't say this
On 09-Jun-99 Holger Waechtler wrote:
> you should not try to compile the ggi stuff, if no ggi was found.
That's what the autoconf script actually does.
Unfortunately some of Jon's GGI fixes broke it yesterday :(
but it's fixed now.
> A switch --disable-ggi would be nice, even if a ggi librar
Keith Whitwell wrote:
>
> Can't we do anything about this???
I'm as frustrated as anyone at this point. I've send a message
to [EMAIL PROTECTED] I think it'll reach several sysadmins.
I'm also asking for CVS admin priviledge.
-Brian
--
Can't we do anything about this???
Keith
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Thomas Tanner wrote:
> First off, we'd need a unified driver API for Mesa.
> Why has each driver its own API? This is bad.
> There should be single interface for applications
> so that they don't need to know the underlying driver.
I think you're off track here. What exactly do you mean by
18 matches
Mail list logo
