boot/Kconfig

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