On another note, has anyone tried/sucessfully done gPXE efi in OVMF for qemu experimentation? I tried and it just locks up.<br><br><div class="gmail_quote">On Sun, May 23, 2010 at 2:44 PM, Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Sunday 23 May 2010 03:15:51 Glenn Brown wrote:<br>
> What interface is supported by .efidrv? EFI device<br>
> drivers can interface via the Simple Network Protocol (SNP) interface or<br>
> the UNDI32/64 (Undi) interface. Does gPXE use one of these 'standard'<br>
> interfaces?<br>
<br>
</div>SNP.<br>
<div class="im"><br>
> Does .efidrv reside above or below the EFI device driver interface?<br>
> That is, is it a way to provide a device driver to be used by EFI<br>
> clients, or is a shim to interface a gPXE boot stack over an underlying<br>
> EFI driver? That is, is it a provider or consumer of the interface?<br>
<br>
</div>.efidrv/.efirom provides an SNP interface that other EFI clients can use.<br>
<br>
.efi provides an EFI application that looks like regular BIOS-based gPXE.<br>
<div class="im"><br>
> Does gPXE support EFI-1.1 (Mac) or UEFI-2.0 (everyone else) or both?<br>
> Under what circumstances is each supported.<br>
<br>
</div>Written to UEFI-2.0, but I believe it does work on a Mac.<br>
<div class="im"><br>
> What services are provide by the .efirom? Is it just a PCI expansion<br>
> ROM holding the EFI driver? Something more? Something else?<br>
<br>
</div>Yes; .efirom is just the .efidrv binary packaged as an expansion ROM (using<br>
util/efirom.c).<br>
<div class="im"><br>
> What interface does the .efi application layer itself over?<br>
<br>
</div>It doesn't (at present) layer over any underlying network interface (either<br>
SNP or UNDI). The .efi application exists mainly as an initial bootstrap for<br>
getting gPXE EFI support working; the ultimate target was the .efidrv/.efirom<br>
format.<br>
<br>
That said, it would potentially be useful to add a driver that can utilise an<br>
underlying SNP interface.<br>
<font color="#888888"><br>
Michael<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
gPXE mailing list<br>
<a href="mailto:gPXE@etherboot.org">gPXE@etherboot.org</a><br>
<a href="http://etherboot.org/mailman/listinfo/gpxe" target="_blank">http://etherboot.org/mailman/listinfo/gpxe</a><br>
</div></div></blockquote></div><br>