From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: bluez: dbus method call for switching endpoint
Date: Fri, 28 Dec 2018 21:11:02 +0200 [thread overview]
Message-ID: <20181228191102.GA31975@reaktio.net> (raw)
In-Reply-To: <CABBYNZLK4tyL8nvWbXxr6VctyEyJkMdwNiWMy4gUge9h9Vb4SQ@mail.gmail.com>
Hi Luiz,
On Tue, Dec 18, 2018 at 01:02:39PM -0300, Luiz Augusto von Dentz wrote:
> Hi Pali,
>
> On Sat, Dec 15, 2018 at 5:29 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > On Wednesday 11 July 2018 16:45:01 Pali Rohár wrote:
> > > On Wednesday 11 July 2018 16:27:07 Luiz Augusto von Dentz wrote:
> > > > One way to solve all of these is that we would expose the remote
> > > > endpoints using MediaEndpoint1
> > >
> > > So client application (like pulseadio) would see list of remote
> > > endpoints (one for each codec) and choose one for connection?
> > >
> > > Looks like this should solve this problem.
> >
> > Are there any progress on such API in bluez?
> >
> > On pulseaudio mailing list other people proposed patches for other A2DP
> > codecs and basically bluez API for choosing A2DP codec is still missing
> > part...
>
> Im currenlty on vacation but will try to find time for that, that said
> that shouldn't stop us to include support for other codecs, the last
> set seems to have some sort of priority for ordering the registration
> of the codecs.
>
Let us know when you have something to see/try!
I'm happy to do testing of the patches.
People are currently eager to get support for multiple BT audio codecs working and merged upstream :)
Thanks,
-- Pasi
next prev parent reply other threads:[~2018-12-28 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 8:23 bluez: dbus method call for switching endpoint Pali Rohár
2018-07-11 13:27 ` Luiz Augusto von Dentz
2018-07-11 14:45 ` Pali Rohár
2018-12-15 20:29 ` Pali Rohár
2018-12-18 16:02 ` Luiz Augusto von Dentz
2018-12-28 19:11 ` Pasi Kärkkäinen [this message]
2018-12-28 22:10 ` Luiz Augusto von Dentz
2018-12-29 13:08 ` Pali Rohár
2019-01-08 16:44 ` Luiz Augusto von Dentz
2019-01-08 16:51 ` Pali Rohár
2019-01-08 16:56 ` Pali Rohár
2019-01-09 18:03 ` Pali Rohár
2019-01-09 18:14 ` Pali Rohár
2019-01-10 11:29 ` Luiz Augusto von Dentz
2019-01-10 11:59 ` Pali Rohár
2019-01-26 10:15 ` Pali Rohár
2019-01-19 17:15 ` 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=20181228191102.GA31975@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).