From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5] Date: Wed, 11 Oct 2006 17:18:03 +0200 Message-ID: <452D0B2B.8010004@suse.de> References: <20060904090150.GC4812@cam.ac.uk> <44FC224D.3090300@bull.net> <20060906091505.GD3257@cam.ac.uk> <44FEB3DE.5070502@bull.net> <20060906171006.GA5306@cam.ac.uk> <44FFCAC0.6060809@bull.net> <20060907083848.GA3078@cam.ac.uk> <45016F8E.1030300@cs.utexas.edu> <20060908141248.GA6845@cam.ac.uk> <45017CCF.9050707@cs.utexas.edu> <87psd4ul5c.fsf@pike.pond.sub.org> <1160499227.5951.35.camel@sisko.scot.redhat.com> <87k637nero.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87k637nero.fsf@pike.pond.sub.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Markus Armbruster Cc: "xen-devel@lists.xensource.com" , Jeremy Katz , sos22@srcf.ucam.org, Laurent Vivier , Anthony Liguori List-Id: xen-devel@lists.xenproject.org Hi, > (2) Simply use the host's raw keys. > > The guest needs to understand the host's raw keys, and map them if > they differ from its own idea of raw keys. At this time, the only > idea of raw keys in town is Linux keycodes, so no mapping is > necessary. > > Nice: simple & stupid. > > Unless I misunderstand Anthony, that's what rdesktop and qemu do. Well, there are some corner cases where you can't easily get the hosts raw keys. In that case qemu tries to translate the keysyms back to raw keycodes using the maps in /usr/share/qemu/keymaps. See also qemu manpage, "-k" switch. But, yes, using linux keycodes as wire encoding IMHO is the way to go. cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg