Vulkan WSI+VK_KHR_display for KMS/DRM?
Jason Ekstrand
jason at jlekstrand.net
Mon Apr 10 19:32:26 UTC 2017
On April 10, 2017 12:29:12 PM Chad Versace <chadversary at chromium.org> wrote:
> On Tue 04 Apr 2017, Keith Packard wrote:
>> Jason Ekstrand <jason at jlekstrand.net> writes:
>>
>> > Interesting question. To my knowledge, no one has actually implemented the
>> > Vulkan WSI direct-to-display extensions. (I tried to prevent them from
>> > getting released with 1.0 but failed.) I believe the correct answer is to
>> > use the external memory dma-buf stuff that chad and I have been using and
>> > talk directly to KMS.
>>
>> Sounds good, and minimizes the amount of code I have to write too :-)
>
> I found an implementation. Nvidia's 2017-04-06 Linux driver release
> notes claim newly added support for VK_EXT_direct_mode_diplay, which is
> layered atop VK_KHR_display.
If it's useful to do so, we can always pull Keith's work into Mesa or even
put it in a layer. Let's start with an implementation and figure out the
Vulkan bits later. Of there's something interesting in NVIDIA's
extensions, we can let that guide the design of course.
> http://www.nvidia.com/download/driverResults.aspx/117741/en-us
> https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VK_EXT_direct_mode_display
>
>> > I see no good reason to have a large abstraction in
>> > the middle.
>>
>> Other than 'it's a standard', neither do I.
>
> Yup.
More information about the dri-devel
mailing list