From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] intel-microcode: update to 20191112
Date: Wed, 13 Nov 2019 19:18:00 +0000 [thread overview]
Message-ID: <1885d862-fea5-3c8c-c0d7-aefca373280e@ipfire.org> (raw)
In-Reply-To: <1bd3715b-e3c3-4370-d6f5-1623b125e139@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
For release notes, refer to:
- https://blogs.intel.com/technology/2019/11/ipas-november-2019-intel-platform-update-ipu/
- https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20191112
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/rootfiles/core/138/filelists/i586/intel-microcode | 1 +
config/rootfiles/core/138/filelists/x86_64/intel-microcode | 1 +
lfs/intel-microcode | 6 +++---
3 files changed, 5 insertions(+), 3 deletions(-)
create mode 120000 config/rootfiles/core/138/filelists/i586/intel-microcode
create mode 120000 config/rootfiles/core/138/filelists/x86_64/intel-microcode
diff --git a/config/rootfiles/core/138/filelists/i586/intel-microcode b/config/rootfiles/core/138/filelists/i586/intel-microcode
new file mode 120000
index 000000000..12bdac8bd
--- /dev/null
+++ b/config/rootfiles/core/138/filelists/i586/intel-microcode
@@ -0,0 +1 @@
+../../../../config/rootfiles/common/i586/intel-microcode
\ No newline at end of file
diff --git a/config/rootfiles/core/138/filelists/x86_64/intel-microcode b/config/rootfiles/core/138/filelists/x86_64/intel-microcode
new file mode 120000
index 000000000..0c7158465
--- /dev/null
+++ b/config/rootfiles/core/138/filelists/x86_64/intel-microcode
@@ -0,0 +1 @@
+../../../../config/rootfiles/common/x86_64/intel-microcode
\ No newline at end of file
diff --git a/lfs/intel-microcode b/lfs/intel-microcode
index e01ea9934..c50e73d11 100644
--- a/lfs/intel-microcode
+++ b/lfs/intel-microcode
@@ -24,10 +24,10 @@
include Config
-VER = 20190618
+VER = 20191112
THISAPP = Intel-Linux-Processor-Microcode-Data-Files-microcode-$(VER)
-DL_FILE = $(THISAPP).tar.xz
+DL_FILE = $(THISAPP).tar.gz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 18af9bd8b6c7164f0cd917080a387244
+$(DL_FILE)_MD5 = b215c5a8fd438afd867d8a42d01e27f6
install : $(TARGET)
--
2.16.4
next prev parent reply other threads:[~2019-11-13 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 17:57 Currently working on new intel-microcode package version Peter Müller
2019-11-13 19:18 ` Peter Müller [this message]
2019-11-14 12:24 ` [PATCH] intel-microcode: update to 20191112 Michael Tremer
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=1885d862-fea5-3c8c-c0d7-aefca373280e@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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