From: Sughosh Ganu <sughosh.ganu@arm.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: u-boot@lists.denx.de, jose.marinho@arm.com,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Tom Rini" <trini@konsulko.com>,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Paul HENRYS" <paul.henrys_ext@softathome.com>,
"Greg Malysa" <malysagreg@gmail.com>,
"Arturs Artamonovs" <arturs.artamonovs@analog.com>,
"Vasileios Bimpikas" <vasileios.bimpikas@analog.com>,
"Utsav Agarwal" <utsav.agarwal@analog.com>,
"Nathan Barrett-Morrison" <nathan.morrison@timesys.com>,
"Peng Fan" <peng.fan@nxp.com>, "Simon Glass" <sjg@chromium.org>,
"Duje Mihanović" <duje@dujemihanovic.xyz>,
"Stefan Roese" <stefan.roese@mailbox.org>,
"Mattijs Korpershoek" <mkorpershoek@kernel.org>,
"Sumit Garg" <sumit.garg@kernel.org>,
"Heiko Schocher" <hs@nabladev.com>,
"Alif Zakuan Yuslaimi" <alif.zakuan.yuslaimi@altera.com>,
"E Shattow" <e@freeshell.de>,
"Raymond Mao" <raymondmaoca@gmail.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Shiji Yang" <yangshiji66@outlook.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Leonard Anderweit" <l.anderweit@phytec.de>,
"Yao Zi" <me@ziyao.cc>
Subject: Re: [PATCH v3 5/6] tools: Add support for fwumdata tool
Date: Wed, 18 Feb 2026 16:53:23 +0530 [thread overview]
Message-ID: <aZWhK1ZC1RqsNno7@a079122.arm.com> (raw)
In-Reply-To: <20260218120816.760df1ff@kmaincent-XPS-13-7390>
On Wed, Feb 18, 2026 at 12:08:16PM +0100, Kory Maincent wrote:
> On Wed, 18 Feb 2026 16:15:14 +0530
> Sughosh Ganu <sughosh.ganu@arm.com> wrote:
>
> > On Wed, Feb 18, 2026 at 11:31:16AM +0100, Kory Maincent wrote:
> > > Hello Sughosh,
> > >
> > > On Wed, 18 Feb 2026 15:26:35 +0530
> > > Sughosh Ganu <sughosh.ganu@arm.com> wrote:
> > >
> > > > On Wed, Feb 18, 2026 at 03:17:58PM +0530, Sughosh Ganu wrote:
> > > > > On Mon, Feb 16, 2026 at 02:35:35PM +0100, Kory Maincent wrote:
> > > > > > Add a new fwumdata tool to allows users to read, display, and modify
> > > > > > FWU (Firmware Update) metadata from Linux userspace. It provides
> > > > > > functionality similar to fw_printenv/fw_setenv but for FWU metadata.
> > > > > > Users can view metadata, change active/previous bank indices, modify
> > > > > > bank states, and set image acceptance flags. Configuration is done
> > > > > > via fwumdata.config file.
> > > > > >
> > > > > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > > > > > ---
> > > > >
> > > > > I am not sure if this has been discussed with Ilias earlier, and
> > > > > apologies if it has been, but I do think that this patch is not
> > > > > adhering to the DEN0118 specification, specifically the part mentioned
> > > > > in section A3.2.1, which says that the metadata is to be maintained by
> > > > > the Update Agent. I would like to hear from Jose Marinho, who is the
> > > > > author of the spec, on what he thinks about this approach.
> > > > >
> > > > > I do think that the other patches in series look fine, and can be
> > > > > applied. There is just an issue of inclusion of the tool for
> > > > > building. I will comment on that patch separately.
> > > >
> > > >
> > > > Adding Jose to the discussion.
> > >
> > > We indeed already had some discussion about it with Ilias.
> > > https://lists.denx.de/pipermail/u-boot/2025-December/605924.html
> > >
> > > It seems ST deviate from the original idea behind the standard. It does not
> > > use EFI neither update capsule.
> > > TF-A is managing the selection of the boot partition (FIP image: OPTEE +
> > > bootloader) according to the FWU metadata content and is dealingwith the
> > > rollback mechanism. Linux through this tools is the update agent to select
> > > the boot image.
> >
> > Okay. I guess that is fine then -- with the Update Agent residing in
> > Linux, this is not an issue. My next question then would be, why are
> > you adding this to U-Boot then :). Can this not be bundled with a
> > related package of RAUC maybe(if one such exists)?
>
> There was also a discussion about this topic:
> https://lists.denx.de/pipermail/u-boot/2025-December/604901.html
>
> The final conclusion is:
> - for the short/medium term we add it alongside the mkfwumdata tool.
> - for the long term it would be nice to extract all generic tools to a different repo
> than U-boot to make life easier for other projects.
Okay. In that case, please post a v4 which fixes the building of the
tools. Thanks.
-sughosh
next prev parent reply other threads:[~2026-02-18 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:35 [PATCH v3 0/6] Add support for fwumdata Kory Maincent
2026-02-16 13:35 ` [PATCH v3 1/6] tools: gitignore: Add mkfwumdata to the git ignore file Kory Maincent
2026-02-16 13:35 ` [PATCH v3 2/6] tools: Reorganize mkfwumdata tool into fwumdata_src directory Kory Maincent
2026-02-16 13:35 ` [PATCH v3 3/6] tools: mkfwumdata: Improve error message specificity Kory Maincent
2026-02-16 13:35 ` [PATCH v3 4/6] tools: mkfwumdata: Add bank count validation for FWU metadata v2 Kory Maincent
2026-02-16 13:35 ` [PATCH v3 5/6] tools: Add support for fwumdata tool Kory Maincent
2026-02-18 9:47 ` Sughosh Ganu
2026-02-18 9:56 ` Sughosh Ganu
2026-02-18 10:31 ` Kory Maincent
2026-02-18 10:45 ` Sughosh Ganu
2026-02-18 11:08 ` Kory Maincent
2026-02-18 11:23 ` Sughosh Ganu [this message]
2026-02-18 13:55 ` Ilias Apalodimas
2026-02-18 15:17 ` Kory Maincent
2026-02-18 9:53 ` Sughosh Ganu
2026-02-18 10:36 ` Kory Maincent
2026-02-16 13:35 ` [PATCH v3 6/6] tools: mkfwumdata: Remove dependency on fwu_mdata.h header Kory Maincent
2026-02-18 9:48 ` Sughosh Ganu
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=aZWhK1ZC1RqsNno7@a079122.arm.com \
--to=sughosh.ganu@arm.com \
--cc=alif.zakuan.yuslaimi@altera.com \
--cc=arturs.artamonovs@analog.com \
--cc=daniel@makrotopia.org \
--cc=duje@dujemihanovic.xyz \
--cc=e@freeshell.de \
--cc=hs@nabladev.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=jose.marinho@arm.com \
--cc=kory.maincent@bootlin.com \
--cc=l.anderweit@phytec.de \
--cc=malysagreg@gmail.com \
--cc=me@ziyao.cc \
--cc=mkorpershoek@kernel.org \
--cc=nathan.morrison@timesys.com \
--cc=patrice.chotard@foss.st.com \
--cc=paul.henrys_ext@softathome.com \
--cc=peng.fan@nxp.com \
--cc=raymondmaoca@gmail.com \
--cc=sjg@chromium.org \
--cc=stefan.roese@mailbox.org \
--cc=sumit.garg@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=utsav.agarwal@analog.com \
--cc=vasileios.bimpikas@analog.com \
--cc=xypron.glpk@gmx.de \
--cc=yangshiji66@outlook.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