From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Fg2Tx-00035y-AP
	for qemu-devel@nongnu.org; Tue, 16 May 2006 12:33:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fg2Tv-00035f-IJ
	for qemu-devel@nongnu.org; Tue, 16 May 2006 12:33:11 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fg2Tv-00035c-CM
	for qemu-devel@nongnu.org; Tue, 16 May 2006 12:33:11 -0400
Received: from [209.234.73.39] (helo=narn.hozed.org)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fg2Wb-0003yl-5n
	for qemu-devel@nongnu.org; Tue, 16 May 2006 12:35:57 -0400
Date: Tue, 16 May 2006 11:33:09 -0500
From: Troy Benjegerdes <hozer@hozed.org>
Subject: Re: [Qemu-devel] qemu vnc.c vnchextile.h
Message-ID: <20060516163309.GU15855@narn.hozed.org>
References: <E1FfL4I-0003wK-0G@savannah.gnu.org>
	<20060516152657.GT15855@narn.hozed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
In-Reply-To: <20060516152657.GT15855@narn.hozed.org>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> > Modified files:
> > 	.              : vnc.c vnchextile.h 
> > 
> > Log message:
> > 	support for all VNC pixel formats
> 
> Chicken of the vnc on MacOS X 
> 
> http://sourceforge.net/projects/cotvnc/
> 
> seems to have some issues with hextile encoding with a linux-x86-64 host
> system running qemu. Xvncviewer on a big-endian PPC system works just
> find though.

I have ethereal output from this, although it makes little sense since
there does not seem to be a decent VNC protocol dissector available.

Please contact me directly if you enjoy wading through VNC logs..