Re: [Mesa-dev] [PATCH 1/4] gallium: add pipe_screen::resource_changed

On Dec 5, 2016 11:43 AM, "Philipp Zabel" wrote: Am Montag, den 05.12.2016, 11:19 +0100 schrieb Philipp Zabel: > Hi Marek, > > Am Freitag, den 02.12.2016, 23:10 +0100 schrieb Marek Olšák: > > Shouldn't this be in pipe_context if it does a copy? Actually, resource_changed

Re: [Mesa-dev] [PATCH 1/4] gallium: add pipe_screen::resource_changed

Am Montag, den 05.12.2016, 11:19 +0100 schrieb Philipp Zabel: > Hi Marek, > > Am Freitag, den 02.12.2016, 23:10 +0100 schrieb Marek Olšák: > > Shouldn't this be in pipe_context if it does a copy? Actually, resource_changed is not supposed to create a copy immediately. Maybe instead of "trigger

Re: [Mesa-dev] [PATCH 1/4] gallium: add pipe_screen::resource_changed

Hi Marek, Am Freitag, den 02.12.2016, 23:10 +0100 schrieb Marek Olšák: > Shouldn't this be in pipe_context if it does a copy? It's basically > the opposite of flush_resource, right? I tried this at first (actually, at first I misunderstood the meaning of invalidate_resource and reused that, for

Re: [Mesa-dev] [PATCH 1/4] gallium: add pipe_screen::resource_changed

Shouldn't this be in pipe_context if it does a copy? It's basically the opposite of flush_resource, right? Marek On Fri, Dec 2, 2016 at 4:27 PM, Philipp Zabel wrote: > Add a hook to tell drivers that an imported resource may have changed > and they need to update their

[Mesa-dev] [PATCH 1/4] gallium: add pipe_screen::resource_changed

Add a hook to tell drivers that an imported resource may have changed and they need to update their internal derived resources. Signed-off-by: Philipp Zabel --- src/gallium/include/pipe/p_screen.h | 6 ++ 1 file changed, 6 insertions(+) diff --git