From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez - check for new a2dp features
Date: Wed, 3 Jul 2019 14:56:08 +0200 [thread overview]
Message-ID: <20190703125608.nl72umoinhg2kh6k@pali> (raw)
In-Reply-To: <20190622170933.lxuftoxmvtv7ssfo@pali>
On Saturday 22 June 2019 19:09:33 Pali Rohár wrote:
> On Saturday 22 June 2019 20:01:15 Luiz Augusto von Dentz wrote:
> > Hi Pali,
> >
> > I think a better idea would be that we introduce something specific to
> > that, such as the SEID being returned so the next time around you may
> > restore a SEID, this may actually make more sense perhaps if we reuse
> > the RegisterApplication semantics:
> >
> > https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/gatt-api.txt#n464
> >
> > That means it is no longer required to call RegisterEndpoint as many
> > times as there are endpoints since that is time-consuming due to the
> > D-Bus round trips, instead, the endpoint are discovered with the use
> > of ObjectManager, if the method doesn't exist then you just fall back
> > to the old mechanism since it might be an old daemon.
>
> Hi! If I understand it correctly, pulseaudio would register itself via
> new dbus method and bluez daemon then discover A2DP SEP endpoints
> automatically, right? And if that new dbus method does not exist
> pulseaudio would know that in system is running old bluez version
> without codec switching support. Seems it is perfectly fine solution.
Hi Luiz! Do you have some patches ready for testing?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2019-07-03 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 17:05 bluez - check for new a2dp features Pali Rohár
2019-06-07 12:58 ` 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 [this message]
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=20190703125608.nl72umoinhg2kh6k@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;
as well as URLs for NNTP newsgroup(s).