From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] intel-ucode: use iucode-tool with earlyfw option
Date: Tue, 16 Jan 2024 18:04:02 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48234@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
There is a new pull request by dkwo against master on the void-packages repository
https://github.com/dkwo/void-packages ucode
https://github.com/void-linux/void-packages/pull/48234
intel-ucode: use iucode-tool with earlyfw option
- I tested the changes in this PR: yes, by `cat ucode old-init > new-init`
- I built this PR locally for my native architecture, (x86_64)
A patch file from https://github.com/void-linux/void-packages/pull/48234.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ucode-48234.patch --]
[-- Type: text/x-diff, Size: 1478 bytes --]
From 2b6797b1afde370b1fb0ea0be0bd34c1fb6e4768 Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Mon, 15 Jan 2024 09:53:13 +0100
Subject: [PATCH] intel-ucode: use iucode-tool with earlyfw option
---
srcpkgs/intel-ucode/template | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/intel-ucode/template b/srcpkgs/intel-ucode/template
index eb4060e3201ca..0b24bbd79f8b4 100644
--- a/srcpkgs/intel-ucode/template
+++ b/srcpkgs/intel-ucode/template
@@ -1,8 +1,9 @@
# Template file for 'intel-ucode'
pkgname=intel-ucode
version=20231114
-revision=1
+revision=2
archs="i686* x86_64*"
+hostmakedepends="iucode-tool"
short_desc="Microcode update files for Intel CPUs"
maintainer="Orphaned <orphan@voidlinux.org>"
license="custom: Proprietary"
@@ -12,10 +13,15 @@ distfiles="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/a
checksum=cee26f311f7e2c039dd48cd30f995183bde9b98fb4c3039800e2ddaf5c090e55
repository=nonfree
+do_build() {
+ rm -f intel-ucode{,-with-caveats}/list
+ iucode_tool -v --write-earlyfw=intel-ucode.img intel-ucode{,-with-caveats}/
+}
+
do_install() {
- vmkdir usr/lib/firmware/intel-ucode
- vcopy "intel-ucode/*" usr/lib/firmware/intel-ucode
+ vinstall intel-ucode.img 0644 usr/lib/firmware/intel-ucode
+ vlicense license
+
vmkdir usr/lib/dracut/dracut.conf.d
echo "early_microcode=yes" >> ${DESTDIR}/usr/lib/dracut/dracut.conf.d/intel_ucode.conf
- vlicense license
}
next reply other threads:[~2024-01-16 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 17:04 dkwo [this message]
2024-01-16 19:33 ` [PR PATCH] [Closed]: " dkwo
2024-01-16 19:33 ` dkwo
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48234@inbox.vuxu.org \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).