From: "Vincent Zimmer" <vincent.zimmer@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Cc: "Oram, Isaac W" <isaac.w.oram@intel.com>
Subject: Re: [edk2-devel] [edk2-non-osi] [PATCH V3 0/1] Add Intel® Management Engine Firmware Binaries for 2nd Generation Intel® Xeon®
Date: Tue, 11 Feb 2020 00:11:08 +0000 [thread overview]
Message-ID: <76DE84138CBE89489874B70B432D8F9BE644E39C@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <15F22FA434DFD5E4.13468@groups.io>
Reviewed by: vincent zimmer <vincent.zimmer@intel.com>
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Desimone, Nathaniel L
Sent: Monday, February 10, 2020 3:53 PM
To: devel@edk2.groups.io
Cc: Oram, Isaac W <isaac.w.oram@intel.com>; Zimmer, Vincent <vincent.zimmer@intel.com>
Subject: [edk2-devel] [edk2-non-osi] [PATCH V3 0/1] Add Intel® Management Engine Firmware Binaries for 2nd Generation Intel® Xeon®
This patch series adds Intel® PCH Ignition Firmware binaries for the 2nd Generation Intel® Xeon® Scalable Processors and chipsets formerly known as Cascade Lake to the edk2-non-osi repository.
Intel® PCH Ignition Firmware is a variant of Intel® Management Engine (ME) Firmware that is intended to provide lightweight chipset initialization.
It does not contain all the features of the Intel® Server Platform Services
(SPS) ME firmware. Intel® PCH Ignition Firmware is consequently much smaller than Intel® SPS Firmware (~0.5 MB vs. ~3 MB).
This patch series represents a milestone for Intel as it is the first time Intel has provided a Intel® Management Engine (ME) Firmware binary under a redistributable license to the public. The license is identical to the license for Microcode and Intel® Firmware Support Package (FSP).
Cc: Isaac W Oram <isaac.w.oram@intel.com>
Cc: Vincent Zimmer <vincent.zimmer@intel.com>
Signed-off-by: Nate DeSimone <nathaniel.l.desimone@intel.com>
Nate DeSimone (1):
Intel/PurleySiliconBinPkg: Add Intel(R) PCH Ignition Firmware 1.0.2.43
.../MeFirmware/IgnitionFirmware/License.txt | 37 +++++++++
.../MeFirmware/IgnitionFirmware/MeRegion.bin | Bin 0 -> 471040 bytes
.../Other_Licenses/libgcc_License.txt | 73 ++++++++++++++++++
.../MeFirmware/IgnitionFirmware/README.md | 17 ++++
.../PurleySiliconBinPkg/MeFirmware/README.md | 5 ++
5 files changed, 132 insertions(+)
create mode 100644 Silicon/Intel/PurleySiliconBinPkg/MeFirmware/IgnitionFirmware/License.txt
create mode 100644 Silicon/Intel/PurleySiliconBinPkg/MeFirmware/IgnitionFirmware/MeRegion.bin
create mode 100644 Silicon/Intel/PurleySiliconBinPkg/MeFirmware/IgnitionFirmware/Other_Licenses/libgcc_License.txt
create mode 100644 Silicon/Intel/PurleySiliconBinPkg/MeFirmware/IgnitionFirmware/README.md
create mode 100644 Silicon/Intel/PurleySiliconBinPkg/MeFirmware/README.md
--
2.24.0.windows.2
parent reply other threads:[~2020-02-11 0:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <15F22FA434DFD5E4.13468@groups.io>]
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-list 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=76DE84138CBE89489874B70B432D8F9BE644E39C@ORSMSX106.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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