From: Ben Hutchings <ben@decadent.org.uk>
To: Sherry Hurwitz <sherry.hurwitz@amd.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, amd64-microcode@amd64.org
Subject: Re: [PATCH 1/1] linux-firmware: Add AMD microcode patch firmware files
Date: Thu, 04 Jul 2013 03:56:23 +0100 [thread overview]
Message-ID: <1372906583.22888.66.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1372447651-10290-1-git-send-email-sherry.hurwitz@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
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.
--
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-07-04 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 19:27 Sherry Hurwitz
2013-07-04 2:56 ` Ben Hutchings [this message]
2013-07-11 0:22 ` Sherry Hurwitz
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=1372906583.22888.66.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=amd64-microcode@amd64.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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®