diff options
| author | Keith Whitwell <[email protected]> | 2010-11-02 17:47:06 +0000 |
|---|---|---|
| committer | Keith Whitwell <[email protected]> | 2010-11-03 09:36:01 +0000 |
| commit | 29c4a15bf61a76cd71ffa5b8f09706d0eab84281 (patch) | |
| tree | dd9fe2c087e1c83c1812b0010016cd32c9c67105 /src/gallium/drivers/r600/r600.h | |
| parent | 14c0bbf469642722f86df315b9f85d23f9753956 (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/drivers/r600/r600.h')
| -rw-r--r-- | src/gallium/drivers/r600/r600.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/gallium/drivers/r600/r600.h b/src/gallium/drivers/r600/r600.h index 62d983269f5..5ec607bbd85 100644 --- a/src/gallium/drivers/r600/r600.h +++ b/src/gallium/drivers/r600/r600.h @@ -112,7 +112,8 @@ struct r600_tiling_info *r600_get_tiling_info(struct radeon *radeon); /* r600_bo.c */ struct r600_bo; struct r600_bo *r600_bo(struct radeon *radeon, - unsigned size, unsigned alignment, unsigned usage); + unsigned size, unsigned alignment, + unsigned binding, unsigned usage); struct r600_bo *r600_bo_handle(struct radeon *radeon, unsigned handle, unsigned *array_mode); void *r600_bo_map(struct radeon *radeon, struct r600_bo *bo, unsigned usage, void *ctx); |