From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] add pattern based copy for ATF as already used for u-boot. This add support for different platforms where the binaries have different extension
Date: Mon, 11 Nov 2019 11:51:18 +0300 [thread overview]
Message-ID: <20191111085118.5ymswhzmvkpdkwit@bars> (raw)
In-Reply-To: <1573221183-25905-1-git-send-email-michael.schenk@noser.com>
> Signed-off-by: Michael Schenk <michael.schenk@noser.com>
> ---
> boot/arm-trusted-firmware/Config.in | 7 +++++++
> boot/arm-trusted-firmware/arm-trusted-firmware.mk | 4 +++-
> 2 files changed, 10 insertions(+), 1 deletion(-)
...
> define ARM_TRUSTED_FIRMWARE_INSTALL_IMAGES_CMDS
> - cp -dpf $(ARM_TRUSTED_FIRMWARE_IMG_DIR)/*.bin $(BINARIES_DIR)/
> + $(foreach f,$(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES)), \
> + cp -dpf $(ARM_TRUSTED_FIRMWARE_IMG_DIR)/$(f) $(BINARIES_DIR)/
> + )
> $(ARM_TRUSTED_FIRMWARE_BL31_UBOOT_INSTALL)
> $(ARM_TRUSTED_FIRMWARE_BL31_UBOOT_INSTALL_ELF)
> endef
Looks good to me: Reviewed-by: Sergey Matyukevich <geomatsi@gmail.com>
For better understanding of the rationale behind the change, it would
be great if you could share some technical details of your use-case.
Regards,
Sergey
next parent reply other threads:[~2019-11-11 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1573221183-25905-1-git-send-email-michael.schenk@noser.com>
2019-11-11 8:51 ` Sergey Matyukevich [this message]
[not found] ` <DB7PR04MB500309181A711B70FEB5B58181740@DB7PR04MB5003.eurprd04.prod.outlook.com>
2019-11-12 20:17 ` [Buildroot] [PATCH 1/1] add pattern based copy for ATF as already used for u-boot. This add support for different platforms where the binaries have different extension Sergey Matyukevich
2019-11-12 20:26 ` Thomas Petazzoni
2019-11-14 13:29 Schenk Michael
2019-11-15 7:29 ` Sergey Matyukevich
2019-11-15 7:36 ` Yegor Yefremov
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=20191111085118.5ymswhzmvkpdkwit@bars \
--to=geomatsi@gmail.com \
--cc=buildroot@busybox.net \
/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.