[Mesa-dev] How about vk_features.txt?

Jason Ekstrand jason at jlekstrand.net
Mon Feb 13 02:58:52 UTC 2017

I'm certainly not opposed.  I've considered adding such a tracking file for
a while.  I'm not sure whether or not it's needed but it wouldn't hurt.

On Sun, Feb 12, 2017 at 6:48 PM, Romain Failliot <
romain.failliot at foolstep.com> wrote:

> Hi!
> I regularly receive questions about having Mesamatrix tracking the state
> of Vulkan API for ANV and RADV.
> I don't think there is a file in mesa repo that state the progression of
> Vulkan on each driver. So if you're interested, I could generate a base
> file (xml?) extracting the <feature> tag from the official API (
> https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml#L4117)
> and maybe the <extensions> tag as well, if you want. Then you could
> simply add the status of each "feature" for RADV and ANV.
> I'm open to discussion if you think it's a good idea. I don't know exactly
> what you would need to simplify the task as much as possible. But I think
> we could use our experience on features.txt to build something both more
> structured and easier to read (for a human and a machine)
> Cheers!
> --
> Romain "Creak" Failliot
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170212/cf994070/attachment.html>

More information about the mesa-dev mailing list