From: Tom Rini <trini@konsulko.com>
To: Sven Schwermer <sven@svenschwermer.de>
Cc: u-boot@lists.denx.de, Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Artem Lapkin <email2tema@gmail.com>,
Ramon Fried <rfried.dev@gmail.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v2 1/2] cmd: source: Use script from default config
Date: Tue, 18 Jan 2022 08:29:43 -0500 [thread overview]
Message-ID: <20220118132943.GA2928548@bill-the-cat> (raw)
In-Reply-To: <20220101184540.42491-1-sven@svenschwermer.de>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On Sat, Jan 01, 2022 at 07:45:39PM +0100, Sven Schwermer wrote:
> When sourcing FIT images, source the script node from the "bootscr"
> property within the default configuration. If
> board_fit_config_name_match is overridden, this will determine the
> selected configuration rather than the default one.
>
> The old behaviour is inconsistent with the FIT image specification which
> does not mention a "default" property in the "/images" node.
>
> Signed-off-by: Sven Schwermer <sven@svenschwermer.de>
This ends up being a noticeable size growth on a large number of
platforms. Can you please elaborate on the use case here, with some
links to the OE layers in question that generate these images? Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-18 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 18:45 [PATCH v2 1/2] cmd: source: Use script from default config Sven Schwermer
2022-01-01 18:45 ` [PATCH v2 2/2] f_sdp: Retry sourcing default FIT script Sven Schwermer
2022-01-18 13:29 ` Tom Rini [this message]
2022-01-22 20:36 ` [PATCH v2 1/2] cmd: source: Use script from default config Sven Schwermer
2022-01-24 18:08 ` Tom Rini
2022-01-24 20:31 ` Sven Schwermer
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=20220118132943.GA2928548@bill-the-cat \
--to=trini@konsulko.com \
--cc=email2tema@gmail.com \
--cc=mr.nuke.me@gmail.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=sven@svenschwermer.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox