From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 032ea0: monitor: Decode Intel DDC LE extended features
Date: Thu, 30 Jul 2026 12:01:00 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1137629/000000-032ea0@github.com> (raw)
Branch: refs/heads/1137629
Home: https://github.com/bluez/bluez
Commit: 032ea05b41638c34a105bc2665fb495ec25faa82
https://github.com/bluez/bluez/commit/032ea05b41638c34a105bc2665fb495ec25faa82
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-07-30 (Thu, 30 Jul 2026)
Changed paths:
M monitor/intel.c
Log Message:
-----------
monitor: Decode Intel DDC LE extended features
The Intel DDC Config Write command (0x3f|0x008b) can carry identifier
0x031f which holds the 248 octet LE extended features array, using the
same layout as LE Read All Local Features: page 0 is 8 octets followed
by 10 pages of 24 octets each.
Decode it with the existing LE feature tables instead of dumping raw
hex, and make the parameter loop stop on truncated/padded entries.
Example, setting only the SCI bits on page 1 (bits 8 and 9):
hcitool cmd 0x3F 0x008B 0xFA 0x1F 0x03 \
0xFF 0xF9 0x01 0x3F 0xBE 0x00 0x00 0x80 \
0x00 0x03 0x00 0x00 ... (padding up to 248 octets)
< HCI Command: Intel DDC Config Write (0x3f|0x008b) plen 251
Identifier: 0x031f
Features[0/0][8]:
ff f9 01 3f be 00 00 80 ...?....
LE Encryption
Connection Parameter Request Procedure
...
LL Extended Feature Set
Features[1/0][8]:
00 03 00 00 00 00 00 00 ........
Shorter Connection Intervals
Shorter Connection Intervals (Host Support)
Features[1/1][8]:
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:[~2026-07-30 19:01 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/1137629/000000-032ea0@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