summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIan Romanick <idr@us.ibm.com>2004-01-22 16:25:02 +0000
committerIan Romanick <idr@us.ibm.com>2004-01-22 16:25:02 +0000
commit004d71f55429a97513457c1cc67b910d86e8bca9 (patch)
tree45fb4b7cd5514c75a29b7c0f4e7b155488fa71fc
parent03166f73f33970245d22b61b629f91647196e0f1 (diff)
Corrected a comment about how the DOT3 hardware works in the R200.
-rw-r--r--src/mesa/drivers/dri/r200/r200_texstate.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/mesa/drivers/dri/r200/r200_texstate.c b/src/mesa/drivers/dri/r200/r200_texstate.c
index b57657c32b4..2eb6962189b 100644
--- a/src/mesa/drivers/dri/r200/r200_texstate.c
+++ b/src/mesa/drivers/dri/r200/r200_texstate.c
@@ -1038,10 +1038,10 @@ static GLboolean r200UpdateTextureEnv( GLcontext *ctx, int unit )
case GL_DOT3_RGBA:
/* DOT3 works differently on R200 than on R100. On R100, just
* setting the DOT3 mode did everything for you. On R200, the
- * driver has to enable the biasing (the -0.5 in the combine
- * equation), and it has add the 4x scale factor. The hardware
- * only supports up to 8x in the post filter, so 2x part of it
- * happens on the inputs going into the combiner.
+ * driver has to enable the biasing and scale in the inputs to
+ * put them in the proper [-1,1] range. This is what the 4x and
+ * the -0.5 in the DOT3 spec do. The post-scale is then set
+ * normally.
*/
RGBshift++;