From: Phillip Susi <phill@thesusis.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: xen-devel@lists.xenproject.org, linux-input@vger.kernel.org
Subject: Re: Xen Virtual Keyboard modalias breaking uevents
Date: Fri, 30 Apr 2021 09:16:57 -0400 [thread overview]
Message-ID: <87bl9vaoph.fsf@vps.thesusis.net> (raw)
In-Reply-To: <YIszOwADJ8jdBov8@google.com>
Dmitry Torokhov writes:
> I don't know why Xen keyboard exports that many keycodes ;) In general,
> my recommendation is to mirror the physical device when possible, and
> instantiate several devices so there is 1:1 relationship between virtual
> and physical devices.
I'm still trying to wrap my head around why keys are even declared in
the first place. PS/2 ports have no idea what keys are on the keyboard
plugged into them, so I guess they don't declare any? And that doesn't
stop them from emitting any of the scan codes, so what is the use in
declaring them in the first place?
A lot of "interesting" buttons don't seem very interesting to me, such
as left and right parenthesis. Is a user space mail program really
going to bypass X11/wayland and open input devices directly to look for
someone to press the "send mail" key? Even if it did, why would it only
want to open a keyboard that advertises that it has such a key instead
of listening to all keyboards? Even if all USB keyboards report all of
their special keys, the fact that you could still have a PS/2 keyboard
that has a "send mail" key on it means that the reporting function can
not be relied on and so you just have to listen on all keyboards anyhow.
I guess as long as not reporting keys doesn't stop you from using them,
then the Xen Virtual Keyboard driver should just report none, like the
PS/2 keyboard driver.
next prev parent reply other threads:[~2021-04-30 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 19:08 Xen Virtual Keyboard modalias breaking uevents Phillip Susi
2021-04-29 20:10 ` Phillip Susi
2021-04-29 22:29 ` Dmitry Torokhov
2021-04-30 0:11 ` Phillip Susi
2021-04-30 0:35 ` Dmitry Torokhov
2021-04-30 0:57 ` Phillip Susi
2021-04-30 13:16 ` Phillip Susi [this message]
2021-05-06 14:36 ` [PATCH] Xen Keyboard: don't advertise every key known to man Phillip Susi
2021-05-06 20:26 ` Dmitry Torokhov
2021-05-18 16:20 ` Phillip Susi
2021-05-18 17:13 ` Phillip Susi
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=87bl9vaoph.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.