panvk: rework how we deal with extension-reqs
We're currently exposing a bunch of extensions that requiring Vulkan 1.1, and we'll soon enough do the same for Vulkan 1.2. Instead of having to update each of these extensions separately once we add new Vulkan version support for some gens, let's use a single variable for this instead. And while we *could* query the exposed vulkan version and do this a bit more "automatically", this makes it easy to leave some needless checks behind if the baseline version changes. Leaving this as a arch check in this function should make it a bit more obvious when the check can be removed. Reviewed-by:Boris Brezillon <boris.brezillon@collabora.com> Part-of: <!33971>
Please register or sign in to comment