diff options
| author | Marek Olšák <[email protected]> | 2010-06-25 03:28:09 +0200 |
|---|---|---|
| committer | Marek Olšák <[email protected]> | 2010-06-27 15:13:13 +0200 |
| commit | c200c47e6c2f8581608b83e703d611db1bebd7f6 (patch) | |
| tree | 37540af7d3f90b74c0a6fc54fe012dc9191bb79f /src/gallium/drivers/r300/r300_context.h | |
| parent | bb47d1c26fa000735bd06751ba00a98354c921b7 (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/r300/r300_context.h')
| -rw-r--r-- | src/gallium/drivers/r300/r300_context.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/gallium/drivers/r300/r300_context.h b/src/gallium/drivers/r300/r300_context.h index cea3ab3418f..5e35d890712 100644 --- a/src/gallium/drivers/r300/r300_context.h +++ b/src/gallium/drivers/r300/r300_context.h @@ -116,8 +116,6 @@ struct r300_rs_state { struct pipe_rasterizer_state rs_draw; uint32_t vap_control_status; /* R300_VAP_CNTL_STATUS: 0x2140 */ - uint32_t multisample_position_0;/* R300_GB_MSPOS0: 0x4010 */ - uint32_t multisample_position_1;/* R300_GB_MSPOS1: 0x4014 */ uint32_t point_size; /* R300_GA_POINT_SIZE: 0x421c */ uint32_t point_minmax; /* R300_GA_POINT_MINMAX: 0x4230 */ uint32_t line_control; /* R300_GA_LINE_CNTL: 0x4234 */ |