From: Frank Praznik <frank.praznik@gmail.com>
To: "Martin Kjær Jørgensen" <mkj@gotu.dk>
Cc: Antonio Ospite <ao2@ao2.it>, linux-bluetooth@vger.kernel.org
Subject: Re: DS4 issues
Date: Tue, 26 Apr 2016 21:22:06 -0400 [thread overview]
Message-ID: <41D0958C-321B-46A4-A29F-27D83AC3404B@gmail.com> (raw)
In-Reply-To: <877ffrq6ox.fsf@gotu.dk>
> On Apr 21, 2016, at 12:15, Martin Kjær Jørgensen <mkj@gotu.dk> wrote:
>
>
> 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?
The bus type and version parameters of the input_id struct retrieved with EVIOCGID are different when using bluetooth vs USB. That’s just how it is and software has to accommodate both values to work correctly. For instance, the SDL game controller mapping database has two separate entries for both the wired and wireless modes to deal with this.
prev parent reply other threads:[~2016-04-27 1:22 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
2016-04-27 1:22 ` Frank Praznik [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=41D0958C-321B-46A4-A29F-27D83AC3404B@gmail.com \
--to=frank.praznik@gmail.com \
--cc=ao2@ao2.it \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mkj@gotu.dk \
/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).