summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/nvfx/nvfx_screen.c
diff options
context:
space:
mode:
authorMarek Olšák <maraeo@gmail.com>2010-06-25 03:28:09 +0200
committerMarek Olšák <maraeo@gmail.com>2010-06-27 15:13:13 +0200
commitc200c47e6c2f8581608b83e703d611db1bebd7f6 (patch)
tree37540af7d3f90b74c0a6fc54fe012dc9191bb79f /src/gallium/drivers/nvfx/nvfx_screen.c
parentbb47d1c26fa000735bd06751ba00a98354c921b7 (diff)
r300g: move emission of the MSPOS regs into the framebuffer state
Now the question is whether we are allowed to ignore gl_rasterization_rules and pipe_rasterizer_state::multisample. The former is invariant anyway and I think the latter would need re-emitting the AA state which is quite costly, considering that it implicitly flushes the whole pipeline (all AA regs in the AA state are *unpipelined*).
Diffstat (limited to 'src/gallium/drivers/nvfx/nvfx_screen.c')
0 files changed, 0 insertions, 0 deletions