We get called for TexImage higher up, and in a relatively normal way
(pixels == NULL is common for FBO setup).
---
 src/mesa/drivers/dri/intel/intel_tex_image.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/src/mesa/drivers/dri/intel/intel_tex_image.c 
b/src/mesa/drivers/dri/intel/intel_tex_image.c
index be328d1..060f22c 100644
--- a/src/mesa/drivers/dri/intel/intel_tex_image.c
+++ b/src/mesa/drivers/dri/intel/intel_tex_image.c
@@ -403,10 +403,6 @@ intelTexImage(struct gl_context * ctx,
       return;
    }
 
-   /* intelCopyTexImage calls this function with pixels == NULL, with
-    * the expectation that the mipmap tree will be set up but nothing
-    * more will be done.  This is where those calls return:
-    */
    pixels = _mesa_validate_pbo_teximage(ctx, dims, width, height, 1,
                                        format, type,
                                        pixels, unpack, "glTexImage");
-- 
1.7.5.4

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to