All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Maxim Gorbachyov <maxim.gorbachyov@gmail.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Access to raw keycodes in xen domU
Date: Thu, 14 Aug 2008 16:21:51 +0100	[thread overview]
Message-ID: <20080814152151.GU4590@implementation.uk.xensource.com> (raw)
In-Reply-To: <291f35090808140809lf43f6bfv5925f780af076f08@mail.gmail.com>

Maxim Gorbachyov, le Thu 14 Aug 2008 19:09:55 +0400, a écrit :
> On Thu, Aug 14, 2008 at 6:39 PM, Ian Jackson <Ian.Jackson@eu.citrix.com> 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.
> 
> 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

  reply	other threads:[~2008-08-14 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 13:58 Access to raw keycodes in xen domU Maxim Gorbachyov
2008-08-14 14:07 ` Keir Fraser
2008-08-14 14:39   ` Ian Jackson
2008-08-14 15:09     ` Maxim Gorbachyov
2008-08-14 15:21       ` Samuel Thibault [this message]
2008-08-25  9:26         ` Maxim Gorbachyov
2008-08-14 14:10 ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080814152151.GU4590@implementation.uk.xensource.com \
    --to=samuel.thibault@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=maxim.gorbachyov@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.