From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 14 Oct 2015 20:41:57 +0200 Subject: [U-Boot] [PATCH] arm: vf610: move device tree after kernel image In-Reply-To: <05bb4b4a170fcd5b2c9abe875591c0c1@agner.ch> References: <1444803105-3312-1-git-send-email-stefan@agner.ch> <20151014103642.1f2a62f5@lilith> <05bb4b4a170fcd5b2c9abe875591c0c1@agner.ch> Message-ID: <20151014204157.6b6198ec@lilith> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Stefan, On Wed, 14 Oct 2015 10:45:57 -0700, Stefan Agner wrote: > On 2015-10-14 01:36, Albert ARIBAUD wrote: > > Hello Stefan, > > > > On Tue, 13 Oct 2015 23:11:45 -0700, Stefan Agner > > 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. Thanks -- I've just seen Tom's answer. I guess I'll update pcm052 too... > Stefan Amicalement, -- Albert.