Hi Tom, On Wed, 3 Jul 2024 at 22:23, Tom Rini <tr...@konsulko.com> wrote: > > A valid memory location to stash bootstage information at will be > architecture dependent. Move the existing defaults to the main Kconfig > file for this option and set 0x0 as the default only for sandbox. > > Signed-off-by: Tom Rini <tr...@konsulko.com> > --- > Cc: Simon Glass <s...@chromium.org> > --- > arch/arm/mach-stm32mp/Kconfig.13x | 3 --- > arch/arm/mach-stm32mp/Kconfig.15x | 3 --- > arch/arm/mach-stm32mp/Kconfig.25x | 3 --- > boot/Kconfig | 4 +++- > 4 files changed, 3 insertions(+), 10 deletions(-)
Reviewed-by: Simon Glass <s...@chromium.org> But from my previous investigations, having no default for a hex option can cause the build to hang unless the user is presentt, since the build keeps asking for the value. I added support in buildman to try to detect this, so we'll see how it goes. Regards, Simon
