From: Gerd Hoffmann <kraxel@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jeremy Katz <katzj@redhat.com>,
sos22@srcf.ucam.org, Laurent Vivier <Laurent.Vivier@bull.net>,
Anthony Liguori <aliguori@cs.utexas.edu>
Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5]
Date: Wed, 11 Oct 2006 17:18:03 +0200 [thread overview]
Message-ID: <452D0B2B.8010004@suse.de> (raw)
In-Reply-To: <87k637nero.fsf@pike.pond.sub.org>
Hi,
> (2) Simply use the host's raw keys.
>
> The guest needs to understand the host's raw keys, and map them if
> they differ from its own idea of raw keys. At this time, the only
> idea of raw keys in town is Linux keycodes, so no mapping is
> necessary.
>
> Nice: simple & stupid.
>
> Unless I misunderstand Anthony, that's what rdesktop and qemu do.
<unimportant side node>
Well, there are some corner cases where you can't easily get the hosts
raw keys. In that case qemu tries to translate the keysyms back to
raw keycodes using the maps in /usr/share/qemu/keymaps. See also qemu
manpage, "-k" switch.
</>
But, yes, using linux keycodes as wire encoding IMHO is the way to go.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-10-11 15:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 19:58 [PATCH] Paravirt framebuffer backend tools [2/5] Jeremy Katz
2006-09-04 9:01 ` Steven Smith
2006-09-04 12:55 ` Laurent Vivier
2006-09-06 9:15 ` Steven Smith
2006-09-06 11:41 ` Laurent Vivier
2006-09-06 17:10 ` Steven Smith
2006-09-06 17:50 ` Gerd Hoffmann
2006-09-07 7:32 ` Laurent Vivier
2006-09-07 7:50 ` Steven Smith
2006-09-07 7:31 ` Laurent Vivier
2006-09-07 8:38 ` Steven Smith
2006-09-07 9:31 ` Laurent Vivier
2006-09-07 9:55 ` Steven Smith
2006-09-07 12:03 ` Laurent Vivier
2006-09-08 13:26 ` Anthony Liguori
2006-09-08 14:00 ` Laurent Vivier
2006-09-08 14:12 ` Steven Smith
2006-09-08 14:23 ` Anthony Liguori
2006-10-07 16:48 ` Markus Armbruster
2006-10-10 16:53 ` Stephen C. Tweedie
2006-10-10 17:46 ` Anthony Liguori
2006-10-10 17:46 ` Anthony Liguori
2006-10-11 13:49 ` Markus Armbruster
2006-10-11 15:18 ` Gerd Hoffmann [this message]
2006-10-11 15:21 ` Laurent Vivier
2006-10-10 18:48 ` Steven Smith
2006-09-10 10:40 ` Steven Smith
2006-09-10 13:05 ` Anthony Liguori
2006-09-05 16:11 ` Jeremy Katz
2006-09-05 16:57 ` Anthony Liguori
2006-09-06 9:14 ` Steven Smith
2006-09-06 9:13 ` Steven Smith
2006-09-30 8:51 ` Markus Armbruster
2006-10-02 9:01 ` Steven Smith
2006-10-04 14:04 ` Markus Armbruster
2006-10-04 14:20 ` Daniel P. Berrange
2006-10-04 14:57 ` Anthony Liguori
2006-10-05 18:41 ` Steven Smith
2006-10-05 18:33 ` Steven Smith
2006-10-06 14:10 ` Markus Armbruster
2006-10-07 9:42 ` Steven Smith
2006-09-12 18:55 ` Daniel P. Berrange
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=452D0B2B.8010004@suse.de \
--to=kraxel@suse.de \
--cc=Laurent.Vivier@bull.net \
--cc=aliguori@cs.utexas.edu \
--cc=armbru@redhat.com \
--cc=katzj@redhat.com \
--cc=sos22@srcf.ucam.org \
--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.