st: play it safe for now and check _NEW_PROGRAM for shader const buffer atom
authorBrian Paul <brianp@vmware.com>
Tue, 21 Apr 2009 23:00:54 +0000 (17:00 -0600)
committerBrian Paul <brianp@vmware.com>
Tue, 21 Apr 2009 23:00:54 +0000 (17:00 -0600)
When a new program is bound but no constants are updated we still need
to update the Gallium const buffer.

src/mesa/state_tracker/st_atom_constbuf.c

index c31b120ed127ac83bd0d4d8aba11f8fbcce92387..77ecd0719e64b40839d53842c5b5a8f466cfff33 100644 (file)
@@ -124,7 +124,7 @@ static void update_fs_constants(struct st_context *st )
 const struct st_tracked_state st_update_fs_constants = {
    "st_update_fs_constants",                           /* name */
    {                                                   /* dirty */
-      _NEW_PROGRAM_CONSTANTS,
+      (_NEW_PROGRAM | _NEW_PROGRAM_CONSTANTS),          /* mesa */
       ST_NEW_FRAGMENT_PROGRAM,                         /* st */
    },
    update_fs_constants                                 /* update */