From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Support intel-ucode when using mkinitcpio
Date: Wed, 10 Jan 2024 10:31:42 +0100 [thread overview]
Message-ID: <20240110093142.q8bU9dw_EnnCj0KqZO2LZC6nwAtUCWoY-CtdM4lrp2A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48145@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1884486750
Comment:
The arch page you link says
> However, Arch Linux defaults to using mkinitcpio to generate its initial ramdisk (initramfs), which does not support this.
but i agree it'd be nice to have a mechanism for other initrams to load microcode (e.g. booster, tinyramfs).
in the intel case, it could be stripped first (otherwise it's huge) and placed somewhere.
next prev parent reply other threads:[~2024-01-10 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 22:53 [ISSUE] " basploeger
2024-01-10 9:31 ` dkwo [this message]
2024-01-10 12:08 ` basploeger
2024-01-10 14:24 ` classabbyamp
2024-01-10 14:25 ` classabbyamp
2024-01-10 16:25 ` dkwo
2024-01-10 16:38 ` classabbyamp
2024-01-10 17:52 ` dkwo
2024-01-10 18:00 ` dkwo
2024-01-16 17:06 ` classabbyamp
2024-02-05 21:05 ` classabbyamp
2024-03-16 16:47 ` classabbyamp
2024-03-16 16:47 ` [ISSUE] [CLOSED] " classabbyamp
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=20240110093142.q8bU9dw_EnnCj0KqZO2LZC6nwAtUCWoY-CtdM4lrp2A@z \
--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).