i965/miptree: Delete the layered rendering resolve

We never fast-clear more than the base slice (LOD 0, layer 0) anyway, so
layered rendering without a resolve is always perfectly safe.  Should
this ever change in the future, we'll have to put some sort of resolve
back in but we can cross that bridge when we come to it.

Reviewed-by: Chad Versace <chadversary@chromium.org>

diff --git a/src/mesa/drivers/dri/i965/intel_mipmap_tree.c b/src/mesa/drivers/dri/i965/intel_mipmap_tree.c
index 7996ca7cc9278d57395bd889fe0dec574736e1d7..366e45c51805d3b0ab010feb2a8d2e510aec0f64 100644 (file)
--- a/src/mesa/drivers/dri/i965/intel_mipmap_tree.c
+++ b/src/mesa/drivers/dri/i965/intel_mipmap_tree.c
@@ -2536,20 +2536,6 @@ intel_miptree_prepare_render(struct brw_context *brw,
       intel_miptree_prepare_access(brw, mt, level, 1, start_layer, layer_count,
                                    false, false);
    }
-
-   /* For layered rendering non-compressed fast cleared buffers need to be
-    * resolved. Surface state can carry only one fast color clear value
-    * while each layer may have its own fast clear color value. For
-    * compressed buffers color value is available in the color buffer.
-    */
-   if (layer_count > 1 &&
-       !(mt->aux_disable & INTEL_AUX_DISABLE_CCS) &&
-       !intel_miptree_is_lossless_compressed(brw, mt)) {
-      assert(brw->gen >= 8);
-
-      intel_miptree_prepare_access(brw, mt, level, 1, start_layer, layer_count,
-                                   false, false);
-   }
 }
 
 void