<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor""
href="https://bugs.freedesktop.org/show_bug.cgi?id=99715#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor""
href="https://bugs.freedesktop.org/show_bug.cgi?id=99715">bug 99715</a>
from <span class="vcard"><a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> <span class="fn">Emil Velikov</span></a>
</span></b>
<pre>Rene, Jason, all, thanks for the patience. Yes I was very silly of me to
suggest Vulkan layers.
With the risk of sounding like a complete nob I'll repeat my very first
question/suggestion.
How do other vendors deal with unmet requirements ? For example:
- when the NV-CONTROL/other extension is missing
- version mismatch for the extension and/or libraries present on the system
- the xorg.conf file setting are 'wrong'
As implied earlier, imho adding heuristics around NV-CONTROL/others is [sort
of] broken, since:
- these interfaces and can be implemented by others
- it makes future interop between AMDGPU-PRO and RADV rough
- does not scale - you can plug a AMD card in a ARM (Mali/Qcom/other) board
Hopefully that is nice food for thought, I won't bother you any more.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>