From 2ccf481c17ccded161b9eecb63a257d81056e3ec Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Tue, 6 Dec 2022 16:16:08 +0100 Subject: [PATCH] zink: don't use defunct custom-flag We're no longer respecting this flag, so there's no need in setting it. Fixes: 00dc0036bb6 ("zink: flatten out buffer creation usage flags codepath") Part-of: --- src/gallium/drivers/zink/zink_context.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/src/gallium/drivers/zink/zink_context.c b/src/gallium/drivers/zink/zink_context.c index d4b5ad6..fa5a60e 100644 --- a/src/gallium/drivers/zink/zink_context.c +++ b/src/gallium/drivers/zink/zink_context.c @@ -3958,11 +3958,7 @@ zink_create_stream_output_target(struct pipe_context *pctx, if (!t) return NULL; - /* using PIPE_BIND_CUSTOM here lets us create a custom pipe buffer resource, - * which allows us to differentiate and use VK_BUFFER_USAGE_TRANSFORM_FEEDBACK_COUNTER_BUFFER_BIT_EXT - * as we must for this case - */ - t->counter_buffer = pipe_buffer_create(pctx->screen, PIPE_BIND_STREAM_OUTPUT | PIPE_BIND_CUSTOM, PIPE_USAGE_DEFAULT, 4); + t->counter_buffer = pipe_buffer_create(pctx->screen, PIPE_BIND_STREAM_OUTPUT, PIPE_USAGE_DEFAULT, 4); if (!t->counter_buffer) { FREE(t); return NULL; -- 2.7.4