<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BYT] ES31-CTS.functional.copy_image.non_compressed.viewclass_96_bits.rgb32f_rgb32f" href="https://bugs.freedesktop.org/show_bug.cgi?id=101910#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BYT] ES31-CTS.functional.copy_image.non_compressed.viewclass_96_bits.rgb32f_rgb32f" href="https://bugs.freedesktop.org/show_bug.cgi?id=101910">bug 101910</a> from <a class="email" href="mailto:topi.pohjolainen@intel.com" title="Topi Pohjolainen <topi.pohjolainen@intel.com>"> Topi Pohjolainen</a> <pre>After realizing that writing level 6 actually interferes with level 1 (instead of level 0 that I stated earlier), the bug started make more sense as levels 1 and 6 reside in the same tile. I reminded myself how Y-tiling is laid out and how the individual levels reside respect to one and other. Then the difference between valign == 2 and valign == 4 started to make more sense (initially the intra tile offset difference (32, 0) vs. (0, 4) looked odd). After some more digging I realized that the alignment difference itself wasn't significant - valign == 4 case was just lucky to place levels on tile boundary with respect to x-coordinate. And furthermore that our image copy logic failed to adjust intra tile x-coordinate when it treated RGB surfaces as three times wide R-only.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>