boot: Reorder FIT and BOOTSTD to be first

The boot menu shows Android first and then a timestamp option. Move
these later since they are less commonly used.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass 2023-12-14 21:18:59 -07:00 committed by Tom Rini
parent 6b8f26bca4
commit 52b3c47d7c

View File

@ -2,24 +2,6 @@ menu "Boot options"
menu "Boot images"
config ANDROID_BOOT_IMAGE
bool "Android Boot Images"
default y if FASTBOOT
help
This enables support for booting images which use the Android
image format header.
config TIMESTAMP
bool "Show image date and time when displaying image information"
default y if CMD_DATE
help
When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
an image is printed by image commands like bootm or iminfo. This
is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
loaded that does not, the message 'Wrong FIT format: no timestamp'
is shown.
menuconfig FIT
bool "Flattened Image Tree (FIT)"
select HASH
@ -695,6 +677,24 @@ config BOOTMETH_SCRIPT
endif # BOOTSTD
config ANDROID_BOOT_IMAGE
bool "Android Boot Images"
default y if FASTBOOT
help
This enables support for booting images which use the Android
image format header.
config TIMESTAMP
bool "Show image date and time when displaying image information"
default y if CMD_DATE
help
When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
an image is printed by image commands like bootm or iminfo. This
is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
loaded that does not, the message 'Wrong FIT format: no timestamp'
is shown.
config LEGACY_IMAGE_FORMAT
bool "Enable support for the legacy image format"
default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE