From: Joshua Ashton <joshua@froggi.es>
Subject: Re: [PATCH] d3d12: Check for VK_KHR_external_fence_capabilities before using VkPhysicalDeviceIDProperties.
Message-Id: <1ab2f18e-7b35-caf9-4af7-e0ff6c976233@froggi.es>
Date: Thu, 25 Feb 2021 16:18:44 +0000
In-Reply-To: <4b8621f3-b9a8-0101-33aa-3b60c11ff0bc@codeweavers.com>
References: <20210224205842.591939-1-z.figura12@gmail.com> <CAOsNvwxQKv7s506JfJpYC6=bXUTqr0-FXrUm7YBOa05tT_3Ouw@mail.gmail.com> <a88451e6-5185-0c1d-0d7a-9ee91baf34d0@froggi.es> <4b8621f3-b9a8-0101-33aa-3b60c11ff0bc@codeweavers.com>

On 2/25/21 4:01 PM, Zebediah Figura (she/her) wrote:
> On 2/25/21 7:00 AM, Joshua Ashton wrote:
>> There is no reason to. This is core in Vulkan 1.1.
>>
>> You should just use a newer API version.
>> There is no relevant driver that doesn't support this.
> 
> Mesa's v3dv is an example of a driver that does not support Vulkan 1.1.

That is not relevant hardware:
It is not capable of supporting D3D12.

- Joshie 🐸✨

> 
>>
>> - Joshie 🐸✨
>>
>