[Mesa-dev] [PATCH] GLX: Add an env var to enable the support of GLX extensions needing both client and server support, in case of client support and direct rendering.

Axel Davy axel.davy at ens.fr
Thu Jun 19 07:19:58 PDT 2014

On 19/06/2014 01:55, Kenneth Graunke wrote :
> That would make the common case that most people want (GLX_ARB_create_context
> for direct rendered 3.2+ core profile stuff) work out of the box, without the
> need for environment variables.  It's technically out of spec, but for X on
> Wayland, I think it's not unreasonable.
> On the other hand, supporting AIGLX of sorts might be possible...
> With XWayland, there are really a couple layers to "indirect" rendering...
> 1. Doing it X client side (direct rendering)
> 2. Doing it in the XWayland X11 server/Wayland client (semi-indirect).
> 3. Doing it wherever Weston/etc are running (total indirect).
> It seems like XWayland could support AIGLX with model #2 - X clients would
> speak GLX protocol to XWayland, which could then do the GL.  Model #3 seems
> like something we should avoid at all costs.
> Of course, I don't know that there's any *benefit* to supporting AIGLX in
> XWayland, so...my real suggestion is to just raise a GLX error or lie if asked
> to create an indirect context.
> --Ken
It is possible to support indirect rendering for XWayland, for that the 
Xserver should be updated to be able to use DRIImage and DRI3 specific 
things for indirect rendering (instead of DRI2).

This patch is just a workaround because it's not done yet.

Axel Davy

More information about the mesa-dev mailing list