public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: amateur <ztl.post@gmail.com>,
	BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [Bluez-devel] How to setup a reliable RFCOMM	connection
Date: Sun, 10 Dec 2006 13:39:32 +0100	[thread overview]
Message-ID: <1165754372.22251.14.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20061209015000.GD3119@163.com>

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?

this won't fly. The underlaying L2CAP connection must be reliable and so
we are not using an automatic flush timeout at all for that channel.
Please check the specification for details.

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

  reply	other threads:[~2006-12-10 12:39 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
2006-12-10 12:39     ` Marcel Holtmann [this message]
2006-12-10 14:10       ` [Bluez-users] [Bluez-devel] " 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=1165754372.22251.14.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=ztl.post@gmail.com \
    /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