<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0pt;
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:purple;
text-decoration:underline;}
tt
{font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>After downloading the firmware, the ARM is
told by the boot2 to jump to a specific location of the internal memory. If the
firmware is not downloaded, the boot2 starts the grab the firmware from the Flash
and jumps to the same location of the internal memory once that is done. The
flash tool does not figure out anything here. The boot2 code is smart enough to
figure that out.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Best Regards,</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Ronak</span></font><o:p></o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Michail Bletsas
[mailto:mbletsas@laptop.org] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, January 19, 2008
10:23 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Dan Williams; Ronak Chokshi<br>
<b><span style='font-weight:bold'>Cc:</span></b> Ricardo Carrano; devel; David
Woodhouse; Giannis Galanis; networking@laptop.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: Testing the Wireless
driver changes</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
</span></font><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><br>
<tt><font face="Courier New">> </font></tt><br>
<tt><font face="Courier New">> Does the Boot2 code take care of figuring out
the correct address to</font></tt><br>
<tt><font face="Courier New">> write the thick firmware to, or does the
flash tool have to figure out</font></tt><br>
<tt><font face="Courier New">> the address to write it to? Normally
this address is embedded in the</font></tt><br>
<tt><font face="Courier New">> firmware flash file header, is there an
address the tool should check</font></tt><br>
<tt><font face="Courier New">> for to verify, or is that address completely
irrelevant because the</font></tt><br>
<tt><font face="Courier New">> boot2 code is smart enough to figure out
where to put it?</font></tt><br>
<tt><font face="Courier New">> </font></tt><br>
<tt><font face="Courier New">Dan,</font></tt></span></font> <br>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>You have to
ask Ronak that. Right now the flash writing logic lives in the firmware.</span></font></tt>
<br>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>M.</span></font></tt>
<o:p></o:p></p>
</div>
</body>
</html>