From: Emil Velikov Date: Thu, 14 Aug 2014 20:09:43 +0000 (+0100) Subject: gallium/svga: handle query_rendered caps X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=3a6b68b1132675dbb0c63cc6d977e19e4f473bd1;p=mesa.git gallium/svga: handle query_rendered caps All the values are are currently hardcoded. One could use some heuristics to determine the amount of video memory if a callback to the host is not available. Do we what to advertise the driver as hardwar accelerated ? Cc: Brian Paul Cc: José Fonseca Signed-off-by: Emil Velikov --- diff --git a/src/gallium/drivers/svga/svga_screen.c b/src/gallium/drivers/svga/svga_screen.c index d140f561e80..0fc96192311 100644 --- a/src/gallium/drivers/svga/svga_screen.c +++ b/src/gallium/drivers/svga/svga_screen.c @@ -288,6 +288,18 @@ svga_get_param(struct pipe_screen *screen, enum pipe_cap param) return 1; case PIPE_CAP_ENDIANNESS: return PIPE_ENDIAN_LITTLE; + + case PIPE_CAP_VENDOR_ID: + return 0x15ad; /* VMware Inc. */ + case PIPE_CAP_DEVICE_ID: + return 0x0405; /* assume SVGA II */ + case PIPE_CAP_ACCELERATED: + return 0; /* XXX: */ + case PIPE_CAP_VIDEO_MEMORY: + /* XXX: Query the host ? */ + return 1; + case PIPE_CAP_UMA: + return 0; } debug_printf("Unexpected PIPE_CAP_ query %u\n", param);