commit 86cf1c82850f7c226f23684e19616e526ffaf10f
author Tom Rini <trini@konsulko.com> Thu Aug 16 08:16:24 2018 -0400
committer Tom Rini <trini@konsulko.com> Thu Aug 16 16:45:02 2018 -0400
tree 215dc29cd1f62c44019733ef85367a8d1f034287
parent 999a772d9f24bf9b8d0726e1359c9d8c3bdad72e

configs: Migrate CONFIG_NR_DRAM_BANKS

We have the following cases:
- CONFIG_NR_DRAM_BANKS was defined, migrate normally
- CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
  CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
- CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
  2), set this to 8.

Signed-off-by: Tom Rini <trini@konsulko.com>

configs/usbarmory_defconfig

diff --git a/configs/usbarmory_defconfig b/configs/usbarmory_defconfig
index 2e5bdad..4bac8f1 100644
--- a/configs/usbarmory_defconfig
+++ b/configs/usbarmory_defconfig
@@ -4,6 +4,7 @@
 CONFIG_TARGET_USBARMORY=y
 # CONFIG_CMD_BMODE is not set
 CONFIG_DISTRO_DEFAULTS=y
+CONFIG_NR_DRAM_BANKS=1
 # CONFIG_USE_BOOTCOMMAND is not set
 CONFIG_CMD_MEMTEST=y
 CONFIG_CMD_FUSE=y