Hi, On Wed, Jul 12, 2017 at 10:35 PM, Heinrich Schuchardt <[email protected]> wrote: > > Please, reword http://ipxe.org/appnote/buildtargets in way that a newbie > can pick up the meaning. Some terms like NII are not easily found by > search engines. I suggest: > > * Target snponly.efi assumes that iPXE was loaded via a network > interface card (NIC). This NIC or a parent in the device tree supports > either the the Simple Network Protocol (SNP) or the Network Interface > Identifier Protocol (NII) in conjunction with the Universal Network > Driver Interface (UNDI). The NIC used for loading is passed as system > handle to the EFI entry point. IPXE then activates only this specific > network interface card it was chained from.
Thanks for your suggestion I'm not quite sure what you mean by conjunction here, since UNDI can only be used for pcbios builds and SNP/NII can only be used for EFI. IMHO the explanation you propose are a bit on the long side. and "should only find and boot NIC device it was chained from" quite clearly states that it only uses the device from which the handle was given. but using words such as handles and "device tree" is not very newbie friendly. > > * Target snp.efi does not make any assumptions about the device it was > loaded from but activates all network interface cards that support > either the Simple Network Protocol (SNP) or the Network Interface > Identifier Protocol (NII). > Here " same as snponly but tries to boot all devices and not just the one it was chained via" Will try to add Simple Network Protocol and Network Interface Identifier Protocol to the page /Christian _______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
