Re: [PATCH xserver 2/2] modesetting: Fix reported size when using atomic modesetting

On Thu, 2018-03-29 at 09:16 +0100, Daniel Stone wrote: > On 29 March 2018 at 08:46, Olivier Fourdan wrote: > > Looks good to me *but* this is not sufficient because > > do_queue_flip_on_crtc() calls drmmode_crtc_set_fb() with (x=0,y=0) for any > > CRTC regardless of its

Re: [PATCH xserver 2/2] modesetting: Fix reported size when using atomic modesetting

On 29 March 2018 at 08:46, Olivier Fourdan wrote: > Looks good to me *but* this is not sufficient because > do_queue_flip_on_crtc() calls drmmode_crtc_set_fb() with (x=0,y=0) for any > CRTC regardless of its actual location... > > So, it also requires

Re: [PATCH xserver 2/2] modesetting: Fix reported size when using atomic modesetting

On Thu, Mar 29, 2018 at 7:07 AM, Louis-Francis Ratté-Boulianne < l...@collabora.com> wrote: > The framebuffer can include multiple CRTCs in multi-monitors > setup. So we shouldn't use the buffer size but the CRTC size > instead. Rotated displays are shadowed, so we don't need to > worry about it

[PATCH xserver 2/2] modesetting: Fix reported size when using atomic modesetting

The framebuffer can include multiple CRTCs in multi-monitors setup. So we shouldn't use the buffer size but the CRTC size instead. Rotated displays are shadowed, so we don't need to worry about it there. Signed-off-by: Louis-Francis Ratté-Boulianne ---