[Mesa-dev] How about vk_features.txt?
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 tag from the official API ( https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml#L4117) and maybe the 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@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] How about vk_features.txt?
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.faill...@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 tag from the official API ( > https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml#L4117) > and maybe the 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@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] How about vk_features.txt?
I won't have time for the next 2 weeks, but after that I'll propose a file formatted in a way that is both easy to parse and easy to edit by a human. 2017-02-12 21:58 GMT-05:00 Jason Ekstrand : > 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.faill...@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 tag from the official API ( >> https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/ >> spec/vk.xml#L4117) and maybe the 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@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/mesa-dev >> >> > -- Romain "Creak" Failliot ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] How about vk_features.txt?
Hi! I'd like to know which information I should extract from this vk.xml file so that we can track the progress of ANV and RADV Vulkan drivers. Thanks! -- Romain "Creak" Failliot ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
