<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=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, x86_64 needs a lot of clean up to do. It’s a lot big and including too many unused modules in the kernel. Thanks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ning<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> openwrt-devel [mailto:openwrt-devel-bounces@lists.openwrt.org] <b>On Behalf Of </b>William Haynes<br><b>Sent:</b> Thursday, October 09, 2014 12:17 PM<br><b>To:</b> Dirk Neukirchen<br><b>Cc:</b> openwrt-devel@lists.openwrt.org<br><b>Subject:</b> Re: [OpenWrt-Devel] x86_64 option is now missing - help!<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>That makes sense. So, if I build from the trunk, will Barrier Breaker packages still be able to be pulled or will the versions diverge to the point I have to maintain a separate download location for packages until time for an upgrade?<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal>Sincerely,<br><br>William Haynes<br>Sabai Technology<br>--------------------------------------------------------------<o:p></o:p></p><div><p class=MsoNormal>Technology for the People<o:p></o:p></p></div><div><p class=MsoNormal>--------------------------------------------------------------<o:p></o:p></p><div><p class=MsoNormal>p - 864-962-4072<o:p></o:p></p></div><div><p class=MsoNormal>f - 919-590-1929<br>e - <a href="mailto:william@sabaitechnology.com" target="_blank">william@sabaitechnology.com</a> <o:p></o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Oct 9, 2014 at 11:51 AM, Dirk Neukirchen <<a href="mailto:dirkneukirchen@web.de" target="_blank">dirkneukirchen@web.de</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>On 09.10.2014 15:00, William Haynes wrote:<br>> I've been developing a x86_64 bit system during the release candidates.<br>> Now that the final is released, x86_64 is not an option anymore. Is there<br>> a possibility of getting this added back or is it something I can do? I'm<br>> developing for a baytrail (Intel) multicore processor and would like it to<br>> run in 64 bit.<br><br>x86_64 is still available in trunk<br><br>Maybe it was not considered stable enough to be included in BB final?<br>Some commits are only build tested and maybe there is not that much feedback<br>on Hyper-V / ESXi / KVM / Virtualbox / qemu setups / real hw (apu1c , minnowboard ?).<br><br><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>