[compiz] [Mesa3d-dev] The direct/indirect rendering stuff and compiz

Michel Dänzer michel at tungstengraphics.com
Tue Apr 17 03:26:48 PDT 2007

[ Apologies for the late followup, I've been away over the weekend ]

On Fri, 2007-04-13 at 17:04 -0400, David Reveman wrote:
> On Fri, 2007-04-13 at 19:50 +0200, Michel Dänzer wrote:
> > 
> > I wonder why I didn't get any feedback on my proposal: Make
> > glXQueryExtensionsString take the current context into account when
> > appropriate. Would it be feasible for compiz to make the context current
> > before calling glXQueryExtensionsString?
> That's actually what compiz is doing now as I thought that
> glXQueryExtensionsString took the current context into account. However,
> as this is wrong I'd prefer to remove it.

Why is it wrong? It seems odd that it shouldn't take the context into
account when the context matters for whether an extension is really
supported, I'm inclined to consider it a bug.

> How about putting something like the attached workaround in mesa? It's
> checking if the client is the window manager for any screen and avoids
> using direct rendering if that's the case. It would be more better to
> check if the client is the compositing manager but I couldn't think of a
> way to check that without creating a top-level window and that seemed a
> bit too nasty here.

I don't like either way. If there's really no clean GLX solution a
wrapper script such as the one used by Debian makes more sense to me.

Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer

More information about the compiz mailing list