From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 2 Aug 2017 15:32:18 -0400 Subject: [U-Boot] [U-Boot, 5/5] boot: fdt: fixup the memory dt nodes falcon boot In-Reply-To: References: <1492516647-26840-6-git-send-email-ravibabu@ti.com> Message-ID: <20170802193218.GO16135@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 Wed, Aug 02, 2017 at 07:10:51PM +0000, York Sun wrote: > On 04/18/2017 04:57 AM, B, Ravi wrote: > > In single stage bootmode or falcon boot mode, > > the SPL shall update the memory dt nodes > > spl_fixup_fdt() based on DDR configuration for > > specific platform. > > > > Signed-off-by: Ravi Babu > > --- > > common/spl/spl.c | 40 ++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 40 insertions(+) > > Clearly I am late for this thread. I only notice this change when I try > to merge my FIT improvement for falcon boot. > > Why do we need to fixup the device tree for falcon boot at all? The > device tree is static, saved as argument when exporting it, isn't it? As > far as the normal boot fixes up the device tree, the exported device > tree is correct. So, the further argument here is that if you have to edit the dts to include a valid amount of memory so that the dtb the kernel spits out is useful in falcon mode, it's not at all useful in development. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: