[gPXE] x86_64-efi build

[Mike Bishton]

Josh,

The output of the `nm bin-x86_64-efi/e1000e.efi.tmp` is attached.

addr2line returned an error as written. Switching -ef to -fe resulted in

??
??:0

Thanks,
Mike


Joshua Oreman wrote:
> On Fri, Apr 2, 2010 at 2:06 PM, Mike Bishton <mbishton at xes-inc.com> wrote:
>   
>> Hi Josh,
>>
>> Thanks for getting back to me.
>>
>> Thats good news, hopefully that means that I shouldn't run into too many
>> more difficulties moving forward :). I only brought up the question about
>> native EFI support because I've heard that Apple butchered the spec for
>> their firmware.
>>     
>
> gPXE didn't require any code changes to work on Apple's EFI, but I
> know the support was initially developed by Michael Brown for a
> company that was using a "normal" EFI stack.
>
>   
>> I'll work on getting write permissions to the wiki this afternoon so I can
>> start helping out with documenting the EFI build process.
>>     
>
> Thank you!
>
>   
>> Like I said before, I haven't really put much time into debugging this
>> myself, so I certainly don't expect you to. But, since you asked, here is
>> the output so far:
>> ...
>> Loading driver at 0x357BC000 EntryPoint=0x357C62D8 e1000e.efi
>> ...
>> RIP - 00000000357BC241, CS - 0000000000000038, RFLAGS - 0000000000010287
>>     
>
> Could you send the output of `nm bin-x86_64-efi/e1000e.efi.tmp`? Also,
> `echo 0x241 | addr2line -ef bin-x86_64-efi/e1000e.efi.tmp` may be
> helpful as well.
>
> Thanks,
>
> -- Josh
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100402/9727ca2d/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: symbols.txt
Url: http://etherboot.org/pipermail/gpxe/attachments/20100402/9727ca2d/attachment-0001.txt