mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v2 00/11] Add FIT image overlay support
Date: Thu, 13 Jun 2024 14:58:07 +0200	[thread overview]
Message-ID: <20240613125818.30499-1-m.felsch@pengutronix.de> (raw)

Hi,

this series add the support to load FIT image supplied devicetree overlays.
The v1 of this series can be found here [1].

The overlay loading wasn't coupled to bootm due to the following
reasons:
 - By making use of the common overlay handling we can specifiy a
   different/separate FIT image which provides only overlays.
 - It should be possible to apply FIT image overlay to the barebox
   live-tree (not implemented yet).
 - Loading a single overlay takes ~20ms (depending on the overlay size)
   if the same FIT image is used to supply the kernel, initrd,
   devicetree and devicetree-overlays. This is an improvement compared to
   the v1 of this series which required ~1sec.

Regards,
  Marco

[1] https://lore.pengutronix.de/barebox/20240322164953.1772129-1-m.felsch@pengutronix.de/

Marco Felsch (11):
  FIT: fix missing free in fit_open error path
  of: overlay: add of.overlay.fitconfigpattern param
  FIT: skip possible overlay config nodes
  of: overlay: make the pattern match function more generic
  of: overlay: make search dir/path more generic
  FIT: expose useful helpers
  of: overlay: add FIT overlay support
  of: overlay: drop unnecessary empty check in
    of_overlay_global_fixup_dir
  of: overlay: replace filename with an more unique name
  FIT: save filename during fit_open
  FIT: add support to cache opened fit images

 common/image-fit.c   |  69 +++++++++++++-
 drivers/of/overlay.c | 212 ++++++++++++++++++++++++++++++++++---------
 include/image-fit.h  |   7 ++
 include/of.h         |   3 +-
 4 files changed, 246 insertions(+), 45 deletions(-)

-- 
2.39.2




             reply	other threads:[~2024-06-13 12:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 12:58 Marco Felsch [this message]
2024-06-13 12:58 ` [PATCH v2 01/11] FIT: fix missing free in fit_open error path Marco Felsch
2024-06-13 12:58 ` [PATCH v2 02/11] of: overlay: add of.overlay.fitconfigpattern param Marco Felsch
2024-06-13 12:58 ` [PATCH v2 03/11] FIT: skip possible overlay config nodes Marco Felsch
2024-06-17  8:05   ` Sascha Hauer
2024-06-13 12:58 ` [PATCH v2 04/11] of: overlay: make the pattern match function more generic Marco Felsch
2024-06-13 12:58 ` [PATCH v2 05/11] of: overlay: make search dir/path " Marco Felsch
2024-06-13 12:58 ` [PATCH v2 06/11] FIT: expose useful helpers Marco Felsch
2024-06-13 12:58 ` [PATCH v2 07/11] of: overlay: add FIT overlay support Marco Felsch
2024-06-13 12:58 ` [PATCH v2 08/11] of: overlay: drop unnecessary empty check in of_overlay_global_fixup_dir Marco Felsch
2024-06-13 12:58 ` [PATCH v2 09/11] of: overlay: replace filename with an more unique name Marco Felsch
2024-06-13 12:58 ` [PATCH v2 10/11] FIT: save filename during fit_open Marco Felsch
2024-06-17 11:02   ` Sascha Hauer
2024-06-26 10:15     ` Marco Felsch
2024-06-13 12:58 ` [PATCH v2 11/11] FIT: add support to cache opened fit images Marco Felsch
2024-06-17 11:11   ` Sascha Hauer
2024-06-26 10:14     ` Marco Felsch

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=20240613125818.30499-1-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox