1. Patchew
  2. EDK2
  3. View series

[edk2] [Patch] DSC spec: Update Skuid value to support Hex number

Yonghong Zhu posted 1 patch 6 years, 11 months ago
Failed in applying to current master (apply log)
2_dsc_overview/25_[skuids]_section_processing.md | 2 +-
3_edk_ii_dsc_file_format/37_[skuids]_section.md  | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
[edk2] [Patch] DSC spec: Update Skuid value to support Hex number
Posted by Yonghong Zhu 6 years, 11 months ago 
Original Skuid value only support to use integer, this patch extend it
to also support hex number.

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>
---
 2_dsc_overview/25_[skuids]_section_processing.md | 2 +-
 3_edk_ii_dsc_file_format/37_[skuids]_section.md  | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/2_dsc_overview/25_[skuids]_section_processing.md b/2_dsc_overview/25_[skuids]_section_processing.md
index 428f7cf..afd102e 100644
--- a/2_dsc_overview/25_[skuids]_section_processing.md
+++ b/2_dsc_overview/25_[skuids]_section_processing.md
@@ -35,11 +35,11 @@ The contents of this section are used to define valid `SKUID_IDENTIFIER` names.
 Since a platform may support different SKUs, and different SKUs may implement
 different methods for handing platform configuration data (PCD) the user can
 define, in this section, tag names to use. Use `0` for the `DEFAULT` SKU
 identifier. Each entry below the section header is of the form:
 
-`integer | word`
+`Number | word`
 
 The following is an example of a `[SkuIds]` section:
 
 ```
 [SkuIds]
diff --git a/3_edk_ii_dsc_file_format/37_[skuids]_section.md b/3_edk_ii_dsc_file_format/37_[skuids]_section.md
index 97642e9..756ded2 100644
--- a/3_edk_ii_dsc_file_format/37_[skuids]_section.md
+++ b/3_edk_ii_dsc_file_format/37_[skuids]_section.md
@@ -42,18 +42,18 @@ recommended that a ".txt" extension be used.
 
 If this section is not specified, the parsing tools will assume a SkuId of 0,
 with a `UiName` of "DEFAULT". The default entry must not be re-defined.
 
 The `!include` file can only contain an ASCII (not Unicode) list of
-"integer|UiSkuName" statements.
+"Number|UiSkuName" statements.
 
 #### Prototype
 
 ```c
 <SkuId>     ::= "[SkuIds]" <EOL>
                 {<Statement>*} {<IncludeStatement>}
-<Statement> ::= <TS> <Integer> <FS> <UiName> <EOL>
+<Statement> ::= <TS> <Number> <FS> <UiName> <EOL>
 <UiName>    ::= <Word>
 ```
 
 #### Example
 
-- 
2.6.1.windows.1

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] [Patch] DSC spec: Update Skuid value to support Hex number
Posted by Gao, Liming 6 years, 10 months ago 
Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Zhu, Yonghong
>Sent: Tuesday, January 23, 2018 11:18 AM
>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] DSC spec: Update Skuid value to support Hex number
>
>Original Skuid value only support to use integer, this patch extend it
>to also support hex number.
>
>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>
>---
> 2_dsc_overview/25_[skuids]_section_processing.md | 2 +-
> 3_edk_ii_dsc_file_format/37_[skuids]_section.md  | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/2_dsc_overview/25_[skuids]_section_processing.md
>b/2_dsc_overview/25_[skuids]_section_processing.md
>index 428f7cf..afd102e 100644
>--- a/2_dsc_overview/25_[skuids]_section_processing.md
>+++ b/2_dsc_overview/25_[skuids]_section_processing.md
>@@ -35,11 +35,11 @@ The contents of this section are used to define valid
>`SKUID_IDENTIFIER` names.
> Since a platform may support different SKUs, and different SKUs may
>implement
> different methods for handing platform configuration data (PCD) the user can
> define, in this section, tag names to use. Use `0` for the `DEFAULT` SKU
> identifier. Each entry below the section header is of the form:
>
>-`integer | word`
>+`Number | word`
>
> The following is an example of a `[SkuIds]` section:
>
> ```
> [SkuIds]
>diff --git a/3_edk_ii_dsc_file_format/37_[skuids]_section.md
>b/3_edk_ii_dsc_file_format/37_[skuids]_section.md
>index 97642e9..756ded2 100644
>--- a/3_edk_ii_dsc_file_format/37_[skuids]_section.md
>+++ b/3_edk_ii_dsc_file_format/37_[skuids]_section.md
>@@ -42,18 +42,18 @@ recommended that a ".txt" extension be used.
>
> If this section is not specified, the parsing tools will assume a SkuId of 0,
> with a `UiName` of "DEFAULT". The default entry must not be re-defined.
>
> The `!include` file can only contain an ASCII (not Unicode) list of
>-"integer|UiSkuName" statements.
>+"Number|UiSkuName" statements.
>
> #### Prototype
>
> ```c
> <SkuId>     ::= "[SkuIds]" <EOL>
>                 {<Statement>*} {<IncludeStatement>}
>-<Statement> ::= <TS> <Integer> <FS> <UiName> <EOL>
>+<Statement> ::= <TS> <Number> <FS> <UiName> <EOL>
> <UiName>    ::= <Word>
> ```
>
> #### Example
>
>--
>2.6.1.windows.1

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Patchew 2.1-devel-8c64711

© 2016 - 2024 Red Hat, Inc.