public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: linux-firmware and CPU microcodes
Date: Tue, 03 May 2022 11:20:26 +0100	[thread overview]
Message-ID: <462D2CCB-7142-410A-A1BA-0A65F3B0FA47@ipfire.org> (raw)
In-Reply-To: <249d8f86-a4de-916b-13cd-03ca91f32159@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

Hello Peter,

> On 30 Apr 2022, at 09:41, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello development folks,
> 
> while working on the linux-firmware update for Core Update 168 yesterday, I realised it
> comes with CPU microcodes for Intel and AMD as well (which kind of makes sense for a bundled
> conglomerate of firmware, I guess).

I cannot find any microcode for Intel processors in Linux firmware. That comes entirely out of the intel microcode package that we ship.

AMD however is part of linux-firmware:

  https://git.ipfire.org/?p=thirdparty/linux-firmware.git;a=tree;f=amd-ucode;h=eacd0a5d489f0c953461a5d5023e7ed448c43529;hb=refs/heads/main

> This means that either the CPU microcodes in linux-firmware or the dedicated LFS files
> for Intel and AMD microcode is redundant. Can we just drop the latter? Or did I overlook
> something?

So in my opinion, we will need to ship both.

Please remember to re-generate the initramdisks because they contain a copy of the microcode.

-Michael

> 
> Thanks, and best regards,
> Peter Müller


           reply	other threads:[~2022-05-03 10:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <249d8f86-a4de-916b-13cd-03ca91f32159@ipfire.org>]

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=462D2CCB-7142-410A-A1BA-0A65F3B0FA47@ipfire.org \
    --to=michael.tremer@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