qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change
Date: Thu, 20 Nov 2008 17:16:47 -0600	[thread overview]
Message-ID: <4925EFDF.4090709@codemonkey.ws> (raw)
In-Reply-To: <200811202246.18906.paul@codesourcery.com>

Paul Brook wrote:
>> There are really two parts to this patch.  One part is a completely
>> mechanical conversion of things like ds->linesize to
>> ds->surface->linesize.  The second is the guys of the API change.
>>
>> If you introduce accessors to access things like linesize from
>> DisplayState, so something like:
>>
>> int ds_get_linesize(DisplayState *ds) {
>>      return ds->linesize;
>> }
>>     
>
> I think this sort of thing should be going via the console structures.
> i.e. vga emulation deals entirely with a QEMUConsole.  sdl/vnc deal entirely 
> with a DisplayState, and qemu mediates in between.
>   

BTW, I really like the idea of just using DisplayState because it 
implies that you could stack these things in multiple orders.  For 
instance, you may want to have a DisplayState that took two 
DisplayStates, and produced a tiled image (think side-by-side VGA 
displays).  You may want to take that DisplayState and combine it with a 
DisplayState for serial/monitor/parallel so that you can switch by the 
side-by-side VGA display and the other consoles.

Using the same structure here gives you lots of flexibility in how you 
stack these things.

Regards,

Anthony Liguori

> Paul
>   

      parent reply	other threads:[~2008-11-20 23:16 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
     [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 [this message]

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=4925EFDF.4090709@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).