[Mesa-dev] [PATCH 23/25] gallium/svga: handle query_rendered caps

[Emil Velikov]

All the values returned 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 hardware accelerated ?

Cc: Brian Paul <brianp at vmware.com>
Cc: José Fonseca <jose.r.fonseca at gmail.com>
Signed-off-by: Emil Velikov <emil.l.velikov at gmail.com>
---

Hello gents,
I'm assuming that there is no callback to host to determine
the amount of video memory, but I assume that you can think
of a reasonable way of determining the value that should be
returned by PIPE_CAP_VIDEO_MEMORY.

-Emil

 src/gallium/drivers/svga/svga_screen.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/src/gallium/drivers/svga/svga_screen.c b/src/gallium/drivers/svga/svga_screen.c
index b20aa26..c14ac20 100644
--- a/src/gallium/drivers/svga/svga_screen.c
+++ b/src/gallium/drivers/svga/svga_screen.c
@@ -284,6 +284,18 @@ svga_get_param(struct pipe_screen *screen, enum pipe_cap param)
       return 11;
    case PIPE_CAP_MAX_GL_ES2_VERSION:
       return 20;
+
+   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);
-- 
1.9.0