From: silviubarbulescu <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] eeb349: shared/bap: Split unicast and broadcast structures
Date: Wed, 07 Jun 2023 17:31:39 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/08d627-303088@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: eeb349bbab8662d78fa49ce439af632dd313ff50
https://github.com/bluez/bluez/commit/eeb349bbab8662d78fa49ce439af632dd313ff50
Author: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Date: 2023-06-07 (Wed, 07 Jun 2023)
Changed paths:
M profiles/audio/bap.c
M profiles/audio/media.c
M profiles/audio/transport.c
M src/shared/bap.c
M src/shared/bap.h
M unit/test-bap.c
Log Message:
-----------
shared/bap: Split unicast and broadcast structures
This splits bt_bap_qos structure into unicast and broadcast structures.
Commit: eb821743f9bfd142a3b5c8b9c5a6e9b308709fce
https://github.com/bluez/bluez/commit/eb821743f9bfd142a3b5c8b9c5a6e9b308709fce
Author: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Date: 2023-06-07 (Wed, 07 Jun 2023)
Changed paths:
M client/player.c
Log Message:
-----------
client/player: Add support for broadcast source
This adds bluetoothctl support for broadcast source.
To test the current implementation use bluetoothctl with the commands:
endpoint.register 00001852-0000-1000-8000-00805f9b34fb 0x06
endpoint.config <created endpoint> <local endpoint> 16_2_1
transport.acquire <created transport>
transport.send <created transport> <file.wav>
Commit: d15d9669ce4483023e75f272faab21ba8c9991d1
https://github.com/bluez/bluez/commit/d15d9669ce4483023e75f272faab21ba8c9991d1
Author: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Date: 2023-06-07 (Wed, 07 Jun 2023)
Changed paths:
M src/shared/bap.c
M src/shared/bap.h
Log Message:
-----------
shared/bap: Add initial code for BAP broadcast source
This adds initial support for BAP broadcast source.
Commit: 3030883005c02c77766e1a27a8d5c4d579daa9b5
https://github.com/bluez/bluez/commit/3030883005c02c77766e1a27a8d5c4d579daa9b5
Author: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Date: 2023-06-07 (Wed, 07 Jun 2023)
Changed paths:
M profiles/audio/bap.c
M profiles/audio/media.c
M profiles/audio/media.h
M profiles/audio/transport.c
Log Message:
-----------
bap: Add broadcast source support
This updates BAP plugin with broadcast source support.
Compare: https://github.com/bluez/bluez/compare/08d62744ce17...3030883005c0
reply other threads:[~2023-06-08 0:31 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/master/08d627-303088@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;
as well as URLs for NNTP newsgroup(s).