intel/dev: Handle CHV CS thread weirdness in get_device_info_from_fd
Cherryview is weird in that the actual limits we can expose through GL are dependent on fusing information which is only obtainable at runtime. The same PCI ID may have different configurations with different maximum CS thread counts. We currently handle this in i965 and ANV by doing the calculation in the driver. This dates back to when intel_device_info was computed from the PCI ID. Now that we have get_device_info_from_fd, we can move the CHV stuff there and get it out of the driver. This fixes CHV thread counts on crocus as well. Reviewed-by:Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com> Part-of: <mesa/mesa!11861>
- src/intel/dev/intel_device_info.c 26 additions, 0 deletionssrc/intel/dev/intel_device_info.c
- src/intel/vulkan/anv_device.c 0 additions, 11 deletionssrc/intel/vulkan/anv_device.c
- src/intel/vulkan/anv_private.h 0 additions, 1 deletionsrc/intel/vulkan/anv_private.h
- src/mesa/drivers/dri/i965/brw_context.c 0 additions, 12 deletionssrc/mesa/drivers/dri/i965/brw_context.c