From: Szymon Janc <szymon.janc@gmail.com>
To: simon@mungewell.org
Cc: Szymon Janc <szymon.janc@tieto.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/5] lib: Add flag to force large MTU size used for SDP connection
Date: Mon, 20 Jan 2014 19:48:31 +0100 [thread overview]
Message-ID: <21065964.6PlzB0c1ck@athlon> (raw)
In-Reply-To: <cfdf976e52d86b180ee5e750c23fed8f.squirrel@mungewell.org>
Hi Simon,
On Monday 20 January 2014 13:28:57 simon@mungewell.org wrote:
> > From: Szymon Janc <szymon.janc@gmail.com>
> >
> > 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@gmail.com
prev parent reply other threads:[~2014-01-20 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 11:08 [PATCH v2 1/5] lib: Add flag to force large MTU size used for SDP connection Szymon Janc
2014-01-20 11:08 ` [PATCH v2 2/5] core: Opencode get_sdp_session in sdp-client Szymon Janc
2014-01-20 11:08 ` [PATCH v2 3/5] core: Add flags parameter to bt_search_service Szymon Janc
2014-01-20 11:08 ` [PATCH v2 4/5] device: Add workaround for Sony Dualshock 4 broken SDP Szymon Janc
2014-01-20 11:08 ` [PATCH v2 5/5] device: Match Dualshock4 with name and class Szymon Janc
2014-01-20 13:20 ` [PATCH v2 1/5] lib: Add flag to force large MTU size used for SDP connection Johan Hedberg
2014-01-20 18:28 ` simon
2014-01-20 18:48 ` Szymon Janc [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=21065964.6PlzB0c1ck@athlon \
--to=szymon.janc@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon@mungewell.org \
--cc=szymon.janc@tieto.com \
/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