From: Sumeet VERMA <sumeet.verma@st.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2CAP disconnect problem
Date: Wed, 22 Nov 2006 11:13:59 +0530 [thread overview]
Message-ID: <010701c70df9$35ee3590$8935c70a@dlh.st.com> (raw)
In-Reply-To: <1164094036.28429.1.camel@localhost>
Marcel,
So you mean if I use 2.6 kernel this problem will not occur. I tried
2.6.9-34.EL kernel but the same problem occurs. No RFCOMM disconnect :(
Regds,
Sumeet
-----Original Message-----
From: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Marcel
Holtmann
Sent: Tuesday, November 21, 2006 12:57 PM
To: BlueZ users
Subject: Re: [Bluez-users] L2CAP disconnect problem
Hi Sumeet,
> I am using 2.4-20.8 with bluez-utils-2.25
actually this kernel is kinda old. You are better of with the latest 2.6
based kernel.
> I also tried using shutdown(fd, SHUT_RDWR) instead of close(fd) but
> still the rfcomm doesn't disconnect. This happens only when I get an
> incoming RFCOMM connection. When I initiate a connection, and disconnect,
it works.
This was a reference counting bug and I fixed it some time ago.
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
-------------------------------------------------------------------------
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-22 5:43 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 [this message]
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
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='010701c70df9$35ee3590$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