From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Qemu vnc color depth Date: Tue, 12 Feb 2008 08:56:32 -0600 Message-ID: <47B1B3A0.6080302@codemonkey.ws> References: <47B02F63.4010406@eu.citrix.com> <20080211145414.GA17784@redhat.com> <47B06763.2000406@eu.citrix.com> <20080211152933.GB17784@redhat.com> <47B06E2F.1030001@codemonkey.ws> <47B181C5.1040502@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47B181C5.1040502@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: xen-devel@lists.xensource.com, "Daniel P. Berrange" List-Id: xen-devel@lists.xenproject.org Stefano Stabellini wrote: > 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. 0x574D5669 The encoding number they use is 0x574D5669 and it is registered in the latest RFB spec. Regards, Anthony Liguori