6 This is the library functionality to provide a text-based menu of
7 choices for the user to make choices with.
10 bool "Console recording"
12 This provides a way to record console output (and provide console
13 input) through circular buffers. This is mostly useful for testing.
14 Console output is recorded even when the console is silent.
15 To enable console recording, call console_record_reset_enable()
18 config CONSOLE_RECORD_INIT_F
19 bool "Enable console recording during pre-relocation init"
20 depends on CONSOLE_RECORD && SYS_MALLOC_F
23 This option enables console recording during pre-relocation init.
24 CONFIG_SYS_MALLOC_F must be enabled to use this feature.
26 config CONSOLE_RECORD_OUT_SIZE
27 hex "Output buffer size"
28 depends on CONSOLE_RECORD
29 default 0x400 if CONSOLE_RECORD
31 Set the size of the console output buffer. When this fills up, no
32 more data will be recorded until some is removed. The buffer is
33 allocated immediately after the malloc() region is ready.
35 config CONSOLE_RECORD_OUT_SIZE_F
36 hex "Output buffer size before relocation"
37 depends on CONSOLE_RECORD
38 default 0x400 if CONSOLE_RECORD
40 Set the size of the console output buffer before relocation. When
41 this fills up, no more data will be recorded until some is removed.
42 The buffer is allocated immediately after the early malloc() region is
45 config CONSOLE_RECORD_IN_SIZE
46 hex "Input buffer size"
47 depends on CONSOLE_RECORD
48 default 0x100 if CONSOLE_RECORD
50 Set the size of the console input buffer. When this contains data,
51 tstc() and getc() will use this in preference to real device input.
52 The buffer is allocated immediately after the malloc() region is
55 config DISABLE_CONSOLE
56 bool "Add functionality to disable console completely"
58 Disable console (in & out).
61 string "Board specific string to be added to uboot version string"
63 This options adds the board specific name to u-boot version.
70 All Messages with a loglevel smaller than the console loglevel will
71 be compiled in. The loglevels are defined as follows:
82 9 - debug hardware I/O
95 int "loglevel for VPL"
99 All Messages with a loglevel smaller than the console loglevel will
100 be compiled in to VPL. See LOGLEVEL for a list of available log
101 levels. Setting this to a value above 4 may increase the code size
104 config SILENT_CONSOLE
105 bool "Support a silent console"
107 This option allows the console to be silenced, meaning that no
108 output will appear on the console devices. This is controlled by
109 setting the environment variable 'silent' to a non-empty value.
110 Note this also silences the console when booting Linux.
112 When the console is set up, the variable is checked, and the
113 GD_FLG_SILENT flag is set. Changing the environment variable later
114 will update the flag.
116 config SPL_SILENT_CONSOLE
117 bool "Use a silent console in SPL"
118 default y if SILENT_CONSOLE && !SANDBOX
120 This selects a silent console in SPL. When enabled it drops some
121 output messages. The GD_FLG_SILENT flag is not used in SPL so there
122 is no run-time control of console messages in SPL.
124 Future work may allow the SPL console to be silenced completely using
127 config TPL_SILENT_CONSOLE
128 bool "Use a silent console in TPL"
129 default y if SILENT_CONSOLE && !SANDBOX
131 This selects a silent console in TPL. When enabled it drops some
132 output messages. The GD_FLG_SILENT flag is not used in TPL so there
133 is no run-time control of console messages in TPL.
135 Future work may allow the TPL console to be silenced completely using
138 config SILENT_U_BOOT_ONLY
139 bool "Only silence the U-Boot console"
140 depends on SILENT_CONSOLE
142 Normally when the U-Boot console is silenced, Linux's console is
143 also silenced (assuming the board boots into Linux). This option
144 allows the linux console to operate normally, even if U-Boot's
147 config SILENT_CONSOLE_UPDATE_ON_SET
148 bool "Changes to the 'silent' environment variable update immediately"
149 depends on SILENT_CONSOLE
150 default y if SILENT_CONSOLE
152 When the 'silent' environment variable is changed, update the
153 console silence flag immediately. This allows 'setenv' to be used
154 to silence or un-silence the console.
156 The effect is that any change to the variable will affect the
159 config SILENT_CONSOLE_UPDATE_ON_RELOC
160 bool "Allow flags to take effect on relocation"
161 depends on SILENT_CONSOLE
163 In some cases the environment is not available until relocation
164 (e.g. NAND). This option makes the value of the 'silent'
165 environment variable take effect at relocation.
167 config SILENT_CONSOLE_UNTIL_ENV
168 bool "Keep console silent until environment is loaded"
169 depends on SILENT_CONSOLE
171 This option makes sure U-Boot will never use the console unless the
172 environment from flash does not contain the 'silent' variable. If
173 set, the console is kept silent until after the environment was
174 loaded. Use this in combination with PRE_CONSOLE_BUFFER to print out
175 earlier messages after loading the environment when allowed.
177 config PRE_CONSOLE_BUFFER
178 bool "Buffer characters before the console is available"
180 Prior to the console being initialised (i.e. serial UART
181 initialised etc) all console output is silently discarded.
182 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
183 buffer any console messages prior to the console being
184 initialised to a buffer. The buffer is a circular buffer, so
185 if it overflows, earlier output is discarded.
187 Note that this is not currently supported in SPL. It would be
188 useful to be able to share the pre-console buffer with SPL.
190 config PRE_CON_BUF_SZ
191 int "Sets the size of the pre-console buffer"
192 depends on PRE_CONSOLE_BUFFER
195 The size of the pre-console buffer affects how much console output
196 can be held before it overflows and starts discarding earlier
197 output. Normally there is very little output at this early stage,
198 unless debugging is enabled, so allow enough for ~10 lines of
201 This is a useful feature if you are using a video console and
202 want to see the full boot output on the console. Without this
203 option only the post-relocation output will be displayed.
205 config PRE_CON_BUF_ADDR
206 hex "Address of the pre-console buffer"
207 depends on PRE_CONSOLE_BUFFER
208 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
209 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
210 default 0x0f000000 if ROCKCHIP_RK3288
211 default 0x0f200000 if ROCKCHIP_RK3399
213 This sets the start address of the pre-console buffer. This must
214 be in available memory and is accessed before relocation and
215 possibly before DRAM is set up. Therefore choose an address
218 We should consider removing this option and allocating the memory
219 in board_init_f_init_reserve() instead.
221 config CONSOLE_FLUSH_SUPPORT
222 bool "Enable console flush support"
225 This enables compilation of flush() function for console flush support.
228 bool "Enable console multiplexing"
229 default y if VIDEO || VIDEO || LCD
231 This allows multiple devices to be used for each console 'file'.
232 For example, stdout can be set to go to serial and video.
233 Similarly, stdin can be set to come from serial and keyboard.
234 Input can be provided from either source. Console multiplexing
235 adds a small amount of size to U-Boot. Changes to the environment
236 variables stdout, stdin and stderr will take effect immediately.
238 config SYS_CONSOLE_IS_IN_ENV
239 bool "Select console devices from the environment"
240 default y if CONSOLE_MUX
242 This allows multiple input/output devices to be set at boot time.
243 For example, if stdout is set to "serial,vidconsole" then output
244 will be sent to both the serial and video devices on boot. The
245 environment variables can be updated after boot to change the
246 input/output devices.
248 config SYS_CONSOLE_OVERWRITE_ROUTINE
249 bool "Allow board control over console overwriting"
251 If this is enabled, and the board-specific function
252 overwrite_console() returns 1, the stdin, stderr and stdout are
253 switched to the serial port, else the settings in the environment
254 are used. If this is not enabled, the console will not be switched
257 config SYS_CONSOLE_ENV_OVERWRITE
258 bool "Update environment variables during console init"
260 The console environment variables (stdout, stdin, stderr) can be
261 used to determine the correct console devices on start-up. This
262 option writes the console devices to these variables on console
263 start-up (after relocation). This causes the environment to be
264 updated to match the console devices actually chosen.
266 config SYS_CONSOLE_INFO_QUIET
267 bool "Don't display the console devices on boot"
269 Normally U-Boot displays the current settings for stdout, stdin
270 and stderr on boot when the post-relocation console is set up.
271 Enable this option to suppress this output. It can be obtained by
272 calling stdio_print_current_devices() from board code.
274 config SYS_STDIO_DEREGISTER
275 bool "Allow deregistering stdio devices"
276 default y if USB_KEYBOARD
278 Generally there is no need to deregister stdio devices since they
279 are never deactivated. But if a stdio device is used which can be
280 removed (for example a USB keyboard) then this option can be
281 enabled to ensure this is handled correctly.
283 config SPL_SYS_STDIO_DEREGISTER
284 bool "Allow deregistering stdio devices in SPL"
286 Generally there is no need to deregister stdio devices since they
287 are never deactivated. But if a stdio device is used which can be
288 removed (for example a USB keyboard) then this option can be
289 enabled to ensure this is handled correctly. This is very rarely
292 config SYS_DEVICE_NULLDEV
293 bool "Enable a null device for stdio"
294 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
296 Enable creation of a "nulldev" stdio device. This allows silent
297 operation of the console by setting stdout to "nulldev". Enable
298 this to use a serial console under board control.
305 bool "Enable logging support"
308 This enables support for logging of status and debug messages. These
309 can be displayed on the console, recorded in a memory buffer, or
310 discarded if not needed. Logging supports various categories and
316 int "Maximum log level to record"
320 This selects the maximum log level that will be recorded. Any value
321 higher than this will be ignored. If possible log statements below
322 this level will be discarded at build time. Levels:
333 9 - debug hardware I/O
335 config LOG_DEFAULT_LEVEL
336 int "Default logging level to display"
337 default LOG_MAX_LEVEL
338 range 0 LOG_MAX_LEVEL
340 This is the default logging level set when U-Boot starts. It can
341 be adjusted later using the 'log level' command. Note that setting
342 this to a value above LOG_MAX_LEVEL will be ineffective, since the
343 higher levels are not compiled in to U-Boot.
354 9 - debug hardware I/O
357 bool "Allow log output to the console"
360 Enables a log driver which writes log records to the console.
361 Generally the console is the serial port or LCD display. Only the
362 log message is shown - other details like level, category, file and
363 line number are omitted.
366 bool "Show source file name in log messages by default"
368 Show the source file name in log messages by default. This value
369 can be overridden using the 'log format' command.
372 bool "Show source line number in log messages by default"
374 Show the source line number in log messages by default. This value
375 can be overridden using the 'log format' command.
378 bool "Show function name in log messages by default"
380 Show the function name in log messages by default. This value can
381 be overridden using the 'log format' command.
384 int "Number of characters to use for function"
387 Sets the field width to use when showing the function. Set this to
388 a larger value if you have lots of long function names, and want
392 bool "Log output to syslog server"
395 Enables a log driver which broadcasts log records via UDP port 514
399 bool "Enable logging support in SPL"
400 depends on LOG && SPL
402 This enables support for logging of status and debug messages. These
403 can be displayed on the console, recorded in a memory buffer, or
404 discarded if not needed. Logging supports various categories and
409 config SPL_LOG_MAX_LEVEL
410 int "Maximum log level to record in SPL"
415 This selects the maximum log level that will be recorded. Any value
416 higher than this will be ignored. If possible log statements below
417 this level will be discarded at build time. Levels:
428 9 - debug hardware I/O
430 config SPL_LOG_CONSOLE
431 bool "Allow log output to the console in SPL"
434 Enables a log driver which writes log records to the console.
435 Generally the console is the serial port or LCD display. Only the
436 log message is shown - other details like level, category, file and
437 line number are omitted.
442 bool "Enable logging support in TPL"
443 depends on LOG && TPL
445 This enables support for logging of status and debug messages. These
446 can be displayed on the console, recorded in a memory buffer, or
447 discarded if not needed. Logging supports various categories and
452 config TPL_LOG_MAX_LEVEL
453 int "Maximum log level to record in TPL"
458 This selects the maximum log level that will be recorded. Any value
459 higher than this will be ignored. If possible log statements below
460 this level will be discarded at build time. Levels:
471 9 - debug hardware I/O
473 config TPL_LOG_CONSOLE
474 bool "Allow log output to the console in TPL"
477 Enables a log driver which writes log records to the console.
478 Generally the console is the serial port or LCD display. Only the
479 log message is shown - other details like level, category, file and
480 line number are omitted.
485 bool "Enable logging support in VPL"
486 depends on LOG && VPL
488 This enables support for logging of status and debug messages. These
489 can be displayed on the console, recorded in a memory buffer, or
490 discarded if not needed. Logging supports various categories and
495 config VPL_LOG_MAX_LEVEL
496 int "Maximum log level to record in VPL"
499 This selects the maximum log level that will be recorded. Any value
500 higher than this will be ignored. If possible log statements below
501 this level will be discarded at build time. Levels:
512 9 - debug hardware I/O
514 config VPL_LOG_CONSOLE
515 bool "Allow log output to the console in VPL"
518 Enables a log driver which writes log records to the console.
519 Generally the console is the serial port or LCD display. Only the
520 log message is shown - other details like level, category, file and
521 line number are omitted.
525 config LOG_ERROR_RETURN
526 bool "Log all functions which return an error"
528 When an error is returned in U-Boot it is sometimes difficult to
529 figure out the root cause. For example, reading from SPI flash may
530 fail due to a problem in the SPI controller or due to the flash part
531 not returning the expected information. This option changes
532 log_ret() to log any errors it sees. With this option disabled,
535 You can add log_ret() to all functions which return an error code.
538 bool "Provide a test for logging"
542 This enables a 'log test' command to test logging. It is normally
543 executed from a pytest and simply outputs logging information
544 in various different ways to test that the logging system works
545 correctly with various settings.
554 bool "Call get_board_type() to get and display the board type"
556 If this option is enabled, checkboard() will call get_board_type()
557 to get a string containing the board type and this will be
558 displayed immediately after the model is shown on the console
561 config DISPLAY_CPUINFO
562 bool "Display information about the CPU during start up"
563 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
565 Display information about the CPU that U-Boot is running on
566 when U-Boot starts up. The function print_cpuinfo() is called
569 config DISPLAY_BOARDINFO
570 bool "Display information about the board during early start up"
571 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
573 Display information about the board that U-Boot is running on
574 when U-Boot starts up. The board function checkboard() is called
577 config DISPLAY_BOARDINFO_LATE
578 bool "Display information about the board during late start up"
580 Display information about the board that U-Boot is running on after
581 the relocation phase. The board function checkboard() is called to do
584 menu "Start-up hooks"
587 bool "General-purpose cyclic execution mechanism"
589 This enables a general-purpose cyclic execution infrastructure,
590 to allow "small" (run-time wise) functions to be executed at
591 a specified frequency. Things like LED blinking or watchdog
592 triggering are examples for such tasks.
596 config CYCLIC_MAX_CPU_TIME_US
597 int "Sets the max allowed time for a cyclic function in us"
600 The max allowed time for a cyclic function in us. If a functions
601 takes longer than this duration this function will get unregistered
607 bool "General-purpose event-handling mechanism"
610 This enables sending and processing of events, to allow interested
611 parties to be alerted when something happens. This is an attempt to
612 stem the flow of weak functions, hooks, functions in board_f.c
613 and board_r.c and the Kconfig options below.
615 See doc/develop/event.rst for more information.
620 bool "Support event registration at runtime"
623 Enable this to support adding an event spy at runtime, without adding
624 it to the EVENT_SPy() linker list. This increases code size slightly
625 but provides more flexibility for boards and subsystems that need it.
628 bool "Enable event debugging assistance"
631 Enable this get usefui features for seeing what is happening with
632 events, such as event-type names. This adds to the code size of
633 U-Boot so can be turned off for production builds.
637 config ARCH_EARLY_INIT_R
638 bool "Call arch-specific init soon after relocation"
640 With this option U-Boot will call arch_early_init_r() soon after
641 relocation. Driver model is running by this point, and the cache
642 is on. Note that board_early_init_r() is called first, if
643 enabled. This can be used to set up architecture-specific devices.
645 config ARCH_MISC_INIT
646 bool "Call arch-specific init after relocation, when console is ready"
648 With this option U-Boot will call arch_misc_init() after
649 relocation to allow miscellaneous arch-dependent initialisation
650 to be performed. This function should be defined by the board
651 and will be called after the console is set up, after relocation.
653 config BOARD_EARLY_INIT_F
654 bool "Call board-specific init before relocation"
656 Some boards need to perform initialisation as soon as possible
657 after boot. With this option, U-Boot calls board_early_init_f()
658 after driver model is ready in the pre-relocation init sequence.
659 Note that the normal serial console is not yet set up, but the
660 debug UART will be available if enabled.
662 config BOARD_EARLY_INIT_R
663 bool "Call board-specific init after relocation"
665 Some boards need to perform initialisation as directly after
666 relocation. With this option, U-Boot calls board_early_init_r()
667 in the post-relocation init sequence.
669 config BOARD_POSTCLK_INIT
670 bool "Call board_postclk_init"
672 Some boards need this to initialize select items, after clocks /
673 timebase and before env / serial.
675 config BOARD_LATE_INIT
676 bool "Execute Board late init"
678 Sometimes board require some initialization code that might
679 require once the actual init done, example saving board specific env,
680 boot-modes etc. which eventually done at late.
682 So this config enable the late init code with the help of board_late_init
683 function which should defined on respective boards.
686 bool "Call set_cpu_clk_info"
690 bool "hwconfig infrastructure"
691 default y if PPC || ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
695 depends on ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3 || \
696 (FSL_ESDHC_IMX && (ARCH_MX5 || ARCH_MX6 || ARCH_MX7))
699 Enable to call get_clocks() in board_init_f() for platforms other
700 than PowerPC or M68k. This is a legacy option. If not TARGET_BRPPT2
702 config LAST_STAGE_INIT
703 bool "Call board-specific as last setup step"
705 Some boards need to perform initialisation immediately before control
706 is passed to the command-line interpreter (e.g. for initializations
707 that depend on later phases in the init sequence). With this option,
708 U-Boot calls last_stage_init() before the command-line interpreter is
712 bool "Execute Misc Init"
713 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
714 default y if ARCH_OMAP2PLUS && !AM33XX
716 Enabling this option calls 'misc_init_r' function
718 config SYS_MALLOC_BOOTPARAMS
719 bool "Malloc a buffer to use for bootparams"
721 In some cases rather than using a known location to store the
722 bi_boot_params portion of gd we need to allocate it from our malloc pool.
724 config SYS_BOOTPARAMS_LEN
725 hex "Size of the bootparam buffer to malloc in bytes"
726 depends on SYS_MALLOC_BOOTPARAMS
727 default 0x20000 if MIPS || RCAR_GEN3
731 bool "Enable I2C connected system identifier EEPROM"
733 A number of different systems and vendors enable a vendor-specified
734 EEPROM that contains various identifying features.
736 config SYS_EEPROM_BUS_NUM
737 int "I2C bus number of the system identifier EEPROM"
742 prompt "EEPROM starts with 'CCID' or 'NXID'"
743 depends on ID_EEPROM && (PPC || ARCH_LS1021A || FSL_LAYERSCAPE)
744 default SYS_I2C_EEPROM_NXID
746 Specify if the Freescale / NXP ID EEPROM starts with 'CCID' or 'NXID'
747 ASCII literal string.
749 config SYS_I2C_EEPROM_CCID
750 bool "EEPROM starts with 'CCID'"
752 config SYS_I2C_EEPROM_NXID
753 bool "EEPROM starts with 'NXID'"
758 bool "Enumerate PCI buses during init"
761 With this option U-Boot will call pci_init() soon after relocation,
762 which will enumerate PCI buses. This is needed, for instance, in the
763 case of DM PCI-based Ethernet devices, which will not be detected
764 without having the enumeration performed earlier.
767 bool "Reset ethernet PHY during init"
769 Implement reset_phy() in board code if required to reset the ethernet
774 endmenu # Init options
776 menu "Security support"
779 bool # "Support hashing API (SHA1, SHA256, etc.)"
781 This provides a way to hash data in memory using various supported
782 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
783 and the algorithms it supports are defined in common/hash.c. See
784 also CMD_HASH for command-line access.
787 bool "Build Android Verified Boot operations"
790 depends on PARTITION_UUIDS
792 This option enables compilation of bootloader-dependent operations,
793 used by Android Verified Boot 2.0 library (libavb). Includes:
794 * Helpers to process strings in order to build OS bootargs.
795 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
796 * Helpers to alloc/init/free avb ops.
801 hex "Define AVB buffer address"
802 default FASTBOOT_BUF_ADDR
804 AVB requires a buffer for memory transactions. This variable defines the
808 hex "Define AVB buffer SIZE"
809 default FASTBOOT_BUF_SIZE
811 AVB requires a buffer for memory transactions. This variable defines the
817 bool "Build SCP03 - Secure Channel Protocol O3 - controls"
818 depends on OPTEE || SANDBOX
821 This option allows U-Boot to enable and or provision SCP03 on an OPTEE
822 controlled Secured Element.
825 bool # "Support hashing API (SHA1, SHA256, etc.)"
827 This provides a way to hash data in memory using various supported
828 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
829 and the algorithms it supports are defined in common/hash.c. See
830 also CMD_HASH for command-line access.
833 bool # "Support hashing API (SHA1, SHA256, etc.)"
835 This provides a way to hash data in memory using various supported
836 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
837 and the algorithms it supports are defined in common/hash.c. See
838 also CMD_HASH for command-line access.
840 config STACKPROTECTOR
841 bool "Stack Protector buffer overflow detection"
843 Enable stack smash detection through compiler's stack-protector
846 config SPL_STACKPROTECTOR
847 bool "Stack Protector buffer overflow detection for SPL"
848 depends on STACKPROTECTOR && SPL
850 config TPL_STACKPROTECTOR
851 bool "Stack Protector buffer overflow detection for TPL"
852 depends on STACKPROTECTOR && TPL
854 config BOARD_RNG_SEED
855 bool "Provide /chosen/rng-seed property to the linux kernel"
857 Selecting this option requires the board to define a
858 board_rng_seed() function, which should return a buffer
859 which will be used to populate the /chosen/rng-seed property
860 in the device tree for the OS being booted.
862 It is up to the board code (and more generally the whole
863 BSP) where and how to store (or generate) such a seed, how
864 to ensure a given seed is only used once, how to create a
865 new seed for use on subsequent boots, and whether or not the
866 kernel should account any entropy from the given seed.
870 menu "Update support"
877 bool "Auto-update using fitImage via TFTP"
881 This option allows performing update of NOR with data in fitImage
884 config UPDATE_TFTP_CNT_MAX
885 int "The number of connection retries during auto-update"
887 depends on UPDATE_TFTP
889 config UPDATE_TFTP_MSEC_MAX
890 int "Delay in mSec to wait for the TFTP server during auto-update"
892 depends on UPDATE_TFTP
895 bool "Firmware update using fitImage"
900 This option allows performing update of DFU-capable storage with
904 bool "Android A/B updates"
906 If enabled, adds support for the new Android A/B update model. This
907 allows the bootloader to select which slot to boot from based on the
908 information provided by userspace via the Android boot_ctrl HAL. This
909 allows a bootloader to try a new version of the system but roll back
910 to previous version if the new one didn't boot all the way.
917 bool "Support for a bloblist"
919 This enables support for a bloblist in U-Boot, which can be passed
920 from TPL to SPL to U-Boot proper (and potentially to Linux). The
921 blob list supports multiple binary blobs of data, each with a tag,
922 so that different U-Boot components can store data which can survive
923 through to the next phase of the boot.
926 bool "Support for a bloblist in SPL"
927 depends on BLOBLIST && SPL_LIBGENERIC_SUPPORT && SPL_LIBCOMMON_SUPPORT
930 This enables a bloblist in SPL. If this is the first part of U-Boot
931 to run, then the bloblist is set up in SPL and passed to U-Boot
932 proper. If TPL also has a bloblist, then SPL uses the one from there.
935 bool "Support for a bloblist in TPL"
936 depends on BLOBLIST && TPL_LIBGENERIC_SUPPORT && TPL_LIBCOMMON_SUPPORT
939 This enables a bloblist in TPL. The bloblist is set up in TPL and
940 passed to SPL and U-Boot proper.
943 bool "Support for a bloblist in VPL"
944 depends on BLOBLIST && VPL_LIBGENERIC_SUPPORT && VPL_LIBCOMMON_SUPPORT
947 This enables a bloblist in VPL. The bloblist is set up in VPL and
948 passed to SPL and U-Boot proper.
953 prompt "Bloblist location"
955 Select the location of the bloblist, via various means.
957 config BLOBLIST_FIXED
958 bool "Place bloblist at a fixed address in memory"
960 Select this to used a fixed memory address for the bloblist. If the
961 bloblist exists at this address from a previous phase, it used as is.
962 If not it is created at this address in U-Boot.
964 config BLOBLIST_ALLOC
965 bool "Allocate bloblist"
967 Allocate the bloblist using malloc(). This avoids the need to
968 specify a fixed address on systems where this is unknown or can
974 hex "Address of bloblist"
975 default 0xc000 if SANDBOX
976 depends on BLOBLIST_FIXED
978 Sets the address of the bloblist, set up by the first part of U-Boot
979 which runs. Subsequent U-Boot phases typically use the same address.
981 This is not used if BLOBLIST_ALLOC is selected.
984 hex "Size of bloblist"
987 Sets the size of the bloblist in bytes. This must include all
988 overhead (alignment, bloblist header, record header). The bloblist
989 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
990 proper), and this sane bloblist is used for subsequent phases.
992 config BLOBLIST_SIZE_RELOC
993 hex "Size of bloblist after relocation"
994 default BLOBLIST_SIZE if BLOBLIST_FIXED || BLOBLIST_ALLOC
995 default 0 if BLOBLIST_PASSAGE
997 Sets the size of the bloblist in bytes after relocation. Since U-Boot
998 has a lot more memory available then, it is possible to use a larger
999 size than the one set up by SPL. This bloblist is set up during the
1007 prompt "Bloblist location in SPL"
1009 Select the location of the bloblist, via various means. Typically
1010 you should use the same value for SPL as for U-Boot, since they need
1011 to look in the same place. But if BLOBLIST_ALLOC is used, then a
1012 fresh bloblist will be created each time, since there is no shared
1013 address (between phases) for the bloblist.
1015 config SPL_BLOBLIST_FIXED
1016 bool "Place bloblist at a fixed address in memory"
1018 Select this to used a fixed memory address for the bloblist. If the
1019 bloblist exists at this address from a previous phase, it used as is.
1020 If not it is created at this address in SPL.
1022 config SPL_BLOBLIST_ALLOC
1023 bool "Allocate bloblist"
1025 Allocate the bloblist using malloc(). This avoids the need to
1026 specify a fixed address on systems where this is unknown or can
1031 endif # SPL_BLOBLIST
1036 prompt "Bloblist location in TPL"
1038 Select the location of the bloblist, via various means. Typically
1039 you should use the same value for SPL as for U-Boot, since they need
1040 to look in the same place. But if BLOBLIST_ALLOC is used, then a
1041 fresh bloblist will be created each time, since there is no shared
1042 address (between phases) for the bloblist.
1044 config TPL_BLOBLIST_FIXED
1045 bool "Place bloblist at a fixed address in memory"
1047 Select this to used a fixed memory address for the bloblist. If the
1048 bloblist exists at this address from a previous phase, it used as is.
1049 If not it is created at this address in TPL.
1051 config TPL_BLOBLIST_ALLOC
1052 bool "Allocate bloblist"
1054 Allocate the bloblist using malloc(). This avoids the need to
1055 specify a fixed address on systems where this is unknown or can
1060 endif # TPL_BLOBLIST
1064 source "common/spl/Kconfig"
1066 config IMAGE_SIGN_INFO
1071 Enable image_sign_info helper functions.
1075 config SPL_IMAGE_SIGN_INFO
1080 Enable image_sign_info helper functions in SPL.
1082 config VPL_IMAGE_SIGN_INFO
1087 Enable image_sign_info helper functions in SPL.
1092 bool "FDT tools for simplefb support"
1093 depends on OF_LIBFDT
1095 Enable the fdt tools to manage the simple fb nodes in device tree.
1096 These functions can be used by board to indicate to the OS
1097 the presence of the simple frame buffer with associated reserved