.2, also allowed "Divinity" to start up
successfully on i965, though rendering bugs remain.
Based on Karol's report, I expect this test should pass on Catalyst, but
I only have Intel hardware to test on.
Signed-off-by: Jamey Sharp
Cc: Ian Romanick
Cc: Kenneth Graunke
---
v3: S
.2, also allowed "Divinity" to start up
successfully on i965, though rendering bugs remain.
Based on Karol's report, I expect this test should pass on Catalyst, but
I only have Intel hardware to test on.
Signed-off-by: Jamey Sharp
Cc: Ian Romanick
---
"But Ian, I lea
i965, though rendering bugs
remain.
Signed-off-by: Jamey Sharp
Cc: Karol Herbst
---
src/mesa/main/shaderapi.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/mesa/main/shaderapi.c b/src/mesa/main/shaderapi.c
index b28b5ce..fc2e885 100644
--- a/src/mesa/main/shaderapi.c
+++ b/src/mes
.2, also allowed "Divinity" to start up
successfully on i965, though rendering bugs remain.
Based on Karol's report, I expect this test should pass on Catalyst, but
I only have Intel hardware to test on.
Signed-off-by: Jamey Sharp
Cc: Karol Herbst
---
tests/all.py
the refresh rate calculation.
>
> We fallback to the current XVidMode method if XRandR is not available.
>
> Signed-off-by: Chris Wilson
> Cc: TheoH
> Cc: Jamey Sharp
> ---
> configure.ac| 7 +++
> src/glx/Makefile.am | 8 ++-
> src/glx/glxcmds.c | 16
On Fri, Apr 18, 2014 at 5:30 PM, Ian Romanick wrote:
> On 04/18/2014 05:07 PM, Jamey Sharp wrote:
>> if you're using Xlib, then by default it will be abort()ing your
>> client as soon as it pulls the error out of the event queue.
>
> Unless the client has an error handle
ersion,
>> but I'm not convinced it's necessary.
>>
>> I talked to Jamey Sharp, and he doesn't understand why most of Mesa
>> calls the unchecked versions of XCB functions. He thought most
>> developers would want to use the normal (checked) versions, sinc
On Wed, Jul 06, 2011 at 12:18:18PM -0700, Ian Romanick wrote:
> This is an area that I've been thinking about lately. I noticed that
> XCB uses a framework called check (http://check.sourceforge.net/), and
> I've been wanting to talk to Jamey and Josh about their experience with
> it, but I never