<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
Josh,<br>
<br>
The output of the `nm bin-x86_64-efi/e1000e.efi.tmp` is attached. <br>
<br>
addr2line returned an error as written. Switching -ef to -fe resulted
in <br>
<br>
<tt>??<br>
??:0</tt><br>
<br>
Thanks,<br>
Mike<br>
<br>
<br>
Joshua Oreman wrote:
<blockquote type="cite" cite="mid:g2x197f0ba31004021117hafb3806bubecbb6de893af217@mail.gmail.com">
<pre wrap="">On Fri, Apr 2, 2010 at 2:06 PM, Mike Bishton <a href="mailto:mbishton@xes-inc.com" class="moz-txt-link-rfc2396E"><mbishton@xes-inc.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
<blockquote type="cite">
<pre wrap="">I'll work on getting write permissions to the wiki this afternoon so I can
start helping out with documenting the EFI build process.
</pre>
</blockquote>
<pre wrap=""><!---->
Thank you!
</pre>
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><!---->
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
</pre>
</blockquote>
</body>
</html>