05 Jan, 2015
1 commit
-
efivars is currently enabled under MISC_FILESYSTEMS, which is decribed
as "such as filesystems that came from other operating systems".
In reality, it is a pseudo filesystem, providing access to the kernel
UEFI variable interface.Since this is the preferred interface for accessing UEFI variables, over
the legacy efivars interface, also build it by default as a module if
CONFIG_EFI.Signed-off-by: Leif Lindholm
Signed-off-by: Matt Fleming
17 Apr, 2013
2 commits
-
This registers /sys/firmware/efi/{,systab,efivars/} whenever EFI is enabled
and the system is booted with EFI.This allows
*) userspace to check for the existence of /sys/firmware/efi as a way
to determine whether or it is running on an EFI system.
*) 'mount -t efivarfs none /sys/firmware/efi/efivars' without manually
loading any modules.[ Also, move the efivar API into vars.c and unconditionally compile it.
This allows us to move efivars.c, which now only contains the sysfs
variable code, into the firmware/efi directory. Note that the efivars.c
filename is kept to maintain backwards compatability with the old
efivars.ko module. With this patch it is now possible for efivarfs
to be built without CONFIG_EFI_VARS - Matt ]Cc: Seiji Aguchi
Cc: Tony Luck
Cc: Mike Waychison
Cc: Kay Sievers
Cc: Jeremy Kerr
Cc: Matthew Garrett
Cc: Chun-Yi Lee
Cc: Andy Whitcroft
Cc: Tobias Powalowski
Signed-off-by: Tom Gundersen
Signed-off-by: Matt Fleming -
Now that efivarfs uses the efivar API, move it out of efivars.c and
into fs/efivarfs where it belongs. This move will eventually allow us
to enable the efivarfs code without having to also enable
CONFIG_EFI_VARS built, and vice versa.Furthermore, things like,
mount -t efivarfs none /sys/firmware/efi/efivars
will now work if efivarfs is built as a module without requiring the
use of MODULE_ALIAS(), which would have been necessary when the
efivarfs code was part of efivars.c.Cc: Matthew Garrett
Cc: Jeremy Kerr
Reviewed-by: Tom Gundersen
Tested-by: Tom Gundersen
Signed-off-by: Matt Fleming