From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: bluez A2DP socket reliability
Date: Sat, 18 May 2019 21:06:18 +0200 [thread overview]
Message-ID: <20190518190618.m7rdkthvpz4agxd2@pali> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
transfer configured in bluez? It is reliable with big/infinite
retransmit count? Or in best-effort manner and some packets may be
dropped? And it is possible to change between these two modes for
application which uses bluez DBUS API? I'm asking because some A2DP
audio codecs are designed to deal with packet loss and for those codecs
it would be probably better to configure L2CAP socket to unreliable
mode.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-05-18 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 19:06 Pali Rohár [this message]
2019-05-19 8:13 ` bluez A2DP socket reliability Luiz Augusto von Dentz
2019-05-19 12:22 ` Pali Rohár
2019-06-07 13:00 ` Pali Rohár
2019-06-07 15:23 ` Luiz Augusto von Dentz
2019-06-10 10:51 ` Pali Rohár
2019-06-10 12:16 ` Luiz Augusto von Dentz
2019-06-10 16:06 ` Frédéric Danis
2019-06-14 7:16 ` Pali Rohár
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=20190518190618.m7rdkthvpz4agxd2@pali \
--to=pali.rohar@gmail.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).