On Wed, Jan 13, 2016 at 01:43:38PM +0100, Laszlo Ersek wrote: > I just noticed that the most recent release of BITS provides a > standalone HTTP client! > > http://biosbits.org/news/bits-2070/ > > Josh, a couple of points: > > - edk2 doesn't provide EFI_IP4_CONFIG_PROTOCOL any longer; it provides > EFI_IP4_CONFIG2_PROTOCOL. I haven't tested this new release of BITS > just yet, but I know this caused problems for a few consumers of edk2.
Most existing BIOSes we've worked with don't provide the newer protocol, though. So at a minimum we'll have to support both. Probably not too difficult to do, though. > - OVMF *should* provide EFI_DNS4_SERVICE_BINDING_PROTOCOL: if you > build it with -D HTTP_BOOT_ENABLE, then "NetworkPkg/DnsDxe/DnsDxe.inf" > gets included, and that INF file says: Good to know. However, most existing BIOSes, including current-generation BIOSes, don't provide that protocol. We've actually seriously considered a minimal pure-Python implementation of DNS that can fetch A records, to work around that. > Are you using Gerd's RPMs? No, we typically build OVMF from source ourselves, using its default configuration. - Josh Triplett _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
