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_shader.c | |
| 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_shader.c')
| -rw-r--r-- | src/gallium/drivers/r600/r600_shader.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/drivers/r600/r600_shader.c b/src/gallium/drivers/r600/r600_shader.c index 4106587398b..1a0b35d9bf5 100644 --- a/src/gallium/drivers/r600/r600_shader.c +++ b/src/gallium/drivers/r600/r600_shader.c @@ -218,7 +218,7 @@ static int r600_pipe_shader(struct pipe_context *ctx, struct r600_pipe_shader *s /* copy new shader */ if (shader->bo == NULL) { - shader->bo = r600_bo(rctx->radeon, rshader->bc.ndw * 4, 4096, 0); + shader->bo = r600_bo(rctx->radeon, rshader->bc.ndw * 4, 4096, 0, 0); if (shader->bo == NULL) { return -ENOMEM; } |