Hi Tom,
On Wed, 12 Apr 2023 at 17:03, Simon Glass sjg@chromium.org wrote:
Hi Tom,
On Sun, 9 Apr 2023 at 18:07, Tom Rini trini@konsulko.com wrote:
On Sun, Apr 09, 2023 at 08:18:31AM +1200, Simon Glass wrote:
Hi Tom,
[..]
Because that's the key here, on the 564 platforms that use distro_bootcmd today, there shouldn't be any growth when we switch to bootstd, and there's even more platforms that enable CONFIG_DISTRO_DEFAULTS than there are that use distro_bootcmd so the cases like xilinx mini should be the exception, not the rule. And that's what I keep circling back to. The logic to keep the defaults that generic distro support needs are (almost) always already set on the platforms that are using generic distro boot, so we shouldn't grow in size when bootstd turns it on. And if I'm changing my mind about forcing this on, on platforms that hadn't been doing generic distro before, I guess I'm changing my mind, sorry, there's too many platforms that are doing other things (not generic distro or Android or Special Things).
Yes I agree there should be no size growth for platforms which use distro_bootcmd today and move to bootstd. That is easy enough to check as part of migration. For the rpi and rockchip series the size reduces from where we are today by 1-12KB.
It shouldn't change it at all tho, let alone reduce? Why is it reducing?
Just on this point, which I missed, dropping the scripts in the environment reduces the size by 4-5KB depending on the board. Dropping hush can reduce by quite a lot. Standard boot does not need scripts or hush.
Regards, Simon