From: Rudolf Marek <r.marek@assembler.cz>
To: "Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Ivan Ivanov <qmastery16@gmail.com>
Cc: Josh Boyer <jwboyer@kernel.org>,
Linux Firmware <linux-firmware@kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Grimm, Jon" <Jon.Grimm@amd.com>
Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h
Date: Tue, 5 Jun 2018 19:55:40 +0200 [thread overview]
Message-ID: <9aa8d2aa-c58e-89fe-a2be-3b0de50fd554@assembler.cz> (raw)
In-Reply-To: <MWHPR1201MB2526CF0F174938EA64156AE98B660@MWHPR1201MB2526.namprd12.prod.outlook.com>
Hi Sherry,
Many thanks for your efforts. Are there any technical restriction(s) of why the OS bundled updates are not the latest available
version? I think we can't count much on hardware vendors to release microcode updates in the BIOS in the timely manner. I also
think especially for older families that BIOS updates won't be ever released. It is in the public interest
to always have latest update available - and it is also in line with AMD phrase "At AMD, security is a top priority".
Please consider having the latest microcode version available for OS updates too.
I would also appreciate of having the latest microcode available for the coreboot.org project.
Many thanks
Rudolf
next prev parent reply other threads:[~2018-06-05 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 1:57 Sherry Hurwitz
2018-05-25 12:10 ` Josh Boyer
2018-05-30 14:16 ` Ivan Ivanov
2018-05-31 22:05 ` Henrique de Moraes Holschuh
2018-06-04 19:27 ` Rudolf Marek
2018-06-05 14:27 ` Hurwitz, Sherry
2018-06-05 17:55 ` Rudolf Marek [this message]
2018-09-01 15:46 ` Rudolf Marek
2018-09-01 17:09 ` Rudolf Marek
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=9aa8d2aa-c58e-89fe-a2be-3b0de50fd554@assembler.cz \
--to=r.marek@assembler.cz \
--cc=Jon.Grimm@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=hmh@hmh.eng.br \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qmastery16@gmail.com \
--cc=sherry.hurwitz@amd.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
all inboxes | Powered by JetHome®