Sigh, and I generated that against the wrong branch. Here is one that actually applies on current master:
>From 34f8069eb293d524824fe10efba30993c2cb1eb4 Mon Sep 17 00:00:00 2001 From: Leif Lindholm <[email protected]> Date: Wed, 8 Oct 2014 15:20:04 +0100 Subject: [PATCH] ArmVExpressPkg: enable specifying firmware version string on build If FIRMWARE_VER is defined on the build command line, set gEfiMdeModulePkgTokenSpaceGuid.PcdFirmwareVersionString based on it. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Leif Lindholm <[email protected]> --- ArmPlatformPkg/ArmVExpressPkg/ArmVExpress.dsc.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress.dsc.inc b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress.dsc.inc index fb2efd5..c97aa58 100644 --- a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress.dsc.inc +++ b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress.dsc.inc @@ -256,6 +256,9 @@ [PcdsFixedAtBuild.common] gArmPlatformTokenSpaceGuid.PcdFirmwareVendor|"ARM Versatile Express" +!ifdef $(FIRMWARE_VER) + gEfiMdeModulePkgTokenSpaceGuid.PcdFirmwareVersionString|L"$(FIRMWARE_VER)" +!endif gEmbeddedTokenSpaceGuid.PcdEmbeddedPrompt|"VExpress" gEfiMdePkgTokenSpaceGuid.PcdMaximumUnicodeStringLength|1000000 -- 1.7.10.4 ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
