mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-29 15:43:59 +08:00
5daf538a03
Is it meaningful/useful to enable EFI_VARS but not EFI? That's what GOOGLE_SMI does. Make it enable EFI also. Fixes this kconfig dependency warning: warning: (GOOGLE_SMI) selects EFI_VARS which has unmet direct dependencies (EFI) Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Acked-by: Mike Waychison <mikew@google.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
33 lines
909 B
Plaintext
33 lines
909 B
Plaintext
config GOOGLE_FIRMWARE
|
|
bool "Google Firmware Drivers"
|
|
depends on X86
|
|
default n
|
|
help
|
|
These firmware drivers are used by Google's servers. They are
|
|
only useful if you are working directly on one of their
|
|
proprietary servers. If in doubt, say "N".
|
|
|
|
menu "Google Firmware Drivers"
|
|
depends on GOOGLE_FIRMWARE
|
|
|
|
config GOOGLE_SMI
|
|
tristate "SMI interface for Google platforms"
|
|
depends on ACPI && DMI
|
|
select EFI
|
|
select EFI_VARS
|
|
help
|
|
Say Y here if you want to enable SMI callbacks for Google
|
|
platforms. This provides an interface for writing to and
|
|
clearing the EFI event log and reading and writing NVRAM
|
|
variables.
|
|
|
|
config GOOGLE_MEMCONSOLE
|
|
tristate "Firmware Memory Console"
|
|
depends on DMI
|
|
help
|
|
This option enables the kernel to search for a firmware log in
|
|
the EBDA on Google servers. If found, this log is exported to
|
|
userland in the file /sys/firmware/log.
|
|
|
|
endmenu
|