From: Tom Rini Date: Fri, 17 May 2013 12:52:02 -0400 Subject: [U-Boot] [PATCH] fdt_support: Use CONFIG_NR_DRAM_BANKS if defined In-Reply-To: References: <1367353321-21204-1-git-send-email-dianders@chromium.org> <51802B0E.1070403@ti.com> <51803428.1070507@ti.com> <20130517164039.GT32163@bill-the-cat> Message-ID: <20130517165202.GU32163@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, May 17, 2013 at 09:48:13AM -0700, Doug Anderson wrote: > Tom, > > On Fri, May 17, 2013 at 9:40 AM, Tom Rini wrote: > > I think my email must have been lost in the shuffle, see > > http://patchwork.ozlabs.org/patch/240687/ > > > > So yes, I've got another fix in mind that should solve this and some > > other problems. > > Saw your reply but don't completely understand it. I think we'd still > like U-Boot to populate the memory property if possible and it sounds > like your patch would prevent that. One reason is that we'd like to > be able to handle different memory configurations (one of which is > 3.5G) with a single binary and have U-Boot just tell the kernel how > much space there is. So, I've been assuming that these are different platforms that you already append different device trees on, so that you use the same binary still and just different DTs. Is that not the case here? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: