On 2018-08-24 1:34 a.m., Alex Goins wrote:
> Hi Adam,
>
> Can this be merged?
Pushed, thanks.
To ssh://gitlab.freedesktop.org/xorg/xserver
1fc20b985..a90f33721 master -> master
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast
Hi Adam,
Can this be merged?
Thanks,
Alex
On Wed, 15 Aug 2018, Alex Goins wrote:
> Thanks, Keith and Michel!
>
> Yes, I'll test and review the change, and help where necessary. Thanks for
> pointing it out.
>
> -Alex
>
> On Wed, 15 Aug 2018, Michel Dänzer wrote:
>
> > On 2018-08-14 10:05
Thanks, Keith and Michel!
Yes, I'll test and review the change, and help where necessary. Thanks for
pointing it out.
-Alex
On Wed, 15 Aug 2018, Michel Dänzer wrote:
> On 2018-08-14 10:05 PM, Alex Goins wrote:
> > The purpose of rrCheckPixmapBounding() is to make sure that the fb is large
> >
On 2018-08-14 10:05 PM, Alex Goins wrote:
> The purpose of rrCheckPixmapBounding() is to make sure that the fb is large
> enough to accommodate the region scanned out by a GPU screen. Currently,
> however,
> it will actually shrink the fb if it's larger than it needs to be.
>
> This is a problem
Alex Goins writes:
> Instead, this change simply
> makes it so that rrCheckPixmapBounding() will only resize the fb to be larger
> than it already is, preventing it from stepping on prior requests to increase
> the size of the fb.
Seems like a fine plan to me.
Reviewed-by: Keith Packard
--
The purpose of rrCheckPixmapBounding() is to make sure that the fb is large
enough to accommodate the region scanned out by a GPU screen. Currently,
however,
it will actually shrink the fb if it's larger than it needs to be.
This is a problem when combining PRIME output slaving with arbitrary
