On 2018-08-15, Bin Meng wrote:
On Thu, Aug 16, 2018 at 4:02 AM, Vagrant Cascadian vagrant@debian.org wrote:
This reverts commit 2a1f4f1758b55589395f90f583aacb07ae6fcafe.
Eh, this is a revert to a "revert" commit?
Sure. I mostly was submitting it as a bug report targeting a specific fix...
Maybe there's a better way to fix this, but reverting this got odroid-xu4 booting agian:
Have we found out the real root cause? There must be a reason in the original fix, then followed by another reasonable "revert", and now the "revert" will be reverted again?
This has apparently been discussed in other threads:
https://lists.denx.de/pipermail/u-boot/2018-August/337979.html https://lists.denx.de/pipermail/u-boot/2018-August/338090.html
It seems the working best option so far is to switch CONFIG_NR_DRAM_BANKS to to Kconfig:
https://lists.denx.de/pipermail/u-boot/2018-August/338215.html https://lists.denx.de/pipermail/u-boot/2018-August/338227.html
live well, vagrant