From: Edd Dumbill <edd@usefulinc.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Release of new BlueZ libs and utils
Date: Sat, 03 Jan 2004 18:33:34 +0000 [thread overview]
Message-ID: <1073154814.8729.66.camel@saag> (raw)
In-Reply-To: <1073149849.25261.97.camel@pegasus>
On Sat, 2004-01-03 at 17:10, Marcel Holtmann wrote:
> this can never be a libs problem, because L2CAP and RFCOMM are only
> kernel related. However having this problem is somekind odd. Do it only
> happens on BlueZ <-> BlueZ connections?
No, I've not tried BlueZ<->BlueZ, it happened with my SE P800 connecting
back to BlueZ.
Occasionally it gets a bit further, then hangs:
> ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x41 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x169 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x002a flags 0x02 dlen 18
L2CAP(d): cid 0x41 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 0 ack_timer 0 frame_size
667 max_retrans 0 credits 3
< ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x169 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0169
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0169
> HCI Event: Number of Completed Packets(0x13) plen 5
-- Edd
next prev parent reply other threads:[~2004-01-03 18:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 23:55 [Bluez-users] Release of new BlueZ libs and utils Marcel Holtmann
2003-12-19 0:28 ` Michal Semler (volny.cz)
2003-12-19 9:19 ` Marcel Holtmann
2003-12-19 10:22 ` Michal Semler (volny.cz)
2003-12-20 7:14 ` Charles Bueche
2003-12-20 14:39 ` Marcel Holtmann
2003-12-19 10:15 ` Stephen Crane
2004-01-01 20:39 ` Edd Dumbill
2004-01-02 11:04 ` [Bluez-users] " Marcel Holtmann
2004-01-02 11:09 ` Edd Dumbill
2004-01-02 11:24 ` [Bluez-users] " Marcel Holtmann
2004-01-02 17:18 ` Michal Semler (volny.cz)
2004-01-02 23:35 ` Marcel Holtmann
2004-01-03 19:54 ` Michal Semler (volny.cz)
2004-01-04 10:35 ` Marcel Holtmann
2004-01-03 16:32 ` [Bluez-users] " Edd Dumbill
2004-01-03 16:47 ` Edd Dumbill
2004-01-03 17:10 ` Marcel Holtmann
2004-01-03 18:33 ` Edd Dumbill [this message]
2004-01-04 10:38 ` Marcel Holtmann
2004-01-06 11:26 ` Edd Dumbill
2004-01-06 12:37 ` Marcel Holtmann
2004-01-06 13:11 ` Edd Dumbill
2004-01-06 13:20 ` Marcel Holtmann
2004-01-06 14:02 ` Edd Dumbill
2004-01-06 14:15 ` Marcel Holtmann
2004-01-06 14:30 ` Edd Dumbill
2004-01-06 14:18 ` Xavier Garreau
2004-01-06 12:54 ` Xavier Garreau
2004-01-06 13:06 ` 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=1073154814.8729.66.camel@saag \
--to=edd@usefulinc.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.