2 ms·
As I understand it, Wayland doesn't define a protocol for using the server's hardware to render. Waypipe requires rendering at the client (probably in software,
by erik_seaberg 6y ago
As I understand it, Wayland doesn't define a protocol for using the server's hardware to render. Waypipe requires rendering at the client (probably in software, because datacenter GPUs are a rare extra) followed by a video codec for remoting.
- Blikkentrekker 6y agoYes, in both cases it is not not for technical reasons. Many Wayland compositors simply lack support for nVidia cards as they use a different protocol than all the others, and many graphics acceleration calls are simply not implemented through nested servers.
- erik_seaberg 6y agoWhat I’m getting at is that Wayland has better hardware acceleration only of compositing. It doesn’t seem to have any support for rendering shapes into pixels, even though that’s mostly why hardware accelerators were invented.
- Blikkentrekker 6y agoAs far as I know, there is no technical reason why Wayland would have better hardware acceleration. Modern X11 compositors work on very similar principles. — the only difference is the Wayland protocol requires that there be such a compositor, and on X11 one is free to even use outdated server drawing calls that have not been used for decades.
- kaba0 6y agoBut there is no reason for X11 to be in the picture, it does absolutely nothing other than adding another communication step between the client and the compositor.