qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Moving keymaps -> pc-bios/keymaps
Date: Thu, 28 May 2009 10:29:57 +0100	[thread overview]
Message-ID: <20090528092957.GA24488@redhat.com> (raw)
In-Reply-To: <20090528084448.GW5809@const.bordeaux.inria.fr>

On Thu, May 28, 2009 at 10:44:48AM +0200, Samuel Thibault wrote:
> Anthony Liguori, le Thu 28 May 2009 03:37:44 -0500, a écrit :
> > Samuel Thibault wrote:
> > > Could qemu perhaps just use xkb data?
> > 
> > We could but we would probably want to keep it in the tree for Windows
> > and non-X11 targets.
> 
> Yes, of course.  My idea was mostly to get keymaps for free :)

For VNC at least you're better off getting a VNC client that supports
the hardware scancode extension[1], avoiding the need for any of this
horrible keymap conversion in QEMU itself, leaving it entirely to the
guest OS where xkb (or equiv) is indeed used. Not sure what SDL does...

Regards,
Daniel

[1] eg gtk-vnc as found in vinagre, virt-manager, virt-viewer
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-05-28  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  8:15 [Qemu-devel] Moving keymaps -> pc-bios/keymaps Anthony Liguori
2009-05-28  8:32 ` Samuel Thibault
2009-05-28  8:37   ` Anthony Liguori
2009-05-28  8:44     ` Samuel Thibault
2009-05-28  9:29       ` Daniel P. Berrange [this message]
2009-05-28  9:31 ` Stefan Weil
2009-05-28  9:42   ` Anthony Liguori
2009-05-28 12:59   ` Paul Brook
2009-05-30 11:30     ` Stuart Brady
2009-05-30 12:15       ` Stuart Brady

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=20090528092957.GA24488@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@gnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).