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