Intel's Mesa Driver Appears Ready For OpenGL 4.5

[Enverex]

Just built GIT and this is the output for a Broadwell GPU. Looks like it's showing 4.4 rather than 4.5 for now.

    Extended renderer info (GLX_MESA_query_renderer):
        Vendor: Intel Open Source Technology Center (0x8086)
        Device: Mesa DRI Intel(R) Iris Pro 6200 (Broadwell GT3e)  (0x1622)
        Version: 12.1.0
        Accelerated: yes
        Video memory: 3072MB
        Unified memory: yes
        Preferred profile: core (0x1)
        Max core profile version: 4.4
        Max compat profile version: 3.0
        Max GLES1 profile version: 1.1
        Max GLES[23] profile version: 3.1

[smitty3268]

Just built GIT and this is the output for a Broadwell GPU. Looks like it's showing 4.4 rather than 4.5 for now.

Right. Here's the commit that ended up enabling 4.4, they'll need to do something similar to enable 4.5. Those 2 lines should be it though.

https://cgit.freedesktop.org/mesa/me...1c74f27e26edb3

[Krejzi]

OpenGL 4.5 is ready for the Intel driver. Issue is rather internal and some paperwork is required before flipping it on.

[airlied]

Any chance this will be done in the future? Does Mesa see any value in doing this?

It's not really Mesa as a project to do it. Individual drivers have to get compliance tested. So Intel can say gl4.5 complaince but amdgpu or nouveau couldn't unless they also get tested.

Dave.

[airlied]

airlied

I don't think it would be too complicated to pass it... Even the Intel Vulkan implementation seems to pass the Vulkan tests, but that does not say anything about usefulness in practice.

It's non-trivial. Vulkan CTS was open source from the start, and it slowly being built up. OpenGL CTS is very different and has a lot of legacy in it. We have to fix all bugs all the way back to GL2 times. I've spent a month or two on it already, and there is still a fair bit of work left.

Dave.

[Kano]

Ok, maybe you can add piglit tests for the things you fix, most likely they are missing then.

[Notavi]

All the other features could be done in the compiler front-end and so were shared by all drivers. To get the most from this feature its better to implement it further down the stack. I think the plan is to add support for it in Galliums IR so that should give support to the other platforms, nobody has started work on this yet however.

Ah, that makes sense. Thanks for the info .

[caligula]

Is it time to celebrate?!?! 😃

https://media.giphy.com/media/RDbZGZ3O0UmL6/giphy.gif

No, people still can't use Intel drivers due to the lack of ES 3.2 and perfect OpenCL 2.0 support. For instance many run the unreleased GIMP which uses OpenCL 2.0 all day long. All the other GPU drivers for other hardware are ok, especially PowerVR and Mali, but for Intel, there's a really long way ahead.

[ssokolow]

Any chance this will be done in the future? Does Mesa see any value in doing this?

I doubt they will in any meaningful sense, for the same reason Linux isn't allowed to call itself UNIX. Linux and Mesa, like most healthy open-source projects, iterate so quickly that it's not worth the cost to get every new release certified.

[starshipeleven]

I doubt they will in any meaningful sense, for the same reason Linux isn't allowed to call itself UNIX. Linux and Mesa, like most healthy open-source projects, iterate so quickly that it's not worth the cost to get every new release certified.

Mesa/Gallium cannot get certified because it is a framework to build drivers. A framework itself cannot get certified as openGL compliant as it cannot run hardware on its own (as it is basically a huge library of stuff, not a driver), so any compliance tests have nowhere to run on.

Drivers using the framework can get certified as they are drivers and run on hardware.