Hi,
> first output/display:
> spice_qxl_set_device_info(instance1, path1, 0, 1);
> second:
> spice_qxl_set_device_info(instance2, path1, 1, 1);
> third:
> spice_qxl_set_device_info(instance3, path1, 2, 1);
That is a much better example IMHO.
cheers,
Gerd
> On Thu, Nov 08, 2018 at 11:05:10AM +0100, Lukáš Hrázký wrote:
> > Hello,
> >
> > On Thu, 2018-11-08 at 07:49 +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > + * The device_display_id_{start,count} denotes the sequence of device
> > > > display
> > > > + * IDs that map to the zero-based
On Thu, Nov 08, 2018 at 11:05:10AM +0100, Lukáš Hrázký wrote:
> Hello,
>
> On Thu, 2018-11-08 at 07:49 +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > + * The device_display_id_{start,count} denotes the sequence of device
> > > display
> > > + * IDs that map to the zero-based sequence of
Hello,
On Thu, 2018-11-08 at 07:49 +0100, Gerd Hoffmann wrote:
> Hi,
>
> > + * The device_display_id_{start,count} denotes the sequence of device
> > display
> > + * IDs that map to the zero-based sequence of monitor IDs provided by
> > monitors
> > + * config on this interface. For example
Hi,
> + * The device_display_id_{start,count} denotes the sequence of device display
> + * IDs that map to the zero-based sequence of monitor IDs provided by
> monitors
> + * config on this interface. For example with device_display_id_start = 2 and
> + * device_display_id_count = 3 you get
Adds a function to let QEMU provide information to identify graphics
devices and their monitors in the guest. The function
(spice_qxl_set_device_info) sets the device address (e.g. a PCI path)
and monitor ID -> device display ID mapping of displays exposed by given
QXL interface.
Signed-off-by:
