Jason Ekstrand 406cd9d126 intel/blorp: Emit all the binding tables ... At least on Sky Lake, after emitting 3DSTATE_CONSTANT_*, you are required to re-emit the 3DSTATE_BINDING_TABLE_POINTERS packet for the corresponding stage. If you don't, double-buffering may fail and you may get the wrong constants. It turns out that you need to do this even if you have no push constants to speak of or else the next 3DSTATE_CONSTANT packet you emit for that stage may not work correctly. Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Reviewed-by: Topi Pohjolainen <topi.pohjolainen@intel.com> Cc: "13.0" <mesa-stable@lists.freedesktop.org>		2016-11-08 08:32:55 -08:00
..
blorp.c	intel/blorp: Use wm_prog_data instead of hand-rolling our own	2016-11-02 09:32:15 -07:00
blorp.h	intel/blorp: Pass a brw_stage_prog_data to upload_shader	2016-11-02 09:32:19 -07:00
blorp_blit.c	intel/blorp: Pass a brw_stage_prog_data to upload_shader	2016-11-02 09:32:19 -07:00
blorp_clear.c	intel/blorp: Pass a brw_stage_prog_data to upload_shader	2016-11-02 09:32:19 -07:00
blorp_genX_exec.h	intel/blorp: Emit all the binding tables	2016-11-08 08:32:55 -08:00
blorp_priv.h	intel/blorp: Use wm_prog_data instead of hand-rolling our own	2016-11-02 09:32:15 -07:00
TODO	intel/blorp: Add a TODO file	2016-09-12 10:14:49 -07:00