From 258ebe79a0c2133e362035b76f3cf3243880926f Mon Sep 17 00:00:00 2001 From: Bas Nieuwenhuizen Date: Mon, 25 Dec 2017 14:30:50 +0100 Subject: [PATCH] radv: Don't handle DCC in compute resolve. If the destination has DCC, we will use the FS resolve. Reviewed-by: Dave Airlie --- src/amd/vulkan/radv_meta_resolve_cs.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/amd/vulkan/radv_meta_resolve_cs.c b/src/amd/vulkan/radv_meta_resolve_cs.c index 5b6cea6c103..7c569aa9202 100644 --- a/src/amd/vulkan/radv_meta_resolve_cs.c +++ b/src/amd/vulkan/radv_meta_resolve_cs.c @@ -506,10 +506,7 @@ radv_cmd_buffer_resolve_subpass_cs(struct radv_cmd_buffer *cmd_buffer) struct radv_image *dst_img = cmd_buffer->state.framebuffer->attachments[dest_att.attachment].attachment->image; struct radv_image_view *src_iview = cmd_buffer->state.framebuffer->attachments[src_att.attachment].attachment; - if (dst_img->surface.dcc_size) { - radv_initialize_dcc(cmd_buffer, dst_img, 0xffffffff); - cmd_buffer->state.attachments[dest_att.attachment].current_layout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL; - } + assert(!dst_img->surface.dcc_size); VkImageSubresourceRange range; range.aspectMask = VK_IMAGE_ASPECT_COLOR_BIT; -- 2.30.2