lkml.org 
[lkml]   [2017]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86/microcode: Document the three loading methods
On Tue, Jul 18, 2017 at 08:27:54AM +0200, Dominik Brodowski wrote:
> What about: "... microcode in (uncompressed) cpio format followed by the
> (possibly compressed) initrd image", to clarify this distinction?

Meh.

> What about something more fancy, such as
> iucode_tool -v /lib/firmware/intel-ucode/ -S $DSTDIR/GenuineIntel.bin
> ?

Why, because fancy is better? And simple is not good enough?

The less we rely on special tools for kernel stuff, the better.

> Maybe specify here that this works using the firmware infrastructure,
> therefore the microcode will be loaded from /lib/firmware/ ? Basically the
> same terms apply for this method as for the builtin microcode you describe
> next.

The distro package already installs it into /lib/firmware but ok, I'll
note the path explicitly.

Thx.

--
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.
--

\
 
 \ /
  Last update: 2017-07-18 09:43    [W:0.046 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site