summaryrefslogtreecommitdiffstats
path: root/doxygen
diff options
context:
space:
mode:
authorKenneth Graunke <[email protected]>2018-12-11 00:34:11 -0800
committerKenneth Graunke <[email protected]>2018-12-14 00:44:54 -0800
commit0b44644ca6886de4201e3edd911b7d418a9d7680 (patch)
tree56cab0cfb09f7f56411eda32ba3476b8aa76c378 /doxygen
parenta2ec78883f402ccfb60bce3c35ec819061e6338f (diff)
genxml: Consistently use a numeric "MOCS" field
When we first started using genxml, we decided to represent MOCS as an actual structure, and pack values. However, in many places, it was more convenient to use a numeric value rather than treating it as a struct, so we added secondary setters in a bunch of places as well. We were not entirely consistent, either. Some places only had one. Gen6 had both kinds of setters for STATE_BASE_ADDRESS, but newer gens only had the struct-based setters. The names were sometimes "Constant Buffer Object Control State" instead of "Memory", making it harder to find. Many had prefixes like "Vertex Buffer MOCS"...in a vertex buffer packet...which is a bit redundant. On modern hardware, MOCS is simply an index into a table, but we were still carrying around the structure with an "Index to MOCS Table" field, in addition to the direct numeric setters. This is clunky - we really just want a number on new hardware. This patch eliminates the struct-based setters, and makes the numeric setters be consistently called "MOCS". We leave the struct definition around on Gen7-8 for reference purposes, but it is unused. v2: Drop bonus "Depth Buffer MOCS" fields on Gen7.5 and Gen9 Reviewed-by: Jordan Justen <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]>
Diffstat (limited to 'doxygen')
0 files changed, 0 insertions, 0 deletions