All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: xen-devel@lists.xensource.com,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: Qemu vnc color depth
Date: Tue, 12 Feb 2008 11:23:49 +0000	[thread overview]
Message-ID: <47B181C5.1040502@eu.citrix.com> (raw)
In-Reply-To: <47B06E2F.1030001@codemonkey.ws>

Anthony Liguori wrote:
> We can use the existing space for gtk-vnc although VMware actually 
> already has an extension to support server initiated pixel format 
> changes.  See http://wiki.multimedia.cx/index.php?title=VMNC
> 
> The extension is VMVi (display mode change).  I would much rather just 
> implement that in QEMU and in gtk-vnc.
> 
> This would also count in my mind as finally fixing SetPixelFormat since 
> a client could rely on getting the DisplayModeChange message before the 
> server starts using the new pixel format.

I have given a look at WMVi: the message format is fine as it is 
identical to the PIXEL_FORMAT part of the ServerInit message.
However I couldn't see the pseudo encoding number or any client side 
implementation.
I think they used WMVi as part of their format to record AVI videos and 
not as a VNC protocol extension.

We can use the message format they proposed, but we need also a proper 
pseudo encoding number.
Then we'll send "DisplayModeChange" messages as 1 rectangle framebuffer 
updates.

  reply	other threads:[~2008-02-12 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 11:20 Qemu vnc color depth Stefano Stabellini
2008-02-11 11:31 ` James Harper
2008-02-11 11:37   ` Stefano Stabellini
2008-02-11 14:54 ` Daniel P. Berrange
2008-02-11 15:18   ` Stefano Stabellini
2008-02-11 15:29     ` Daniel P. Berrange
2008-02-11 15:47       ` Anthony Liguori
2008-02-12 11:23         ` Stefano Stabellini [this message]
2008-02-12 14:56           ` Anthony Liguori
2008-02-12 15:10             ` Stefano Stabellini

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=47B181C5.1040502@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=anthony@codemonkey.ws \
    --cc=berrange@redhat.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.