May 10, 2020, 22:39 by s...@jkqxz.net:
> On 10/05/2020 15:23, Lynne wrote:
>
>> May 10, 2020, 14:33 by s...@jkqxz.net:
>>
>>> On 10/05/2020 11:54, Lynne wrote:
>>>
...
>>
>> From 6ecc3547bcfcc450c8ffe8d93a3040fd863f6288 Mon Sep 17 00:00:00 2001
>> From: Lynne
>> Date: Sun, 10 May 2020 1
On 10/05/2020 15:23, Lynne wrote:
> May 10, 2020, 14:33 by s...@jkqxz.net:
>> On 10/05/2020 11:54, Lynne wrote:
>>> ...
>
> From 6ecc3547bcfcc450c8ffe8d93a3040fd863f6288 Mon Sep 17 00:00:00 2001
> From: Lynne
> Date: Sun, 10 May 2020 11:47:50 +0100
> Subject: [PATCH 2/3] hwcontext_vulkan: expose
May 10, 2020, 14:33 by s...@jkqxz.net:
> On 10/05/2020 11:54, Lynne wrote:
>
>> */
>> VkInstance inst;
>> +/**
>> + * Enabled instance extensions. By default, VK_KHR_surface is enabled
>> if found.
>> + */
>>
>
> Clarify how this should be set by the user if they are supplying the
This solves a huge oversight - it lets users reliably use their own
AVVulkanDeviceContext. Otherwise, the extensions supplied and enabled
are not discoverable by anything outside of hwcontext_vulkan.
Patch attached.
This, and the previous patch to enable extensions through the options are
reall
On 10/05/2020 11:54, Lynne wrote:
> This solves a huge oversight - it lets users reliably use their own
> AVVulkanDeviceContext. Otherwise, the extensions supplied and enabled
> are not discoverable by anything outside of hwcontext_vulkan.
>
> Patch attached.
>
> This, and the previous patch to
