From: Marcel Holtmann <marcel@holtmann.org>
To: Victor Shcherbatyuk <Victor.Shcherbatyuk@tomtom.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Connection with a phone stays open afterclosingRFCOMM channel
Date: Wed, 02 Mar 2005 15:19:41 +0100 [thread overview]
Message-ID: <1109773181.8284.16.camel@pegasus> (raw)
In-Reply-To: <C70061B183DE09419568AB2060C52A9518EE74@arion.intra.local>
Hi Victor,
> Don't know if I have to post it on the mailing list (with binary
> files)...
if I ask for it, it is always fine ;)
> I can not try 2.11 rc5 cause it is not an option for the current project
> and I do not have time to try it at home at the moment.
Using a 2.6.10-mh4 is also possible, but you should at least try it with
my kernel patch.
> At the moment it is not clear from the protocol (at least for me) who is
> responsible for terminating connection. It may be as well a bug in
> SE630, cause Nokia 7650 for instance takes initiative to terminate the
> connection after DISC on dlci6 (but from another side Nokias do not take
> initiative to reconnect to HF device when call is received when
> bluetooth connection is broken, as SE phones do...)
You won't find any written words or hints inside the specification who
is responsible for terminating a connection. I discussed this problem
with a lot of people so far and there is no solution besides accepting
bad implementations.
Actually I asked you for the contents of
/proc/bluetooth/rfcomm/{dlc|sock}
after you ran into the stalled connection. They are really needed,
because it might be a bug with our code that we don't cleanup the mess
of the SE 630.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
parent reply other threads:[~2005-03-02 14:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <C70061B183DE09419568AB2060C52A9518EE74@arion.intra.local>]
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=1109773181.8284.16.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Victor.Shcherbatyuk@tomtom.com \
--cc=bluez-devel@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