From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Revert "ARM: Use armlinux_bootparams address for DTB"
Date: Thu, 08 Aug 2013 11:17:28 +0400 [thread overview]
Message-ID: <1375946248.679028165@f304.i.mail.ru> (raw)
In-Reply-To: <1375871688.726256777@f18.i.mail.ru>
> > On Wed, Aug 07, 2013 at 01:55:42PM +0400, Alexander Shiyan wrote:
> > > > This patch placed the flattened devicetree to armlinux_bootparams.
> > > > armlinux_bootparams normally is at SDRAM_START + 0x100. The kernels
> > > > initial page tables are normally at SDRAM_START + 0x4000, so the
> > > > flattened devicetree gets overwritten once it exceeds 0x3f00 bytes
> > > > which is quite common.
> > > >
> > > > Revert this patch for now once a better solution can be found
> > >
> > > In such a case, tree may be placed immediately after the kernel?
> > > It can also serve as an automatic option "ARM_APPENDED_DTB".
> >
> > Did you actually stumbled over this problem? Normally the dtb is
> > allocated using malloc. The malloc region normally shouldn't overlap
> > with the kernels text region unless you are really tight of memory.
> > Was this on a clps711x?
>
> I described it here:
> http://www.spinics.net/lists/u-boot-v2/msg15612.html
Seems this issue can be resolved by decrease MALLOC_SIZE.
...
0xc0380000 - 0xc077ffff (size 0x00400000) malloc space
...
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-08-08 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 9:45 [PATCH] Revert "ARM: Use armlinux_bootparams address for DTB" Sascha Hauer
2013-08-07 9:55 ` Alexander Shiyan
2013-08-07 10:11 ` Sascha Hauer
2013-08-07 10:34 ` Alexander Shiyan
2013-08-08 7:17 ` Alexander Shiyan [this message]
2013-08-09 6:58 ` Sascha Hauer
2013-08-09 7:02 ` Alexander Shiyan
2013-08-09 8:02 ` Sascha Hauer
2013-08-07 11:37 ` Maxime Ripard
2013-08-07 12:06 ` Alexander Shiyan
2013-08-07 12:40 ` Maxime Ripard
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=1375946248.679028165@f304.i.mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.