On Fri, Jul 04, 2025 at 10:48:26AM -0300, Fabio Estevam wrote: > Hi Tom, > > On Fri, Jul 4, 2025 at 10:31 AM Tom Rini <[email protected]> wrote: > > > If we correct the size limit for where the environment is today and > > switch to CONFIG_MULTI_DTB_FIT_LZO do we fit within the limits again? We > > Yes, changing to CONFIG_MULTI_DTB_FIT_LZO generates a u-boot.img of > 715488 bytes. > > This fits within the existing 715766 limit with a 278-byte margin, and > the board boots. > > After disabling RTEM and PLAN9, the binary goes to 715200. > > I can submit your suggested changes to fix the boot regression in > 2024.07, if you'd like. > > For 2024.10, we can discuss whether it is safe to use the current > CONFIG_ENV_OFFSET, as this is a topic that has haunted us from time to > time.
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. -- Tom
signature.asc
Description: PGP signature
