From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FedoA-0003cN-1F
	for qemu-devel@nongnu.org; Fri, 12 May 2006 16:00:18 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fedo7-0003bG-H4
	for qemu-devel@nongnu.org; Fri, 12 May 2006 16:00:16 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fedo7-0003b5-EL
	for qemu-devel@nongnu.org; Fri, 12 May 2006 16:00:15 -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 1Fedpv-0003Fx-1U
	for qemu-devel@nongnu.org; Fri, 12 May 2006 16:02:07 -0400
Date: Fri, 12 May 2006 15:00:13 -0500
From: Troy Benjegerdes <hozer@hozed.org>
Message-ID: <20060512200013.GP15855@narn.hozed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [Qemu-devel] VNC cross-endian failures
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

The VNC protocol says the server is is supposed to send the data in the
format the client wants, however the current implementation sends vnc
data in the server native format.

What is the best way to fix this? Using -bgr is not right since that
will mess up same-endian clients.