public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zhiguang Liu" <zhiguang.liu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"oleksiyy@ami.com" <oleksiyy@ami.com>,
	"robert@ami.com" <robert@ami.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Felixp@ami.com" <Felixp@ami.com>,
	"robert@ami.com" <robert@ami.com>
Subject: Re: [edk2-devel] [PATCH 2/5] MdePkg: Updates to PI 1.7 Revision numbers for
Date: Mon, 11 May 2020 05:20:27 +0000	[thread overview]
Message-ID: <BN7PR11MB28040EC8CC93AA5A3F8623EC90A10@BN7PR11MB2804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200507190310.38968-3-oleksiyy@ami.com>

Hi Robert,
In PI spec 1.7 A, page 2-16
#define DXE_SPECIFICATION_MINOR_REVISION 60

This is not consistent with you code change, am I using the latest spec? Or, does spec need updated?

Thanks
Zhiguang

 

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Oleksiy
> Yakovlev
> Sent: Friday, May 8, 2020 3:03 AM
> To: devel@edk2.groups.io
> Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Felixp@ami.com; oleksiyy@ami.com;
> robert@ami.com
> Subject: [edk2-devel] [PATCH 2/5] MdePkg: Updates to PI 1.7 Revision
> numbers for
> 
> From: Robert Phelps <robert@ami.com>
> 
> Revision number defines and MACROs were incorrect for the current version
> of the Specification (PI 1.7 Mantis 1892)
> 
> Signed-off-by: Robert Phelps <robert@ami.com>
> ---
>  MdePkg/Include/Pi/PiDxeCis.h | 4 ++--
>  MdePkg/Include/Pi/PiPeiCis.h | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/MdePkg/Include/Pi/PiDxeCis.h b/MdePkg/Include/Pi/PiDxeCis.h
> index e44744654f..1682211d92 100644
> --- a/MdePkg/Include/Pi/PiDxeCis.h
> +++ b/MdePkg/Include/Pi/PiDxeCis.h
> @@ -5,7 +5,7 @@ Copyright (c) 2006 - 2018, Intel Corporation. All rights
> reserved.<BR>
>  SPDX-License-Identifier: BSD-2-Clause-Patent
> 
>    @par Revision Reference:
> -  PI Version 1.6
> +  PI Version 1.7
> 
>  **/
> 
> @@ -690,7 +690,7 @@ EFI_STATUS
>  //
>  #define DXE_SERVICES_SIGNATURE            0x565245535f455844ULL
>  #define DXE_SPECIFICATION_MAJOR_REVISION  1 -#define
> DXE_SPECIFICATION_MINOR_REVISION  60
> +#define DXE_SPECIFICATION_MINOR_REVISION  70
>  #define DXE_SERVICES_REVISION
> ((DXE_SPECIFICATION_MAJOR_REVISION<<16) |
> (DXE_SPECIFICATION_MINOR_REVISION))
> 
>  typedef struct {
> diff --git a/MdePkg/Include/Pi/PiPeiCis.h b/MdePkg/Include/Pi/PiPeiCis.h
> index d9d4ed7d41..ebfe598172 100644
> --- a/MdePkg/Include/Pi/PiPeiCis.h
> +++ b/MdePkg/Include/Pi/PiPeiCis.h
> @@ -5,7 +5,7 @@ Copyright (c) 2006 - 2019, Intel Corporation. All rights
> reserved.<BR>
>  SPDX-License-Identifier: BSD-2-Clause-Patent
> 
>    @par Revision Reference:
> -  PI Version 1.6.
> +  PI Version 1.7.
> 
>  **/
> 
> @@ -850,7 +850,7 @@ EFI_STATUS
>  // PEI Specification Revision information  //  #define
> PEI_SPECIFICATION_MAJOR_REVISION  1 -#define
> PEI_SPECIFICATION_MINOR_REVISION  60
> +#define PEI_SPECIFICATION_MINOR_REVISION  70
>  ///
>  /// Specification inconsistency here:
>  /// In the PI1.0 spec, PEI_SERVICES_SIGNATURE is defined as
> 0x5652455320494550. But
> --
> 2.24.1.windows.2
> 
> 
> Please consider the environment before printing this email.
> 
> The information contained in this message may be confidential and
> proprietary to American Megatrends (AMI).  This communication is intended
> to be read only by the individual or entity to whom it is addressed or by their
> designee. If the reader of this message is not the intended recipient, you are
> on notice that any distribution of this message, in any form, is strictly
> prohibited.  Please promptly notify the sender by reply e-mail or by
> telephone at 770-246-8600, and then delete or destroy all copies of the
> transmission.
> 
> 


  reply	other threads:[~2020-05-11  5:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 19:03 [PATCH 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a Oleksiy Yakovlev
2020-05-07 19:03 ` [PATCH 1/5] MdePkg: New Status Codes Oleksiy Yakovlev
2020-05-11  5:13   ` [edk2-devel] " Zhiguang Liu
2020-05-07 19:03 ` [PATCH 2/5] MdePkg: Updates to PI 1.7 Revision numbers for Oleksiy Yakovlev
2020-05-11  5:20   ` Zhiguang Liu [this message]
     [not found]   ` <160DE1B9669AE9D0.7726@groups.io>
2020-05-11  5:22     ` [edk2-devel] " Zhiguang Liu
2020-05-07 19:03 ` [PATCH 3/5] MdePkg: EFI_MM_COMUNICATION2_PROTOCOL Oleksiy Yakovlev
2020-05-11  5:31   ` [edk2-devel] " Zhiguang Liu
2020-05-07 19:03 ` [PATCH 4/5] MdePkg: Added header file for Delayed Dispatch PPI Oleksiy Yakovlev
2020-05-11  5:43   ` [edk2-devel] " Zhiguang Liu
2020-05-07 19:03 ` [PATCH 5/5] MdePkg: Update structures for MpServices Protocol Oleksiy Yakovlev
2020-05-11  5:00   ` [edk2-devel] " Ni, Ray
2020-05-15  4:56     ` Liming Gao
2020-05-15  5:33       ` Ni, Ray
     [not found]       ` <160F1CC8B9ACB17A.23170@groups.io>
2020-05-15  7:48         ` Ni, Ray
2020-05-15  7:50           ` Liming Gao
2020-05-11  6:05   ` Zhiguang Liu
2020-05-11 14:29 ` [edk2-devel] [PATCH 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a Liming Gao

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=BN7PR11MB28040EC8CC93AA5A3F8623EC90A10@BN7PR11MB2804.namprd11.prod.outlook.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