summaryrefslogtreecommitdiff
path: root/include/ti-usb-phy-uboot.h
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2023-11-18 15:52:53 -0500
committerTom Rini <trini@konsulko.com>2023-11-18 15:52:53 -0500
commit9e4b42267e1fb5805ecddbb92629f456d8cd4047 (patch)
tree55418a14399a744ee648c997eeb1b3fdb3fb5ef4 /include/ti-usb-phy-uboot.h
parentae7ec8b0be41b59ef323f7531c0fe6745e8fef45 (diff)
parentc022eed4bedf2e16e737fde22b03289d2a48cb27 (diff)
downloadu-boot-9e4b42267e1fb5805ecddbb92629f456d8cd4047.tar.gz
u-boot-9e4b42267e1fb5805ecddbb92629f456d8cd4047.tar.bz2
u-boot-9e4b42267e1fb5805ecddbb92629f456d8cd4047.zip
Merge tag 'efi-next-18112023' of https://source.denx.de/u-boot/custodians/u-boot-tpm into next
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/CAOMZO5CoduEgwgdQiybmoKh6qQZOezUtRRQO4ecaGdZBBz5dDw@mail.gmail.c om/ 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
Diffstat (limited to 'include/ti-usb-phy-uboot.h')
0 files changed, 0 insertions, 0 deletions