From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: Anshul Dalal <anshuld@ti.com>, <u-boot@lists.denx.de>,
<vigneshr@ti.com>, <trini@konsulko.com>,
<robertcnelson@gmail.com>, <w.egorov@phytec.de>,
<francesco.dolcini@toradex.com>, <ggiordano@phytec.com>,
<m-chawdhry@ti.com>, <a-nandan@ti.com>
Subject: Re: [PATCH v1 0/4] k3: migrate SPL_TEXT_BASE to new address
Date: Wed, 16 Apr 2025 14:51:13 -0500 [thread overview]
Message-ID: <20250416195113.mtfdclfvb756vpll@scoreless> (raw)
In-Reply-To: <8146a036-681d-4c45-9285-c58259fec14b@ti.com>
On 11:38-20250416, Andrew Davis wrote:
> > > > How about u-boot documentation?
> > >
> > > I will update that in the next revision along with any feedback I
> > > receive on this patch.
> >
> > IMHO, This change is too intrusive and impacts downstream customers
> > including inflight production devices.
> >
>
> Could you elaborate a little?
>
> They do not even need to update their TF-A version, if they want to
> use their current version they simply recompile it with a single
> extra build flag:
>
> PRELOADED_BL33_BASE=0x822000000
For folks who are trying to boot linux from TFA, they could do the same.
>
> They should have no reason not to be able to do this. But even *if*
> they cannot do that, the whole point of the jump-stub here is to
> save them even having to do a simple compile.
>
> IMHO "downstream customers including inflight production devices"
> should not be a reason to block good and useful changes here in
> upstream. But again, this change doesn't break anything for them in
> the first place, so why bring that up?
I dont see a specific value here. U-boot just works. For folks who want
direct TFA to kernel jump (which is a niche fast boot usecase), go ahead
and use TFA with the mentioned build option.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-04-16 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 7:30 [PATCH v1 0/4] k3: migrate SPL_TEXT_BASE to new address Anshul Dalal
2025-04-16 7:30 ` [PATCH v1 1/4] spl: Kconfig: k3: set SPL_TEXT_BASE to 0x82200000 Anshul Dalal
2025-04-16 7:30 ` [PATCH v1 2/4] mach-k3: add a jump stub to support older ATF builds Anshul Dalal
2025-04-16 7:30 ` [PATCH v1 3/4] binman: k3: add jump-stub to tispl.bin Anshul Dalal
2025-04-16 7:30 ` [PATCH v1 4/4] binman: k3: add jump-stub as loadable Anshul Dalal
2025-04-16 11:24 ` [PATCH v1 0/4] k3: migrate SPL_TEXT_BASE to new address Nishanth Menon
2025-04-16 13:48 ` Anshul Dalal
2025-04-16 15:05 ` Nishanth Menon
2025-04-16 16:38 ` Andrew Davis
2025-04-16 19:51 ` Nishanth Menon [this message]
2025-04-17 9:21 ` Anshul Dalal
2025-04-17 11:30 ` Nishanth Menon
2025-04-17 14:16 ` Tom Rini
2025-04-22 6:59 ` Ahmad Fatoum
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=20250416195113.mtfdclfvb756vpll@scoreless \
--to=nm@ti.com \
--cc=a-nandan@ti.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=francesco.dolcini@toradex.com \
--cc=ggiordano@phytec.com \
--cc=m-chawdhry@ti.com \
--cc=robertcnelson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.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 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.