Re: [Mesa3d-dev] glPointSize in radeon driver

2006-06-26 Thread Matthias Hopf
On Jun 23, 06 19:59:58 +0100, Keith Whitwell wrote: The egg on our face is that, AFAIK, Mesa based drivers are the *only* drivers that don't support this functionality. That app developers expect it to be there isn't surprising. I guess I was the one who introduced the behaviour in the

Re: [Mesa3d-dev] glPointSize in radeon driver

2006-06-26 Thread Brian Paul
Matthias Hopf wrote: On Jun 23, 06 19:59:58 +0100, Keith Whitwell wrote: The egg on our face is that, AFAIK, Mesa based drivers are the *only* drivers that don't support this functionality. That app developers expect it to be there isn't surprising. I guess I was the one who introduced the

Re: [Mesa3d-dev] [PATCH] Possible bug in r128 DRI driver [r128_cce_depth called without lock held]

2006-06-26 Thread Brian Paul
Martijn van Oosterhout wrote: I've been trying to track down a bug in the r128 driver causing lots of the following messages in the kernel logs: r128_cce_depth called without lock held The problem appears (to me anyway) to be in Mesa-6.4.2/src/mesa/drivers/dri/r128/r128_span.c. There are

Re: [Mesa3d-dev] The mysteriously changing pClipRects

2006-06-26 Thread Martijn van Oosterhout
On 6/26/06, Keith Whitwell [EMAIL PROTECTED] wrote: The semantics are that it is valid between LOCK_HARDWARE() and UNLOCK_HARDWARE(). On a lower level, you've investigated the way it is updated on contended locks already. I see. In any case I've found one problem, and that is with the code in

[Mesa3d-dev] [Bug 7340] New: Conversion error in t_vertex.c when compiling MesaLib-6.5 on Darwin

2006-06-26 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=7340 Summary: Conversion error in t_vertex.c when compiling MesaLib-