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.

diff --git a/src/gallium/drivers/nvfx/nvfx_transfer.c b/src/gallium/drivers/nvfx/nvfx_transfer.c
index 59ab14826c354b2ded98f1e2cee06f18aee951d7..320f9a80f09d8791ad87e2013786cb91ca81fdea 100644 (file)
--- 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);