Hi Simon, On Sunday 19 January 2014 14:45:43 simon@xxxxxxxxxxxxx wrote: > > Sony Dualshock 4 controller is ignoring L2CAP MTU while sending SDP > > response. This results in data being dropped and no SDP response is > > received (so no input device was created and HID connection was > > refused). Workaround this by using large IMTU for SDP. > > I tried with this and your earlier DS4 patch, on top of a Fedora 20 Live > CD, and unfortunately it does not work for me. I still get the situation > where the DS initiates a connection and then turns off immediately. > > I get the log messages > -- > Jan 19 14:01:14 localhost systemd: Reached target Bluetooth. > Jan 19 14:01:14 localhost bluetoothd[1803]: Refusing input device connect: > No such file or directory (2) > Jan 19 14:01:14 localhost bluetoothd[1803]: Refusing connection from > 1C:66:6D:07:C3:E0: unknown device > -- > > See log files: > pair_ds4_fedora.txt > connect_ds4_fedora.txt > > There is also a problem when the pairing is initiated from the PC side, > seems that the resultant link key is not accepted on connection. > > See: > pair_fedora_ds4_2.txt > connect_ds4_fedora_2.txt > > I note that the cache file for the DS4's mac picks up some details on a > SDP browse, but not a complete record. This is on an older machine, so BT > chipset might be a factor. > > Anything I can try? > Simon It looks like you are using BT 2.0 dongle. I suggest trying with 2.1. I didn't check with 2.0 yet. BTW This patch is not going to be merge in current form. I'll be sending V2 later. -- Szymon K. Janc szymon.janc@xxxxxxxxx -- 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
