Looks like Windows drivers exist already, too.
Announcement
Collapse
No announcement yet.
Valve Developed An Intel Linux Vulkan GPU Driver
Collapse
X
-
Originally posted by Kemosabe View PostAnd hopefully wine devs will replace their OGL wrapper with Vulkan
Originally posted by johnc View PostWho's going to use this? Most game devs can barely be bothered to port to Windows, let alone OpenGL.
So that leaves Valve.
And Valve doesn't make any games anymore.
So that leaves nobody.
Comment
-
Originally posted by johnc View PostWho's going to use this? Most game devs can barely be bothered to port to Windows, let alone OpenGL.
So that leaves Valve.
And Valve doesn't make any games anymore.
So that leaves nobody.Last edited by justmy2cents; 05 March 2015, 03:21 PM.
Comment
-
Originally posted by johnc View PostWho's going to use this? Most game devs can barely be bothered to port to Windows, let alone OpenGL.
So that leaves Valve.
And Valve doesn't make any games anymore.
So that leaves nobody.
What does "most game devs" mean? Microsoft, Sony, and Nintendo first party devs? Because everyone else make Windows ports. Some ports have issues, especially Ubisoft games, but most work fine.
Valve does make games, they just don't release a new sequel every year like other devs do. Granted because of the steady income from Steam, they have the privilege to be able to take their time.
OpenGL have nothing to do with this, this is a Vulkan driver. A ton of devs are excited about Vulkan, so I'd guess they want to "be bothered" to support it.
Comment
-
Originally posted by Ancurio View PostWhy would it be based on Mesa? Since Intel has side-stepped the API-agnostic Gallium3D infrastructure, their entire Mesa driver is completely OpenGL specific. I doubt there'd be anything useful to repurpose.
Comment
-
Originally posted by bakgwailo View PostThat is some revisionist history right there. How did Intel sidestep Gallium? Intel already had a massive investment in the legacy Mesa driver styles before Gallium came out, looked at Gallium, and decided that it would be way too much work with little benefit to them to drop all of their (working very well) old driver code and port to Gallium. Seems fair to me, its not like they don't contribute a ton to Mesa/X anyways.
Comment
-
Any informations about how Gallium3D is useful for Vulkan?
As far as I understand it, Gallium is a framework for "classic" graphic APIs. To build Vulkan on top of Gallium it had to read the SPIR-V code and transform it to its own IR so the driver can execute it...
Sounds rather stupid to me. It would be more effective to put Vulkan under Gallium3D.
Comment
-
I don't know for sure but is Gallium3D even low enough level to implement Vulkan? You can probably throw the state tracker code out as there won't be much state to track...
If that is the case, that may be why they could have chosen intel's driver stack over other cards. Perhaps intel's drivers are more ogl abstract than one may first assume?
Comment
Comment