Announcement

Collapse
No announcement yet.

DRI3 Support Merged Into Mesa 10.0

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

  • DRI3 Support Merged Into Mesa 10.0

    Phoronix: DRI3 Support Merged Into Mesa 10.0

    Thursday was a heck of a day for Mesa development activity with several new OpenGL extensions having been merged, the Xorg state tracker being nuked, and the new game developer-focused GLX extension landing. However, that was not all and in the last commits prior to branching Mesa 10.0 from Git master was the adding of DRI3 support...

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

  • #2
    Cool to see __DRIimageLoaderExtension and __DRIimageDriverExtension are merged for the intel drivers.

    When they will be written for gallium drivers, dri3 will be supported on all cards, and the Wayland egl backend will use these extensions instead of the dri2 ones.

    Comment


    • #3
      I'm surprised there is no article yet about the new power management that was merged in nouveau git: http://cgit.freedesktop.org/nouveau/linux-2.6 .

      Comment


      • #4
        One thing that I would love the developers to clarify is... Drivers need support for DRI(X) but do Toolkits? Like do Qt or GTK need specific support for DRI3 or are things just going to automatically get better when Xorg 1.15 and Mesa 10 come out?

        Comment


        • #5
          Originally posted by Ericg View Post
          One thing that I would love the developers to clarify is... Drivers need support for DRI(X) but do Toolkits? Like do Qt or GTK need specific support for DRI3 or are things just going to automatically get better when Xorg 1.15 and Mesa 10 come out?
          This.



          jiejroejfskljdf;sjf (50 words extra-mega stupid limit).

          Comment


          • #6
            I'm still waiting for proper Optimus support.......... does DRI3 help with this? It keeps being hinted that DRI3 'may' help in this regard, but no clear answers have been posted.

            Comment


            • #7
              Originally posted by dh04000 View Post
              I'm still waiting for proper Optimus support.......... does DRI3 help with this? It keeps being hinted that DRI3 'may' help in this regard, but no clear answers have been posted.
              Ask one of the kernel devs if DMA-Sync ever got merged into the kernel, cause that was the big 'next' checklist item for Optimus

              Comment


              • #8
                Well I guess the hackers make sure the big v "10" is deserved.
                Though with the usual scheme it ought to be a devs release and for the users a stable 10.1 is then to come later.

                Comment


                • #9
                  Originally posted by Adarion View Post
                  Though with the usual scheme it ought to be a devs release and for the users a stable 10.1 is then to come later.
                  Mesa doesn't have separate 'feature freezes' and 'branching dates' (AFAIK) so changes are allowed to be submitted right up until a second before they branch the source tree, so this is kind of par for the course for them lol.

                  Comment


                  • #10
                    Originally posted by Ericg View Post
                    Ask one of the kernel devs if DMA-Sync ever got merged into the kernel, cause that was the big 'next' checklist item for Optimus
                    Would be good to see this getting some covering.

                    Comment


                    • #11
                      Originally posted by Ericg View Post
                      One thing that I would love the developers to clarify is... Drivers need support for DRI(X) but do Toolkits? Like do Qt or GTK need specific support for DRI3 or are things just going to automatically get better when Xorg 1.15 and Mesa 10 come out?
                      Isn't this kind of stuff hidden behind the X API?

                      Comment


                      • #12
                        Mesa trunk now comprehensively broken in Fedora

                        So I've just tried to Build Mesa on Fedora 19. First it complained about the missing dri3proto extension, and so I downloaded it from here:

                        http://cgit.freedesktop.org/xorg/proto/dri3proto

                        Then it complained about a missing presentproto extension, which I dutifully downloaded from here:

                        http://cgit.freedesktop.org/xorg/proto/presentproto

                        And now it is complaining about:
                        Code:
                        configure: error: Package requirements (x11 xext xdamage xfixes x11-xcb xcb-glx >= 1.8.1 xcb-dri2 >= 1.8 xcb-dri3 xcb-present xcb-sync xshmfence xxf86vm) were not met:
                        
                        No package 'xcb-dri3' found
                        No package 'xcb-present' found
                        No package 'xshmfence' found
                        And so I've given up. So much for "backwards compatibility". How is anyone expected to perform a "git bisect" now, with the tree in this state?

                        Comment


                        • #13
                          Heh, looks like I'm not the only one with this problem!

                          Originally posted by chrisr View Post
                          So I've just tried to Build Mesa on Fedora 19...
                          Somone has raised - and fixed - this as https://bugs.freedesktop.org/show_bug.cgi?id=71397.

                          Comment

                          Working...
                          X