From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "Revert "fdt_support: Use CONFIG_NR_DRAM_BANKS if defined""
Date: Thu, 16 Aug 2018 07:54:11 -0700 [thread overview]
Message-ID: <87r2iy746k.fsf@aikidev.net> (raw)
In-Reply-To: <CAEUhbmU66CJX3jvNfHyB787adB7XXU8_2_ETXhBj4fa=+VyYcg@mail.gmail.com>
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180816/cf8903da/attachment.sig>
prev parent reply other threads:[~2018-08-16 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 20:02 [U-Boot] [PATCH] Revert "Revert "fdt_support: Use CONFIG_NR_DRAM_BANKS if defined"" Vagrant Cascadian
2018-08-16 3:25 ` Bin Meng
2018-08-16 14:54 ` Vagrant Cascadian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2iy746k.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox