Mesa 8.0 Advances Open-Source Linux Graphics Drivers

[phoronix]

Phoronix: Mesa 8.0 Advances Open-Source Linux Graphics Drivers

Here's another reason to celebrate today besides the release of Wayland 0.85: Mesa 8.0 has been officially released! Mesa 8.0 is what brings OpenGL 3.0 compliance to several open-source graphics drivers, advances the Gallium3D architecture, brings many new features, and a heck of a lot of other changes that materialized over the past six months...

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

[elanthis]

glxglears was clearly the best application to screenshot to show off all of Mesa's many accomplishments for 8.0.

[Ex-Cyber]

glxglears was clearly the best application to screenshot to show off all of Mesa's many accomplishments for 8.0.

No kidding. Even glxinfo would have made more sense.

[AnonymousCoward]

Hey, nothing screams "graphics performance" like glxgears!

[Drago]

You made my day guys

[Veerappan]

You made my day guys

Agreed. Congratulations to all involved!

[ryszardzonk]

"The exposed video APIs that are maturing within Gallium3D is for VA-API and VDPAU. "

I was under the imperession that VA-API code was not mantained and that its VDPAU support that is supported atm. Have anything changed lately in mesa?

[ChrisXY]

"The exposed video APIs that are maturing within Gallium3D is for VA-API and VDPAU. "

I was under the imperession that VA-API code was not mantained and that its VDPAU support that is supported atm. Have anything changed lately in mesa?

Last time I checked (Some days/weeks ago) the --enable-va wouldn't compile with the libva than 1.0.15 which has been the default in archlinux for quite a while and instead demand an earlier version.
And you're probably right:

mesa-git-repository (git)-[master] % git log --stat src/gallium/state_trackers/va/
commit 3db309aecee57d7e0055a49a0e12a491a554347b
Author: Stéphane Marchesin <marcheu@chromium.org>
Date:   Fri Sep 30 17:49:48 2011 -0700

    configure: replace pkg-config calls with $(PKG_CONFIG) in the makefiles.
    
    Us poor souls who cross compile mesa want to be able to specify which pkg-config to pick, or at least just change one place.
    
    Reviewed-by: Brian Paul <brianp@vmware.com>
    Reviewed-by: Matt Turner <mattst88@gmail.com>

 src/gallium/state_trackers/va/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

commit d8c443ddde5e9734d60b63b3ec3b5a5ba756d022
Author: Michel Dänzer <michel.daenzer@amd.com>
Date:   Wed Sep 14 18:37:48 2011 +0200

    glx/dri2: Don't call X server for SwapBuffers when there's no back buffer.
    
    As already done in dri2CopySubBuffer().
    
    Should fix:
    
    https://bugs.freedesktop.org/show_bug.cgi?id=36371
    https://bugs.freedesktop.org/show_bug.cgi?id=40533
    
    Might fix:
    
    https://bugs.freedesktop.org/show_bug.cgi?id=32589
    
    Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>

 src/gallium/state_trackers/va/Makefile        |   28 +++++
 src/gallium/state_trackers/va/ftab.c          |  136 +++++++++++++++++++++
 src/gallium/state_trackers/va/htab.c          |   95 +++++++++++++++
 src/gallium/state_trackers/va/va_buffer.c     |   88 +++++++++++++
 src/gallium/state_trackers/va/va_config.c     |  121 ++++++++++++++++++
 src/gallium/state_trackers/va/va_context.c    |  106 ++++++++++++++++
 src/gallium/state_trackers/va/va_display.c    |   63 ++++++++++
 src/gallium/state_trackers/va/va_image.c      |  151 +++++++++++++++++++++++
 src/gallium/state_trackers/va/va_picture.c    |   60 +++++++++
 src/gallium/state_trackers/va/va_private.h    |  162 +++++++++++++++++++++++++
 src/gallium/state_trackers/va/va_subpicture.c |  143 ++++++++++++++++++++++
 src/gallium/state_trackers/va/va_surface.c    |  142 ++++++++++++++++++++++
 12 files changed, 1295 insertions(+), 0 deletions(-)

[droidix]

Very good news indeed. Congratulations to all of those involved in the effort!

I know the article mentioned much work has to be done for GL 3.1/3.2, etc.. support but I was wondering, in terms of scale, how much work will it take to go from GL 3.0 to 3.1 versus the amount of work it took to go from the last pre-3.0 to 3.0 support?

Another way of asking it: did this release clear a major technical/patent hurdle that will make future releases more straightforward?

[whizse]

Dunno about the amount of work, but word on IRC was that Intel was planning for 3.1 or 3.2 for Mesa 8.1.

A lot of work has already been done for 3.1 and 3.2:
http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt