<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">David,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://github.com/tianocore/tianocore.github.io/wiki/EDK%20II%20White%20papers">EDK II white papers</a> has several new UEFI features and most of them requires edk2 trunk or edk2-staging branch. Minnowboard
is labeled as the open hardware platform but it is stuck in stable/aged UDK2015.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Case in point, <a href="https://twitter.com/Intel_UEFI">
New firmware for Intel® Server Board S1200RP UEFI Development Kit (SDV.RP.B6) includes HTTP/HTTPS Boot & TPM 2.0.</a> is a nice new release but it is closed source firmware.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">From another perspective, if Minnowboard platform is still committed to adopt new UEFI feature, then why not actively making it compatible with edk2 trunk so that when new feature demands, it would be quicker
to create a new UDK-next branch with a functional Minnowboard firmware. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In another word, this no-boot-device problem has to be addressed eventually, why not fix it as soon as possible instead of waiting for UDK-next stable branch? I would like to see Minnowboard able to run edk2
trunk for leading edge open source firmware development besides the stable UDK2015 for production deployment.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Moso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> elinux-MinnowBoard [mailto:elinux-minnowboard-bounces@lists.elinux.org]
<b>On Behalf Of </b>Wei, David<br>
<b>Sent:</b> Wednesday, July 13, 2016 2:02 AM<br>
<b>To:</b> MinnowBoard Development and Community Discussion <elinux-minnowboard@lists.elinux.org><br>
<b>Subject:</b> Re: [MinnowBoard] edk2 trunk<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Moso,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Basically, MinnowBoard platform development only bases on a stable version of UDK2015 core, not bases on the evolving EDKII trunk. If the new MinnowBoard Dual-E really needs latest UEFI feature support, maybe
could consider upgrading the UDK2015 core packages of repo edk2-platforms/minnowboard-max-udk2015 to a newer stable version.</span> <span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">David Wei
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Intel SSG BIOS Team<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b>From:</b> elinux-MinnowBoard [<a href="mailto:elinux-minnowboard-bounces@lists.elinux.org">mailto:elinux-minnowboard-bounces@lists.elinux.org</a>]
<b>On Behalf Of </b>Moso Lee<br>
<b>Sent:</b> Wednesday, July 13, 2016 12:30 PM<br>
<b>To:</b> MinnowBoard Development and Community Discussion <<a href="mailto:elinux-minnowboard@lists.elinux.org">elinux-minnowboard@lists.elinux.org</a>><br>
<b>Subject:</b> Re: [MinnowBoard] edk2 trunk<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">David,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Are you saying that the newly announced MinnowBoard Dual-E from ADI Engineering hitting shelves in Q3 will not be using edk2 trunk with UEFI 2.6 either?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If so, this is the end of MinnowBoard platform. What do you recommend for another open hardware platform capable of UEFI 2.6 development?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Moso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> elinux-MinnowBoard [<a href="mailto:elinux-minnowboard-bounces@lists.elinux.org">mailto:elinux-minnowboard-bounces@lists.elinux.org</a>]
<b>On Behalf Of </b>Wei, David<br>
<b>Sent:</b> Tuesday, July 12, 2016 11:00 PM<br>
<b>To:</b> MinnowBoard Development and Community Discussion <<a href="mailto:elinux-minnowboard@lists.elinux.org">elinux-minnowboard@lists.elinux.org</a>><br>
<b>Subject:</b> [MinnowBoard] edk2 trunk<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have no plan to continue merging edk2-platforms/minnowboard-max-udk2015 to git repo “edk2 trunk”.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">MinnowBoard platform development will only be on edk2-platforms repo. The stable MinnowBoard release (<a href="https://firmware.intel.com/projects/minnowboard-max">https://firmware.intel.com/projects/minnowboard-max</a> ) also only bases
on this repo. <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">David Wei
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Intel SSG BIOS Team<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> elinux-MinnowBoard [<a href="mailto:elinux-minnowboard-bounces@lists.elinux.org">mailto:elinux-minnowboard-bounces@lists.elinux.org</a>]
<b>On Behalf Of </b>Moso Lee<br>
<b>Sent:</b> Wednesday, July 13, 2016 10:08 AM<br>
<b>To:</b> <a href="mailto:elinux-minnowboard@lists.elinux.org">elinux-minnowboard@lists.elinux.org</a><br>
<b>Subject:</b> [MinnowBoard] edk2 trunk<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is Vlv2TbltDevicePkg supported in the latest edk2/trunk?<o:p></o:p></p>
<p class="MsoNormal">I would like to use Minnowboard Max to experiment some of the newer UEFI features that is not in edk2-platforms/minnowboard-max-udk2015 branch.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I built Vlv2TbltDevicePkg from edk2/trunk few months back with 0.84 Binary Object Modules (per BiosIdD.env) and it worked. But the latest trunk no longer work. The machine can boot up but there is no boot device at all.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Comparing between trunk and edk2-platforms, there seems to be parallel independent new development between the two branches.<o:p></o:p></p>
<p class="MsoNormal"><a href="https://github.com/tianocore/edk2/commits/master/Vlv2TbltDevicePkg">https://github.com/tianocore/edk2/commits/master/Vlv2TbltDevicePkg</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://github.com/tianocore/edk2-platforms/commits/minnowboard-max-udk2015/Vlv2TbltDevicePkg">https://github.com/tianocore/edk2-platforms/commits/minnowboard-max-udk2015/Vlv2TbltDevicePkg</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To piggyback to the question from the top, when will edk2-platforms/minnowboard-max-udk2015 be merged back to trunk?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Moso<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>