From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: simon@mungewell.org, Henrik Rydberg <rydberg@euromail.se>,
case <case@corpsmoderne.net>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: About the PS3 Sixaxis linux driver
Date: Mon, 18 Nov 2013 12:02:56 -0500 [thread overview]
Message-ID: <528A4840.6010205@redhat.com> (raw)
In-Reply-To: <20131118172535.e6abd12d338023ead6477058@studenti.unina.it>
On 18/11/13 11:25, Antonio Ospite wrote:
> On Mon, 18 Nov 2013 10:38:42 -0500
> Benjamin Tissoires <benjamin.tissoires@redhat.com> wrote:
>
>> Hi guys,
>>
>> I forgot to say that:
>> - IMO, the approach raised in 2011 by Antonio[1] was the correct one:
>> the multitouch protocol introduced a regression with devices providing
>> large axis number, so we should fix this in input core, not on a per
>> device basis.
>> - I'll send an update to this patch later this week.
>
> Thanks.
>
>> - I don't think remapping the PS3 axis now will make into upstream
>> (backward compatibility), but this is only my own opinion
>
> What do other people think? I was going to motivate the change of
> keycodes with the fact that the device was not fully functional for a
> long time, but if you fix it in input core this argument does not hold
> anymore :)
Just FYI, I mentioned this because there already has been 2 or 3 threads
regarding bad uses of keycodes/axis for gamepads (WII, XBox, and PS3
IIRC), and the result was always "we do not break user space".
Personally, I have nothing against mapping the correct axis :)
>
> It would have been a good excuse to have a user of the full gamepad
> API and of a good part of the motion-tracking API, but I won't push
> this too hard.
There are some initiatives in the user space to fix those kernel
problems. libinputmapper (find one of David Herrmann's post) and
libevdev (on Freedesktop) are some good candidates.
Cheers,
Benjamin
next prev parent reply other threads:[~2013-11-18 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526A697E.7050605@corpsmoderne.net>
2013-11-04 20:37 ` About the PS3 Sixaxis linux driver Benjamin Tissoires
2013-11-04 21:07 ` simon
2013-11-04 21:18 ` Antonio Ospite
2013-11-04 21:40 ` simon
2013-11-16 17:06 ` Antonio Ospite
2013-11-18 15:38 ` Benjamin Tissoires
2013-11-18 16:25 ` Antonio Ospite
2013-11-18 17:02 ` Benjamin Tissoires [this message]
2013-11-04 23:03 ` Marc
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=528A4840.6010205@redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=case@corpsmoderne.net \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=ospite@studenti.unina.it \
--cc=rydberg@euromail.se \
--cc=simon@mungewell.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).