diff options
author | Ben Skeggs <[email protected]> | 2017-01-28 13:14:10 +1000 |
---|---|---|
committer | Ilia Mirkin <[email protected]> | 2017-06-20 20:18:54 -0400 |
commit | 7bae3ef812f979f6bf6b84098d59ace3be7ca075 (patch) | |
tree | b2838bb145f1add2d3f3e02c6b863ab2e0111b69 /src/gallium/state_trackers | |
parent | ec3d489d5b70686359030dcca542ff979cfd50ff (diff) |
nvc0: fix transfer of larger rectangles with DmaCopy on gk104 and up
By treating the rectangles as 1cpp, we can run up against some internal
copy engine limits and trigger a MEM2MEM_RECT_OUT_OF_BOUNDS error check
at launch time.
This commit enables the REMAP hardware, which allows us to specify both
the component size and number of components for a transfer. We're then
able to pass in the real width/nblocksx values and not hit the limits.
There's a couple of "supported" CPPs in the list that we can't actually
hit, but are there simply because they're possible.
Signed-off-by: Ben Skeggs <[email protected]>
Acked-by: Ilia Mirkin <[email protected]>
Diffstat (limited to 'src/gallium/state_trackers')
0 files changed, 0 insertions, 0 deletions