zink: Fix dummy CB path decision for VK_EXT_cwe presence.

We have to do the dummy workaround when we *don't* have the ext.  This was
apparently a mis-sedding.

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19057>
This commit is contained in:
Emma Anholt 2022-10-12 15:25:41 -07:00 committed by Marge Bot
parent 6a18e154bc
commit 179e638bb8
2 changed files with 2 additions and 2 deletions

View file

@ -2862,7 +2862,7 @@ zink_set_color_write_enables(struct zink_context *ctx)
if (disable_color_writes && ctx->clears_enabled)
zink_batch_rp(ctx);
ctx->disable_color_writes = disable_color_writes;
if (zink_screen(ctx->base.screen)->info.have_EXT_color_write_enable) {
if (!zink_screen(ctx->base.screen)->info.have_EXT_color_write_enable) {
/* use dummy color buffers instead of the more sane option */
zink_batch_no_rp(ctx);
ctx->rp_changed = true;

View file

@ -140,7 +140,7 @@ fail:
bool
zink_use_dummy_attachments(const struct zink_context *ctx)
{
return ctx->disable_color_writes && zink_screen(ctx->base.screen)->info.have_EXT_color_write_enable;
return ctx->disable_color_writes && !zink_screen(ctx->base.screen)->info.have_EXT_color_write_enable;
}
struct zink_framebuffer *