Hi Tom, On 2023-03-24 21:58, Tom Rini wrote: > The defined altbootcmd was specific to distro_bootcmd which is not > longer in use on these platforms, so drop it. > > Signed-off-by: Tom Rini <tr...@konsulko.com> > --- > Changes in v4: > - New patch > > Cc: Kever Yang <kever.y...@rock-chips.com> > Cc: Simon Glass <s...@chromium.org> > Cc: Jonas Karlman <jo...@kwiboo.se> > --- > include/configs/rk3399_common.h | 5 +---- > 1 file changed, 1 insertion(+), 4 deletions(-) > > diff --git a/include/configs/rk3399_common.h b/include/configs/rk3399_common.h > index 04dcbf20bcb5..96ba19c659bd 100644 > --- a/include/configs/rk3399_common.h > +++ b/include/configs/rk3399_common.h > @@ -52,10 +52,7 @@ > "fdtfile=" CONFIG_DEFAULT_FDT_FILE "\0" \ > "partitions=" PARTS_DEFAULT \ > ROCKCHIP_DEVICE_SETTINGS \ > - "boot_targets=" BOOT_TARGETS "\0" \ > - "altbootcmd=" \ > - "setenv boot_syslinux_conf extlinux/extlinux-rollback.conf;" \ > - "run distro_bootcmd\0" > + "boot_targets=" BOOT_TARGETS "\0" > > #endif >
With this series my rk3399 boards stop trying to use distro_bootcmd and will now successfully boot using default bootcmd=bootflow scan. So for the entire series: Tested-by: Jonas Karlman <jo...@kwiboo.se> Reviewed-by: Jonas Karlman <jo...@kwiboo.se> Regards, Jonas
