From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [RFC] keymap support for PVFB Date: Fri, 12 Jan 2007 09:15:21 +0100 Message-ID: <45A74399.6080401@suse.de> References: <009d01c72a36$405dd400$d9b2220a@VF05186P> <87r6u2my8s.fsf@pike.pond.sub.org> <45A5FEB0.4010606@suse.de> <87hcuxh2lk.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: <87hcuxh2lk.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, Junko Ichino List-Id: xen-devel@lists.xenproject.org Hi, >> I've tried to tackle the same issue by hacking the vnc client side to >> send us keysyms no matter what the local keyboard mapping is. So I can >> have any keyboard map loaded on the host, qemu-dm/vncfb sees us keysyms >> nevertheless and passes the correct scancodes to the guest OS. > > You mean scan codes, don't you? Key symbols are the XK_a and so > forth. No, keysyms. This is what the vnc protocol uses, so there is no way around that, unfortunaly. It takes the X11 keycodes and translates these to us keymap keysyms using a buildin table, then sends them. So for the server side (from vnc protocol view, i.e. qemu-dm or vnc-fb) it looks like a vnc client with us keyboard. > Passing scan codes in addition to key symbols makes sense. Does the vnc protocol allow that? I don't think so :-( > Would you mind sharing your code when it's ready? http://www.suse.de/~kraxel/xen/, the vnc client in the "xenwatch" package. cheers, Gerd -- Gerd Hoffmann