From: Steven Smith <sos22-xen@srcf.ucam.org>
To: Anthony Liguori <aliguori@cs.utexas.edu>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Laurent Vivier <Laurent.Vivier@bull.net>,
Markus Armbruster <armbru@redhat.com>,
iap10@cl.cam.ac.uk, sos22@srcf.ucam.org,
Jeremy Katz <katzj@redhat.com>
Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5]
Date: Sun, 10 Sep 2006 11:40:21 +0100 [thread overview]
Message-ID: <20060910104021.GC1874@cam.ac.uk> (raw)
In-Reply-To: <45016F8E.1030300@cs.utexas.edu>
[-- Attachment #1.1: Type: text/plain, Size: 695 bytes --]
> >First: I now agree with you that scancodes are a better choice than
> >keysyms, and that I was wrong initially.
> The problem with scancodes is that you cannot always get scancodes from
> the viewer. You can get scancodes from SDL but you can only get keysyms
> from VNC. We would have to map VNC keysyms (which are just Xk keysyms)
> to scancodes?
Ian just pointed out that there's some code in rdesktop to do just
that. xkeymap.c contains stuff to pull the keymap out of the X
server, parse it up, and then do keysym->scancode translation. Of
course, choosing a suitable keymap isn't entirely trivial, since the
server can't see what keymap the client's using.
Steven.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-09-10 10:40 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
2006-10-11 15:21 ` Laurent Vivier
2006-10-10 18:48 ` Steven Smith
2006-09-10 10:40 ` Steven Smith [this message]
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=20060910104021.GC1874@cam.ac.uk \
--to=sos22-xen@srcf.ucam.org \
--cc=Laurent.Vivier@bull.net \
--cc=aliguori@cs.utexas.edu \
--cc=armbru@redhat.com \
--cc=iap10@cl.cam.ac.uk \
--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.