From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/3] u-boot: Move image copying from targetinstall to install.
Date: Tue, 30 Aug 2022 09:25:10 +0200 [thread overview]
Message-ID: <Yw27Vg5SOvIdog9M@pengutronix.de> (raw)
In-Reply-To: <20220826133537.1843791-3-christian.melki@t2data.com>
On Fri, Aug 26, 2022 at 03:35:37PM +0200, Christian Melki wrote:
> This seems like a potential issue in several packages.
> When signing u-boot images in tf-a, tf-a has u-boot as
> a dependency. But u-boot doesn't install images to be processed
> until targetinstall, which leads to problems.
>
> Some things might be targetinstall. But resulting images destined
> for the imagedir aren't really targetinstall unless
> they are also copied to rootfs.
This is broken. 'ptxdist clean root' will remove the files from images/ and
then only targetinstall is executed. So the files won't be copied again.
If other packages need those files, then they must be copied to
$(U_BOOT_PKGDIR) in the install stage.
Michael
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> rules/u-boot.make | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/rules/u-boot.make b/rules/u-boot.make
> index 0b632e8b2..bdbe03ffe 100644
> --- a/rules/u-boot.make
> +++ b/rules/u-boot.make
> @@ -133,14 +133,7 @@ endif
>
> $(STATEDIR)/u-boot.install:
> @$(call targetinfo)
> - @$(call touch)
> -
> -# ----------------------------------------------------------------------------
> -# Target-Install
> -# ----------------------------------------------------------------------------
>
> -$(STATEDIR)/u-boot.targetinstall:
> - @$(call targetinfo)
> @$(call world/image-clean, U_BOOT)
> ifdef PTXCONF_U_BOOT_INSTALL_U_BOOT_BIN
> @$(call ptx/image-install, U_BOOT, $(U_BOOT_BUILD_DIR)/u-boot.bin)
> @@ -194,6 +187,14 @@ ifndef PTXCONF_U_BOOT_ENV_IMAGE_NONE
> @$(call ptx/image-install, U_BOOT, $(U_BOOT_BUILD_DIR)/u-boot-env.img)
> endif
>
> + @$(call touch)
> +
> +# ----------------------------------------------------------------------------
> +# Target-Install
> +# ----------------------------------------------------------------------------
> +
> +$(STATEDIR)/u-boot.targetinstall:
> + @$(call targetinfo)
> ifdef PTXCONF_U_BOOT_BOOT_SCRIPT
> @$(call install_init, u-boot)
> @$(call install_fixup, u-boot, PRIORITY, optional)
> --
> 2.34.1
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-08-30 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 13:35 [ptxdist] [PATCH 1/3] u-boot: Move u-boot URL to github Christian Melki
2022-08-26 13:35 ` [ptxdist] [PATCH 2/3] u-boot: Add two new u-boot image targets Christian Melki
2022-08-26 13:35 ` [ptxdist] [PATCH 3/3] u-boot: Move image copying from targetinstall to install Christian Melki
2022-08-30 7:25 ` Michael Olbrich [this message]
2022-08-30 7:41 ` Christian Melki
2022-08-29 8:49 ` [ptxdist] [PATCH 1/3] u-boot: Move u-boot URL to github Alexander Dahl
2022-08-29 16:57 ` Christian Melki
2022-08-30 7:23 ` Michael Olbrich
2022-08-30 7:58 ` Christian Melki
2022-08-30 9:13 ` Alexander Dahl
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=Yw27Vg5SOvIdog9M@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.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