Announcement

Collapse
No announcement yet.

The Hawaii Desktop Readies To Dance On Wayland

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • The Hawaii Desktop Readies To Dance On Wayland

    Phoronix: The Hawaii Desktop Readies To Dance On Wayland

    With the Green Island Compositor, the Hawaii Desktop is looking to be the very first Wayland-friendly desktop environment for Linux...

    http://www.phoronix.com/vr.php?view=MTI4ODA

  • #2
    Originally posted by phoronix View Post
    Phoronix: The Hawaii Desktop Readies To Dance On Wayland

    With the Green Island Compositor, the Hawaii Desktop is looking to be the very first Wayland-friendly desktop environment for Linux...

    http://www.phoronix.com/vr.php?view=MTI4ODA
    It's good to see that Wayland is finally getting some love in that regard, all we can hope for now is that the graphics card manufacturers add support for this standard soon, and if not that at least the Nouveau and radeon teams.
    Because software rendering, well, isn't the most speedy thing around. Just ask anyone who has to use LLVMpipe to render 3D compositing on unsupported hardware and you'll see what I mean.

    Comment


    • #3
      Originally posted by intellivision View Post
      Because software rendering, well, isn't the most speedy thing around.
      tell that to the e17 clowns.

      Comment


      • #4
        Originally posted by intellivision View Post
        It's good to see that Wayland is finally getting some love in that regard, all we can hope for now is that the graphics card manufacturers add support for this standard soon, and if not that at least the Nouveau and radeon teams.
        Because software rendering, well, isn't the most speedy thing around. Just ask anyone who has to use LLVMpipe to render 3D compositing on unsupported hardware and you'll see what I mean.
        Wayland is not a new X-Server, thus, it only specifies the user-space-tools and does not need to be "re-implemented" by manufacturers, as X still serves as a "back-end".

        Comment


        • #5
          Originally posted by frign View Post
          Wayland is not a new X-Server, thus, it only specifies the user-space-tools and does not need to be "re-implemented" by manufacturers, as X still serves as a "back-end".
          For now, every distro is going to have Wayland-on-X and it doesn't really matter, but in the long run it would be good to have the ability to run Wayland only without X. The proprietary drivers do need to support it, as Wayland needs access to certain functionality.

          It should be very simple for them to provide, though - the functionality is already there in their drivers, they just have to connect the APIs, and it's much simpler than getting X to work.

          Comment


          • #6
            Originally posted by smitty3268 View Post
            For now, every distro is going to have Wayland-on-X and it doesn't really matter, but in the long run it would be good to have the ability to run Wayland only without X. The proprietary drivers do need to support it, as Wayland needs access to certain functionality.

            It should be very simple for them to provide, though - the functionality is already there in their drivers, they just have to connect the APIs, and it's much simpler than getting X to work.
            Thanks for carrying it out a bit more; I could not have put it better .

            Comment


            • #7
              Originally posted by garegin View Post
              tell that to the e17 clowns.
              Not sure of your position, but you do realize that EVAS has tons of backends, including OGL?

              Comment


              • #8
                Originally posted by smitty3268 View Post
                For now, every distro is going to have Wayland-on-X and it doesn't really matter, but in the long run it would be good to have the ability to run Wayland only without X. The proprietary drivers do need to support it, as Wayland needs access to certain functionality.

                It should be very simple for them to provide, though - the functionality is already there in their drivers, they just have to connect the APIs, and it's much simpler than getting X to work.
                I think "X on wayland" is a better way to put what most distros are planning to go to. Wayland would serve as the system compositor, and any apps that need backwards compatibility would run via a rootless x server running on top of the wayland system compositor (xwayland).

                Comment

                Working...
                X