From: Eric Anholt <eric@anholt.net>
Date: Thu, 21 Apr 2011 00:55:54 +0000 (-0700)
Subject: mesa: Add some comments about FRAG_RESULT_COLOR vs FRAG_RESULT_DATAn.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=e4da46e007de5c83202976a12efb0e894494a354;p=mesa.git

mesa: Add some comments about FRAG_RESULT_COLOR vs FRAG_RESULT_DATAn.

This came from reading what swrast does, and 965 now behaves the same
and gallium appears to as well.
---

diff --git a/src/mesa/main/mtypes.h b/src/mesa/main/mtypes.h
index 160ae9d2622..e90941d3570 100644
--- a/src/mesa/main/mtypes.h
+++ b/src/mesa/main/mtypes.h
@@ -376,7 +376,15 @@ typedef enum
 {
    FRAG_RESULT_DEPTH = 0,
    FRAG_RESULT_STENCIL = 1,
+   /* If a single color should be written to all render targets, this
+    * register is written.  No FRAG_RESULT_DATAn will be written.
+    */
    FRAG_RESULT_COLOR = 2,
+
+   /* FRAG_RESULT_DATAn are the per-render-target (GLSL gl_FragData[n]
+    * or ARB_fragment_program fragment.color[n]) color results.  If
+    * any are written, FRAG_RESULT_COLOR will not be written.
+    */
    FRAG_RESULT_DATA0 = 3,
    FRAG_RESULT_MAX = (FRAG_RESULT_DATA0 + MAX_DRAW_BUFFERS)
 } gl_frag_result;