Hi
On Tue, Jun 14, 2016 at 10:46 AM, Christophe Fergeau
wrote:
>> Imho, the fix should be on server or guest/driver side, it shouldn't
>> use a display monitor config with a scanout offset if there is none to
>> be applied by the client.
>
> Regarding fixing this on the
On Mon, Jun 13, 2016 at 07:09:29PM +0200, Marc-André Lureau wrote:
> My understanding is that there is some confusing between monitor
> configuration position (the monitor config on main channel), and the
> scanout/primary position (the monitor config on display channel).
>
> Imho, the fix should
Hey,
On Mon, Jun 13, 2016 at 07:09:29PM +0200, Marc-André Lureau wrote:
> >> On Thu, Jun 18, 2015 at 07:14:13PM -0400, sstut...@redhat.com wrote:
> >> > From: Sandy Stutsman
> >> >
> >> > Each monitor on a Windows guest is represented as a separate,
> >> > single-headed
>
Hi
On Mon, Jun 22, 2015 at 3:15 PM, Christophe Fergeau wrote:
> On Mon, Jun 22, 2015 at 03:03:24PM +0200, Christophe Fergeau wrote:
>> On Thu, Jun 18, 2015 at 07:14:13PM -0400, sstut...@redhat.com wrote:
>> > From: Sandy Stutsman
>> >
>> > Each monitor
On Thu, Jun 18, 2015 at 07:14:13PM -0400, sstut...@redhat.com wrote:
From: Sandy Stutsman sstut...@redhat.com
Each monitor on a Windows guest is represented as a separate, single-headed
device with its own framebuffer. When there are multiple monitors, all
monitors but one will have a
On Mon, Jun 22, 2015 at 03:03:24PM +0200, Christophe Fergeau wrote:
On Thu, Jun 18, 2015 at 07:14:13PM -0400, sstut...@redhat.com wrote:
From: Sandy Stutsman sstut...@redhat.com
Each monitor on a Windows guest is represented as a separate, single-headed
device with its own framebuffer.
From: Sandy Stutsman sstut...@redhat.com
Each monitor on a Windows guest is represented as a separate, single-headed
device with its own framebuffer. When there are multiple monitors, all
monitors but one will have a non-zero xy config position. But even in
these cases the whole area