public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Tim Lewis <tim.lewis@insyde.com>
To: "Zeng, Star" <star.zeng@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [RFC] PCD: Extended SKU support 1 - inheritance
Date: Wed, 26 Apr 2017 16:21:16 +0000	[thread overview]
Message-ID: <7236196A5DF6C040855A6D96F556A53F5763C0@msmail.insydesw.com.tw> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103B87E776@shsmsx102.ccr.corp.intel.com>

Star --

This assumes that the SKU ID is only used for PCDs, which is not the case. The SKU ID may be used by other components, and other components may use the 0|DEFAULT rule as well. 

1) There is no way to read this defaulting rule at runtime. The information is buried in the PCD database, but not available externally.
2) There is no way to read the contents of SKUID_IDENTIFIER when multiple SKUs are specified. While more than one SKU can be specified (separated by spaces), there is no way to pass multiple values into build.exe today, nor is there any way to identify which SKUs (out of the total list of SKUs) is supported on one build at runtime.

Tim


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Zeng, Star
Sent: Tuesday, April 25, 2017 5:40 AM
To: edk2-devel@lists.01.org
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Zeng, Star <star.zeng@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: [edk2] [RFC] PCD: Extended SKU support 1 - inheritance

- Requirement
Simplify the PCDs configuring for multiple SKUs in DSC.


- Current limitation
Non-DEFAULT SKU could only derive from DEFAULT SKU, but could not derive from another non-DEFAULT SKU.
For example below, SkuA and SkuB could only derive from DEFAULT, but SkuB could not derive from SkuA.

[SkuIds]
  0 | DEFAULT
  1 | SkuA
  2 | SkuB


- Proposal: One non-DEFAULT SKU could be a derivative of another non-DEFAULT SKU.
This proposal only extends DSC [SkuIds] section syntax and the extension is optional.
This proposal keeps the backward compatibility with current SKU usage.
BaseTools update is needed to support the syntax extension, and no any change in PCD database and driver is required.

DSC syntax:
  [SkuIds]
    SkuValue|SkuName[|ParentSkuName]
      SkuValue: integer, 0 is reserved for DEFAULT SKU.
      SkuName: string
      ParentSkuName: string, optional, it is new introduced in this proposal and defines which SKU the PCD value will derive from for this SKU. The PCD value will derive from DEFAULT SKU for this SKU if the ParentSkuName is absent.


- Example: SkuB is a derivative of SkuA, but not a derivative of DEFAULT.

  [SkuIds]
    0 | DEFAULT
    1 | SkuA
    2 | SkuB | SkuA

  [PcdsDynamicDefault.Common.DEFAULT]
    gXXXPkgTokenSpaceGuid.PcdXXXSignature|"DEFAULT"
    gXXXPkgTokenSpaceGuid.PcdXXXConfig1|FALSE
    gXXXPkgTokenSpaceGuid.PcdXXXConfig2|FALSE
    gXXXPkgTokenSpaceGuid.PcdXXXConfig3|FALSE

  [PcdsDynamicDefault.Common.SkuA]
    gXXXPkgTokenSpaceGuid.PcdXXXSignature|"SkuA"
    gXXXPkgTokenSpaceGuid.PcdXXXConfig1|TRUE
    gXXXPkgTokenSpaceGuid.PcdXXXConfig2|TRUE
    # No need statement for PcdXXXConfig3 whose value will derive from DEFAULT SKU and be FLASE.
 
  [PcdsDynamicDefault.Common.SkuB]
    gXXXPkgTokenSpaceGuid.PcdXXXSignature|" SkuB"
    # No need statement for PcdXXXConfig1 and PcdXXXConfig2 whose values will derive from SkuA SKU and be TRUE.
    gXXXPkgTokenSpaceGuid.PcdXXXConfig3|TRUE
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-04-26 16:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 12:39 [RFC] PCD: Extended SKU support 1 - inheritance Zeng, Star
2017-04-26 16:21 ` Tim Lewis [this message]
2017-04-26 18:04   ` Kinney, Michael D
2017-04-26 18:23     ` Tim Lewis
2017-04-26 18:40       ` Kinney, Michael D
2017-04-26 18:46         ` Tim Lewis
2017-04-26 19:04           ` Kinney, Michael D
2017-04-26 19:58             ` Tim Lewis
2017-04-26 22:56               ` Kinney, Michael D
2017-04-26 23:06                 ` Tim Lewis
2017-04-27  0:28                   ` Kinney, Michael D
2017-04-27 16:28                     ` Tim Lewis
2017-04-28  1:00                       ` Zeng, Star
2017-04-28  1:43                         ` Tim Lewis
2017-04-28  1:53                           ` Zeng, Star
2017-04-28  2:02                             ` Andrew Fish
2017-04-28  2:10                               ` Zeng, Star
2017-04-28  2:09                             ` Tim Lewis
2017-04-28  3:25                               ` Kinney, Michael D
2017-05-03 14:02                                 ` Zeng, Star
2017-05-03 18:55                                   ` Tim Lewis
2017-05-04 13:41                                     ` Zeng, Star
2017-05-04 16:35                                       ` Tim Lewis
2017-05-05 10:07                                         ` Zeng, Star
2017-05-05 16:06                                           ` Tim Lewis
2017-05-05 16:06                                           ` Kinney, Michael D
2017-05-15  9:45                                             ` Zeng, Star
2017-05-15 16:30                                               ` Tim Lewis

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=7236196A5DF6C040855A6D96F556A53F5763C0@msmail.insydesw.com.tw \
    --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