mesa: in glReadBufer() set _NEW_BUFFERS, not _NEW_PIXEL
authorBrian Paul <brianp@vmware.com>
Sat, 2 May 2009 00:31:04 +0000 (18:31 -0600)
committerBrian Paul <brianp@vmware.com>
Sat, 2 May 2009 00:31:04 +0000 (18:31 -0600)
commit62043b27575c378c027251316421e4699f461108
treed7ea4d16eec360c450067c6886efa6b0e76208ac
parenta7ef5b76d6889c4a6614eddea0c021c83f6a8703
mesa: in glReadBufer() set _NEW_BUFFERS, not _NEW_PIXEL

Since GL_READ_BUFFER is historically part of the gl_pixel_attrib group
it made sense to signal changes with _NEW_PIXEL.  But now with FBOs it's
also part of the framebuffer state.

Now _NEW_PIXEL strictly indicates pixels transfer state changes.

This change avoids framebuffer state validation when any random bit of
pixel-transfer state is set.

DRI drivers updated too:  don't check _NEW_COLOR when updating framebuffer
state.  I think that was just copied from the Xlib driver because we care
about dither enable/disable state there.
src/mesa/drivers/dri/intel/intel_buffers.c
src/mesa/drivers/dri/r200/r200_state.c
src/mesa/drivers/dri/r300/r300_state.c
src/mesa/drivers/dri/radeon/radeon_state.c
src/mesa/drivers/x11/xm_dd.c
src/mesa/main/buffers.c