From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9736f3: shared: rap: Introduce Channel Sounding HCI raw in...
Date: Tue, 14 Apr 2026 08:45:06 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1081191/000000-1729f3@github.com> (raw)
Branch: refs/heads/1081191
Home: https://github.com/bluez/bluez
Commit: 9736f3017b53172b929ee0a710eec6b8c23212f2
https://github.com/bluez/bluez/commit/9736f3017b53172b929ee0a710eec6b8c23212f2
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-04-14 (Tue, 14 Apr 2026)
Changed paths:
M src/shared/hci.c
M src/shared/hci.h
M src/shared/rap.c
M src/shared/rap.h
Log Message:
-----------
shared: rap: Introduce Channel Sounding HCI raw interface support
Implement stub callbacks for Channel Sounding HCI events and add the
required protocol definitions for CS configuration, procedure control,
and subevent result parsing
Add data structures to support Channel Sounding Processing
Add helper function to get hci conn info list and integrate it with RAP
Commit: 1729f38c58dfdd3d54034aed674f885f17ef759f
https://github.com/bluez/bluez/commit/1729f38c58dfdd3d54034aed674f885f17ef759f
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-04-14 (Tue, 14 Apr 2026)
Changed paths:
M src/bluetooth.service.in
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
main.conf: Add Channel Sounding config parsing support
Add support for parsing Channel Sounding (CS) configuration options
from the configuration file.
Add CAP_NET_RAW to CapabilityBoundingSet in bluetooth.service.
bluetoothd requires CAP_NET_RAW to receive and process HCI LE events
when running under a constrained systemd capability bounding set
Compare: https://github.com/bluez/bluez/compare/9736f3017b53%5E...1729f38c58df
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-14 15:45 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/1081191/000000-1729f3@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