WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Paravirt framebuffer backend tools [2/5]

To: Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Paravirt framebuffer backend tools [2/5]
From: Laurent Vivier <Laurent.Vivier@xxxxxxxx>
Date: Wed, 11 Oct 2006 17:21:00 +0200
Cc: Jeremy Katz <katzj@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, sos22@xxxxxxxxxxxxx
Delivery-date: Wed, 11 Oct 2006 08:21:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <452D0B2B.8010004@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Bull S.A.S.
References: <20060904090150.GC4812@xxxxxxxxx> <44FC224D.3090300@xxxxxxxx> <20060906091505.GD3257@xxxxxxxxx> <44FEB3DE.5070502@xxxxxxxx> <20060906171006.GA5306@xxxxxxxxx> <44FFCAC0.6060809@xxxxxxxx> <20060907083848.GA3078@xxxxxxxxx> <45016F8E.1030300@xxxxxxxxxxxxx> <20060908141248.GA6845@xxxxxxxxx> <45017CCF.9050707@xxxxxxxxxxxxx> <87psd4ul5c.fsf@xxxxxxxxxxxxxxxxx> <1160499227.5951.35.camel@xxxxxxxxxxxxxxxxxxxxx> <87k637nero.fsf@xxxxxxxxxxxxxxxxx> <452D0B2B.8010004@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.2 (X11/20060420)
Gerd Hoffmann wrote:
>   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.
> 
> <unimportant side node>
>   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
> 

So, perhaps the patch I post sometime ago on this subject should be useful ?

Laurent
-- 
                Laurent.Vivier@xxxxxxxx
+----- "Any sufficiently advanced technology is ----+
| indistinguishable from magic." - Arthur C. Clarke |

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel