public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Shaw, Kevin W" <kevin.w.shaw@intel.com>
Subject: Re: [Patch] Build Spec: Add some clarification of Build report section
Date: Thu, 27 Sep 2018 15:42:11 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E31C9EC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1537865854-9408-1-git-send-email-yonghong.zhu@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

> -----Original Message-----
> From: Zhu, Yonghong
> Sent: Tuesday, September 25, 2018 4:58 PM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
> Subject: [Patch] Build Spec: Add some clarification of Build report section
> 
> 1. Add the section header of Global PCD Section
> 2. Add 'INF DEFAULT' in the module PCD section
> 
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Michael Kinney <michael.d.kinney@intel.com>
> Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> ---
>  13_build_reports/136_global_pcd_section.md | 13 +++++++++++++
>  13_build_reports/138_module_section.md     |  8 +++++---
>  2 files changed, 18 insertions(+), 3 deletions(-)
> 
> diff --git a/13_build_reports/136_global_pcd_section.md b/13_build_reports/136_global_pcd_section.md
> index 2b7cf5f..0e3afa7 100644
> --- a/13_build_reports/136_global_pcd_section.md
> +++ b/13_build_reports/136_global_pcd_section.md
> @@ -45,10 +45,23 @@ gEfiNt32PkgTokenSpaceGuid
>  ```
> 
>  PCD values derived from expressions or other PCDs are not differentiated in the
>  report. Only the final value is displayed.
> 
> +The section header is:
> +```
> +>===============================================================================<
> +Platform Configuration Database Report
> +  *B  - PCD override in the build option
> +  *P  - Platform scoped PCD override in DSC file
> +  *F  - Platform scoped PCD override in FDF file
> +  *M  - Module scoped PCD override
> +=================================================================================
> +.. (List of PCDs)
> +<===============================================================================>
> +```
> +
>  Each global PCD item contains one or more lines:
> 
>  ### 13.6.1 Required line
> 
>  The first line is required:
> diff --git a/13_build_reports/138_module_section.md b/13_build_reports/138_module_section.md
> index 52288d7..843ad34 100644
> --- a/13_build_reports/138_module_section.md
> +++ b/13_build_reports/138_module_section.md
> @@ -241,15 +241,17 @@ Each PCD may contain up to following lines:
>       ```
>       *F PcdVpdSample : DYN-VPD (UINT32) = 0x1 (1)
>                         0x0001FFF
>       ```
> 
> -3. The third and fourth lines are both option if the module's final
> -   `<PcdValue>` is not equal to the PCD value in the PCD common section in the
> -   DSC file and the PCD value in the DEC file respectively.
> +3. The `DSC DEFAULT` `INF DEFAULT` and `DEC DEFAULT` are option if the module's
> +   final `<PcdValue>` is not equal to the PCD value in the PCD common section in
> +   DSC file, the PCD value in the module INF file and the PCD value in the DEC
> +   file respectively.
>     ```
>     DSC DEFAULT = <Value in PCD Common Section in DSC>
> +   INF DEFAULT = <Value in module INF>
>     DEC DEFAULT = <Value in DEC>
>     ```
>     For example:
>     ```
>     *M PcdDebugPrintErrorLevel : FIXED   (UINT32) = 0x80000042 (2147483714)
> --
> 2.6.1.windows.1



      reply	other threads:[~2018-09-27 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  8:57 [Patch] Build Spec: Add some clarification of Build report section Yonghong Zhu
2018-09-27 15:42 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E31C9EC@SHSMSX104.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