From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pipe key broken on US keyboards
Date: Fri, 17 Aug 2018 15:44:21 +0100 [thread overview]
Message-ID: <20180817144421.GS11124@redhat.com> (raw)
In-Reply-To: <e88687b0-f116-e6eb-0432-12e38ecece2f@ubuntu.com>
On Fri, Aug 17, 2018 at 10:36:14AM -0400, Phillip Susi wrote:
> I've been reading up here:
> http://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html
>
> And man, what a mess keyboards are! Worse than floppy controllers.
> According to that site, the scan code for \ should be 0x2b, so why does
> xev say the keycode is 51? Is keycode something else entirely from scan
> codes and keysyms? If so how can I see the scan code?
0x2b is 43 in hex.
xev reports the Xorg scancode, which is the same as the XT/AT-set1
scancodes, with an offset of 8 added
IOW, 51 from xev does actually match 0x2b from XT scancode set
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-08-17 14:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 17:11 [Qemu-devel] Pipe key broken on US keyboards Phillip Susi
2018-08-16 17:27 ` Daniel P. Berrangé
2018-08-16 19:44 ` Phillip Susi
2018-08-17 8:56 ` Daniel P. Berrangé
2018-08-17 12:44 ` Phillip Susi
2018-08-17 12:58 ` Daniel P. Berrangé
2018-08-17 13:10 ` Phillip Susi
2018-08-17 13:12 ` Daniel P. Berrangé
2018-08-17 13:23 ` Phillip Susi
2018-08-17 14:36 ` Phillip Susi
2018-08-17 14:44 ` Daniel P. Berrangé [this message]
2018-08-17 14:55 ` Phillip Susi
2018-08-17 15:06 ` Daniel P. Berrangé
2018-08-17 12:56 ` Daniel P. Berrangé
2018-08-17 15:05 ` Daniel P. Berrangé
2018-08-17 15:16 ` Phillip Susi
2018-08-17 15:51 ` Daniel P. Berrangé
2018-08-21 19:35 ` Phillip Susi
2018-08-20 8:43 ` Gerd Hoffmann
2018-08-20 14:23 ` Phillip Susi
2018-08-20 15:07 ` Christian Ehrhardt
2018-08-20 19:51 ` Phillip Susi
2018-08-20 20:04 ` Christian Ehrhardt
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=20180817144421.GS11124@redhat.com \
--to=berrange@redhat.com \
--cc=psusi@ubuntu.com \
--cc=qemu-devel@nongnu.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 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.