From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v6 2/6] Makefile: rockchip: Suffix platform type with tpl name
Date: Sat, 4 Jan 2020 14:08:02 +0530 [thread overview]
Message-ID: <20200104083806.3930-3-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20200104083806.3930-1-jagan@amarulasolutions.com>
Most of the platforms uses the platform type on their boot
stage image naming conventions in makefile like,
u-boot-x86-start16-tpl.bin - x86 start16 TPL bin
u-boot-spl-mtk.bin - Mediatek SPL bin
This would help to understand the users to what that
particular image belongs to? and less confused.
On that note, suffix platform type rockchip for existing
u-boot-tpl.img so now it become u-boot-tpl-rockchip.bin
Also, bin is more conventional way to include it on tools
like binman, pad_cat etc in future patches.
Note: usage of platform type doesn't follow consistent order
as of now.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
---
Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 9998d238f3..e519103be4 100644
--- a/Makefile
+++ b/Makefile
@@ -1382,10 +1382,10 @@ else
ROCKCHIP_IMG_TYPE := rksd
endif
-MKIMAGEFLAGS_u-boot-tpl.img = -n $(CONFIG_SYS_SOC) -T $(ROCKCHIP_IMG_TYPE)
-tpl/u-boot-tpl.img: tpl/u-boot-tpl.bin FORCE
+MKIMAGEFLAGS_u-boot-tpl-rockchip.bin = -n $(CONFIG_SYS_SOC) -T $(ROCKCHIP_IMG_TYPE)
+tpl/u-boot-tpl-rockchip.bin: tpl/u-boot-tpl.bin FORCE
$(call if_changed,mkimage)
-idbloader.img: tpl/u-boot-tpl.img spl/u-boot-spl.bin FORCE
+idbloader.img: tpl/u-boot-tpl-rockchip.bin spl/u-boot-spl.bin FORCE
$(call if_changed,cat)
endif
--
2.18.0.321.gffc6fa0e3
next prev parent reply other threads:[~2020-01-04 8:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 8:38 [PATCH v6 0/6] rockchip: Add Binman support Jagan Teki
2020-01-04 8:38 ` [PATCH v6 1/6] Makefile: Add rockchip image type Jagan Teki
2020-01-04 8:38 ` Jagan Teki [this message]
2020-01-04 8:38 ` [PATCH v6 3/6] Makefile: rockchip: Support SPL-alone mkimage Jagan Teki
2020-01-04 8:38 ` [PATCH v6 4/6] arm: dts: rk3036: Add rk3036-u-boot.dtsi Jagan Teki
2020-01-04 8:38 ` [PATCH v6 5/6] rockchip: Add Single boot image (with binman, pad_cat) Jagan Teki
2020-01-07 9:47 ` [PATCH v6 5/6] rockchip: Add Single boot image (with binman, pad_cat)【请注意，邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2020-01-10 9:39 ` [PATCH v6 5/6] rockchip: Add Single boot image (with binman, pad_cat) Simon Glass
2020-01-10 9:42 ` Matwey V. Kornilov
2020-01-30 2:17 ` Simon Glass
2020-01-04 8:38 ` [PATCH v6 6/6] doc: boards: Add rockchip documentation Jagan Teki
2020-01-07 8:40 ` Kever Yang
2020-01-07 9:59 ` [PATCH v6 0/6] rockchip: Add Binman support Kever Yang
2020-01-08 11:34 ` Wadim Egorov
2020-01-08 11:55 ` Jagan Teki
2020-01-09 13:59 ` Jagan Teki
2020-01-09 15:28 ` Wadim Egorov
2020-01-09 18:47 ` Jagan Teki
2020-01-10 9:39 ` Simon Glass
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=20200104083806.3930-3-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--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