From: Manuel Naranjo <manuel@aircable.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Klaus Teller <klaus.teller@gmx.net>, linux-bluetooth@vger.kernel.org
Subject: Re: Supporting more than 7 Connections
Date: Sat, 28 Mar 2009 10:58:50 -0300 [thread overview]
Message-ID: <49CE2D1A.30500@aircable.net> (raw)
In-Reply-To: <1238212849.8206.20.camel@localhost.localdomain>
Hi Marcel,
>> I've inquired with Aircable and it appears their Bluetooth Chip can handle 7 active connections and 128 parked connections. The comment at http://osdir.com/ml/linux.bluez.devel/2003-07/msg00110.html also suggests that the CSR chip is capable of handling more than 7 connections overall.
>>
>> So, what effort would be involved in making supervisory unpark-parks in BlueZ possible?
>>
>
> Aircable is not building their own chips. So I highly doubt that any
> chip manufacturer bothered to test park with 128 slaves.
You're right we're not building the chips, almost no one can do it, not
every company can afford the money for this. We're just using BlueCore 4
from CSR for the dongle Klaus is talking about.
> I think these guys mixing specification values with real life values.
According to CSR the chip it self should be available to support park
mode, but I agree with you, I doubt they tested this in a real
environment. I think that for bluetooth uses 7 connections is quite
enough, I can't imagine when you would need more, the only scenario I
can think off is real time sensors networks.
> However be my guest to prove me wrong, but keep in mind that park state will be eventually be deprecated since nobody is using it.
>
I agree.
Thanks,
Manuel Naranjo
Wireless Cables Inc
www.aircable.net
prev parent reply other threads:[~2009-03-28 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 17:45 Supporting more than 7 Connections Klaus Teller
2009-03-26 7:05 ` Marcel Holtmann
2009-03-27 20:48 ` Klaus Teller
2009-03-28 4:00 ` Marcel Holtmann
2009-03-28 13:58 ` Manuel Naranjo [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=49CE2D1A.30500@aircable.net \
--to=manuel@aircable.net \
--cc=klaus.teller@gmx.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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