diff options
author | Sami Mujawar <sami.mujawar@arm.com> | 2020-10-02 22:13:57 +0100 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-10-16 17:21:04 +0000 |
commit | d3095addf31a0bfa48a4be64299928b4550d8e66 (patch) | |
tree | 08cd9b8a55a28f136836309a9e7b9e0683fd8704 /OvmfPkg/Sec | |
parent | cd09c38465f662674619c10abd9d35a25e47146e (diff) | |
download | edk2-d3095addf31a0bfa48a4be64299928b4550d8e66.tar.gz edk2-d3095addf31a0bfa48a4be64299928b4550d8e66.tar.bz2 edk2-d3095addf31a0bfa48a4be64299928b4550d8e66.zip |
ArmPlatformPkg: Dynamic flash variable base
Some virtual machine managers like kvmtool can relocate
the devices in the system memory map. The information
about the devices location in memory is described in the
device tree. Therefore, the CFI memory region and the
associated Non volatile storage variables need to be
adjusted accordingly.
To support such use cases the non-volatile storage
variable base PCD PcdFlashNvStorageVariableBase has
been defined as a dynamic PCD.
The NOR flash driver was using the Flash non-volatile
storage variable base PCD as a fixed PCD, thereby
preventing runtime resolution of the variable base
address.
Therefore update the NOR flash driver to load the
PCD using PcdGet32 instead of FixedPcdGet32.
Signed-off-by: Sami Mujawar <sami.mujawar@arm.com>
Reviewed-by: Ard Biesheuvel <Ard.Biesheuvel@arm.com>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'OvmfPkg/Sec')
0 files changed, 0 insertions, 0 deletions