On Fri, Jul 04, 2025 at 11:11:34AM -0300, Fabio Estevam wrote: > On Fri, Jul 4, 2025 at 10:53 AM Tom Rini <[email protected]> wrote: > > > Yes please, thanks! And I would like to explore a little if some other > > compression algorithm (that we don't have support for yet) might be a > > larger win too, for v2025.10. > > Ah, I manually tried this change below: > > --- a/configs/mx6sabresd_defconfig > +++ b/configs/mx6sabresd_defconfig > @@ -40,6 +40,8 @@ CONFIG_SPL_WATCHDOG=y > CONFIG_HUSH_PARSER=y > CONFIG_SYS_MAXARGS=32 > CONFIG_CMD_BOOTZ=y > +# CONFIG_BOOTM_PLAN9 is not set > +# CONFIG_BOOTM_RTEMS is not set > CONFIG_CMD_SPL=y > CONFIG_CMD_SPL_WRITE_SIZE=0x20000 > CONFIG_CMD_GPIO=y > @@ -65,7 +67,7 @@ CONFIG_EFI_PARTITION=y > # CONFIG_SPL_EFI_PARTITION is not set > CONFIG_OF_CONTROL=y > CONFIG_OF_LIST="imx6q-sabresd imx6qp-sabresd imx6dl-sabresd" > -CONFIG_MULTI_DTB_FIT=y > +CONFIG_MULTI_DTB_FIT_LZO=y > CONFIG_ENV_OVERWRITE=y > CONFIG_ENV_IS_IN_MMC=y > CONFIG_SYS_RELOC_GD_ENV_ADDR=y > > After running make savedefconfig; cp defconfig > configs/mx6sabresd_defconfig, I see that CONFIG_MULTI_DTB_FIT_LZO does > not get selected, and CONFIG_MULTI_DTB_FIT=y is removed. > > According to doc/README.multi-dtb-fit: > > "Usually the DTB is selected by the SPL and passed down to U-Boot. But some > platforms don't use the SPL. In this case MULTI_DTB_FIT can used to provide > U-Boot with a choice of DTBs" > > mx6sabresd uses SPL, so MULTI_DTB_FIT can be safely dropped. > > I tested it on a imx6dl and imx6q sabresd boards. > > I'll send a v2.
I guess the question is if we need to be using SPL_MULTI_FIT_DTB to pass the right one along, or if we don't really need to have the exact DTB in any case? -- Tom
signature.asc
Description: PGP signature
