linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grégoire Gentil" <gregoire@gentil.com>
To: linux-bluetooth@vger.kernel.org
Subject: Where is the documentation of l2cap_options?
Date: Fri, 18 May 2018 10:40:01 -0700	[thread overview]
Message-ID: <4afa32dd-c21d-d1a8-b077-470bde05e5cc@gentil.com> (raw)
In-Reply-To: <20161230072113.GA20773@x1c.P-661HNU-F1>

Hello,


I have a couple of questions regarding l2cap_options.

I have posted the main question on Stackoverflow:
https://stackoverflow.com/questions/50380020/where-is-the-documentation-of-l2cap-options


I would like to play with the options of l2cap. But there is no 
documentation even in the kernel header. Where can I find a description 
of the different fields?

On my system, I see:
omtu:0 imtu:672 flush_to:65535 mode:0 fcs:1 max_tx:3 txwin_size:63

I don't understand why omtu is different from imtu. What are the other 
options?


Also, on this page 
https://people.csail.mit.edu/albert/bluez-intro/x95.html#l2cap-and-udp, 
it says that there are three policies possible: never retransmit, 
default, drop and move. How do I select the policy?

I was guessing that the "default" is to have flush timeout of 0 and the 
"drop and move" after x ms is just to put a specific timeout (knowing 
that 1279ms = 0x7ff * 625us). Am I right? But then how do you select 
"never retransmit"?


Grégoire




      reply	other threads:[~2018-05-18 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 23:34 rfcomm without bluetoothd? Grégoire Gentil
2016-12-30  7:21 ` Johan Hedberg
2018-05-18 17:40   ` Grégoire Gentil [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=4afa32dd-c21d-d1a8-b077-470bde05e5cc@gentil.com \
    --to=gregoire@gentil.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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).