i965/gen6: Remove state flagging on BRW_NEW_CURBE_OFFSETS.
That flag was leftover from gen4, where brw_curbe.c is choosing ranges of the CURBE space for constants to live in, and the unit state tells where to load them from. That's not the case on gen6 -- we don't set this flag (since constants aren't in the URB), nor do we have any state like that to upload.
This commit is contained in:
@@ -65,8 +65,7 @@ upload_gs_state(struct brw_context *brw)
|
||||
const struct brw_tracked_state gen6_gs_state = {
|
||||
.dirty = {
|
||||
.mesa = _NEW_TRANSFORM,
|
||||
.brw = (BRW_NEW_CURBE_OFFSETS |
|
||||
BRW_NEW_URB_FENCE |
|
||||
.brw = (BRW_NEW_URB_FENCE |
|
||||
BRW_NEW_CONTEXT),
|
||||
.cache = CACHE_NEW_GS_PROG
|
||||
},
|
||||
|
@@ -165,8 +165,7 @@ upload_vs_state(struct brw_context *brw)
|
||||
const struct brw_tracked_state gen6_vs_state = {
|
||||
.dirty = {
|
||||
.mesa = _NEW_TRANSFORM | _NEW_PROGRAM_CONSTANTS,
|
||||
.brw = (BRW_NEW_CURBE_OFFSETS |
|
||||
BRW_NEW_NR_VS_SURFACES |
|
||||
.brw = (BRW_NEW_NR_VS_SURFACES |
|
||||
BRW_NEW_URB_FENCE |
|
||||
BRW_NEW_CONTEXT |
|
||||
BRW_NEW_VERTEX_PROGRAM |
|
||||
|
@@ -209,8 +209,7 @@ const struct brw_tracked_state gen6_wm_state = {
|
||||
_NEW_BUFFERS |
|
||||
_NEW_PROGRAM_CONSTANTS |
|
||||
_NEW_POLYGON),
|
||||
.brw = (BRW_NEW_CURBE_OFFSETS |
|
||||
BRW_NEW_FRAGMENT_PROGRAM |
|
||||
.brw = (BRW_NEW_FRAGMENT_PROGRAM |
|
||||
BRW_NEW_NR_WM_SURFACES |
|
||||
BRW_NEW_URB_FENCE |
|
||||
BRW_NEW_BATCH),
|
||||
|
Reference in New Issue
Block a user