From: Iain Hibbert <plunky@rya-online.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Link Mode
Date: Sun, 4 Mar 2007 21:58:38 +0000 (GMT) [thread overview]
Message-ID: <1173045518.989564.4714.nullmailer@galant.ukfsn.org> (raw)
Hi,
I am trying to write a compatible equivalent to the Link Mode socket
options API for NetBSD, and I wonder if somebody can clarify some things
for me since I can't find any documentation about this.
I assume that RFCOMM_LM and L2CAP_LM are essentially the same, the
following bits are defined:
_LM_MASTER
means we prefer to be master of the baseband link
_LM_AUTH
means we want the baseband link to be authenticated
_LM_ENCRYPT
means we want the baseband link to be encrypted
_LM_TRUSTED
this seems unused, is there an intention?
_LM_RELIABLE
signal error on unreliable link (means disconnect?)
_LM_SECURE
is this somehow different than (_LM_AUTH | _LM_ENCRYPT)?
thanks,
iain
-------------------------------------------------------------------------
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 reply other threads:[~2007-03-04 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 21:58 Iain Hibbert [this message]
2007-03-05 12:35 ` [Bluez-devel] Link Mode 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=1173045518.989564.4714.nullmailer@galant.ukfsn.org \
--to=plunky@rya-online.net \
--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;
as well as URLs for NNTP newsgroup(s).