Hi Simon, On Monday 20 January 2014 13:28:57 simon@xxxxxxxxxxxxx wrote: > > From: Szymon Janc <szymon.janc@xxxxxxxxx> > > > > This will allow to workaround Dualshock4 not respecting L2CAP MTU > > size while sending SDP response. Use same L2CAP MTU value base on > > RFCOMM. > > I can confirm that the V2 series of patches work with my DS4 and crappy > laptop. Still require particular 'connect' sequence... Thanks for testing, and yes this sequence is about dedicated vs general bonding mentioned in commit message. > > I note that I do not need the original '[PATCH 3/3] input: Add DualShock 4 > detection' patch. I am using just this sequence of 5 patches on top of > 5.13. This detection is used only when using SSP controller. And only in case when dedicated bonding is used - when DS4 tries to connect immediately after pairing is completed, but before bluetoothd was able to retrieve SDP. -- 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
