From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35753 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OmSuR-0005JF-HT
	for qemu-devel@nongnu.org; Fri, 20 Aug 2010 10:49:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1OmSuN-00061E-Dz
	for qemu-devel@nongnu.org; Fri, 20 Aug 2010 10:49:28 -0400
Received: from mx1.redhat.com ([209.132.183.28]:15693)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1OmSuN-00060z-6B
	for qemu-devel@nongnu.org; Fri, 20 Aug 2010 10:49:27 -0400
Message-ID: <4C6E95F0.2060404@redhat.com>
Date: Fri, 20 Aug 2010 16:49:20 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 6/9] spice: add keyboard
References: <1282221625-29501-1-git-send-email-kraxel@redhat.com>
	<1282221625-29501-7-git-send-email-kraxel@redhat.com>
	<4C6D3E92.8060604@codemonkey.ws> <4C6E766A.2000809@redhat.com>
	<4C6E809D.9050408@codemonkey.ws> <4C6E89A4.2060906@redhat.com>
	<20100820141509.GL16437@redhat.com>
In-Reply-To: <20100820141509.GL16437@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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.nongnu.org/archive/html/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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org

   Hi,

> AT (well XT) keycodes aren't that bad a choice, at least if you go for the
> extended mapping used by the Linux keyboard driver.

Hmm, as far I know those extended mappings are not standardized.  Uses 
linux this just as internal representation?  Or can you actually feed a 
linux guest with them and expect it to work?  How about non-linux guests?

When using it as wire protocol guest compatibility doesn't matter that 
much though ...

> The master mapping is from Linux keycodes to other sets:
>
>    http://git.gnome.org/browse/gtk-vnc/tree/src/keymaps.csv
>
> And a tool that can then create you C arrays for mapping between
> arbitrary keycode sets in any direction (potentially lossy
> of course, depending on choice of keycode sets):
>
>    http://git.gnome.org/browse/gtk-vnc/tree/src/keymap-gen.pl

Nice.

cheers,
   Gerd