summaryrefslogtreecommitdiff
path: root/arch/arm/configs
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2022-06-20 14:34:03 +0300
committerArd Biesheuvel <ardb@kernel.org>2022-06-24 21:40:19 +0300
commit0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 (patch)
tree7069d2c58ce3e649fe97aed8f74743a710b260f0 /arch/arm/configs
parent5ac941367a6f85777ef34ec15d60e17ea8e446d4 (diff)
downloadlinux-0f5b2c69a4cbe4166ca24b76d5ada98ed2867741.tar.xz
efi: vars: Remove deprecated 'efivars' sysfs interface
Commit 5d9db883761a ("efi: Add support for a UEFI variable filesystem") dated Oct 5, 2012, introduced a new efivarfs pseudo-filesystem to replace the efivars sysfs interface that was used up to that point to expose EFI variables to user space. The main problem with the sysfs interface was that it only supported up to 1024 bytes of payload per file, whereas the underlying variables themselves are only bounded by a platform specific per-variable and global limit that is typically much higher than 1024 bytes. The deprecated sysfs interface is only enabled on x86 and Itanium, other EFI enabled architectures only support the efivarfs pseudo-filesystem. So let's finally rip off the band aid, and drop the old interface entirely. This will make it easier to refactor and clean up the underlying infrastructure that is shared between efivars, efivarfs and efi-pstore, and is long overdue for a makeover. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'arch/arm/configs')
-rw-r--r--arch/arm/configs/milbeaut_m10v_defconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
index 7c07f9893a0f..9b4789af0201 100644
--- a/arch/arm/configs/milbeaut_m10v_defconfig
+++ b/arch/arm/configs/milbeaut_m10v_defconfig
@@ -44,7 +44,6 @@ CONFIG_ARM_CPUIDLE=y
CONFIG_VFP=y
CONFIG_NEON=y
CONFIG_KERNEL_MODE_NEON=y
-CONFIG_EFI_VARS=m
CONFIG_EFI_CAPSULE_LOADER=m
CONFIG_ARM_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM_NEON=m