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
259 Define this if you want to use the FAT file system for the environment.
263 Define this to a string that is the name of the block device.
265 - FAT_ENV_DEVICE_AND_PART:
267 Define this to a string to specify the partition of the device. It can
270 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
271 - "D:P": device D partition P. Error occurs if device D has no
274 - "D" or "D:": device D partition 1 if device D has partition
275 table, or the whole device D if has no partition
277 - "D:auto": first partition in device D with bootable flag set.
278 If none, first valid partition in device D. If no
279 partition table then means device D.
283 It's a string of the FAT file name. This file use to store the
287 This must be enabled. Otherwise it cannot save the environment file.
289 config ENV_IS_IN_FLASH
290 bool "Environment in flash memory"
291 depends on !CHAIN_OF_TRUST
293 Define this if you have a flash device which you want to use for the
296 a) The environment occupies one whole flash sector, which is
297 "embedded" in the text segment with the U-Boot code. This
298 happens usually with "bottom boot sector" or "top boot
299 sector" type flash chips, which have several smaller
300 sectors at the start or the end. For instance, such a
301 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
302 such a case you would place the environment in one of the
303 4 kB sectors - with U-Boot code before and after it. With
304 "top boot sector" type flash chips, you would put the
305 environment in one of the last sectors, leaving a gap
306 between U-Boot and the environment.
310 Offset of environment data (variable area) to the
311 beginning of flash memory; for instance, with bottom boot
312 type flash chips the second sector can be used: the offset
313 for this sector is given here.
315 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
319 This is just another way to specify the start address of
320 the flash sector containing the environment (instead of
323 CONFIG_ENV_SECT_SIZE:
325 Size of the sector containing the environment.
328 b) Sometimes flash chips have few, equal sized, BIG sectors.
329 In such a case you don't want to spend a whole sector for
334 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
335 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
336 of this flash sector for the environment. This saves
337 memory for the RAM copy of the environment.
339 It may also save flash memory if you decide to use this
340 when your environment is "embedded" within U-Boot code,
341 since then the remainder of the flash sector could be used
342 for U-Boot code. It should be pointed out that this is
343 STRONGLY DISCOURAGED from a robustness point of view:
344 updating the environment in flash makes it always
345 necessary to erase the WHOLE sector. If something goes
346 wrong before the contents has been restored from a copy in
347 RAM, your target system will be dead.
349 CONFIG_ENV_ADDR_REDUND
350 CONFIG_ENV_SIZE_REDUND
352 These settings describe a second storage area used to hold
353 a redundant copy of the environment data, so that there is
354 a valid backup copy in case there is a power failure during
355 a "saveenv" operation.
357 BE CAREFUL! Any changes to the flash layout, and some changes to the
358 source code will make it necessary to adapt <board>/u-boot.lds*
362 bool "Environment in an MMC device"
363 depends on !CHAIN_OF_TRUST
364 default y if ARCH_SUNXI
366 Define this if you have an MMC device which you want to use for the
369 CONFIG_SYS_MMC_ENV_DEV:
371 Specifies which MMC device the environment is stored in.
373 CONFIG_SYS_MMC_ENV_PART (optional):
375 Specifies which MMC partition the environment is stored in. If not
376 set, defaults to partition 0, the user area. Common values might be
377 1 (first MMC boot partition), 2 (second MMC boot partition).
382 These two #defines specify the offset and size of the environment
383 area within the specified MMC device.
385 If offset is positive (the usual case), it is treated as relative to
386 the start of the MMC partition. If offset is negative, it is treated
387 as relative to the end of the MMC partition. This can be useful if
388 your board may be fitted with different MMC devices, which have
389 different sizes for the MMC partitions, and you always want the
390 environment placed at the very end of the partition, to leave the
391 maximum possible space before it, to store other data.
393 These two values are in units of bytes, but must be aligned to an
396 CONFIG_ENV_OFFSET_REDUND (optional):
398 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
399 hold a redundant copy of the environment data. This provides a
400 valid backup copy in case the other copy is corrupted, e.g. due
401 to a power failure during a "saveenv" operation.
403 This value may also be positive or negative; this is handled in the
404 same way as CONFIG_ENV_OFFSET.
406 This value is also in units of bytes, but must also be aligned to
407 an MMC sector boundary.
409 CONFIG_ENV_SIZE_REDUND (optional):
411 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
412 set. If this value is set, it must be set to the same value as
415 config ENV_IS_IN_NAND
416 bool "Environment in a NAND device"
417 depends on !CHAIN_OF_TRUST
419 Define this if you have a NAND device which you want to use for the
425 These two #defines specify the offset and size of the environment
426 area within the first NAND device. CONFIG_ENV_OFFSET must be
427 aligned to an erase block boundary.
429 - CONFIG_ENV_OFFSET_REDUND (optional):
431 This setting describes a second storage area of CONFIG_ENV_SIZE
432 size used to hold a redundant copy of the environment data, so
433 that there is a valid backup copy in case there is a power failure
434 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
435 aligned to an erase block boundary.
437 - CONFIG_ENV_RANGE (optional):
439 Specifies the length of the region in which the environment
440 can be written. This should be a multiple of the NAND device's
441 block size. Specifying a range with more erase blocks than
442 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
443 the range to be avoided.
445 - CONFIG_ENV_OFFSET_OOB (optional):
447 Enables support for dynamically retrieving the offset of the
448 environment from block zero's out-of-band data. The
449 "nand env.oob" command can be used to record this offset.
450 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
451 using CONFIG_ENV_OFFSET_OOB.
453 config ENV_IS_IN_NVRAM
454 bool "Environment in a non-volatile RAM"
455 depends on !CHAIN_OF_TRUST
457 Define this if you have some non-volatile memory device
458 (NVRAM, battery buffered SRAM) which you want to use for the
464 These two #defines are used to determine the memory area you
465 want to use for environment. It is assumed that this memory
466 can just be read and written to, without any special
469 config ENV_IS_IN_ONENAND
470 bool "Environment is in OneNAND"
471 depends on !CHAIN_OF_TRUST
473 Define this if you want to put your local device's environment in
479 These two #defines are used to determine the device range you
480 want to use for environment. It is assumed that this memory
481 can just be read and written to, without any special
484 config ENV_IS_IN_REMOTE
485 bool "Environment is in remove memory space"
486 depends on !CHAIN_OF_TRUST
488 Define this if you have a remote memory space which you
489 want to use for the local device's environment.
494 These two #defines specify the address and size of the
495 environment area within the remote memory space. The
496 local device can get the environment from remote memory
497 space by SRIO or PCIE links.
499 config ENV_IS_IN_SPI_FLASH
500 bool "Environment is in SPI flash"
501 depends on !CHAIN_OF_TRUST
503 Define this if you have a SPI Flash memory device which you
504 want to use for the environment.
509 These two #defines specify the offset and size of the
510 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
511 aligned to an erase sector boundary.
513 - CONFIG_ENV_SECT_SIZE:
515 Define the SPI flash's sector size.
517 - CONFIG_ENV_OFFSET_REDUND (optional):
519 This setting describes a second storage area of CONFIG_ENV_SIZE
520 size used to hold a redundant copy of the environment data, so
521 that there is a valid backup copy in case there is a power failure
522 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
523 aligned to an erase sector boundary.
525 - CONFIG_ENV_SPI_BUS (optional):
526 - CONFIG_ENV_SPI_CS (optional):
528 Define the SPI bus and chip select. If not defined they will be 0.
530 - CONFIG_ENV_SPI_MAX_HZ (optional):
532 Define the SPI max work clock. If not defined then use 1MHz.
534 - CONFIG_ENV_SPI_MODE (optional):
536 Define the SPI work mode. If not defined then use SPI_MODE_3.
539 bool "Environment in a UBI volume"
540 depends on !CHAIN_OF_TRUST
542 Define this if you have an UBI volume that you want to use for the
543 environment. This has the benefit of wear-leveling the environment
544 accesses, which is important on NAND.
546 - CONFIG_ENV_UBI_PART:
548 Define this to a string that is the mtd partition containing the UBI.
550 - CONFIG_ENV_UBI_VOLUME:
552 Define this to the name of the volume that you want to store the
555 - CONFIG_ENV_UBI_VOLUME_REDUND:
557 Define this to the name of another volume to store a second copy of
558 the environment in. This will enable redundant environments in UBI.
559 It is assumed that both volumes are in the same MTD partition.
561 - CONFIG_UBI_SILENCE_MSG
562 - CONFIG_UBIFS_SILENCE_MSG
564 You will probably want to define these to avoid a really noisy system
565 when storing the env in UBI.
567 config ENV_IS_NOWHERE
568 bool "Environment is not stored"
570 Define this if you don't want to or can't have an environment stored
576 hex "Environment Offset"
577 depends on !ENV_IS_IN_UBI
578 depends on !ENV_IS_NOWHERE
579 default 0x88000 if ARCH_SUNXI
581 Offset from the start of the device (or partition)
584 hex "Environment Size"
585 depends on !ENV_IS_NOWHERE
586 default 0x20000 if ARCH_SUNXI
588 Size of the environment storage area
591 string "UBI partition name"
592 depends on ENV_IS_IN_UBI
594 MTD partition containing the UBI device
596 config ENV_UBI_VOLUME
597 string "UBI volume name"
598 depends on ENV_IS_IN_UBI
600 Name of the volume that you want to store the environment in.
607 int "delay in seconds before automatically booting"
611 Delay before automatically running bootcmd;
612 set to 0 to autoboot with no delay, but you can stop it by key input.
613 set to -1 to disable autoboot.
614 set to -2 to autoboot with no delay and not check for abort
616 See doc/README.autoboot for details.
623 This is the library functionality to provide a text-based menu of
624 choices for the user to make choices with.
626 config CONSOLE_RECORD
627 bool "Console recording"
629 This provides a way to record console output (and provide console
630 input) through circular buffers. This is mostly useful for testing.
631 Console output is recorded even when the console is silent.
632 To enable console recording, call console_record_reset_enable()
635 config CONSOLE_RECORD_OUT_SIZE
636 hex "Output buffer size"
637 depends on CONSOLE_RECORD
638 default 0x400 if CONSOLE_RECORD
640 Set the size of the console output buffer. When this fills up, no
641 more data will be recorded until some is removed. The buffer is
642 allocated immediately after the malloc() region is ready.
644 config CONSOLE_RECORD_IN_SIZE
645 hex "Input buffer size"
646 depends on CONSOLE_RECORD
647 default 0x100 if CONSOLE_RECORD
649 Set the size of the console input buffer. When this contains data,
650 tstc() and getc() will use this in preference to real device input.
651 The buffer is allocated immediately after the malloc() region is
655 string "Board specific string to be added to uboot version string"
657 This options adds the board specific name to u-boot version.
659 config SILENT_CONSOLE
660 bool "Support a silent console"
662 This option allows the console to be silenced, meaning that no
663 output will appear on the console devices. This is controlled by
664 setting the environment vaariable 'silent' to a non-empty value.
665 Note this also silences the console when booting Linux.
667 When the console is set up, the variable is checked, and the
668 GD_FLG_SILENT flag is set. Changing the environment variable later
669 will update the flag.
671 config SILENT_U_BOOT_ONLY
672 bool "Only silence the U-Boot console"
673 depends on SILENT_CONSOLE
675 Normally when the U-Boot console is silenced, Linux's console is
676 also silenced (assuming the board boots into Linux). This option
677 allows the linux console to operate normally, even if U-Boot's
680 config SILENT_CONSOLE_UPDATE_ON_SET
681 bool "Changes to the 'silent' environment variable update immediately"
682 depends on SILENT_CONSOLE
683 default y if SILENT_CONSOLE
685 When the 'silent' environment variable is changed, update the
686 console silence flag immediately. This allows 'setenv' to be used
687 to silence or un-silence the console.
689 The effect is that any change to the variable will affect the
692 config SILENT_CONSOLE_UPDATE_ON_RELOC
693 bool "Allow flags to take effect on relocation"
694 depends on SILENT_CONSOLE
696 In some cases the environment is not available until relocation
697 (e.g. NAND). This option makes the value of the 'silent'
698 environment variable take effect at relocation.
700 config PRE_CONSOLE_BUFFER
701 bool "Buffer characters before the console is available"
703 Prior to the console being initialised (i.e. serial UART
704 initialised etc) all console output is silently discarded.
705 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
706 buffer any console messages prior to the console being
707 initialised to a buffer. The buffer is a circular buffer, so
708 if it overflows, earlier output is discarded.
710 Note that this is not currently supported in SPL. It would be
711 useful to be able to share the pre-console buffer with SPL.
713 config PRE_CON_BUF_SZ
714 int "Sets the size of the pre-console buffer"
715 depends on PRE_CONSOLE_BUFFER
718 The size of the pre-console buffer affects how much console output
719 can be held before it overflows and starts discarding earlier
720 output. Normally there is very little output at this early stage,
721 unless debugging is enabled, so allow enough for ~10 lines of
724 This is a useful feature if you are using a video console and
725 want to see the full boot output on the console. Without this
726 option only the post-relocation output will be displayed.
728 config PRE_CON_BUF_ADDR
729 hex "Address of the pre-console buffer"
730 depends on PRE_CONSOLE_BUFFER
731 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
732 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
734 This sets the start address of the pre-console buffer. This must
735 be in available memory and is accessed before relocation and
736 possibly before DRAM is set up. Therefore choose an address
739 We should consider removing this option and allocating the memory
740 in board_init_f_init_reserve() instead.
743 bool "Enable console multiplexing"
744 default y if DM_VIDEO || VIDEO || LCD
746 This allows multiple devices to be used for each console 'file'.
747 For example, stdout can be set to go to serial and video.
748 Similarly, stdin can be set to come from serial and keyboard.
749 Input can be provided from either source. Console multiplexing
750 adds a small amount of size to U-Boot. Changes to the environment
751 variables stdout, stdin and stderr will take effect immediately.
753 config SYS_CONSOLE_IS_IN_ENV
754 bool "Select console devices from the environment"
755 default y if CONSOLE_MUX
757 This allows multiple input/output devices to be set at boot time.
758 For example, if stdout is set to "serial,video" then output will
759 be sent to both the serial and video devices on boot. The
760 environment variables can be updated after boot to change the
761 input/output devices.
763 config SYS_CONSOLE_OVERWRITE_ROUTINE
764 bool "Allow board control over console overwriting"
766 If this is enabled, and the board-specific function
767 overwrite_console() returns 1, the stdin, stderr and stdout are
768 switched to the serial port, else the settings in the environment
769 are used. If this is not enabled, the console will not be switched
772 config SYS_CONSOLE_ENV_OVERWRITE
773 bool "Update environment variables during console init"
775 The console environment variables (stdout, stdin, stderr) can be
776 used to determine the correct console devices on start-up. This
777 option writes the console devices to these variables on console
778 start-up (after relocation). This causes the environment to be
779 updated to match the console devices actually chosen.
781 config SYS_CONSOLE_INFO_QUIET
782 bool "Don't display the console devices on boot"
784 Normally U-Boot displays the current settings for stdout, stdin
785 and stderr on boot when the post-relocation console is set up.
786 Enable this option to supress this output. It can be obtained by
787 calling stdio_print_current_devices() from board code.
789 config SYS_STDIO_DEREGISTER
790 bool "Allow deregistering stdio devices"
791 default y if USB_KEYBOARD
793 Generally there is no need to deregister stdio devices since they
794 are never deactivated. But if a stdio device is used which can be
795 removed (for example a USB keyboard) then this option can be
796 enabled to ensure this is handled correctly.
801 bool "Support swapping dtbs at a later point in boot"
804 It is possible during initial boot you may need to use a generic
805 dtb until you can fully determine the board your running on. This
806 config allows boards to implement a function at a later point
807 during boot to switch to the "correct" dtb.
810 bool "Support a FIT image embedded in the U-boot image"
812 This option provides hooks to allow U-boot to parse an
813 appended FIT image and enable board specific code to then select
814 the correct DTB to be used.
816 config DEFAULT_FDT_FILE
817 string "Default fdt file"
819 This option is used to set the default fdt file to boot OS.
821 config VERSION_VARIABLE
822 bool "add U-Boot environment variable vers"
825 If this variable is defined, an environment variable
826 named "ver" is created by U-Boot showing the U-Boot
827 version as printed by the "version" command.
828 Any change to this variable will be reverted at the
831 config BOARD_LATE_INIT
834 Sometimes board require some initialization code that might
835 require once the actual init done, example saving board specific env,
836 boot-modes etc. which eventually done at late.
838 So this config enable the late init code with the help of board_late_init
839 function which should defined on respective boards.
841 config DISPLAY_CPUINFO
842 bool "Display information about the CPU during start up"
843 default y if ARM || NIOS2 || X86 || XTENSA
845 Display information about the CPU that U-Boot is running on
846 when U-Boot starts up. The function print_cpuinfo() is called
849 config DISPLAY_BOARDINFO
850 bool "Display information about the board during start up"
851 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
853 Display information about the board that U-Boot is running on
854 when U-Boot starts up. The board function checkboard() is called
857 menu "Start-up hooks"
859 config ARCH_EARLY_INIT_R
860 bool "Call arch-specific init soon after relocation"
863 With this option U-Boot will call arch_early_init_r() soon after
864 relocation. Driver model is running by this point, and the cache
865 is on. Note that board_early_init_r() is called first, if
866 enabled. This can be used to set up architecture-specific devices.
868 config ARCH_MISC_INIT
869 bool "Call arch-specific init after relocation, when console is ready"
871 With this option U-Boot will call arch_misc_init() after
872 relocation to allow miscellaneous arch-dependent initialisation
873 to be performed. This function should be defined by the board
874 and will be called after the console is set up, after relocaiton.
876 config BOARD_EARLY_INIT_F
877 bool "Call board-specific init before relocation"
880 Some boards need to perform initialisation as soon as possible
881 after boot. With this option, U-Boot calls board_early_init_f()
882 after driver model is ready in the pre-relocation init sequence.
883 Note that the normal serial console is not yet set up, but the
884 debug UART will be available if enabled.
888 menu "Security support"
891 bool # "Support hashing API (SHA1, SHA256, etc.)"
893 This provides a way to hash data in memory using various supported
894 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
895 and the algorithms it supports are defined in common/hash.c. See
896 also CMD_HASH for command-line access.
900 source "common/spl/Kconfig"