Our bootcmd is the same regardless of where the SoC loaded it's code from, so we don't want fsl_setenv_bootcmd to do anything.
Signed-off-by: Mathew McBride <m...@traverse.com.au> --- board/traverse/ten64/ten64.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/board/traverse/ten64/ten64.c b/board/traverse/ten64/ten64.c index 17057966c8..3cb8bad855 100644 --- a/board/traverse/ten64/ten64.c +++ b/board/traverse/ten64/ten64.c @@ -465,3 +465,12 @@ static void ten64_board_retimer_ds110df410_init(void) puts("OK\n"); } +/* Opt out of the fsl_setenv_bootcmd + * in arch/arm/cpu/armv8/fsl-layerscape/soc.c + * which is invoked by board_late_init. + */ +int fsl_setenv_bootcmd(void) +{ + return 0; +} + -- 2.30.1