From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Signification of the state term
Date: Thu, 16 Nov 2006 11:30:24 +0100 [thread overview]
Message-ID: <1163673024.5169.25.camel@localhost> (raw)
In-Reply-To: <009e01c70908$9ab526a0$8ba54256@claudia>
Hi,
> I search the signification of the "state" term given for each
> connection
> by the "hcitool con" command.
>
>
> 1. First, I have an ACL connection between 2 bluetooth kits : the
> state of the ACL connection is 1
>
> 2. I create an SCO connection on this ACL connection : the
> state of the ACL connection stills 1
>
> 3. I make an HCI_disconnect on one side of the connection.
>
> With hcidump, after the HCI_disconnect command, I see consecutively
> two events of complete deconnection :
>
> - the first one for the SCO link,
> - the second one for the ACL link.
>
> But, the "hcitool con" command shows again the ACL connection with 8
> value for the "state".
>
> When I try to disconnect this link I have a disconnect error.
>
> Does someone have an idea ? What is the signification of a 8 value for
> the "state" ?
it is the connection state. Check /usr/include/bluetooth/bluetooth.h and
its enum for all possible states.
Regards
Marcel
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-11-16 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 22:51 [Bluez-users] Signification of the state term Michel Leconte
2006-11-16 10:30 ` Marcel Holtmann [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=1163673024.5169.25.camel@localhost \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.