From: mkj@gotu.dk (Martin Kjær Jørgensen)
To: Frank Praznik <frank.praznik@gmail.com>
Cc: Antonio Ospite <ao2@ao2.it>, linux-bluetooth@vger.kernel.org
Subject: Re: DS4 issues
Date: Thu, 21 Apr 2016 18:15:26 +0200 [thread overview]
Message-ID: <877ffrq6ox.fsf@gotu.dk> (raw)
In-Reply-To: <87k2m7602c.fsf@gotu.dk> ("Martin \=\?utf-8\?Q\?Kj\=C3\=A6r_J\=C3\=B8\?\= \=\?utf-8\?Q\?rgensen\=22's\?\= message of "Sun, 14 Feb 2016 11:47:07 +0100")
I've now upgraded my Debian Testing machine to kernel 4.5.1. It seems to
have fixed my first issue. The controller now binds, gets recognized
and I can test it with jstest and use it in programs :-)
However, it's not recognized as a DS4 controller, so programs that
would automatically map keys and buttons according to controller now
requires manual mapping.
Upon turning my DS4 controller on, dmesg produces this:
[ 4469.637467] sony 0005:054C:05C4.0009: Using modified Dualshock 4 Bluetooth report descriptor
[ 4469.638626] input: Wireless Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:054C:05C4.0009/input/input27
[ 4469.639080] sony 0005:054C:05C4.0009: input,hidraw5: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on 28:b2:bd:94:0c:4f
... which is different from when using USB cabel. Again, when using
cabel the controller works perfectly.
Any suggestions to this?
next prev parent reply other threads:[~2016-04-21 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 14:46 DS4 issues Martin Kjær Jørgensen
2015-12-28 9:18 ` Antonio Ospite
2015-12-28 15:48 ` Frank Praznik
2015-12-28 16:40 ` Martin Kjær Jørgensen
2015-12-30 11:09 ` Martin Kjær Jørgensen
2015-12-30 15:36 ` Frank Praznik
2016-02-14 10:47 ` Martin Kjær Jørgensen
2016-04-21 16:15 ` Martin Kjær Jørgensen [this message]
2016-04-27 1:22 ` Frank Praznik
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=877ffrq6ox.fsf@gotu.dk \
--to=mkj@gotu.dk \
--cc=ao2@ao2.it \
--cc=frank.praznik@gmail.com \
--cc=linux-bluetooth@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.