summaryrefslogtreecommitdiff
path: root/src/gallium/winsys/r600/drm/r600_priv.h
diff options
context:
space:
mode:
authorKeith Whitwell <keithw@vmware.com>2010-11-02 17:47:06 +0000
committerKeith Whitwell <keithw@vmware.com>2010-11-03 09:36:01 +0000
commit29c4a15bf61a76cd71ffa5b8f09706d0eab84281 (patch)
treedd9fe2c087e1c83c1812b0010016cd32c9c67105 /src/gallium/winsys/r600/drm/r600_priv.h
parent14c0bbf469642722f86df315b9f85d23f9753956 (diff)
r600g: propogate resource usage flags to winsys, use to choose bo domains
This opens the question of what interface the winsys layer should really have for talking about these concepts. For now I'm using the existing gallium resource usage concept, but there is no reason not use terms closer to what the hardware understands - eg. the domains themselves.
Diffstat (limited to 'src/gallium/winsys/r600/drm/r600_priv.h')
-rw-r--r--src/gallium/winsys/r600/drm/r600_priv.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gallium/winsys/r600/drm/r600_priv.h b/src/gallium/winsys/r600/drm/r600_priv.h
index efecfebc2b..97c582397a 100644
--- a/src/gallium/winsys/r600/drm/r600_priv.h
+++ b/src/gallium/winsys/r600/drm/r600_priv.h
@@ -79,6 +79,7 @@ struct r600_bo {
unsigned size;
unsigned tiling_flags;
unsigned kernel_pitch;
+ unsigned domains;
};