From: Steven Singer <steven.singer@csr.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] connections
Date: Thu, 07 Dec 2006 10:48:44 +0000 [thread overview]
Message-ID: <4577F18C.2010806@csr.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0611281554510.30196@redbean.intranet.gw-instruments.de>
Peter Wippich wrote:
> No quite sure but it is a problem with your BT chip. It only allows 3
> connection. If it is a CSR chip may be soembody has configured it to allow
> only 3 ACL connections. You can find out using bccmd. There is a PS-key
> named something like MAX_ACL_CONNECTIONS.
No. It's not a baseband issue. If it were, the connection would be
rejected at the HCI level. Instead, the connection is being rejected at
the L2CAP level indicating that the baseband was happy to accept the
connection, but something that's nominally in the host has rejected it.
- Steven
--
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-07 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 14:35 [Bluez-devel] connections mark bernard
2006-11-28 14:57 ` Peter Wippich
2006-12-07 10:48 ` Steven Singer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 21:00 [Bluez-devel] Connections markusv
2006-06-07 21:11 ` 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=4577F18C.2010806@csr.com \
--to=steven.singer@csr.com \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).