From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: CPU microcode reported wrong in /proc/cpuinfo
Date: Thu, 16 Jul 2020 20:41:17 +0000 [thread overview]
Message-ID: <DM6PR09MB4043B7192355669826230DBEA57F0@DM6PR09MB4043.namprd09.prod.outlook.com> (raw)
> https://software.intel.com/security-software-guidance/insights/microcode-update-guidance
Thanks, interesting reading.
I think in my case the ucode update is done via the FIT method, though, as the latest microcode (0xA0E) is included in the re-packaged BIOS, and re-flashed into ROM along with it.
next reply other threads:[~2020-07-16 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 20:41 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 20:36 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 20:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis
2020-07-10 1:27 ` Brian Inglis
2020-07-16 14:56 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-07-16 19:46 ` Brian Inglis
2020-07-16 20:13 ` Brian Inglis
2020-06-10 15:34 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis
2020-05-31 15:07 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-02 20:11 ` Brian Inglis
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=DM6PR09MB4043B7192355669826230DBEA57F0@DM6PR09MB4043.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).