> On Apr 21, 2016, at 12:15, Martin Kjær Jørgensen <mkj@xxxxxxx> 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.-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
