Announcement

Collapse
No announcement yet.

Weston 8.0 Released With DRM HDCP Support, EGL Partial Updates, Headless OpenGL

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

  • Weston 8.0 Released With DRM HDCP Support, EGL Partial Updates, Headless OpenGL

    Phoronix: Weston 8.0 Released With DRM HDCP Support, EGL Partial Updates, Headless OpenGL

    Weston 8.0 was released today as the newest version of this reference Wayland compositor...

    http://www.phoronix.com/scan.php?pag...and-Weston-8.0

  • #2
    Weston 8 already? I'm pretty sure we will be in Weston 500.0 by 2050.

    Comment


    • #3
      If you see anyone trying to install Weston, do the world a favour and show them Sway or Wayfire instead.

      They have a far lower overhead than Weston, actually work, don't cause weird artifacts, don't cause hangs, and are generally not completely broken.

      Comment


      • #4
        Originally posted by archsway View Post
        If you see anyone trying to install Weston, do the world a favour and show them Sway or Wayfire instead.

        They have a far lower overhead than Weston, actually work, don't cause weird artifacts, don't cause hangs, and are generally not completely broken.
        Weston is a reference implementation. It was never developed to be used directly

        Comment


        • #5
          Originally posted by RahulSundaram View Post

          Weston is a reference implementation. It was never developed to be used directly
          Softpipe is a reference implementation. It was never developed to be used directly.

          However, when another driver gives different results to softpipe, softpipe is usually right.

          When a Wayland compositor is different from Weston, Weston is usually wrong.

          The core focus of Weston is correctness and reliability. Weston aims to be lean and fast.
          Weston isn't any of those things.

          Comment


          • #6
            A real important progress in terms of multimedia contents fruition.

            Comment


            • #7
              Originally posted by tildearrow View Post
              Weston 8 already? I'm pretty sure we will be in Weston 500.0 by 2050.
              it means that it improves quickly.

              Comment


              • #8
                HDCP, yuck! 🤮️

                No Vulkan support.

                Comment


                • #9
                  HDCP, yuck! 🤮️

                  No Vulkan support.
                  *quickly gets vomiting bag but too late*

                  Arghhh what a mess to clean up! But guess that is the mess HDCP is.




                  No Rust, $35 100% open-hardware RISC-V support.

                  Comment


                  • #10
                    Originally posted by tildearrow View Post
                    Weston 8 already? I'm pretty sure we will be in Weston 500.0 by 2050.
                    They bump the major version every time they make an API breakage, which is basically every release at this point.

                    Originally posted by archsway View Post
                    They have a far lower overhead than Weston, actually work, don't cause weird artifacts, don't cause hangs, and are generally not completely broken.
                    Originally posted by archsway View Post
                    When a Wayland compositor is different from Weston, Weston is usually wrong.
                    Originally posted by archsway View Post
                    Weston isn't any of those things.
                    I'm a developer for wlroots. What you've said is just plain wrong.
                    Weston is the highest quality Wayland compositor in many regards, and we're still playing catch up in a few areas, particularly regarding low-level graphics.
                    It is still a useful reference implementation which we compare a lot of our behaviour against.

                    Originally posted by uid313 View Post
                    HDCP, yuck! 🤮️
                    Honestly, it's pretty benign here. Weston's main use case currently is embedded, where they may care about this.
                    It's going to have absolutely no effect on any desktop uses. Also, due to how the kernel API works, and the user has full control of the compositor, it's trivial to lie to the client that we're actually "protecting" their content. It doesn't take any freedom away from the user.

                    Comment

                    Working...
                    X