On Sun, Jun 21, 2020 at 12:09:23AM +0530, Sughosh Ganu wrote: > On Wed, 17 Jun 2020 at 08:26, AKASHI Takahiro <takahiro.aka...@linaro.org> > wrote: > > > In this commit, a very simple firmware management protocol driver > > is implemented. It will take a common FIT image firmware in a capsule > > file and apply the data using dfu backend storage drivers via > > update_fit() interface. > > > > So "dfu_alt_info" variable should be properly set to specify a device > > and location to be updated. Please read README.dfu. > > > > Fit image is a common file format for firmware update on U-Boot, and > > this protocol works neatly just as a wrapper for one. > > > > Signed-off-by: AKASHI Takahiro <takahiro.aka...@linaro.org> > > --- > > include/efi_api.h | 4 + > > include/efi_loader.h | 2 + > > lib/efi_loader/Kconfig | 11 ++ > > lib/efi_loader/Makefile | 1 + > > lib/efi_loader/efi_capsule.c | 12 +- > > lib/efi_loader/efi_firmware.c | 253 ++++++++++++++++++++++++++++++++++ > > 6 files changed, 282 insertions(+), 1 deletion(-) > > create mode 100644 lib/efi_loader/efi_firmware.c > > > > Like we had discussed this offline, I don't think that efi_firmware.c name > accurately represents that the file is implementing the firmware management > protocol. This can be changed to efi_fmp.c, or if you don't prefer > acronyms, efi_firmware_mgmt_protocol.c
I think that efi_firmware is a good prefix without any confusion given that there is no other features related to "firmware". -Takahiro Akashi > > -sughosh