public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: Wim Vervoorn <wvervoorn@eltan.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Oram, Isaac W" <isaac.w.oram@intel.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"Kubacki, Michael A" <michael.a.kubacki@intel.com>
Subject: Re: [edk2-devel] [edk2-non-osi] [PATCH V2 0/1] Add ME Firmware Binaries for Cascade Lake
Date: Thu, 21 Nov 2019 00:59:52 +0000	[thread overview]
Message-ID: <02A34F284D1DA44BB705E61F7180EF0AB5BEE0A3@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <3bda3382e4d64f358e6a1ba308ba7506@Eltsrv03.Eltan.local>

Hi Wim,

Yeah I was excited to send the patch series!

Just to clear up any potential confusion "Purley Refresh" and "Cascade Lake" are one and the same. With regard to the removal of the Purley MinPlatform code, basically it just comes down to nobody was maintaining it. It was never compliant with the MinPlatform spec and it was missing a lot of the new changes. Most of the maintainers were not even responding to email patches.

We would love to have a good MinPlatform implementation for it, its just there isn't enough people actively contributing to the development of MinPlatform right now. Hopefully it can be resurrected at some point.

Thanks,
Nate

-----Original Message-----
From: Wim Vervoorn <wvervoorn@eltan.com> 
Sent: Wednesday, November 20, 2019 3:11 AM
To: devel@edk2.groups.io; Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
Cc: Oram, Isaac W <isaac.w.oram@intel.com>; Zimmer, Vincent <vincent.zimmer@intel.com>; Kubacki, Michael A <michael.a.kubacki@intel.com>
Subject: RE: [edk2-devel] [edk2-non-osi] [PATCH V2 0/1] Add ME Firmware Binaries for Cascade Lake

Hi,

This is great news.

What I don't understand yet is how this relates to the removal of the Purley platform and the comments made when the bug report requesting Cascade Lake support was closed.

Does this mean a replacement for the Purley Refresh platform that supports the MinPlatform architecture can be expected shortly?

Best Regards,
Wim Vervoorn

Eltan B.V.
Ambachtstraat 23
5481 SM Schijndel
The Netherlands

T : +31-(0)73-594 46 64
E : wvervoorn@eltan.com
W : http://www.eltan.com


"THIS MESSAGE CONTAINS CONFIDENTIAL INFORMATION. UNLESS YOU ARE THE INTENDED RECIPIENT OF THIS MESSAGE, ANY USE OF THIS MESSAGE IS STRICTLY PROHIBITED. IF YOU HAVE RECEIVED THIS MESSAGE IN ERROR, PLEASE IMMEDIATELY NOTIFY THE SENDER BY TELEPHONE +31-(0)73-5944664 OR REPLY EMAIL, AND IMMEDIATELY DELETE THIS MESSAGE AND ALL COPIES." 


-----Original Message-----
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Nate DeSimone
Sent: Wednesday, November 20, 2019 3:39 AM
To: devel@edk2.groups.io
Cc: Isaac W Oram <isaac.w.oram@intel.com>; Vincent Zimmer <vincent.zimmer@intel.com>; Michael Kubacki <michael.a.kubacki@intel.com>
Subject: [edk2-devel] [edk2-non-osi] [PATCH V2 0/1] Add ME Firmware Binaries for Cascade Lake

This patch series adds ignition ME firmware binaries for the 2nd Generation Intel® Xeon® Scalable Processors and chipsets formerly known as Cascade Lake to the edk2-non-osi repository.

Ignition Firmware is a variant of 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. 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 ME firmware binary under a redistributable license to the public. The license is identical to the license for Microcode and FSP.

Cc: Isaac W Oram <isaac.w.oram@intel.com>
Cc: Vincent Zimmer <vincent.zimmer@intel.com>
Cc: Michael Kubacki <michael.a.kubacki@intel.com>
Signed-off-by: Nate DeSimone <nathaniel.l.desimone@intel.com>

Nate DeSimone (1):
  Intel/PurleySiliconBinPkg: Add Ignition ME Firmware 1.0.2.29

 .../MeFirmware/IgnitionFirmware/License.txt   |  37 +++++++++
 .../MeFirmware/IgnitionFirmware/MeRegion.bin  | Bin 0 -> 471040 bytes
 .../Other_Licenses/libgcc_License.txt         |  73 ++++++++++++++++++
 .../MeFirmware/IgnitionFirmware/README.md     |  15 ++++
 .../PurleySiliconBinPkg/MeFirmware/README.md  |   5 ++
 5 files changed, 130 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









      reply	other threads:[~2019-11-21  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  2:38 [edk2-non-osi] [PATCH V2 0/1] Add ME Firmware Binaries for Cascade Lake Nate DeSimone
2019-11-20  2:38 ` [edk2-non-osi] [PATCH V2 1/1] Intel/PurleySiliconBinPkg: Add Ignition ME Firmware 1.0.2.29 Nate DeSimone
2019-11-21  0:56   ` Kubacki, Michael A
2019-11-21  1:00   ` Vincent Zimmer
2019-11-20 11:11 ` [edk2-devel] [edk2-non-osi] [PATCH V2 0/1] Add ME Firmware Binaries for Cascade Lake wvervoorn
2019-11-21  0:59   ` Nate DeSimone [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-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=02A34F284D1DA44BB705E61F7180EF0AB5BEE0A3@ORSMSX114.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