The important thing is OpenGL 4.5. It's the last major release of OpenGL. Once the drivers have supported that, then there is optimisation and bugfixing to be done before Mesa OpenGL is complete. My guess is that a lot of the OpenGL development work will be dropped once Vulkan is released and a large number of contributors try to move onto adding Vulkan. I'd like to see OpenGL get to a nice optimised point sooner than later, but feature completeness is a must. Looking at Mesa Matrix suggests that a lot of 4.4 and 4.5 is going to get completed very quickly. Most extensions have already had work done, and looking at what remains in 4.3 it appears that 4.4 and 4.5 rely on that work.
Announcement
Collapse
No announcement yet.
Core Mesa Is Now Just One Step Away From OpenGL 4.3 Compliance
Collapse
X
-
Originally posted by blackiwid View Postif there is much effort we dont know, maybe from the 5 people that are on it, its really much effort, compared to proprietary drivers its maybe 1/100 effort. Maybe the factor is only 1/20 or so dont know the exact numbers but "much effort" is something relativ...
I dont want to bitch but valve could have interest in good free intel and amd drivers because they dont want to make their customers have to use fglrx, so they could pay 20 fulltime people, I know they do SOME stuff, thats always better than nothing, but maybe I am wrong what I read so far sounded more like 1-5 full-time developers on that front if not less.
Comment
-
Originally posted by DMJC View PostThe important thing is OpenGL 4.5. It's the last major release of OpenGL. Once the drivers have supported that, then there is optimisation and bugfixing to be done before Mesa OpenGL is complete. My guess is that a lot of the OpenGL development work will be dropped once Vulkan is released and a large number of contributors try to move onto adding Vulkan. I'd like to see OpenGL get to a nice optimised point sooner than later, but feature completeness is a must. Looking at Mesa Matrix suggests that a lot of 4.4 and 4.5 is going to get completed very quickly. Most extensions have already had work done, and looking at what remains in 4.3 it appears that 4.4 and 4.5 rely on that work.
Comment
-
Originally posted by geearf View PostI don't believe OGL is end of life, we might still get new OGL in the future, so once mesa caught up to 4.5, it might still have to catch up to 4.6 or more... Of course I do hope I'm wrong about that.
- Likes 3
Comment
-
I'm curious about how much these drivers have in common. I know that Gallium unified things a lot but clearly there are still a lot of hardware-specific aspects to this. Does implementing this stuff in one driver at least give you a good clue about how to implement it in the others?
- Likes 1
Comment
-
Originally posted by Aeder View Post
They might want a complete working implementation that behaves according to the specification as much as possible before they start looking into serious optimization.
Comment
-
Originally posted by DMJC View PostThe important thing is OpenGL 4.5. It's the last major release of OpenGL. Once the drivers have supported that, then there is optimisation and bugfixing to be done before Mesa OpenGL is complete. My guess is that a lot of the OpenGL development work will be dropped once Vulkan is released and a large number of contributors try to move onto adding Vulkan. I'd like to see OpenGL get to a nice optimised point sooner than later, but feature completeness is a must. Looking at Mesa Matrix suggests that a lot of 4.4 and 4.5 is going to get completed very quickly. Most extensions have already had work done, and looking at what remains in 4.3 it appears that 4.4 and 4.5 rely on that work.Michael Larabel
https://www.michaellarabel.com/
Comment
-
Originally posted by eydee View PostBut why bother with implementing it for Intel before they come up with a GPU that can run anything 3D faster than 2 fps?Michael Larabel
https://www.michaellarabel.com/
- Likes 2
Comment
-
Originally posted by Chewi View PostI'm curious about how much these drivers have in common. I know that Gallium unified things a lot but clearly there are still a lot of hardware-specific aspects to this. Does implementing this stuff in one driver at least give you a good clue about how to implement it in the others?
Comment
Comment