From: "benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>
To: Manuel Valls <manolo@vlrz.es>
Cc: "Eric.Brunet@lps.ens.fr" <Eric.Brunet@lps.ens.fr>,
"jkosina@suse.cz" <jkosina@suse.cz>,
linux-input@vger.kernel.org
Subject: Re: Issue caused by your commit to the linux kernel
Date: Thu, 21 Jan 2016 17:47:25 +0100 [thread overview]
Message-ID: <20160121164725.GC20099@mail.corp.redhat.com> (raw)
In-Reply-To: <15227381b21.be24b19a14291.7794248722302336410@vlrz.es>
Hi Manuel,
On Jan 09 2016 or thereabouts, Manuel Valls wrote:
>
>
> Commit 79346d620e9de87912de73337f6df8b7f9a46888 caused DragonRise Inc. PC TWIN SHOCK Gamepad's right stick to be wrongly detected as a Z axis, making it unusable. I'm writing to you as the authors of said commit requesting a fix. Looking forward to an answer.
>
It looks like I finally understood why this commit broke some gamepads.
Basically, nothing prevents a HID device to use an axis more than once.
This is noticeably used by multitouch devices.
So some gamepads manufacturers, are using for both joysticks (under the
2 thumbs) X and Y. Before 79346d620, this used to be working in Linux
because we were looking for the next available axis.
So when the second joystick gets parsed, X and Y are already in used,
and so they gets assigned Z and RX. Luckily, the gamepad does not uses
those particular axis (plus the fact that we actually do not care which
axis is which, this gets sorted out later on by userspace).
To be able to fix this, I will need you to provide the report
descriptors of your gamepad. Can you run hid-recorder[1] on the gamepad?
Once I have those, I should be able to either remove the gamepads from
the list of "hey, if you declare X, you should map it to X", or I might
just force the pen usages to be on this list only.
Cheers,
Benjamin
[1] https://bentiss.github.io/hid-replay-docs/
next parent reply other threads:[~2016-01-21 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15227381b21.be24b19a14291.7794248722302336410@vlrz.es>
2016-01-21 16:47 ` benjamin.tissoires [this message]
[not found] ` <15284a5ef2c.bfd3652817115.6670882487483674658@vlrz.es>
[not found] ` <15284a969a1.f76ccc5f17182.598695392442003133@vlrz.es>
2016-06-03 8:43 ` Issue caused by your commit to the linux kernel benjamin.tissoires
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=20160121164725.GC20099@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=Eric.Brunet@lps.ens.fr \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=manolo@vlrz.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.