<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Image corruption with vkCmdCopyImage into I915_FORMAT_MOD_Y_TILED_CCS-tiled swapchain image"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111568#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Image corruption with vkCmdCopyImage into I915_FORMAT_MOD_Y_TILED_CCS-tiled swapchain image"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111568">bug 111568</a>
from <span class="vcard"><a class="email" href="mailto:mesa@felixdoerre.de" title="Felix <mesa@felixdoerre.de>"> <span class="fn">Felix</span></a>
</span></b>
<pre>Yes, that's the same commit that I also got while bisecting.
Regarding X vs Wayland: The application always connects via X (either directly
or via Xwayland), so from mesa-view it is always the X11-wsi-part. The
difference between native X and Xwayland (on my system) is that native X
reports:
DRM_FORMAT_MOD_LINEAR,
I915_FORMAT_MOD_X_TILED,
I915_FORMAT_MOD_Y_TILED,
as supported drm modifiers and Xwayland reports:
DRM_FORMAT_MOD_LINEAR,
I915_FORMAT_MOD_X_TILED,
I915_FORMAT_MOD_Y_TILED,
I915_FORMAT_MOD_Y_TILED_CCS,
Because I915_FORMAT_MOD_Y_TILED_CCS is missing in "native" X, the error does
not occur there.
Yes, you got perfect screenshots of "expected" vs "actual" behaviour (Denis
having "expected"=good and Lionel having "actual"=bad)</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>