<div dir="ltr">If micahel doesn't get around to it in the next few days, I'll try to neaten up the ugly edges. To enumurate the ugly edges of that patch if someone else wants to take a swing:<div><br></div><div style>
The 'if (1)' is a placeholder for a function to check loaded image for SNP protocol support. The snponly <font color="#000000" face="monospace"><span style="font-size:12px;white-space:pre">snpbus_probe function has an example of doing this.</span></font></div>
<div style><font color="#000000" face="monospace"><span style="font-size:12px;white-space:pre"><br></span></font></div><div style><font color="#000000" face="monospace"><span style="font-size:12px;white-space:pre">The way I wrangled </span></font><span style="color:rgb(0,136,0);font-family:monospace;font-size:12px;white-space:pre">loaded.image->DeviceHandle and friends didn;t sit right with me because I didn't quite take the time to understand the context. At a bare minimum, it should be conditional upon the above if statement coming through.</span><br>
</div><div style><span style="color:rgb(0,136,0);font-family:monospace;font-size:12px;white-space:pre"><br></span></div><div style><span style="color:rgb(0,136,0);font-family:monospace;font-size:12px;white-space:pre">However, if all you want is snoponly.efi in the very short term, apply that patch against master and you'll be able to build snponly.efi competently, just probably no other target.</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 8, 2013 at 5:04 PM, James A. Peltier <span dir="ltr"><<a href="mailto:jpeltier@sfu.ca" target="_blank">jpeltier@sfu.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:12pt;font-family:times new roman,new york,times,serif">I would REALLY like the ability to load in snponly.efi . It would certainly make it very easy for me to provide the single unified installation menu that I have for all hardware. It really sucks that this isn't in the main code base.<br>
<br><hr><div><div class="h5"><blockquote style="padding-left:5px;font-size:12pt;font-style:normal;margin-left:5px;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal;border-left:2px solid rgb(16,16,255)">
<div dir="ltr"><div>I restored snponly.efi function with a PoC patch:<br><a href="https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/19447d9c39e06c3d5aabd198736cd23d8e40c870" target="_blank">https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/19447d9c39e06c3d5aabd198736cd23d8e40c870</a><br>
<br></div>I haven't gotten around to cleaning it up, it could be much better.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 3, 2013 at 8:19 AM, Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk" target="_blank">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>On Thursday 02 May 2013 23:14:47 Duane Voth wrote:<br>
> I am right in expecting the snponly ipxe to work nicely with existing<br>
> network devices right? Or perhaps this usage impacts the question above?<br>
<br>
</div>Quite possibly not. EFI doesn't have a clean model for multiple users of an<br>
SNP interface.<br>
<div><br>
> Last, at what point does snp ipxe plug into the uEFI stack? Is the ipxe<br>
> dhcp config separate from the EFI dhcp client? (I have noticed two<br>
> different IP addresses being allocated for this same NIC/MAC)<br>
<br>
</div>iPXE's TCP/IP stack is entirely separate from the EFI TCP/IP stack. EFI knows<br>
nothing about addresses obtained using DHCP inside iPXE.<br>
<div><br>
> Could ipxe use more of the existing protocols now that edk2 is more stable?<br>
<br>
</div>It could, but it's not going to. iPXE is going to deliberately avoid the EDK2<br>
facilities and limitations. See <a href="http://ipxe.org/efi/vision" target="_blank">http://ipxe.org/efi/vision</a> for the reason why.<br>
<div><div><br>
Michael<br>
_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>ipxe-devel mailing list<br><a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br><a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
</blockquote><br><br><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><span name="x"></span>James A. Peltier<br>Manager, IT Services - Research Computing Group<br>Simon Fraser University - Burnaby Campus<br>
Phone : <a href="tel:778-782-6573" value="+17787826573" target="_blank">778-782-6573</a><br>Fax : <a href="tel:778-782-3045" value="+17787823045" target="_blank">778-782-3045</a><br>E-Mail : <a href="mailto:jpeltier@sfu.ca" target="_blank">jpeltier@sfu.ca</a><br>
Website : <a href="http://www.sfu.ca/itservices" target="_blank">http://www.sfu.ca/itservices</a><br><br>“A successful person is one who can lay a solid foundation from the bricks others have thrown at them.” -David Brinkley via Luke Shaw<span name="x"></span><br>
</div></font></span></div></div><br>_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
<br></blockquote></div><br></div>