On 03/31/2011 07:19 AM, Wolfgang Denk wrote:
Dear Paul Eggleton,
In
message<41ae31ba057b63d3c518e2edf217109c59b64603.1301578942.git.paul.eggle...@linux.intel.com>
you wrote:
From: Paul Eggleton<[email protected]>
Upgrading u-boot is apparently not necessary with current board revisions,
and these instructions may not work properly anyway (our toolchain seems not
to be able to compile u-boot in the way described), and given that they are
potentially risky they should be removed.
The instructions you delete appear to be pretty generic ones, and I
see no reason why they would not work.
When I followed them I ended up with a dead mpc3815e-rdb. I suspect my
u-boot image was bad in some way, but my concern was that others would
end up in the same situation following the instructions. Since the
existing u-boot version was able to boot the linux-yocto kernel recipe,
there appears to be no need to reflash u-boot.
If the Poky too chain has issues with this, then there is a problem
with that tool chain, and you should enter a bug report.
What exactly would that problem be?
Absolutely, this wasn't intended as a final "solution". The issue
appears to be related to the 4.5.1 version of gcc failing in various
ways to build either u-boot master or v2010.09, or v2010.12. I will
report this to the u-boot mailing list just as soon as I can get back to it.
--
Darren
In any case, just papering over the problems seems not a good
startegy to me.
Best regards,
Wolfgang Denk
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
