public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"afish@apple.com" <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] PcdDebugPropertyMask in DSC: How to I set different values for PEI and DXE?
Date: Wed, 16 Feb 2022 22:10:44 +0000	[thread overview]
Message-ID: <CO1PR11MB4929506C36C80759BD2596F5D2359@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <885704FE-E5FC-40DF-B145-B97B00B2E02D@apple.com>

Hi Andrew,

Current DSC syntax for platform scoped [PcdsXXX] sections only supports
CPU Arch and SKUID.

So there is no mechanism today to specify different PCD values based on
module type.

You can manage this in the DSC file, but it does require the module
scoped <PcdXXX> section for each module INF that requires a different
value that the platform scoped [PcdXXX] section.

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Andrew Fish via groups.io
> Sent: Wednesday, February 16, 2022 1:02 PM
> To: edk2-devel-groups-io <devel@edk2.groups.io>
> Subject: [edk2-devel] PcdDebugPropertyMask in DSC: How to I set different values for PEI and DXE?
> 
> I’m trying to have a different platform policy for PcdDebugPropertyMask in PEI and DXE. I can’t figure out how to do without
> overriding every PEIM that I build?
> 
> My PEI and DXE has the same arch so I can’t use the CPU Arch to tell them apart.
> 
> Is there something I’m missing?
> 
> Thanks,
> 
> Andrew Fish
> 
> 
> 


  reply	other threads:[~2022-02-16 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 21:01 PcdDebugPropertyMask in DSC: How to I set different values for PEI and DXE? Andrew Fish
2022-02-16 22:10 ` Michael D Kinney [this message]
2022-02-17  3:25   ` [edk2-devel] " Andrew Fish
2022-02-17 18:52     ` Michael D Kinney
2022-02-17 20:22       ` Andrew Fish
2022-02-18  0:26         ` Oram, Isaac W
2022-02-18  0:41           ` Andrew Fish
2022-02-18  1:36             ` Michael D Kinney
2022-02-18  2:49               ` Andrew Fish

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=CO1PR11MB4929506C36C80759BD2596F5D2359@CO1PR11MB4929.namprd11.prod.outlook.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