Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-09 Thread Jon Leech
On Sat, Feb 07, 2004 at 12:44:39AM -0800, Ian Romanick wrote: I like it. :) It looks a little weird to me like that, but I think doing 1.2 (1.4.20040108 Foobar, Inc. Fancypants GL) should work just as well. I would want to be very sure that there are no apps parsing that string before

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-08 Thread Andreas Stenglein
Am 2004.02.07 09:44:39 +0100 schrieb(en) Ian Romanick: [...] as well. I'll try to have a patch tomorrow. The server-side of things Looks like its fixed in DRI CVS with/since your patch. I have to admit that I only tried with the new libGL.so and old Xserver/libs, not with old libGL and new

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-07 Thread Ian Romanick
Andreas Stenglein wrote: Am 2004.02.04 21:00:14 +0100 schrieb(en) Brian Paul: Ian Romanick wrote: Making that change and changing the server-side to not advertise a core version that it can't take protocol for would fix the bug for 4.4.0. Do you think anything should be done to preserve text

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-05 Thread Brian Paul
Andreas Stenglein wrote: Am 2004.02.04 21:00:14 +0100 schrieb(en) Brian Paul: Ian Romanick wrote: [snip] Making that change and changing the server-side to not advertise a core version that it can't take protocol for would fix the bug for 4.4.0. Do you think anything should be done to

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-04 Thread Allen Akin
On Wed, Feb 04, 2004 at 10:12:19AM -0800, Ian Romanick wrote: | | Okay, that's just weird. Normally the Nvidia extension string is about | 3 pages long. Just for reference, here's the direct-rendering version (table of Visuals omitted): name of display: :0.0 display: :0 screen: 0 direct

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-04 Thread Brian Paul
Ian Romanick wrote: Andreas Stenglein wrote: after setting LIBGL_ALWAYS_INDIRECT=1 glxinfo shows OpenGL version string: 1.5 Mesa 6.0 but doesnt show all extensions necessary for OpenGL 1.5 An application only checking for GL_VERSION 1.5 would probably fail. Any idea what would happen with

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-04 Thread Ian Romanick
Brian Paul wrote: Ian Romanick wrote: That's *bad*. It is currently *impossible* to have GL 1.5 with indirect rendering because some of the GLX protocol (for ARB_occlusion_query ARB_vertex_buffer_objects) was never completely defined. Looking back at it, we can't even advertise 1.3 or 1.4

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-04 Thread Brian Paul
Ian Romanick wrote: Brian Paul wrote: Ian Romanick wrote: That's *bad*. It is currently *impossible* to have GL 1.5 with indirect rendering because some of the GLX protocol (for ARB_occlusion_query ARB_vertex_buffer_objects) was never completely defined. Looking back at it, we can't even

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-04 Thread Andreas Stenglein
Am 2004.02.04 21:00:14 +0100 schrieb(en) Brian Paul: Ian Romanick wrote: [snip] Making that change and changing the server-side to not advertise a core version that it can't take protocol for would fix the bug for 4.4.0. Do you think anything should be done to preserve text after the

[Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-03 Thread Andreas Stenglein
after setting LIBGL_ALWAYS_INDIRECT=1 glxinfo shows OpenGL version string: 1.5 Mesa 6.0 but doesnt show all extensions necessary for OpenGL 1.5 An application only checking for GL_VERSION 1.5 would probably fail. Any idea what would happen with libGL.so / libGLcore.a from different versions of

Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?

2004-02-03 Thread Ian Romanick
Andreas Stenglein wrote: after setting LIBGL_ALWAYS_INDIRECT=1 glxinfo shows OpenGL version string: 1.5 Mesa 6.0 but doesnt show all extensions necessary for OpenGL 1.5 An application only checking for GL_VERSION 1.5 would probably fail. Any idea what would happen with libGL.so / libGLcore.a