[PATCH v6 07/12] tools: mkeficapsule: allow for specifying GUID explicitly

Simon Glass sjg at chromium.org
Tue Nov 2 15:58:18 CET 2021


Hi Takahiro,

On Mon, 1 Nov 2021 at 18:56, AKASHI Takahiro <takahiro.akashi at linaro.org> wrote:
>
> The existing options, "--fit" and "--raw," are only used to put a proper
> GUID in a capsule header, where GUID identifies a particular FMP (Firmware
> Management Protocol) driver which then would handle the firmware binary in
> a capsule. In fact, mkeficapsule does the exact same job in creating
> a capsule file whatever the firmware binary type is.
>
> To prepare for the future extension, the command syntax will be a bit
> modified to allow users to specify arbitrary GUID for their own FMP driver.
> OLD:
>    [--fit <image> | --raw <image>] <capsule file>
> NEW:
>    [--fit | --raw | --guid <guid-string>] <image> <capsule file>

Do these drivers have names? A guid is not a very friendly thing to
have to provide.

>
> Signed-off-by: AKASHI Takahiro <takahiro.akashi at linaro.org>
> ---
>  doc/develop/uefi/uefi.rst |  4 +-
>  doc/mkeficapsule.1        | 26 +++++++++----
>  tools/mkeficapsule.c      | 78 ++++++++++++++++++++++++++++++---------
>  3 files changed, 81 insertions(+), 27 deletions(-)
>

Reviewed-by: Simon Glass <sjg at chromium.org>

Regards,
Simon


More information about the U-Boot mailing list