Re: nexuiz crashes with Free driver

On Wed, 2007-03-07 at 19:34 +, Freyr Gunnar Ólafsson wrote: Hello. I'm interested in getting Nexuiz to run well with the dri driver. I know it's not nexuiz since I tried it also with the binary-blob driver. Should I make a bug in the freedesktop.org bugzilla? Already done:

[Bug 10215] Radeon driver claims to support VBOs, but segfaults on glGenBuffers

http://bugs.freedesktop.org/show_bug.cgi?id=10215 --- Comment #3 from [EMAIL PROTECTED] 2007-03-08 03:32 PST --- (In reply to comment #2) It appears that the proper call is made only when a driver claims to support gl version 1.5 or greater, and radeon claims to support 1.3.

[Bug 10215] Radeon driver claims to support VBOs, but segfaults on glGenBuffers

http://bugs.freedesktop.org/show_bug.cgi?id=10215 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

On Thursday 08 March 2007 12:12, Michel Dänzer wrote: Does calling radeonSetCliprects unconditionally before _mesa_make_current help? I don't see a way for radeonMakeCurrent to be sure DoBindContext didn't update the cliprects. Yep it helps. Calling radeonSetCliprects when stamp!=lastStamp

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

Calling radeonSetCliprects when stamp!=lastStamp also helps! Sorry meant radeon-lastStamp != driDrawPriv-lastStamp and radeon-lastStamp != driReadPriv-lastStamp. - Take Surveys. Earn Cash. Influence the Future of IT Join

[Bug 10215] Radeon driver claims to support VBOs, but segfaults on glGenBuffers

http://bugs.freedesktop.org/show_bug.cgi?id=10215 --- Comment #5 from [EMAIL PROTECTED] 2007-03-08 05:30 PST --- (In reply to comment #4) (In reply to comment #3) Mesa 6.5.1 implementation error: User called no-op dispatch function (an unsupported extension function?) Not

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

On Thu, 2007-03-08 at 14:25 +0200, Panagiotis Papadakos wrote: Calling radeonSetCliprects when stamp!=lastStamp also helps! Sorry meant radeon-lastStamp != driDrawPriv-lastStamp That'll usually be fine, but in theory the stamps could be identical when a different drawable was bound

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

On Thu, 2007-03-08 at 14:31 +0100, Michel Dänzer wrote: On Thu, 2007-03-08 at 14:25 +0200, Panagiotis Papadakos wrote: Calling radeonSetCliprects when stamp!=lastStamp also helps! Sorry meant radeon-lastStamp != driDrawPriv-lastStamp That'll usually be fine, but in theory the stamps

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

I still get invalid reads with your latest patch. On Thursday 08 March 2007 15:42, Michel Dänzer wrote: On Thu, 2007-03-08 at 14:31 +0100, Michel Dänzer wrote: On Thu, 2007-03-08 at 14:25 +0200, Panagiotis Papadakos wrote: Calling radeonSetCliprects when stamp!=lastStamp also helps!

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

On Thu, 2007-03-08 at 17:03 +0200, Panagiotis Papadakos wrote: I still get invalid reads with your latest patch. Any idea what's going on? The only situation where radeonSetCliprects doesn't get called from radeonMakeCurrent is if neither the drawable nor its stamp has changed... -- Earthling

[Bug 10178] Strange pattern in OpenGL

http://bugs.freedesktop.org/show_bug.cgi?id=10178 --- Comment #5 from [EMAIL PROTECTED] 2007-03-08 08:48 PST --- Well, it seems that it's going to take awhile for you people to make everybody happy (thanks, ATI, for not releasing proper drivers/specs), so for now i'll stick with

Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

On Thursday 08 March 2007 17:05, Michel Dänzer wrote: Any idea what's going on? The only situation where radeonSetCliprects doesn't get called from radeonMakeCurrent is if neither the drawable nor its stamp has changed... We have to call radeonSetCliprects(radeon), before

[Bug 10215] Radeon driver claims to support VBOs, but segfaults on glGenBuffers

http://bugs.freedesktop.org/show_bug.cgi?id=10215 --- Comment #7 from [EMAIL PROTECTED] 2007-03-08 09:28 PST --- Created an attachment (id=9041) -- (http://bugs.freedesktop.org/attachment.cgi?id=9041action=view) patch to enable ARB_vbo (In reply to comment #6) Looking at glxinfo.

[Bug 10192] r200: Regression from 6.5.1 games rendering single texture or pixel at bottom left only

http://bugs.freedesktop.org/show_bug.cgi?id=10192 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 9876] SecondLife does not show login screen

http://bugs.freedesktop.org/show_bug.cgi?id=9876 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment

[Bug 10215] Radeon driver claims to support VBOs, but segfaults on glGenBuffers

http://bugs.freedesktop.org/show_bug.cgi?id=10215 --- Comment #8 from [EMAIL PROTECTED] 2007-03-08 12:11 PST --- Thank you very much. The patch worked against the debian sources, so I should be able to get my homework done (even if it does turn out to be slow). -- Configure