From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fd9000: monitor: Print data if LTV and data length don't m...
Date: Wed, 22 Oct 2025 11:27:48 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1014654/000000-fd9000@github.com> (raw)
Branch: refs/heads/1014654
Home: https://github.com/bluez/bluez
Commit: fd9000c2076e3184caed19e4e147b8f5140cfaa9
https://github.com/bluez/bluez/commit/fd9000c2076e3184caed19e4e147b8f5140cfaa9
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-22 (Wed, 22 Oct 2025)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Print data if LTV and data length don't match
If data length and LTV don't match this should be made visible so
issues like the data coming as all zeros as bellow can be detected:
> HCI Event: LE Meta Event (0x3e) plen 50
LE Periodic Advertising Report (0x0f)
Sync handle: 64
TX power: 127 dbm (0x7f)
RSSI: -55 dBm (0xc9)
CTE Type: No Constant Tone Extension (0xff)
Data status: Complete
Data length: 0x2a
Versus:
> HCI Event: LE Meta Event (0x3e) plen 50
LE Periodic Advertising Report (0x0f)
Sync handle: 64
TX power: 127 dbm (0x7f)
RSSI: -55 dBm (0xc9)
CTE Type: No Constant Tone Extension (0xff)
Data status: Complete
Data length: 0x2a
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 ..........
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-22 18:27 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/1014654/000000-fd9000@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).