linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 3c046e: monitor: Add decoding support for LL Extended Feat...
Date: Thu, 30 Oct 2025 12:53:18 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1017886/000000-1a9f88@github.com> (raw)

  Branch: refs/heads/1017886
  Home:   https://github.com/bluez/bluez
  Commit: 3c046e5ff7f7092170f5603f4ec429fac1d74518
      https://github.com/bluez/bluez/commit/3c046e5ff7f7092170f5603f4ec429fac1d74518
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-10-30 (Thu, 30 Oct 2025)

  Changed paths:
    M monitor/bt.h
    M monitor/packet.c

  Log Message:
  -----------
  monitor: Add decoding support for LL Extended Feature Set

This adds support for decoding LL Extended Feature Set introduced in 6.0
that adds the following:

Commands:

 - HCI_LE_Read_All_Local_Supported_­Features(0x2087)(Feature:47,1)
 - HCI_LE_Read_All_Remote_Features(0x2088)(Feature:47,2)

Events:

 - HCI_LE_Read_All_Remote_Features_Complete(0x2b)(Mask bit:42)


  Commit: 1a9f88452d23aff75adff896bed064ec0e6c0c77
      https://github.com/bluez/bluez/commit/1a9f88452d23aff75adff896bed064ec0e6c0c77
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-10-30 (Thu, 30 Oct 2025)

  Changed paths:
    M monitor/bt.h
    M monitor/ll.c
    M monitor/packet.c
    M monitor/packet.h

  Log Message:
  -----------
  monitor: Add decoding support for LL_FEATURE_EXT_{REQ,RSP}

This adds support for LL_FEATURE_EXT_{REQ,RSP} which is used to
exchange LL Features.


Compare: https://github.com/bluez/bluez/compare/3c046e5ff7f7%5E...1a9f88452d23

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2025-10-30 19:53 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/1017886/000000-1a9f88@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).