Re: [Mesa-dev] [PATCH] etnaviv: keep track of buffer valid ranges

2017-10-26 Thread Wladimir
On Thu, Oct 19, 2017 at 11:52 AM, Christian Gmeiner wrote: >>> + if ((usage & PIPE_TRANSFER_WRITE) && >>> + prsc->target == PIPE_BUFFER && >>> + !util_ranges_intersect(&rsc->valid_buffer_range, >>> +box->x, box->x + box->width)) { >>> + /*

Re: [Mesa-dev] [PATCH] etnaviv: keep track of buffer valid ranges

2017-10-19 Thread Christian Gmeiner
Hi Lucas, 2017-10-19 11:25 GMT+02:00 Lucas Stach : > Am Donnerstag, den 19.10.2017, 07:59 +0200 schrieb Christian Gmeiner: >> This allows a write to proceed to an uninitialized part of a buffer >> even when the GPU is using the previously-initialized portions. >> Same is done for freedreno, nouvea

Re: [Mesa-dev] [PATCH] etnaviv: keep track of buffer valid ranges

2017-10-19 Thread Lucas Stach
Am Donnerstag, den 19.10.2017, 07:59 +0200 schrieb Christian Gmeiner: > This allows a write to proceed to an uninitialized part of a buffer > even when the GPU is using the previously-initialized portions. > Same is done for freedreno, nouveau and radeon. > > > Signed-off-by: Christian Gmeiner >

[Mesa-dev] [PATCH] etnaviv: keep track of buffer valid ranges

2017-10-18 Thread Christian Gmeiner
This allows a write to proceed to an uninitialized part of a buffer even when the GPU is using the previously-initialized portions. Same is done for freedreno, nouveau and radeon. Signed-off-by: Christian Gmeiner --- src/gallium/drivers/etnaviv/etnaviv_resource.c | 3 +++ src/gallium/drivers/et