summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Anholt <eric@anholt.net>2009-01-07 14:26:11 -0800
committerXiang, Haihao <haihao.xiang@intel.com>2009-01-08 16:51:41 +0800
commit5b3bb7aaf7646ab5fb1ab632529ea0ae4511079d (patch)
tree510d3164ba473a0a364614a8ca064787ccafe426
parent32e43b60027eb7a3be31abde661a221de97963b1 (diff)
i965: Remove worrisome comment about _NEW_PROGRAM signaling fp change.
Everything now depends on either BRW_NEW_FRAGMENT_PROGRAM or BRW_NEW_VERTEX_PROGRAM. (cherry picked from commit 6d2cf395f401b53da1c2fc4485a297fd975637c6)
-rw-r--r--src/mesa/drivers/dri/i965/brw_state_upload.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/mesa/drivers/dri/i965/brw_state_upload.c b/src/mesa/drivers/dri/i965/brw_state_upload.c
index 5124535f2a..4845859b3e 100644
--- a/src/mesa/drivers/dri/i965/brw_state_upload.c
+++ b/src/mesa/drivers/dri/i965/brw_state_upload.c
@@ -314,12 +314,8 @@ void brw_validate_state( struct brw_context *brw )
state->brw |= ~0;
}
- /* texenv program needs to notify us somehow when this happens:
- * Some confusion about which state flag should represent this change.
- */
if (brw->fragment_program != brw->attribs.FragmentProgram->_Current) {
brw->fragment_program = brw->attribs.FragmentProgram->_Current;
- brw->state.dirty.mesa |= _NEW_PROGRAM;
brw->state.dirty.brw |= BRW_NEW_FRAGMENT_PROGRAM;
}