diff options
author | Emil Velikov <[email protected]> | 2014-08-14 21:09:43 +0100 |
---|---|---|
committer | Emil Velikov <[email protected]> | 2014-08-15 17:42:47 +0100 |
commit | 3a6b68b1132675dbb0c63cc6d977e19e4f473bd1 (patch) | |
tree | e6fd34290be49666b8af68f63fe15eb1eb0011fa /src/gallium/drivers | |
parent | 2b5f3956be2defaa3aad81371fc7cba16c338a45 (diff) |
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 <[email protected]>
Cc: José Fonseca <[email protected]>
Signed-off-by: Emil Velikov <[email protected]>
Diffstat (limited to 'src/gallium/drivers')
-rw-r--r-- | src/gallium/drivers/svga/svga_screen.c | 12 |
1 files changed, 12 insertions, 0 deletions
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); |