From: Sherry Hurwitz <sherry.hurwitz@amd.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
<linux-kernel@vger.kernel.org>, <amd64-microcode@amd64.org>,
<suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH 1/1] linux-firmware: Add AMD microcode patch firmware files
Date: Wed, 10 Jul 2013 19:22:23 -0500 [thread overview]
Message-ID: <51DDFABF.4030101@amd.com> (raw)
In-Reply-To: <1372906583.22888.66.camel@deadeye.wl.decadent.org.uk>
On 07/03/2013 09:56 PM, Ben Hutchings wrote:
> On Fri, 2013-06-28 at 14:27 -0500, Sherry Hurwitz wrote:
>> For AMD Families 10h ~ 14h Processors
>> file: amd-ucode/microcode_amd.bin
>> md5sum: 55ae79b82cbfddcf7142058be3c9ec2d
>>
>> For AMD Family 15h Processors
>> file: amd-ucode/microcode_amd_fam15h.bin
>> md5sum: 122ac7e56442c2b7c28eb26978b2d57c
>>
>> Signed-off-by: Sherry Hurwitz<sherry.hurwitz@amd.com>
>> ---
>> LICENSE.amd-ucode | 64 ++++++++++++++++++++++++++++++++++++
>> WHENCE | 9 +++++
>> amd-ucode/microcode_amd.bin | Bin 0 -> 12684 bytes
>> amd-ucode/microcode_amd_fam15h.bin | Bin 0 -> 7876 bytes
>> 4 files changed, 73 insertions(+)
>> create mode 100644 LICENSE.amd-ucode
>> create mode 100644 amd-ucode/microcode_amd.bin
>> create mode 100644 amd-ucode/microcode_amd_fam15h.bin
> [...]
>> --- a/WHENCE
>> +++ b/WHENCE
>> @@ -2169,3 +2169,12 @@ File: go7007/wis-startrek.fw
>> Licence: Redistributable. See LICENCE.go7007_firmware for details
>>
>> --------------------------------------------------------------------------
>> +
>> +Driver: microcode_amd - AMD CPU Microcode Update Driver for Linux
>> +
>> +File: amd-ucode/microcode_amd.bin
>> +File: amd-ucode/microcode_amd_fam15h.bin
>> +
>> +License: Redistributable. See LICENSE.amd-ucode for details
> [...]
>
> Please include the version number.
>
> I notice that the download page on amd64.org also has GPG signatures.
> Perhaps those should be included too?
>
> (Actually, I would like to see verifiable signatures on all binary
> firmware, but I don't think that can be made a requirement any time
> soon. Key 9F94BC90 isn't signed by another published key, so I still
> have no reason to trust its identity.)
>
> Ben.
>
The amd64.org site is down and will no longer be used for distributing
AMD microcode patches. Therefore, the Key ID 9F94BC90 will no longer be
used to sign the future microcode container files. A new key will be
created and signed by me and another AMD co-worker. We will resend the
patch with the Key ID 8C0108B4. You can pull this key from the gnuPG
key server to verify and see it is signed by two other keys, one
belonging to me and the other by Suravee Suthikulpanit, with AMD email
addresses.
Sherry
prev parent reply other threads:[~2013-07-11 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 19:27 [PATCH 1/1] linux-firmware: Add AMD microcode patch firmware files Sherry Hurwitz
2013-07-04 2:56 ` Ben Hutchings
2013-07-11 0:22 ` Sherry Hurwitz [this message]
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=51DDFABF.4030101@amd.com \
--to=sherry.hurwitz@amd.com \
--cc=amd64-microcode@amd64.org \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@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