From: amateur <ztl.post@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>,
bluez-devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [Bluez-users] How to setup a reliable RFCOMM connection
Date: Sat, 9 Dec 2006 09:50:00 +0800 [thread overview]
Message-ID: <20061209015000.GD3119@163.com> (raw)
In-Reply-To: <1165573471.5529.24.camel@aeonflux.holtmann.net>
On Fri, Dec 08, 2006 at 11:24:31AM +0100, Marcel Holtmann wrote:
> Hi,
>
> > How to setup a reliable RFCOMM connection, that is, a connection with
> > infinite flush timeout. I find the RFCOMM_LM_RELIABLE option in the
> > example program l2test.c. It compiles, but at runtime setsockopt with
> > RFCOMM_LM give me an error. I'm using kernel-2.4.21 patched by
> > patch-2.4.21-mh10. So what's the problem. Doesn't kernel-2.4.21-mh10
> > support RFCOMM_LM? If so, how can I setup a reliable RFCOMM connection?
>
> the RFCOMM channels are always reliable. No need for any other options.
>
Does that mean that the Automatic Flush Timeout Timer for the L2CAP
connection underlying the RFCOMM connection is set to 0xFFFF by
default? And when does the RFCOMM_LM option introduced?
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-09 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 8:45 [Bluez-users] How to setup a reliable RFCOMM connection amateur
2006-12-08 10:24 ` [Bluez-devel] " Marcel Holtmann
2006-12-09 1:50 ` amateur [this message]
2006-12-10 12:39 ` [Bluez-users] [Bluez-devel] " Marcel Holtmann
2006-12-10 14:10 ` amateur
2006-12-10 14:18 ` [Bluez-devel] [Bluez-users] " Marcel Holtmann
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=20061209015000.GD3119@163.com \
--to=ztl.post@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.