Kconfig 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. config EFI_LOADER
  2. bool "Support running UEFI applications"
  3. depends on (ARM || X86 || RISCV || SANDBOX) && OF_LIBFDT
  4. # We need EFI_STUB_64BIT to be set on x86_64 with EFI_STUB
  5. depends on !EFI_STUB || !X86_64 || EFI_STUB_64BIT
  6. # We need EFI_STUB_32BIT to be set on x86_32 with EFI_STUB
  7. depends on !EFI_STUB || !X86 || X86_64 || EFI_STUB_32BIT
  8. default y
  9. select LIB_UUID
  10. select HAVE_BLOCK_DEVICE
  11. select REGEX
  12. imply CFB_CONSOLE_ANSI
  13. help
  14. Select this option if you want to run UEFI applications (like GNU
  15. GRUB or iPXE) on top of U-Boot. If this option is enabled, U-Boot
  16. will expose the UEFI API to a loaded application, enabling it to
  17. reuse U-Boot's device drivers.
  18. if EFI_LOADER
  19. config EFI_LOADER_HII
  20. bool "HII protocols"
  21. default y
  22. help
  23. The Human Interface Infrastructure is a complicated framework that
  24. allows UEFI applications to draw fancy menus and hook strings using
  25. a translation framework.
  26. U-Boot implements enough of its features to be able to run the UEFI
  27. Shell, but not more than that.
  28. config EFI_UNICODE_COLLATION_PROTOCOL
  29. bool "Unicode collation protocol"
  30. default y
  31. help
  32. The Unicode collation protocol is used for lexical comparisons. It is
  33. required to run the UEFI shell.
  34. if EFI_UNICODE_COLLATION_PROTOCOL
  35. config EFI_UNICODE_CAPITALIZATION
  36. bool "Support Unicode capitalization"
  37. default y
  38. help
  39. Select this option to enable correct handling of the capitalization of
  40. Unicode codepoints in the range 0x0000-0xffff. If this option is not
  41. set, only the the correct handling of the letters of the codepage
  42. used by the FAT file system is ensured.
  43. endif
  44. config EFI_LOADER_BOUNCE_BUFFER
  45. bool "EFI Applications use bounce buffers for DMA operations"
  46. depends on ARM64
  47. default n
  48. help
  49. Some hardware does not support DMA to full 64bit addresses. For this
  50. hardware we can create a bounce buffer so that payloads don't have to
  51. worry about platform details.
  52. config EFI_PLATFORM_LANG_CODES
  53. string "Language codes supported by firmware"
  54. default "en-US"
  55. help
  56. This value is used to initialize the PlatformLangCodes variable. Its
  57. value is a semicolon (;) separated list of language codes in native
  58. RFC 4646 format, e.g. "en-US;de-DE". The first language code is used
  59. to initialize the PlatformLang variable.
  60. endif