4 bool "Boot timing and reporting"
6 Enable recording of boot time while booting. To use it, insert
7 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
8 bootstage.h. Only a single entry is recorded for each ID. You can
9 give the entry a name with bootstage_mark_name(). You can also
10 record elapsed time in a particular stage using bootstage_start()
11 before starting and bootstage_accum() when finished. Bootstage will
12 add up all the accumulated time and report it.
14 Normally, IDs are defined in bootstage.h but a small number of
15 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
18 Calls to show_boot_progress() will also result in log entries but
19 these will not have names.
22 bool "Boot timing and reported in SPL"
25 Enable recording of boot time in SPL. To make this visible to U-Boot
26 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
27 information when SPL finishes and load it when U-Boot proper starts
30 config BOOTSTAGE_REPORT
31 bool "Display a detailed boot timing report before booting the OS"
34 Enable output of a boot time report just before the OS is booted.
35 This shows how long it took U-Boot to go through each stage of the
36 boot process. The report looks something like this:
38 Timer summary in microseconds:
41 3,575,678 3,575,678 board_init_f start
42 3,575,695 17 arch_cpu_init A9
43 3,575,777 82 arch_cpu_init done
44 3,659,598 83,821 board_init_r start
45 3,910,375 250,777 main_loop
46 29,916,167 26,005,792 bootm_start
47 30,361,327 445,160 start_kernel
49 config BOOTSTAGE_USER_COUNT
50 int "Number of boot ID numbers available for user use"
53 This is the number of available user bootstage records.
54 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
55 a new ID will be allocated from this stash. If you exceed
56 the limit, recording will stop.
58 config BOOTSTAGE_RECORD_COUNT
59 int "Number of boot stage records to store"
62 This is the size of the bootstage record list and is the maximum
63 number of bootstage records that can be recorded.
66 bool "Store boot timing information in the OS device tree"
69 Stash the bootstage information in the FDT. A root 'bootstage'
70 node is created with each bootstage id as a child. Each child
71 has a 'name' property and either 'mark' containing the
72 mark time in microseconds, or 'accum' containing the
73 accumulated time for that bootstage id in microseconds.
78 name = "board_init_f";
87 Code in the Linux kernel can find this in /proc/devicetree.
89 config BOOTSTAGE_STASH
90 bool "Stash the boot timing information in memory before booting OS"
93 Some OSes do not support device tree. Bootstage can instead write
94 the boot timing information in a binary format at a given address.
95 This happens through a call to bootstage_stash(), typically in
96 the CPU's cleanup_before_linux() function. You can use the
97 'bootstage stash' and 'bootstage unstash' commands to do this on
100 config BOOTSTAGE_STASH_ADDR
101 hex "Address to stash boot timing information"
104 Provide an address which will not be overwritten by the OS when it
105 starts, so that it can read this information when ready.
107 config BOOTSTAGE_STASH_SIZE
108 hex "Size of boot timing stash region"
111 This should be large enough to hold the bootstage stash. A value of
112 4096 (4KiB) is normally plenty.
119 bool "Support for booting from NOR flash"
122 Enabling this will make a U-Boot binary that is capable of being
123 booted via NOR. In this case we will enable certain pinmux early
124 as the ROM only partially sets up pinmux. We also default to using
128 bool "Support for booting from NAND flash"
131 Enabling this will make a U-Boot binary that is capable of being
132 booted via NAND flash. This is not a must, some SoCs need this,
136 bool "Support for booting from ONENAND"
139 Enabling this will make a U-Boot binary that is capable of being
140 booted via ONENAND. This is not a must, some SoCs need this,
144 bool "Support for booting from QSPI flash"
147 Enabling this will make a U-Boot binary that is capable of being
148 booted via QSPI flash. This is not a must, some SoCs need this,
152 bool "Support for booting from SATA"
155 Enabling this will make a U-Boot binary that is capable of being
156 booted via SATA. This is not a must, some SoCs need this,
160 bool "Support for booting from SD/EMMC"
163 Enabling this will make a U-Boot binary that is capable of being
164 booted via SD/EMMC. This is not a must, some SoCs need this,
168 bool "Support for booting from SPI flash"
171 Enabling this will make a U-Boot binary that is capable of being
172 booted via SPI flash. This is not a must, some SoCs need this,
179 config ENV_IS_IN_DATAFLASH
180 bool "Environment in dataflash"
181 depends on !CHAIN_OF_TRUST
183 Define this if you have a DataFlash memory device which you
184 want to use for the environment.
190 These three #defines specify the offset and size of the
191 environment area within the total memory of your DataFlash placed
192 at the specified address.
194 config ENV_IS_IN_EEPROM
195 bool "Environment in EEPROM"
196 depends on !CHAIN_OF_TRUST
198 Use this if you have an EEPROM or similar serial access
199 device and a driver for it.
204 These two #defines specify the offset and size of the
205 environment area within the total memory of your EEPROM.
207 - CONFIG_SYS_I2C_EEPROM_ADDR:
208 If defined, specified the chip address of the EEPROM device.
209 The default address is zero.
211 - CONFIG_SYS_I2C_EEPROM_BUS:
212 If defined, specified the i2c bus of the EEPROM device.
214 - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
215 If defined, the number of bits used to address bytes in a
216 single page in the EEPROM device. A 64 byte page, for example
217 would require six bits.
219 - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
220 If defined, the number of milliseconds to delay between
221 page writes. The default is zero milliseconds.
223 - CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
224 The length in bytes of the EEPROM memory array address. Note
225 that this is NOT the chip address length!
227 - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
228 EEPROM chips that implement "address overflow" are ones
229 like Catalyst 24WC04/08/16 which has 9/10/11 bits of
230 address and the extra bits end up in the "chip address" bit
231 slots. This makes a 24WC08 (1Kbyte) chip look like four 256
234 Note that we consider the length of the address field to
235 still be one byte because the extra address bits are hidden
238 - CONFIG_SYS_EEPROM_SIZE:
239 The size in bytes of the EEPROM device.
241 - CONFIG_ENV_EEPROM_IS_ON_I2C
242 define this, if you have I2C and SPI activated, and your
243 EEPROM, which holds the environment, is on the I2C bus.
245 - CONFIG_I2C_ENV_EEPROM_BUS
246 if you have an Environment on an EEPROM reached over
247 I2C muxes, you can define here, how to reach this
250 #define CONFIG_I2C_ENV_EEPROM_BUS 1
252 EEPROM which holds the environment, is reached over
253 a pca9547 i2c mux with address 0x70, channel 3.
256 bool "Environment is in a FAT filesystem"
257 depends on !CHAIN_OF_TRUST
260 Define this if you want to use the FAT file system for the environment.
264 This must be enabled. Otherwise it cannot save the environment file.
266 config ENV_IS_IN_FLASH
267 bool "Environment in flash memory"
268 depends on !CHAIN_OF_TRUST
270 Define this if you have a flash device which you want to use for the
273 a) The environment occupies one whole flash sector, which is
274 "embedded" in the text segment with the U-Boot code. This
275 happens usually with "bottom boot sector" or "top boot
276 sector" type flash chips, which have several smaller
277 sectors at the start or the end. For instance, such a
278 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
279 such a case you would place the environment in one of the
280 4 kB sectors - with U-Boot code before and after it. With
281 "top boot sector" type flash chips, you would put the
282 environment in one of the last sectors, leaving a gap
283 between U-Boot and the environment.
287 Offset of environment data (variable area) to the
288 beginning of flash memory; for instance, with bottom boot
289 type flash chips the second sector can be used: the offset
290 for this sector is given here.
292 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
296 This is just another way to specify the start address of
297 the flash sector containing the environment (instead of
300 CONFIG_ENV_SECT_SIZE:
302 Size of the sector containing the environment.
305 b) Sometimes flash chips have few, equal sized, BIG sectors.
306 In such a case you don't want to spend a whole sector for
311 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
312 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
313 of this flash sector for the environment. This saves
314 memory for the RAM copy of the environment.
316 It may also save flash memory if you decide to use this
317 when your environment is "embedded" within U-Boot code,
318 since then the remainder of the flash sector could be used
319 for U-Boot code. It should be pointed out that this is
320 STRONGLY DISCOURAGED from a robustness point of view:
321 updating the environment in flash makes it always
322 necessary to erase the WHOLE sector. If something goes
323 wrong before the contents has been restored from a copy in
324 RAM, your target system will be dead.
326 CONFIG_ENV_ADDR_REDUND
327 CONFIG_ENV_SIZE_REDUND
329 These settings describe a second storage area used to hold
330 a redundant copy of the environment data, so that there is
331 a valid backup copy in case there is a power failure during
332 a "saveenv" operation.
334 BE CAREFUL! Any changes to the flash layout, and some changes to the
335 source code will make it necessary to adapt <board>/u-boot.lds*
339 bool "Environment in an MMC device"
340 depends on !CHAIN_OF_TRUST
341 default y if ARCH_SUNXI
343 Define this if you have an MMC device which you want to use for the
346 CONFIG_SYS_MMC_ENV_DEV:
348 Specifies which MMC device the environment is stored in.
350 CONFIG_SYS_MMC_ENV_PART (optional):
352 Specifies which MMC partition the environment is stored in. If not
353 set, defaults to partition 0, the user area. Common values might be
354 1 (first MMC boot partition), 2 (second MMC boot partition).
359 These two #defines specify the offset and size of the environment
360 area within the specified MMC device.
362 If offset is positive (the usual case), it is treated as relative to
363 the start of the MMC partition. If offset is negative, it is treated
364 as relative to the end of the MMC partition. This can be useful if
365 your board may be fitted with different MMC devices, which have
366 different sizes for the MMC partitions, and you always want the
367 environment placed at the very end of the partition, to leave the
368 maximum possible space before it, to store other data.
370 These two values are in units of bytes, but must be aligned to an
373 CONFIG_ENV_OFFSET_REDUND (optional):
375 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
376 hold a redundant copy of the environment data. This provides a
377 valid backup copy in case the other copy is corrupted, e.g. due
378 to a power failure during a "saveenv" operation.
380 This value may also be positive or negative; this is handled in the
381 same way as CONFIG_ENV_OFFSET.
383 This value is also in units of bytes, but must also be aligned to
384 an MMC sector boundary.
386 CONFIG_ENV_SIZE_REDUND (optional):
388 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
389 set. If this value is set, it must be set to the same value as
392 config ENV_IS_IN_NAND
393 bool "Environment in a NAND device"
394 depends on !CHAIN_OF_TRUST
396 Define this if you have a NAND device which you want to use for the
402 These two #defines specify the offset and size of the environment
403 area within the first NAND device. CONFIG_ENV_OFFSET must be
404 aligned to an erase block boundary.
406 - CONFIG_ENV_OFFSET_REDUND (optional):
408 This setting describes a second storage area of CONFIG_ENV_SIZE
409 size used to hold a redundant copy of the environment data, so
410 that there is a valid backup copy in case there is a power failure
411 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
412 aligned to an erase block boundary.
414 - CONFIG_ENV_RANGE (optional):
416 Specifies the length of the region in which the environment
417 can be written. This should be a multiple of the NAND device's
418 block size. Specifying a range with more erase blocks than
419 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
420 the range to be avoided.
422 - CONFIG_ENV_OFFSET_OOB (optional):
424 Enables support for dynamically retrieving the offset of the
425 environment from block zero's out-of-band data. The
426 "nand env.oob" command can be used to record this offset.
427 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
428 using CONFIG_ENV_OFFSET_OOB.
430 config ENV_IS_IN_NVRAM
431 bool "Environment in a non-volatile RAM"
432 depends on !CHAIN_OF_TRUST
434 Define this if you have some non-volatile memory device
435 (NVRAM, battery buffered SRAM) which you want to use for the
441 These two #defines are used to determine the memory area you
442 want to use for environment. It is assumed that this memory
443 can just be read and written to, without any special
446 config ENV_IS_IN_ONENAND
447 bool "Environment is in OneNAND"
448 depends on !CHAIN_OF_TRUST
450 Define this if you want to put your local device's environment in
456 These two #defines are used to determine the device range you
457 want to use for environment. It is assumed that this memory
458 can just be read and written to, without any special
461 config ENV_IS_IN_REMOTE
462 bool "Environment is in remove memory space"
463 depends on !CHAIN_OF_TRUST
465 Define this if you have a remote memory space which you
466 want to use for the local device's environment.
471 These two #defines specify the address and size of the
472 environment area within the remote memory space. The
473 local device can get the environment from remote memory
474 space by SRIO or PCIE links.
476 config ENV_IS_IN_SPI_FLASH
477 bool "Environment is in SPI flash"
478 depends on !CHAIN_OF_TRUST
480 Define this if you have a SPI Flash memory device which you
481 want to use for the environment.
486 These two #defines specify the offset and size of the
487 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
488 aligned to an erase sector boundary.
490 - CONFIG_ENV_SECT_SIZE:
492 Define the SPI flash's sector size.
494 - CONFIG_ENV_OFFSET_REDUND (optional):
496 This setting describes a second storage area of CONFIG_ENV_SIZE
497 size used to hold a redundant copy of the environment data, so
498 that there is a valid backup copy in case there is a power failure
499 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
500 aligned to an erase sector boundary.
502 - CONFIG_ENV_SPI_BUS (optional):
503 - CONFIG_ENV_SPI_CS (optional):
505 Define the SPI bus and chip select. If not defined they will be 0.
507 - CONFIG_ENV_SPI_MAX_HZ (optional):
509 Define the SPI max work clock. If not defined then use 1MHz.
511 - CONFIG_ENV_SPI_MODE (optional):
513 Define the SPI work mode. If not defined then use SPI_MODE_3.
516 bool "Environment in a UBI volume"
517 depends on !CHAIN_OF_TRUST
519 Define this if you have an UBI volume that you want to use for the
520 environment. This has the benefit of wear-leveling the environment
521 accesses, which is important on NAND.
523 - CONFIG_ENV_UBI_PART:
525 Define this to a string that is the mtd partition containing the UBI.
527 - CONFIG_ENV_UBI_VOLUME:
529 Define this to the name of the volume that you want to store the
532 - CONFIG_ENV_UBI_VOLUME_REDUND:
534 Define this to the name of another volume to store a second copy of
535 the environment in. This will enable redundant environments in UBI.
536 It is assumed that both volumes are in the same MTD partition.
538 - CONFIG_UBI_SILENCE_MSG
539 - CONFIG_UBIFS_SILENCE_MSG
541 You will probably want to define these to avoid a really noisy system
542 when storing the env in UBI.
544 config ENV_IS_NOWHERE
545 bool "Environment is not stored"
547 Define this if you don't want to or can't have an environment stored
550 config ENV_FAT_INTERFACE
551 string "Name of the block device for the environment"
552 depends on ENV_IS_IN_FAT
553 default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
555 Define this to a string that is the name of the block device.
557 config ENV_FAT_DEVICE_AND_PART
558 string "Device and partition for where to store the environemt in FAT"
559 depends on ENV_IS_IN_FAT
560 default "0:1" if TI_COMMON_CMD_OPTIONS
561 default "0:auto" if ARCH_ZYNQMP
562 default "0" if ARCH_AT91
564 Define this to a string to specify the partition of the device. It can
567 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
568 - "D:P": device D partition P. Error occurs if device D has no
571 - "D" or "D:": device D partition 1 if device D has partition
572 table, or the whole device D if has no partition
574 - "D:auto": first partition in device D with bootable flag set.
575 If none, first valid partition in device D. If no
576 partition table then means device D.
579 string "Name of the FAT file to use for the environemnt"
580 depends on ENV_IS_IN_FAT
583 It's a string of the FAT file name. This file use to store the
589 hex "Environment Offset"
590 depends on !ENV_IS_IN_UBI
591 depends on !ENV_IS_NOWHERE
592 default 0x88000 if ARCH_SUNXI
594 Offset from the start of the device (or partition)
597 hex "Environment Size"
598 depends on !ENV_IS_NOWHERE
599 default 0x20000 if ARCH_SUNXI
601 Size of the environment storage area
604 string "UBI partition name"
605 depends on ENV_IS_IN_UBI
607 MTD partition containing the UBI device
609 config ENV_UBI_VOLUME
610 string "UBI volume name"
611 depends on ENV_IS_IN_UBI
613 Name of the volume that you want to store the environment in.
620 int "delay in seconds before automatically booting"
624 Delay before automatically running bootcmd;
625 set to 0 to autoboot with no delay, but you can stop it by key input.
626 set to -1 to disable autoboot.
627 set to -2 to autoboot with no delay and not check for abort
629 See doc/README.autoboot for details.
632 bool "Enable boot arguments"
634 Provide boot arguments to bootm command. Boot arguments are specified
635 in CONFIG_BOOTARGS option. Enable this option to be able to specify
636 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
637 will be undefined and won't take any space in U-Boot image.
640 string "Boot arguments"
641 depends on USE_BOOTARGS
643 This can be used to pass arguments to the bootm command. The value of
644 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
645 this value will also override the "chosen" node in FDT blob.
652 This is the library functionality to provide a text-based menu of
653 choices for the user to make choices with.
655 config CONSOLE_RECORD
656 bool "Console recording"
658 This provides a way to record console output (and provide console
659 input) through circular buffers. This is mostly useful for testing.
660 Console output is recorded even when the console is silent.
661 To enable console recording, call console_record_reset_enable()
664 config CONSOLE_RECORD_OUT_SIZE
665 hex "Output buffer size"
666 depends on CONSOLE_RECORD
667 default 0x400 if CONSOLE_RECORD
669 Set the size of the console output buffer. When this fills up, no
670 more data will be recorded until some is removed. The buffer is
671 allocated immediately after the malloc() region is ready.
673 config CONSOLE_RECORD_IN_SIZE
674 hex "Input buffer size"
675 depends on CONSOLE_RECORD
676 default 0x100 if CONSOLE_RECORD
678 Set the size of the console input buffer. When this contains data,
679 tstc() and getc() will use this in preference to real device input.
680 The buffer is allocated immediately after the malloc() region is
684 string "Board specific string to be added to uboot version string"
686 This options adds the board specific name to u-boot version.
688 config SILENT_CONSOLE
689 bool "Support a silent console"
691 This option allows the console to be silenced, meaning that no
692 output will appear on the console devices. This is controlled by
693 setting the environment vaariable 'silent' to a non-empty value.
694 Note this also silences the console when booting Linux.
696 When the console is set up, the variable is checked, and the
697 GD_FLG_SILENT flag is set. Changing the environment variable later
698 will update the flag.
700 config SILENT_U_BOOT_ONLY
701 bool "Only silence the U-Boot console"
702 depends on SILENT_CONSOLE
704 Normally when the U-Boot console is silenced, Linux's console is
705 also silenced (assuming the board boots into Linux). This option
706 allows the linux console to operate normally, even if U-Boot's
709 config SILENT_CONSOLE_UPDATE_ON_SET
710 bool "Changes to the 'silent' environment variable update immediately"
711 depends on SILENT_CONSOLE
712 default y if SILENT_CONSOLE
714 When the 'silent' environment variable is changed, update the
715 console silence flag immediately. This allows 'setenv' to be used
716 to silence or un-silence the console.
718 The effect is that any change to the variable will affect the
721 config SILENT_CONSOLE_UPDATE_ON_RELOC
722 bool "Allow flags to take effect on relocation"
723 depends on SILENT_CONSOLE
725 In some cases the environment is not available until relocation
726 (e.g. NAND). This option makes the value of the 'silent'
727 environment variable take effect at relocation.
729 config PRE_CONSOLE_BUFFER
730 bool "Buffer characters before the console is available"
732 Prior to the console being initialised (i.e. serial UART
733 initialised etc) all console output is silently discarded.
734 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
735 buffer any console messages prior to the console being
736 initialised to a buffer. The buffer is a circular buffer, so
737 if it overflows, earlier output is discarded.
739 Note that this is not currently supported in SPL. It would be
740 useful to be able to share the pre-console buffer with SPL.
742 config PRE_CON_BUF_SZ
743 int "Sets the size of the pre-console buffer"
744 depends on PRE_CONSOLE_BUFFER
747 The size of the pre-console buffer affects how much console output
748 can be held before it overflows and starts discarding earlier
749 output. Normally there is very little output at this early stage,
750 unless debugging is enabled, so allow enough for ~10 lines of
753 This is a useful feature if you are using a video console and
754 want to see the full boot output on the console. Without this
755 option only the post-relocation output will be displayed.
757 config PRE_CON_BUF_ADDR
758 hex "Address of the pre-console buffer"
759 depends on PRE_CONSOLE_BUFFER
760 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
761 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
763 This sets the start address of the pre-console buffer. This must
764 be in available memory and is accessed before relocation and
765 possibly before DRAM is set up. Therefore choose an address
768 We should consider removing this option and allocating the memory
769 in board_init_f_init_reserve() instead.
772 bool "Enable console multiplexing"
773 default y if DM_VIDEO || VIDEO || LCD
775 This allows multiple devices to be used for each console 'file'.
776 For example, stdout can be set to go to serial and video.
777 Similarly, stdin can be set to come from serial and keyboard.
778 Input can be provided from either source. Console multiplexing
779 adds a small amount of size to U-Boot. Changes to the environment
780 variables stdout, stdin and stderr will take effect immediately.
782 config SYS_CONSOLE_IS_IN_ENV
783 bool "Select console devices from the environment"
784 default y if CONSOLE_MUX
786 This allows multiple input/output devices to be set at boot time.
787 For example, if stdout is set to "serial,video" then output will
788 be sent to both the serial and video devices on boot. The
789 environment variables can be updated after boot to change the
790 input/output devices.
792 config SYS_CONSOLE_OVERWRITE_ROUTINE
793 bool "Allow board control over console overwriting"
795 If this is enabled, and the board-specific function
796 overwrite_console() returns 1, the stdin, stderr and stdout are
797 switched to the serial port, else the settings in the environment
798 are used. If this is not enabled, the console will not be switched
801 config SYS_CONSOLE_ENV_OVERWRITE
802 bool "Update environment variables during console init"
804 The console environment variables (stdout, stdin, stderr) can be
805 used to determine the correct console devices on start-up. This
806 option writes the console devices to these variables on console
807 start-up (after relocation). This causes the environment to be
808 updated to match the console devices actually chosen.
810 config SYS_CONSOLE_INFO_QUIET
811 bool "Don't display the console devices on boot"
813 Normally U-Boot displays the current settings for stdout, stdin
814 and stderr on boot when the post-relocation console is set up.
815 Enable this option to supress this output. It can be obtained by
816 calling stdio_print_current_devices() from board code.
818 config SYS_STDIO_DEREGISTER
819 bool "Allow deregistering stdio devices"
820 default y if USB_KEYBOARD
822 Generally there is no need to deregister stdio devices since they
823 are never deactivated. But if a stdio device is used which can be
824 removed (for example a USB keyboard) then this option can be
825 enabled to ensure this is handled correctly.
830 bool "Support swapping dtbs at a later point in boot"
833 It is possible during initial boot you may need to use a generic
834 dtb until you can fully determine the board your running on. This
835 config allows boards to implement a function at a later point
836 during boot to switch to the "correct" dtb.
839 bool "Support a FIT image embedded in the U-boot image"
841 This option provides hooks to allow U-boot to parse an
842 appended FIT image and enable board specific code to then select
843 the correct DTB to be used.
845 config DEFAULT_FDT_FILE
846 string "Default fdt file"
848 This option is used to set the default fdt file to boot OS.
850 config VERSION_VARIABLE
851 bool "add U-Boot environment variable vers"
854 If this variable is defined, an environment variable
855 named "ver" is created by U-Boot showing the U-Boot
856 version as printed by the "version" command.
857 Any change to this variable will be reverted at the
860 config BOARD_LATE_INIT
863 Sometimes board require some initialization code that might
864 require once the actual init done, example saving board specific env,
865 boot-modes etc. which eventually done at late.
867 So this config enable the late init code with the help of board_late_init
868 function which should defined on respective boards.
870 config DISPLAY_CPUINFO
871 bool "Display information about the CPU during start up"
872 default y if ARM || NIOS2 || X86 || XTENSA
874 Display information about the CPU that U-Boot is running on
875 when U-Boot starts up. The function print_cpuinfo() is called
878 config DISPLAY_BOARDINFO
879 bool "Display information about the board during start up"
880 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
882 Display information about the board that U-Boot is running on
883 when U-Boot starts up. The board function checkboard() is called
886 menu "Start-up hooks"
888 config ARCH_EARLY_INIT_R
889 bool "Call arch-specific init soon after relocation"
891 With this option U-Boot will call arch_early_init_r() soon after
892 relocation. Driver model is running by this point, and the cache
893 is on. Note that board_early_init_r() is called first, if
894 enabled. This can be used to set up architecture-specific devices.
896 config ARCH_MISC_INIT
897 bool "Call arch-specific init after relocation, when console is ready"
899 With this option U-Boot will call arch_misc_init() after
900 relocation to allow miscellaneous arch-dependent initialisation
901 to be performed. This function should be defined by the board
902 and will be called after the console is set up, after relocaiton.
904 config BOARD_EARLY_INIT_F
905 bool "Call board-specific init before relocation"
907 Some boards need to perform initialisation as soon as possible
908 after boot. With this option, U-Boot calls board_early_init_f()
909 after driver model is ready in the pre-relocation init sequence.
910 Note that the normal serial console is not yet set up, but the
911 debug UART will be available if enabled.
915 menu "Security support"
918 bool # "Support hashing API (SHA1, SHA256, etc.)"
920 This provides a way to hash data in memory using various supported
921 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
922 and the algorithms it supports are defined in common/hash.c. See
923 also CMD_HASH for command-line access.
927 source "common/spl/Kconfig"