On Tue, Apr 03, 2018 at 11:53:19AM -0700, Scott D Phillips wrote:
> Nanley Chery writes:
>
> > On Tue, Jan 09, 2018 at 11:17:02PM -0800, Scott D Phillips wrote:
> >> Instead of gtt mapping, call out to other map functions (map_map
> >> or map_tiled_memcpy) for the depth surface. Removes a place w
Nanley Chery writes:
> On Tue, Jan 09, 2018 at 11:17:02PM -0800, Scott D Phillips wrote:
>> Instead of gtt mapping, call out to other map functions (map_map
>> or map_tiled_memcpy) for the depth surface. Removes a place where
>> gtt mapping is used.
>> ---
>> This is a bit icky, perhaps something
On Tue, Jan 09, 2018 at 11:17:02PM -0800, Scott D Phillips wrote:
> Instead of gtt mapping, call out to other map functions (map_map
> or map_tiled_memcpy) for the depth surface. Removes a place where
> gtt mapping is used.
> ---
> This is a bit icky, perhaps something like mapping z_mt with
> BRW_
Instead of gtt mapping, call out to other map functions (map_map
or map_tiled_memcpy) for the depth surface. Removes a place where
gtt mapping is used.
---
This is a bit icky, perhaps something like mapping z_mt with
BRW_MAP_DIRECT_BIT could be cleaner (but in that case the
depthstencil mapping and
