From: Soeren Moch <smoch@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] board: tbs2910: Remove FIT support in defconfig to reduce u-boot size
Date: Tue, 8 Jan 2019 11:14:47 +0100 [thread overview]
Message-ID: <f566697f-84b1-e983-ce68-ab73f036d40e@web.de> (raw)
In-Reply-To: <20190105083118.13491-2-smoch@web.de>
Stefano,
can you apply this for v2019.01? This is really a important fix to avoid
environment and u-boot binary overwriting each other.
It is also a small local fix which cannot hurt anybody else.
Thanks,
Soeren
On 05.01.19 09:31, Soeren Moch wrote:
> The current defconfig build generates a u-boot.imx file that is too large
> for the available space on a eMMC/SD card. Installing this file overwrites
> the u-boot environment. So disable the unused FIT support to reduce the
> size of the u-boot binary.
>
> Signed-off-by: Soeren Moch <smoch@web.de>
> ---
> Cc: Stefano Babic <sbabic@denx.de>
> Cc: Fabio Estevam <fabio.estevam@nxp.com>
> Cc: u-boot at lists.denx.de
> ---
> configs/tbs2910_defconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/configs/tbs2910_defconfig b/configs/tbs2910_defconfig
> index 55cd9bd998..fc15dcf013 100644
> --- a/configs/tbs2910_defconfig
> +++ b/configs/tbs2910_defconfig
> @@ -5,7 +5,6 @@ CONFIG_SYS_TEXT_BASE=0x17800000
> CONFIG_TARGET_TBS2910=y
> CONFIG_CMD_HDMIDETECT=y
> CONFIG_NR_DRAM_BANKS=1
> -CONFIG_FIT=y
> CONFIG_BOOTDELAY=3
> CONFIG_PRE_CONSOLE_BUFFER=y
> CONFIG_PRE_CON_BUF_ADDR=0x7c000000
>
next prev parent reply other threads:[~2019-01-08 10:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 8:31 [U-Boot] [PATCH 1/2] board: tbs2910: Add u-boot.imx size limit check Soeren Moch
2019-01-05 8:31 ` [U-Boot] [PATCH 2/2] board: tbs2910: Remove FIT support in defconfig to reduce u-boot size Soeren Moch
2019-01-08 10:14 ` Soeren Moch [this message]
2019-01-08 10:24 ` Stefano Babic
2019-01-08 11:03 ` Soeren Moch
2019-01-09 16:01 ` Stefano Babic
2019-01-09 22:39 ` Tom Rini
2019-01-10 1:28 ` Soeren Moch
2019-01-10 2:30 ` Tom Rini
2019-01-10 14:03 ` Soeren Moch
2019-01-10 15:06 ` Tom Rini
2019-01-11 13:11 ` Soeren Moch
2019-01-11 14:32 ` Tom Rini
2019-01-10 8:00 ` Stefano Babic
2019-01-10 8:11 ` Simon Goldschmidt
2019-01-10 15:56 ` Tom Rini
2019-01-10 16:36 ` Simon Goldschmidt
2019-01-10 16:54 ` Tom Rini
2019-01-11 6:43 ` Simon Goldschmidt
2019-01-11 7:22 ` Simon Goldschmidt
2019-01-11 14:44 ` Tom Rini
2019-01-10 14:44 ` Tom Rini
2019-01-10 14:51 ` Stefano Babic
2019-01-10 15:12 ` Tom Rini
2019-01-10 22:46 ` Stefano Babic
2019-01-11 6:27 ` Simon Goldschmidt
2019-01-10 15:53 ` Tom Rini
2019-01-11 13:11 ` Sören Moch
2019-01-10 8:09 ` Joakim Tjernlund
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=f566697f-84b1-e983-ce68-ab73f036d40e@web.de \
--to=smoch@web.de \
--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