Announcement

Collapse
No announcement yet.

Initial XWayland Support Merged For X.Org Server 1.16

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

  • Initial XWayland Support Merged For X.Org Server 1.16

    Phoronix: Initial XWayland Support Merged For X.Org Server 1.16

    As anticipated, X.Org Server 1.16 when released this summer will feature initial support for XWayland...

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

  • #2
    Michael, you did a good job of listing the git commits in the Wayland full screen article. But this article doesn't have a single git link, trunk link, mailing list link, or anything. Its all follow-backs. Cite your sources.

    Comment


    • #3
      Originally posted by Ericg View Post
      Michael, you did a good job of listing the git commits in the Wayland full screen article. But this article doesn't have a single git link, trunk link, mailing list link, or anything. Its all follow-backs. Cite your sources.
      +1

      I'm hitting 'visit page' less often in my rss reader because the articles don't have anything interesting to follow. Although I get why its more interesting to have links to other pages (commercial revenue).

      Comment


      • #4
        Typical

        Typical Michael, never citing sources. Really shitty journalism.

        Comment


        • #5
          Originally posted by uid313 View Post
          Typical Michael, never citing sources. Really shitty journalism.
          Michael describes himself as "not being a journalist", so you can't say it's journalist. He frequently states his opinions in articles and sometimes reports not-worthy news.

          See the page title: [Phoronix] Linux Hardware Reviews, Open-Source Benchmarking & Linux Gaming

          Nothing talks about news or journalism here...

          Comment


          • #6
            See here for the X.Org mailing list where there are the patches posted/pulled.
            Here the post about the XWayland patches pulled
            Here is the reply of Kristian about the glamor support inclusion

            Bye.

            Comment


            • #7
              Originally posted by Ericg View Post
              Michael, you did a good job of listing the git commits in the Wayland full screen article. But this article doesn't have a single git link, trunk link, mailing list link, or anything. Its all follow-backs. Cite your sources.
              Yess, please be more open source.

              Comment


              • #8
                Originally posted by Calinou View Post
                Michael describes himself as "not being a journalist", so you can't say it's journalist. He frequently states his opinions in articles and sometimes reports not-worthy news.

                See the page title: [Phoronix] Linux Hardware Reviews, Open-Source Benchmarking & Linux Gaming

                Nothing talks about news or journalism here...
                Funny... you forgot to link to your source

                Comment


                • #9
                  To complete what is said on the mailing list:

                  . New gbm functions were introduced to Mesa master to export/import a dma-buf fd, so we don't use the ioctl directly (it seems the intel driver doesn't initialize something properly in this case) or use the EGL extension to import dma-buf (which implementation is... not very reliable. A restriction not in the spec is implemented, and a detail in the spec changed recently.). The glamor xwayland backend uses these gbm functions, but then can't be shipped until a Mesa release with the gbm functions. So finally only the software acceleration backend was merged, with a possibility to merge the glamor part before final release if Mesa releases a new version.

                  . XWayland Present support didn't make it. It needed some rework. Thus when using DRI3, you hit the Present support fallback, which doesn't avoid any copy, thus would not be faster than DRI2. (Note that DRI2 support wasn't added to XWayland by choice). Since Gnome still doesn't bypass scanout for Wayland, benchmarks shouldn't change.

                  . XWayland is still missing an important feature for games: the ability to restrict the mouse to the window (and still receive relative motion inputs if the mouse is blocked at the border), which makes a lot of games unplayable. This needs an Wayland extension, and even the SDL2 Wayland backend lacks this feature (I think it's the reason the backend isn't enabled by default)

                  Comment


                  • #10
                    The funny thing is that any "journalist" could start his/her own Linux news site and have a good chunk of news delivered by using Michael's anzwix.com:

                    http://anzwix.com/a/X.Org%20Server/M...ylandforkeithp
                    http://cgit.freedesktop.org/xorg/xse..._source=anzwix

                    Comment

                    Working...
                    X