I've tested the HttpBoot implementation with a simple test environment:
[QEMU] <---(tap0)---> [HOST]
Ovmf DHCP server
HTTP server
With a proper config for the dhcp and http server in the host, the firmware
successfully fetched the remote EFI file and executed it. However, the EFI
file couldn't get the correct device path so it's still not good enough for
the bootloader development.
Although the current HttpBoot implementation is incomplete, it would be
easier to develop and test the software stack with a virtual machine.
Gary Ching-Pang Lin (2):
NetworkPkg: Remove the hostname for the http request url
OvmfPkg: Add HttpBoot support
NetworkPkg/HttpDxe/HttpImpl.c | 14 +++++++++++++-
OvmfPkg/OvmfPkgIa32.dsc | 10 ++++++++++
OvmfPkg/OvmfPkgIa32.fdf | 5 +++++
OvmfPkg/OvmfPkgIa32X64.dsc | 10 ++++++++++
OvmfPkg/OvmfPkgIa32X64.fdf | 5 +++++
OvmfPkg/OvmfPkgX64.dsc | 10 ++++++++++
OvmfPkg/OvmfPkgX64.fdf | 5 +++++
7 files changed, 58 insertions(+), 1 deletion(-)
--
2.1.4
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
