On 8/28/25 23:09, Hal Feng wrote: > So the VisionFive 2 Lite DT will be built and merged into FIT. > > Signed-off-by: Hal Feng <hal.f...@starfivetech.com> > --- > configs/starfive_visionfive2_defconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configs/starfive_visionfive2_defconfig > b/configs/starfive_visionfive2_defconfig > index 544140c03f7..5a0e918c733 100644 > --- a/configs/starfive_visionfive2_defconfig > +++ b/configs/starfive_visionfive2_defconfig > @@ -78,7 +78,7 @@ CONFIG_CMD_WDT=y > CONFIG_CMD_WGET=y > CONFIG_CMD_BOOTSTAGE=y > CONFIG_OF_BOARD=y > -CONFIG_OF_LIST="starfive/jh7110-deepcomputing-fml13v01 > starfive/jh7110-milkv-mars starfive/jh7110-pine64-star64 > starfive/jh7110-starfive-visionfive-2-v1.2a > starfive/jh7110-starfive-visionfive-2-v1.3b" > +CONFIG_OF_LIST="starfive/jh7110-deepcomputing-fml13v01 > starfive/jh7110-milkv-mars starfive/jh7110-pine64-star64 > starfive/jh7110-starfive-visionfive-2-v1.2a > starfive/jh7110-starfive-visionfive-2-v1.3b > starfive/jh7110s-starfive-visionfive-2-lite" > CONFIG_MULTI_DTB_FIT=y > CONFIG_ENV_OVERWRITE=y > CONFIG_ENV_IS_IN_SPI_FLASH=y
Okay. While we are adding a target with a different (yet similar) CPU JH7110S, I have questions about if we can also make JH7100 a variant here too. How much difference is allowed for one U-Boot board target? It would be great to have a single U-Boot target starfive_jh71xx_defconfig for example. I am aware that mainline Linux kernel defconfig can boot on JH7100 but some peripheral drivers do not work correctly, and so there is a requirement to compile Linux kernel as non-portable [1]. However I want to know what prevents U-Boot from supporting all of JH7100, JH7110, JH7110S, with the same build target? 1: https://wiki.debian.org/InstallingDebianOn/StarFive/VisionFiveV1 Anyways, this change to CONFIG_OF_LIST is sorted correctly and looks good to me. Reviewed-by: E Shattow <e...@freeshell.de>
