From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KH4F0-0001NI-7p for qemu-devel@nongnu.org; Thu, 10 Jul 2008 18:03:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KH4Ey-0001MA-Nn for qemu-devel@nongnu.org; Thu, 10 Jul 2008 18:03:53 -0400 Received: from [199.232.76.173] (port=46358 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KH4Ey-0001M3-LE for qemu-devel@nongnu.org; Thu, 10 Jul 2008 18:03:52 -0400 Received: from py-out-1112.google.com ([64.233.166.180]:37392) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KH4Ey-0008Ji-3L for qemu-devel@nongnu.org; Thu, 10 Jul 2008 18:03:52 -0400 Received: by py-out-1112.google.com with SMTP id p76so1977783pyb.10 for ; Thu, 10 Jul 2008 15:03:49 -0700 (PDT) Message-ID: <4876872B.6080704@codemonkey.ws> Date: Thu, 10 Jul 2008 17:03:23 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Bug in SDL key event processing References: <20080709235516.GM4889@implementation> <48755320.5090707@dbservice.com> <48757FB8.8010400@codemonkey.ws> <4875C0B6.2060302@dbservice.com> <4876101A.1080800@codemonkey.ws> <487611FC.5070500@dbservice.com> <487616BB.8020402@dbservice.com> <48761F31.4090909@codemonkey.ws> <48762C59.9010204@dbservice.com> <48766211.2090304@codemonkey.ws> <20080710215524.GB4579@implementation> In-Reply-To: <20080710215524.GB4579@implementation> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Samuel Thibault wrote: > Anthony Liguori, le Thu 10 Jul 2008 14:25:05 -0500, a écrit : > >>> Keep in mind that using '-k' completely changes the semantics of the >>> keyboard. I'm using the colemak layout, so my top row is: qwfpg. For >>> the sake of simplicity, assume that the guest uses the standard en-us >>> layout. >>> >> Then you would need to add a colemak translation table if you wanted >> that to be reflected in the guest. However, if you use -k en-us and use >> en-us in the guest, it should just work for you. >> > > That won't for the shifted characters. Let's take for instance azerty, > which has the numbers in the shifted position instead of the direct > position. Typing shift+1 will produce a 1 keysym, which will indeed be > converted to the correct scancode, but shift will be simulated too, and > thus produce in the guest '!'... Yes, unfortunately, I don't see a great way to fix that :-/ You basically have to have the guest also set up to use azerty. > There is no other correct than properly > reverse-engineering the keysyms we get into a positional keycode, and > then convert to PS2 scancode, and let the guest use its keymaps.. > Which is what we're trying to do. The issue is that the keysyms=>positional keycode mapping is 1->many. That's what the -k mappings are selecting. Regards, Anthony Liguroi > Samuel > > >