On Wed Feb 18, 2026 at 12:31 PM EET, Kory Maincent wrote: > Hello Sughosh, > > On Wed, 18 Feb 2026 15:26:35 +0530 > Sughosh Ganu <[email protected]> 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 <[email protected]> >> > > --- >> > >> > 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. > The final goal is to have RAUC updating the boot A/B partition and switching > to > it calling this new tool.
The whole point of adding this via EFI, is that we had an existing mechanism for reporting. e.g when an update is in trial state and an acceptance must be explicitly approved by the OS. I assume RAUC etc will implement that ad-hoc? Thanks /Ilias > > Regards,
