linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Reimer <mail+linux-input@m-reimer.de>
To: linux-input@vger.kernel.org
Subject: Simple approach to write PS3/PS4 usermode driver?
Date: Mon, 15 Feb 2016 20:29:18 +0100	[thread overview]
Message-ID: <56C2270E.9080603@m-reimer.de> (raw)

Hello,

now I've been trying several things, but maybe I missed something.

- If I just blacklist "hid-sony", then everything is dead. No bluetooth 
binding, no "/dev/hidrawX".
- After some searching, I found out that the core reason for this is a 
"hid_have_special_driver" list in hid-core.c which contains the PS3/PS4 
controller.
- So I thought: Maybe I can keep "hid-sony" to keep "/dev/hidrawX" and 
somehow detach the generated eventX and jsX devices. I've been searching 
/sys for about half an hour but I didn't find any way to do this. Maybe 
impossible?

I know that libusb may be an option, but this way I also give up easy 
bluetooth binding. Especially the PS4 gamepad is easy to bind. If the 
resulting bluetooth device wouldn't be blacklisted in hid-core.c.

Maybe someone can give me a hint. Is there any easy way to get the HID 
to input device translation process ported into usermode without giving 
up all the things that work automatically if hid-sony is active?

Thank you very much for any information.

Best regards,

Manuel

             reply	other threads:[~2016-02-15 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 19:29 Manuel Reimer [this message]
2016-02-15 21:34 ` Simple approach to write PS3/PS4 usermode driver? 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

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=56C2270E.9080603@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).