From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM server problem
Date: 16 May 2003 10:14:13 +0200 [thread overview]
Message-ID: <1053072859.26550.15.camel@pegasus> (raw)
In-Reply-To: <5.1.0.14.2.20030515171955.0d4a34f8@unixmail.qualcomm.com>
Hi Max,
> I cannot reproduce that. I just tried to connect from my Dual PPro, which
> is still running 2.4.21-pre4 with no updates to BT stuff, to my laptop
> with very latest bt-2.4.
> I get normal trace
> 1053045305.509342 > RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> 1053045305.509438 < RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> 1053045305.540498 > RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
> dlci 20 frame_type 0 credit_flow 15 pri 0 ack_timer 0 frame_size 1019 max_retrans 0 credits 7
> 1053045305.540619 < RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
> dlci 20 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 1019 max_retrans 0 credits 7
> 1053045305.549164 > RFCOMM(s): SABM: cr 1 dlci 20 pf 1 ilen 0 fcs 0xfd
> 1053045305.549206 < RFCOMM(s): UA: cr 1 dlci 20 pf 1 ilen 0 fcs 0x36
> 1053045305.549248 < RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
> dlci 20 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> 1053045305.579298 > RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
> dlci 20 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> 1053045305.579387 < RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
> dlci 20 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> 1053045305.579660 > RFCOMM(d): UIH: cr 1 dlci 20 pf 1 ilen 0 fcs 0x2d
> 1053045305.589091 > RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
> dlci 20 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> 1053045305.589117 < RFCOMM(d): UIH: cr 0 dlci 20 pf 1 ilen 0 fcs 0xf7
>
> (first UIH sent before last MSC response came from 2.4.21-pre4
> which doesn't have MSC fixes).
>
> So. I'm absolutely sure that new code is 100% compatible with the old one. I see
> no delays in SABM processing.
> And I have no idea what's going on with your P4 :).
after my latest tests I am pretty sure that this has nothing to do with
our changes in the RFCOMM code. It must be some kind of side effect,
which hasn't been noticed yet.
Did anyone had similar problems?
Regards
Marcel
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-05-16 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 0:05 [Bluez-devel] RFCOMM server problem Marcel Holtmann
2003-05-14 16:38 ` Max Krasnyansky
2003-05-14 22:21 ` Marcel Holtmann
2003-05-16 0:38 ` Max Krasnyansky
2003-05-16 8:14 ` 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=1053072859.26550.15.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
/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