Hi, I was under the impression that the UEFI firmware would maintain the network connection unless a EFI program or OS determine to create a new connection. Take PXE for example. After the bootloader is loaded, it can utilize the PxeBaseCode protocol to download the OS image with the existed connection without starting the DHCP process again. However, the current implementation of HttpBoot seems to be another case.
In HttpBootDxeLoadFile() in NetworkPkg/HttpBootDxe/HttpBootImpl.c, the driver closes the DHCP4 connection right after the file is loaded. This means the bootloader has to set up the network connection on its own if it needs to load a remote file. My question is: what's the expection for a bootloader/Network Boot Program? Should the bootloader always create its own connection for HTTP Boot? Thanks, Gary Lin _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
