From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Access to raw keycodes in xen domU Date: Thu, 14 Aug 2008 16:21:51 +0100 Message-ID: <20080814152151.GU4590@implementation.uk.xensource.com> References: <291f35090808140658i41ef68acx50ebb15e12f237be@mail.gmail.com> <18596.17306.166292.733162@mariner.uk.xensource.com> <291f35090808140809lf43f6bfv5925f780af076f08@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <291f35090808140809lf43f6bfv5925f780af076f08@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Maxim Gorbachyov Cc: xen-devel@lists.xensource.com, Ian Jackson List-Id: xen-devel@lists.xenproject.org Maxim Gorbachyov, le Thu 14 Aug 2008 19:09:55 +0400, a =E9crit : > On Thu, Aug 14, 2008 at 6:39 PM, Ian Jackson wrote: > > There was a discussion of some of this area on qemu-devel recently. > > Sadly it's a bit of a mess (in part, inevitably), and it may be > > difficult to do exactly what you want. > > > > If you tell us why you want the raw keycodes - what overall result > > you're trying to achieve etc. - then we may be able to suggest some > > kind of answer. >=20 > There is a binary which sets K_RAW and expects certain codes from > keyboard to work. It's kind of dinosaur, but we have to use it.. Well, the problem is that since the xen console can be accessed e.g. through ssh, there is really no way to properly return keycodes. If you can not use pvfb, The only half-sane way I see is that you hardcode the translation that your dinosaur binary expects according to the keyboard layout you are using and use that patched version. I really don't see how that could ever fit generically in xen console. Samuel