Home Verkennen Help
Inloggen
rama982
/
kernel_xiaomi_lancelot
Volgen 1
Ster 0
Vork 0
Bestanden Kwesties 0 Pull-aanvragen 0 Wiki
Boom: b940215a20
Aftakkingen Labels
kernel_xiaom...
/
drivers
/
firmware
/
google
/
Kconfig

Kconfig 2.3 KB
Geschiedenis Ruwe

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475 
  1. menuconfig GOOGLE_FIRMWARE
    2. 

  2. 	bool "Google Firmware Drivers"
    3. 

  3. 	default n
    4. 

  4. 	help
    5. 

  5. 	  These firmware drivers are used by Google's servers.  They are
    6. 

  6. 	  only useful if you are working directly on one of their
    7. 

  7. 	  proprietary servers.  If in doubt, say "N".
    8. 

  8. 

  9. if GOOGLE_FIRMWARE
    10. 

  10. 

  11. config GOOGLE_SMI
    12. 

  12. 	tristate "SMI interface for Google platforms"
    13. 

  13. 	depends on X86 && ACPI && DMI && EFI
    14. 

  14. 	select EFI_VARS
    15. 

  15. 	help
    16. 

  16. 	  Say Y here if you want to enable SMI callbacks for Google
    17. 

  17. 	  platforms.  This provides an interface for writing to and
    18. 

  18. 	  clearing the EFI event log and reading and writing NVRAM
    19. 

  19. 	  variables.
    20. 

  20. 

  21. config GOOGLE_COREBOOT_TABLE
    22. 

  22. 	tristate
    23. 

  23. 	depends on GOOGLE_COREBOOT_TABLE_ACPI || GOOGLE_COREBOOT_TABLE_OF
    24. 

  24. 

  25. config GOOGLE_COREBOOT_TABLE_ACPI
    26. 

  26. 	tristate "Coreboot Table Access - ACPI"
    27. 

  27. 	depends on ACPI
    28. 

  28. 	select GOOGLE_COREBOOT_TABLE
    29. 

  29. 	help
    30. 

  30. 	  This option enables the coreboot_table module, which provides other
    31. 

  31. 	  firmware modules to access to the coreboot table. The coreboot table
    32. 

  32. 	  pointer is accessed through the ACPI "GOOGCB00" object.
    33. 

  33. 	  If unsure say N.
    34. 

  34. 

  35. config GOOGLE_COREBOOT_TABLE_OF
    36. 

  36. 	tristate "Coreboot Table Access - Device Tree"
    37. 

  37. 	depends on OF
    38. 

  38. 	select GOOGLE_COREBOOT_TABLE
    39. 

  39. 	help
    40. 

  40. 	  This option enable the coreboot_table module, which provide other
    41. 

  41. 	  firmware modules to access coreboot table. The coreboot table pointer
    42. 

  42. 	  is accessed through the device tree node /firmware/coreboot.
    43. 

  43. 	  If unsure say N.
    44. 

  44. 

  45. config GOOGLE_MEMCONSOLE
    46. 

  46. 	tristate
    47. 

  47. 	depends on GOOGLE_MEMCONSOLE_X86_LEGACY || GOOGLE_MEMCONSOLE_COREBOOT
    48. 

  48. 

  49. config GOOGLE_MEMCONSOLE_X86_LEGACY
    50. 

  50. 	tristate "Firmware Memory Console - X86 Legacy support"
    51. 

  51. 	depends on X86 && ACPI && DMI
    52. 

  52. 	select GOOGLE_MEMCONSOLE
    53. 

  53. 	help
    54. 

  54. 	  This option enables the kernel to search for a firmware log in
    55. 

  55. 	  the EBDA on Google servers.  If found, this log is exported to
    56. 

  56. 	  userland in the file /sys/firmware/log.
    57. 

  57. 

  58. config GOOGLE_MEMCONSOLE_COREBOOT
    59. 

  59. 	tristate "Firmware Memory Console"
    60. 

  60. 	depends on GOOGLE_COREBOOT_TABLE
    61. 

  61. 	select GOOGLE_MEMCONSOLE
    62. 

  62. 	help
    63. 

  63. 	  This option enables the kernel to search for a firmware log in
    64. 

  64. 	  the coreboot table.  If found, this log is exported to userland
    65. 

  65. 	  in the file /sys/firmware/log.
    66. 

  66. 

  67. config GOOGLE_VPD
    68. 

  68. 	tristate "Vital Product Data"
    69. 

  69. 	depends on GOOGLE_COREBOOT_TABLE
    70. 

  70. 	help
    71. 

  71. 	  This option enables the kernel to expose the content of Google VPD
    72. 

  72. 	  under /sys/firmware/vpd.
    73. 

  73. 

  74. endif # GOOGLE_FIRMWARE
    75. 

  75.