From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 10 Dec 2018 07:23:36 -0500 Subject: [U-Boot] ARM: rockchip: rv1108: Fix booting with initramfs In-Reply-To: References: <20181204134926.28794-1-otavio@ossystems.com.br> <20181210002814.GF8702@bill-the-cat> Message-ID: <20181210122336.GH8702@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Dec 10, 2018 at 10:01:06AM -0200, Otavio Salvador wrote: > On Sun, Dec 9, 2018 at 10:28 PM Tom Rini wrote: > > On Mon, Dec 10, 2018 at 01:01:52AM +0100, Philipp Tomsich wrote: > > > > We move the ramdisk_addr_r to 0x68000000 and disable the initrd and > > > > fdt relocation, so the initramfs works out of box. > > > > > > > > Signed-off-by: Otavio Salvador > > > > Reviewed-by: Philipp Tomsich > > > > --- > > > > > > > > include/configs/rv1108_common.h | 4 +++- > > > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > > > > > > > Applied to u-boot-rockchip, thanks! > > > > Ugh, sorry for not spotting this sooner. Please don't disable > > fdt/initrd relocation and instead use bootm_size. > > I never used it, any reference to look at? Specifically? No. There should be a lot of general hits on $search-engine over it however as not disabling and instead using bootm_size is how to fix "Kernel suddenly stops booting... oh we're overwriting fdt/initrd". This isn't to say that disabling fdt/initrd relocation isn't a useful production optimization, it is. But it's not a good general best practice. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: