<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - DRI3 screen corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95475#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - DRI3 screen corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95475">bug 95475</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>To elaborate on <a href="show_bug.cgi?id=95475#c21">comment 21</a>:
The problem is that DRI3 can be used as a general buffer sharing mechanism. The
shared buffers can be used like any other pixmap in X, and the client can also
do whatever it wants with them on the client side.
EXA doesn't know that these pixmaps are shared with the client, so its tracking
of valid pixmap contents gets confused, and it ends up using stale contents. I
believe this is unfixable with the current EXA design because in contrast to
DRI2, there is no clearly defined flow of data between client and server side.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>