On Mon, 15 Jul 2019 09:23:43 +0200
Boris Brezillon wrote:
> Hello Marek,
>
> On Tue, 2 Jul 2019 20:09:23 +0200
> Boris Brezillon wrote:
>
> > On Tue, 2 Jul 2019 13:21:31 -0400
> > Marek Olšák wrote:
> >
> > > On Tue., Jul. 2, 2019, 09:50 Boris Brezillon,
> > > wrote:
> > >
> > > >
Hello Marek,
On Tue, 2 Jul 2019 20:09:23 +0200
Boris Brezillon wrote:
> On Tue, 2 Jul 2019 13:21:31 -0400
> Marek Olšák wrote:
>
> > On Tue., Jul. 2, 2019, 09:50 Boris Brezillon,
> > wrote:
> >
> > > From: Daniel Stone
> > >
> > > Add a pipe_screen->set_damage_region() hook to propagate
On Tue, 2 Jul 2019 13:21:31 -0400
Marek Olšák wrote:
> On Tue., Jul. 2, 2019, 09:50 Boris Brezillon,
> wrote:
>
> > From: Daniel Stone
> >
> > Add a pipe_screen->set_damage_region() hook to propagate
> > set-damage-region requests to the driver, it's then up to the
> > driver to decide what
On Tue., Jul. 2, 2019, 09:50 Boris Brezillon,
wrote:
> From: Daniel Stone
>
> Add a pipe_screen->set_damage_region() hook to propagate
> set-damage-region requests to the driver, it's then up to the driver to
> decide what to do with this piece of information.
>
> If the hook is left
From: Daniel Stone
Add a pipe_screen->set_damage_region() hook to propagate
set-damage-region requests to the driver, it's then up to the driver to
decide what to do with this piece of information.
If the hook is left unassigned, the buffer-damage extension is
considered unsupported.
