From 2413398a19c1ac00360ec560dadb4bbe4818f163 Mon Sep 17 00:00:00 2001 From: Anuj Mittal Date: Wed, 10 Jun 2020 08:07:47 +0800 Subject: intel-microcode: upgrade 20200520 -> 20200609 Release notes: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/021c295269a06159b8c3ebefc0fac932e69e259e/releasenote Signed-off-by: Anuj Mittal --- recipes-core/microcode/intel-microcode_20200520.bb | 68 ---------------------- recipes-core/microcode/intel-microcode_20200609.bb | 68 ++++++++++++++++++++++ 2 files changed, 68 insertions(+), 68 deletions(-) delete mode 100644 recipes-core/microcode/intel-microcode_20200520.bb create mode 100644 recipes-core/microcode/intel-microcode_20200609.bb diff --git a/recipes-core/microcode/intel-microcode_20200520.bb b/recipes-core/microcode/intel-microcode_20200520.bb deleted file mode 100644 index 01a72718..00000000 --- a/recipes-core/microcode/intel-microcode_20200520.bb +++ /dev/null @@ -1,68 +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=6b58767419df274d2409b294ddae17e6" - -SRC_URI = "git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https \ - " - -SRCREV = "437f382b1be4412b9d03e2bbdcda46d83d581242" - -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-to=${WORKDIR}/microcode_${PV}.bin \ - ${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/* - - ${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 \ - --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(\d+)[a-z]*)$" diff --git a/recipes-core/microcode/intel-microcode_20200609.bb b/recipes-core/microcode/intel-microcode_20200609.bb new file mode 100644 index 00000000..7b617f15 --- /dev/null +++ b/recipes-core/microcode/intel-microcode_20200609.bb @@ -0,0 +1,68 @@ +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=6b58767419df274d2409b294ddae17e6" + +SRC_URI = "git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https \ + " + +SRCREV = "021c295269a06159b8c3ebefc0fac932e69e259e" + +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-to=${WORKDIR}/microcode_${PV}.bin \ + ${S}/intel-ucode/* ${S}/intel-ucode-with-caveats/* + + ${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 \ + --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(\d+)[a-z]*)$" -- cgit v1.2.3-54-g00ecf