From: Sumeet VERMA <sumeet.verma@st.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2CAP disconnect problem
Date: Fri, 24 Nov 2006 11:57:45 +0530 [thread overview]
Message-ID: <018201c70f91$a77cff90$8935c70a@dlh.st.com> (raw)
In-Reply-To: <1164348861.28284.4.camel@localhost>
Thanks a lot Marcel. Actually I didn't have time to upgrade the kernel as I am in customer support.:) I will do it in my spare time.
Sumeet
-----Original Message-----
From: bluez-users-bounces@lists.sourceforge.net [mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Marcel Holtmann
Sent: Friday, November 24, 2006 11:44 AM
To: BlueZ users
Subject: Re: [Bluez-users] L2CAP disconnect problem
Hi Sumeet,
> I investigated the RFCOMM disconnect problem in more detail and found
> out that when the device is a listener, it expects the initiator of
> RFCOMM connection to disconnect dlci 0. But all devices don't send
> RFCOMM DISC for dlci 0. For ex PTS doesn't disconnect dlci 0 in case
> of HS profile testing Test Case:
> -> IUT (BlueZ) is HS Gateway, PTS is HS PTS initiates connection and
> -> then disconnect RFCOMM data channel is disconnected by BlueZ but it
> -> waits for PTS to
> disconnect RFCOMM control channel which doesn't happen.
> -> As a result test case fails
>
> The HS Spec says HS Gateway is responsible for disconnecting the connection.
> In that case I think there is a misbehaviour here.
>
> If there is something I am missing in understanding the RFCOMM
> implementation and this problem, please correct me.
> Otherwise do you have a patch to solve this problem, wherein the
> listener disconnects dlci 0?
I told you that this was a known bug and we fixed it. You should have tested a recent 2.6 kernel and this basically means 2.6.18 or even later. Not an ancient RHEL4 kernel. Anyway, this is the patch that went in upstream to fix this problem.
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
next prev parent reply other threads:[~2006-11-24 6:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 11:45 [Bluez-users] L2CAP disconnect problem Sumeet VERMA
2006-11-20 12:40 ` Marcel Holtmann
2006-11-21 7:16 ` Sumeet VERMA
2006-11-21 7:27 ` Marcel Holtmann
2006-11-22 5:43 ` Sumeet VERMA
2006-11-22 6:23 ` Marcel Holtmann
2006-11-24 5:59 ` Sumeet VERMA
2006-11-24 6:14 ` Marcel Holtmann
2006-11-24 6:27 ` Sumeet VERMA [this message]
2006-11-24 7:15 ` Sumeet VERMA
2006-11-24 7:31 ` Marcel Holtmann
2006-11-24 8:52 ` Sumeet VERMA
2006-11-24 17:25 ` Marcel Holtmann
2006-11-24 8:53 ` Sumeet VERMA
2006-11-24 9:01 ` Sumeet VERMA
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='018201c70f91$a77cff90$8935c70a@dlh.st.com' \
--to=sumeet.verma@st.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