From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Mario_Limonciello@dell.com, dvhart@infradead.org,
gabriele.mzt@gmail.com, luto@kernel.org, alex.hung@canonical.com,
kernel@kempniu.pl, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling
Date: Tue, 21 Jun 2016 19:33:27 +0100 [thread overview]
Message-ID: <20160621183327.GA18073@srcf.ucam.org> (raw)
In-Reply-To: <201606212029.28029@pali>
On Tue, Jun 21, 2016 at 08:29:27PM +0200, Pali Rohár wrote:
> Is there some way to disable this insane nonsense activity of BIOS,
> firmware or whatever it is doing in HW to send *one* key scancode when
> pressing *one* key?
There's certainly no generic cross-vendor way to do so, so userspace has
to deal in any case.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2016-06-21 19:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 19:49 [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling Pali Rohár
2016-06-15 19:49 ` [PATCH v3 1/4] dell-wmi: Ignore WMI event code 0xe045 Pali Rohár
2016-06-15 19:49 ` [PATCH v3 2/4] dell-wmi: Sort WMI event codes and update comments Pali Rohár
2016-06-15 19:49 ` [PATCH v3 3/4] dell-wmi: Add information about other WMI event codes Pali Rohár
2016-06-15 19:49 ` [PATCH v3 4/4] dell-wmi: Generate one sparse keymap for all machines Pali Rohár
2016-06-16 3:19 ` [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling Darren Hart
2016-06-16 7:33 ` Pali Rohár
2016-06-16 23:01 ` Gabriele Mazzotta
2016-06-21 16:27 ` Darren Hart
2016-06-21 18:06 ` Darren Hart
2016-06-21 18:16 ` Mario_Limonciello
2016-06-21 18:29 ` Pali Rohár
2016-06-21 18:33 ` Matthew Garrett [this message]
2016-06-22 10:31 ` Pali Rohár
2016-06-21 18:37 ` Mario_Limonciello
2016-06-22 10:30 ` Pali Rohár
2016-06-22 13:20 ` Mario_Limonciello
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=20160621183327.GA18073@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Mario_Limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=dvhart@infradead.org \
--cc=gabriele.mzt@gmail.com \
--cc=kernel@kempniu.pl \
--cc=luto@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.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