Re: [Mesa-dev] [PATCH v2 06/18] anv: Implement VK_KHX_external_memory

2017-03-31 Thread Chad Versace
On Thu 30 Mar 2017, Jason Ekstrand wrote: > On Thu, Mar 30, 2017 at 11:27 AM, Chad Versace > wrote: > > > On Mon 13 Mar 2017, Jason Ekstrand wrote: > > > There's really nothing for us to do here. So long as the user doesn't > > > set any crazy environment variables such as INTEL_VK_HIZ=false, al

Re: [Mesa-dev] [PATCH v2 06/18] anv: Implement VK_KHX_external_memory

2017-03-30 Thread Jason Ekstrand
On Thu, Mar 30, 2017 at 11:27 AM, Chad Versace wrote: > On Mon 13 Mar 2017, Jason Ekstrand wrote: > > There's really nothing for us to do here. So long as the user doesn't > > set any crazy environment variables such as INTEL_VK_HIZ=false, all of > > the compression formats etc. should "just wor

Re: [Mesa-dev] [PATCH v2 06/18] anv: Implement VK_KHX_external_memory

2017-03-30 Thread Chad Versace
On Mon 13 Mar 2017, Jason Ekstrand wrote: > There's really nothing for us to do here. So long as the user doesn't > set any crazy environment variables such as INTEL_VK_HIZ=false, all of > the compression formats etc. should "just work" at least for opaque > handle types. I think the commit messa

[Mesa-dev] [PATCH v2 06/18] anv: Implement VK_KHX_external_memory

2017-03-13 Thread Jason Ekstrand
There's really nothing for us to do here. So long as the user doesn't set any crazy environment variables such as INTEL_VK_HIZ=false, all of the compression formats etc. should "just work" at least for opaque handle types. --- src/intel/vulkan/anv_device.c | 6 +- src/intel/vulkan/a