I guess the default context setup in the kernel is very 3D friendly.
Reviewed-by: Lionel Landwerlin
On 12/02/18 21:42, Jason Ekstrand wrote:
We were setting current_pipeline to UINT32_MAX and then calling
cmd_cmd_state_reset which memsets the entire state struct to 0 which
implicitly resets cu
We were setting current_pipeline to UINT32_MAX and then calling
cmd_cmd_state_reset which memsets the entire state struct to 0 which
implicitly resets current_pipeline to 3D. I have no idea how this
hasn't caused everything to explode.
Fixes: cd3feea74582 "anv/cmd_buffer: Rework anv_cmd_state_res
We were setting current_pipeline to UINT32_MAX and then calling
cmd_cmd_state_reset which memsets the entire state struct to 0 which
implicitly resets current_pipeline to 3D. I have no idea how this
hasn't caused everything to explode.
Fixes: cd3feea74582 "anv/cmd_buffer: Rework anv_cmd_state_res