From: Anshul Dalal <anshuld@ti.com>
To: <u-boot@lists.denx.de>
Cc: Anshul Dalal <anshuld@ti.com>, <vigneshr@ti.com>, <trini@konsulko.com>
Subject: [PATCH v7 4/4] configs: colibri_vf: set CMD_BOOTM
Date: Tue, 8 Apr 2025 19:44:33 +0530 [thread overview]
Message-ID: <20250408141436.712387-4-anshuld@ti.com> (raw)
In-Reply-To: <20250408141436.712387-1-anshuld@ti.com>
Currently, CMD_BOOTx selects both bootm.o and the respective image.o or
zimage.o for compilation. After the addition of LIB_BOOTx, the behaviour
changes so CMD_BOOTx would not select bootm.o. This leads to build
failure on calibri_vf since it unsets BOOTM while still using BOOTZ.
This was added in commit c5954431eb6c ("configs: colibri_vf: disable
obscure options") to save size but unsetting BOOTM specifically does not
seem to save any space. So the change can be safely reverted
Signed-off-by: Anshul Dalal <anshuld@ti.com>
---
configs/colibri_vf_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/configs/colibri_vf_defconfig b/configs/colibri_vf_defconfig
index 3a806243b19..823b4f07460 100644
--- a/configs/colibri_vf_defconfig
+++ b/configs/colibri_vf_defconfig
@@ -34,7 +34,6 @@ CONFIG_HUSH_PARSER=y
# CONFIG_SYS_LONGHELP is not set
CONFIG_SYS_PROMPT="Colibri VFxx # "
# CONFIG_CMD_BOOTD is not set
-# CONFIG_CMD_BOOTM is not set
CONFIG_CMD_BOOTZ=y
# CONFIG_CMD_ELF is not set
# CONFIG_CMD_IMI is not set
--
2.49.0
next prev parent reply other threads:[~2025-04-08 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 14:14 [PATCH v7 1/4] spl: remove usage of CMD_BOOTx from image parsing Anshul Dalal
2025-04-08 14:14 ` [PATCH v7 2/4] configs: disable SPL_BOOTZ to preserve spl size Anshul Dalal
2025-04-08 14:14 ` [PATCH v7 3/4] configs: migrate falcon configs to SPL_BOOTx Anshul Dalal
2025-04-08 14:14 ` Anshul Dalal [this message]
2025-04-17 20:58 ` [PATCH v7 1/4] spl: remove usage of CMD_BOOTx from image parsing Tom Rini
2025-04-17 21:37 ` Simon Glass
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=20250408141436.712387-4-anshuld@ti.com \
--to=anshuld@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.