On Thu, Mar 30, 2023 at 10:17:22PM +1300, Simon Glass wrote:
Hi Nicolas,
On Wed, 29 Mar 2023 at 20:55, Nicolas Ferre nicolas.ferre@microchip.com wrote:
Hi Simon,
On 29/03/2023 at 09:16, Simon Glass wrote:
This is needed to enable the boot command used to start standard boot. Enable it by default. This brings in quite a few features, mostly in common with DISTRO_DEFAULTS
Disable this option for boards which don't have enough space.
What is the identified minimal space for benefiting from this feature?
Well some boards have a limit on the size of U-Boot. The defaults enables lots of things, including ext and fat filesystems, partition types, booti/z for ARM, etc.
I have not locked at what a minimal board requires. But if you know what you are doing, you could drop BOOT_DEFAULTS and BOOTSTD_DEFAULTS or DISTRO_DEFAULTS and manually enable just what you need.
Disable CONFIG_ENV_VARS_UBOOT_CONFIG for some Xilinx boards which have a very small environment. Disable BOOTSTD_DEFAULTS for smartweb since it is too close to its limit.
I see that a few Microchip boards are in this case too and even if sama5d27 som1 ek might be impacted, I would like to double check for the other sama5d2 boards.
OK, sure. The really big thing is booting EFI images - CONFIG_EFI_LOADER. It adds over 100KB I think.
These are examples of platforms I was talking about. They do not use distro boot today, and have a real bootcmd defined. They should just get bootstd turned off now until someone is interested in seeing how bootstd would be used here.