uefi.txt 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. UEFI, the Unified Extensible Firmware Interface, is a specification
  2. governing the behaviours of compatible firmware interfaces. It is
  3. maintained by the UEFI Forum - http://www.uefi.org/.
  4. UEFI is an evolution of its predecessor 'EFI', so the terms EFI and
  5. UEFI are used somewhat interchangeably in this document and associated
  6. source code. As a rule, anything new uses 'UEFI', whereas 'EFI' refers
  7. to legacy code or specifications.
  8. UEFI support in Linux
  9. =====================
  10. Booting on a platform with firmware compliant with the UEFI specification
  11. makes it possible for the kernel to support additional features:
  12. - UEFI Runtime Services
  13. - Retrieving various configuration information through the standardised
  14. interface of UEFI configuration tables. (ACPI, SMBIOS, ...)
  15. For actually enabling [U]EFI support, enable:
  16. - CONFIG_EFI=y
  17. - CONFIG_EFI_VARS=y or m
  18. The implementation depends on receiving information about the UEFI environment
  19. in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
  20. UEFI stub
  21. =========
  22. The "stub" is a feature that extends the Image/zImage into a valid UEFI
  23. PE/COFF executable, including a loader application that makes it possible to
  24. load the kernel directly from the UEFI shell, boot menu, or one of the
  25. lightweight bootloaders like Gummiboot or rEFInd.
  26. The kernel image built with stub support remains a valid kernel image for
  27. booting in non-UEFI environments.
  28. UEFI kernel support on ARM
  29. ==========================
  30. UEFI kernel support on the ARM architectures (arm and arm64) is only available
  31. when boot is performed through the stub.
  32. When booting in UEFI mode, the stub deletes any memory nodes from a provided DT.
  33. Instead, the kernel reads the UEFI memory map.
  34. The stub populates the FDT /chosen node with (and the kernel scans for) the
  35. following parameters:
  36. ________________________________________________________________________________
  37. Name | Size | Description
  38. ================================================================================
  39. linux,uefi-system-table | 64-bit | Physical address of the UEFI System Table.
  40. --------------------------------------------------------------------------------
  41. linux,uefi-mmap-start | 64-bit | Physical address of the UEFI memory map,
  42. | | populated by the UEFI GetMemoryMap() call.
  43. --------------------------------------------------------------------------------
  44. linux,uefi-mmap-size | 32-bit | Size in bytes of the UEFI memory map
  45. | | pointed to in previous entry.
  46. --------------------------------------------------------------------------------
  47. linux,uefi-mmap-desc-size | 32-bit | Size in bytes of each entry in the UEFI
  48. | | memory map.
  49. --------------------------------------------------------------------------------
  50. linux,uefi-mmap-desc-ver | 32-bit | Version of the mmap descriptor format.
  51. --------------------------------------------------------------------------------
  52. linux,uefi-stub-kern-ver | string | Copy of linux_banner from build.
  53. --------------------------------------------------------------------------------
  54. For verbose debug messages, specify 'uefi_debug' on the kernel command line.