From 8a09eee8587cd9117474ffabfd3c18b4b1d71095 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Fri, 28 Oct 2022 22:39:44 -0400 Subject: [PATCH] i915g: Advertise PIPE_CAP_BUFFER_MAP_PERSISTENT_COHERENT Currently buffer_map returns the raw pointer, there is no syncing or flushing or staging buffers or resource shadowing anywhere. That means if the driver is currently correct, it is implementing persistent and coherent behaviour already, so the CAP is trivial. Signed-off-by: Alyssa Rosenzweig Reviewed-by: Emma Anholt Part-of: --- src/gallium/drivers/i915/i915_screen.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/gallium/drivers/i915/i915_screen.c b/src/gallium/drivers/i915/i915_screen.c index b9e7b4dd1a2..a3480425e5b 100644 --- a/src/gallium/drivers/i915/i915_screen.c +++ b/src/gallium/drivers/i915/i915_screen.c @@ -393,6 +393,7 @@ i915_get_param(struct pipe_screen *screen, enum pipe_cap cap) case PIPE_CAP_ANISOTROPIC_FILTER: case PIPE_CAP_NPOT_TEXTURES: case PIPE_CAP_MIXED_FRAMEBUFFER_SIZES: + case PIPE_CAP_BUFFER_MAP_PERSISTENT_COHERENT: case PIPE_CAP_PRIMITIVE_RESTART: /* draw module */ case PIPE_CAP_PRIMITIVE_RESTART_FIXED_INDEX: case PIPE_CAP_VERTEX_ELEMENT_INSTANCE_DIVISOR: