09:57dmitryK: Hi, all! Could you please help me with clarifying one thing, when the user uses proprietary drivers, like NVidia, do they provide their own EGL/GLX libraries/implementations, or they are somehow forwarded via Mesa/DRI3?
10:01pq: dmitryK, the is a dispatcher layer called glvnd, it's its own project. The implementations of EGL, GLX, GL are then either Mesa or proprietary.
10:02pq: Before glvnd was a thing, people indeed needed to replace all those application-facing libraries.
10:03dmitryK: pq: is it like levelzero API in Intel proucts?
10:03pq: I've no idea what that is.
10:03dmitryK: I remember they have some form or "loaders"
10:04pq: see https://gitlab.freedesktop.org/glvnd/libglvnd
10:04dmitryK:is reading...
10:09dmitryK: pq: do I understand it right that from the client side this glvnd comes in a form of libGLX.so, libGL.so and libEGL.so, which basically dispatch all the requests to the implementation registered by the driver and selected by the user based on EGLDisplay?
10:12dmitryK: it seems like "yes": https://www.x.org/wiki/Events/XDC2017/brenneman_GLVND.pdf
10:19dolphin: dmitryK: the dispatcher/loader library to forward to different implementations is rather generic mechanism
10:20dmitryK: is the same thing happens when requesting ELG from Wayland versus GLX? Or it is a different beast?
10:22MrCooper: that's different front-end libraries (libEGL vs. libGLX / libGL)
10:23dmitryK: MrCooper: okay, thank you!
10:24dmitryK: MrCooper: btw, that swap-interval resetting issue for implicit GLX surfaces cannot be considered as a bug in Mesa, can it?
10:24MrCooper: it is
10:25dmitryK: MrCooper: hm... should I report that then? Isn't "implicit surface" thing a "gray zone"?
10:27MrCooper: hmm, maybe it is indeed
10:28MrCooper: I wouldn't hold my breath for it getting fixed anyway
10:43dmitryK: Hm.. the specification is rather vague on that:
10:43dmitryK: "For backwards compatibility with GLX versions 1.2 and earlier, a rendering context can also be used to render into a Window. Thus, a GLXDrawable is the union {GLXWindow, GLXPixmap, GLXPbuffer, Window}"
10:45dmitryK: so, theoretically, it could be read that Mesa is required to render to Window only for 1.2 apps, but swap-buffers is an extension for 1.3 :)
10:47dmitryK: MrCooper: is it possible to correlate the version of Mesa with the usage of DRI3 (that presumably broke the thing?)?
11:07MrCooper: don't think so; one indicator is GLX_EXT_buffer_age, which couldn't be supported before DRI3
12:07dmitryK: MrCooper: and this problem shouldn't appear on systems before DRI3, right?
13:01MrCooper: right
15:04dmitryK: MrCooper: thanks a lot for your help! :)
15:05MrCooper: no worries
18:42robclark: karolherbst: what's the deal w/ cts test_spir? AFAIU this extension is deprecated? But it reports as failing..
18:42robclark: https://www.irccloud.com/pastebin/g2HFR6NW/