boot/Kconfig

   1 menu "Boot options"
   2
   3 menu "Boot images"
   4
   5 config ANDROID_BOOT_IMAGE
   6         bool "Android Boot Images"
   7         default y if FASTBOOT
   8         help
   9           This enables support for booting images which use the Android
  10           image format header.
  11
  12 config TIMESTAMP
  13         bool "Show image date and time when displaying image information"
  14         default y if CMD_DATE
  15         help
  16           When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
  17           an image is printed by image commands like bootm or iminfo. This
  18           is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
  19           enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
  20           loaded that does not, the message 'Wrong FIT format: no timestamp'
  21           is shown.
  22
  23 menuconfig FIT
  24         bool "Flattened Image Tree (FIT)"
  25         select HASH
  26         select MD5
  27         select SHA1
  28         imply SHA256
  29         help
  30           This option allows you to boot the new uImage structure,
  31           Flattened Image Tree.  FIT is formally a FDT, which can include
  32           images of various types (kernel, FDT blob, ramdisk, etc.)
  33           in a single blob.  To boot this new uImage structure,
  34           pass the address of the blob to the "bootm" command.
  35           FIT is very flexible, supporting compression, multiple images,
  36           multiple configurations, verification through hashing and also
  37           verified boot (secure boot using RSA).
  38
  39 if FIT
  40
  41 config FIT_EXTERNAL_OFFSET
  42         hex "FIT external data offset"
  43         default 0x0
  44         help
  45           This specifies a data offset in fit image.
  46           The offset is from data payload offset to the beginning of
  47           fit image header. When specifies a offset, specific data
  48           could be put in the hole between data payload and fit image
  49           header, such as CSF data on i.MX platform.
  50
  51 config FIT_FULL_CHECK
  52         bool "Do a full check of the FIT before using it"
  53         default y
  54         help
  55           Enable this do a full check of the FIT to make sure it is valid. This
  56           helps to protect against carefully crafted FITs which take advantage
  57           of bugs or omissions in the code. This includes a bad structure,
  58           multiple root nodes and the like.
  59
  60 config FIT_SIGNATURE
  61         bool "Enable signature verification of FIT uImages"
  62         depends on DM
  63         select HASH
  64         imply RSA
  65         imply RSA_VERIFY
  66         select IMAGE_SIGN_INFO
  67         select FIT_FULL_CHECK
  68         help
  69           This option enables signature verification of FIT uImages,
  70           using a hash signed and verified using RSA. If
  71           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  72           hashing is available using hardware, then the RSA library will use
  73           it. See doc/uImage.FIT/signature.txt for more details.
  74
  75           WARNING: When relying on signed FIT images with a required signature
  76           check the legacy image format is disabled by default, so that
  77           unsigned images cannot be loaded. If a board needs the legacy image
  78           format support in this case, enable it using
  79           CONFIG_LEGACY_IMAGE_FORMAT.
  80
  81 config FIT_SIGNATURE_MAX_SIZE
  82         hex "Max size of signed FIT structures"
  83         depends on FIT_SIGNATURE
  84         default 0x10000000
  85         help
  86           This option sets a max size in bytes for verified FIT uImages.
  87           A sane value of 256MB protects corrupted DTB structures from overlapping
  88           device memory. Assure this size does not extend past expected storage
  89           space.
  90
  91 config FIT_RSASSA_PSS
  92         bool "Support rsassa-pss signature scheme of FIT image contents"
  93         depends on FIT_SIGNATURE
  94         help
  95           Enable this to support the pss padding algorithm as described
  96           in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  97
  98 config FIT_CIPHER
  99         bool "Enable ciphering data in a FIT uImages"
 100         depends on DM
 101         select AES
 102         help
 103           Enable the feature of data ciphering/unciphering in the tool mkimage
 104           and in the u-boot support of the FIT image.
 105
 106 config FIT_VERBOSE
 107         bool "Show verbose messages when FIT images fail"
 108         help
 109           Generally a system will have valid FIT images so debug messages
 110           are a waste of code space. If you are debugging your images then
 111           you can enable this option to get more verbose information about
 112           failures.
 113
 114 config FIT_BEST_MATCH
 115         bool "Select the best match for the kernel device tree"
 116         help
 117           When no configuration is explicitly selected, default to the
 118           one whose fdt's compatibility field best matches that of
 119           U-Boot itself. A match is considered "best" if it matches the
 120           most specific compatibility entry of U-Boot's fdt's root node.
 121           The order of entries in the configuration's fdt is ignored.
 122
 123 config FIT_IMAGE_POST_PROCESS
 124         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 125         depends on SOCFPGA_SECURE_VAB_AUTH
 126         help
 127           Allows doing any sort of manipulation to blobs after they got extracted
 128           from FIT images like stripping off headers or modifying the size of the
 129           blob, verification, authentication, decryption etc. in a platform or
 130           board specific way. In order to use this feature a platform or board-
 131           specific implementation of board_fit_image_post_process() must be
 132           provided. Also, anything done during this post-processing step would
 133           need to be comprehended in how the images were prepared before being
 134           injected into the FIT creation (i.e. the blobs would have been pre-
 135           processed before being added to the FIT image).
 136
 137 config FIT_PRINT
 138         bool "Support FIT printing"
 139         default y
 140         help
 141           Support printing the content of the fitImage in a verbose manner.
 142
 143 config SPL_FIT
 144         bool "Support Flattened Image Tree within SPL"
 145         depends on SPL
 146         select SPL_HASH
 147         select SPL_OF_LIBFDT
 148
 149 config SPL_FIT_PRINT
 150         bool "Support FIT printing within SPL"
 151         depends on SPL_FIT
 152         help
 153           Support printing the content of the fitImage in a verbose manner in SPL.
 154
 155 config SPL_FIT_FULL_CHECK
 156         bool "Do a full check of the FIT before using it"
 157         depends on SPL_FIT
 158         help
 159           Enable this do a full check of the FIT to make sure it is valid. This
 160           helps to protect against carefully crafted FITs which take advantage
 161           of bugs or omissions in the code. This includes a bad structure,
 162           multiple root nodes and the like.
 163
 164 config SPL_FIT_SIGNATURE
 165         bool "Enable signature verification of FIT firmware within SPL"
 166         depends on SPL_DM
 167         depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
 168         select FIT_SIGNATURE
 169         select SPL_FIT
 170         select SPL_CRYPTO
 171         select SPL_HASH
 172         imply SPL_RSA
 173         imply SPL_RSA_VERIFY
 174         select SPL_IMAGE_SIGN_INFO
 175         select SPL_FIT_FULL_CHECK
 176
 177 config SPL_FIT_SIGNATURE_MAX_SIZE
 178         hex "Max size of signed FIT structures in SPL"
 179         depends on SPL_FIT_SIGNATURE
 180         default 0x10000000
 181         help
 182           This option sets a max size in bytes for verified FIT uImages.
 183           A sane value of 256MB protects corrupted DTB structures from overlapping
 184           device memory. Assure this size does not extend past expected storage
 185           space.
 186
 187 config SPL_FIT_RSASSA_PSS
 188         bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
 189         depends on SPL_FIT_SIGNATURE
 190         help
 191           Enable this to support the pss padding algorithm as described
 192           in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
 193
 194 config SPL_LOAD_FIT
 195         bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
 196         depends on SPL
 197         select SPL_FIT
 198         help
 199           Normally with the SPL framework a legacy image is generated as part
 200           of the build. This contains U-Boot along with information as to
 201           where it should be loaded. This option instead enables generation
 202           of a FIT (Flat Image Tree) which provides more flexibility. In
 203           particular it can handle selecting from multiple device tree
 204           and passing the correct one to U-Boot.
 205
 206           This path has the following limitations:
 207
 208           1. "loadables" images, other than FDTs, which do not have a "load"
 209              property will not be loaded. This limitation also applies to FPGA
 210              images with the correct "compatible" string.
 211           2. For FPGA images, the supported "compatible" list is in the
 212              doc/uImage.FIT/source_file_format.txt.
 213           3. FDTs are only loaded for images with an "os" property of "u-boot".
 214              "linux" images are also supported with Falcon boot mode.
 215
 216 config SPL_LOAD_FIT_ADDRESS
 217         hex "load address of fit image"
 218         depends on SPL_LOAD_FIT
 219         default 0x0
 220         help
 221           Specify the load address of the fit image that will be loaded
 222           by SPL.
 223
 224 config SPL_LOAD_FIT_APPLY_OVERLAY
 225         bool "Enable SPL applying DT overlays from FIT"
 226         depends on SPL_LOAD_FIT
 227         select OF_LIBFDT_OVERLAY
 228         help
 229           The device tree is loaded from the FIT image. Allow the SPL to
 230           also load device-tree overlays from the FIT image an apply them
 231           over the device tree.
 232
 233 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
 234         depends on SPL_LOAD_FIT_APPLY_OVERLAY
 235         default 0x10000
 236         hex "size of temporary buffer used to load the overlays"
 237         help
 238           The size of the area where the overlays will be loaded and
 239           uncompress. Must be at least as large as biggest overlay
 240           (uncompressed)
 241
 242 config SPL_LOAD_FIT_FULL
 243         bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
 244         select SPL_FIT
 245         help
 246           Normally with the SPL framework a legacy image is generated as part
 247           of the build. This contains U-Boot along with information as to
 248           where it should be loaded. This option instead enables generation
 249           of a FIT (Flat Image Tree) which provides more flexibility. In
 250           particular it can handle selecting from multiple device tree
 251           and passing the correct one to U-Boot.
 252
 253 config SPL_FIT_IMAGE_POST_PROCESS
 254         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 255         depends on SPL_LOAD_FIT
 256         default y if TI_SECURE_DEVICE
 257         help
 258           Allows doing any sort of manipulation to blobs after they got extracted
 259           from the U-Boot FIT image like stripping off headers or modifying the
 260           size of the blob, verification, authentication, decryption etc. in a
 261           platform or board specific way. In order to use this feature a platform
 262           or board-specific implementation of board_fit_image_post_process() must
 263           be provided. Also, anything done during this post-processing step would
 264           need to be comprehended in how the images were prepared before being
 265           injected into the FIT creation (i.e. the blobs would have been pre-
 266           processed before being added to the FIT image).
 267
 268 config SPL_FIT_SOURCE
 269         string ".its source file for U-Boot FIT image"
 270         depends on SPL_FIT
 271         help
 272           Specifies a (platform specific) FIT source file to generate the
 273           U-Boot FIT image. This could specify further image to load and/or
 274           execute.
 275
 276 config USE_SPL_FIT_GENERATOR
 277         bool "Use a script to generate the .its script"
 278         depends on SPL_FIT
 279         default y if SPL_FIT && ARCH_ZYNQMP
 280
 281 config SPL_FIT_GENERATOR
 282         string ".its file generator script for U-Boot FIT image"
 283         depends on USE_SPL_FIT_GENERATOR
 284         default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
 285         help
 286           Specifies a (platform specific) script file to generate the FIT
 287           source file used to build the U-Boot FIT image file. This gets
 288           passed a list of supported device tree file stub names to
 289           include in the generated image.
 290
 291 if VPL
 292
 293 config VPL_FIT
 294         bool "Support Flattened Image Tree within VPL"
 295         depends on VPL
 296         default y
 297         select VPL_HASH
 298         select VPL_OF_LIBFDT
 299
 300 config VPL_FIT_PRINT
 301         bool "Support FIT printing within VPL"
 302         depends on VPL_FIT
 303         default y
 304         help
 305           Support printing the content of the fitImage in a verbose manner in VPL.
 306
 307 config VPL_FIT_FULL_CHECK
 308         bool "Do a full check of the FIT before using it"
 309         default y
 310         help
 311           Enable this do a full check of the FIT to make sure it is valid. This
 312           helps to protect against carefully crafted FITs which take advantage
 313           of bugs or omissions in the code. This includes a bad structure,
 314           multiple root nodes and the like.
 315
 316 config VPL_FIT_SIGNATURE
 317         bool "Enable signature verification of FIT firmware within VPL"
 318         depends on VPL_DM
 319         default y
 320         select FIT_SIGNATURE
 321         select VPL_FIT
 322         select VPL_CRYPTO
 323         select VPL_HASH
 324         imply VPL_RSA
 325         imply VPL_RSA_VERIFY
 326         select VPL_IMAGE_SIGN_INFO
 327         select VPL_FIT_FULL_CHECK
 328
 329 config VPL_FIT_SIGNATURE_MAX_SIZE
 330         hex "Max size of signed FIT structures in VPL"
 331         depends on VPL_FIT_SIGNATURE
 332         default 0x10000000
 333         help
 334           This option sets a max size in bytes for verified FIT uImages.
 335           A sane value of 256MB protects corrupted DTB structures from overlapping
 336           device memory. Assure this size does not extend past expected storage
 337           space.
 338
 339 endif # VPL
 340
 341 endif # FIT
 342
 343 config PXE_UTILS
 344         bool
 345         select MENU
 346         help
 347           Utilities for parsing PXE file formats.
 348
 349 config BOOT_DEFAULTS
 350         bool  # Common defaults for standard boot and distroboot
 351         imply USE_BOOTCOMMAND
 352         select CMD_ENV_EXISTS
 353         select CMD_EXT2
 354         select CMD_EXT4
 355         select CMD_FAT
 356         select CMD_FS_GENERIC
 357         select CMD_PART if PARTITIONS
 358         select CMD_DHCP if CMD_NET
 359         select CMD_PING if CMD_NET
 360         select CMD_PXE if CMD_NET
 361         select SUPPORT_RAW_INITRD
 362         select ENV_VARS_UBOOT_CONFIG
 363         select CMD_BOOTI if ARM64
 364         select CMD_BOOTZ if ARM && !ARM64
 365         imply CMD_MII if NET
 366         imply USB_STORAGE
 367         imply EFI_PARTITION
 368         imply ISO_PARTITION
 369         help
 370           These are not required but are commonly needed to support a good
 371           selection of booting methods. Enable this to improve the capability
 372           of U-Boot to boot various images. Currently much functionality is
 373           tied to enabling the command that exercises it.
 374
 375 menuconfig BOOTSTD
 376         bool "Standard boot"
 377         default y
 378         depends on DM && OF_CONTROL && BLK
 379         help
 380           U-Boot supports a standard way of locating something to boot,
 381           typically an Operating System such as Linux, provided by a distro such
 382           as Arch Linux or Debian. Enable this to support iterating through
 383           available bootdevs and using bootmeths to find bootflows suitable for
 384           booting.
 385
 386           Standard boot is not a standard way of booting, just a framework
 387           within U-Boot for supporting all the different ways that exist.
 388
 389           Terminology:
 390
 391             - bootdev - a device which can hold a distro (e.g. MMC)
 392             - bootmeth - a method to scan a bootdev to find bootflows (owned by
 393                 U-Boot)
 394             - bootflow - a description of how to boot (owned by the distro)
 395
 396 if BOOTSTD
 397
 398 config SPL_BOOTSTD
 399         bool "Standard boot support in SPL"
 400         depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
 401         default y if VPL
 402         help
 403           This enables standard boot in SPL. This is neeeded so that VBE
 404           (Verified Boot for Embedded) can be used, since it depends on standard
 405           boot. It is enabled by default since the main purpose of VPL is to
 406           handle the firmware part of VBE.
 407
 408 config VPL_BOOTSTD
 409         bool "Standard boot support in VPL"
 410         depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
 411         default y
 412         help
 413           This enables standard boot in SPL. This is neeeded so that VBE
 414           (Verified Boot for Embedded) can be used, since it depends on standard
 415           boot. It is enabled by default since the main purpose of VPL is to
 416           handle the firmware part of VBE.
 417
 418 config BOOTSTD_FULL
 419         bool "Enhanced features for standard boot"
 420         default y if SANDBOX
 421         help
 422           This enables various useful features for standard boot, which are not
 423           essential for operation:
 424
 425           - bootdev, bootmeth commands
 426           - extra features in the bootflow command
 427           - support for selecting the ordering of bootmeths ("bootmeth order")
 428           - support for selecting the ordering of bootdevs using the devicetree
 429             as well as the "boot_targets" environment variable
 430
 431 config BOOTSTD_DEFAULTS
 432         bool "Select some common defaults for standard boot"
 433         depends on BOOTSTD
 434         imply USE_BOOTCOMMAND
 435         select BOOT_DEFAULTS
 436         select BOOTMETH_DISTRO
 437         help
 438           These are not required but are commonly needed to support a good
 439           selection of booting methods. Enable this to improve the capability
 440           of U-Boot to boot various images.
 441
 442 config BOOTSTD_BOOTCOMMAND
 443         bool "Use bootstd to boot"
 444         default y if !DISTRO_DEFAULTS
 445         help
 446           Enable this to select a default boot-command suitable for booting
 447           with standard boot. This can be overridden by the board if needed,
 448           but the default command should be enough for most boards which use
 449           standard boot.
 450
 451           For now this is only selected if distro boot is NOT used, since
 452           standard boot does not support all of the features of distro boot
 453           yet.
 454
 455 config BOOTMETH_GLOBAL
 456         bool
 457         help
 458           Add support for global bootmeths. This feature is used by VBE and
 459           EFI bootmgr, since they take full control over which bootdevs are
 460           selected to boot.
 461
 462 config BOOTMETH_CROS
 463         bool "Bootdev support for Chromium OS"
 464         depends on X86 || ARM || SANDBOX
 465         default y if !ARM
 466         select EFI_PARTITION
 467         select PARTITION_TYPE_GUID
 468         select PARTITION_UUIDS
 469         help
 470           Enables support for booting Chromium OS using bootdevs. This uses the
 471           kernel A slot and obtains the kernel command line from the parameters
 472           provided there.
 473
 474           Note that only x86 devices are supported at present.
 475
 476 config BOOTMETH_EXTLINUX
 477         bool "Bootdev support for extlinux boot"
 478         select PXE_UTILS
 479         default y
 480         help
 481           Enables support for extlinux boot using bootdevs. This makes the
 482           bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
 483           they scan.
 484
 485           The specification for this filed is here:
 486
 487             https://uapi-group.org/specifications/specs/boot_loader_specification/
 488
 489           This provides a way to try out standard boot on an existing boot flow.
 490
 491 config BOOTMETH_EXTLINUX_PXE
 492         bool "Bootdev support for extlinux boot over network"
 493         depends on CMD_PXE && CMD_NET && DM_ETH
 494         default y
 495         help
 496           Enables support for extlinux boot using bootdevs. This makes the
 497           bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
 498
 499           The specification for this file is here:
 500
 501             https://uapi-group.org/specifications/specs/boot_loader_specification/
 502
 503           This provides a way to try out standard boot on an existing boot flow.
 504
 505 config BOOTMETH_EFILOADER
 506         bool "Bootdev support for EFI boot"
 507         depends on EFI_LOADER
 508         default y
 509         help
 510           Enables support for EFI boot using bootdevs. This makes the
 511           bootdevs look for a 'boot<arch>.efi' on each filesystem
 512           they scan. The resulting file is booted after enabling U-Boot's
 513           EFI loader support.
 514
 515           The <arch> depends on the architecture of the board:
 516
 517              aa64      - aarch64 (ARM 64-bit)
 518              arm       - ARM 32-bit
 519              ia32      - x86 32-bit
 520              x64       - x86 64-bit
 521              riscv32   - RISC-V 32-bit
 522              riscv64   - RISC-V 64-bit
 523
 524           This provides a way to try out standard boot on an existing boot flow.
 525
 526 config BOOTMETH_VBE
 527         bool "Bootdev support for Verified Boot for Embedded"
 528         depends on FIT
 529         default y
 530         select BOOTMETH_GLOBAL
 531         select EVENT
 532         help
 533           Enables support for VBE boot. This is a standard boot method which
 534           supports selection of various firmware components, seleciton of an OS to
 535           boot as well as updating these using fwupd.
 536
 537 config BOOTMETH_DISTRO
 538         bool  # Options needed to boot any distro
 539         select BOOTMETH_SCRIPT  # E.g. Armbian uses scripts
 540         select BOOTMETH_EXTLINUX  # E.g. Debian uses these
 541         select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
 542         select BOOTMETH_EFILOADER if EFI_LOADER # E.g. Ubuntu uses this
 543
 544 config SPL_BOOTMETH_VBE
 545         bool "Bootdev support for Verified Boot for Embedded (SPL)"
 546         depends on SPL && FIT
 547         select EVENT
 548         default y if VPL
 549         help
 550           Enables support for VBE boot. This is a standard boot method which
 551           supports selection of various firmware components, seleciton of an OS to
 552           boot as well as updating these using fwupd.
 553
 554 config VPL_BOOTMETH_VBE
 555         bool "Bootdev support for Verified Boot for Embedded (VPL)"
 556         depends on VPL && FIT
 557         select EVENT
 558         default y
 559         help
 560           Enables support for VBE boot. This is a standard boot method which
 561           supports selection of various firmware components, seleciton of an OS to
 562           boot as well as updating these using fwupd.
 563
 564 if BOOTMETH_VBE
 565
 566 config BOOTMETH_VBE_REQUEST
 567         bool "Support for serving VBE OS requests"
 568         default y
 569         help
 570           Enables support for looking that the requests made by the
 571           Operating System being booted. These requests result in additions to
 572           the device tree /chosen node, added during the device tree fixup
 573           phase.
 574
 575 config SPL_BOOTMETH_VBE_REQUEST
 576         bool "Support for serving VBE OS requests (SPL)"
 577         depends on SPL
 578         help
 579           Enables support for looking that the requests made by the
 580           Operating System being booted. These requests result in additions to
 581           the device tree /chosen node, added during the device tree fixup
 582           phase.
 583
 584           This is only useful if you are booting an OS direct from SPL.
 585
 586 config BOOTMETH_VBE_SIMPLE
 587         bool "Bootdev support for VBE 'simple' method"
 588         default y
 589         help
 590           Enables support for VBE 'simple' boot. This allows updating a single
 591           firmware image in boot media such as MMC. It does not support any sort
 592           of rollback, recovery or A/B boot.
 593
 594 config BOOTMETH_VBE_SIMPLE_OS
 595         bool "Bootdev support for VBE 'simple' method OS phase"
 596         default y
 597         help
 598           Enables support for the OS parts of VBE 'simple' boot. This includes
 599           fixing up the device tree with the required VBE information, ready
 600           for booting into the OS. This option is only enabled for U-Boot
 601           proper, since it is the phase where device tree fixups happen.
 602
 603 config SPL_BOOTMETH_VBE_SIMPLE
 604         bool "Bootdev support for VBE 'simple' method (SPL)"
 605         depends on SPL
 606         default y if VPL
 607         help
 608           Enables support for VBE 'simple' boot. This allows updating a single
 609           firmware image in boot media such as MMC. It does not support any sort
 610           of rollback, recovery or A/B boot.
 611
 612 config VPL_BOOTMETH_VBE_SIMPLE
 613         bool "Bootdev support for VBE 'simple' method (VPL)"
 614         depends on VPL
 615         default y
 616         help
 617           Enables support for VBE 'simple' boot. This allows updating a single
 618           firmware image in boot media such as MMC. It does not support any sort
 619           of rollback, recovery or A/B boot.
 620
 621 config SPL_BOOTMETH_VBE_SIMPLE_FW
 622         bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
 623         depends on VPL
 624         default y
 625         help
 626           Enables support for the firmware parts of VBE 'simple' boot. This
 627           includes an SPL loader which locates the correct U-Boot to boot into.
 628           This option should really only be enabled for VPL, since it is the
 629           phase where the SPL + U-Boot decision should be made. But for now,
 630           SPL does its own FIT-configuration selection.
 631
 632 config VPL_BOOTMETH_VBE_SIMPLE_FW
 633         bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
 634         depends on VPL
 635         default y
 636         help
 637           Enables support for the firmware parts of VBE 'simple' boot. This
 638           includes an SPL loader which locates the correct SPL to boot into.
 639           This option enabled for VPL, since it is the phase where the SPL
 640           decision is made.
 641
 642 endif # BOOTMETH_VBE
 643
 644 config EXPO
 645         bool "Support for expos - groups of scenes displaying a UI"
 646         depends on VIDEO
 647         default y if BOOTMETH_VBE
 648         help
 649           An expo is a way of presenting and collecting information from the
 650           user. It consists of a collection of 'scenes' of which only one is
 651           presented at a time. An expo is typically used to show a boot menu
 652           and allow settings to be changed.
 653
 654           The expo can be presented in graphics form using a vidconsole, or in
 655           text form on a serial console.
 656
 657 config BOOTMETH_SANDBOX
 658         def_bool y
 659         depends on SANDBOX
 660         help
 661           This is a sandbox bootmeth driver used for testing. It always returns
 662           -ENOTSUPP when attempting to boot.
 663
 664 config BOOTMETH_SCRIPT
 665         bool "Bootdev support for U-Boot scripts"
 666         default y if BOOTSTD_FULL
 667         select HUSH_PARSER
 668         help
 669           Enables support for booting a distro via a U-Boot script. This makes
 670           the bootdevs look for a 'boot/boot.scr' file which can be used to
 671           boot the distro.
 672
 673           This provides a way to try out standard boot on an existing boot flow.
 674           It is not enabled by default to save space.
 675
 676 endif # BOOTSTD
 677
 678 config LEGACY_IMAGE_FORMAT
 679         bool "Enable support for the legacy image format"
 680         default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
 681         help
 682           This option enables the legacy image format. It is enabled by
 683           default for backward compatibility, unless FIT_SIGNATURE is
 684           set where it is disabled so that unsigned images cannot be
 685           loaded. If a board needs the legacy image format support in this
 686           case, enable it here.
 687
 688 config SUPPORT_RAW_INITRD
 689         bool "Enable raw initrd images"
 690         help
 691           Note, defining the SUPPORT_RAW_INITRD allows user to supply
 692           kernel with raw initrd images. The syntax is slightly different, the
 693           address of the initrd must be augmented by it's size, in the following
 694           format: "<initrd address>:<initrd size>".
 695
 696 config CHROMEOS
 697         bool "Support booting Chrome OS"
 698         help
 699           Chrome OS requires U-Boot to set up a table indicating the boot mode
 700           (e.g. Developer mode) and a few other things. Enable this if you are
 701           booting on a Chromebook to avoid getting an error about an invalid
 702           firmware ID.
 703
 704 config CHROMEOS_VBOOT
 705         bool "Support Chrome OS verified boot"
 706         help
 707           This is intended to enable the full Chrome OS verified boot support
 708           in U-Boot. It is not actually implemented in the U-Boot source code
 709           at present, so this option is always set to 'n'. It allows
 710           distinguishing between booting Chrome OS in a basic way (developer
 711           mode) and a full boot.
 712
 713 config SYS_RAMBOOT
 714         bool
 715
 716 config RAMBOOT_PBL
 717         bool "Freescale PBL(pre-boot loader) image format support"
 718         select SYS_RAMBOOT if PPC
 719         help
 720           Some SoCs use PBL to load RCW and/or pre-initialization instructions.
 721           For more details refer to doc/README.pblimage
 722
 723 choice
 724         prompt "Freescale PBL (or predecessor) load location"
 725         depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
 726                 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
 727                 && !CMD_NAND)
 728
 729 config SDCARD
 730         bool "Freescale PBL (or similar) is found on SD card"
 731
 732 config SPIFLASH
 733         bool "Freescale PBL (or similar) is found on SPI flash"
 734
 735 config NO_PBL
 736         bool "Freescale PBL (or similar) is not used in this case"
 737
 738 endchoice
 739
 740 config FSL_FIXED_MMC_LOCATION
 741         bool "PBL MMC is at a fixed location"
 742         depends on SDCARD && !RAMBOOT_PBL
 743
 744 config ESDHC_HC_BLK_ADDR
 745         def_bool y
 746         depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
 747         help
 748           In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
 749           code length of these soc specify the memory address in block address
 750           format. Block length is fixed to 512 bytes as per the SD High
 751           Capacity specification.
 752
 753 config SYS_FSL_PBL_PBI
 754         string "PBI(pre-boot instructions) commands for the PBL image"
 755         depends on RAMBOOT_PBL
 756         help
 757           PBI commands can be used to configure SoC before it starts the execution.
 758           Please refer doc/README.pblimage for more details.
 759
 760 config SYS_FSL_PBL_RCW
 761         string "Aadditional RCW (Power on reset configuration) for the PBL image"
 762         depends on RAMBOOT_PBL
 763         help
 764           Enables addition of RCW (Power on reset configuration) in built image.
 765           Please refer doc/README.pblimage for more details.
 766
 767 config SYS_BOOT_RAMDISK_HIGH
 768         depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
 769         depends on !(NIOS2 || SANDBOX || SH || XTENSA)
 770         def_bool y
 771         select LMB
 772         help
 773           Enable initrd_high functionality.  If defined then the initrd_high
 774           feature is enabled and the boot* ramdisk subcommand is enabled.
 775
 776 endmenu         # Boot images
 777
 778 config DISTRO_DEFAULTS
 779         bool "(deprecated) Script-based booting of Linux distributions"
 780         select BOOT_DEFAULTS
 781         select AUTO_COMPLETE
 782         select CMDLINE_EDITING
 783         select CMD_SYSBOOT
 784         select HUSH_PARSER
 785         select SYS_LONGHELP
 786         help
 787           Note: These scripts have been replaced by Standard Boot. Do not use
 788           them on new boards. See 'Migrating from distro_boot' at
 789           doc/develop/bootstd.rst
 790
 791           Select this to enable various options and commands which are suitable
 792           for building u-boot for booting general purpose Linux distributions.
 793
 794 menu "Boot timing"
 795
 796 config BOOTSTAGE
 797         bool "Boot timing and reporting"
 798         help
 799           Enable recording of boot time while booting. To use it, insert
 800           calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
 801           bootstage.h. Only a single entry is recorded for each ID. You can
 802           give the entry a name with bootstage_mark_name(). You can also
 803           record elapsed time in a particular stage using bootstage_start()
 804           before starting and bootstage_accum() when finished. Bootstage will
 805           add up all the accumulated time and report it.
 806
 807           Normally, IDs are defined in bootstage.h but a small number of
 808           additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
 809           as the ID.
 810
 811           Calls to show_boot_progress() will also result in log entries but
 812           these will not have names.
 813
 814 config SPL_BOOTSTAGE
 815         bool "Boot timing and reported in SPL"
 816         depends on BOOTSTAGE && SPL
 817         help
 818           Enable recording of boot time in SPL. To make this visible to U-Boot
 819           proper, enable BOOTSTAGE_STASH as well. This will stash the timing
 820           information when SPL finishes and load it when U-Boot proper starts
 821           up.
 822
 823 config TPL_BOOTSTAGE
 824         bool "Boot timing and reported in TPL"
 825         depends on BOOTSTAGE && TPL
 826         help
 827           Enable recording of boot time in SPL. To make this visible to U-Boot
 828           proper, enable BOOTSTAGE_STASH as well. This will stash the timing
 829           information when TPL finishes and load it when U-Boot proper starts
 830           up.
 831
 832 config BOOTSTAGE_REPORT
 833         bool "Display a detailed boot timing report before booting the OS"
 834         depends on BOOTSTAGE
 835         help
 836           Enable output of a boot time report just before the OS is booted.
 837           This shows how long it took U-Boot to go through each stage of the
 838           boot process. The report looks something like this:
 839
 840                 Timer summary in microseconds:
 841                        Mark    Elapsed  Stage
 842                           0          0  reset
 843                   3,575,678  3,575,678  board_init_f start
 844                   3,575,695         17  arch_cpu_init A9
 845                   3,575,777         82  arch_cpu_init done
 846                   3,659,598     83,821  board_init_r start
 847                   3,910,375    250,777  main_loop
 848                  29,916,167 26,005,792  bootm_start
 849                  30,361,327    445,160  start_kernel
 850
 851 config BOOTSTAGE_RECORD_COUNT
 852         int "Number of boot stage records to store"
 853         depends on BOOTSTAGE
 854         default 30
 855         help
 856           This is the size of the bootstage record list and is the maximum
 857           number of bootstage records that can be recorded.
 858
 859 config SPL_BOOTSTAGE_RECORD_COUNT
 860         int "Number of boot stage records to store for SPL"
 861         depends on SPL_BOOTSTAGE
 862         default 5
 863         help
 864           This is the size of the bootstage record list and is the maximum
 865           number of bootstage records that can be recorded.
 866
 867 config TPL_BOOTSTAGE_RECORD_COUNT
 868         int "Number of boot stage records to store for TPL"
 869         depends on TPL_BOOTSTAGE
 870         default 5
 871         help
 872           This is the size of the bootstage record list and is the maximum
 873           number of bootstage records that can be recorded.
 874
 875 config BOOTSTAGE_FDT
 876         bool "Store boot timing information in the OS device tree"
 877         depends on BOOTSTAGE
 878         help
 879           Stash the bootstage information in the FDT. A root 'bootstage'
 880           node is created with each bootstage id as a child. Each child
 881           has a 'name' property and either 'mark' containing the
 882           mark time in microseconds, or 'accum' containing the
 883           accumulated time for that bootstage id in microseconds.
 884           For example:
 885
 886                 bootstage {
 887                         154 {
 888                                 name = "board_init_f";
 889                                 mark = <3575678>;
 890                         };
 891                         170 {
 892                                 name = "lcd";
 893                                 accum = <33482>;
 894                         };
 895                 };
 896
 897           Code in the Linux kernel can find this in /proc/devicetree.
 898
 899 config BOOTSTAGE_STASH
 900         bool "Stash the boot timing information in memory before booting OS"
 901         depends on BOOTSTAGE
 902         help
 903           Some OSes do not support device tree. Bootstage can instead write
 904           the boot timing information in a binary format at a given address.
 905           This happens through a call to bootstage_stash(), typically in
 906           the CPU's cleanup_before_linux() function. You can use the
 907           'bootstage stash' and 'bootstage unstash' commands to do this on
 908           the command line.
 909
 910 config BOOTSTAGE_STASH_ADDR
 911         hex "Address to stash boot timing information"
 912         default 0x0
 913         help
 914           Provide an address which will not be overwritten by the OS when it
 915           starts, so that it can read this information when ready.
 916
 917 config BOOTSTAGE_STASH_SIZE
 918         hex "Size of boot timing stash region"
 919         default 0x1000
 920         help
 921           This should be large enough to hold the bootstage stash. A value of
 922           4096 (4KiB) is normally plenty.
 923
 924 config SHOW_BOOT_PROGRESS
 925         bool "Show boot progress in a board-specific manner"
 926         help
 927           Defining this option allows to add some board-specific code (calling
 928           a user-provided function show_boot_progress(int) that enables you to
 929           show the system's boot progress on some display (for example, some
 930           LEDs) on your board. At the moment, the following checkpoints are
 931           implemented:
 932
 933           Legacy uImage format:
 934
 935           Arg   Where                   When
 936             1   common/cmd_bootm.c      before attempting to boot an image
 937            -1   common/cmd_bootm.c      Image header has bad     magic number
 938             2   common/cmd_bootm.c      Image header has correct magic number
 939            -2   common/cmd_bootm.c      Image header has bad     checksum
 940             3   common/cmd_bootm.c      Image header has correct checksum
 941            -3   common/cmd_bootm.c      Image data   has bad     checksum
 942             4   common/cmd_bootm.c      Image data   has correct checksum
 943            -4   common/cmd_bootm.c      Image is for unsupported architecture
 944             5   common/cmd_bootm.c      Architecture check OK
 945            -5   common/cmd_bootm.c      Wrong Image Type (not kernel, multi)
 946             6   common/cmd_bootm.c      Image Type check OK
 947            -6   common/cmd_bootm.c      gunzip uncompression error
 948            -7   common/cmd_bootm.c      Unimplemented compression type
 949             7   common/cmd_bootm.c      Uncompression OK
 950             8   common/cmd_bootm.c      No uncompress/copy overwrite error
 951            -9   common/cmd_bootm.c      Unsupported OS (not Linux, BSD, VxWorks, QNX)
 952
 953             9   common/image.c          Start initial ramdisk verification
 954           -10   common/image.c          Ramdisk header has bad     magic number
 955           -11   common/image.c          Ramdisk header has bad     checksum
 956            10   common/image.c          Ramdisk header is OK
 957           -12   common/image.c          Ramdisk data   has bad     checksum
 958            11   common/image.c          Ramdisk data   has correct checksum
 959            12   common/image.c          Ramdisk verification complete, start loading
 960           -13   common/image.c          Wrong Image Type (not PPC Linux ramdisk)
 961            13   common/image.c          Start multifile image verification
 962            14   common/image.c          No initial ramdisk, no multifile, continue.
 963
 964            15   arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
 965
 966           -30   arch/powerpc/lib/board.c        Fatal error, hang the system
 967           -31   post/post.c             POST test failed, detected by post_output_backlog()
 968           -32   post/post.c             POST test failed, detected by post_run_single()
 969
 970            34   common/cmd_doc.c        before loading a Image from a DOC device
 971           -35   common/cmd_doc.c        Bad usage of "doc" command
 972            35   common/cmd_doc.c        correct usage of "doc" command
 973           -36   common/cmd_doc.c        No boot device
 974            36   common/cmd_doc.c        correct boot device
 975           -37   common/cmd_doc.c        Unknown Chip ID on boot device
 976            37   common/cmd_doc.c        correct chip ID found, device available
 977           -38   common/cmd_doc.c        Read Error on boot device
 978            38   common/cmd_doc.c        reading Image header from DOC device OK
 979           -39   common/cmd_doc.c        Image header has bad magic number
 980            39   common/cmd_doc.c        Image header has correct magic number
 981           -40   common/cmd_doc.c        Error reading Image from DOC device
 982            40   common/cmd_doc.c        Image header has correct magic number
 983            41   common/cmd_ide.c        before loading a Image from a IDE device
 984           -42   common/cmd_ide.c        Bad usage of "ide" command
 985            42   common/cmd_ide.c        correct usage of "ide" command
 986           -43   common/cmd_ide.c        No boot device
 987            43   common/cmd_ide.c        boot device found
 988           -44   common/cmd_ide.c        Device not available
 989            44   common/cmd_ide.c        Device available
 990           -45   common/cmd_ide.c        wrong partition selected
 991            45   common/cmd_ide.c        partition selected
 992           -46   common/cmd_ide.c        Unknown partition table
 993            46   common/cmd_ide.c        valid partition table found
 994           -47   common/cmd_ide.c        Invalid partition type
 995            47   common/cmd_ide.c        correct partition type
 996           -48   common/cmd_ide.c        Error reading Image Header on boot device
 997            48   common/cmd_ide.c        reading Image Header from IDE device OK
 998           -49   common/cmd_ide.c        Image header has bad magic number
 999            49   common/cmd_ide.c        Image header has correct magic number
