Wayland EGL interposer
dcommander opened this issue · 4 comments
Referring to TurboVNC/turbovnc#18 in the near term at least, it is going to be necessary to implement a Wayland EGL interposer in order to get OpenGL hardware acceleration in a Weston remote display environment with the nVidia proprietary drivers. Although it is likely that this interposer will be rendered obsolete at some point (because the Weston developers have a long-term plan to support a hardware-accelerated headless remote display backend, and eventually the nVidia stuff will be sorted out), at the moment an interposer would be the easiest way to enable remote display with OpenGL hardware acceleration under Weston, which would likely spur development of remote display technologies based on that compositor.
Depends on #10. Once VirtualGL is using EGL "behind the scenes", i.e. once it's converting GLX calls to EGL calls, then implementing an EGL-to-EGL interposer for Wayland would be trivial. It would simply redirect EGL calls targeted at a Wayland display to a DRM device instead and maintain a mapping of Wayland windows to FBOs.
Just found out about Waypipe https://mstoeckl.com/notes/gsoc/blog.html Looks interesting to try see how it performs.
Interesting. So Waypipe is sort of implementing the equivalent of remote X but for Wayland?
Interesting. So Waypipe is sort of implementing the equivalent of remote X but for Wayland?
Yeah looks like so.
The EGL/X11 interposer proposed in #66 (which emulates EGL/X11 using EGL/DRM) is now implemented in VirtualGL 3.1 evolving (dev branch), so emulating EGL/Wayland using EGL/DRM would be a fairly simple add-on, if it proves necessary.