From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method
Date: Fri, 18 Oct 2019 11:37:31 +0300 [thread overview]
Message-ID: <20191018083731.GJ28704@reaktio.net> (raw)
In-Reply-To: <20191017095957.cce7jzejvn76kwkc@pali>
On Thu, Oct 17, 2019 at 11:59:57AM +0200, Pali Rohár wrote:
> > > >
> > > > So... what should applications expects and how they should implement
> > > > above decision?
> > >
> > > Actually the decision should be based on the presence of
> > > RegisterApplication method, if that exists then endpoint switching
> > > should be supported as well, so has nothing to do the
> > > GetManagedObjects API of the bluetoothd. That said RegisterApplication
> > > was not made experimental which kind makes 5.51 broken because it
> > > would appear that it endpoint objects would be exposed but when in
> > > fact there are not, anyway lets finally have the code to use this
> > > interface and then we can remove the experimental flag from
> > > MediaEndpoint.
> >
> > Ok, so can pulseaudio do following?
> >
> > Call RegisterApplication. If success then expects that codec switching
> > is possible and via GetManagedObjects exports all available codecs.
> > If RegisterApplication fails then fallback to RegisterEndpoint, expects
> > that codec switching is not possible and so register only one SBC codec.
>
> Also can we solve this problem in bluez ASAP? Last released bluez
> version is due to that non-experimental API broken and once applications
> (e.g. pulseaudio) starts using this new API then A2DP without bluetoothd
> -E would be broken.
>
> I would propose to remove experimental mark for codec switching API and
> release a new bugfix version of bluez, so people would not use released
> 5.51 broken version... which could prevent breakage of A2DP in future.
>
+1
It would be nice to get bluez 5.52 released before 5.51 gets released by distros..
-- Pasi
next prev parent reply other threads:[~2019-10-18 8:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 15:13 [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 2/4] media: Add implementation of RegisterApplication Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 3/4] test: Add example-endpoint Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 4/4] test: Add example-player Luiz Augusto von Dentz
2019-07-13 14:52 ` [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method Luiz Augusto von Dentz
2019-07-18 10:00 ` Pali Rohár
2019-07-21 15:55 ` Pali Rohár
2019-08-10 6:54 ` Luiz Augusto von Dentz
2019-08-29 12:57 ` Pasi Kärkkäinen
2019-08-29 20:05 ` Pali Rohár
2019-10-03 18:18 ` Pasi Kärkkäinen
2019-10-06 10:05 ` Pali Rohár
2019-10-06 10:53 ` Luiz Augusto von Dentz
2019-10-06 10:56 ` Pali Rohár
2019-10-06 11:14 ` Luiz Augusto von Dentz
2019-10-06 11:17 ` Pali Rohár
2019-10-06 18:02 ` Pali Rohár
2019-10-06 12:02 ` Pali Rohár
2019-10-07 14:33 ` Pali Rohár
2019-10-08 10:28 ` Luiz Augusto von Dentz
2019-10-08 10:33 ` Pali Rohár
2019-10-09 13:15 ` Luiz Augusto von Dentz
2019-10-09 13:19 ` Pali Rohár
2019-10-17 9:59 ` Pali Rohár
2019-10-18 8:37 ` Pasi Kärkkäinen [this message]
2019-10-18 10:55 ` Luiz Augusto von Dentz
2019-10-18 11:30 ` Pali Rohár
2019-10-09 13:20 ` Pali Rohár
2019-11-14 11:27 ` Pali Rohár
2020-04-14 23:07 ` Undocumented property "DelayReporting" (Was: Re: [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method) 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=20191018083731.GJ28704@reaktio.net \
--to=pasik@iki.fi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pali.rohar@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).