<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - KHR-GL43.compute_shader.resource-texture fails with MCS fast clears disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=109113#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - KHR-GL43.compute_shader.resource-texture fails with MCS fast clears disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=109113">bug 109113</a> from <a class="email" href="mailto:nanleychery@gmail.com" title="Nanley Chery <nanleychery@gmail.com>"> Nanley Chery</a> <pre>(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=109113#c1">comment #1</a>) > Sagar also noted that hacking intel_miptree_alloc_aux to set memset_value = > 0 instead of memset_value = 0xFF also makes the test pass. (I also > discovered 1/2/3 work, so basically any slice - just not "clear"...) > > That was pretty surprising to me. I wonder if we need to follow the restriction we assumed was only for CCS: If Software wants to enable Color Compression without Fast clear, Software needs to initialize MCS with zeros. That restriction goes all the way back to HSW at least (before single sample compression). Is this the only test that fails with fast clears disabled on CMS surfaces?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>