From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: mkimage_fit_atf: Fix DTC warnings
Date: Tue, 7 May 2019 12:44:57 -0300 [thread overview]
Message-ID: <20190507154457.7578-1-festevam@gmail.com> (raw)
When generating the flash.bin binary the following DTC warnings
are seen:
u-boot.itb.tmp: Warning (unit_address_vs_reg): Node /images/uboot at 1 has a unit name, but no reg property
u-boot.itb.tmp: Warning (unit_address_vs_reg): Node /images/atf at 1 has a unit name, but no reg property
u-boot.itb.tmp: Warning (unit_address_vs_reg): Node /images/fdt at 1 has a unit name, but no reg property
u-boot.itb.tmp: Warning (unit_address_vs_reg): Node /configurations/config at 1 has a unit name, but no reg property
Fix them by removing the meaningless @1 entries.
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
arch/arm/mach-imx/mkimage_fit_atf.sh | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/arch/arm/mach-imx/mkimage_fit_atf.sh b/arch/arm/mach-imx/mkimage_fit_atf.sh
index 38c9858e84..fc9342543a 100755
--- a/arch/arm/mach-imx/mkimage_fit_atf.sh
+++ b/arch/arm/mach-imx/mkimage_fit_atf.sh
@@ -53,7 +53,7 @@ cat << __HEADER_EOF
description = "Configuration to load ATF before U-Boot";
images {
- uboot@1 {
+ uboot {
description = "U-Boot (64-bit)";
data = /incbin/("$BL33");
type = "standalone";
@@ -61,7 +61,7 @@ cat << __HEADER_EOF
compression = "none";
load = <$BL33_LOAD_ADDR>;
};
- atf at 1 {
+ atf {
description = "ARM Trusted Firmware";
data = /incbin/("$BL31");
type = "firmware";
@@ -74,7 +74,7 @@ __HEADER_EOF
if [ -f $BL32 ]; then
cat << __HEADER_EOF
- tee at 1 {
+ tee {
description = "TEE firmware";
data = /incbin/("$BL32");
type = "firmware";
@@ -90,7 +90,7 @@ cnt=1
for dtname in $*
do
cat << __FDT_IMAGE_EOF
- fdt@$cnt {
+ fdt {
description = "$(basename $dtname .dtb)";
data = /incbin/("$dtname");
type = "flat_dt";
@@ -103,7 +103,7 @@ done
cat << __CONF_HEADER_EOF
};
configurations {
- default = "config at 1";
+ default = "config";
__CONF_HEADER_EOF
@@ -112,20 +112,20 @@ for dtname in $*
do
if [ -f $BL32 ]; then
cat << __CONF_SECTION_EOF
- config@$cnt {
+ config {
description = "$(basename $dtname .dtb)";
- firmware = "uboot at 1";
- loadables = "atf at 1", "tee at 1";
- fdt = "fdt@$cnt";
+ firmware = "uboot";
+ loadables = "atf", "tee";
+ fdt = "fdt";
};
__CONF_SECTION_EOF
else
cat << __CONF_SECTION1_EOF
- config@$cnt {
+ config {
description = "$(basename $dtname .dtb)";
- firmware = "uboot at 1";
- loadables = "atf@1";
- fdt = "fdt@$cnt";
+ firmware = "uboot";
+ loadables = "atf";
+ fdt = "fdt";
};
__CONF_SECTION1_EOF
fi
--
2.17.1
next reply other threads:[~2019-05-07 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 15:44 Fabio Estevam [this message]
2019-05-08 1:24 ` [U-Boot] [PATCH] imx: mkimage_fit_atf: Fix DTC warnings Peng Fan
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=20190507154457.7578-1-festevam@gmail.com \
--to=festevam@gmail.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