From: Tom Rini <trini@konsulko.com>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
u-boot@lists.denx.de,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Anand Moon <anand@edgeble.ai>
Subject: Re: [PATCH] Revert "rockchip: Only call binman when TPL available"
Date: Mon, 30 Jan 2023 10:15:32 -0500 [thread overview]
Message-ID: <Y9ffFD8n/412vOCP@bill-the-cat> (raw)
In-Reply-To: <CA+VMnFxFMtd2+4CuUdZ_=Nk_4DmvtxtD_Ap4jRZVRWEOKNXcpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Mon, Jan 30, 2023 at 08:29:35PM +0530, Jagan Teki wrote:
> On Fri, 27 Jan 2023 at 12:51, Jagan Teki <jagan@edgeble.ai> wrote:
> >
> > This reverts commit f5315dd6290a588434e4f79bfd2886bb7df9210d.
> >
> > [why]
> > TPL is not mandatory for not all Rockchip SoCs, some SoCs like
> > RK356x, and RK3588 still use mainline u-boot without TPL as
> > their ddr init programs are accessed via binaries provided by
> > Rockchip instead of ddr source code.
> >
> > Marking TPL build makes it not able to build u-boot.itb on
> > RK356x targets so revert this so that it can build an SPL build
> > that would support all across Rockchip platforms.
> >
> > Suggested-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> > Signed-off-by: Jagan Teki <jagan@edgeble.ai>
> > ---
>
> Can someone apply this before -rc is released?
Yes, but where's the follow-up series to make both cases work again, I
think I missed it?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-30 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 7:21 [PATCH] Revert "rockchip: Only call binman when TPL available" Jagan Teki
2023-01-27 11:44 ` Anand Moon
2023-01-30 14:59 ` Jagan Teki
2023-01-30 15:15 ` Tom Rini [this message]
2023-01-30 21:14 ` Jagan Teki
2023-01-30 21:21 ` Tom Rini
2023-01-30 21:05 ` Tom Rini
2023-01-31 2:53 ` Kever Yang
2023-01-31 3:09 ` Tom Rini
2023-01-31 10:54 ` Quentin Schulz
2023-02-04 22:23 ` Simon Glass
2023-02-05 20:29 ` Jonas Karlman
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=Y9ffFD8n/412vOCP@bill-the-cat \
--to=trini@konsulko.com \
--cc=anand@edgeble.ai \
--cc=jagan@edgeble.ai \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--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 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.