qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change
Date: Thu, 20 Nov 2008 19:02:26 +0000	[thread overview]
Message-ID: <4925B442.8050206@eu.citrix.com> (raw)
In-Reply-To: <200811201839.24213.paul@codesourcery.com>

Paul Brook wrote:

> On Thursday 20 November 2008, Stefano Stabellini wrote:
>> Paul Brook wrote:
>>> No, I mean what happens when I have (for example) two emulated VGA
>>> devices, one displaying to SDL and the other to VNC? Or I want an
>>> intermediate later that composites multiple device outputs into a single
>>> host image.
>> If you want multiple device output you need multiple DisplayStates.
>> You need a DisplayState for each device output you want at the same time.
>> My patches do not make any harder to implement this scenario, actually
>> being the interface simpler it should be much simpler to handle this
>> case as well.
> 
> Maybe. We already have a per-display structure (QEMUConsole). IIUC you're 
> using DisplayState (which IMHO should be per host side display) to store per 
> device information.
> 

The assumption I made in my patches is the following:
DisplayState is the interface between multiple backend (for example vga
and serial, each of them has its own QEMUConsole) and multiple host-side
display (vnc.c and sdl.c).

If you want to see different things at the same time on multiple display
you need multiple DisplayState.
Then you can have, for example, two vga, each of them connected to an
sdl windows and a vnc server (2 windows and 2 servers total).

  parent reply	other threads:[~2008-11-20 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 16:58 [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change Stefano Stabellini
     [not found] ` <200811201737.00254.paul@codesourcery.com>
2008-11-20 17:48   ` Stefano Stabellini
     [not found]     ` <200811201823.22742.paul@codesourcery.com>
2008-11-20 18:36       ` Stefano Stabellini
     [not found]         ` <200811201839.24213.paul@codesourcery.com>
2008-11-20 19:02           ` Stefano Stabellini [this message]
     [not found]     ` <200811211040.44235.paul@codesourcery.com>
2008-11-21 11:31       ` Stefano Stabellini
2008-11-20 18:58 ` Anthony Liguori
     [not found]   ` <200811202246.18906.paul@codesourcery.com>
2008-11-20 23:06     ` Anthony Liguori
2008-11-20 23:07     ` Anthony Liguori
2008-11-20 23:16     ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4925B442.8050206@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).