Re: [RFC PATCH v2 00/20] Monitor ID rework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Gerd,

On Thu, 2018-08-23 at 22:56 +0200, Gerd Hoffmann wrote:
>   Hi,
> 
> > 1. The logic used to switch something for something and when - You need
> > to define somehow you have this QXL device that is showing the boot in
> > client display 1 and then you start X and want to replace client
> > display 1 with X monitor 1. Then the user switches VTs and you need to
> > switch client display 1 back to QXL and so on.
> 
> I'd suggest to simply ignore this for now.

This described a hypothetical issue if we wanted to implement the
channel switching, which we don't, at this moment.

> Long-term there should be no need to have a separate QXL device for
> boot messages.

Interesting, why do you think so?

> cheers,
>   Gerd
> 
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux Virtualization]     [Linux Virtualization]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]