[ipxe-devel] Image Load is gone?

[Jarrod Johnson]

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:

The 'if (1)' is a placeholder for a function to check loaded image for SNP
protocol support.  The snponly snpbus_probe function has an example of
doing this.

The way I wrangled 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.

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.


On Wed, May 8, 2013 at 5:04 PM, James A. Peltier <jpeltier at sfu.ca> wrote:

> 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.
>
> ------------------------------
>
> 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 <mbrown at 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 at lists.ipxe.org
>> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>>
>
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
>
>
>
> --
> James A. Peltier
> Manager, IT Services - Research Computing Group
> Simon Fraser University - Burnaby Campus
> Phone   : 778-782-6573
> Fax     : 778-782-3045
> E-Mail  : jpeltier at sfu.ca
> Website : http://www.sfu.ca/itservices
>
> “A successful person is one who can lay a solid foundation from the bricks
> others have thrown at them.” -David Brinkley via Luke Shaw
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130508/a08a5fda/attachment.htm>