diff options
| author | AKASHI Takahiro <takahiro.akashi@linaro.org> | 2022-02-09 19:10:39 +0900 |
|---|---|---|
| committer | Heinrich Schuchardt <heinrich.schuchardt@canonical.com> | 2022-02-11 20:07:55 +0100 |
| commit | d9612f4426b490a5df420083b5aaf812607d4197 (patch) | |
| tree | 85810db4cb18dde17e9e438de0531e6977dc8a7e /lib/efi_loader/efi_image_loader.c | |
| parent | bad58cb308acdf739e855e3336dfdf1a8d7b08a4 (diff) | |
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>
Diffstat (limited to 'lib/efi_loader/efi_image_loader.c')
0 files changed, 0 insertions, 0 deletions