From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: vf610: move device tree after kernel image
Date: Wed, 14 Oct 2015 10:45:57 -0700 [thread overview]
Message-ID: <05bb4b4a170fcd5b2c9abe875591c0c1@agner.ch> (raw)
In-Reply-To: <20151014103642.1f2a62f5@lilith>
On 2015-10-14 01:36, Albert ARIBAUD wrote:
> Hello Stefan,
>
> On Tue, 13 Oct 2015 23:11:45 -0700, Stefan Agner <stefan@agner.ch>
> wrote:
>> Since the device tree relocation is disabled (fdt_high set to
>> 0xffffffff), U-Boot keeps the device tree at its load address
>> 0x81000000. The kernel uncompresses itself to 0x80008000 by
>> default, hence this limits the maximum (uncompressed) kernel
>> size to somewhat below 16MiB, otherwise the device tree gets
>> overwritten by the kernel data...
>>
>> Move the device tree load address to 0x84000000 to avoid that
>> the device tree being overwritten by the kernel.
>
> OOC, why is device tree relocation disabled? I'm asking because by
> manually placing the device tree (or anything else) high in DDR, one
> runs the risk of overwriting some of U-Boot's data.
I guess this has been done for Cortex-M4 firmwares running from DDR. As
Tom pointed out, this can be archived in a nicer way using bootm_size.
--
Stefan
next prev parent reply other threads:[~2015-10-14 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 6:11 [U-Boot] [PATCH] arm: vf610: move device tree after kernel image Stefan Agner
2015-10-14 8:36 ` Albert ARIBAUD
2015-10-14 9:08 ` Albert ARIBAUD
2015-10-14 17:45 ` Stefan Agner [this message]
2015-10-14 18:41 ` Albert ARIBAUD
2015-10-14 12:39 ` Tom Rini
2015-10-14 16:05 ` Stefan Agner
2015-10-14 16:36 ` Tom Rini
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=05bb4b4a170fcd5b2c9abe875591c0c1@agner.ch \
--to=stefan@agner.ch \
--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