From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d2cf60: doc: describe the true wireless broadcast test cases
Date: Mon, 21 Sep 2026 15:43:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1170704/000000-959a7d@github.com> (raw)
Branch: refs/heads/1170704
Home: https://github.com/bluez/bluez
Commit: d2cf6053569a902f289d8a5c5e721872e8cf35cb
https://github.com/bluez/bluez/commit/d2cf6053569a902f289d8a5c5e721872e8cf35cb
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
M doc/functional-bap.rst
Log Message:
-----------
doc: describe the true wireless broadcast test cases
Assisted-by: opencode:claude-opus-5
Commit: 505336bc3b00a39bd69107662d7fef130fa60805
https://github.com/bluez/bluez/commit/505336bc3b00a39bd69107662d7fef130fa60805
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
M doc/functional-bap.rst
Log Message:
-----------
doc: describe the true wireless broadcast assistant test case
Assisted-by: opencode:claude-opus-5
Commit: dfce14a430df89220e92def94a97410ac0789d68
https://github.com/bluez/bluez/commit/dfce14a430df89220e92def94a97410ac0789d68
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
A client/scripts/broadcast-sink-left.bt
A client/scripts/broadcast-sink-right.bt
M doc/functional-bap.rst
M test/functional/test_bap.py
Log Message:
-----------
test: functional: add the true wireless broadcast tests
Assisted-by: opencode:claude-opus-5
Commit: 07b0f4b52599e558802fe0d0d0b33fd3b01e4855
https://github.com/bluez/bluez/commit/07b0f4b52599e558802fe0d0d0b33fd3b01e4855
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
bass: keep the push target per MediaAssistant object
Every MediaAssistant object of a local broadcast shares the bass_data of
the adapter, and pushing one stored the session of the delegator it was
pushed to by overwriting the bass of that shared data.
With a single delegator this goes unnoticed, but with one delegator per
side of a true wireless pair the second push replaces the target of the
first one, so the Broadcast Code of a request coming from the first
delegator is written to the second one, and the first never syncs.
Keep the session of the push in the assistant itself, and only handle
the changes reported by the delegator an assistant was pushed to.
Assisted-by: opencode:claude-opus-5
Commit: 8eacebfca4f55fbfaef5e70c915e596bd8573957
https://github.com/bluez/bluez/commit/8eacebfca4f55fbfaef5e70c915e596bd8573957
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
M client/main.c
M doc/bluetoothctl.rst
Log Message:
-----------
client: connect a device that is already paired
Pairing a device that is already paired is rejected by the daemon with
AlreadyExists, which is of no use to the user: the bond asked for is
already there, and what pairing it anew takes is removing it first.
Connect it instead, telling what happened, so pairing a device is a way
of getting to it whether it is known already or not.
The documentation already described this behaviour, though as removing
the pairing first, which is not what happened either.
Assisted-by: opencode:claude-opus-5
Commit: 959a7ddc3a87d95d77e071dff27266a2959e5432
https://github.com/bluez/bluez/commit/959a7ddc3a87d95d77e071dff27266a2959e5432
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-21 (Mon, 21 Sep 2026)
Changed paths:
A client/scripts/broadcast-delegator-left.bt
A client/scripts/broadcast-delegator-right.bt
M doc/functional-bap.rst
M test/functional/test_bap.py
Log Message:
-----------
test: functional: add the true wireless broadcast assistant test
Assisted-by: opencode:claude-opus-5
Compare: https://github.com/bluez/bluez/compare/d2cf6053569a%5E...959a7ddc3a87
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-21 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1170704/000000-959a7d@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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