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 SILENT_U_BOOT_ONLY
117 bool "Only silence the U-Boot console"
118 depends on SILENT_CONSOLE
120 Normally when the U-Boot console is silenced, Linux's console is
121 also silenced (assuming the board boots into Linux). This option
122 allows the linux console to operate normally, even if U-Boot's
125 config SILENT_CONSOLE_UPDATE_ON_SET
126 bool "Changes to the 'silent' environment variable update immediately"
127 depends on SILENT_CONSOLE
128 default y if SILENT_CONSOLE
130 When the 'silent' environment variable is changed, update the
131 console silence flag immediately. This allows 'setenv' to be used
132 to silence or un-silence the console.
134 The effect is that any change to the variable will affect the
137 config SILENT_CONSOLE_UPDATE_ON_RELOC
138 bool "Allow flags to take effect on relocation"
139 depends on SILENT_CONSOLE
141 In some cases the environment is not available until relocation
142 (e.g. NAND). This option makes the value of the 'silent'
143 environment variable take effect at relocation.
145 config PRE_CONSOLE_BUFFER
146 bool "Buffer characters before the console is available"
148 Prior to the console being initialised (i.e. serial UART
149 initialised etc) all console output is silently discarded.
150 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
151 buffer any console messages prior to the console being
152 initialised to a buffer. The buffer is a circular buffer, so
153 if it overflows, earlier output is discarded.
155 Note that this is not currently supported in SPL. It would be
156 useful to be able to share the pre-console buffer with SPL.
158 config PRE_CON_BUF_SZ
159 int "Sets the size of the pre-console buffer"
160 depends on PRE_CONSOLE_BUFFER
163 The size of the pre-console buffer affects how much console output
164 can be held before it overflows and starts discarding earlier
165 output. Normally there is very little output at this early stage,
166 unless debugging is enabled, so allow enough for ~10 lines of
169 This is a useful feature if you are using a video console and
170 want to see the full boot output on the console. Without this
171 option only the post-relocation output will be displayed.
173 config PRE_CON_BUF_ADDR
174 hex "Address of the pre-console buffer"
175 depends on PRE_CONSOLE_BUFFER
176 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
177 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
178 default 0x0f000000 if ROCKCHIP_RK3288
179 default 0x0f200000 if ROCKCHIP_RK3399
181 This sets the start address of the pre-console buffer. This must
182 be in available memory and is accessed before relocation and
183 possibly before DRAM is set up. Therefore choose an address
186 We should consider removing this option and allocating the memory
187 in board_init_f_init_reserve() instead.
190 bool "Enable console multiplexing"
191 default y if DM_VIDEO || VIDEO || LCD
193 This allows multiple devices to be used for each console 'file'.
194 For example, stdout can be set to go to serial and video.
195 Similarly, stdin can be set to come from serial and keyboard.
196 Input can be provided from either source. Console multiplexing
197 adds a small amount of size to U-Boot. Changes to the environment
198 variables stdout, stdin and stderr will take effect immediately.
200 config SYS_CONSOLE_IS_IN_ENV
201 bool "Select console devices from the environment"
202 default y if CONSOLE_MUX
204 This allows multiple input/output devices to be set at boot time.
205 For example, if stdout is set to "serial,vidconsole" then output
206 will be sent to both the serial and video devices on boot. The
207 environment variables can be updated after boot to change the
208 input/output devices.
210 config SYS_CONSOLE_OVERWRITE_ROUTINE
211 bool "Allow board control over console overwriting"
213 If this is enabled, and the board-specific function
214 overwrite_console() returns 1, the stdin, stderr and stdout are
215 switched to the serial port, else the settings in the environment
216 are used. If this is not enabled, the console will not be switched
219 config SYS_CONSOLE_ENV_OVERWRITE
220 bool "Update environment variables during console init"
222 The console environment variables (stdout, stdin, stderr) can be
223 used to determine the correct console devices on start-up. This
224 option writes the console devices to these variables on console
225 start-up (after relocation). This causes the environment to be
226 updated to match the console devices actually chosen.
228 config SYS_CONSOLE_INFO_QUIET
229 bool "Don't display the console devices on boot"
231 Normally U-Boot displays the current settings for stdout, stdin
232 and stderr on boot when the post-relocation console is set up.
233 Enable this option to suppress this output. It can be obtained by
234 calling stdio_print_current_devices() from board code.
236 config SYS_STDIO_DEREGISTER
237 bool "Allow deregistering stdio devices"
238 default y if USB_KEYBOARD
240 Generally there is no need to deregister stdio devices since they
241 are never deactivated. But if a stdio device is used which can be
242 removed (for example a USB keyboard) then this option can be
243 enabled to ensure this is handled correctly.
245 config SPL_SYS_STDIO_DEREGISTER
246 bool "Allow deregistering stdio devices in SPL"
248 Generally there is no need to deregister stdio devices since they
249 are never deactivated. But if a stdio device is used which can be
250 removed (for example a USB keyboard) then this option can be
251 enabled to ensure this is handled correctly. This is very rarely
254 config SYS_DEVICE_NULLDEV
255 bool "Enable a null device for stdio"
256 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
258 Enable creation of a "nulldev" stdio device. This allows silent
259 operation of the console by setting stdout to "nulldev". Enable
260 this to use a serial console under board control.
267 bool "Enable logging support"
270 This enables support for logging of status and debug messages. These
271 can be displayed on the console, recorded in a memory buffer, or
272 discarded if not needed. Logging supports various categories and
278 int "Maximum log level to record"
282 This selects the maximum log level that will be recorded. Any value
283 higher than this will be ignored. If possible log statements below
284 this level will be discarded at build time. Levels:
295 9 - debug hardware I/O
297 config LOG_DEFAULT_LEVEL
298 int "Default logging level to display"
299 default LOG_MAX_LEVEL
300 range 0 LOG_MAX_LEVEL
302 This is the default logging level set when U-Boot starts. It can
303 be adjusted later using the 'log level' command. Note that setting
304 this to a value above LOG_MAX_LEVEL will be ineffective, since the
305 higher levels are not compiled in to U-Boot.
316 9 - debug hardware I/O
319 bool "Allow log output to the console"
322 Enables a log driver which writes log records to the console.
323 Generally the console is the serial port or LCD display. Only the
324 log message is shown - other details like level, category, file and
325 line number are omitted.
328 bool "Show source file name in log messages by default"
330 Show the source file name in log messages by default. This value
331 can be overridden using the 'log format' command.
334 bool "Show source line number in log messages by default"
336 Show the source line number in log messages by default. This value
337 can be overridden using the 'log format' command.
340 bool "Show function name in log messages by default"
342 Show the function name in log messages by default. This value can
343 be overridden using the 'log format' command.
346 int "Number of characters to use for function"
349 Sets the field width to use when showing the function. Set this to
350 a larger value if you have lots of long function names, and want
354 bool "Log output to syslog server"
357 Enables a log driver which broadcasts log records via UDP port 514
361 bool "Enable logging support in SPL"
362 depends on LOG && SPL
364 This enables support for logging of status and debug messages. These
365 can be displayed on the console, recorded in a memory buffer, or
366 discarded if not needed. Logging supports various categories and
371 config SPL_LOG_MAX_LEVEL
372 int "Maximum log level to record in SPL"
377 This selects the maximum log level that will be recorded. Any value
378 higher than this will be ignored. If possible log statements below
379 this level will be discarded at build time. Levels:
390 9 - debug hardware I/O
392 config SPL_LOG_CONSOLE
393 bool "Allow log output to the console in SPL"
396 Enables a log driver which writes log records to the console.
397 Generally the console is the serial port or LCD display. Only the
398 log message is shown - other details like level, category, file and
399 line number are omitted.
404 bool "Enable logging support in TPL"
405 depends on LOG && TPL
407 This enables support for logging of status and debug messages. These
408 can be displayed on the console, recorded in a memory buffer, or
409 discarded if not needed. Logging supports various categories and
414 config TPL_LOG_MAX_LEVEL
415 int "Maximum log level to record in TPL"
420 This selects the maximum log level that will be recorded. Any value
421 higher than this will be ignored. If possible log statements below
422 this level will be discarded at build time. Levels:
433 9 - debug hardware I/O
435 config TPL_LOG_CONSOLE
436 bool "Allow log output to the console in TPL"
439 Enables a log driver which writes log records to the console.
440 Generally the console is the serial port or LCD display. Only the
441 log message is shown - other details like level, category, file and
442 line number are omitted.
447 bool "Enable logging support in VPL"
448 depends on LOG && VPL
450 This enables support for logging of status and debug messages. These
451 can be displayed on the console, recorded in a memory buffer, or
452 discarded if not needed. Logging supports various categories and
457 config VPL_LOG_MAX_LEVEL
458 int "Maximum log level to record in VPL"
461 This selects the maximum log level that will be recorded. Any value
462 higher than this will be ignored. If possible log statements below
463 this level will be discarded at build time. Levels:
474 9 - debug hardware I/O
476 config VPL_LOG_CONSOLE
477 bool "Allow log output to the console in VPL"
480 Enables a log driver which writes log records to the console.
481 Generally the console is the serial port or LCD display. Only the
482 log message is shown - other details like level, category, file and
483 line number are omitted.
487 config LOG_ERROR_RETURN
488 bool "Log all functions which return an error"
490 When an error is returned in U-Boot it is sometimes difficult to
491 figure out the root cause. For example, reading from SPI flash may
492 fail due to a problem in the SPI controller or due to the flash part
493 not returning the expected information. This option changes
494 log_ret() to log any errors it sees. With this option disabled,
497 You can add log_ret() to all functions which return an error code.
500 bool "Provide a test for logging"
504 This enables a 'log test' command to test logging. It is normally
505 executed from a pytest and simply outputs logging information
506 in various different ways to test that the logging system works
507 correctly with various settings.
516 bool "Call get_board_type() to get and display the board type"
518 If this option is enabled, checkboard() will call get_board_type()
519 to get a string containing the board type and this will be
520 displayed immediately after the model is shown on the console
523 config DISPLAY_CPUINFO
524 bool "Display information about the CPU during start up"
525 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
527 Display information about the CPU that U-Boot is running on
528 when U-Boot starts up. The function print_cpuinfo() is called
531 config DISPLAY_BOARDINFO
532 bool "Display information about the board during early start up"
533 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
535 Display information about the board that U-Boot is running on
536 when U-Boot starts up. The board function checkboard() is called
539 config DISPLAY_BOARDINFO_LATE
540 bool "Display information about the board during late start up"
542 Display information about the board that U-Boot is running on after
543 the relocation phase. The board function checkboard() is called to do
546 menu "Start-up hooks"
549 bool "General-purpose cyclic execution mechanism"
551 This enables a general-purpose cyclic execution infrastructure,
552 to allow "small" (run-time wise) functions to be executed at
553 a specified frequency. Things like LED blinking or watchdog
554 triggering are examples for such tasks.
558 config CYCLIC_MAX_CPU_TIME_US
559 int "Sets the max allowed time for a cyclic function in us"
562 The max allowed time for a cyclic function in us. If a functions
563 takes longer than this duration this function will get unregistered
569 bool "General-purpose event-handling mechanism"
572 This enables sending and processing of events, to allow interested
573 parties to be alerted when something happens. This is an attempt to
574 step the flow of weak functions, hooks, functions in board_f.c
575 and board_r.c and the Kconfig options below.
577 See doc/develop/event.rst for more information.
582 bool "Support event registration at runtime"
585 Enable this to support adding an event spy at runtime, without adding
586 it to the EVENT_SPy() linker list. This increases code size slightly
587 but provides more flexibility for boards and subsystems that need it.
590 bool "Enable event debugging assistance"
593 Enable this get usefui features for seeing what is happening with
594 events, such as event-type names. This adds to the code size of
595 U-Boot so can be turned off for production builds.
599 config ARCH_EARLY_INIT_R
600 bool "Call arch-specific init soon after relocation"
602 With this option U-Boot will call arch_early_init_r() soon after
603 relocation. Driver model is running by this point, and the cache
604 is on. Note that board_early_init_r() is called first, if
605 enabled. This can be used to set up architecture-specific devices.
607 config ARCH_MISC_INIT
608 bool "Call arch-specific init after relocation, when console is ready"
610 With this option U-Boot will call arch_misc_init() after
611 relocation to allow miscellaneous arch-dependent initialisation
612 to be performed. This function should be defined by the board
613 and will be called after the console is set up, after relocation.
615 config BOARD_EARLY_INIT_F
616 bool "Call board-specific init before relocation"
618 Some boards need to perform initialisation as soon as possible
619 after boot. With this option, U-Boot calls board_early_init_f()
620 after driver model is ready in the pre-relocation init sequence.
621 Note that the normal serial console is not yet set up, but the
622 debug UART will be available if enabled.
624 config BOARD_EARLY_INIT_R
625 bool "Call board-specific init after relocation"
627 Some boards need to perform initialisation as directly after
628 relocation. With this option, U-Boot calls board_early_init_r()
629 in the post-relocation init sequence.
631 config BOARD_POSTCLK_INIT
632 bool "Call board_postclk_init"
634 Some boards need this to initialize select items, after clocks /
635 timebase and before env / serial.
637 config BOARD_LATE_INIT
638 bool "Execute Board late init"
640 Sometimes board require some initialization code that might
641 require once the actual init done, example saving board specific env,
642 boot-modes etc. which eventually done at late.
644 So this config enable the late init code with the help of board_late_init
645 function which should defined on respective boards.
648 bool "Call set_cpu_clk_info"
653 depends on ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3 || \
654 (FSL_ESDHC_IMX && (ARCH_MX5 || ARCH_MX6 || ARCH_MX7))
657 Enable to call get_clocks() in board_init_f() for platforms other
658 than PowerPC or M68k. This is a legacy option. If not TARGET_BRPPT2
660 config LAST_STAGE_INIT
661 bool "Call board-specific as last setup step"
663 Some boards need to perform initialisation immediately before control
664 is passed to the command-line interpreter (e.g. for initializations
665 that depend on later phases in the init sequence). With this option,
666 U-Boot calls last_stage_init() before the command-line interpreter is
670 bool "Execute Misc Init"
671 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
672 default y if ARCH_OMAP2PLUS && !AM33XX
674 Enabling this option calls 'misc_init_r' function
676 config SYS_MALLOC_BOOTPARAMS
677 bool "Malloc a buffer to use for bootparams"
679 In some cases rather than using a known location to store the
680 bi_boot_params portion of gd we need to allocate it from our malloc pool.
682 config SYS_BOOTPARAMS_LEN
683 hex "Size of the bootparam buffer to malloc in bytes"
684 depends on SYS_MALLOC_BOOTPARAMS
685 default 0x20000 if MIPS || RCAR_GEN3
689 bool "Enable I2C connected system identifier EEPROM"
691 A number of different systems and vendors enable a vendor-specified
692 EEPROM that contains various identifying features.
694 config SYS_EEPROM_BUS_NUM
695 int "I2C bus number of the system identifier EEPROM"
700 prompt "EEPROM starts with 'CCID' or 'NXID'"
701 depends on ID_EEPROM && (PPC || ARCH_LS1021A || FSL_LAYERSCAPE)
702 default SYS_I2C_EEPROM_NXID
704 Specify if the Freescale / NXP ID EEPROM starts with 'CCID' or 'NXID'
705 ASCII literal string.
707 config SYS_I2C_EEPROM_CCID
708 bool "EEPROM starts with 'CCID'"
710 config SYS_I2C_EEPROM_NXID
711 bool "EEPROM starts with 'NXID'"
716 bool "Enumerate PCI buses during init"
719 With this option U-Boot will call pci_init() soon after relocation,
720 which will enumerate PCI buses. This is needed, for instance, in the
721 case of DM PCI-based Ethernet devices, which will not be detected
722 without having the enumeration performed earlier.
725 bool "Reset ethernet PHY during init"
727 Implement reset_phy() in board code if required to reset the ethernet
732 endmenu # Init options
734 menu "Security support"
737 bool # "Support hashing API (SHA1, SHA256, etc.)"
739 This provides a way to hash data in memory using various supported
740 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
741 and the algorithms it supports are defined in common/hash.c. See
742 also CMD_HASH for command-line access.
745 bool "Build Android Verified Boot operations"
748 depends on PARTITION_UUIDS
750 This option enables compilation of bootloader-dependent operations,
751 used by Android Verified Boot 2.0 library (libavb). Includes:
752 * Helpers to process strings in order to build OS bootargs.
753 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
754 * Helpers to alloc/init/free avb ops.
759 hex "Define AVB buffer address"
760 default FASTBOOT_BUF_ADDR
762 AVB requires a buffer for memory transactions. This variable defines the
766 hex "Define AVB buffer SIZE"
767 default FASTBOOT_BUF_SIZE
769 AVB requires a buffer for memory transactions. This variable defines the
775 bool "Build SCP03 - Secure Channel Protocol O3 - controls"
776 depends on OPTEE || SANDBOX
779 This option allows U-Boot to enable and or provision SCP03 on an OPTEE
780 controlled Secured Element.
783 bool # "Support hashing API (SHA1, SHA256, etc.)"
785 This provides a way to hash data in memory using various supported
786 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
787 and the algorithms it supports are defined in common/hash.c. See
788 also CMD_HASH for command-line access.
791 bool # "Support hashing API (SHA1, SHA256, etc.)"
793 This provides a way to hash data in memory using various supported
794 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
795 and the algorithms it supports are defined in common/hash.c. See
796 also CMD_HASH for command-line access.
798 config STACKPROTECTOR
799 bool "Stack Protector buffer overflow detection"
801 Enable stack smash detection through compiler's stack-protector
804 config SPL_STACKPROTECTOR
805 bool "Stack Protector buffer overflow detection for SPL"
806 depends on STACKPROTECTOR && SPL
808 config TPL_STACKPROTECTOR
809 bool "Stack Protector buffer overflow detection for TPL"
810 depends on STACKPROTECTOR && TPL
814 menu "Update support"
821 bool "Auto-update using fitImage via TFTP"
825 This option allows performing update of NOR with data in fitImage
828 config UPDATE_TFTP_CNT_MAX
829 int "The number of connection retries during auto-update"
831 depends on UPDATE_TFTP
833 config UPDATE_TFTP_MSEC_MAX
834 int "Delay in mSec to wait for the TFTP server during auto-update"
836 depends on UPDATE_TFTP
839 bool "Firmware update using fitImage"
844 This option allows performing update of DFU-capable storage with
848 bool "Android A/B updates"
850 If enabled, adds support for the new Android A/B update model. This
851 allows the bootloader to select which slot to boot from based on the
852 information provided by userspace via the Android boot_ctrl HAL. This
853 allows a bootloader to try a new version of the system but roll back
854 to previous version if the new one didn't boot all the way.
861 bool "Support for a bloblist"
863 This enables support for a bloblist in U-Boot, which can be passed
864 from TPL to SPL to U-Boot proper (and potentially to Linux). The
865 blob list supports multiple binary blobs of data, each with a tag,
866 so that different U-Boot components can store data which can survive
867 through to the next phase of the boot.
870 bool "Support for a bloblist in SPL"
871 depends on BLOBLIST && SPL_LIBGENERIC_SUPPORT && SPL_LIBCOMMON_SUPPORT
874 This enables a bloblist in SPL. If this is the first part of U-Boot
875 to run, then the bloblist is set up in SPL and passed to U-Boot
876 proper. If TPL also has a bloblist, then SPL uses the one from there.
879 bool "Support for a bloblist in TPL"
880 depends on BLOBLIST && TPL_LIBGENERIC_SUPPORT && TPL_LIBCOMMON_SUPPORT
883 This enables a bloblist in TPL. The bloblist is set up in TPL and
884 passed to SPL and U-Boot proper.
887 bool "Support for a bloblist in VPL"
888 depends on BLOBLIST && VPL_LIBGENERIC_SUPPORT && VPL_LIBCOMMON_SUPPORT
891 This enables a bloblist in VPL. The bloblist is set up in VPL and
892 passed to SPL and U-Boot proper.
897 prompt "Bloblist location"
899 Select the location of the bloblist, via various means.
901 config BLOBLIST_FIXED
902 bool "Place bloblist at a fixed address in memory"
904 Select this to used a fixed memory address for the bloblist. If the
905 bloblist exists at this address from a previous phase, it used as is.
906 If not it is created at this address in U-Boot.
908 config BLOBLIST_ALLOC
909 bool "Allocate bloblist"
911 Allocate the bloblist using malloc(). This avoids the need to
912 specify a fixed address on systems where this is unknown or can
918 hex "Address of bloblist"
919 default 0xc000 if SANDBOX
920 depends on BLOBLIST_FIXED
922 Sets the address of the bloblist, set up by the first part of U-Boot
923 which runs. Subsequent U-Boot phases typically use the same address.
925 This is not used if BLOBLIST_ALLOC is selected.
928 hex "Size of bloblist"
931 Sets the size of the bloblist in bytes. This must include all
932 overhead (alignment, bloblist header, record header). The bloblist
933 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
934 proper), and this sane bloblist is used for subsequent phases.
936 config BLOBLIST_SIZE_RELOC
937 hex "Size of bloblist after relocation"
938 default BLOBLIST_SIZE if BLOBLIST_FIXED || BLOBLIST_ALLOC
939 default 0 if BLOBLIST_PASSAGE
941 Sets the size of the bloblist in bytes after relocation. Since U-Boot
942 has a lot more memory available then, it is possible to use a larger
943 size than the one set up by SPL. This bloblist is set up during the
951 prompt "Bloblist location in SPL"
953 Select the location of the bloblist, via various means. Typically
954 you should use the same value for SPL as for U-Boot, since they need
955 to look in the same place. But if BLOBLIST_ALLOC is used, then a
956 fresh bloblist will be created each time, since there is no shared
957 address (between phases) for the bloblist.
959 config SPL_BLOBLIST_FIXED
960 bool "Place bloblist at a fixed address in memory"
962 Select this to used a fixed memory address for the bloblist. If the
963 bloblist exists at this address from a previous phase, it used as is.
964 If not it is created at this address in SPL.
966 config SPL_BLOBLIST_ALLOC
967 bool "Allocate bloblist"
969 Allocate the bloblist using malloc(). This avoids the need to
970 specify a fixed address on systems where this is unknown or can
980 prompt "Bloblist location in TPL"
982 Select the location of the bloblist, via various means. Typically
983 you should use the same value for SPL as for U-Boot, since they need
984 to look in the same place. But if BLOBLIST_ALLOC is used, then a
985 fresh bloblist will be created each time, since there is no shared
986 address (between phases) for the bloblist.
988 config TPL_BLOBLIST_FIXED
989 bool "Place bloblist at a fixed address in memory"
991 Select this to used a fixed memory address for the bloblist. If the
992 bloblist exists at this address from a previous phase, it used as is.
993 If not it is created at this address in TPL.
995 config TPL_BLOBLIST_ALLOC
996 bool "Allocate bloblist"
998 Allocate the bloblist using malloc(). This avoids the need to
999 specify a fixed address on systems where this is unknown or can
1004 endif # TPL_BLOBLIST
1008 source "common/spl/Kconfig"
1010 config IMAGE_SIGN_INFO
1015 Enable image_sign_info helper functions.
1019 config SPL_IMAGE_SIGN_INFO
1024 Enable image_sign_info helper functions in SPL.
1029 bool "FDT tools for simplefb support"
1030 depends on OF_LIBFDT
1032 Enable the fdt tools to manage the simple fb nodes in device tree.
1033 These functions can be used by board to indicate to the OS
1034 the presence of the simple frame buffer with associated reserved