From: Matthew Reimer <mreimer@vpop.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] How to configure a 723kbps connection?
Date: Tue, 17 Feb 2004 17:09:56 -0600 [thread overview]
Message-ID: <40329F44.5070603@vpop.net> (raw)
In-Reply-To: <lists.bluez.users.403291AD.7080601@csr.com>
Steven Singer wrote:
> Marcel Holtmann wrote:
>
>>no I don't missed the point here. But the thread was broken and if you
>>look at the beginning you see that I already told him that it can be a
>>problem with a too slow UART. This is true for the 3870.
>
>
> I read Matt's message as that he was asking for confirmation of your
> suggestion that the UART baud rate was the most likely limit and that
> he should stop wasting his time playing with the packet settings. Given
> the information he listed, particularly that the link quality was 255,
> I think it's unlikely to be a problem with the Bluetooth link and more
> likely to be a problem elsewhere in the system.
Yes, you read my message correctly.
> The next few messages in the thread were talking about whether the Zeevo
> chip was a bad chip or had a bad link manager. This appears to be
> irrelevant as the most likely source of the bandwidth limit is the Ipaq
> UART.
>
> Although I'm normally quite happy to see our competitors' products
> maligned, I think that in this case, the conclusion was unwarranted.
>
>
>>>Also, although you're right that the RSSI has nothing to do with the
>>>chosen packet type, the link quality has a big effect. As the link
>>>quality falls, devices will tend to switch automatically from DH
>>>packets to the more robust DM packets.
>>
>>The link quality is problematic, because every chip manufacturer can
>>interpret this value different. For CSR this is bound to the BER. Had
>>you ever run any test with your chips against the old Zeevo TC2001
>>generation?
>
>
> The spec allows the link quality to be tied to anything, but module
> manufacturers will be aware that if they don't have at least some
> component of the link quality sensitive to whether DH packets are likely
> to get through, they're going to get support calls of the form "why am I
> getting only 400 kbps but get_link_quality says the link is perfect?"
>
> However, since the logs Matt gave show him running hcitool to get
> the link quality, he must be getting it on the Linux side of the
> link which, according to his hciconfig, is a CSR device.
Correct; that was all from the linux side where the CSR device
(Actiontec USB dongle) is connected.
> This tells us that the CSR device is has a BER for received packets
> that's low enough for DH5 packets to stream at 700 kbps. However, it
> tells us nothing about the BER for packets received at the Ipaq end.
> The link may not be symmetric. However, even if the link had switched
> to DM5 packets, we'd expect to see 470 kbps. To get 265 kbps the link
> would have to be atrocious (> 0.4% BER). I think it's unlikely that
> we'd have a 0.4% BER one way and < 0.0025% the other way.
>
> There may be other issues. For example, poor choice of L2CAP MTU
> could limit the packet types that are allowed (for example, L2CAP
> MTUs sigificantly below 150 could limit the data rate). This would
> show up on an HCI trace. An HCI trace would also confirm which profile
> was being used for the connection.
Can I change the L2CAP MTU? Is that different than the ACL MTU that can
be set via hciconfig? Can I get "an HCI trace" with hcidump, or is that
what a protocol analyzer would be needed for?
I'm using the NAP profile (sorry for not mentioning that).
> It may be that the Ipaq is limited in the rate at which it can process
> data. This could cause it to assert UART flow control to the Bluetooth
> chip, stalling the data flow.
>
> As for testing with Zeevo, it's probably safest if I say nothing. Most
> interoperability testing is covered by NDAs.
>
> - Steven
Thanks for your insights!
Matt
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next parent reply other threads:[~2004-02-17 23:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lists.bluez.users.1077037423.2665.72.camel@pegasus.SOMEWHERE>
[not found] ` <lists.bluez.users.403291AD.7080601@csr.com>
2004-02-17 23:09 ` Matthew Reimer [this message]
2004-02-17 23:36 ` [Bluez-users] How to configure a 723kbps connection? Marcel Holtmann
2004-02-18 3:51 ` Matthew Reimer
2004-02-24 3:49 ` Matthew Reimer
2004-02-25 15:03 ` Paulo Marques
[not found] <lists.bluez.users.1077061006.2665.141.camel@pegasus.SOMEWHERE>
[not found] ` <lists.bluez.users.4032E137.7080902@vpop.net>
2004-02-18 3:56 ` Matthew Reimer
[not found] <lists.bluez.users.40327430.2090807@grupopie.com>
2004-02-17 20:45 ` Matthew Reimer
[not found] <200402160913.i1G9DCP02222@webserver.restinfor.pt>
2004-02-17 20:06 ` Paulo Marques
[not found] <lists.bluez.users.40323EC2.8080203@csr.com>
2004-02-17 10:50 ` grpmind+bluez.users
2004-02-17 18:58 ` Marcel Holtmann
2004-02-17 6:36 grpmind+bluez.users
2004-02-17 15:37 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 3:42 grpmind+bluez.users
2004-02-17 11:52 ` Marcel Holtmann
2004-02-17 16:18 ` Steven Singer
2004-02-17 17:03 ` Marcel Holtmann
2004-02-17 22:11 ` Steven Singer
2004-02-17 22:51 ` Marcel Holtmann
2004-02-14 17:06 grpmind+bluez.users
2004-02-15 14:33 ` Marcel Holtmann
2004-02-16 22:20 ` Michel Planques
2004-02-16 22:58 ` Marcel Holtmann
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=40329F44.5070603@vpop.net \
--to=mreimer@vpop.net \
--cc=bluez-users@lists.sourceforge.net \
/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