From: prathibhamadugonde <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] cd6e34: monitor: Add support for Ranging Service (RAS) Imp...
Date: Fri, 23 Jan 2026 03:21:19 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1046215/000000-cd6e34@github.com> (raw)
Branch: refs/heads/1046215
Home: https://github.com/bluez/bluez
Commit: cd6e34b9c951dc1210c98ccb256fc99eef85d49e
https://github.com/bluez/bluez/commit/cd6e34b9c951dc1210c98ccb256fc99eef85d49e
Author: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
Date: 2026-01-23 (Fri, 23 Jan 2026)
Changed paths:
M monitor/att.c
M src/shared/util.c
Log Message:
-----------
monitor: Add support for Ranging Service (RAS) Implement comprehensive decoding support for the Bluetooth Ranging Service (RAS) in the ATT monitor, including:
- RAS Features characteristic (0x2c14) with feature bitfield decoding
- Real-time and On-demand Ranging Data characteristics (0x2c15, 0x2c16)
with segmentation header, ranging header, and subevent header parsing
- RAS Control Point (0x2c17) with command opcodes:
* Get Ranging Data
* ACK Ranging Data
* Retrieve Lost Ranging Data Segments
* Abort Operation
* Set Filter
- RAS Ranging Data Ready (0x2c18) and Data Overwritten (0x2c19)
notification characteristics
Also add RAS service and characteristic UUIDs to the shared UUID table.
This enables btmon to properly decode and display RAS protocol
operations for debugging and analysis of Bluetooth ranging
implementations.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-01-23 11:21 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/1046215/000000-cd6e34@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