Linux-Bluetooth Archive mirror
 help / color / mirror / Atom feed
From: Arun Raghavan <arun@asymptotic.io>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 3/5] test: Add a script to test ASHA
Date: Wed, 8 May 2024 22:20:51 -0400	[thread overview]
Message-ID: <CAN03qa85aUiPMrN-eQ-N1ktoWALDba2qcnW4V3NbvMzhNZ4Krw@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZKzCe-c-JivKC5gT0P0ZKGwXX9DQeEeZmeDvQS3CpyNTw@mail.gmail.com>

On Wed, 8 May 2024 at 12:34, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
[...]
> While I don't mind having a python example I think we are much better
> of adding such support in bluetoothctl, most should already work with
> transport submenu but perhaps we want to add support for gstreamer
> pipeline instead of just a file which would be useful for creating
> A2DP sbc and BAP lc3 streams.

Makes sense, I can take a look at this, but if possible I'd like to
punt this till I get the end-to-end flow working with the PipeWire
BlueZ modules.

Cheers,
Arun

  reply	other threads:[~2024-05-09  2:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 15:45 [PATCH BlueZ 0/5] ASHA plugin Arun Raghavan
2024-05-08 15:46 ` [PATCH BlueZ 1/5] profiles: Add initial code for an " Arun Raghavan
2024-05-08 16:25   ` Luiz Augusto von Dentz
2024-05-09  2:16     ` Arun Raghavan
2024-05-08 17:36   ` bluez.test.bot
2024-05-08 15:46 ` [PATCH BlueZ 2/5] asha: Implement volume on transport Arun Raghavan
2024-05-08 15:46 ` [PATCH BlueZ 3/5] test: Add a script to test ASHA Arun Raghavan
2024-05-08 16:34   ` Luiz Augusto von Dentz
2024-05-09  2:20     ` Arun Raghavan [this message]
2024-05-08 15:46 ` [PATCH BlueZ 4/5] gitignore: Add compile_commands.json Arun Raghavan
2024-05-08 15:46 ` [PATCH BlueZ 5/5] gitignore: Add __pycache__ Arun Raghavan

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=CAN03qa85aUiPMrN-eQ-N1ktoWALDba2qcnW4V3NbvMzhNZ4Krw@mail.gmail.com \
    --to=arun@asymptotic.io \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).