Module: Mesa Branch: master Commit: 930bba24e556d94c676b6828340431a15a9edffb URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=930bba24e556d94c676b6828340431a15a9edffb
Author: Luca Barbieri <[email protected]> Date: Mon Apr 12 04:55:05 2010 +0200 nvfx: make NOUVEAU_NO_TRANSFER default off Otherwise, we read from VRAM... Yes, again, it should be fixed to tell whether the buffer is in VRAM or not and behave appropriately. But this should be in pipebuffer/a generic layer; revisit this later too. --- src/gallium/drivers/nvfx/nvfx_transfer.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/gallium/drivers/nvfx/nvfx_transfer.c b/src/gallium/drivers/nvfx/nvfx_transfer.c index 59ab148..320f9a8 100644 --- a/src/gallium/drivers/nvfx/nvfx_transfer.c +++ b/src/gallium/drivers/nvfx/nvfx_transfer.c @@ -63,7 +63,7 @@ nvfx_miptree_transfer_new(struct pipe_context *pipe, static int no_transfer = -1; unsigned bind = nvfx_transfer_bind_flags(usage); if(no_transfer < 0) - no_transfer = debug_get_bool_option("NOUVEAU_NO_TRANSFER", TRUE/*XXX:FALSE*/); + no_transfer = debug_get_bool_option("NOUVEAU_NO_TRANSFER", FALSE); tx = CALLOC_STRUCT(nvfx_transfer); _______________________________________________ mesa-commit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-commit
