From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.93, mailfrom: chasel.chiu@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by groups.io with SMTP; Mon, 19 Aug 2019 19:34:28 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Aug 2019 19:34:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,407,1559545200"; d="scan'208";a="207206726" Received: from pgsmsx104.gar.corp.intel.com ([10.221.44.91]) by fmsmga002.fm.intel.com with ESMTP; 19 Aug 2019 19:34:21 -0700 Received: from pgsmsx111.gar.corp.intel.com ([169.254.2.22]) by PGSMSX104.gar.corp.intel.com ([169.254.3.208]) with mapi id 14.03.0439.000; Tue, 20 Aug 2019 10:34:20 +0800 From: "Chiu, Chasel" To: "devel@edk2.groups.io" , "Kubacki, Michael A" CC: "Chaganty, Rangasai V" , "Gao, Liming" , "Desimone, Nathaniel L" , "Kinney, Michael D" , "Sinha, Ankit" Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 1/1] Platform/Intel/Readme.md: Content update Thread-Topic: [edk2-devel] [edk2-platforms][PATCH V1 1/1] Platform/Intel/Readme.md: Content update Thread-Index: AQHVVvtg7MJJzsZqhUeH76cH7LED7qcDUWDw Date: Tue, 20 Aug 2019 02:34:19 +0000 Message-ID: <3C3EFB470A303B4AB093197B6777CCEC50463E1F@PGSMSX111.gar.corp.intel.com> References: <20190820020231.38324-1-michael.a.kubacki@intel.com> In-Reply-To: <20190820020231.38324-1-michael.a.kubacki@intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTk2NTgzNjAtOGRlYi00YTE4LWIzYTItYmVkZDRkYmFkODdkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiNG5SWFl6TUdUR2Y3OUVPWVUwY2lTVFBxRWlhQVNLVVI1TmQyczJLZXRDNTk3ditcL1p2dnJHajVpbnVGdjJGWEoifQ== x-ctpclassification: CTP_NT x-originating-ip: [172.30.20.205] MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Reviewed-by: Chasel Chiu > -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > Kubacki, Michael A > Sent: Tuesday, August 20, 2019 10:03 AM > To: devel@edk2.groups.io > Cc: Chaganty, Rangasai V ; Chiu, Chasel > ; Gao, Liming ; Desimone, > Nathaniel L ; Kinney, Michael D > ; Sinha, Ankit > Subject: [edk2-devel] [edk2-platforms][PATCH V1 1/1] > Platform/Intel/Readme.md: Content update >=20 > This change makes the following updates: > 1. Indicate that build via batch scripts is no longer allowed. > 2. Remove ClevoOpenBoardPkg batch build instructions since > the batch build scripts no longer exist in the package. > 3. Move firmware image flashing instructions to a clearly labeled > section. > 4. Elaborate the firmware image flashing instructions. >=20 > Cc: Sai Chaganty > Cc: Chasel Chiu > Cc: Liming Gao > Cc: Nate DeSimone > Cc: Michael D Kinney > Cc: Ankit Sinha > Signed-off-by: Michael Kubacki > --- > Platform/Intel/Readme.md | 28 ++++++++++---------- > 1 file changed, 14 insertions(+), 14 deletions(-) >=20 > diff --git a/Platform/Intel/Readme.md b/Platform/Intel/Readme.md index > aaf6ef4d3e..3caf362983 100644 > --- a/Platform/Intel/Readme.md > +++ b/Platform/Intel/Readme.md > @@ -1,4 +1,4 @@ > -# **EDK II Minimum Platform Firmware for Intel(R) Platforms** > +# **EDK II Minimum Platform Firmware for Intel® Platforms** >=20 > The Minimum Platform is a software architecture that guides uniform del= ivery > of Intel platforms enabling firmware solutions for basic boot functiona= lity > with extensibility built-in. Please see the @@ -200,7 +200,8 @@ return b= ack to > the minimum platform caller. > >=20 > **Building with the batch scripts** > -KabylakeOpenBoardPkg does not support batch scripts, please use > build_bios.py. > +Only PurleyOpenBoardPkg still supports batch script build. Future board > +packages must only use the Python build infrastructure. >=20 > For PurleyOpenBoardPkg > 1. Open command window, go to the workspace directory, e.g. c:\Purley. > @@ -214,18 +215,6 @@ For PurleyOpenBoardPkg The validated version of > iasl compiler that can build MinPurley is 20180629. Older version may ge= nerate > ACPI build errors. >=20 > -For ClevoOpenBoardPkg > -1. Open command window, go to the workspace directory, e.g. c:\Clevo. > -2. Type "cd edk2-platforms\Platform\Intel\ClevoOpenBoardPkg\N1xxWU". > -3. Type "GitEdk2Clevo.bat" to setup GIT environment. > -4. Type "bld" to build Clevo UEFI firmware image, "bld release" for rel= ease > build, "bld clean" to remove intermediate -files. > - > -Users with access to the Intel proprietary FITC tool and ME ingredients= can > build full images for flash (BIOS + ME + -DESC). > - > -Users can also flash the UEFI firmware image to the highest area of the= flash > region directly. > - > ### **Known limitations** >=20 > **ClevoOpenBoardPkg** > @@ -258,6 +247,17 @@ Users can also flash the UEFI firmware image to the > highest area of the flash re 4. The Linux build was tested on Ubuntu 16= .04.5 > LTS with GCC version 5.4.0. > 5. The build was tested with NASM version 2.11.08. >=20 > +### **Firmware Image Flashing** > + > +The full Intel firmware image on a flash device is called the > +Integrated Firmware Image (IFWI). Users with access to the Intel propri= etary > FITC tool and ME ingredients can build full IFWI images that may be flas= hed > (Descriptor, UEFI FW, ME FW, etc.). > + > +Users without such access can directly flash a custom built UEFI FW ima= ge > over the highest area of the flash region directly. > +It is always recommended to have a hardware flash programmer accessible > +to recover the firmware image. The original full flash image should > +always be backed up so it may be flashed again for recovery. Please be > +aware that if a system supports a technology that authenticates the ini= tial > firmware boot image such as Boot Guard, it will fail to boot with a cust= om > firmware image that is not signed properly. > + > ### **Planned Activities** > * Replace the batch build scripts with cross-platform Python build scri= pts. > * Publish a Minimum Platform specification to describe the architecture= and > interfaces in more detail. > -- > 2.16.2.windows.1 >=20 >=20 >=20