Re:Firefox 75 on Wayland now to have full WebGL, working VA-...
by kevin_thibedeau on Tuesday March 03, 2020 @02:34PM
(#22477945)
These are all driver issues. Xorg and commercial servers on Windows don't have these problems. Intel and AMD drivers don't either unless misconfigured. It is not X's responsibility to handle low level hardware implementation details.
[ Parent
| on HN ]
Re:Firefox 75 on Wayland now to have full WebGL, working VA-...
by jstimpfle on Tuesday March 03, 2020 @02:50PM
(#22478119)
There is nothing in Xlib (that I'm aware of) that has a notion of complete frames - i.e. no buffer swap, no "frame complete" signal. How would the server know when a frame is complete then?
Re:Firefox 75 on Wayland now to have full WebGL, working VA-...
by pengaru on Tuesday March 03, 2020 @03:15PM
(#22478325)
The XDBE [0] extension attempted to add this, but I don't think anything actually implements it. (see edit)
I tried using it over a decade ago on XOrg and it didn't seem to do anything useful...
[0] https://www.x.org/releases/X11R7.6/doc/libXext/dbelib.html
Edit:
It's definitely there in the Xorg xserver [1]. My memory is fuzzy as it was a long time ago but I distinctly remember wasting a day trying to use this extension and becoming frustrated with its ineffectiveness. Maybe it was just for lack of any vsync mechanism to schedule the swap?
[1] https://gitlab.freedesktop.org/xorg/xserver/-/tree/master/db...
Re:Firefox 75 on Wayland now to have full WebGL, working VA-...
by jandrese on Tuesday March 03, 2020 @03:11PM
(#22478293)
Isn't this the point of the XDB extension that everybody has?
Re:Firefox 75 on Wayland now to have full WebGL, working VA-...
by jstimpfle on Tuesday March 03, 2020 @03:35PM
(#22478473)
Never heard of that, I don't think it's commonly used.