From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Connection with a phonestaysopenafterclosingRFCOMM channel
Date: Thu, 03 Mar 2005 00:54:37 +0100 [thread overview]
Message-ID: <1109807677.8284.41.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.44.0503022328530.31250-100000@antilope>
Hi Victor,
> 2.6.10-mh4 - did not help
so this is still a problem with the current Bluetooth subsystem.
> lsmod - /proc/modules is empty, but i have no modules (everything i
> need is compiled into kernel)...
Too bad, because I don't know of any other way to check the module
reference counting. If there is something wrong we would be sure that I
have to look for that.
> l2cap:
> 72:FF:28:C6:10:00 42:E4:11:DE:0F:00 1 3 0x0040 0x0043 1024 251 0x0
> 00:00:00:00:00:00 00:00:00:00:00:00 4 19 0x0000 0x0000 48 48 0x0
> 00:00:00:00:00:00 00:00:00:00:00:00 4 17 0x0000 0x0000 48 48 0x0
> 00:00:00:00:00:00 00:00:00:00:00:00 4 1 0x0000 0x0000 672 0 0x0
> 00:00:00:00:00:00 00:00:00:00:00:00 4 3 0x0000 0x0000 1024 0 0x0
The L2CAP PSM 3 for RFCOMM is still connected. It's actually that what I
expected.
> Am I missing something?
No, because we should simply close the DLCI 0 when no other RFCOMM
channel is open.
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
prev parent reply other threads:[~2005-03-02 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 22:58 [Bluez-devel] Connection with a phonestaysopenafterclosingRFCOMM channel Victor Shcherbatyuk
2005-03-02 23:54 ` 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=1109807677.8284.41.camel@pegasus \
--to=marcel@holtmann.org \
--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