u-boot.git/boot/Kconfig, branch v2023.04

boot: Create a common BOOT_DEFAULTS for distro and bootstd

2023-03-27T15:16:04Z

These two features use a lot of common options. Move them into a common CONFIG to reduce duplication. Use 'select' for most options since these are things that boards aren't supposed to override. For now it is not possible to disable BOOT_DEFAULTS but we may take another look later. Note that five options use 'imply' to match existing behaviour. Signed-off-by: Simon Glass [trini: Rework a bit so we don't grow so many platforms unintentionally] Signed-off-by: Tom Rini

lmb: Enable LMB if SYS_BOOT_RAMDISK_HIGH

2023-03-27T15:16:04Z

Ramdisk relocation requires LMB, so enable it automatically to avoid build errors. Signed-off-by: Simon Glass

Move DISTRO_DEFAULTS into boot/

2023-03-27T15:16:04Z

This relates to booting so move it in to that Kconfig file, before changing it. Signed-off-by: Simon Glass

bootstd: Add some default filesystems and commands

2023-02-06T18:04:53Z

We need to support a basic set of filesystems for booting to work in most cases. Add these in via a new option, letting the board disable them individually (for space reasons) if desired. This enables the filesystem commands as well as the actual functionality, even though bootstd is quite happy to use ext4 without the ext4 command. Further work would be needed to disintangle this and reduce code size. Add several other options as well, providing sensible defaults. We cannot enable this by default, since it expands the size of many boards quite a lot. Signed-off-by: Simon Glass

bootstd: Allow enabling BOOTSTD_FULL without needing EXPO

2023-02-06T18:04:53Z

It is sometimes useful to have one without the other, e.g. on a device without a display, since at present the expo feature requires CONFIG_VIDEO to be enabled. Update the Makefile and bootflow command to support this, as well as the EXPO dependency. Signed-off-by: Simon Glass

Merge tag 'dm-pull-18jan23' of https://source.denx.de/u-boot/custodians/u-boot-dm

2023-01-19T14:46:57Z

convert rockchip to use binman patman fix for checkpatch binman optional entries, improved support for ELF symbols trace improvements minor fdt refactoring

rockchip: Drop the FIT generator script

2023-01-18T21:55:40Z

This is not used anymore. Drop it. Signed-off-by: Simon Glass

rockchip: Convert all boards to use binman

2023-01-18T21:55:40Z

Instead of the bash script, use binman to generate the FIT for arm64. For 32-bit boards, use binman for all images, dropping the intermediate files. With this change, only Zynq is now using SPL_FIT_GENERATOR so update the Kconfig rule accordingly. Clean up the Makefile to the extent possible. Unfortunately, two boards do not use SPL_FRAMEWORK so don't enable the u-boot.img rule: evb-rk3036 kylin-rk3036 So a small remnant remains. Signed-off-by: Simon Glass

event: Correct dependencies on the EVENT framework

2023-01-18T17:46:13Z

The event framework is just that, a framework. Enabling it by itself does nothing, so we shouldn't ask the user about it. Reword (and correct typos) around this the option and help text. This also applies to DM_EVENT and EVENT_DYNAMIC. Only EVENT_DEBUG and CMD_EVENT should be visible to the user to select, when EVENT is selected. With this, it's time to address the larger problems. When functionality uses events, typically via EVENT_SPY, the appropriate framework then must be select'd and NOT imply'd. As the functionality will cease to work (and so, platforms will fail to boot) this is non-optional and where select is appropriate. Audit the current users of EVENT_SPY to have a more fine-grained approach to select'ing the framework where used. Also ensure the current users of event_register and also select EVENT_DYNAMIC. Cc: AKASHI Takahiro Cc: Heinrich Schuchardt Reported-by: Oliver Graute Reported-by: Francesco Dolcini Fixes: 7fe32b3442f0 ("event: Convert arch_cpu_init_dm() to use events") Fixes: 42fdcebf859f ("event: Convert misc_init_f() to use events") Fixes: c5ef2025579e ("dm: fix DM_EVENT dependencies") Signed-off-by: Tom Rini Tested-by: Simon Glass Reviewed-by: Simon Glass Reviewed-by: Fabio Estevam

expo: Add basic implementation

2023-01-16T23:26:50Z

An expo is a way of presenting and collecting information from the user. It consists of a collection of 'scenes' of which only one is presented at a time. An expo is typically used to show a boot menu and allow settings to be changed. One created, the same expo can be automatically presented in graphical form using a vidconsole, or in text form on a serial console. Add an initial implementation of the expo itself. Supports for scenes and objects is provided later. Signed-off-by: Simon Glass