On Fri, 20 Jul 2018 12:26:22 +0100
Daniel Stone wrote:
> Hi Deepak,
>
> On Fri, 20 Jul 2018 at 12:21, Deepak Singh Rawat wrote:
> > In brief the damage is in frame-buffer coordinate of attached fb to the
> > plane.
> > Unlike plane src coordinates, damage clips are not in 16.16 fixed point.
> > > The damage region received during output repaint is in Weston's global
> > > co-ordinate space. To shift to CRTC co-ordinates, you need to
> > > translate the damage region by (-output->x, -output->y). When we are
> > > using the renderer, there is no scaling, so CRTC co-ordinates and
> > >
Hi Deepak,
On Wed, 25 Jul 2018 at 18:26, Deepak Singh Rawat wrote:
> > The damage region received during output repaint is in Weston's global
> > co-ordinate space. To shift to CRTC co-ordinates, you need to
> > translate the damage region by (-output->x, -output->y). When we are
> > using the
>
> The damage region received during output repaint is in Weston's global
> co-ordinate space. To shift to CRTC co-ordinates, you need to
> translate the damage region by (-output->x, -output->y). When we are
> using the renderer, there is no scaling, so CRTC co-ordinates and
> framebuffer
Hi Deepak,
On Fri, 20 Jul 2018 at 12:21, Deepak Singh Rawat wrote:
> In brief the damage is in frame-buffer coordinate of attached fb to the plane.
> Unlike plane src coordinates, damage clips are not in 16.16 fixed point.
> Damage
> during page flip is helpful for some drivers like vmwgfx
Hi List,
A while back I submitted RFC for page flip with damage interface in DRM
(https://lists.freedesktop.org/archives/dri-devel/2018-April/171900.html)
In brief the damage is in frame-buffer coordinate of attached fb to the plane.
Unlike plane src coordinates, damage clips are not in 16.16
