From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/85xx: Increase fdt address
Date: Tue, 19 Jul 2016 20:20:43 -0400 [thread overview]
Message-ID: <20160720002043.GQ21225@windriver.com> (raw)
In-Reply-To: <1468968726-18056-1-git-send-email-oss@buserror.net>
[[PATCH] powerpc/85xx: Increase fdt address] On 19/07/2016 (Tue 17:52) Scott Wood wrote:
> Loading the fdt at 0xc00000 fails if the uncompressed kernel image is
> greater than 12 MiB, which is quite common with modern kernels and
> multiplatform defconfigs. Move fdtaddr to 0x1e00000 which is just under
> the ramdiskaddr on most targets.
>
> Signed-off-by: Scott Wood <oss@buserror.net>
> Cc: Peter Tyser <ptyser@xes-inc.com>
> Cc: Dirk Eibach <eibach@gdsys.de>
> Cc: Andy Fleming <afleming@gmail.com>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
[...]
diff --git a/include/configs/sbc8548.h b/include/configs/sbc8548.h
> index bbd1a63..74f219f 100644
> --- a/include/configs/sbc8548.h
> +++ b/include/configs/sbc8548.h
> @@ -596,7 +596,7 @@
> "consoledev=ttyS0\0" \
> "ramdiskaddr=2000000\0" \
> "ramdiskfile=uRamdisk\0" \
> -"fdtaddr=c00000\0" \
> +"fdtaddr=1e00000\0" \
Pretty sure it was common to have to bump the "c" to an "e" now and
again, so "1e" sounds like a better long term solution. For sbc,
Acked-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Thanks,
Paul.
--
> "fdtfile=sbc8548.dtb\0"
>
> #define CONFIG_NFSBOOTCOMMAND \
prev parent reply other threads:[~2016-07-20 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 22:52 [U-Boot] [PATCH] powerpc/85xx: Increase fdt address Scott Wood
2016-07-20 0:20 ` Paul Gortmaker [this message]
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=20160720002043.GQ21225@windriver.com \
--to=paul.gortmaker@windriver.com \
--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