HDR, VRR, Mixed refresh rate/DPI displays, Zero-copy video acceleration, support for tiled GPUs
Yeh... we should totally keep to X11.... especially when toolkits start to drop support.
Yeh... we should totally keep to X11.... especially when toolkits start to drop support.
Yep. Sucks. It's the only thing I miss about gaming on Windows. Hopefully xlibre will be adding that in.
> ...VRR, Mixed refresh rate/DPI displays, Zero-copy video acceleration...
I know that the first two work fine on xorg [0]. It's not entirely clear what you're talking about with the third, but I know that xorg supports compositor bypass for windows so that programs can interact with the graphics card without the windowing system getting in the way. Like, I think this is a thing people were talking about working on back when Compiz and its wobbly windows was new and exciting.
If that isn't what you mean by your third thing, perhaps you'd be interested in specifying what video acceleration mechanism xorg doesn't have?
> ...support for tiled GPUs.
Doesn't that only matter for Apple Silicon(TM) machines, and maybe some ARM machines with integrated graphics? If folks want that, it's "just" a matter of writing the drivers to make it happen and getting them into an xorg fork. Can you show me a feature or features of xorg that makes it impossible.. other than FDO's tactical neglect?
EDIT: Actually, I dimly recall some old hardware that I think was supported by DRM that did tiled rendering. Maybe it was some PowerVR stuff? If my memory isn't failing me, then there's the counter to claims that it's impossible for xorg to support. :P
[0] Source: Me having these work just fine for quite a long time now on my personal machines that run xorg.
You will also need toolkits/games to add support for any additional protocol, which I doubt they will.
> It's not entirely clear what you're talking about with the third
Zero-copy video means you can play vides in web pages hardware accelerated and have no copy of the video frame required to send it to the display. This saves a lot of power.
> it's "just" a matter of writing the drivers to make it happen and getting them into an xorg fork
Compositing with Xorgs model and applying any kind of screen effect would be extremely painful on tiling GPU because of how the screen is passed back and fourth to the compositor. Given compositing in Wayland compositors is passive, it does not have that issue.
Notice how Wayland on the RPi had performance that it simply couldn't gain under Xorg.
> Me having these work just fine for quite a long time now on my personal machines that run xorg
Good for you. But we have modern hardware and demands that simply Xorg doesn't meet and the protocol is archaic that adding support isn't worth it.
HTML5 was not shitty because internet explorer was a shitty browser.
I want to use KDE. KDE was perfect for me before Wayland. I don't criticize Wayland here, I criticize KDE Wayland. And I'm worried because very soon KDE will delete X11 support.
So you think we should have one protocol for people who have HDR etc and another for those that don't?
I'm not saying you're wrong, but it's clear that basics of window management are not universally broken under Wayland. It works well for me and has for a couple of years.
Which toolkits are dropping support for X11?
AFAICR, few toolkits support Wayland (even though the two major ones, GTK and Qt, do).