<div dir="ltr">Thanks. Seems like my google foo was weak.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 8 Nov 2019 at 22:57, Chris Forbes <<a href="mailto:chrisf@ijw.co.nz">chrisf@ijw.co.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is enforcing a hard requirement in the spec:<br>
<br>
30.1. Feature Requirements<br>
<br>
All Vulkan graphics implementations must support the following features:<br>
<br>
* robustBufferAccess<br>
<br>
<br>
On Fri, Nov 8, 2019 at 1:49 PM <<a href="mailto:abergmeier@gmx.net" target="_blank">abergmeier@gmx.net</a>> wrote:<br>
><br>
> Testing my Vulkan driver agains Vulkan CTS, I am a bit suprised, that is seems like CTS does enforce robustBufferAccess (e.g. <a href="https://github.com/KhronosGroup/VK-GL-CTS/blob/master/external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp#L1045" rel="noreferrer" target="_blank">https://github.com/KhronosGroup/VK-GL-CTS/blob/master/external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp#L1045</a>).<br>
><br>
> Am I mistaken or can someone explain what the logic behind all that is.<br>
><br>
> Bonus points for pointing me to a hidden documentation about Vulkan CTS which I haven't found yet.<br>
><br>
> _______________________________________________<br>
> mesa-dev mailing list<br>
> <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
> <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
</blockquote></div>