qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: merge GGI support? [was: Re: [Qemu-devel] [RFC] CRIS target port]
Date: Wed, 3 Oct 2007 15:16:42 +0100	[thread overview]
Message-ID: <20071003141642.GB8342@redhat.com> (raw)
In-Reply-To: <4703A053.2000805@codemonkey.ws>

On Wed, Oct 03, 2007 at 08:59:47AM -0500, Anthony Liguori wrote:
> andrzej zaborowski wrote:
> >Hi,
> >
> >  
> >>If the only argument for adding GGI is so that you don't have to install
> >>libsdl, then does that mean that we should have an X11, fbdev, etc.
> >>backend for people who don't have GGI installed?
> >>    
> >
> >I think a GGI back-end would be useful.
> >
> >I wouldn't mind also having other back-ends even if SDL supports them
> >(e.g. there's an Xlib patch for qemu, it is very little code compared
> >to vnc.c which you could say duplicates code already present in
> >libraries). The situation is the same with audio backends: there's
> >oss, alsa and SDL which can do both oss and alsa but works poorly.
> >
> >Unrelated to this discussion on slow links VNC is much more usable
> >with the Xlib patch and Xvnc than through the built-in VNC (I think it
> >makes a better decision on what format to use based on the connection
> >speed).
> 
> It's probably just the lack of a compressed encoding.

There are various optimizations to the VNC server in QEMU Uthat the
Xen project did in their fork. On my infinite todo list is an note to
take a look at these & see if its worth posting them here for merge.
At least one of the changes was to reduce the number of FB updates 
sent to the client under some circumstances.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-10-03 14:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 10:57 [Qemu-devel] [RFC] CRIS target port Edgar E. Iglesias
2007-10-02 12:02 ` Johannes Schindelin
2007-10-02 13:40   ` Edgar E. Iglesias
2007-10-02 16:42   ` merge GGI support? [was: Re: [Qemu-devel] [RFC] CRIS target port] Bernhard Fischer
2007-10-02 17:32     ` Johannes Schindelin
2007-10-02 17:56       ` Bernhard Fischer
2007-10-02 18:36     ` Thiemo Seufer
2007-10-02 19:29       ` Bernhard Fischer
2007-10-02 20:15         ` Bernhard Fischer
2007-10-02 18:45     ` Anthony Liguori
2007-10-02 19:21       ` Bernhard Fischer
2007-10-02 20:09         ` Anthony Liguori
2007-10-02 20:24           ` Avi Kivity
2007-10-02 20:32             ` Anthony Liguori
2007-10-02 20:30           ` Bernhard Fischer
2007-10-02 20:38             ` Anthony Liguori
2007-10-03 12:16               ` andrzej zaborowski
2007-10-03 13:59                 ` Anthony Liguori
2007-10-03 14:16                   ` Daniel P. Berrange [this message]
2007-10-02 20:28       ` Johannes Schindelin
2007-10-02 17:00 ` [Qemu-devel] [RFC] CRIS target port Thiemo Seufer

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=20071003141642.GB8342@redhat.com \
    --to=berrange@redhat.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).