From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-input@vger.kernel.org
Subject: Re: PS4 controller with Bluetooth: Only the touch pad sends events?
Date: Sat, 23 Jan 2016 18:26:23 +0100 [thread overview]
Message-ID: <n80d3v$qcj$1@ger.gmane.org> (raw)
In-Reply-To: <n8097h$uek$1@ger.gmane.org>
Hello,
just a short follow up.
I've tested the controller directly on the PS3 console (don't own a PS4
yet) and it works well there, which confirms that the controller is OK.
Then I searched around a bit and found:
https://bugzilla.kernel.org/show_bug.cgi?id=107081
Did this patch ever land here on the mailing list?
If not, I'll take over, have a look at reformatting the patch, test it
with my PC and my PS4 controller and then send it to the list.
Thanks in advance
Manuel
On 01/23/2016 05:20 PM, Manuel Reimer wrote:
> Hello,
>
> I'm currently trying to get my PS4 controller to work via Bluetooth.
>
> My kernel is:
> $ uname -a
> Linux manuelspc 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016
> x86_64 GNU/Linux
>
> If I run "evtest" on the event device, created by the controller, then I
> only get events if the touch pad is touched. Even pressing the touch pad
> doesn't create a event and all other buttons and sticks don't send
> events either.
>
> What's the reason for this? If I connect via USB, I don't have any
> issues and all buttons and axis work well...
>
> Thank you very much in advance.
>
> 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-01-23 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 16:20 PS4 controller with Bluetooth: Only the touch pad sends events? Manuel Reimer
2016-01-23 17:26 ` 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='n80d3v$qcj$1@ger.gmane.org' \
--to=manuel.spam@nurfuerspam.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 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.