From: Kiran K <kiran.k@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: ravishankar.srivatsa@intel.com, chethan.tumkur.narayan@intel.com,
Kiran K <kiran.k@intel.com>
Subject: [PATCH v1] monitor/intel: Add decoding of firmware SHA1 in read version event
Date: Wed, 28 Feb 2024 14:55:04 +0530 [thread overview]
Message-ID: <20240228092504.3716904-1-kiran.k@intel.com> (raw)
< HCI Command: Intel Read Version (0x3f|0x0005) plen 1
Requested Type:
All Supported Types(0xff)
> HCI Event: Command Complete (0x0e) plen 107
Intel Read Version (0x3f|0x0005) ncmd 1
Status: Success (0x00)
CNVi TOP(16): 0x00400410
CNVr TOP(17): 0x00400410
CNVi BT(18): 0x00173700
CNVr BT(19): 0x00123720
CNVr OTP(21): 0x0413
Device Rev ID(22): 0x0000
USB VID(23): 0x8087
USB PID(24): 0x0032
Image Type(28): Firmware(0x03)
Time Stamp(29): 23-42
Build Type(30): 0x01
Build Num(31): 0x00011d97
FW Build Product(32): 0x06
FW Build HW(33): 0x06
FW Build Step(34): 0xa0
BT Spec(35): 0x00
Manufacturer(36): Intel Corp. (2)
HCI Revision(37): 0x3597
LMP SubVersion(38): 0x3597
OTP Lock(42): Disabled(0)
API Lock(43): Disabled(0)
Firmware SHA1(50): 0x2e575f2a
Unknown Type(51):
00
Unknown Type(52):
Unknown Type(53):
00 00 00 00
---
monitor/intel.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/monitor/intel.c b/monitor/intel.c
index 0de864d8a41e..aa05a803bf8e 100644
--- a/monitor/intel.c
+++ b/monitor/intel.c
@@ -291,6 +291,7 @@ static const struct intel_version_tlv_desc {
{ 47, "SBE Type", print_version_tlv_u8 },
{ 48, "OTP BDADDR", print_version_tlv_otp_bdaddr },
{ 49, "Unlocked State", print_version_tlv_enabled },
+ { 50, "Firmware SHA1", print_version_tlv_u32 },
{ 0, NULL, NULL },
};
--
2.34.1
next reply other threads:[~2024-02-28 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 9:25 Kiran K [this message]
2024-02-28 10:32 ` [v1] monitor/intel: Add decoding of firmware SHA1 in read version event bluez.test.bot
2024-03-12 5:12 ` [PATCH v1] " K, Kiran
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=20240228092504.3716904-1-kiran.k@intel.com \
--to=kiran.k@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.com \
/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.