From: Manuel Reimer <mail+linux-input@m-reimer.de>
To: linux-input@vger.kernel.org
Subject: Re: Simple approach to write PS3/PS4 usermode driver?
Date: Tue, 1 Mar 2016 20:56:56 +0100 [thread overview]
Message-ID: <56D5F408.4020604@m-reimer.de> (raw)
In-Reply-To: <20160227225909.073f78a9@neptune.home>
On 02/27/2016 10:59 PM, Bruno Prémont wrote:
> Have you tried event remapping as supported by evdev?
>
> Have a look at EVIOCGKEYCODE and EVIOCSKEYCODE ioctls for event devices.
>
> Those might be sufficient to perform your remapping (as long as games don't
> do magic based on event device identification).
They do! A few games actually have support for the PS3 controller so I
would have to enable/disable my modifications depending on that.
I just want some easy way to use my controllers with any game that
supports xbox pads. This also involves scaling the stick values to the
range used by the Xbox pad.
I'm nearly done with USB support in my usermode driver and currently I
think I won't do bluetooth as this starts to suck. USB seems to be many
times easier...
For whatever reason the PS4 controller doesn't send anything to the
interrupt socket (I already send all "initialization sequences" I found
on the web) and the PS3 controller seems to use some crazy special type
of connecting (does the controller actually try to connect to my PC and
so I have to listen for it??).
I still hope to be at least able to support the PS4 controller in
bluetooth mode, but I don't have any clue why the interrupt socket is
silent...
Best regards,
Manuel
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-01 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 19:29 Simple approach to write PS3/PS4 usermode driver? Manuel Reimer
2016-02-15 21:34 ` Antonio Ospite
2016-02-16 19:45 ` Manuel Reimer
2016-02-16 20:56 ` Clément VUCHENER
2016-02-27 21:59 ` Bruno Prémont
2016-03-01 19:56 ` Manuel Reimer [this message]
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=56D5F408.4020604@m-reimer.de \
--to=mail+linux-input@m-reimer.de \
--cc=linux-input@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).