<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#c7">Comment # 7</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>(In reply to Rene Lindsay from <a href="show_bug.cgi?id=99715#c3">comment #3</a>)
<span class="quote">> ...As for the error message, as Jason said, the historical reason for
> printing:
> "No DRI3 support", is to inform the USER that he hasn't configured his
> system correctly, and he should please go enable DRI3.
>
> However, following it with "Buggy applications may crash", implies that its
> the application DEVELOPER's fault for not adding DRI3, which is misleading
> and unfair.
>
> Actually, the USER should enable DRI3 himself, and NOT go "report to vendor".</span >
Rene,
Please note that _nothing_ is implied by the message. It's straight out facts.
If you think the message is misleading, please send a patch to improve it.
As mentioned in our email chat, what do other drivers when their prerequisites
are not met ? Using a similar approach in mesa would be better imho.
On the topic of detecting the first [working] implementation I'll repeat my
earlier decision - shouldn't this information be provided by the Vulkan layers
?
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 ?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>