Announcement

Collapse
No announcement yet.

X.Org Server 1.16 Delayed To Let In Non-PCI Graphics Support

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

  • X.Org Server 1.16 Delayed To Let In Non-PCI Graphics Support

    Phoronix: X.Org Server 1.16 Delayed To Let In Non-PCI Graphics Support

    X.Org Server 1.16 has been delayed. However, it's not been delayed like in some of the more notorious past releases due to outstanding bugs, etc, but over letting in a late feature to this latest revision of the X11 server...

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

  • #2
    And it looks like xserver i going to stay for a lot of years...

    Comment


    • #3
      Well of course it will take a ****load of years, it will take at least 10 years for mir to get into usable state, plus another 5-10 years for software devs to port software, plus of course there will be some devs that will not port to mir and so on.

      Comment


      • #4
        Originally posted by TheOne View Post
        And it looks like xserver i going to stay for a lot of years...
        At least transition has been started, xwayland mainlined is one of news for this xserver .

        Transition will be very slow of course, no one sane wants to broke all the Desktops now .

        Comment


        • #5
          1) X11 works.
          2) It really works.
          3) Really.

          And that is not irony. Xorg is stable software with known shortcomings, which do not prevent it from being usable.

          Good story is that nowadays most apps use middleware that handle all traffic to the OS graphic stack. So those apps require updated middleware in worst scenario.

          Some apps use plain X11, and those will need Xwaylan/Xmir. But both of those work OK, even now.

          What we wait for then is stability and general usefulness of Wayland/Mir themselfs.

          We can wait. X.org works. No cats/dogs will be harmed if they come with some delay.

          Comment


          • #6
            Originally posted by przemoli View Post
            1) X11 works.
            2) It really works.
            3) Really.

            And that is not irony. Xorg is stable software with known shortcomings, which do not prevent it from being usable.
            Can I use my hotkeys or lock the screen when a right-click menu is displayed? No.

            Can I expect to get a tear-free display regardless of my GPU? No.

            Is it still a huge security hole running as root, compromising every single Linux desktop? Yes.

            X11 does not work and it is finally going to die the death it deserves. No tears were shed.

            Comment


            • #7
              Originally posted by startzz View Post
              Well of course it will take a ****load of years, it will take at least 10 years for mir to get into usable state, plus another 5-10 years for software devs to port software, plus of course there will be some devs that will not port to mir and so on.
              Who cares about Mir when you have Wayland?

              Comment


              • #8
                Originally posted by BlackStar View Post
                Can I use my hotkeys or lock the screen when a right-click menu is displayed? No.
                I can use hotkeys just fine regardless of what X does, even if X is not running...

                Comment


                • #9
                  Originally posted by BlackStar View Post
                  Can I use my hotkeys or lock the screen when a right-click menu is displayed? No.
                  Why you can't i can do that . Which one from ~200 WM is yours

                  http://www.gilesorr.com/wm/table.html

                  Can I expect to get a tear-free display regardless of my GPU? No.
                  You can't expect that for Wayland either, neither for Windows nor for OS_X .

                  Is it still a huge security hole running as root, compromising every single Linux desktop? Yes.
                  Intel, Radeon Drivers Become Friendly With Non-Root X Server What is used that is compromised, what is not used that is not used (you fairly knows that ) - no one wants to compromise something that few developers understands, because they are working on it and maybe use it daily . Besides, all software has security issues .

                  "every single Linux desktop?" that "every single" is not true, Puppy Linux runs "everything" as root .
                  Last edited by dungeon; 07-08-2014, 06:09 AM.

                  Comment


                  • #10
                    ARM vs X86 GNU/Linux benchmarks sometimes please

                    Michael i would love to read the ARM vs Intel GNU/Linux benchmark battle

                    As there are basically 4 models, Mediatek, Qualcomm, Nvidia and Samsung ones, the new 64bit multicore CPUs and their GPUs tested vs the intel SoCs at Android (java) + GNU/Linux ( it seems that intel has a x2 performance not using java - art - or 1/2 performace using java - art -)

                    And of course compare the evolution and actual state of the art with the AMD and Intel x86_64 models and price / performance charts.

                    Comment


                    • #11
                      Originally posted by dungeon View Post
                      You can't expect that for Wayland either, neither for Windows nor for OS_X .
                      The Wayland's motto states exactly the opposite:
                      "every frame is perfect: which means that the applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker".
                      So not only you can expect that in Wayland, but if you see something wrong, you should fill a bug instead to workaround to the design deficiencies.

                      Comment


                      • #12
                        Originally posted by valeriodean View Post
                        The Wayland's motto states exactly the opposite:
                        "every frame is perfect: which means that the applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker".
                        So not only you can expect that in Wayland, but if you see something wrong, you should fill a bug instead to workaround to the design deficiencies.
                        You have that client allocated per windows buffers like Wayland do in DRI3 implementation which works for intel drivers in X, others (will) follow... . Of course that is goal for Wayland since 5 years ago, but that is only "a goal" because even now that is not true because of drivers and not for *all* GPUs ... so basicaly you don't have it for blindely picked up GPU . To quote again to the assumpation i answering:

                        Can I expect to get a tear-free display regardless of my GPU? No.

                        Comment


                        • #13
                          Originally posted by dungeon View Post
                          You have that client allocated per windows buffers like Wayland do in DRI3 implementation which works for intel drivers in X, others (will) follow... . Of course that is goal for Wayland since 5 years ago, but that is only "a goal" because even now that is not true because of drivers and not for *all* GPUs ... so basicaly you don't have it for blindely picked up GPU . To quote again to the assumpation i answering:
                          Do you know what tearing is? It's that artifact you see when an app draws to the framebuffer at the same time the graphics card is pushing it to the screen. That doesn't happen in Wayland, because apps don't draw to the framebuffer, and the compositor can decide when to draw, and to avoid drawing when the screen is refreshing. So if you see tearing in a Wayland compositor file a bug, because the compositor is broken.

                          Comment


                          • #14
                            Originally posted by BlackStar View Post
                            X11 does not work and it is finally going to die the death it deserves. No tears were shed.
                            Software is non-corporeal; it does not live or die, neither does it "deserve" anything (or not). You are allowing your emotions to impinge upon your rational judgement.

                            Comment


                            • #15
                              Originally posted by giucam View Post
                              Do you know what tearing is? It's that artifact you see when an app draws to the framebuffer at the same time the graphics card is pushing it to the screen. That doesn't happen in Wayland, because apps don't draw to the framebuffer, and the compositor can decide when to draw, and to avoid drawing when the screen is refreshing. So if you see tearing in a Wayland compositor file a bug, because the compositor is broken.
                              Oh, i know what is tearing, that is something people fighting last 90 years, and no one beat it complitely without some downsides . Wayland provide "forced solution" for that problem, that does not mean X can't have some solution to prevent tearing . And which known dowsides that solution has?

                              Wayland force users to use compositor, xserver does not . Some people have issues looking at anything which is composited, so Wayland is not something which magically "God send to as" . It is just software (althorough with good ideas), but nowhere near finished nor so widely supported and it is nowhere near robustness of X, which is this article all about .

                              Comment

                              Working...
                              X