2017-03-28 10:11:25 -06:00
|
|
|
menuconfig GOOGLE_FIRMWARE
|
2011-04-29 18:39:31 -06:00
|
|
|
bool "Google Firmware Drivers"
|
|
|
|
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".
|
|
|
|
|
2017-03-28 10:11:25 -06:00
|
|
|
if GOOGLE_FIRMWARE
|
2011-04-29 18:39:31 -06:00
|
|
|
|
2011-04-29 18:39:19 -06:00
|
|
|
config GOOGLE_SMI
|
|
|
|
tristate "SMI interface for Google platforms"
|
2018-10-12 10:04:47 -06:00
|
|
|
depends on X86 && ACPI && DMI
|
2011-04-29 18:39:19 -06:00
|
|
|
help
|
|
|
|
Say Y here if you want to enable SMI callbacks for Google
|
|
|
|
platforms. This provides an interface for writing to and
|
2018-10-12 10:04:47 -06:00
|
|
|
clearing the event log. If EFI_VARS is also enabled this
|
|
|
|
driver provides an interface for reading and writing NVRAM
|
2011-04-29 18:39:19 -06:00
|
|
|
variables.
|
2011-04-29 18:39:25 -06:00
|
|
|
|
2017-03-28 10:11:27 -06:00
|
|
|
config GOOGLE_COREBOOT_TABLE
|
2018-08-15 14:37:06 -06:00
|
|
|
tristate "Coreboot Table Access"
|
|
|
|
depends on ACPI || OF
|
2017-03-28 10:11:27 -06:00
|
|
|
help
|
|
|
|
This option enables the coreboot_table module, which provides other
|
2018-08-15 14:37:06 -06:00
|
|
|
firmware modules access to the coreboot table. The coreboot table
|
|
|
|
pointer is accessed through the ACPI "GOOGCB00" object or the
|
|
|
|
device tree node /firmware/coreboot.
|
2017-03-28 10:11:27 -06:00
|
|
|
If unsure say N.
|
|
|
|
|
2018-08-15 14:37:06 -06:00
|
|
|
config GOOGLE_COREBOOT_TABLE_ACPI
|
|
|
|
tristate
|
|
|
|
select GOOGLE_COREBOOT_TABLE
|
|
|
|
|
2017-03-28 10:11:29 -06:00
|
|
|
config GOOGLE_COREBOOT_TABLE_OF
|
2018-08-15 14:37:06 -06:00
|
|
|
tristate
|
2017-03-28 10:11:29 -06:00
|
|
|
select GOOGLE_COREBOOT_TABLE
|
|
|
|
|
2011-04-29 18:39:25 -06:00
|
|
|
config GOOGLE_MEMCONSOLE
|
2017-03-28 10:11:26 -06:00
|
|
|
tristate
|
2017-03-28 10:11:27 -06:00
|
|
|
depends on GOOGLE_MEMCONSOLE_X86_LEGACY || GOOGLE_MEMCONSOLE_COREBOOT
|
2017-03-28 10:11:26 -06:00
|
|
|
|
|
|
|
config GOOGLE_MEMCONSOLE_X86_LEGACY
|
|
|
|
tristate "Firmware Memory Console - X86 Legacy support"
|
|
|
|
depends on X86 && ACPI && DMI
|
|
|
|
select GOOGLE_MEMCONSOLE
|
2011-04-29 18:39:25 -06:00
|
|
|
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.
|
2011-04-29 18:39:31 -06:00
|
|
|
|
2018-01-24 18:41:20 -07:00
|
|
|
config GOOGLE_FRAMEBUFFER_COREBOOT
|
|
|
|
tristate "Coreboot Framebuffer"
|
|
|
|
depends on FB_SIMPLE
|
|
|
|
depends on GOOGLE_COREBOOT_TABLE
|
|
|
|
help
|
|
|
|
This option enables the kernel to search for a framebuffer in
|
|
|
|
the coreboot table. If found, it is registered with simplefb.
|
|
|
|
|
2017-03-28 10:11:27 -06:00
|
|
|
config GOOGLE_MEMCONSOLE_COREBOOT
|
|
|
|
tristate "Firmware Memory Console"
|
|
|
|
depends on GOOGLE_COREBOOT_TABLE
|
|
|
|
select GOOGLE_MEMCONSOLE
|
|
|
|
help
|
|
|
|
This option enables the kernel to search for a firmware log in
|
|
|
|
the coreboot table. If found, this log is exported to userland
|
|
|
|
in the file /sys/firmware/log.
|
|
|
|
|
2017-04-12 10:56:19 -06:00
|
|
|
config GOOGLE_VPD
|
|
|
|
tristate "Vital Product Data"
|
|
|
|
depends on GOOGLE_COREBOOT_TABLE
|
|
|
|
help
|
|
|
|
This option enables the kernel to expose the content of Google VPD
|
|
|
|
under /sys/firmware/vpd.
|
|
|
|
|
2017-03-28 10:11:25 -06:00
|
|
|
endif # GOOGLE_FIRMWARE
|