Announcement

Collapse
No announcement yet.

New X DRI3 Extension Starts Working On GNOME, KDE

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

  • New X DRI3 Extension Starts Working On GNOME, KDE

    Phoronix: New X DRI3 Extension Starts Working On GNOME, KDE

    Keith Packard has announced that the first of two new DRI3 (DRI3000) extensions for X.Org is working and the new extension can cooperate with the loading of the complete KDE and GNOME desktops...

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

  • #2
    So DRI3 fixes evreything wrong with X.org, kind of like Wayland?

    When you run XWayland, does it use DRI3?
    Or is this only useful when X.org runs standalone?

    Comment


    • #3
      Originally posted by uid313 View Post
      So DRI3 fixes evreything wrong with X.org, kind of like Wayland?

      When you run XWayland, does it use DRI3?
      Or is this only useful when X.org runs standalone?
      DRI is all about Xorg and XWayland only. Wayland doesn't NEED these extensions, its all in there already by design.

      EDIT 1: DRI3 is mostly about sending buffer allocations back to the clients-- and also fixing tearing on sandy bridge / ivy bridge (yes...according to keith, the tearing on sandy bridge and ivy bridge could only be fixed by a new DRI extension)

      EDIT 2: As far as XWayland is concerned... it would probably use DRI3 internally, then hand off the buffer to Wayland to be displayed. But if you're using a GTK3 or Qt5 app, thats a non-issue because they are Wayland-native anyway.
      Last edited by Ericg; 06-05-2013, 06:56 PM.

      Comment


      • #4
        Originally posted by uid313 View Post
        So DRI3 fixes evreything wrong with X.org, kind of like Wayland?
        Not everything... they can't fix *everything*. All this does is prop up some of the weak areas, keeping X going a bit longer. Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...

        Comment


        • #5
          Originally posted by Delgarde View Post
          Not everything... they can't fix *everything*. All this does is prop up some of the weak areas, keeping X going a bit longer. Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...
          Michael should be putting up a Wayland article tomorrow (Thursday) or Friday in regards to fixing "everything" with X.

          Comment


          • #6
            Originally posted by Delgarde View Post
            Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...
            The funny part is that we're now in the 'cloud' era where everyone is going to push their processing to remote servers while displaying the results on a low-powered tablet, but apparently the future is throwing away the capability to separate the display from the software because that's a hangover from the last time we were all going to push processing to remote servers while displaying the output on low-powered hardware.

            Comment


            • #7
              Originally posted by movieman View Post
              The funny part is that we're now in the 'cloud' era where everyone is going to push their processing to remote servers while displaying the results on a low-powered tablet
              In a time where on slightly crowded wifis you still easily get 1+ seconds latency and sub 100 kbyte/s bandwidth?

              Comment


              • #8
                Silly consumer, you're not supposed to use wifi, but the glorious 4G connection that costs 100/month, and fills its cap in an hour of full-speed use. Chi-ching!

                Comment


                • #9
                  Originally posted by movieman View Post
                  The funny part is that we're now in the 'cloud' era where everyone is going to push their processing to remote servers while displaying the results on a low-powered tablet, but apparently the future is throwing away the capability to separate the display from the software because that's a hangover from the last time we were all going to push processing to remote servers while displaying the output on low-powered hardware.
                  What are you talking about? Wayland only throws away the ability to send render commands over the wire to a remote server. Next to none of the commonly used X11 apps today use these APIs, they render into a buffer instead and hands that buffer to X. This is what Wayland is designed for, and making that work with a remote client is no harder than with X and should work just as well. In fact, there is already (experimental) SPICE and RDP backends for Wayland/Weston. VNC would of course also be possible.
                  http://www.phoronix.com/scan.php?pag...tem&px=MTM0MDg
                  http://www.phoronix.com/scan.php?pag...tem&px=MTM1NzQ

                  Comment

                  Working...
                  X