Originally posted by SaucyJack
View Post
That said, I think this is a great idea. Our Vulkan driver currently lives entirely outside of Mesa with a completely different hardware layer (proprietary Linux drivers code-share with other OSes rather than other vendors) so just open sourcing it as-is isn't enough anyways.
We need to get to the point where we are sharing HW layer code between the open Vulkan driver and Mesa GL in order to have a sustainable open source stack, so having a community driver "pulling" and a proprietary driver "pushing" seems like pretty much the ideal way to work out what the final stack should look like.
Comment