<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BSW] Artifacts left on screen when using DRI3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98746#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BSW] Artifacts left on screen when using DRI3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98746">bug 98746</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>That config is not used. A software cursor is employed as a fallback when the
hw cursor fails. It shouldn't cause a visible trail, that would be DRI3 not
sync'ing correctly (known), but we shouldn't be hitting the swcursor either
(except for when the cursor goes slightly out of bounds on pipe C on bsw). I'm
more worried about why we have a swcursor here.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>