From: Andreas Gaufer <Andreas.Gaufer@blue-cell-networks.com>
To: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] HCI Event: Connect Complete with Status 09
Date: Wed, 9 Jun 2004 18:53:48 +0200 [thread overview]
Message-ID: <20040609185348.65a9f382.Andreas.Gaufer@blue-cell-networks.com> (raw)
Hi,
I get into situations where the chip returnes a "Connect Complete" event
with status MAX NUMBER OF CONNECTIONS (0X09) without having open handles.
The only way to get this Stick back to a usable state is removing power.
There is no connection listed by "hcitool con".
Is there a (even csr specific) way of listing the acl handles that the chip
thinks are open to drop them properly or a vendor specific hci command
(besides "Reset(0x03|0x0003)") to get a "hard" reset?
Greetigs
Andy
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-06-09 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 16:53 Andreas Gaufer [this message]
2004-06-09 17:54 ` [Bluez-devel] HCI Event: Connect Complete with Status 09 Steven Singer
2004-06-09 19:25 ` Andreas Gaufer
2004-06-10 10:18 ` [Bluez-devel] hcitool con list incomplete (was: Connect Complete with Status 09) Andreas Gaufer
2004-06-10 10:20 ` [Bluez-devel] HCI Event: Connect Complete with Status 09 Marcel Holtmann
2004-06-10 14:01 ` Andreas Gaufer
2004-06-10 14:32 ` 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=20040609185348.65a9f382.Andreas.Gaufer@blue-cell-networks.com \
--to=andreas.gaufer@blue-cell-networks.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