public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "leif.lindholm@arm.com" <leif.lindholm@arm.com>,
	 "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 00/10] *** BaseTools: Tools change to support PI v1.5 Specification. ***
Date: Thu, 08 Jun 2017 09:30:48 -0500	[thread overview]
Message-ID: <1496932248.3781.6.camel@arm.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D746FC9@shsmsx102.ccr.corp.intel.com>

On Thu, 2017-06-08 at 03:32 +0000, Gao, Liming wrote:
> Supreeth:
>   Thanks for your contribution. I review this patch set, and have two
> comments. 
Thanks Liming for reviewing the Patch set.

> 1) This is added in PI1.5. So, its version check should be with
> 0x00010032 (1 and 50), not 0x0001000A (1 and 10).  Smm standalone
> module INF needs to specify PI_SPECIFICATION_VERSION       =
> 0x00010032.
I will rectify it and upload v2 version.

> 2) Does the change conform to doc change recorded in below bugzilla?
> https://bugzilla.tianocore.org/show_bug.cgi?id=550
Not sure about the [Depex] sections (page 34). Will check this and
confirm before uploading v2.

> https://bugzilla.tianocore.org/show_bug.cgi?id=551
Yes. It conforms with this, though I will recheck once again.

> https://bugzilla.tianocore.org/show_bug.cgi?id=552
Yes. It conforms with this, though I will recheck once again.
> 
> Thanks
> Liming
> > 
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf
> > Of
> > Supreeth Venkatesh
> > Sent: Tuesday, June 06, 2017 5:44 AM
> > To: edk2-devel@lists.01.org
> > Cc: leif.lindholm@arm.com; ard.biesheuvel@linaro.org
> > Subject: [edk2] [PATCH 00/10] *** BaseTools: Tools change to
> > support PI v1.5
> > Specification. ***
> > 
> > ***
> > PI v1.5 Specification Volume 4 defines Management Mode Core
> > Interface.
> > In order to support Management Mode Core Interface, Module Types
> > MM_STANDALONE, MM_CORE_STANDALONE are needed.
> > PI specification v1.5 defines the following new file types:
> > #define EFI_FV_FILETYPE_MM 0x0A
> > #define EFI_FV_FILETYPE_COMBINED_MM_DXE 0x0C
> > #define EFI_FV_FILETYPE_MM_STANDALONE 0x0E
> > The following changes are necessitated in order to support the
> > above changes
> > to the specification.
> > ***
> > 
> > Supreeth Venkatesh (10):
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> >  BaseTools: Tools change to support PI v1.5 Specification.
> > 
> > BaseTools/Source/C/GenFfs/GenFfs.c                 |   6 +-
> > BaseTools/Source/C/GenFw/GenFw.c                   |   5 +-
> > BaseTools/Source/C/Include/Common/PiFirmwareFile.h |   1 +
> > BaseTools/Source/Python/AutoGen/GenC.py            | 148
> > ++++++++++++++++++++-
> > BaseTools/Source/Python/AutoGen/GenDepex.py        |  17 ++-
> > BaseTools/Source/Python/Common/DataType.py         |   4 +-
> > BaseTools/Source/Python/Common/FdfParserLite.py    |   4 +-
> > .../Source/Python/CommonDataClass/CommonClass.py   |   6 +-
> > .../Source/Python/CommonDataClass/PackageClass.py  |   2 +-
> > BaseTools/Source/Python/Eot/FvImage.py             |   1 +
> > BaseTools/Source/Python/GenFds/FdfParser.py        |   4 +-
> > BaseTools/Source/Python/GenFds/Ffs.py              |   7 +-
> > BaseTools/Source/Python/GenFds/FfsInfStatement.py  |   3 +
> > .../Source/Python/Workspace/WorkspaceDatabase.py   |   4 +
> > BaseTools/Source/Python/build/BuildReport.py       |   4 +-
> > BaseTools/Source/Python/build/build.py             |   2 +-
> > 16 files changed, 199 insertions(+), 19 deletions(-)
> > 
> > --
> > 2.7.4
> > 
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-06-08 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 21:43 [PATCH 00/10] *** BaseTools: Tools change to support PI v1.5 Specification. *** Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 01/10] BaseTools: Tools change to support PI v1.5 Specification Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 02/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 03/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 04/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 05/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 06/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 07/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 08/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 09/10] " Supreeth Venkatesh
2017-06-05 21:43 ` [PATCH 10/10] " Supreeth Venkatesh
2017-06-08  3:32 ` [PATCH 00/10] *** BaseTools: Tools change to support PI v1.5 Specification. *** Gao, Liming
2017-06-08 14:30   ` Supreeth Venkatesh [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=1496932248.3781.6.camel@arm.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