Bug 72756

Summary: glxinfo shows openGL 3.1 version; ATI card is OpenGL 3.2 capable
Product: Mesa Reporter: Javier Fernandez <elhoir>
Component: Drivers/Gallium/r300Assignee: Default DRI bug account <dri-devel>
Status: CLOSED NOTABUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Javier Fernandez 2013-12-16 12:19:08 UTC
elhoir@elhoir-laptop:~$ glxinfo | more
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
    GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
    GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, 
    GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, 
    GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV710
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.0
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
    GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, 
    GL_AMD_shader_stencil_export, GL_ANGLE_texture_compression_dxt3, 
elhoir@elhoir-laptop:~$ 



while webpage shows that card supports OpenGL 3.2

http://www.amd.com/es/products/notebook/graphics/ati-mobility-hd-4000/hd-4500/Pages/hd-4500-specs.aspx

im not sure this is a bug, but i wanted to post about it
Comment 1 Javier Fernandez 2013-12-16 12:32:13 UTC
And, im using Ubuntu 14.04 which ships the 10.0.0 version. So, i have no chance to test 10.0.1. Sorry.
Comment 2 Marek Olšák 2013-12-16 12:35:05 UTC
OpenGL 3.2 hasn't been implemented yet. I will be done when it's done. Closing.

The webpage is wrong, your hardware supports OpenGL 3.3.
Comment 3 Javier Fernandez 2013-12-16 12:46:59 UTC
then why glxinfo shows 3.1? are you sure its not a bug?
Comment 4 Christian König 2013-12-16 12:58:49 UTC
Nope that's isn't a bug. It's working as expected, closing.
Comment 5 Alan Coopersmith 2013-12-16 15:34:26 UTC
(In reply to comment #3)
> then why glxinfo shows 3.1?

Because that's the limit of what the software for it currently supports - the
hardware having support for newer features doesn't help until someone writes
code to use them.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.