Announcement

Collapse
No announcement yet.

A Lot Of Improvements Are Coming For Mir 0.13, Including Work Towards Libinput

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

  • A Lot Of Improvements Are Coming For Mir 0.13, Including Work Towards Libinput

    Phoronix: A Lot Of Improvements Are Coming For Mir 0.13, Including Work Towards Libinput

    We've known since March that Mir 0.13 would be a very large release and it's certainly panning out that way...

    http://www.phoronix.com/scan.php?pag...r-0.13-Changes

  • #2
    Great

    Really nice that they are adopting libinput.
    So that X, Wayland and Mir will all run on one common input library.

    Comment


    • #3
      Originally posted by uid313 View Post
      Really nice that they are adopting libinput.
      So that X, Wayland and Mir will all run on one common input library.
      I find it quite ironical, because the main excuse for mir was that input handling in wayland sucked or something like that.

      Comment


      • #4
        Originally posted by uid313 View Post
        Really nice that they are adopting libinput.
        So that X, Wayland and Mir will all run on one common input library.
        All input drivers will be based off libinput and all OpenGL graphics drivers will work through EGL support. Not only that, logind will be controlling user sessions. Systemd and the underlying stack of Wayland that took 6+ years to write is not only simplifying the stack for desktops that implement the Wayland protocol but also for Unity and X.org/XWayland!

        Kind of shows everyone was over-reacting when stating Mir was going to complicate the already complicated graphics stack!

        Comment


        • #5
          Originally posted by CTown View Post
          Kind of shows everyone was over-reacting when stating Mir was going to complicate the already complicated graphics stack!
          Kind of the opposite really.

          It was obvious that Mir could only become reality after all the years of hard work that was done for Wayland.

          Now Mir is using even more of the Wayland stack, which is a good thing but it leaves the question over why they decided to duplicate that work. The reasons do not seem to be technical in nature.

          Comment


          • #6
            impkementation
            implementation

            Comment


            • #7
              Originally posted by CTown View Post
              All input drivers will be based off libinput and all OpenGL graphics drivers will work through EGL support. Not only that, logind will be controlling user sessions. Systemd and the underlying stack of Wayland that took 6+ years to write is not only simplifying the stack for desktops that implement the Wayland protocol but also for Unity and X.org/XWayland!

              Kind of shows everyone was over-reacting when stating Mir was going to complicate the already complicated graphics stack!
              only logind and libinput actually do anything for a wayland desktop
              that and ofc EGL (that is not only for opengl) and the other simplifications of DRI (buffers/framebuffers and modesetting)

              systemd has nothing to do with that, other then logind being the session manager and udev supplying input device nodes
              bout of which existed before and still can be found outside of systemd
              (and have nothing to do with the graphics stack (DRI))
              Last edited by gens; 02 May 2015, 07:31 PM.

              Comment


              • #8
                Originally posted by gens View Post
                ...
                PS if you wanna thank somebody, thank embedded and DirectFB devs (there are probably others, like Kristian and mesa devs)

                Comment


                • #9
                  Originally posted by Krejzi View Post
                  I find it quite ironical, because the main excuse for mir was that input handling in wayland sucked or something like that.
                  that is not the only joke. they needed phone support with drivers. and now they use libhybris,... go figure.

                  Comment


                  • #10
                    Originally posted by gens View Post
                    only logind and libinput actually do anything for a wayland desktop
                    that and ofc EGL (that is not only for opengl) and the other simplifications of DRI (buffers/framebuffers and modesetting)

                    systemd has nothing to do with that, other then logind being the session manager and udev supplying input device nodes
                    bout of which existed before and still can be found outside of systemd
                    (and have nothing to do with the graphics stack (DRI))
                    I meant systemd, the project; which logind is a part of. More parts of systemd simplify the desktop than just logind.

                    http://blog.davidedmundson.co.uk/blo...emd-and-plasma

                    Originally posted by justmy2cents View Post
                    that is not the only joke. they needed phone support with drivers. and now they use libhybris,... go figure.
                    In Canonical's defense, they really wasn't anything like QtCompositor, libhybris, or libinput around the time of Mir's announcement. Everything had to be done from scratch. Though, they should've worked with the community more. Perhaps, they could have helped with modularizing Weston.

                    Comment

                    Working...
                    X