From: Marco Felsch <m.felsch@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH v2 1/2] environment: support DT-compatible-specific overlays
Date: Mon, 13 Apr 2026 16:22:02 +0200 [thread overview]
Message-ID: <swgwnzw2j6qsmqq7kbwlfawp4ay2u3wq3fpvyvyt76reyexfyq@2s7q2lqbqiup> (raw)
In-Reply-To: <20260413134422.3562639-1-a.fatoum@pengutronix.de>
On 26-04-13, Ahmad Fatoum wrote:
> From: Ahmad Fatoum <a.fatoum@barebox.org>
>
> Board-specific environments are registered from board code via
> defaultenv_append_directory(), but this isn't possible when using
> CONFIG_DEFAULT_ENVIRONMENT_PATH with an external environment.
>
> Add support for a match.of_compatible/ directory convention within
> the default environment. Subdirectories named after DT root compatible
> strings are overlaid onto /env from most generic to most specific
> after the default environment is loaded. The match.of_compatible/
> directory is removed afterwards to keep /env clean.
>
> Example layout in CONFIG_DEFAULT_ENVIRONMENT_PATH:
>
> barebox-defaultenv/
> nv/boot.default
> match.of_compatible/
> fsl,imx8mm/
> nv/boot.default
> fsl,imx8mm-evk/
> nv/boot.default
>
> For compatible = "fsl,imx8mm-evk", "fsl,imx8mm":
> 1. fsl,imx8mm/ overlay applied first (most generic)
> 2. fsl,imx8mm-evk/ overlay applied second (most specific)
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
next prev parent reply other threads:[~2026-04-13 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 13:43 Ahmad Fatoum
2026-04-13 13:43 ` [PATCH v2 2/2] sandbox: add a match.of_compatible directory to exercise the feature Ahmad Fatoum
2026-04-13 14:22 ` Marco Felsch [this message]
2026-04-13 15:10 ` [PATCH v2 1/2] environment: support DT-compatible-specific overlays Sascha Hauer
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=swgwnzw2j6qsmqq7kbwlfawp4ay2u3wq3fpvyvyt76reyexfyq@2s7q2lqbqiup \
--to=m.felsch@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=a.fatoum@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