U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 5/5] boot: fdt: fixup the memory dt nodes falcon boot
Date: Wed, 2 Aug 2017 15:32:18 -0400	[thread overview]
Message-ID: <20170802193218.GO16135@bill-the-cat> (raw)
In-Reply-To: <VI1PR04MB207895742FD0EBC697B2B8969AB00@VI1PR04MB2078.eurprd04.prod.outlook.com>

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 <ravibabu@ti.com>
> > ---
> >   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: <http://lists.denx.de/pipermail/u-boot/attachments/20170802/850ddcdc/attachment.sig>

  reply	other threads:[~2017-08-02 19:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 11:57 [U-Boot] [PATCH 0/5] QSPI: Falcon or single stage boot mode support Ravi Babu
2017-04-18 11:57 ` [U-Boot] [PATCH 1/5] spl: reorder the assignment of board info to global data Ravi Babu
2017-04-18 13:25   ` Lukasz Majewski
2017-04-18 13:42   ` Tom Rini
2017-05-12 17:18   ` [U-Boot] [U-Boot, " Tom Rini
2017-08-03  0:53   ` York Sun
2017-04-18 11:57 ` [U-Boot] [PATCH 2/5] arch: arm: omap: Declare size of ddr very early Ravi Babu
2017-04-18 13:33   ` Lukasz Majewski
2017-04-18 14:09     ` B, Ravi
2017-04-20  2:08     ` Lokesh Vutla
2017-05-12 17:18   ` [U-Boot] [U-Boot, " Tom Rini
2017-04-18 11:57 ` [U-Boot] [PATCH 3/5] qspi: dra7xx: enable qspi-boot for dra7x paltform Ravi Babu
2017-04-18 13:33   ` Lukasz Majewski
2017-05-12 17:18   ` [U-Boot] [U-Boot, " Tom Rini
2017-04-18 11:57 ` [U-Boot] [PATCH 4/5] spl: fdt: support for fdt fixup for falcon boot Ravi Babu
2017-04-18 13:35   ` Lukasz Majewski
2017-05-12 17:19   ` [U-Boot] [U-Boot, " Tom Rini
2017-04-18 11:57 ` [U-Boot] [PATCH 5/5] boot: fdt: fixup the memory dt nodes " Ravi Babu
2017-04-18 13:25   ` Lukasz Majewski
2017-04-18 14:05     ` B, Ravi
2017-04-20  1:54     ` Lokesh Vutla
2017-05-12 17:19   ` [U-Boot] [U-Boot, " Tom Rini
2017-08-02 19:10   ` York Sun
2017-08-02 19:32     ` Tom Rini [this message]
2017-08-26 11:50       ` Jagan Teki
2017-08-28 16:47         ` York Sun
2017-08-29 19:29           ` Jagan Teki
2017-08-29 20:21             ` York Sun

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=20170802193218.GO16135@bill-the-cat \
    --to=trini@konsulko.com \
    --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