public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io
Subject: PCD Migration issue
Date: Mon, 10 Feb 2020 09:39:03 -0800	[thread overview]
Message-ID: <6D19BFCB-B1F3-415E-9DDA-23992E98B637@apple.com> (raw)

We recently hit an issue when updating our UDK version in our common code base. Our recovery update path started failing for older platforms since the PEI was the old UDK version and the DXE from the Capsule was the new UDK version. Basically the version of the PCD changed. It looks like there are some checks, but the seem to be more about making sure the build systems matches the code vs. dealing with an update case like we hit. 

It does not look like the PCD database is designed to deal with this. We are fixing this by extracting the PEI PCD database from the capsule and then having some platform specific code to patch any PCD entries that got set in PEI that are needed by DXE. 

In the future it would be helpful if the PCD database would change in some what of a backward compatible way, and have the headers needed to parse the old and new version. 

It also seems like adding a Dynamic PCD could potentially change the token layout and thus break compatibility? Is there any scheme to keep a previous token layout? 

Thanks,

Andrew Fish

             reply	other threads:[~2020-02-10 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 17:39 Andrew Fish [this message]
2020-02-12  3:54 ` [edk2-devel] PCD Migration issue Liming Gao
2020-02-12  6:21   ` Andrew Fish
2020-02-12 14:17     ` Liming Gao

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=6D19BFCB-B1F3-415E-9DDA-23992E98B637@apple.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