From: Luca Barbieri <luca@luca-barbieri.com>
Date: Mon, 12 Apr 2010 02:55:05 +0000 (+0200)
Subject: nvfx: make NOUVEAU_NO_TRANSFER default off
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=930bba24e556d94c676b6828340431a15a9edffb;p=mesa.git

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 59ab14826c3..320f9a80f09 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);