From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [RFC] keymap support for PVFB Date: Thu, 11 Jan 2007 10:09:04 +0100 Message-ID: <45A5FEB0.4010606@suse.de> References: <009d01c72a36$405dd400$d9b2220a@VF05186P> <87r6u2my8s.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: <87r6u2my8s.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, > In the longer run, I'd like to replace LibVNCServer by code from QEMU > alltogether. In the short run, working keymaps are quite welcome. Hmm, so this works by telling the vnc server side which keymap the client is using I guess? 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. Problem with that is that I don't have keysyms to send for keys which are not present on a us keyboard. That affects the 102th/105th key on i18n keyboards ("<>|" key on a german keyboard), and I think japanese keyboards have a few more keys which are just dead ... cheers, Gerd -- Gerd Hoffmann