On Sat, Nov 18, 2023 at 10:29:45PM +0200, Ilias Apalodimas wrote:
Hi Tom,
The following changes since commit ae7ec8b0be41b59ef323f7531c0fe6745e8fef45:
Merge branch '2023-11-16-assorted-updates' into next (2023-11-17 08:38:05 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-tpm/ tags/efi-next-18112023
for you to fetch changes up to c022eed4bedf2e16e737fde22b03289d2a48cb27:
doc: uefi: add HTTP Boot support (2023-11-18 10:08:09 +0200)
EFI HTTP Boot is currently supported by using a combination of wget, blkmap and bootefi commands. The user has to download the image, mount it using blkmap and then execute the efi installer using bootefi. This series simplifies the user experience. Instead of doing all the steps manually, users can now enable a new Kconfig (EFI_HTTP_BOOT) which will select wget, blkmap and dns options. They can then use efidebug command to add a boot option for the EFI Bootmanager using => efidebug boot add -u 3 netinst http://<path> => efidebug boot order 3 => bootefi bootmgr
The boot manager will automatically download and mount the image. Once it's mounted it will locate and launch the installer.
It's worth noting that this rarely fails, but the reason is irrelevant to the current patchset. More information can be found here https://lore.kernel.org/u-boot/CAOMZO5CoduEgwgdQiybmoKh6qQZOezUtRRQO4ecaGdZB... The tl;dr is that wget sometimes fails to download the file correctly or set the size env variables. We expect all these to be solved once LWIP is stable and pulled
The CI reported no issues https://source.denx.de/u-boot/custodians/u-boot-tpm/-/pipelines/18623 Please consider pulling!
Applied to u-boot/next, thanks!