1menu "Boot timing" 2 3config BOOTSTAGE 4 bool "Boot timing and reporting" 5 help 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. 13 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 16 as the ID. 17 18 Calls to show_boot_progress() will also result in log entries but 19 these will not have names. 20 21config SPL_BOOTSTAGE 22 bool "Boot timing and reported in SPL" 23 depends on BOOTSTAGE 24 help 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 28 up. 29 30config BOOTSTAGE_REPORT 31 bool "Display a detailed boot timing report before booting the OS" 32 depends on BOOTSTAGE 33 help 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: 37 38 Timer summary in microseconds: 39 Mark Elapsed Stage 40 0 0 reset 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 48 49config BOOTSTAGE_USER_COUNT 50 int "Number of boot ID numbers available for user use" 51 default 20 52 help 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. 57 58config BOOTSTAGE_RECORD_COUNT 59 int "Number of boot stage records to store" 60 default 30 61 help 62 This is the size of the bootstage record list and is the maximum 63 number of bootstage records that can be recorded. 64 65config BOOTSTAGE_FDT 66 bool "Store boot timing information in the OS device tree" 67 depends on BOOTSTAGE 68 help 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. 74 For example: 75 76 bootstage { 77 154 { 78 name = "board_init_f"; 79 mark = <3575678>; 80 }; 81 170 { 82 name = "lcd"; 83 accum = <33482>; 84 }; 85 }; 86 87 Code in the Linux kernel can find this in /proc/devicetree. 88 89config BOOTSTAGE_STASH 90 bool "Stash the boot timing information in memory before booting OS" 91 depends on BOOTSTAGE 92 help 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 98 the command line. 99 100config BOOTSTAGE_STASH_ADDR 101 hex "Address to stash boot timing information" 102 default 0 103 help 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. 106 107config BOOTSTAGE_STASH_SIZE 108 hex "Size of boot timing stash region" 109 default 0x1000 110 help 111 This should be large enough to hold the bootstage stash. A value of 112 4096 (4KiB) is normally plenty. 113 114endmenu 115 116menu "Boot media" 117 118config NOR_BOOT 119 bool "Support for booting from NOR flash" 120 depends on NOR 121 help 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 125 NOR for environment. 126 127config NAND_BOOT 128 bool "Support for booting from NAND flash" 129 default n 130 help 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, 133 some not. 134 135config ONENAND_BOOT 136 bool "Support for booting from ONENAND" 137 default n 138 help 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, 141 some not. 142 143config QSPI_BOOT 144 bool "Support for booting from QSPI flash" 145 default n 146 help 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, 149 some not. 150 151config SATA_BOOT 152 bool "Support for booting from SATA" 153 default n 154 help 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, 157 some not. 158 159config SD_BOOT 160 bool "Support for booting from SD/EMMC" 161 default n 162 help 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, 165 some not. 166 167config SPI_BOOT 168 bool "Support for booting from SPI flash" 169 default n 170 help 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, 173 some not. 174 175endmenu 176 177menu "Environment" 178 179config ENV_IS_IN_DATAFLASH 180 bool "Environment in dataflash" 181 depends on !CHAIN_OF_TRUST 182 help 183 Define this if you have a DataFlash memory device which you 184 want to use for the environment. 185 186 - CONFIG_ENV_OFFSET: 187 - CONFIG_ENV_ADDR: 188 - CONFIG_ENV_SIZE: 189 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. 193 194config ENV_IS_IN_EEPROM 195 bool "Environment in EEPROM" 196 depends on !CHAIN_OF_TRUST 197 help 198 Use this if you have an EEPROM or similar serial access 199 device and a driver for it. 200 201 - CONFIG_ENV_OFFSET: 202 - CONFIG_ENV_SIZE: 203 204 These two #defines specify the offset and size of the 205 environment area within the total memory of your EEPROM. 206 207 - CONFIG_SYS_I2C_EEPROM_ADDR: 208 If defined, specified the chip address of the EEPROM device. 209 The default address is zero. 210 211 - CONFIG_SYS_I2C_EEPROM_BUS: 212 If defined, specified the i2c bus of the EEPROM device. 213 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. 218 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. 222 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! 226 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 232 byte chips. 233 234 Note that we consider the length of the address field to 235 still be one byte because the extra address bits are hidden 236 in the chip address. 237 238 - CONFIG_SYS_EEPROM_SIZE: 239 The size in bytes of the EEPROM device. 240 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. 244 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 248 EEPROM. For example: 249 250 #define CONFIG_I2C_ENV_EEPROM_BUS 1 251 252 EEPROM which holds the environment, is reached over 253 a pca9547 i2c mux with address 0x70, channel 3. 254 255config ENV_IS_IN_FLASH 256 bool "Environment in flash memory" 257 depends on !CHAIN_OF_TRUST 258 help 259 Define this if you have a flash device which you want to use for the 260 environment. 261 262 a) The environment occupies one whole flash sector, which is 263 "embedded" in the text segment with the U-Boot code. This 264 happens usually with "bottom boot sector" or "top boot 265 sector" type flash chips, which have several smaller 266 sectors at the start or the end. For instance, such a 267 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In 268 such a case you would place the environment in one of the 269 4 kB sectors - with U-Boot code before and after it. With 270 "top boot sector" type flash chips, you would put the 271 environment in one of the last sectors, leaving a gap 272 between U-Boot and the environment. 273 274 CONFIG_ENV_OFFSET: 275 276 Offset of environment data (variable area) to the 277 beginning of flash memory; for instance, with bottom boot 278 type flash chips the second sector can be used: the offset 279 for this sector is given here. 280 281 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE. 282 283 CONFIG_ENV_ADDR: 284 285 This is just another way to specify the start address of 286 the flash sector containing the environment (instead of 287 CONFIG_ENV_OFFSET). 288 289 CONFIG_ENV_SECT_SIZE: 290 291 Size of the sector containing the environment. 292 293 294 b) Sometimes flash chips have few, equal sized, BIG sectors. 295 In such a case you don't want to spend a whole sector for 296 the environment. 297 298 CONFIG_ENV_SIZE: 299 300 If you use this in combination with CONFIG_ENV_IS_IN_FLASH 301 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part 302 of this flash sector for the environment. This saves 303 memory for the RAM copy of the environment. 304 305 It may also save flash memory if you decide to use this 306 when your environment is "embedded" within U-Boot code, 307 since then the remainder of the flash sector could be used 308 for U-Boot code. It should be pointed out that this is 309 STRONGLY DISCOURAGED from a robustness point of view: 310 updating the environment in flash makes it always 311 necessary to erase the WHOLE sector. If something goes 312 wrong before the contents has been restored from a copy in 313 RAM, your target system will be dead. 314 315 CONFIG_ENV_ADDR_REDUND 316 CONFIG_ENV_SIZE_REDUND 317 318 These settings describe a second storage area used to hold 319 a redundant copy of the environment data, so that there is 320 a valid backup copy in case there is a power failure during 321 a "saveenv" operation. 322 323 BE CAREFUL! Any changes to the flash layout, and some changes to the 324 source code will make it necessary to adapt <board>/u-boot.lds* 325 accordingly! 326 327config ENV_IS_IN_MMC 328 bool "Environment in an MMC device" 329 depends on !CHAIN_OF_TRUST 330 default y if ARCH_SUNXI 331 help 332 Define this if you have an MMC device which you want to use for the 333 environment. 334 335 CONFIG_SYS_MMC_ENV_DEV: 336 337 Specifies which MMC device the environment is stored in. 338 339 CONFIG_SYS_MMC_ENV_PART (optional): 340 341 Specifies which MMC partition the environment is stored in. If not 342 set, defaults to partition 0, the user area. Common values might be 343 1 (first MMC boot partition), 2 (second MMC boot partition). 344 345 CONFIG_ENV_OFFSET: 346 CONFIG_ENV_SIZE: 347 348 These two #defines specify the offset and size of the environment 349 area within the specified MMC device. 350 351 If offset is positive (the usual case), it is treated as relative to 352 the start of the MMC partition. If offset is negative, it is treated 353 as relative to the end of the MMC partition. This can be useful if 354 your board may be fitted with different MMC devices, which have 355 different sizes for the MMC partitions, and you always want the 356 environment placed at the very end of the partition, to leave the 357 maximum possible space before it, to store other data. 358 359 These two values are in units of bytes, but must be aligned to an 360 MMC sector boundary. 361 362 CONFIG_ENV_OFFSET_REDUND (optional): 363 364 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to 365 hold a redundant copy of the environment data. This provides a 366 valid backup copy in case the other copy is corrupted, e.g. due 367 to a power failure during a "saveenv" operation. 368 369 This value may also be positive or negative; this is handled in the 370 same way as CONFIG_ENV_OFFSET. 371 372 This value is also in units of bytes, but must also be aligned to 373 an MMC sector boundary. 374 375 CONFIG_ENV_SIZE_REDUND (optional): 376 377 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is 378 set. If this value is set, it must be set to the same value as 379 CONFIG_ENV_SIZE. 380 381config ENV_IS_IN_NAND 382 bool "Environment in a NAND device" 383 depends on !CHAIN_OF_TRUST 384 help 385 Define this if you have a NAND device which you want to use for the 386 environment. 387 388 - CONFIG_ENV_OFFSET: 389 - CONFIG_ENV_SIZE: 390 391 These two #defines specify the offset and size of the environment 392 area within the first NAND device. CONFIG_ENV_OFFSET must be 393 aligned to an erase block boundary. 394 395 - CONFIG_ENV_OFFSET_REDUND (optional): 396 397 This setting describes a second storage area of CONFIG_ENV_SIZE 398 size used to hold a redundant copy of the environment data, so 399 that there is a valid backup copy in case there is a power failure 400 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 401 aligned to an erase block boundary. 402 403 - CONFIG_ENV_RANGE (optional): 404 405 Specifies the length of the region in which the environment 406 can be written. This should be a multiple of the NAND device's 407 block size. Specifying a range with more erase blocks than 408 are needed to hold CONFIG_ENV_SIZE allows bad blocks within 409 the range to be avoided. 410 411 - CONFIG_ENV_OFFSET_OOB (optional): 412 413 Enables support for dynamically retrieving the offset of the 414 environment from block zero's out-of-band data. The 415 "nand env.oob" command can be used to record this offset. 416 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when 417 using CONFIG_ENV_OFFSET_OOB. 418 419config ENV_IS_IN_NVRAM 420 bool "Environment in a non-volatile RAM" 421 depends on !CHAIN_OF_TRUST 422 help 423 Define this if you have some non-volatile memory device 424 (NVRAM, battery buffered SRAM) which you want to use for the 425 environment. 426 427 - CONFIG_ENV_ADDR: 428 - CONFIG_ENV_SIZE: 429 430 These two #defines are used to determine the memory area you 431 want to use for environment. It is assumed that this memory 432 can just be read and written to, without any special 433 provision. 434 435config ENV_IS_IN_SPI_FLASH 436 bool "Environment is in SPI flash" 437 depends on !CHAIN_OF_TRUST 438 help 439 Define this if you have a SPI Flash memory device which you 440 want to use for the environment. 441 442 - CONFIG_ENV_OFFSET: 443 - CONFIG_ENV_SIZE: 444 445 These two #defines specify the offset and size of the 446 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be 447 aligned to an erase sector boundary. 448 449 - CONFIG_ENV_SECT_SIZE: 450 451 Define the SPI flash's sector size. 452 453 - CONFIG_ENV_OFFSET_REDUND (optional): 454 455 This setting describes a second storage area of CONFIG_ENV_SIZE 456 size used to hold a redundant copy of the environment data, so 457 that there is a valid backup copy in case there is a power failure 458 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 459 aligned to an erase sector boundary. 460 461 - CONFIG_ENV_SPI_BUS (optional): 462 - CONFIG_ENV_SPI_CS (optional): 463 464 Define the SPI bus and chip select. If not defined they will be 0. 465 466 - CONFIG_ENV_SPI_MAX_HZ (optional): 467 468 Define the SPI max work clock. If not defined then use 1MHz. 469 470 - CONFIG_ENV_SPI_MODE (optional): 471 472 Define the SPI work mode. If not defined then use SPI_MODE_3. 473 474config ENV_IS_IN_UBI 475 bool "Environment in a UBI volume" 476 depends on !CHAIN_OF_TRUST 477 help 478 Define this if you have an UBI volume that you want to use for the 479 environment. This has the benefit of wear-leveling the environment 480 accesses, which is important on NAND. 481 482 - CONFIG_ENV_UBI_PART: 483 484 Define this to a string that is the mtd partition containing the UBI. 485 486 - CONFIG_ENV_UBI_VOLUME: 487 488 Define this to the name of the volume that you want to store the 489 environment in. 490 491 - CONFIG_ENV_UBI_VOLUME_REDUND: 492 493 Define this to the name of another volume to store a second copy of 494 the environment in. This will enable redundant environments in UBI. 495 It is assumed that both volumes are in the same MTD partition. 496 497 - CONFIG_UBI_SILENCE_MSG 498 - CONFIG_UBIFS_SILENCE_MSG 499 500 You will probably want to define these to avoid a really noisy system 501 when storing the env in UBI. 502 503config ENV_IS_NOWHERE 504 bool "Environment is not stored" 505 help 506 Define this if you don't want to or can't have an environment stored 507 on a storage medium 508 509if ARCH_SUNXI 510 511config ENV_OFFSET 512 hex "Environment Offset" 513 depends on !ENV_IS_IN_UBI 514 depends on !ENV_IS_NOWHERE 515 default 0x88000 if ARCH_SUNXI 516 help 517 Offset from the start of the device (or partition) 518 519config ENV_SIZE 520 hex "Environment Size" 521 depends on !ENV_IS_NOWHERE 522 default 0x20000 if ARCH_SUNXI 523 help 524 Size of the environment storage area 525 526config ENV_UBI_PART 527 string "UBI partition name" 528 depends on ENV_IS_IN_UBI 529 help 530 MTD partition containing the UBI device 531 532config ENV_UBI_VOLUME 533 string "UBI volume name" 534 depends on ENV_IS_IN_UBI 535 help 536 Name of the volume that you want to store the environment in. 537 538endif 539 540endmenu 541 542config BOOTDELAY 543 int "delay in seconds before automatically booting" 544 default 2 545 depends on AUTOBOOT 546 help 547 Delay before automatically running bootcmd; 548 set to 0 to autoboot with no delay, but you can stop it by key input. 549 set to -1 to disable autoboot. 550 set to -2 to autoboot with no delay and not check for abort 551 552 See doc/README.autoboot for details. 553 554menu "Console" 555 556config MENU 557 bool 558 help 559 This is the library functionality to provide a text-based menu of 560 choices for the user to make choices with. 561 562config CONSOLE_RECORD 563 bool "Console recording" 564 help 565 This provides a way to record console output (and provide console 566 input) through circular buffers. This is mostly useful for testing. 567 Console output is recorded even when the console is silent. 568 To enable console recording, call console_record_reset_enable() 569 from your code. 570 571config CONSOLE_RECORD_OUT_SIZE 572 hex "Output buffer size" 573 depends on CONSOLE_RECORD 574 default 0x400 if CONSOLE_RECORD 575 help 576 Set the size of the console output buffer. When this fills up, no 577 more data will be recorded until some is removed. The buffer is 578 allocated immediately after the malloc() region is ready. 579 580config CONSOLE_RECORD_IN_SIZE 581 hex "Input buffer size" 582 depends on CONSOLE_RECORD 583 default 0x100 if CONSOLE_RECORD 584 help 585 Set the size of the console input buffer. When this contains data, 586 tstc() and getc() will use this in preference to real device input. 587 The buffer is allocated immediately after the malloc() region is 588 ready. 589 590config IDENT_STRING 591 string "Board specific string to be added to uboot version string" 592 help 593 This options adds the board specific name to u-boot version. 594 595config SILENT_CONSOLE 596 bool "Support a silent console" 597 help 598 This option allows the console to be silenced, meaning that no 599 output will appear on the console devices. This is controlled by 600 setting the environment vaariable 'silent' to a non-empty value. 601 Note this also silences the console when booting Linux. 602 603 When the console is set up, the variable is checked, and the 604 GD_FLG_SILENT flag is set. Changing the environment variable later 605 will update the flag. 606 607config SILENT_U_BOOT_ONLY 608 bool "Only silence the U-Boot console" 609 depends on SILENT_CONSOLE 610 help 611 Normally when the U-Boot console is silenced, Linux's console is 612 also silenced (assuming the board boots into Linux). This option 613 allows the linux console to operate normally, even if U-Boot's 614 is silenced. 615 616config SILENT_CONSOLE_UPDATE_ON_SET 617 bool "Changes to the 'silent' environment variable update immediately" 618 depends on SILENT_CONSOLE 619 default y if SILENT_CONSOLE 620 help 621 When the 'silent' environment variable is changed, update the 622 console silence flag immediately. This allows 'setenv' to be used 623 to silence or un-silence the console. 624 625 The effect is that any change to the variable will affect the 626 GD_FLG_SILENT flag. 627 628config SILENT_CONSOLE_UPDATE_ON_RELOC 629 bool "Allow flags to take effect on relocation" 630 depends on SILENT_CONSOLE 631 help 632 In some cases the environment is not available until relocation 633 (e.g. NAND). This option makes the value of the 'silent' 634 environment variable take effect at relocation. 635 636config PRE_CONSOLE_BUFFER 637 bool "Buffer characters before the console is available" 638 help 639 Prior to the console being initialised (i.e. serial UART 640 initialised etc) all console output is silently discarded. 641 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to 642 buffer any console messages prior to the console being 643 initialised to a buffer. The buffer is a circular buffer, so 644 if it overflows, earlier output is discarded. 645 646 Note that this is not currently supported in SPL. It would be 647 useful to be able to share the pre-console buffer with SPL. 648 649config PRE_CON_BUF_SZ 650 int "Sets the size of the pre-console buffer" 651 depends on PRE_CONSOLE_BUFFER 652 default 4096 653 help 654 The size of the pre-console buffer affects how much console output 655 can be held before it overflows and starts discarding earlier 656 output. Normally there is very little output at this early stage, 657 unless debugging is enabled, so allow enough for ~10 lines of 658 text. 659 660 This is a useful feature if you are using a video console and 661 want to see the full boot output on the console. Without this 662 option only the post-relocation output will be displayed. 663 664config PRE_CON_BUF_ADDR 665 hex "Address of the pre-console buffer" 666 depends on PRE_CONSOLE_BUFFER 667 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I 668 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I 669 help 670 This sets the start address of the pre-console buffer. This must 671 be in available memory and is accessed before relocation and 672 possibly before DRAM is set up. Therefore choose an address 673 carefully. 674 675 We should consider removing this option and allocating the memory 676 in board_init_f_init_reserve() instead. 677 678config CONSOLE_MUX 679 bool "Enable console multiplexing" 680 default y if DM_VIDEO || VIDEO || LCD 681 help 682 This allows multiple devices to be used for each console 'file'. 683 For example, stdout can be set to go to serial and video. 684 Similarly, stdin can be set to come from serial and keyboard. 685 Input can be provided from either source. Console multiplexing 686 adds a small amount of size to U-Boot. Changes to the environment 687 variables stdout, stdin and stderr will take effect immediately. 688 689config SYS_CONSOLE_IS_IN_ENV 690 bool "Select console devices from the environment" 691 default y if CONSOLE_MUX 692 help 693 This allows multiple input/output devices to be set at boot time. 694 For example, if stdout is set to "serial,video" then output will 695 be sent to both the serial and video devices on boot. The 696 environment variables can be updated after boot to change the 697 input/output devices. 698 699config SYS_CONSOLE_OVERWRITE_ROUTINE 700 bool "Allow board control over console overwriting" 701 help 702 If this is enabled, and the board-specific function 703 overwrite_console() returns 1, the stdin, stderr and stdout are 704 switched to the serial port, else the settings in the environment 705 are used. If this is not enabled, the console will not be switched 706 to serial. 707 708config SYS_CONSOLE_ENV_OVERWRITE 709 bool "Update environment variables during console init" 710 help 711 The console environment variables (stdout, stdin, stderr) can be 712 used to determine the correct console devices on start-up. This 713 option writes the console devices to these variables on console 714 start-up (after relocation). This causes the environment to be 715 updated to match the console devices actually chosen. 716 717config SYS_CONSOLE_INFO_QUIET 718 bool "Don't display the console devices on boot" 719 help 720 Normally U-Boot displays the current settings for stdout, stdin 721 and stderr on boot when the post-relocation console is set up. 722 Enable this option to supress this output. It can be obtained by 723 calling stdio_print_current_devices() from board code. 724 725config SYS_STDIO_DEREGISTER 726 bool "Allow deregistering stdio devices" 727 default y if USB_KEYBOARD 728 help 729 Generally there is no need to deregister stdio devices since they 730 are never deactivated. But if a stdio device is used which can be 731 removed (for example a USB keyboard) then this option can be 732 enabled to ensure this is handled correctly. 733 734endmenu 735 736config DTB_RESELECT 737 bool "Support swapping dtbs at a later point in boot" 738 depends on FIT_EMBED 739 help 740 It is possible during initial boot you may need to use a generic 741 dtb until you can fully determine the board your running on. This 742 config allows boards to implement a function at a later point 743 during boot to switch to the "correct" dtb. 744 745config FIT_EMBED 746 bool "Support a FIT image embedded in the U-boot image" 747 help 748 This option provides hooks to allow U-boot to parse an 749 appended FIT image and enable board specific code to then select 750 the correct DTB to be used. 751 752config DEFAULT_FDT_FILE 753 string "Default fdt file" 754 help 755 This option is used to set the default fdt file to boot OS. 756 757config VERSION_VARIABLE 758 bool "add U-Boot environment variable vers" 759 default n 760 help 761 If this variable is defined, an environment variable 762 named "ver" is created by U-Boot showing the U-Boot 763 version as printed by the "version" command. 764 Any change to this variable will be reverted at the 765 next reset. 766 767config BOARD_LATE_INIT 768 bool 769 help 770 Sometimes board require some initialization code that might 771 require once the actual init done, example saving board specific env, 772 boot-modes etc. which eventually done at late. 773 774 So this config enable the late init code with the help of board_late_init 775 function which should defined on respective boards. 776 777config DISPLAY_CPUINFO 778 bool "Display information about the CPU during start up" 779 default y if ARM || NIOS2 || X86 || XTENSA 780 help 781 Display information about the CPU that U-Boot is running on 782 when U-Boot starts up. The function print_cpuinfo() is called 783 to do this. 784 785config DISPLAY_BOARDINFO 786 bool "Display information about the board during start up" 787 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA 788 help 789 Display information about the board that U-Boot is running on 790 when U-Boot starts up. The board function checkboard() is called 791 to do this. 792 793menu "Start-up hooks" 794 795config ARCH_EARLY_INIT_R 796 bool "Call arch-specific init soon after relocation" 797 default y if X86 798 help 799 With this option U-Boot will call arch_early_init_r() soon after 800 relocation. Driver model is running by this point, and the cache 801 is on. Note that board_early_init_r() is called first, if 802 enabled. This can be used to set up architecture-specific devices. 803 804config ARCH_MISC_INIT 805 bool "Call arch-specific init after relocation, when console is ready" 806 help 807 With this option U-Boot will call arch_misc_init() after 808 relocation to allow miscellaneous arch-dependent initialisation 809 to be performed. This function should be defined by the board 810 and will be called after the console is set up, after relocaiton. 811 812config BOARD_EARLY_INIT_F 813 bool "Call board-specific init before relocation" 814 default y if X86 815 help 816 Some boards need to perform initialisation as soon as possible 817 after boot. With this option, U-Boot calls board_early_init_f() 818 after driver model is ready in the pre-relocation init sequence. 819 Note that the normal serial console is not yet set up, but the 820 debug UART will be available if enabled. 821 822endmenu 823 824menu "Security support" 825 826config HASH 827 bool # "Support hashing API (SHA1, SHA256, etc.)" 828 help 829 This provides a way to hash data in memory using various supported 830 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h 831 and the algorithms it supports are defined in common/hash.c. See 832 also CMD_HASH for command-line access. 833 834endmenu 835 836source "common/spl/Kconfig" 837