<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#c13">Comment # 13</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#c7">comment #7</a>) > Or at least having a common way _fully documented as part of the spec_ to do > it on all platforms/drivers is what we want here, right ? > Probing the system for NV-CONTROL/other brings vendor specific 'hacks' which > I afaict was against the ideas behind Vulkan ? I think you're a bit out of your depth here. There is a fully documented way to detect whether or not you can use WSI on the given platform. It's to call exactly the function that has the warning in it. The problem is that the warning can "spuriously" return false in anv or radv if DRI3 is not enabled and the application will fail to start or just crash. I put "spuriously" in quotes because returning false really is true in that case because you can't use Vulkan WSI with DRI2. What we're talking about here is not heuristics for determining whether or not Vulkan WSI is supported (that's simple, look for DRI3 and a GPU match). We're talking about heuristics for when to emit a warning message. I think checking for a couple of vendor extensions is a perfectly valid way to do that.</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>