From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] armv8: layerscape: Add support of u-boot device tree fix-up
Date: Tue, 08 Mar 2016 13:31:55 -0600 [thread overview]
Message-ID: <1457465515.5360.110.camel@buserror.net> (raw)
In-Reply-To: <AM2PR04MB1121354D422E67D8A8B3833F97A40@AM2PR04MB1121.eurprd04.prod.outlook.com>
On Tue, 2016-02-23 at 04:09 +0000, Prabhakar Kushwaha wrote:
> > -----Original Message-----
> > From: Scott Wood [mailto:oss at buserror.net]
> > Sent: Tuesday, February 23, 2016 6:52 AM
> > To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>; u-
> > boot at lists.denx.de
> > Cc: york sun <york.sun@nxp.com>; Priyanka Jain <priyanka.jain@nxp.com>
> > Subject: Re: [RFC] armv8: layerscape: Add support of u-boot device tree
> > fix-
> > up
> >
> > Where do you check that the device tree fits in OCRAM? What about when
> > SPL is occupying OCRAM? Does the device tree get used with SPL (I don't
> > think we were using FDT control at all the last time I worked with SPL on
> > these chips)?
> >
>
> I checked ls2085ardb dtb size in Linux. It is ~30K. So from 0xfff0 to 20000
> there is enough space.
>
> For SPL. Assumption is SPL never use dts. It will only be used by u-boot.
> Once control is transferred to u-boot, things work as it is like NOR boot.
I don't think that's a good assumption, given that I just saw a patch posted
regarding SPL_OF_CONTROL.
-Scott
next prev parent reply other threads:[~2016-03-08 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 10:35 [U-Boot] [RFC] armv8: layerscape: Add support of u-boot device tree fix-up Prabhakar Kushwaha
2016-02-23 1:21 ` Scott Wood
2016-02-23 4:09 ` Prabhakar Kushwaha
2016-02-23 6:44 ` Scott Wood
2016-02-24 2:50 ` Prabhakar Kushwaha
2016-02-25 4:44 ` Scott Wood
2016-03-08 19:31 ` Scott Wood [this message]
2016-03-09 2:57 ` Prabhakar Kushwaha
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=1457465515.5360.110.camel@buserror.net \
--to=oss@buserror.net \
--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