Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Wayland Back-End For GTK+ Pushed Forward

  1. #11
    Join Date
    Sep 2010
    Posts
    686

    Default

    Hi, can anyone explain if and how Wayland will speed|ease|simplifiy development of Linux Graphics Drivers Stack?

  2. #12
    Join Date
    Oct 2008
    Posts
    3,149

    Default

    Quote Originally Posted by Prescience500 View Post
    Wouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?
    Applications don't care what support Wayland has, that's why you can still use 3D apps on a strictly 2D desktop. So you'll be able to use OpenGL 4 in games no matter what Wayland is doing.

    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.

  3. #13
    Join Date
    Sep 2008
    Posts
    270

    Default

    Quote Originally Posted by przemoli View Post
    Hi, can anyone explain if and how Wayland will speed|ease|simplifiy development of Linux Graphics Drivers Stack?
    Hi, please use the "search" option at the top of the page. It's been explained a lot of times already.

  4. #14
    Join Date
    Jan 2009
    Posts
    1,687

    Default

    even if this can be considered a milestone there are still stuff in the TODO list that afaik noone is working on

  5. #15

    Default

    Quote Originally Posted by przemoli View Post
    Hi, can anyone explain if and how Wayland will speed|ease|simplifiy development of Linux Graphics Drivers Stack?
    It won't. It uses existing mode-setting drivers, existing mesa, and so on.

  6. #16
    Join Date
    Jan 2009
    Posts
    1,687

    Default

    Quote Originally Posted by srg_13 View Post
    It won't. It uses existing mode-setting drivers, existing mesa, and so on.
    i remember there were some discussions about speed but noone as i can remember gave a proper answer on if it will make a difference

    the ease and simplicity in development will come from the smaller codebase as far as i understand it

  7. #17
    Join Date
    Nov 2007
    Posts
    1,024

    Default

    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •