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, 16 Feb 2016 20:45:30 +0100 [thread overview]
Message-ID: <56C37C5A.6030303@m-reimer.de> (raw)
In-Reply-To: <20160215223436.fc5a3f66f82ee49b161099ea@ao2.it>
On 02/15/2016 10:34 PM, Antonio Ospite wrote:
> Have you tried loading hid.ko with the ignore_special_drivers=1
> parameter? I guess that will ignore _all_ special drivers tho, even
> mouse and keyboard ones.
Exactly. And so it is not what I planned to do.
> Alan Ott's hidapi[1] is a better alternative to libusb for hid
> devices.
Of course, but just for fun, I'll at least try to use libusb directly.
There are many examples on the net. I've already collected some code
snippets to use.
> I reckon a patched kernel is not an option, is it?
The kernel side driver does a great job. It has minor bugs (kernel panic
when disconnecting controller while in game), but nothing too bad.
My plan is to remap to Xbox gamepad button mapping so games actually
work with the controller. In fact, I bought a brand new PS4 controller
just for my driver project. At least so far, I only own the PS3 console.
What I've done so far is to write a daemon which connects to the
existing event device to get events from there, but this didn't really
work as games still see the original controller.
That's why my current plan is to connect one layer deeper so the
original event devices aren't created at all.
My reason for userspace is, that it's easier to debug and for the
potential end user it is easier to install. I just had too much trouble
with dkms in the past.
Best regards,
Manuel
next prev parent reply other threads:[~2016-02-16 19:45 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 [this message]
2016-02-16 20:56 ` Clément VUCHENER
2016-02-27 21:59 ` Bruno Prémont
2016-03-01 19:56 ` Manuel Reimer
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=56C37C5A.6030303@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).