On 2022/01/11 17:23, Marc-André Lureau wrote:
Hi Akihiko
On Tue, Jan 11, 2022 at 7:30 AM Akihiko Odaki wrote:
Hi,
I found this brings an inconsistency and a flaw to scanout semantics and
think the inconsistency should be fixed or this should be reverted
before the next release comes up.
Hi Akihiko
On Tue, Jan 11, 2022 at 7:30 AM Akihiko Odaki wrote:
>
> Hi,
>
> I found this brings an inconsistency and a flaw to scanout semantics and
> think the inconsistency should be fixed or this should be reverted
> before the next release comes up.
>
> The inconsistency is in the handling of
Hi,
I found this brings an inconsistency and a flaw to scanout semantics and
think the inconsistency should be fixed or this should be reverted
before the next release comes up.
The inconsistency is in the handling of the console size. A guest
hardware (especially I'm looking at virtio-gpu-v
From: Marc-André Lureau
Add a new DisplayScanout structure to save the current scanout details.
This allows to attach later UI backends and set the scanout.
Introduce displaychangelistener_display_console() helper function to
handle the dpy_gfx_switch/gl_scanout() & dpy_gfx_update() calls.
Sign
