From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-bluetooth@vger.kernel.org,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: bluez - check for new a2dp features
Date: Mon, 13 May 2019 19:05:50 +0200 [thread overview]
Message-ID: <20190513170550.bsbr2mh7w36hj7io@pali> (raw)
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Hello!
In current git bluez master repository are new features related to A2DP.
E.g. support for codec switching or fallback to other local dbus
endpoints when current selected rejected connection...
Moreover codec switching support is behind experimental runtime switch.
For pulseaudio a2dp module I need to do runtime check if above features
are supported by currently running bluez instance (which registered to
dbus org.bluez. It is needed to ensure that pulseaudio does not
introduce regression for older bluez version without above new A2DP
features.
But currently I have not found any way how to detect if bluez supports
codec switching or if it has support for trying another local SEP for
connection.
So, could you please export e.g. bluez version as dbus property? And
also property if codec switching is supported and enabled by that
experimental flag?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-05-13 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 17:05 Pali Rohár [this message]
2019-06-07 12:58 ` bluez - check for new a2dp features Pali Rohár
2019-06-07 15:26 ` Luiz Augusto von Dentz
2019-06-07 15:37 ` Pali Rohár
2019-06-08 10:56 ` Luiz Augusto von Dentz
2019-06-08 10:59 ` Pali Rohár
2019-06-08 11:15 ` Pali Rohár
2019-06-22 16:18 ` Pali Rohár
2019-06-22 17:01 ` Luiz Augusto von Dentz
2019-06-22 17:09 ` Pali Rohár
2019-07-03 12:56 ` Pali Rohár
2019-07-03 13:26 ` Luiz Augusto von Dentz
2019-07-03 13:30 ` 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=20190513170550.bsbr2mh7w36hj7io@pali \
--to=pali.rohar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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