Mesa (master): mesa: Add some comments about FRAG_RESULT_COLOR vs FRAG_RESULT_DATAn.

Eric Anholt anholt at kemper.freedesktop.org
Sat Apr 23 13:23:06 PDT 2011


Module: Mesa
Branch: master
Commit: e4da46e007de5c83202976a12efb0e894494a354
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=e4da46e007de5c83202976a12efb0e894494a354

Author: Eric Anholt <eric at anholt.net>
Date:   Wed Apr 20 17:55:54 2011 -0700

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.

---

 src/mesa/main/mtypes.h |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/src/mesa/main/mtypes.h b/src/mesa/main/mtypes.h
index 160ae9d..e90941d 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;



More information about the mesa-commit mailing list