From: Dhruva Gole <d-g...@ti.com>

findfdt is the legacy approach to find fdt and platforms have moved away
from this and don't define this anymore. This causes an error that may
seem alarming but is harmless. Remove it from the bootcmd_ti_mmc to
avoid any panic and confusion.

Signed-off-by: Dhruva Gole <d-g...@ti.com>
Signed-off-by: Manorit Chawdhry <m-chawd...@ti.com>
---
 include/env/ti/ti_common.env | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/env/ti/ti_common.env b/include/env/ti/ti_common.env
index c5c36421770c..7029d12bf203 100644
--- a/include/env/ti/ti_common.env
+++ b/include/env/ti/ti_common.env
@@ -25,7 +25,7 @@ get_fit_config=setexpr name_fit_config gsub / _ 
conf-${fdtfile}
 run_fit=run get_fit_config; bootm 
${addr_fit}#${name_fit_config}${overlaystring}
 do_main_cpsw0_qsgmii_phyinit=0
 bootcmd_ti_mmc=
-       run findfdt; run init_${boot};
+       run init_${boot};
 #if CONFIG_CMD_REMOTEPROC
        if test ${do_main_cpsw0_qsgmii_phyinit} -eq 1;
                then run main_cpsw0_qsgmii_phyinit;

-- 
2.45.1

Reply via email to