From: "Zhou, Bowen" <bowen.zhou@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: [Patch][edk2-platforms/devel-MinPlatform] PurleyOpenBoardPkg-Misc: update Readme and Maintainers info
Date: Tue, 24 Jul 2018 02:56:26 +0000 [thread overview]
Message-ID: <477DBD36544FF849A8AD024E912EEC0F58FC2C18@SHSMSX101.ccr.corp.intel.com> (raw)
State iasl version in Readme for MinPurley and update package maintainer information for PurleyOpenBoardPkg
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Xiaohu Zhou <bowen.zhou@intel.com>
---
Platform/Intel/Maintainers.txt | 3 +++
ReadMe.md | 1 +
2 files changed, 4 insertions(+)
diff --git a/Platform/Intel/Maintainers.txt b/Platform/Intel/Maintainers.txt
index c59d2fd76c..7352d9ca34 100644
--- a/Platform/Intel/Maintainers.txt
+++ b/Platform/Intel/Maintainers.txt
@@ -44,3 +44,6 @@ M: Chasel Chiu <chasel.chiu@intel.com>
MinPlatformPkg
M: Jiewen Yao <jiewen.yao@intel.com>
+PurleyOpenBoardPkg
+M: Xiaohu Zhou <xiaohu.zhou@intel.com>
+
diff --git a/ReadMe.md b/ReadMe.md
index 5bcdd1da93..0634e3f543 100644
--- a/ReadMe.md
+++ b/ReadMe.md
@@ -50,6 +50,7 @@ For MinPurley
4. Type "bld" to build Purley BIOS image, "bld release" for release build.
The user can run FITC tool to build full image for flash (BIOS + ME + DESC). The user can also burn the BIOS image to highest part of flash region directly.
+The validated version of iasl compiler that can build MinPurley is 20180629. Older version may generate ACPI build errors.
### Known limitations
--
2.14.3.windows.1
next reply other threads:[~2018-07-24 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 2:56 Zhou, Bowen [this message]
2018-07-24 3:02 ` [Patch][edk2-platforms/devel-MinPlatform] PurleyOpenBoardPkg-Misc: update Readme and Maintainers info Gao, Liming
2018-07-24 3:03 ` Yao, Jiewen
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=477DBD36544FF849A8AD024E912EEC0F58FC2C18@SHSMSX101.ccr.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