[Bug 99715] Don't print: "Note: Buggy applications may crash, if they do please report to vendor"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 16 18:48:19 UTC 2017


--- Comment #7 from Emil Velikov <emil.l.velikov at gmail.com> ---
(In reply to Rene Lindsay from comment #3)
> ...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".


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 ?

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170216/574133c5/attachment.html>

More information about the intel-3d-bugs mailing list