From: Neha Malcom Francis <n-francis@ti.com>
To: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
"sjg@chromium.org" <sjg@chromium.org>
Cc: "kamlesh@ti.com" <kamlesh@ti.com>,
"u-kumar1@ti.com" <u-kumar1@ti.com>,
"m-chawdhry@ti.com" <m-chawdhry@ti.com>,
"afd@ti.com" <afd@ti.com>,
"mkorpershoek@baylibre.com" <mkorpershoek@baylibre.com>,
"nm@ti.com" <nm@ti.com>, "vigneshr@ti.com" <vigneshr@ti.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH 0/2] Cleanup K3 binman FIT images
Date: Thu, 16 Nov 2023 10:38:41 +0530 [thread overview]
Message-ID: <4454dcb0-f97a-4f10-9a87-d043b48d9f31@ti.com> (raw)
In-Reply-To: <8aee10aca8ef6f5acb5687a114d25453fd27b3d0.camel@toradex.com>
Hi Marcel,
On 15/11/23 23:03, Marcel Ziswiler wrote:
> Hi Neha
>
> On Wed, 2023-11-15 at 15:40 +0530, Neha Malcom Francis wrote:
>> Instead of duplicating the same FIT formats over and over again for
>> different K3 devices, make use of the templating support to have FIT
>> templates for the same.
>>
>> Note: I purposely did not add the trial to template out the non-FIT
>> bootloader image (tiboot3.bin) as it reduces the readibility and
>> understandability of how the image is packaged because of the various
>> different boot flows.
>>
>> Boot logs:
>> https://gist.github.com/nehamalcom/9abe7955ebb4a251923e76412834c886
>
> For the whole series:
>
> Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
Thanks for testing!
>> Neha Malcom Francis (2):
>> arm: dts: k3-binman: Add support for FIT templates
>> arm: dts: k3-*-binman: Move to using templated FITs
>>
>> arch/arm/dts/k3-am625-sk-binman.dtsi | 157 +--------
>> .../dts/k3-am625-verdin-wifi-dev-binman.dtsi | 155 +-------
>> arch/arm/dts/k3-am62a-sk-binman.dtsi | 158 +--------
>> arch/arm/dts/k3-am64x-binman.dtsi | 151 +-------
>> arch/arm/dts/k3-am65x-binman.dtsi | 273 +-------------
>> arch/arm/dts/k3-binman.dtsi | 327 +++++++++++++++++
>> arch/arm/dts/k3-j7200-binman.dtsi | 159 +--------
>> arch/arm/dts/k3-j721e-binman.dtsi | 332 +-----------------
>> arch/arm/dts/k3-j721s2-binman.dtsi | 157 +--------
>> 9 files changed, 381 insertions(+), 1488 deletions(-)
>
> Thanks!
>
> Cheers
>
> Marcel
--
Thanking You
Neha Malcom Francis
prev parent reply other threads:[~2023-11-16 5:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 10:10 [PATCH 0/2] Cleanup K3 binman FIT images Neha Malcom Francis
2023-11-15 10:10 ` [PATCH 1/2] arm: dts: k3-binman: Add support for FIT templates Neha Malcom Francis
2023-11-16 16:03 ` Simon Glass
2023-11-16 16:43 ` Marcel Ziswiler
2023-11-17 5:15 ` Neha Malcom Francis
2023-11-22 20:50 ` Tom Rini
2023-11-15 10:10 ` [PATCH 2/2] arm: dts: k3-*-binman: Move to using templated FITs Neha Malcom Francis
2023-11-15 15:52 ` Andrew Davis
2023-11-16 5:08 ` Neha Malcom Francis
2023-11-16 16:04 ` Simon Glass
2023-11-22 5:20 ` Manorit Chawdhry
2023-11-22 5:52 ` Neha Malcom Francis
2023-11-22 20:50 ` Tom Rini
2023-11-15 17:33 ` [PATCH 0/2] Cleanup K3 binman FIT images Marcel Ziswiler
2023-11-16 5:08 ` Neha Malcom Francis [this message]
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=4454dcb0-f97a-4f10-9a87-d043b48d9f31@ti.com \
--to=n-francis@ti.com \
--cc=afd@ti.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mkorpershoek@baylibre.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--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