public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Rebecca Cran <rebecca@bluestop.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: PI 1.6 vs. edk2 - EfiGcdMemoryTypePersistent (EFI_GCD_MEMORY_TYPE)
Date: Sat, 16 Sep 2017 02:31:55 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1500B7@SHSMSX152.ccr.corp.intel.com> (raw)
In-Reply-To: <5c10aa5c-2ca1-2af7-0999-69d0d4aaf6b7@bluestop.org>

Rebecca:
  Thanks for your catch issue. I will provide the patch to fix it. To be compatible, I will keep EfiGcdMemoryTypePersistent and EfiGcdMemoryTypePersistentMemory both. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Rebecca Cran
> Sent: Saturday, September 16, 2017 3:55 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] PI 1.6 vs. edk2 - EfiGcdMemoryTypePersistent (EFI_GCD_MEMORY_TYPE)
> 
> I've noticed an inconsistency between the PI 1.6 specification and the
> edk2 implementation of EFI_GCD_MEMORY_TYPE: PI says it's
> EfiGcdMemoryTypePersistent while Pi/PiDxeCis.h has
> EfiGcdMemoryTypePersistentMemory.
> 
> Since the EfiGcdMemoryTypePersistent is mentioned several times in the
> spec I'm guessing the edk2 is wrong.
> 
> 
> --
> Rebecca
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-09-16  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 19:55 PI 1.6 vs. edk2 - EfiGcdMemoryTypePersistent (EFI_GCD_MEMORY_TYPE) Rebecca Cran
2017-09-16  2:31 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E1500B7@SHSMSX152.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