From: David Herrmann <dh.herrmann@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
Adam Goode <adam@spicenitz.org>,
Fredrik Hallenberg <megahallon@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] HID: input: fix confusion on conflicting mappings
Date: Tue, 6 Jan 2015 22:29:37 +0100 [thread overview]
Message-ID: <CANq1E4TYhDzpLofxCr05hvHJMAvtMHEM210ALsB_UOi2=4c7kQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1501062218200.25732@pobox.suse.cz>
Hi
On Tue, Jan 6, 2015 at 10:19 PM, Jiri Kosina <jkosina@suse.cz> wrote:
> On Mon, 29 Dec 2014, David Herrmann wrote:
>
>> On an PC-101/103/104 keyboard (American layout) the 'Enter' key and its
>> neighbours look like this:
>>
>> +---+ +---+ +-------+
>> | 1 | | 2 | | 5 |
>> +---+ +---+ +-------+
>> +---+ +-----------+
>> | 3 | | 4 |
>> +---+ +-----------+
>
> [ ... snip ... ]
>
> Alright, I can't really see this introducing any regressions. I have now
> queued this for 3.20.
As Fredrik wrote, we need to also check for VARIABLE:
if (!(field->flags & (HID_MAIN_ITEM_RELATIVE |
HID_MAIN_ITEM_BUFFERED_BYTE)) &&
(field->flags & HID_MAIN_ITEM_VARIABLE) &&
usage->usage_index < field->maxusage &&
value == field->value[usage->usage_index]) {
the added line is:
(field->flags & HID_MAIN_ITEM_VARIABLE) &&
I'll not be at home until tomorrow. Feel free to add it yourself,
otherwise, basic HID keyboards that use ARRAY reports are broken.
Thanks
David
next prev parent reply other threads:[~2015-01-06 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 14:21 [PATCH] HID: input: fix confusion on conflicting mappings David Herrmann
2014-12-29 16:13 ` Fredrik Hallenberg
2015-01-06 21:19 ` Jiri Kosina
2015-01-06 21:29 ` David Herrmann [this message]
2015-01-06 21:42 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2014-12-31 0:57 Christopher Head
2015-01-06 12:37 ` Fredrik Hallenberg
2015-01-06 12:47 ` David Herrmann
2015-01-08 5:50 ` Christopher Head
2015-01-08 9:09 ` Fredrik Hallenberg
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='CANq1E4TYhDzpLofxCr05hvHJMAvtMHEM210ALsB_UOi2=4c7kQ@mail.gmail.com' \
--to=dh.herrmann@gmail.com \
--cc=adam@spicenitz.org \
--cc=benjamin.tissoires@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=megahallon@gmail.com \
--cc=stable@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).