From: Andreas Gaufer <Andreas.Gaufer@blue-cell-networks.com>
To: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcitool con list incomplete (was: Connect Complete with Status 09)
Date: Thu, 10 Jun 2004 12:18:05 +0200 [thread overview]
Message-ID: <20040610121805.3121ca26.Andreas.Gaufer@blue-cell-networks.com> (raw)
In-Reply-To: <20040609212529.6901de52.Andreas.Gaufer@blue-cell-networks.com>
Hi,
I dug in a little bit deeper last night and i think its not a problem of the
chip. The list that is printed out by "hcitool con" is incomplete in certain
situations. This leads to various problems with many tools because they try to
connect again witch fails.
If a "create connection" is issiued while there is already a connection the chip
returnes a Connect Complete with status 0x0B witch is absolutely right. The
problem is that the hanlde of the "hcitool con" list is removed but the chip
still keeps it, witch is good behaviour in my opinion. It can be disconected with
"hcitool cmd".
Who or what is keeping this list?
Greetings
Andreas Gaufer
-------------------------------------------------------
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 prev parent reply other threads:[~2004-06-10 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 16:53 [Bluez-devel] HCI Event: Connect Complete with Status 09 Andreas Gaufer
2004-06-09 17:54 ` Steven Singer
2004-06-09 19:25 ` Andreas Gaufer
2004-06-10 10:18 ` Andreas Gaufer [this message]
2004-06-10 10:20 ` 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=20040610121805.3121ca26.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