From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-input@vger.kernel.org
Subject: Extended scancodes and input filtering
Date: Mon, 17 May 2010 16:58:11 +0100 [thread overview]
Message-ID: <20100517155811.GA27311@srcf.ucam.org> (raw)
If an i8042 input filter returns false then the byte will be dropped.
This is unfortunate if it's the second byte of an extended scancode.
We'd like to be able to drop some events if a platform driver consumes
them, but right now it looks like bad things will happen in that case.
The filtering is done at the i8042 layer, which has no knowledge of
extended scancodes - and teaching it would look like a layering
violation.
The simplest approach would seem to be to pass the data byte by
reference rather than by value and then let the filter code change it to
something that would then be an invalid scancode, but that presupposes
that there's such a thing as an invalid scancode. Is there anything
suitable here?
--
Matthew Garrett | mjg59@srcf.ucam.org
reply other threads:[~2010-05-17 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100517155811.GA27311@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).