<div dir="ltr"><div><div>Hi:<br><br></div>That's the case. The system should talk with a device driver. This is in fact a kernel module.<br><br></div>Thanks.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2014-09-12 12:10 GMT-05:00 "Thomas B. Rücker" <span dir="ltr"><<a href="mailto:thomas@ruecker.fi" target="_blank">thomas@ruecker.fi</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 09/12/2014 04:26 PM, Ferchu R wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Darrent:<br>
<br>
Unfortunately my development work implies to work with a third
party library that is only available (at least for now) in 32
bit. So there is not choice for me. By the way, I tried to boot
the old Minnow's SD with the new MAX. It hangs when it asks for
Angstrom login.<br>
</div>
</blockquote>
<br></span>
You can run either a multi-arch distro or a 32-bit userland with a
64bit kernel.<br>
Unless you need to somehow plug some binary only 32bit kernel module
in, there should be no reason for a 32bit kernel, from what I can
tell.<br>
<br>
Cheers<span class="HOEnZb"><font color="#888888"><br>
<br>
Thomas</font></span><div><div class="h5"><br>
<br>
<blockquote type="cite">
<div dir="ltr">Thanks.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-09-12 10:26 GMT-05:00 Darren Hart
<span dir="ltr"><<a href="mailto:dvhart@linux.intel.com" target="_blank">dvhart@linux.intel.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>This was one of the more difficult issues with
MinnowBoard 1. It was 32b EFI, and there were no
common distros that supported it out of the box. Is
there a reason you want to use 32b? I confess I
can't think of reason to sacrifice the extra
registers and instructions when the system has more
than 1GB of memory and gobs of permanent storage.</div>
<span>
<div><br>
</div>
<div>
<div>-- </div>
<div>Darren Hart<span style="white-space:pre-wrap">
</span>Open Source Technology Center</div>
<div><a href="mailto:darren.hart@intel.com" target="_blank">darren.hart@intel.com</a><span style="white-space:pre-wrap"> </span>
Intel Corporation</div>
</div>
</span></div>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"><span style="font-weight:bold">From: </span> Ferchu R
<<a href="mailto:chamac2@gmail.com" target="_blank">chamac2@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>
MinnowBoard Development and Community Discussion <<a href="mailto:elinux-minnowboard@lists.elinux.org" target="_blank">elinux-minnowboard@lists.elinux.org</a>><br>
<span style="font-weight:bold">Date: </span> Friday,
September 12, 2014 at 8:16<br>
<span style="font-weight:bold">To: </span>
MinnowBoard Development and Community Discussion <<a href="mailto:elinux-minnowboard@lists.elinux.org" target="_blank">elinux-minnowboard@lists.elinux.org</a>>
<div>
<div><br>
<span style="font-weight:bold">Subject: </span>
Re: [MinnowBoard] 64-bit vs 32-bit UEFI - What you
need to know!<br>
</div>
</div>
</div>
<div>
<div>
<div><br>
</div>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div dir="ltr">I was wondering if somebody knows
what distro has a 32 bit EFI compatible image.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-09-11 20:54
GMT-05:00 Hawley, John <span dir="ltr"><<a href="mailto:john.hawley@intel.com" target="_blank">john.hawley@intel.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I
agree, I’ve seen it a couple of
times. What happens is:</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>1)<span>
</span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Flash
happens</span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>2)<span>
</span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Flash
program goes to reboot the board
(gives a couple second timeout, then
screen goes blank)</span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>3)<span>
</span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Sometimes
it looks like it can’t call the
shutdown cleanly then both D1 and D1
end up staying on</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><a name="1486ad8323c844fd_1486a7958716cb87_148679155f420fe5__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">When
I’m back in the office on Monday
(I’m heading to the Albuquerque
Maker Faire right now to show off
a bunch of MinnowBoard MAX stuff),
I’ll try the conversion and see
what happens. If I can replicate
the issue I’ll bug the firmware
team about it and see if they can
root cause, and fix that.</span></a></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Glad
you are back up and running though,
I know exactly how iffy upgrading
firmware can be, and it’s always
frustrating when you have to reach
for the external firmware flasher.
I know CircuitCo has a small board
to help deal with external flashing
in development, hopefully that will
be out soon to help alleviate
people’s fears of playing with the
firmware!</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">-
John</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> <a href="mailto:elinux-minnowboard-bounces@lists.elinux.org" target="_blank">elinux-minnowboard-bounces@lists.elinux.org</a>
[mailto:<a href="mailto:elinux-minnowboard-bounces@lists.elinux.org" target="_blank">elinux-minnowboard-bounces@lists.elinux.org</a>]
<b>On Behalf Of </b>Ferchu R<br>
<b>Sent:</b> Thursday,
September 11, 2014 6:45 PM</span></p>
<div>
<div><br>
<b>To:</b> MinnowBoard
Development and Community
Discussion<br>
<b>Subject:</b> Re:
[MinnowBoard] 64-bit vs 32-bit
UEFI - What you need to know!</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">Hi John</p>
</div>
<div>
<p class="MsoNormal"><br>
Thanks, It worked. I think
the firware update should
end gracefully. A black
screen when flashing
firmware makes anyone
nervous.
</p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">2014-09-11
20:33 GMT-05:00 Hawley, John
<<a href="mailto:john.hawley@intel.com" target="_blank">john.hawley@intel.com</a>>:</p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Well
getting into
firmware menu is a
good sign
</span><span style="font-size:11.0pt;font-family:Wingdings;color:#1f497d">J</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><a href="http://elinux.org/Minnowboard:MaxBios#Change_Boot_Order" target="_blank"><span style="font-size:11pt;font-family:Calibri,sans-serif">http://elinux.org/Minnowboard:MaxBios#Change_Boot_Order</span></a></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">You
should be able to
see “Boot
Maintenance
Manager”, with the 4<sup>th</sup>
option being “Change
Boot Order”, you
should be able to
“<EFI Internal
Shell>” (hit
enter, + it to the
top, hit enter) and
commit the changes
back to get back to
the shell, and get
your install going.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">If
that doesn’t work,
let me know here and
we’ll see what is
going on.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">-
John</span></p>
<p class="MsoNormal"><a name="1486ad8323c844fd_1486a7958716cb87_148679155f420fe5_148677eaf5503591__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></a></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"></span><a href="mailto:elinux-minnowboard-bounces@lists.elinux.org" target="_blank"><span style="font-size:11pt;font-family:Calibri,sans-serif">elinux-minnowboard-bounces@lists.elinux.org</span></a><span style="font-size:11pt;font-family:Calibri,sans-serif"> [mailto:</span><a href="mailto:elinux-minnowboard-bounces@lists.elinux.org" target="_blank"><span style="font-size:11pt;font-family:Calibri,sans-serif">elinux-minnowboard-bounces@lists.elinux.org</span></a><span style="font-size:11pt;font-family:Calibri,sans-serif">]
<b>On Behalf Of
</b>Ferchu R<br>
<b>Sent:</b>
Thursday,
September 11,
2014 6:26 PM<br>
<b>To:</b>
MinnowBoard
Development and
Community
Discussion<br>
<b>Subject:</b>
Re:
[MinnowBoard]
64-bit vs 32-bit
UEFI - What you
need to know!</span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">So
I FOLLOWED the
procedure to
pass from 64 to
32. I think the
system filled 2
lines of dots,
when the screen
goes black. I
waited about a
half hour but
there was no
sign of new
action, so I
tried to reboot.
Now the board
has not EUFI
Shell. But it
does have setup,
where the third
line says it is
MNW2CRB1.86C.0071.R30.1408131324.
I was wondering
what coused
this, and how I
get the board on
work again?.<br>
<br>
Thanks</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">2014-09-10
13:04 GMT-05:00
Hawley, John
<<a href="mailto:john.hawley@intel.com" target="_blank">john.hawley@intel.com</a>>:</p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal">I
think there's
some value in
being explicit
or otherwise
we'll actually<br>
cause
confusion.
I.E. when you
download the
firmware and
people see<br>
32-bit vs.
64-bit
firmware in
the same place
will they
always flash
the<br>
right one?
Part of the
problem is
there is no UI
to these
firmware<br>
flashers, they
are command
line
utilities.<br>
<span style="color:#888888"><br>
- John</span></p>
<div>
<div>
<p class="MsoNormal"><br>
On Wed,
2014-09-10 at
13:18 -0400,
Adam Goode
wrote:<br>
> I see the
zip files
already
contain both
EFI binaries.
Assuming the<br>
> firmware
updaters
present some
firmware
selection UI,
the<br>
>
simplification
I can see here
is
consolidating
by putting
both<br>
> firmware
files into the
same zip file.
You could go
further and<br>
> combine
the release
and debug
versions as
well, but that
might be<br>
>
unnecessary.<br>
><br>
><br>
> Thanks,<br>
><br>
> Adam<br>
><br>
><br>
> On Wed,
Sep 10, 2014
at 11:45 AM,
Darren Hart
<<a href="mailto:dvhart@linux.intel.com" target="_blank">dvhart@linux.intel.com</a>>
wrote:<br>
> > On
9/10/14, 8:22,
"Adam Goode"
<<a href="mailto:adam@spicenitz.org" target="_blank">adam@spicenitz.org</a>>
wrote:<br>
> ><br>
>
>>Does
this mean that
both files can
just be put
into place? If
so,<br>
>
>>could
you update the
distribution
to include
both and not
worry about<br>
>
>>what
the current
firmware is?
It would
simplify the
process and<br>
>
>>documentation.<br>
> ><br>
> > That
strikes me as
a pretty good
suggestion.<br>
> ><br>
> > --<br>
> >
Darren<br>
> ><br>
> >><br>
> >><br>
>
>>Adam<br>
> >><br>
> >><br>
>
>>On
Wed, Sep 10,
2014 at 11:08
AM, Darren
Hart <<a href="mailto:dvhart@linux.intel.com" target="_blank">dvhart@linux.intel.com</a>><br>
>
>>wrote:<br>
>
>>>
On 9/10/14,
1:35, "Roel
Jordans" <<a href="mailto:r.jordans@tue.nl" target="_blank">r.jordans@tue.nl</a>>
wrote:<br>
>
>>><br>
>
>>>><br>
>
>>>>><br>
>
>>>>><a href="http://www.elinux.org/Minnowboard:MaxBios#Switching_from_64-bit_to_32-b" target="_blank">http://www.elinux.org/Minnowboard:MaxBios#Switching_from_64-bit_to_32-b</a><br>
>
>>>>>it<br>
>
>>>>><br>
>
>>>>>
Basically you
have to
re-flash the
firmware with
a 32-bit
firmware.<br>
>
>>>>>
There's a line
in the
instructions
that may
confuse some
folks,<br>
>
>>>>>
specifically
using a
FirmwareUpdateX64.efi
to flash a
32-bit
firmware.<br>
>
>>>>>
This is
because when
you go to
change the
firmware you
are running a<br>
>
>>>>>
64-bit
firmware, and
therefore need
a 64-bit EFI
program to
actually<br>
>
>>>>>do<br>
>
>>>>>
the flashing.<br>
>
>>>>><br>
>
>>>>>
If you want to
switch back,
you'll do the
opposite, use<br>
>
>>>>>
FirmwareUpdateIA32.efi
to flash a
64-bit
firmware.<br>
>
>>>>><br>
>
>>>><br>
>
>>>>Maybe
it's possible
to rename
those updates
(or add some
renamed<br>
>
>>>>updates)
to something
like
FirmwareUpdateIA32to64
or something?
That<br>
>
>>>>would
probably
remove most of
the cause for
confusion
here.<br>
>
>>><br>
>
>>>
That isn't
accurate
unfortunately.
The update
tool doesn't
care which<br>
>
>>>bit<br>
>
>>>
length you are
flashing to,
you use the
same tool to
flash to 32b
or to<br>
>
>>>
64b, what
matters is
what firmware
you are
currently
running, and
that<br>
>
>>>is<br>
>
>>>
what the tool
name reflects.<br>
>
>>><br>
>
>>>
--<br>
>
>>>
Darren Hart
Open
Source
Technology<br>
>
>>>Center<br>
>
>>> <a href="mailto:darren.hart@intel.com" target="_blank">darren.hart@intel.com</a>
Intel<br>
>
>>>Corporation<br>
>
>>><br>
>
>>><br>
>
>>><br>
>
>>>
_______________________________________________<br>
>
>>>
elinux-MinnowBoard
mailing list<br>
>
>>> <a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
>
>>> <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">
http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
>
>>_______________________________________________<br>
>
>>elinux-MinnowBoard
mailing list<br>
> >><a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
> >><a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> >
Darren Hart
Open
Source
Technology
Center<br>
> > <a href="mailto:darren.hart@intel.com" target="_blank">darren.hart@intel.com</a>
Intel
Corporation<br>
> ><br>
> ><br>
> ><br>
> >
_______________________________________________<br>
> >
elinux-MinnowBoard
mailing list<br>
> > <a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
> > <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">
http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
>
_______________________________________________<br>
>
elinux-MinnowBoard
mailing list<br>
> <a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
> <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">
http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
<br>
_______________________________________________<br>
elinux-MinnowBoard
mailing list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a></p>
</div>
</div>
</blockquote>
</div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
elinux-MinnowBoard mailing
list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a></p>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
elinux-MinnowBoard mailing list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
<br>
</blockquote>
</div>
<br>
</div>
_______________________________________________
elinux-MinnowBoard mailing list
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a>
</blockquote>
</div>
</div>
</span></div>
<br>
_______________________________________________<br>
elinux-MinnowBoard mailing list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
elinux-MinnowBoard mailing list
<a href="mailto:elinux-MinnowBoard@lists.elinux.org" target="_blank">elinux-MinnowBoard@lists.elinux.org</a>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
elinux-MinnowBoard mailing list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
<br></blockquote></div><br></div>