Adam Jackson

I think this is a bug in Mesa's client side. xserver's stock GLX should generate BadValue for both the legacy path: https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/glx/glxcmds.c#L301 and the CreateContextAttribs path: https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/glx/createcontext.c#L324 Which, to be...

I've opened a merge request for this that fixes things for me: ``` haldol:~/git/mesa% LD_LIBRARY_PATH=/home/ajax/git/mesa/build/src/glx DISPLAY=:8 LIBGL_ALWAYS_INDIRECT=1 glxinfo name of display: :8 X Error of failed request: BadValue (integer parameter...

> Importing contexts across processes certainly won't work for direct-rendering contexts, but there are other aspects of the extension that could remain useful (Querying its Visual, mostly), so I'm inclined...

Hah, right you are, GLX 1.4 only names three context properties and the visual ID is not among them. Mesa's QueryContext has always supported it since the initial GLX 1.3...

Enh. I'm not super thrilled with pretending ES1 is still a thing, but Mesa builds the thunk functions unconditionally so I suppose it's free to advertise. But if we were...

> The NVIDIA extension is significantly larger, so it would may require some work. But if all the functions Piers listed previously are built unconditionally as you said then yeah...

> Just to be sure that I understood: you suggest to use this name "GL_NV_ES1_1_compatibility" absent from the OpenGL-Registry and to submit a merge request of this "GL_NV_ES1_1_compatibility" extension to...

@caramelli yeah, it's a bit different from what you were proposing, but since Mesa _does_ already have the code for the fixed-point support we may as well expose all of...

> [W]e require at least that: > > * FBConfig IDs are unique and persistent across a given X server instance, so logical programs that span multiple processes can look...

> In terms of spec updates I think this just means changing the word "XID" to "int" or "ID" in a few places. I'll write the patch for that. Or,...