I restored snponly.efi function with a PoC patch: https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/19447d9c39e06c3d5aabd198736cd23d8e40c870
I haven't gotten around to cleaning it up, it could be much better. On Fri, May 3, 2013 at 8:19 AM, Michael Brown <mbr...@fensystems.co.uk>wrote: > On Thursday 02 May 2013 23:14:47 Duane Voth wrote: > > I am right in expecting the snponly ipxe to work nicely with existing > > network devices right? Or perhaps this usage impacts the question above? > > Quite possibly not. EFI doesn't have a clean model for multiple users of > an > SNP interface. > > > Last, at what point does snp ipxe plug into the uEFI stack? Is the ipxe > > dhcp config separate from the EFI dhcp client? (I have noticed two > > different IP addresses being allocated for this same NIC/MAC) > > iPXE's TCP/IP stack is entirely separate from the EFI TCP/IP stack. EFI > knows > nothing about addresses obtained using DHCP inside iPXE. > > > Could ipxe use more of the existing protocols now that edk2 is more > stable? > > It could, but it's not going to. iPXE is going to deliberately avoid the > EDK2 > facilities and limitations. See http://ipxe.org/efi/vision for the > reason why. > > Michael > _______________________________________________ > ipxe-devel mailing list > ipxe-devel@lists.ipxe.org > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel >
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