1000           -50   common/cmd_ide.c        Image header has bad     checksum
1001            50   common/cmd_ide.c        Image header has correct checksum
1002           -51   common/cmd_ide.c        Error reading Image from IDE device
1003            51   common/cmd_ide.c        reading Image from IDE device OK
1004            52   common/cmd_nand.c       before loading a Image from a NAND device
1005           -53   common/cmd_nand.c       Bad usage of "nand" command
1006            53   common/cmd_nand.c       correct usage of "nand" command
1007           -54   common/cmd_nand.c       No boot device
1008            54   common/cmd_nand.c       boot device found
1009           -55   common/cmd_nand.c       Unknown Chip ID on boot device
1010            55   common/cmd_nand.c       correct chip ID found, device available
1011           -56   common/cmd_nand.c       Error reading Image Header on boot device
1012            56   common/cmd_nand.c       reading Image Header from NAND device OK
1013           -57   common/cmd_nand.c       Image header has bad magic number
1014            57   common/cmd_nand.c       Image header has correct magic number
1015           -58   common/cmd_nand.c       Error reading Image from NAND device
1016            58   common/cmd_nand.c       reading Image from NAND device OK
1017
1018           -60   common/env_common.c     Environment has a bad CRC, using default
1019
1020            64   net/eth.c               starting with Ethernet configuration.
1021           -64   net/eth.c               no Ethernet found.
1022            65   net/eth.c               Ethernet found.
1023
1024           -80   common/cmd_net.c        usage wrong
1025            80   common/cmd_net.c        before calling net_loop()
1026           -81   common/cmd_net.c        some error in net_loop() occurred
1027            81   common/cmd_net.c        net_loop() back without error
1028           -82   common/cmd_net.c        size == 0 (File with size 0 loaded)
1029            82   common/cmd_net.c        trying automatic boot
1030            83   common/cmd_net.c        running "source" command
1031           -83   common/cmd_net.c        some error in automatic boot or "source" command
1032            84   common/cmd_net.c        end without errors
1033
1034           FIT uImage format:
1035
1036           Arg   Where                   When
1037           100   common/cmd_bootm.c      Kernel FIT Image has correct format
1038           -100  common/cmd_bootm.c      Kernel FIT Image has incorrect format
1039           101   common/cmd_bootm.c      No Kernel subimage unit name, using configuration
1040           -101  common/cmd_bootm.c      Can't get configuration for kernel subimage
1041           102   common/cmd_bootm.c      Kernel unit name specified
1042           -103  common/cmd_bootm.c      Can't get kernel subimage node offset
1043           103   common/cmd_bootm.c      Found configuration node
1044           104   common/cmd_bootm.c      Got kernel subimage node offset
1045           -104  common/cmd_bootm.c      Kernel subimage hash verification failed
1046           105   common/cmd_bootm.c      Kernel subimage hash verification OK
1047           -105  common/cmd_bootm.c      Kernel subimage is for unsupported architecture
1048           106   common/cmd_bootm.c      Architecture check OK
1049           -106  common/cmd_bootm.c      Kernel subimage has wrong type
1050           107   common/cmd_bootm.c      Kernel subimage type OK
1051           -107  common/cmd_bootm.c      Can't get kernel subimage data/size
1052           108   common/cmd_bootm.c      Got kernel subimage data/size
1053           -108  common/cmd_bootm.c      Wrong image type (not legacy, FIT)
1054           -109  common/cmd_bootm.c      Can't get kernel subimage type
1055           -110  common/cmd_bootm.c      Can't get kernel subimage comp
1056           -111  common/cmd_bootm.c      Can't get kernel subimage os
1057           -112  common/cmd_bootm.c      Can't get kernel subimage load address
1058           -113  common/cmd_bootm.c      Image uncompress/copy overwrite error
1059
1060           120   common/image.c          Start initial ramdisk verification
1061           -120  common/image.c          Ramdisk FIT image has incorrect format
1062           121   common/image.c          Ramdisk FIT image has correct format
1063           122   common/image.c          No ramdisk subimage unit name, using configuration
1064           -122  common/image.c          Can't get configuration for ramdisk subimage
1065           123   common/image.c          Ramdisk unit name specified
1066           -124  common/image.c          Can't get ramdisk subimage node offset
1067           125   common/image.c          Got ramdisk subimage node offset
1068           -125  common/image.c          Ramdisk subimage hash verification failed
1069           126   common/image.c          Ramdisk subimage hash verification OK
1070           -126  common/image.c          Ramdisk subimage for unsupported architecture
1071           127   common/image.c          Architecture check OK
1072           -127  common/image.c          Can't get ramdisk subimage data/size
1073           128   common/image.c          Got ramdisk subimage data/size
1074           129   common/image.c          Can't get ramdisk load address
1075           -129  common/image.c          Got ramdisk load address
1076
1077           -130  common/cmd_doc.c        Incorrect FIT image format
1078           131   common/cmd_doc.c        FIT image format OK
1079
1080           -140  common/cmd_ide.c        Incorrect FIT image format
1081           141   common/cmd_ide.c        FIT image format OK
1082
1083           -150  common/cmd_nand.c       Incorrect FIT image format
1084           151   common/cmd_nand.c       FIT image format OK
1085
1086 config SPL_SHOW_BOOT_PROGRESS
1087         bool "Show boot progress in a board-specific manner in SPL"
1088         depends on SPL
1089         help
1090           Defining this option allows to add some board-specific code (calling
1091           a user-provided function show_boot_progress(int) that enables you to
1092           show the system's boot progress on some display (for example, some
1093           LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1094
1095 endmenu
1096
1097 menu "Boot media"
1098
1099 config NOR_BOOT
1100         bool "Support for booting from NOR flash"
1101         depends on NOR
1102         help
1103           Enabling this will make a U-Boot binary that is capable of being
1104           booted via NOR.  In this case we will enable certain pinmux early
1105           as the ROM only partially sets up pinmux.  We also default to using
1106           NOR for environment.
1107
1108 config NAND_BOOT
1109         bool "Support for booting from NAND flash"
1110         imply MTD_RAW_NAND
1111         help
1112           Enabling this will make a U-Boot binary that is capable of being
1113           booted via NAND flash. This is not a must, some SoCs need this,
1114           some not.
1115
1116 config ONENAND_BOOT
1117         bool "Support for booting from ONENAND"
1118         imply MTD_RAW_NAND
1119         help
1120           Enabling this will make a U-Boot binary that is capable of being
1121           booted via ONENAND. This is not a must, some SoCs need this,
1122           some not.
1123
1124 config QSPI_BOOT
1125         bool "Support for booting from QSPI flash"
1126         help
1127           Enabling this will make a U-Boot binary that is capable of being
1128           booted via QSPI flash. This is not a must, some SoCs need this,
1129           some not.
1130
1131 config SATA_BOOT
1132         bool "Support for booting from SATA"
1133         help
1134           Enabling this will make a U-Boot binary that is capable of being
1135           booted via SATA. This is not a must, some SoCs need this,
1136           some not.
1137
1138 config SD_BOOT
1139         bool "Support for booting from SD/EMMC"
1140         help
1141           Enabling this will make a U-Boot binary that is capable of being
1142           booted via SD/EMMC. This is not a must, some SoCs need this,
1143           some not.
1144
1145 config SD_BOOT_QSPI
1146         bool "Support for booting from SD/EMMC and enable QSPI"
1147         help
1148           Enabling this will make a U-Boot binary that is capable of being
1149           booted via SD/EMMC while enabling QSPI on the platform as well. This
1150           is not a must, some SoCs need this, some not.
1151
1152 config SPI_BOOT
1153         bool "Support for booting from SPI flash"
1154         help
1155           Enabling this will make a U-Boot binary that is capable of being
1156           booted via SPI flash. This is not a must, some SoCs need this,
1157           some not.
1158
1159 endmenu
1160
1161 menu "Autoboot options"
1162
1163 config AUTOBOOT
1164         bool "Autoboot"
1165         default y
1166         help
1167           This enables the autoboot.  See doc/README.autoboot for detail.
1168
1169 config BOOTDELAY
1170         int "delay in seconds before automatically booting"
1171         default 2
1172         depends on AUTOBOOT
1173         help
1174           Delay before automatically running bootcmd;
1175           set to 0 to autoboot with no delay, but you can stop it by key input.
1176           set to -1 to disable autoboot.
1177           set to -2 to autoboot with no delay and not check for abort
1178
1179           If this value is >= 0 then it is also used for the default delay
1180           before starting the default entry in bootmenu. If it is < 0 then
1181           a default value of 10s is used.
1182
1183           See doc/README.autoboot for details.
1184
1185 config AUTOBOOT_KEYED
1186         bool "Stop autobooting via specific input key / string"
1187         help
1188           This option enables stopping (aborting) of the automatic
1189           boot feature only by issuing a specific input key or
1190           string. If not enabled, any input key will abort the
1191           U-Boot automatic booting process and bring the device
1192           to the U-Boot prompt for user input.
1193
1194 config AUTOBOOT_FLUSH_STDIN
1195         bool "Enable flushing stdin before starting to read the password"
1196         depends on AUTOBOOT_KEYED && !SANDBOX
1197         help
1198           When this option is enabled stdin buffer will be flushed before
1199           starting to read the password.
1200           This can't be enabled for the sandbox as flushing stdin would
1201           break the autoboot unit tests.
1202
1203 config AUTOBOOT_PROMPT
1204         string "Autoboot stop prompt"
1205         depends on AUTOBOOT_KEYED
1206         default "Autoboot in %d seconds\\n"
1207         help
1208           This string is displayed before the boot delay selected by
1209           CONFIG_BOOTDELAY starts. If it is not defined there is no
1210           output indicating that autoboot is in progress.
1211
1212           Note that this define is used as the (only) argument to a
1213           printf() call, so it may contain '%' format specifications,
1214           provided that it also includes, sepearated by commas exactly
1215           like in a printf statement, the required arguments. It is
1216           the responsibility of the user to select only such arguments
1217           that are valid in the given context.
1218
1219 config AUTOBOOT_ENCRYPTION
1220         bool "Enable encryption in autoboot stopping"
1221         depends on AUTOBOOT_KEYED
1222         help
1223           This option allows a string to be entered into U-Boot to stop the
1224           autoboot.
1225           The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1226           or not.
1227           In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1228           to the crypt-based functionality and be compared against the
1229           string in the environment variable 'bootstopkeycrypt'.
1230           In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1231           and compared against the hash in the environment variable
1232           'bootstopkeysha256'.
1233           If it matches in either case then boot stops and
1234           a command-line prompt is presented.
1235           This provides a way to ship a secure production device which can also
1236           be accessed at the U-Boot command line.
1237
1238 config AUTOBOOT_SHA256_FALLBACK
1239         bool "Allow fallback from crypt-hashed password to sha256"
1240         depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1241         help
1242           This option adds support to fall back from crypt-hashed
1243           passwords to checking a SHA256 hashed password in case the
1244           'bootstopusesha256' environment variable is set to 'true'.
1245
1246 config AUTOBOOT_DELAY_STR
1247         string "Delay autobooting via specific input key / string"
1248         depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1249         help
1250           This option delays the automatic boot feature by issuing
1251           a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1252           or the environment variable "bootdelaykey" is specified
1253           and this string is received from console input before
1254           autoboot starts booting, U-Boot gives a command prompt. The
1255           U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1256           used, otherwise it never times out.
1257
1258 config AUTOBOOT_STOP_STR
1259         string "Stop autobooting via specific input key / string"
1260         depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1261         help
1262           This option enables stopping (aborting) of the automatic
1263           boot feature only by issuing a specific input key or
1264           string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1265           variable "bootstopkey" is specified and this string is
1266           received from console input before autoboot starts booting,
1267           U-Boot gives a command prompt. The U-Boot prompt never
1268           times out, even if CONFIG_BOOT_RETRY_TIME is used.
1269
1270 config AUTOBOOT_KEYED_CTRLC
1271         bool "Enable Ctrl-C autoboot interruption"
1272         depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1273         help
1274           This option allows for the boot sequence to be interrupted
1275           by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1276           Setting this variable provides an escape sequence from the
1277           limited "password" strings.
1278
1279 config AUTOBOOT_NEVER_TIMEOUT
1280         bool "Make the password entry never time-out"
1281         depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1282         help
1283           This option removes the timeout from the password entry
1284           when the user first presses the <Enter> key before entering
1285           any other character.
1286
1287 config AUTOBOOT_STOP_STR_ENABLE
1288         bool "Enable fixed string to stop autobooting"
1289         depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1290         help
1291           This option enables the feature to add a fixed stop
1292           string that is defined at compile time.
1293           In every case it will be tried to load the stop
1294           string from the environment.
1295           In case this is enabled and there is no stop string
1296           in the environment, this will be used as default value.
1297
1298 config AUTOBOOT_STOP_STR_CRYPT
1299         string "Stop autobooting via crypt-hashed password"
1300         depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1301         help
1302           This option adds the feature to only stop the autobooting,
1303           and therefore boot into the U-Boot prompt, when the input
1304           string / password matches a values that is hashed via
1305           one of the supported crypt-style password hashing options
1306           and saved in the environment variable "bootstopkeycrypt".
1307
1308 config AUTOBOOT_STOP_STR_SHA256
1309         string "Stop autobooting via SHA256 hashed password"
1310         depends on AUTOBOOT_STOP_STR_ENABLE
1311         help
1312           This option adds the feature to only stop the autobooting,
1313           and therefore boot into the U-Boot prompt, when the input
1314           string / password matches a values that is encypted via
1315           a SHA256 hash and saved in the environment variable
1316           "bootstopkeysha256". If the value in that variable
1317           includes a ":", the portion prior to the ":" will be treated
1318           as a salt value.
1319
1320 config AUTOBOOT_USE_MENUKEY
1321         bool "Allow a specify key to run a menu from the environment"
1322         depends on !AUTOBOOT_KEYED
1323         help
1324           If a specific key is pressed to stop autoboot, then the commands in
1325           the environment variable 'menucmd' are executed before boot starts.
1326
1327 config AUTOBOOT_MENUKEY
1328         int "ASCII value of boot key to show a menu"
1329         default 0
1330         depends on AUTOBOOT_USE_MENUKEY
1331         help
1332           If this key is pressed to stop autoboot, then the commands in the
1333           environment variable 'menucmd' will be executed before boot starts.
1334           For example, 33 means "!" in ASCII, so pressing ! at boot would take
1335           this action.
1336
1337 config AUTOBOOT_MENU_SHOW
1338         bool "Show a menu on boot"
1339         depends on CMD_BOOTMENU
1340         help
1341           This enables the boot menu, controlled by environment variables
1342           defined by the board. The menu starts after running the 'preboot'
1343           environmnent variable (if enabled) and before handling the boot delay.
1344           See doc/usage/cmd/bootmenu.rst for more details.
1345
1346 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1347         bool "Disallow bootmenu to enter the U-Boot console"
1348         depends on AUTOBOOT_MENU_SHOW
1349         help
1350           If this option is enabled, user can not enter the U-Boot console from
1351           bootmenu. It increases the system security.
1352
1353 config BOOT_RETRY
1354         bool "Boot retry feature"
1355         help
1356           Allow for having the U-Boot command prompt time out and attempt
1357           to boot again.  If the environment variable "bootretry" is found then
1358           its value is used, otherwise the retry timeout is
1359           CONFIG_BOOT_RETRY_TIME.  CONFIG_BOOT_RETRY_MIN is optional and
1360           defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1361
1362 config BOOT_RETRY_TIME
1363         int "Timeout in seconds before attempting to boot again"
1364         depends on BOOT_RETRY
1365         help
1366           Time in seconds before the U-Boot prompt will timeout and boot will
1367           be attempted again.
1368
1369 config BOOT_RETRY_MIN
1370         int "Minimum timeout in seconds for 'bootretry'"
1371         depends on BOOT_RETRY
1372         default BOOT_RETRY_TIME
1373         help
1374           The minimum time in seconds that "bootretry" can be set to.
1375
1376 config RESET_TO_RETRY
1377         bool "Reset the board to retry autoboot"
1378         depends on BOOT_RETRY
1379         help
1380           After the countdown timed out, the board will be reset to restart
1381           again.
1382
1383 endmenu
1384
1385 menu "Image support"
1386
1387 config IMAGE_PRE_LOAD
1388         bool "Image pre-load support"
1389         help
1390           Enable an image pre-load stage in the SPL.
1391           This pre-load stage allows to do some manipulation
1392           or check (for example signature check) on an image
1393           before launching it.
1394
1395 config SPL_IMAGE_PRE_LOAD
1396         bool "Image pre-load support within SPL"
1397         depends on SPL && IMAGE_PRE_LOAD
1398         help
1399           Enable an image pre-load stage in the SPL.
1400           This pre-load stage allows to do some manipulation
1401           or check (for example signature check) on an image
1402           before launching it.
1403
1404 config IMAGE_PRE_LOAD_SIG
1405         bool "Image pre-load signature support"
1406         depends on IMAGE_PRE_LOAD
1407         select FIT_SIGNATURE
1408         select RSA
1409         select RSA_VERIFY_WITH_PKEY
1410         help
1411           Enable signature check support in the pre-load stage.
1412           For this feature a very simple header is added before
1413           the image with few fields:
1414           - a magic
1415           - the image size
1416           - the signature
1417           All other information (header size, type of signature,
1418           ...) are provided in the node /image/pre-load/sig of
1419           u-boot.
1420
1421 config SPL_IMAGE_PRE_LOAD_SIG
1422         bool "Image pre-load signature support witin SPL"
1423         depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1424         select SPL_FIT_SIGNATURE
1425         select SPL_RSA
1426         select SPL_RSA_VERIFY_WITH_PKEY
1427         help
1428           Enable signature check support in the pre-load stage in the SPL.
1429           For this feature a very simple header is added before
1430           the image with few fields:
1431           - a magic
1432           - the image size
1433           - the signature
1434           All other information (header size, type of signature,
1435           ...) are provided in the node /image/pre-load/sig of
1436           u-boot.
1437
1438 endmenu
1439
1440 if OF_LIBFDT
1441
1442 menu "Devicetree fixup"
1443
1444 config OF_BOARD_SETUP
1445         bool "Set up board-specific details in device tree before boot"
1446         help
1447           This causes U-Boot to call ft_board_setup() before booting into
1448           the Operating System. This function can set up various
1449           board-specific information in the device tree for use by the OS.
1450           The device tree is then passed to the OS.
1451
1452 config OF_SYSTEM_SETUP
1453         bool "Set up system-specific details in device tree before boot"
1454         help
1455           This causes U-Boot to call ft_system_setup() before booting into
1456           the Operating System. This function can set up various
1457           system-specific information in the device tree for use by the OS.
1458           The device tree is then passed to the OS.
1459
1460 config OF_STDOUT_VIA_ALIAS
1461         bool "Update the device-tree stdout alias from U-Boot"
1462         help
1463           This uses U-Boot's serial alias from the aliases node to update
1464           the device tree passed to the OS. The "linux,stdout-path" property
1465           in the chosen node is set to point to the correct serial node.
1466           This option currently references CONFIG_CONS_INDEX, which is
1467           incorrect when used with device tree as this option does not
1468           exist / should not be used.
1469
1470 config FDT_FIXUP_PARTITIONS
1471         bool "Overwrite MTD partitions in DTS through defined in 'mtdparts'"
1472         help
1473           Allow overwriting defined partitions in the device tree blob
1474           using partition info defined in the 'mtdparts' environment
1475           variable.
1476
1477 config FDT_SIMPLEFB
1478         bool "FDT tools for simplefb support"
1479         help
1480           Enable the fdt tools to manage the simple fb nodes in device tree.
1481           These functions can be used by board to indicate to the OS
1482           the presence of the simple frame buffer with associated reserved
1483           memory
1484
1485 config ARCH_FIXUP_FDT_MEMORY
1486         bool "Enable arch_fixup_memory_banks() call"
1487         default y
1488         help
1489           Enable FDT memory map syncup before OS boot. This feature can be
1490           used for booting OS with different memory setup where the part of
1491           the memory location should be used for different purpose.
1492
1493 endmenu
1494
1495 endif # OF_LIBFDT
1496
1497 config USE_BOOTARGS
1498         bool "Enable boot arguments"
1499         help
1500           Provide boot arguments to bootm command. Boot arguments are specified
1501           in CONFIG_BOOTARGS option. Enable this option to be able to specify
1502           CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1503           will be undefined and won't take any space in U-Boot image.
1504
1505 config BOOTARGS
1506         string "Boot arguments"
1507         depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1508         help
1509           This can be used to pass arguments to the bootm command. The value of
1510           CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1511           this value will also override the "chosen" node in FDT blob.
1512
1513 config BOOTARGS_SUBST
1514         bool "Support substituting strings in boot arguments"
1515         help
1516           This allows substituting string values in the boot arguments. These
1517           are applied after the commandline has been built.
1518
1519           One use for this is to insert the root-disk UUID into the command
1520           line where bootargs contains "root=${uuid}"
1521
1522                 setenv bootargs "console= root=${uuid}"
1523                 # Set the 'uuid' environment variable
1524                 part uuid mmc 2:2 uuid
1525
1526                 # Command-line substitution will put the real uuid into the
1527                 # kernel command line
1528                 bootm
1529
1530 config USE_BOOTCOMMAND
1531         bool "Enable a default value for bootcmd"
1532         help
1533           Provide a default value for the bootcmd entry in the environment.  If
1534           autoboot is enabled this is what will be run automatically.  Enable
1535           this option to be able to specify CONFIG_BOOTCOMMAND as a string.  If
1536           this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1537           won't take any space in U-Boot image.
1538
1539 config BOOTCOMMAND
1540         string "bootcmd value"
1541         depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1542         default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1543         default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1544         default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1545         help
1546           This is the string of commands that will be used as bootcmd and if
1547           AUTOBOOT is set, automatically run.
1548
1549 config USE_PREBOOT
1550         bool "Enable preboot"
1551         help
1552           When this option is enabled, the existence of the environment
1553           variable "preboot" will be checked immediately before starting the
1554           CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1555           entering interactive mode.
1556
1557           This feature is especially useful when "preboot" is automatically
1558           generated or modified. For example, the boot code can modify the
1559           "preboot" when a user holds down a certain combination of keys.
1560
1561 config PREBOOT
1562         string "preboot default value"
1563         depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1564         default "usb start" if USB_KEYBOARD
1565         default ""
1566         help
1567           This is the default of "preboot" environment variable.
1568
1569 config PREBOOT_DEFINED
1570         bool
1571         default y if PREBOOT != ""
1572
1573 config DEFAULT_FDT_FILE
1574         string "Default fdt file"
1575         help
1576           This option is used to set the default fdt file to boot OS.
1577
1578 config SAVE_PREV_BL_FDT_ADDR
1579         depends on ARM
1580         bool "Saves fdt address, passed by the previous bootloader, to env var"
1581         help
1582           When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1583           enable this option to save fdt address, passed by the
1584           previous bootloader for future use.
1585           Address is saved to `prevbl_fdt_addr` environment variable.
1586
1587           If no fdt was provided by previous bootloader, no env variables
1588           will be created.
1589
1590 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1591         depends on ARM
1592         bool "Saves initramfs address, passed by the previous bootloader, to env var"
1593         help
1594           When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1595           enable this option to save initramfs address, passed by the
1596           previous bootloader for future use.
1597           Address is saved to `prevbl_initrd_start_addr` environment variable.
1598
1599           If no initramfs was provided by previous bootloader, no env variables
1600           will be created.
1601
1602 menu "Configuration editor"
1603
1604 config CEDIT
1605         bool "Configuration editor"
1606         depends on BOOTSTD
1607         help
1608           Provides a way to deal with board configuration and present it to
1609           the user for adjustment.
1610
1611           This is intended to provide both graphical and text-based user
1612           interfaces, but only graphical is support at present.
1613
1614 endmenu         # Configuration editor
1615
1616 endmenu         # Booting