Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: DRI3 Support Merged Into Mesa 10.0

  1. #1
    Join Date
    Jan 2007
    Posts
    15,640

    Default 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. #2
    Join Date
    Dec 2012
    Posts
    172

    Default

    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.

  3. #3
    Join Date
    Dec 2012
    Posts
    459

    Default

    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 .

  4. #4
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,935

    Default

    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?

  5. #5
    Join Date
    May 2012
    Posts
    946

    Default

    Quote 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).

  6. #6
    Join Date
    Aug 2012
    Posts
    526

    Default

    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.

  7. #7
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,935

    Default

    Quote 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

  8. #8
    Join Date
    Mar 2009
    Location
    in front of my box :p
    Posts
    840

    Default

    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.

  9. #9
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,935

    Default

    Quote 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.

  10. #10
    Join Date
    Feb 2013
    Posts
    112

    Default

    Quote 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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •