From: Adrian Dudau <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a0533d: tools: Add raw advertising data support to BlueZ
Date: Fri, 10 Oct 2025 07:14:45 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1010113/000000-a0533d@github.com> (raw)
Branch: refs/heads/1010113
Home: https://github.com/bluez/bluez
Commit: a0533d5282ad0e9736990abb81d577737707dc65
https://github.com/bluez/bluez/commit/a0533d5282ad0e9736990abb81d577737707dc65
Author: Adrian Dudau <adrian-constantin.dudau@nxp.com>
Date: 2025-10-10 (Fri, 10 Oct 2025)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
M src/eir.c
M src/eir.h
M src/shared/ad.c
M src/shared/ad.h
M tools/btpclient.c
Log Message:
-----------
tools: Add raw advertising data support to BlueZ
This patch introduces support for storing and exposing raw advertising
data from Bluetooth Low Energy devices through D-Bus properties and
internal APIs.
Key changes:
- Add raw_data fields to eir_data and bt_ad structures
- Implement bt_ad_set_raw_data(), bt_ad_clear_raw_data(),
bt_ad_has_raw_data(), and bt_ad_get_raw_data() APIs
- Expose RawAdvertisingData D-Bus property on device objects
- Store raw advertising data during EIR parsing
- Update BTP client to include raw advertising data in device found events
The RawAdvertisingData property is marked with G_DBUS_PROPERTY_FLAG_TESTING
for debugging and protocol testing purposes. This enables applications to
access complete raw advertising packet contents for custom parsing,
compliance testing, and troubleshooting scenarios.
The raw data format follows the Extended Inquiry Response Data Format
as described in BLUETOOTH CORE SPECIFICATION Version 6.1 | Vol 3, Part C.
Signed-off-by: Adrian Dudau <adrian-constantin.dudau@nxp.com>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-10 14:14 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/1010113/000000-a0533d@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