From bb9aa0cf3e523ce7a01592fc0446bb35458ea1f1 Mon Sep 17 00:00:00 2001
From: Naveen Saini <naveen.kumar.saini@gmail.com>
Date: Fri, 6 May 2022 17:55:09 +0800
Subject: intel-microcode: upgrade 20220207 -> 20220419

Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 recipes-core/microcode/intel-microcode_20220207.bb | 63 ----------------------
 recipes-core/microcode/intel-microcode_20220419.bb | 63 ++++++++++++++++++++++
 2 files changed, 63 insertions(+), 63 deletions(-)
 delete mode 100644 recipes-core/microcode/intel-microcode_20220207.bb
 create mode 100644 recipes-core/microcode/intel-microcode_20220419.bb

diff --git a/recipes-core/microcode/intel-microcode_20220207.bb b/recipes-core/microcode/intel-microcode_20220207.bb
deleted file mode 100644
index 48b21b26..00000000
--- a/recipes-core/microcode/intel-microcode_20220207.bb
+++ /dev/null
@@ -1,63 +0,0 @@
-SUMMARY = "Intel Processor Microcode Datafile for Linux"
-HOMEPAGE = "http://www.intel.com/"
-DESCRIPTION = "The microcode data file contains the latest microcode\
- definitions for all Intel processors. Intel releases microcode updates\
- to correct processor behavior as documented in the respective processor\
- specification updates. While the regular approach to getting this microcode\
- update is via a BIOS upgrade, Intel realizes that this can be an\
- administrative hassle. The Linux operating system and VMware ESX\
- products have a mechanism to update the microcode after booting.\
- For example, this file will be used by the operating system mechanism\
- if the file is placed in the /etc/firmware directory of the Linux system."
-
-LICENSE = "Intel-Microcode-License"
-LIC_FILES_CHKSUM = "file://license;md5=d8405101ec6e90c1d84b082b0c40c721"
-
-SRC_URI = "git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https;branch=main \
-           "
-
-SRCREV = "115c3e4cdad6a9d84bf06e066162c5c546a9d2c3"
-
-DEPENDS = "iucode-tool-native"
-S = "${WORKDIR}/git"
-
-COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-inherit deploy
-
-# Use any of the iucode_tool parameters to filter specific microcodes from the data file
-# For further information, check the iucode-tool's manpage : http://manned.org/iucode-tool
-UCODE_FILTER_PARAMETERS ?= ""
-
-do_compile() {
-	${STAGING_DIR_NATIVE}${sbindir_native}/iucode_tool \
-		${UCODE_FILTER_PARAMETERS} \
-		--overwrite \
-		--write-earlyfw=${WORKDIR}/microcode_${PV}.cpio \
-		${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/*
-}
-
-do_install() {
-	install -d ${D}${nonarch_base_libdir}/firmware/intel-ucode/
-	${STAGING_DIR_NATIVE}${sbindir_native}/iucode_tool \
-	${UCODE_FILTER_PARAMETERS} \
-	--write-firmware=${D}${nonarch_base_libdir}/firmware/intel-ucode \
-	${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/*
-}
-
-do_deploy() {
-	install -d ${DEPLOYDIR}
-	install ${WORKDIR}/microcode_${PV}.cpio ${DEPLOYDIR}/
-	cd ${DEPLOYDIR}
-	rm -f microcode.cpio
-	ln -sf microcode_${PV}.cpio microcode.cpio
-}
-
-addtask deploy before do_build after do_compile
-
-PACKAGES = "${PN}"
-
-FILES:${PN} = "${nonarch_base_libdir}"
-
-UPSTREAM_CHECK_GITTAGREGEX = "^microcode-(?P<pver>(\d+)[a-z]*)$"
diff --git a/recipes-core/microcode/intel-microcode_20220419.bb b/recipes-core/microcode/intel-microcode_20220419.bb
new file mode 100644
index 00000000..1281266e
--- /dev/null
+++ b/recipes-core/microcode/intel-microcode_20220419.bb
@@ -0,0 +1,63 @@
+SUMMARY = "Intel Processor Microcode Datafile for Linux"
+HOMEPAGE = "http://www.intel.com/"
+DESCRIPTION = "The microcode data file contains the latest microcode\
+ definitions for all Intel processors. Intel releases microcode updates\
+ to correct processor behavior as documented in the respective processor\
+ specification updates. While the regular approach to getting this microcode\
+ update is via a BIOS upgrade, Intel realizes that this can be an\
+ administrative hassle. The Linux operating system and VMware ESX\
+ products have a mechanism to update the microcode after booting.\
+ For example, this file will be used by the operating system mechanism\
+ if the file is placed in the /etc/firmware directory of the Linux system."
+
+LICENSE = "Intel-Microcode-License"
+LIC_FILES_CHKSUM = "file://license;md5=d8405101ec6e90c1d84b082b0c40c721"
+
+SRC_URI = "git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https;branch=main \
+           "
+
+SRCREV = "686ce069071329fce724ce90bf5854a3b86e500a"
+
+DEPENDS = "iucode-tool-native"
+S = "${WORKDIR}/git"
+
+COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+inherit deploy
+
+# Use any of the iucode_tool parameters to filter specific microcodes from the data file
+# For further information, check the iucode-tool's manpage : http://manned.org/iucode-tool
+UCODE_FILTER_PARAMETERS ?= ""
+
+do_compile() {
+	${STAGING_DIR_NATIVE}${sbindir_native}/iucode_tool \
+		${UCODE_FILTER_PARAMETERS} \
+		--overwrite \
+		--write-earlyfw=${WORKDIR}/microcode_${PV}.cpio \
+		${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/*
+}
+
+do_install() {
+	install -d ${D}${nonarch_base_libdir}/firmware/intel-ucode/
+	${STAGING_DIR_NATIVE}${sbindir_native}/iucode_tool \
+	${UCODE_FILTER_PARAMETERS} \
+	--write-firmware=${D}${nonarch_base_libdir}/firmware/intel-ucode \
+	${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/*
+}
+
+do_deploy() {
+	install -d ${DEPLOYDIR}
+	install ${WORKDIR}/microcode_${PV}.cpio ${DEPLOYDIR}/
+	cd ${DEPLOYDIR}
+	rm -f microcode.cpio
+	ln -sf microcode_${PV}.cpio microcode.cpio
+}
+
+addtask deploy before do_build after do_compile
+
+PACKAGES = "${PN}"
+
+FILES:${PN} = "${nonarch_base_libdir}"
+
+UPSTREAM_CHECK_GITTAGREGEX = "^microcode-(?P<pver>(\d+)[a-z]*)$"
-- 
cgit v1.2.3-54-g00ecf