Hi Matthijs,
Am 08.10.2016 um 01:46 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
On 20 September 2016 at 22:29, H. Nikolaus Schaller hns@goldelico.com wrote:
"U-Boot SPL 2015.10-00064-g3a56b36-dirty (Apr 07 2016 - 22:35:27)
Why is such an old u-boot being used?
"Never touch a running (boot) system..."
Especially if you have to urgently fix known problems elsewhere (hardware, software).
Because it is unlikely (until explicitly proven) that the boot loader is the source of the problem.
There have been pretty important-looking patches this year such as this one:
Well, the EVM did work for a long time w/o this patch, so it might improve things but does not seem to be essential to me.
What I also can't see is if this patch fixes something introduced after 2015.10.
Following mainline U-Boot it needs a little time to correctly rebase and update (there are several CONFIG modifications to track and functions move between board file and core and change names).
But anyways I have started to rebase on 2016.09 yesterday because I need a new U-Boot for the GTA04A5 device as well. There we still use an 2011.03 U-Boot which has never made a problem until now because it does not support the OneNAND chip.
It my experience using the latest things sometimes needs more efforts (tracking what has been changed, rebasing, testing) than plainly using an old but mature system.
So we will have a latest U-Boot in some days for testing.
BR, Nikolaus