From: Tom Rini <trini@konsulko.com>
To: Anshul Dalal <anshuld@ti.com>
Cc: u-boot@lists.denx.de, Andrew Davis <afd@ti.com>,
Judith Mendez <jm@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Hrushikesh Salunke <h-salunke@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Vignesh R <vigneshr@ti.com>,
Christoph Niedermaier <cniedermaier@dh-electronics.com>
Subject: Re: [PATCH master v4] Kconfig: select SPL_USE_TINY_PRINTF_POINTER_SUPPORT for K3
Date: Tue, 20 Jan 2026 08:54:09 -0600 [thread overview]
Message-ID: <20260120145409.GL3416603@bill-the-cat> (raw)
In-Reply-To: <20260120-am65_dfu_fix-v4-1-36b2dfab3a64@ti.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Tue, Jan 20, 2026 at 10:04:28AM +0530, Anshul Dalal wrote:
> Since the commit 1e24e84db41a ("tiny-printf: Handle formatting of %p
> with an extra Kconfig"), SPL_USE_TINY_PRINTF_POINTER_SUPPORT has been
> made mandatory in order to use %p which would earlier have defaulted to
> a 'long' print.
>
> Without this config symbol, k3_sysfw_dfu_download fails to set the
> correct value for the DFU string with:
>
> sprintf(dfu_str, "sysfw.itb ram 0x%p 0x%x", addr,
> CONFIG_K3_SYSFW_IMAGE_SIZE_MAX);
>
> The value we get "sysfw.itb ram 0x? 0x41c29d40" causes a boot failure.
>
> Therefore this patch sets SPL_USE_TINY_PRINTF_POINTER_SUPPORT for all K3
> devices since the size impact is less than 100 bytes.
>
> Signed-off-by: Anshul Dalal <anshuld@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-20 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 4:34 [PATCH master v4] Kconfig: select SPL_USE_TINY_PRINTF_POINTER_SUPPORT for K3 Anshul Dalal
2026-01-20 14:54 ` Tom Rini [this message]
2026-01-28 14:02 ` Tom Rini
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=20260120145409.GL3416603@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=cniedermaier@dh-electronics.com \
--cc=h-salunke@ti.com \
--cc=jm@ti.com \
--cc=n-francis@ti.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox