tools: mkeficapsule: allow for specifying GUID explicitly
authorAKASHI Takahiro <takahiro.akashi@linaro.org>
Wed, 9 Feb 2022 10:10:39 +0000 (19:10 +0900)
committerHeinrich Schuchardt <heinrich.schuchardt@canonical.com>
Fri, 11 Feb 2022 19:07:55 +0000 (20:07 +0100)
commitd9612f4426b490a5df420083b5aaf812607d4197
tree85810db4cb18dde17e9e438de0531e6977dc8a7e
parentbad58cb308acdf739e855e3336dfdf1a8d7b08a4
tools: mkeficapsule: allow for specifying GUID explicitly

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>

Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
.azure-pipelines.yml
doc/develop/uefi/uefi.rst
doc/mkeficapsule.1
tools/Makefile
tools/mkeficapsule.c