radv: Don't handle DCC in compute resolve.
If the destination has DCC, we will use the FS resolve. Reviewed-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:
parent
cebc9a119d
commit
258ebe79a0
|
@ -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;
|
||||
|
|
Loading…
Reference in New Issue