From: Arch Sayo <a12chi@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] RFCOMM disconnect command from slave device
Date: Mon, 5 Dec 2005 02:32:57 -0800 (PST) [thread overview]
Message-ID: <20051205103257.18037.qmail@web32409.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]
Hi Marcel,
I would like to ask if it is okay for a slave device to be the first to issue a disconnect command in the RFCOMM layer rather than the master device. Usually, after the OBEX Disconnect request of the master device and the corresponding response of the slave device, the master issues a disconnect command in the RFCOMM layer. However, the slave device (running on BlueZ) is the first one to issue a disconnect command in the RFCOMM layer, and the master device issues a disconnect command (RFCOMM) after that of the slave device. Is this okay?
Trace for this kind of transaction is as follows:
> ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 10 pf 1 ilen 8 fcs 0xac credits 1
OBEX: Disconnect cmd(f): len 8
Connection ID (0xcb) = 0
< ACL data: handle 41 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 10 pf 0 ilen 3 fcs 0x6a
OBEX: Disconnect rsp(f): status 200 len 3
Status 200 = Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 0 dlci 10 pf 1 ilen 0 fcs 0xc
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 10 pf 1 ilen 0 fcs 0x6d
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 0 dlci 10 pf 1 ilen 0 fcs 0xc7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Thanks so much,
Arch
---------------------------------
Yahoo! DSL Something to write home about. Just $16.99/mo. or less
[-- Attachment #2: Type: text/html, Size: 7791 bytes --]
next reply other threads:[~2005-12-05 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 10:32 Arch Sayo [this message]
2005-12-05 21:32 ` [Bluez-users] RFCOMM disconnect command from slave device 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=20051205103257.18037.qmail@web32409.mail.mud.yahoo.com \
--to=a12chi@yahoo.com \
--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 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).