i965/fs: Organize prog_data by ksp number rather than SIMD width
The hardware packets organize kernel pointers and GRF start by slots that don't map directly to dispatch width. This means that all of the state setup code has to re-arrange the data from prog_data into these slots. This logic has been duplicated 4 times in the GL driver and one more time in the Vulkan driver. Let's just put it all in brw_fs.cpp. Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
This commit is contained in:
@@ -1418,12 +1418,7 @@ struct anv_pipeline {
|
||||
struct anv_state blend_state;
|
||||
uint32_t vs_simd8;
|
||||
uint32_t vs_vec4;
|
||||
uint32_t ps_simd8;
|
||||
uint32_t ps_simd16;
|
||||
uint32_t ps_ksp0;
|
||||
uint32_t ps_ksp2;
|
||||
uint32_t ps_grf_start0;
|
||||
uint32_t ps_grf_start2;
|
||||
uint32_t gs_kernel;
|
||||
uint32_t cs_simd;
|
||||
|
||||
|
Reference in New Issue
Block a user