On October 13, 2018 19:50:00 "Keith Packard" <keithp@xxxxxxxxxx> wrote:
Jason Ekstrand <jason@xxxxxxxxxxxxxx> writes:
Actually, I think anv is doing the right thing too. Now I have no idea why
Keith was having problems.
anv is happily returning a valid pointer and radv is not?
In any case, I've switched to using vkGetInstanceProcAddr for the
VkPhysicalDevice function and it works fine with both drivers.
Using vkGetInstanceProcAddr is the right thing to do. The fact that anv
allows you to is a bug which should be investigated and fixed. I looked at
it a bit today and I'm still not sure how it's happening.
--Jason
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel
