All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
Cc: u-boot@lists.denx.de,
	Malte Schmidt <malte.schmidt-oss@weidmueller.com>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
	Etienne Carriere <etienne.carriere@linaro.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Malte Schmidt <malte.schmidt@weidmueller.com>,
	Masahisa Kojima <masahisa.kojima@linaro.org>
Subject: Re: [PATCH 0/5] Extend mkeficapsule tool to pack multiple payloads
Date: Sat, 17 Jun 2023 09:45:04 +0900	[thread overview]
Message-ID: <ZI0CEIT8teuaH3PN@laputa> (raw)
In-Reply-To: <20230616113426.13976-1-stefan.herbrechtsmeier-oss@weidmueller.com>

On Fri, Jun 16, 2023 at 01:34:21PM +0200, Stefan Herbrechtsmeier wrote:
> From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
> 
> 
> Currently, the mkeficapsule tool supports at most one payload inside the
> capsule. However, the UEFI specification and the u-boot code
> support multiple payloads inside one capsule. Extend the tool by
> this feature. The tool is kept backwards-compatible, so it can still
> be used and called exactly as before if desired.

One of reasons why only a single image be included is that I didn't
see any strong reason to do so because U-Boot already has an archive
format of multiple images, named FIT. I wanted to utilize the existing
framework which is widely used on U-Boot and the current implementation
of FMP supports this format.
It seems to be just enough.

Do you have any useful use case of multiple images?

-Takahiro Akashi


> 
> Malte Schmidt (5):
>   mkeficapsule: constify function parameters
>   mkeficapsule: add support for multiple payloads inside capsule
>   test: efi_capsule: test a capsule update containing multiple images
>   doc: uefi: update mkeficapsule documentation
>   doc: uefi: clarify capsule concept
> 
>  doc/develop/uefi/uefi.rst                     |  73 +-
>  test/py/tests/test_efi_capsule/conftest.py    |  18 +-
>  .../test_capsule_firmware_raw.py              |  46 +-
>  .../test_capsule_firmware_signed_raw.py       |  24 +-
>  tools/eficapsule.h                            |   5 -
>  tools/mkeficapsule.c                          | 651 +++++++++++++-----
>  6 files changed, 622 insertions(+), 195 deletions(-)
> 
> -- 
> 2.30.2
> 

  parent reply	other threads:[~2023-06-17  0:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 11:34 [PATCH 0/5] Extend mkeficapsule tool to pack multiple payloads Stefan Herbrechtsmeier
2023-06-16 11:34 ` [PATCH 1/5] mkeficapsule: constify function parameters Stefan Herbrechtsmeier
2023-06-16 18:18   ` Heinrich Schuchardt
2023-06-21 11:40     ` Schmidt, Malte
2023-06-16 11:34 ` [PATCH 2/5] mkeficapsule: add support for multiple payloads inside capsule Stefan Herbrechtsmeier
2023-06-16 12:26   ` Sughosh Ganu
2023-06-16 12:32     ` Sughosh Ganu
2023-06-16 12:59       ` Schmidt, Malte
2023-06-16 13:32         ` Schmidt, Malte
2023-06-17  0:37           ` AKASHI Takahiro
2023-06-19 11:21             ` Schmidt, Malte
2023-06-17  0:56       ` AKASHI Takahiro
2023-06-17  6:38         ` Sughosh Ganu
2023-06-16 18:21   ` Heinrich Schuchardt
2023-06-16 11:34 ` [PATCH 3/5] test: efi_capsule: test a capsule update containing multiple images Stefan Herbrechtsmeier
2023-06-16 11:34 ` [PATCH 4/5] doc: uefi: update mkeficapsule documentation Stefan Herbrechtsmeier
2023-06-16 18:03   ` Heinrich Schuchardt
2023-06-16 11:34 ` [PATCH 5/5] doc: uefi: clarify capsule concept Stefan Herbrechtsmeier
2023-06-16 17:50   ` Heinrich Schuchardt
2023-06-17  0:45 ` AKASHI Takahiro [this message]
2023-06-19 11:15   ` [PATCH 0/5] Extend mkeficapsule tool to pack multiple payloads Schmidt, Malte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZI0CEIT8teuaH3PN@laputa \
    --to=takahiro.akashi@linaro.org \
    --cc=etienne.carriere@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=malte.schmidt-oss@weidmueller.com \
    --cc=malte.schmidt@weidmueller.com \
    --cc=masahisa.kojima@linaro.org \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.com \
    --cc=stefan.herbrechtsmeier@weidmueller.com \
    --cc=sughosh.ganu@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.