<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c17">Comment # 17</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 <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Emil Velikov from <a href="show_bug.cgi?id=99715#c15">comment #15</a>) > 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' They don't have to. NVIDIA at least has the userspace driver, kernel driver, and DDX version-locked so it's impossible to have any mismatches. With AMD, I think it's a bit looser, but whatever WSI mechanism they're using for GL, they're also using for Vulkan. They probably left DRI2 behind a long time ago and don't really have this problem. > 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 Yes, which is why it's good that it only controls a warning and no actual driver behavior.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>