From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: RFCOMM connection lag (slow)
Date: Tue, 26 Jul 2011 10:42:51 +0200 [thread overview]
Message-ID: <4E2E7E0B.20006@kernelconcepts.de> (raw)
In-Reply-To: <1311535249.4311.25.camel@THOR>
Am 24.07.2011 21:20, schrieb Peter Hurley:
> On Sun, 2011-07-24 at 14:42 -0400, Nils Faerber wrote:
>> Am 24.07.2011 19:58, schrieb Nils Faerber:
>>> Am 24.07.2011 19:06, schrieb Peter Hurley:
>>>> 1. What does an hcidump -tX of the session say?
>>>
>>> The complete log would be a little longer.
>>> Is there something special that I could watch for?
> ...
>>
>> Why does the hcidump from Linux not show RFCOMM(d) parts like the G1 dump?
>
> The new l2cap code now sets the first ACL data packet
> Packet_Boundary_Flag to 'not automatically flushable' on l2cap channels
> not marked flushable (the default is not flushable).
>
> The decode of this in hcidump was fixed back in February.
OK, great, with a new one I see the RFCOMM now, thanks!
I also found another hint towards the RFCOMM lag...
If I disable SNIFF on the Linux side it behaves normal again. Once it
has entered SNIFF mode for the first time the connection starts to lag.
So I am almost suspecting not an RFCOMM but rather HCI/SNIFF issue and
this is most likely caused by the Bluetooth device rather the Linux
host. I just can not come up with an explanation why it work including
SNIFF from the older HTC G1 - there the Linux kernel is for sure much
older than on my notebook. Did something concerning SNIFF mode change
more or less recently?
> Regards,
> Peter
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
prev parent reply other threads:[~2011-07-26 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 16:22 RFCOMM connection lag (slow) Nils Faerber
2011-07-24 17:06 ` Peter Hurley
2011-07-24 17:58 ` Nils Faerber
2011-07-24 18:42 ` Nils Faerber
2011-07-24 19:20 ` Peter Hurley
2011-07-26 8:42 ` Nils Faerber [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=4E2E7E0B.20006@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter@hurleysoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.