nvfx: make NOUVEAU_NO_TRANSFER default off
authorLuca Barbieri <luca@luca-barbieri.com>
Mon, 12 Apr 2010 02:55:05 +0000 (04:55 +0200)
committerLuca Barbieri <luca@luca-barbieri.com>
Mon, 12 Apr 2010 03:46:04 +0000 (05:46 +0200)
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

index 59ab14826c354b2ded98f1e2cee06f18aee951d7..320f9a80f09d8791ad87e2013786cb91ca81fdea 100644 (file)
@@ -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);