From: Bastien Nocera <hadess@hadess.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs
Date: Wed, 09 Nov 2022 16:55:41 +0100 [thread overview]
Message-ID: <c89bbf14a147ddcecbf52043927cac31e21ee6bf.camel@hadess.net> (raw)
In-Reply-To: <CABBYNZKXvcUjyuf1DzjB=NX1xVt8bynZQ9KNrOOYGQMtPt5PKA@mail.gmail.com>
On Thu, 2022-11-03 at 13:26 -0700, Luiz Augusto von Dentz wrote:
> Hi Bastien,
>
> On Wed, Nov 2, 2022 at 3:22 AM Bastien Nocera <hadess@hadess.net>
> wrote:
> >
> > ---
> > src/main.conf | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/src/main.conf b/src/main.conf
> > index 2796f155e..fbe0a97be 100644
> > --- a/src/main.conf
> > +++ b/src/main.conf
> > @@ -125,6 +125,8 @@
> > # 330859bc-7506-492d-9370-9a6f0614037f (BlueZ Experimental
> > Bluetooth Quality Report)
> > # a6695ace-ee7f-4fb9-881a-5fac66c629af (BlueZ Experimental Offload
> > Codecs)
> > # 6fbaf188-05e0-496a-9885-d6ddfdb4e03e (BlueZ Experimental ISO
> > socket)
> > +# 00002bcb-0000-1000-8000-00805f9b34fb (BlueZ Experimental LE
> > Audio BAP source)
> > +# 00002bc9-0000-1000-8000-00805f9b34fb (BlueZ Experimental LE
> > Audio BAP sink)
> > # Defaults to false.
> > #KernelExperimental = false
>
> Not really following, these UUID are actually part of LE Audio
> standard, they are not experimental, or perhaps you want to document
> what UUIDs can be registered using MediaEndpoint?
I got confused because those UUIDs would show up when I set
"KernelExperimental = true". But that's because those UUIDs in the
audio plugin are dependent on "ISO socket" support which also gets
enabled when "KernelExperimental = true" is set.
Feel free to drop.
next prev parent reply other threads:[~2022-11-09 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 10:12 [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs Bastien Nocera
2022-11-02 11:18 ` bluez.test.bot
2022-11-03 20:26 ` Luiz Augusto von Dentz
2022-11-09 15:55 ` Bastien Nocera [this message]
2022-11-18 2:31 ` bluez.test.bot
2022-11-18 4:05 ` bluez.test.bot
2022-11-18 4:43 ` bluez.test.bot
2022-11-18 5:13 ` bluez.test.bot
2022-11-18 5:33 ` bluez.test.bot
2022-11-18 6:04 ` bluez.test.bot
2022-11-19 3:47 ` bluez.test.bot
2022-11-19 5:32 ` bluez.test.bot
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=c89bbf14a147ddcecbf52043927cac31e21ee6bf.camel@hadess.net \
--to=hadess@hadess.net \
--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