From 58ee973e8737441a78c3ca49d3f8fe9db29447d0 Mon Sep 17 00:00:00 2001 From: Samuel Pitoiset Date: Mon, 29 Jul 2019 14:15:23 +0200 Subject: radv/gfx10: do not use the fast depth or stencil clear bytes path It causes issues on GFX10. This fixes rendering issues with vkmark and Wreckfest at least. Signed-off-by: Samuel Pitoiset Reviewed-by: Bas Nieuwenhuizen layerCount != iview->image->info.array_size) return false; - if (cmd_buffer->device->physical_device->rad_info.chip_class < GFX9 && + if (cmd_buffer->device->physical_device->rad_info.chip_class != GFX9 && (!(aspects & VK_IMAGE_ASPECT_DEPTH_BIT) || ((vk_format_aspects(iview->image->vk_format) & VK_IMAGE_ASPECT_STENCIL_BIT) && !(aspects & VK_IMAGE_ASPECT_STENCIL_BIT)))) @@ -1048,7 +1048,8 @@ radv_fast_clear_depth(struct radv_cmd_buffer *cmd_buffer, iview->image->planes[0].surface.htile_size, clear_word); } else { /* Only clear depth or stencil bytes in the HTILE buffer. */ - assert(cmd_buffer->device->physical_device->rad_info.chip_class >= GFX9); + /* TODO: Implement that path for GFX10. */ + assert(cmd_buffer->device->physical_device->rad_info.chip_class == GFX9); flush_bits = clear_htile_mask(cmd_buffer, iview->image->bo, iview->image->offset + iview->image->htile_offset, iview->image->planes[0].surface.htile_size, clear_word, -- cgit v1.2.3