From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 70d281: monitor: Add definitions for FSU command and event
Date: Tue, 13 May 2025 10:59:43 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/962526/000000-b4bd32@github.com> (raw)
Branch: refs/heads/962526
Home: https://github.com/bluez/bluez
Commit: 70d281fb1350cf7c6d903a6bc6e5632652e78955
https://github.com/bluez/bluez/commit/70d281fb1350cf7c6d903a6bc6e5632652e78955
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-05-13 (Tue, 13 May 2025)
Changed paths:
M monitor/bt.h
Log Message:
-----------
monitor: Add definitions for FSU command and event
This adds FSU command and event as defined in the Core 6.0
specification.
Commit: b4bd3281429d9fcd14939c24a0aca5fd6721428f
https://github.com/bluez/bluez/commit/b4bd3281429d9fcd14939c24a0aca5fd6721428f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-05-13 (Tue, 13 May 2025)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Add decoding for FSU command and event
This adds decoding for FSU command and event as defined in the Bluetooth
Core 6.0 specification:
$ tools/hcitool cmd 0x08 0x009d 0xff 0xff 0x00 0x00 0x00 0x00 0x01 0x03
< HCI Command: LE Frame Space Update (0x08|0x009d) plen 8
Handle: 65535 Address: 00:00:00:00:00:00 (OUI 00-00-00)
Frame Space min: 0 us (0x0000)
Frame Space max: 0 us (0x0000)
PHYs: LE 1M (0x01)
types: 0x03
T_IFS_ACL_CP
T_IFS_ACL_PC
Compare: https://github.com/bluez/bluez/compare/70d281fb1350%5E...b4bd3281429d
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-13 17:59 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/962526/000000-b4bd32@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.