On Wed, 22 Sep 2010 14:35:50 +0100, Owain Ainsworth <[email protected]> 
wrote:
> On Wed, Sep 22, 2010 at 01:47:27PM +0200, Julien Cristau wrote:
> > Without this change, DRI2 gets enabled but doesn't work and glxinfo
> > crashes my X server.
> 
> I think we need a bigger hammer than this.
> 
> The problem is that when we disable acceleration (EIO returned from
> execbuffer), the same thing happens. I think a fix for this should also
> deal with that case. Probably something conditional on the
> force_fallback member at dri2 time... (we can disallow dri2
> connections, right?)

This is what we get at the moment by returning buffers with name == 0 to
the client. Just we still appear to be exercising what were rarely tested
error paths...
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to