public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rswitch in manpage
Date: Mon, 11 Dec 2006 20:16:44 -0700	[thread overview]
Message-ID: <457E1F1C.8090606@xmission.com> (raw)
In-Reply-To: <1165754285.22251.12.camel@aeonflux.holtmann.net>

Marcel

> And again, the link mode is only a policy for the the time when the
> connection will be created. It says nothing about handling role
> switching for the life time of a connection.

This is good information. Making the distinction in the manpage between
establishing and established connections will make it more clear. Does
this look ok?

diff -u -r1.8 hcid.conf.5
--- hcid.conf.5 14 Nov 2006 18:22:37 -0000      1.8
+++ hcid.conf.5 12 Dec 2006 03:02:41 -0000
@@ -182,13 +182,15 @@

 \fInone\fP means no specific policy. \fIaccept\fP means always accept
 incoming connections. \fImaster\fP means become master on incoming
-connections and deny role switch on outgoing connections.
+connections and deny role switch on outgoing connections during
+connection establishment.

 .TP
 \fBlp\fP  none|rswitch,hold,sniff,park

 \fInone\fP means no specific policy. \fIrswitch\fP means allow role
-switch. \fIhold\fP means allow hold mode. \fIsniff\fP means allow
+switch on established connections. \fIhold\fP means allow hold mode.
+\fIsniff\fP means allow
 sniff mode. \fIpark\fP means allow park mode. Several options can be
 combined.

Brad

-------------------------------------------------------------------------
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

      reply	other threads:[~2006-12-12  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 16:22 [Bluez-devel] rswitch in manpage Brad Midgley
2006-12-10 12:38 ` Marcel Holtmann
2006-12-12  3:16   ` Brad Midgley [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=457E1F1C.8090606@xmission.com \
    --to=bmidgley@xmission.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