From: Daniel Golle <daniel@makrotopia.org>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.u-boot-project.org
Subject: Re: [0/9] boot: add imagemap on-demand image loading from storage
Date: Tue, 29 Sep 2026 01:32:28 +0100 [thread overview]
Message-ID: <arsHHMG3icqe1WdB@makrotopia.org> (raw)
In-Reply-To: <CAFLszTixHT2ZLo92bURLbzbCjyTO1B1SsRkBXhN6FMcBxWhTWg@mail.gmail.com>
Hi Simon,
thank you for the extensive review of the series. Meanwhile v2 had
already been sent and Tom has already picked it into 'next'.
Apart from one issue (see below) I've addressed all correctness issues
you have pointed out in a follow up series which I have sent now.
On Mon, Sep 28, 2026 at 09:13:53AM -0600, Simon Glass wrote:
> Hi Daniel,
>
> On 2026-08-23T19:12:43, Daniel Golle <daniel@makrotopia.org> wrote:
>
> > The first in-tree consumer, a bootmeth for OpenWrt-style FIT firmware, will
> > follow as a separate series.
>
> When that comes, will you be able to add a test for the bootmeth?
Yes. I've got that planned but it's not done yet. Compared to imagemap
and the dm-verity integration (which are both covered by unit tests)
the bootmeth by itself also isn't that spectacular ;)
> > boot: fit: support on-demand loading in fit_image_load()
>
> Related: patch 6 adds a struct udevice *imagemap field to both struct
> bootm_info and struct bootm_headers, but nothing in this series sets
> either outside the tests. The FIT hook is dead code in the built tree.
You are right, that is the gap the bootmeth series is going to close,
and until it lands the integration is carried on the strength of
out-of-tree testing, which is not a good place for it to sit.
I would rather fix that by getting the consumer in than by adding a
synthetic caller.
Cheers
Daniel
next prev parent reply other threads:[~2026-09-29 0:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 19:12 [PATCH 0/9] boot: add imagemap on-demand image loading from storage Daniel Golle
2026-08-23 19:13 ` [PATCH 1/9] mtd: bind an mtd_blk device for non-NAND MTD masters Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:13 ` [PATCH 2/9] mtd: nand: sandbox: forbid sub-page writes Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:13 ` [PATCH 3/9] cmd: ubi: create a ubi_blk device when attaching UBI Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:13 ` [PATCH 4/9] mtd: nand: spi: drop the eager ubi_blk binding Daniel Golle
2026-08-23 19:13 ` [PATCH 5/9] boot: add imagemap on-demand loading from storage Daniel Golle
2026-08-24 22:55 ` Tom Rini
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:14 ` [PATCH 6/9] boot: fit: support on-demand loading in fit_image_load() Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:14 ` [PATCH 7/9] configs: sandbox: enable imagemap and its storage backends Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:16 ` [PATCH 8/9] test: boot: add imagemap unit tests Daniel Golle
2026-09-28 15:12 ` Simon Glass
2026-08-23 19:16 ` [PATCH 9/9] doc: imagemap: document on-demand loading framework Daniel Golle
2026-09-28 15:17 ` Simon Glass
2026-08-24 22:59 ` [PATCH 0/9] boot: add imagemap on-demand image loading from storage Tom Rini
2026-09-28 15:13 ` [0/9] " Simon Glass
2026-09-29 0:32 ` Daniel Golle [this message]
2026-10-01 17:23 ` Simon Glass
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=arsHHMG3icqe1WdB@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.u-boot-project.org \
/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.