summaryrefslogtreecommitdiff
path: root/configs/xilinx_zynqmp_virt_defconfig
diff options
context:
space:
mode:
authorIlias Apalodimas <ilias.apalodimas@linaro.org>2021-06-22 17:38:52 +0300
committerHeinrich Schuchardt <xypron.glpk@gmx.de>2021-07-02 10:37:01 +0300
commitb891ff18f8999c89d00e1a963a4bc07afe3ae061 (patch)
tree244a0552569a929209e9a33c35221516271a6f77 /configs/xilinx_zynqmp_virt_defconfig
parent3ef772230db077a7122de11d93cfc4ff570fb4a7 (diff)
downloadu-boot-b891ff18f8999c89d00e1a963a4bc07afe3ae061.tar.xz
efi_loader: Force a single FMP instance per hardware store
Chapter 23 of the EFI spec (rev 2.9) says: "A specific updatable hardware firmware store must be represented by exactly one FMP instance". This is not the case for us, since both of our FMP protocols can be installed at the same time because they are controlled by a single 'dfu_alt_info' env variable. So make the config options depend on each other and allow the user to install one of them at any given time. If we fix the meta-data provided by the 'dfu_alt_info' in the future, to hint about the capsule type (fit or raw) we can revise this and enable both FMPs to be installed, as long as they target different firmware hardware stores Note that we are not using a Kconfig 'choice' on purpose, since we want to allow both of those to be installed and tested in sandbox Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Diffstat (limited to 'configs/xilinx_zynqmp_virt_defconfig')
-rw-r--r--configs/xilinx_zynqmp_virt_defconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/configs/xilinx_zynqmp_virt_defconfig b/configs/xilinx_zynqmp_virt_defconfig
index b9351d4504..a3d944d94b 100644
--- a/configs/xilinx_zynqmp_virt_defconfig
+++ b/configs/xilinx_zynqmp_virt_defconfig
@@ -187,5 +187,4 @@ CONFIG_OF_LIBFDT_OVERLAY=y
CONFIG_EFI_SET_TIME=y
CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
CONFIG_EFI_CAPSULE_ON_DISK=y
-CONFIG_EFI_CAPSULE_FIRMWARE_FIT=y
CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y