From: John Allen <john.allen@amd.com>
To: <linux-firmware@kernel.org>, <jwboyer@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, John Allen <john.allen@amd.com>
Subject: [PATCH] Add amd-ucode README file
Date: Tue, 9 Aug 2022 20:29:50 +0000 [thread overview]
Message-ID: <20220809202950.297935-1-john.allen@amd.com> (raw)
Create new README file describing the microcode patch levels included in the
microcode container files in the amd-ucode directory.
Signed-off-by: John Allen <john.allen@amd.com>
---
amd-ucode/README | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 amd-ucode/README
diff --git a/amd-ucode/README b/amd-ucode/README
new file mode 100644
index 0000000..f1ad2bb
--- /dev/null
+++ b/amd-ucode/README
@@ -0,0 +1,41 @@
+This repository includes microcode container files for family 15h, 16h,
+17h, and 19h AMD CPUs. Microcode patches for families earlier than 15h are
+included in the microcode_amd.bin microcode container file. The microcode
+patches included in an AMD CPU microcode container file can be listed using
+the script in the following git repository:
+https://github.com/AMDESE/amd_ucode_info
+
+The microcode patches included in the container files in this directory are
+listed below:
+
+Microcode patches in microcode_amd.bin:
+ Family=0x10 Model=0x02 Stepping=0x02: Patch=0x01000083 Length=960 bytes
+ Family=0x10 Model=0x02 Stepping=0x0a: Patch=0x01000084 Length=960 bytes
+ Family=0x10 Model=0x06 Stepping=0x02: Patch=0x010000c7 Length=960 bytes
+ Family=0x10 Model=0x05 Stepping=0x03: Patch=0x010000c8 Length=960 bytes
+ Family=0x10 Model=0x09 Stepping=0x01: Patch=0x010000d9 Length=960 bytes
+ Family=0x10 Model=0x08 Stepping=0x00: Patch=0x010000da Length=960 bytes
+ Family=0x10 Model=0x05 Stepping=0x02: Patch=0x010000db Length=960 bytes
+ Family=0x10 Model=0x0a Stepping=0x00: Patch=0x010000dc Length=960 bytes
+ Family=0x11 Model=0x03 Stepping=0x01: Patch=0x02000032 Length=512 bytes
+ Family=0x12 Model=0x01 Stepping=0x00: Patch=0x03000027 Length=960 bytes
+ Family=0x14 Model=0x01 Stepping=0x00: Patch=0x05000029 Length=1568 bytes
+ Family=0x14 Model=0x02 Stepping=0x00: Patch=0x05000119 Length=1568 bytes
+
+Microcode patches in microcode_amd_fam15h.bin:
+ Family=0x15 Model=0x01 Stepping=0x02: Patch=0x0600063e Length=2592 bytes
+ Family=0x15 Model=0x02 Stepping=0x00: Patch=0x06000852 Length=2592 bytes
+ Family=0x15 Model=0x10 Stepping=0x01: Patch=0x06001119 Length=2592 bytes
+
+Microcode patches in microcode_amd_fam16h.bin:
+ Family=0x16 Model=0x00 Stepping=0x01: Patch=0x0700010f Length=3458 bytes
+
+Microcode patches in microcode_amd_fam17h.bin:
+ Family=0x17 Model=0x08 Stepping=0x02: Patch=0x0800820d Length=3200 bytes
+ Family=0x17 Model=0x01 Stepping=0x02: Patch=0x0800126e Length=3200 bytes
+ Family=0x17 Model=0x31 Stepping=0x00: Patch=0x08301055 Length=3200 bytes
+
+Microcode patches in microcode_amd_fam19h.bin:
+ Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001058 Length=5568 bytes
+ Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a001173 Length=5568 bytes
+ Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001229 Length=5568 bytes
--
2.25.1
reply other threads:[~2022-08-09 20:30 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=20220809202950.297935-1-john.allen@amd.com \
--to=john.allen@amd.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®