summaryrefslogtreecommitdiffstats
path: root/doc/api/efi.rst
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2020-02-29 08:01:07 -0500
committerTom Rini <trini@konsulko.com>2020-02-29 08:01:07 -0500
commit5045289820835ce0baf5d7cea86f9fdc6170d189 (patch)
tree5461a194898326e044d0087345aeea59d7220190 /doc/api/efi.rst
parent1e85aaf3723f0ecd06fcf62e2d2482749e1995d6 (diff)
parent71a7de4467030362ef2582c355c086eb5fc4143f (diff)
downloadu-boot-5045289820835ce0baf5d7cea86f9fdc6170d189.tar.gz
u-boot-5045289820835ce0baf5d7cea86f9fdc6170d189.tar.xz
u-boot-5045289820835ce0baf5d7cea86f9fdc6170d189.zip
Merge tag 'efi-2020-04-rc4-2' of https://gitlab.denx.de/u-boot/custodians/u-boot-efi
Pull request for UEFI sub-system for efi-2020-04-rc4 (2) In Linux next-20200228 patches have been merged to load an initial ramdisk using an EFI_LOAD_FILE2_PROTOCOL provided by the firmware. See commit ec93fc371f01 ("efi/libstub: Add support for loading the initrd from a device path"). The idea behind it is that the firmware should be responsible for validating the initrd in a secure boot setup. This pull-request comprises a patch series which let's U-Boot provide an initial implementation of the EFI_LOAD_FILE2_PROTOCOL providing the initrd.
Diffstat (limited to 'doc/api/efi.rst')
-rw-r--r--doc/api/efi.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/api/efi.rst b/doc/api/efi.rst
index bc59382608..631c0ceb1d 100644
--- a/doc/api/efi.rst
+++ b/doc/api/efi.rst
@@ -125,6 +125,15 @@ Graphical output protocol
.. kernel-doc:: lib/efi_loader/efi_gop.c
:internal:
+Load file 2 protocol
+~~~~~~~~~~~~~~~~~~~~
+
+The load file 2 protocol can be used by the Linux kernel to load the initial
+RAM disk. U-Boot can be configured to provide an implementation.
+
+.. kernel-doc:: lib/efi_loader/efi_load_initrd.c
+ :internal:
+
Network protocols
~~~~~~~~~~~~~~~~~