On Tue, 02 Dec 2025 18:28:25 +0100 Kory Maincent <[email protected]> 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. > > Made a few change to mkfwumdata tool along the way. Still wondering about the choice of putting this fwumdata tool in U-Boot instead of TF-A. TF-A is the boot part that manages the update process and rollback through the FWU metadata, therefore, this is where it should belong. Why, in the first place, mkfwumdata was accepted into U-boot instead of TF-A? Regards, -- Köry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com
