From: f h <haro41@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] drivers: hid: fix G940 axis/button mappings
Date: Tue, 2 Apr 2019 11:11:18 +0200 [thread overview]
Message-ID: <62bf40ca-3bf2-6e36-c54f-fab0eb62a1dc@gmx.de> (raw)
On Mon, 11 Mar 2019, Chris Boyle wrote:
> Provide a complete map of axes and buttons for the Logitech Flight System
> G940, which fixes several issues:
>
> Stop conflating the stick X/Y axes with the mini-stick (hat) axes. This
> stops reported X jumping between stick X and hat X (likewise Y).
>
> Stop conflating the other three hat switches (non-mini-stick) with each
> other. This was caused by commit 190d7f02ce8e ("HID: input: do not
> increment usages when a duplicate is found")
>
> Report TRIM1 and TRIM2, previously ignored as unrecognised usage types.
>
> Report the MODE switch and hand sensor, previously ignored as they're in
> a vendor page.
>
> Signed-off-by: Chris Boyle <chris@xxxxxxxxxx>
> ---
I have to confirm, that the current kernel driver for logitech G940 is
deficient (as desribed by the author of this patches).
I tested this patch series against latest stable kernel (5.0.5, debian
testing) and it fixes all former input related issues.
Regards,
Jens
reply other threads:[~2019-04-02 9:11 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=62bf40ca-3bf2-6e36-c54f-fab0eb62a1dc@gmx.de \
--to=haro41@gmx.de \
--cc=linux-kernel@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).