From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <462D2CCB-7142-410A-A1BA-0A65F3B0FA47@ipfire.org>
In-Reply-To: <249d8f86-a4de-916b-13cd-03ca91f32159@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1361031649132504789=="
List-Id: <development.lists.ipfire.org>

--===============1361031649132504789==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Peter,

> On 30 Apr 2022, at 09:41, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Hello development folks,
>=20
> 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 se=
nse for a bundled
> conglomerate of firmware, I guess).

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

AMD however is part of linux-firmware:

  https://git.ipfire.org/?p=3Dthirdparty/linux-firmware.git;a=3Dtree;f=3Damd-=
ucode;h=3Deacd0a5d489f0c953461a5d5023e7ed448c43529;hb=3Drefs/heads/main

> This means that either the CPU microcodes in linux-firmware or the dedicate=
d LFS files
> for Intel and AMD microcode is redundant. Can we just drop the latter? Or d=
id 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 o=
f the microcode.

-Michael

>=20
> Thanks, and best regards,
> Peter M=C3=BCller


--===============1361031649132504789==--