From 2e47b48e5d1dead0b5a85e001ee8ad14dd341a6f Mon Sep 17 00:00:00 2001
From: Anuj Mittal <anuj.mittal@intel.com>
Date: Wed, 19 Jun 2019 11:18:39 +0800
Subject: intel-microcode: upgrade 20190514a -> 20190618

For changes in this version, see:

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/940d904b7272edd689a5f0eef9dee09c13746748/releasenote

Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 .../microcode/intel-microcode_20190514a.bb         | 68 ----------------------
 1 file changed, 68 deletions(-)
 delete mode 100644 recipes-core/microcode/intel-microcode_20190514a.bb

(limited to 'recipes-core/microcode/intel-microcode_20190514a.bb')

diff --git a/recipes-core/microcode/intel-microcode_20190514a.bb b/recipes-core/microcode/intel-microcode_20190514a.bb
deleted file mode 100644
index aec3c2a5..00000000
--- a/recipes-core/microcode/intel-microcode_20190514a.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=99b296eb12723fd1eeb52e24971eed84"
-
-SRC_URI = "git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https \
-           "
-
-SRCREV = "1dd14da6d1ea5cfbd95923653f31c04aac3aa655"
-
-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}${base_libdir}/firmware/intel-ucode/
-	install ${WORKDIR}/microcode_${PV}.bin ${D}${base_libdir}/firmware/intel-ucode/
-	cd ${D}${base_libdir}/firmware/intel-ucode/
-	ln -sf microcode_${PV}.bin microcode.bin
-}
-
-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} = "${base_libdir}"
-
-UPSTREAM_CHECK_GITTAGREGEX = "^microcode-(?P<pver>(\d+)[a-z])$"
-- 
cgit v1.2.3-54-g00ecf