From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] boards: ls2080: Disable fdt copying by default
Date: Tue, 01 Mar 2016 09:54:29 -0600 [thread overview]
Message-ID: <1456847669.5360.66.camel@buserror.net> (raw)
In-Reply-To: <AM2PR04MB1121C4C01AA6E976ADF34F7597BB0@AM2PR04MB1121.eurprd04.prod.outlook.com>
On Tue, 2016-03-01 at 03:55 +0000, Prabhakar Kushwaha wrote:
> > -----Original Message-----
> > From: Scott Wood [mailto:oss at buserror.net]
> > Sent: Tuesday, March 01, 2016 7:13 AM
> > To: york sun <york.sun@nxp.com>; U-Boot Mailing List <u-
> > boot at lists.denx.de>
> > Cc: Prabhakar Kushwaha <prabhakar@freescale.com>
> > Subject: Re: [U-Boot] [PATCH 2/2] boards: ls2080: Disable fdt copying by
> > default
> >
> > On Tue, 2016-03-01 at 00:08 +0000, york sun wrote:
> > > Sorry for top posting. I am on outlook web access.
> > >
> > > There may be some limitation on fdt relocation. Without setting
> > > fdt_high, u -boot relocates the device tree toward the end of useable
> > > memory. I haven't got a chance to debug why it doesn't work.
> > >
> > > This patch is to disable the relocation by default. A magic number
> > > 0xa0000000 doesn't make much sense here.
> >
> > I agree, if the number is arbitrary. But if Linux has a limitation, as it
> > does on
> > arm32, then it should be expressed here.
> >
>
> Just for understanding purpose.
> u-boot in case of arm32 can only access memory in 32 bit range.
> Will there be possibility of u-boot copying dtb in any memory not
> accessible to core.
No, but that is not the only limitation that needs to be honored regarding
device tree and initrd placement.
-Scott
next prev parent reply other threads:[~2016-03-01 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 23:58 [U-Boot] [PATCH 1/2] boards: ls2080: Fix default bootargs York Sun
2016-02-29 23:58 ` [U-Boot] [PATCH 2/2] boards: ls2080: Disable fdt copying by default York Sun
2016-03-01 0:00 ` Scott Wood
2016-03-01 0:08 ` york sun
2016-03-01 1:42 ` Scott Wood
2016-03-01 3:55 ` Prabhakar Kushwaha
2016-03-01 15:54 ` Scott Wood [this message]
2016-03-01 5:20 ` Bhupesh Sharma
2016-03-01 6:00 ` york sun
2016-03-01 6:03 ` Bhupesh Sharma
2016-03-01 16:01 ` Scott Wood
2016-03-01 16:48 ` york sun
2016-03-01 17:35 ` Scott Wood
2016-03-01 18:56 ` york sun
2016-03-22 15:37 ` [U-Boot] [PATCH 1/2] boards: ls2080: Fix default bootargs 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=1456847669.5360.66.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