
Originally Posted by
smitty3268
Intel supports 3.1, at least on some of their hardware. (Sandybridge and up i think)
Edit: i think glxinfo only loads the old 3.0 version, because it isn't setup to automatically try the core profiles. there is a command line switch you can use to do that i think.
Well, glxinfo from mesa-demos-git doesn't do it.
Code:
$ glxinfo -h
Usage: glxinfo [-v] [-t] [-h] [-i] [-b] [-s] ][-display <dname>]
-v: Print visuals info in verbose form.
-t: Print verbose table.
-display <dname>: Print GLX visuals on specified server.
-h: This information.
-i: Force an indirect rendering context.
-b: Find the 'best' visual and print its number.
-l: Print interesting OpenGL limits.
-s: Print a single extension per line.
glewinfo doesn't either:
Code:
glewinfo | head -8
---------------------------
GLEW Extension Info
---------------------------
GLEW version 1.9.0
Reporting capabilities of display :0, visual 0xa8
Running on a Mesa DRI Intel(R) Ivybridge Mobile from Intel Open Source Technology Center
OpenGL version 3.0 Mesa 9.1-devel (git-0fda2e9) is supported
kwin from kde 4.10 beta also says it's 3.0:
Code:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile
OpenGL version string: 3.0 Mesa 9.1-devel (git-0fda2e9)
OpenGL shading language version string: 1.30
Driver: Intel
GPU class: IvyBridge
OpenGL version: 3.0
GLSL version: 1.30
Mesa version: 9.1
X server version: 1.13.99
Linux kernel version: 3.7
Direct rendering: yes
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
That gputest benchmark tool wouldn't run because there is no GLSL 1.40: http://phoronix.com/forums/showthrea...829#post296829
Maybe these tools all rely on something glxinfo does. But then opengl 3.1 support isn't really useful since so much seems to depend on what is actually advertised.
...