<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml">
<head>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType name="State" namespaceuri="urn:schemas-microsoft-com:office:smarttags">
<o:SmartTagType name="City" namespaceuri="urn:schemas-microsoft-com:office:smarttags">
<o:SmartTagType name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body vlink="blue" link="blue" lang="EN-US">
<div class="Section1">
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy">Thanks for pointing this out. TianoCore
does use 7. Personally, I think 9 makes much more sense, because the OS loader
needs to be architecture-specific. Simply saying “<st1:place w:st="on"><st1:City w:st="on">EFI</st1:City> <st1:State w:st="on">BC</st1:State></st1:place>”
is not enough information to be able to load an OS.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy">So, it’s a question of whether we
want to follow the standard or follow the de facto standard. I’m happy to
change the patch for the sake of compatibility if people think that is the
right way to go.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><br>
Geoff<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" color="navy" size="2"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="text-align:center" align="center" class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">
<hr tabindex="-1" align="center" width="100%" size="2">
</span></font></div>
<p class="MsoNormal"><b><font face="Tahoma" size="2"><span style="font-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size:10.0pt;font-family:Tahoma"> Jarrod Johnson
[mailto:jarrod.b.johnson@gmail.com] <br>
<b><span style="font-weight:bold">Sent:</span></b> Friday, May 28, 2010 6:20 AM<br>
<b><span style="font-weight:bold">To:</span></b> Stefan Hajnoczi<br>
<b><span style="font-weight:bold">Cc:</span></b> Geoff Lywood;
gpxe-devel@etherboot.org<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [gPXE-devel] [PATCH]
Use correct DHCP options on EFI</span></font><o:p></o:p></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt">FYI, IBM UEFI uses arch 7 (efi basecode) when their UEFI code executes.
What is right or wrong, dunno, but currently this patch differs from
their behavior (which might inherit from TianoCore, not sure). Might want
to double check TianoCore to see if they also use 7. I think 9 would have
been more precise and implied 7 and so I prefer what this patch does, thought
I'd just point out what is happening elsewhere in uefi.<o:p></o:p></span></font></p>
<div>
<div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt">On Fri, May 28, 2010 at 1:19 AM, Stefan Hajnoczi <<a href="mailto:stefanha@gmail.com">stefanha@gmail.com</a>> wrote:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt">When adding new files the FILE_LICENCE() macro should be used.
For<br>
example, include/gpxe/list.h uses the macro.<br>
<br>
include/compiler.h has the macro and possible license constants.<br>
<br>
The build system has .license targets (e.g. make<br>
bin/10ec8139.rom.licence) which give a breakdown of licensing for all<br>
involved files.<br>
<br>
Would it be possible for you to add this?<br>
<br>
Thanks,<br>
<font color="#888888"><span style="color:#888888">Stefan</span></font><o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt">_______________________________________________<br>
gPXE-devel mailing list<br>
<a href="mailto:gPXE-devel@etherboot.org">gPXE-devel@etherboot.org</a><br>
<a target="_blank" href="http://etherboot.org/mailman/listinfo/gpxe-devel">http://etherboot.org/mailman/listinfo/gpxe-devel</a><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
</div>
</div>
</div>
</div>
</body>
</html>