Hi, can anyone explain if and how Wayland will speed|ease|simplifiy development of Linux Graphics Drivers Stack?
Announcement
Collapse
No announcement yet.
Wayland Back-End For GTK+ Pushed Forward
Collapse
X
-
Originally posted by Prescience500 View PostWouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?
The only things it really affects are Compiz and Kwin (and other compositors). These will need to be rewritten to work on OpenGL ES, which is basically the same as OpenGL 3 minus all the fixed-function backwards compatibility. It might be missing a few of the newer OpenGL features, but I suspect those will be included as extensions if they aren't already. I think it's good to only guarantee the base ES2.0 functionality anyway, so that the code can also run on mobile devices that only support that much.
Comment
-
Originally posted by srg_13 View PostIt won't. It uses existing mode-setting drivers, existing mesa, and so on.
the ease and simplicity in development will come from the smaller codebase as far as i understand it
Comment
-
Wayland requires apps to use OpenGL ES because there's no actual way to create an OpenGL context on Wayland right now. Normally, to create an OpenGL context, you need to use some windowing-system-specific API, such as GLX (X11), WGL (Windows), or AGL (Mac). Wayland doesn't implement any of these for obvious reasons, instead preferring that applications use EGL.
EGL supports OpenGL, but if I understand correctly it's only really implemented for OpenGL ES and OpenVG in Mesa right now.
This is entirely a short term and fixable problem, not a huge show stopper of any sort.
Comment
Comment