From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] board: STiH410-B2260: Set SYS_BOOTM_LEN to 16M
Date: Thu, 26 Jul 2018 15:54:06 -0400 [thread overview]
Message-ID: <20180726195406.GG7590@bill-the-cat> (raw)
In-Reply-To: <1531728259-14675-1-git-send-email-patrice.chotard@st.com>
On Mon, Jul 16, 2018 at 10:04:19AM +0200, Patrice Chotard wrote:
> With recent kernel v4.18-rcx, uImage becomes bigger than 8MB.
> Set SYS_BOOTM_LEN to 16MB, this fix the following error message:
> "Fix Loading Kernel Image ... Image too large: increase
> CONFIG_SYS_BOOTM_LEN"
>
> Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180726/1487b423/attachment.sig>
prev parent reply other threads:[~2018-07-26 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 8:04 [U-Boot] [PATCH] board: STiH410-B2260: Set SYS_BOOTM_LEN to 16M Patrice Chotard
2018-07-26 19:54 ` Tom Rini [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=20180726195406.GG7590@bill-the-cat \
--to=trini@konsulko.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