<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@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;
        text-align:justify;
        font-size:10.5pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        text-align:justify;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
        {page:WordSection1;}
--></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" style="text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Jesse, hey<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I work for ISG FSP/OTM boot loader team under Khadker Islam. I’ve recently run into an issue that blocks FSP/OTM from supporting
</span><span style="font-size:11.0pt;color:#1F497D">Tizen IVI 3.0 running Bay Trail B3 silicon on Bayley Bay board.  <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Log file</span><span style="font-size:11.0pt;color:#1F497D"> with the failure is a</span><span style="font-size:11.0pt;color:#1F497D">ttached. The fail</span><span style="font-size:11.0pt;color:#1F497D">ure</span><span style="font-size:11.0pt;color:#1F497D">
 is very consistent, happens every time with </span><span style="font-size:11.0pt;color:#1F497D">Bay Trail
</span><span style="font-size:11.0pt;color:#1F497D">B3 silicon</span><span style="font-size:11.0pt;color:#1F497D"> running FSP/OTM boot loader</span><span style="font-size:11.0pt;color:#1F497D">. The boot image was generated from Tizen IVI 3.0 EFI image</span><span style="font-size:11.0pt;color:#1F497D">
 posted at </span><span style="font-size:11.0pt;color:#1F497D"><a href="http://download.tizen.org/releases/milestone/tizen/ivi/latest/images/ivi-release-efi-i586/">http://download.tizen.org/releases/milestone/tizen/ivi/latest/images/ivi-release-efi-i586/</a>.
 The original image from the sever booted with EFI BIOS on the same board. </span>
<span style="font-size:11.0pt;color:#1F497D">Our FSP/OTM is legacy boot loader without EFI support.
</span><span style="font-size:11.0pt;color:#1F497D">Failure </span><span style="font-size:11.0pt;color:#1F497D">seems to be</span><span style="font-size:11.0pt;color:#1F497D"> with the graphics driver. The messages from the failure log file are shown on both
 serial console and local console via VGA. </span><span style="font-size:11.0pt;color:#1F497D">I need some help to understand</span><span style="font-size:11.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;color:#1F497D">if the driver under efi OS only works with efi BIOS</span><span style="font-size:11.0pt;color:#1F497D">?
</span><span style="font-size:11.0pt;color:#1F497D">Does it need some efi run time services from the BIOS? Or does it need certain POST set up from the BIOS? Also, is there a legacy version of Tizen IVI 3.0 ? if yes, where do I get this? Any help
</span><span style="font-size:11.0pt;color:#1F497D">will be greatly appreciated!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Stephanie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"></span><span style="font-size:11.0pt;color:#1F497D"><o:p></o:p></span></p>
</div>
</body>
</html>