From: Jiri Kosina <jkosina@suse.cz>
To: Terry Lambert <tlambert@chromium.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver for Primax keyboards violating USB HID spec
Date: Fri, 14 Oct 2011 01:35:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1110140134200.14768@pobox.suse.cz> (raw)
In-Reply-To: <1318548517-5289-1-git-send-email-tlambert@chromium.org>
On Thu, 13 Oct 2011, Terry Lambert wrote:
> Primax keyboards with the issue this driver addresses report modifier
> keys as in band key events instead of as out of band modifier bits,
> resulting in the modifier keys generating key up events immediately
> before the keys they are intended to modify. This driver rewrites
> the raw report data from such keyboards into USB HID 1.11 compliant
> report data. It only matches the USB vendor and product IDs for the
> keyboard it has been tested on. Since there are several keyboards,
> notably a number of laptops and folding USB keyboards known to have
> similar unresolved problem reports, the list is expected to grow.
>
> Signed-off-by: Terry Lambert <tlambert@chromium.org>
Terry,
thanks for the patch.
[ ... snip ... ]
> +static int px_input_mapping(struct hid_device *hid, struct hid_input *hi,
> + struct hid_field *field, struct hid_usage *usage,
> + unsigned long **bit, int *max)
> +{
> + struct px_device *px = hid_get_drvdata(hid);
> +
> + px->input_primax = hi->input;
> +
> + /* Remap keys, if necesssary, here */
> +
> + return 0;
> +}
I fail to see the point of this routine ... ?
Otherwise, the patch seems fine.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2011-10-13 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 23:28 Terry Lambert
2011-10-13 23:35 ` Jiri Kosina [this message]
2011-10-14 0:11 ` Terry Lambert
2011-10-14 9:30 ` Jiri Kosina
2011-10-14 21:55 ` Terry Lambert
2011-10-15 0:18 Terry Lambert
2011-10-17 15:11 ` Jiri Kosina
2011-10-17 19:21 ` Terry Lambert
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=alpine.LNX.2.00.1110140134200.14768@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tlambert@chromium.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
all inboxes | Powered by JetHome®