public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: jbrasen.qdt <jbrasen.qdt@qualcommdatacenter.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: Question regarding structure PCD
Date: Mon, 26 Mar 2018 20:16:15 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B89A4487@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <d2ad081619904f84a3b4519bce6d1c8a@NASANEXM01B.na.qualcomm.com>

Jeff,

You can provide default values for structure fields
in the DEC file.

Liming has an example posted in the following branch:

https://github.com/lgao4/edk2/tree/UDK2018

DEC file example in TestPkg:

https://github.com/lgao4/edk2/blob/UDK2018/TestPkg/TestPkg.dec

Mike

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> bounces@lists.01.org] On Behalf Of jbrasen.qdt
> Sent: Monday, March 26, 2018 11:51 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Question regarding structure PCD
> 
> Hello,
> 
>    I was implementing support for PCDs in my platform
> using the new structure PCD support, and I had a
> question regarding this. Is it possible in the dec file
> to define the default values of a PCD defined as a
> structure using this format or just the byte array
> format?
> 
> Thanks,
> Jeff Brasen
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-03-26 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 18:51 Question regarding structure PCD jbrasen.qdt
2018-03-26 20:16 ` Kinney, Michael D [this message]
2018-03-27  9:31   ` Laszlo Ersek

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=E92EE9817A31E24EB0585FDF735412F5B89A4487@ORSMSX113.amr.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