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
93 int "loglevel for VPL"
96 All Messages with a loglevel smaller than the console loglevel will
97 be compiled in to VPL. See LOGLEVEL for a list of available log
98 levels. Setting this to a value above 4 may increase the code size
101 config SILENT_CONSOLE
102 bool "Support a silent console"
104 This option allows the console to be silenced, meaning that no
105 output will appear on the console devices. This is controlled by
106 setting the environment variable 'silent' to a non-empty value.
107 Note this also silences the console when booting Linux.
109 When the console is set up, the variable is checked, and the
110 GD_FLG_SILENT flag is set. Changing the environment variable later
111 will update the flag.
113 config SILENT_U_BOOT_ONLY
114 bool "Only silence the U-Boot console"
115 depends on SILENT_CONSOLE
117 Normally when the U-Boot console is silenced, Linux's console is
118 also silenced (assuming the board boots into Linux). This option
119 allows the linux console to operate normally, even if U-Boot's
122 config SILENT_CONSOLE_UPDATE_ON_SET
123 bool "Changes to the 'silent' environment variable update immediately"
124 depends on SILENT_CONSOLE
125 default y if SILENT_CONSOLE
127 When the 'silent' environment variable is changed, update the
128 console silence flag immediately. This allows 'setenv' to be used
129 to silence or un-silence the console.
131 The effect is that any change to the variable will affect the
134 config SILENT_CONSOLE_UPDATE_ON_RELOC
135 bool "Allow flags to take effect on relocation"
136 depends on SILENT_CONSOLE
138 In some cases the environment is not available until relocation
139 (e.g. NAND). This option makes the value of the 'silent'
140 environment variable take effect at relocation.
142 config PRE_CONSOLE_BUFFER
143 bool "Buffer characters before the console is available"
145 Prior to the console being initialised (i.e. serial UART
146 initialised etc) all console output is silently discarded.
147 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
148 buffer any console messages prior to the console being
149 initialised to a buffer. The buffer is a circular buffer, so
150 if it overflows, earlier output is discarded.
152 Note that this is not currently supported in SPL. It would be
153 useful to be able to share the pre-console buffer with SPL.
155 config PRE_CON_BUF_SZ
156 int "Sets the size of the pre-console buffer"
157 depends on PRE_CONSOLE_BUFFER
160 The size of the pre-console buffer affects how much console output
161 can be held before it overflows and starts discarding earlier
162 output. Normally there is very little output at this early stage,
163 unless debugging is enabled, so allow enough for ~10 lines of
166 This is a useful feature if you are using a video console and
167 want to see the full boot output on the console. Without this
168 option only the post-relocation output will be displayed.
170 config PRE_CON_BUF_ADDR
171 hex "Address of the pre-console buffer"
172 depends on PRE_CONSOLE_BUFFER
173 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
174 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
175 default 0x0f000000 if ROCKCHIP_RK3288
176 default 0x0f200000 if ROCKCHIP_RK3399
178 This sets the start address of the pre-console buffer. This must
179 be in available memory and is accessed before relocation and
180 possibly before DRAM is set up. Therefore choose an address
183 We should consider removing this option and allocating the memory
184 in board_init_f_init_reserve() instead.
187 bool "Enable console multiplexing"
188 default y if DM_VIDEO || VIDEO || LCD
190 This allows multiple devices to be used for each console 'file'.
191 For example, stdout can be set to go to serial and video.
192 Similarly, stdin can be set to come from serial and keyboard.
193 Input can be provided from either source. Console multiplexing
194 adds a small amount of size to U-Boot. Changes to the environment
195 variables stdout, stdin and stderr will take effect immediately.
197 config SYS_CONSOLE_IS_IN_ENV
198 bool "Select console devices from the environment"
199 default y if CONSOLE_MUX
201 This allows multiple input/output devices to be set at boot time.
202 For example, if stdout is set to "serial,vidconsole" then output
203 will be sent to both the serial and video devices on boot. The
204 environment variables can be updated after boot to change the
205 input/output devices.
207 config SYS_CONSOLE_OVERWRITE_ROUTINE
208 bool "Allow board control over console overwriting"
210 If this is enabled, and the board-specific function
211 overwrite_console() returns 1, the stdin, stderr and stdout are
212 switched to the serial port, else the settings in the environment
213 are used. If this is not enabled, the console will not be switched
216 config SYS_CONSOLE_ENV_OVERWRITE
217 bool "Update environment variables during console init"
219 The console environment variables (stdout, stdin, stderr) can be
220 used to determine the correct console devices on start-up. This
221 option writes the console devices to these variables on console
222 start-up (after relocation). This causes the environment to be
223 updated to match the console devices actually chosen.
225 config SYS_CONSOLE_INFO_QUIET
226 bool "Don't display the console devices on boot"
228 Normally U-Boot displays the current settings for stdout, stdin
229 and stderr on boot when the post-relocation console is set up.
230 Enable this option to suppress this output. It can be obtained by
231 calling stdio_print_current_devices() from board code.
233 config SYS_STDIO_DEREGISTER
234 bool "Allow deregistering stdio devices"
235 default y if USB_KEYBOARD
237 Generally there is no need to deregister stdio devices since they
238 are never deactivated. But if a stdio device is used which can be
239 removed (for example a USB keyboard) then this option can be
240 enabled to ensure this is handled correctly.
242 config SPL_SYS_STDIO_DEREGISTER
243 bool "Allow deregistering stdio devices in SPL"
245 Generally there is no need to deregister stdio devices since they
246 are never deactivated. But if a stdio device is used which can be
247 removed (for example a USB keyboard) then this option can be
248 enabled to ensure this is handled correctly. This is very rarely
251 config SYS_DEVICE_NULLDEV
252 bool "Enable a null device for stdio"
253 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
255 Enable creation of a "nulldev" stdio device. This allows silent
256 operation of the console by setting stdout to "nulldev". Enable
257 this to use a serial console under board control.
264 bool "Enable logging support"
267 This enables support for logging of status and debug messages. These
268 can be displayed on the console, recorded in a memory buffer, or
269 discarded if not needed. Logging supports various categories and
275 bool "Enable logging support in VPL"
278 This enables support for logging of status and debug messages. These
279 can be displayed on the console, recorded in a memory buffer, or
280 discarded if not needed. Logging supports various categories and
284 int "Maximum log level to record"
288 This selects the maximum log level that will be recorded. Any value
289 higher than this will be ignored. If possible log statements below
290 this level will be discarded at build time. Levels:
301 9 - debug hardware I/O
303 config LOG_DEFAULT_LEVEL
304 int "Default logging level to display"
305 default LOG_MAX_LEVEL
306 range 0 LOG_MAX_LEVEL
308 This is the default logging level set when U-Boot starts. It can
309 be adjusted later using the 'log level' command. Note that setting
310 this to a value above LOG_MAX_LEVEL will be ineffective, since the
311 higher levels are not compiled in to U-Boot.
322 9 - debug hardware I/O
325 bool "Allow log output to the console"
328 Enables a log driver which writes log records to the console.
329 Generally the console is the serial port or LCD display. Only the
330 log message is shown - other details like level, category, file and
331 line number are omitted.
334 bool "Show source file name in log messages by default"
336 Show the source file name in log messages by default. This value
337 can be overridden using the 'log format' command.
340 bool "Show source line number in log messages by default"
342 Show the source line number in log messages by default. This value
343 can be overridden using the 'log format' command.
346 bool "Show function name in log messages by default"
348 Show the function name in log messages by default. This value can
349 be overridden using the 'log format' command.
352 int "Number of characters to use for function"
355 Sets the field width to use when showing the function. Set this to
356 a larger value if you have lots of long function names, and want
360 bool "Log output to syslog server"
363 Enables a log driver which broadcasts log records via UDP port 514
367 bool "Enable logging support in SPL"
370 This enables support for logging of status and debug messages. These
371 can be displayed on the console, recorded in a memory buffer, or
372 discarded if not needed. Logging supports various categories and
377 config SPL_LOG_MAX_LEVEL
378 int "Maximum log level to record in SPL"
383 This selects the maximum log level that will be recorded. Any value
384 higher than this will be ignored. If possible log statements below
385 this level will be discarded at build time. Levels:
396 9 - debug hardware I/O
398 config SPL_LOG_CONSOLE
399 bool "Allow log output to the console in SPL"
402 Enables a log driver which writes log records to the console.
403 Generally the console is the serial port or LCD display. Only the
404 log message is shown - other details like level, category, file and
405 line number are omitted.
410 bool "Enable logging support in TPL"
413 This enables support for logging of status and debug messages. These
414 can be displayed on the console, recorded in a memory buffer, or
415 discarded if not needed. Logging supports various categories and
420 config TPL_LOG_MAX_LEVEL
421 int "Maximum log level to record in TPL"
426 This selects the maximum log level that will be recorded. Any value
427 higher than this will be ignored. If possible log statements below
428 this level will be discarded at build time. Levels:
439 9 - debug hardware I/O
441 config TPL_LOG_CONSOLE
442 bool "Allow log output to the console in TPL"
445 Enables a log driver which writes log records to the console.
446 Generally the console is the serial port or LCD display. Only the
447 log message is shown - other details like level, category, file and
448 line number are omitted.
453 bool "Enable logging support in VPL"
456 This enables support for logging of status and debug messages. These
457 can be displayed on the console, recorded in a memory buffer, or
458 discarded if not needed. Logging supports various categories and
463 config VPL_LOG_MAX_LEVEL
464 int "Maximum log level to record in VPL"
467 This selects the maximum log level that will be recorded. Any value
468 higher than this will be ignored. If possible log statements below
469 this level will be discarded at build time. Levels:
480 9 - debug hardware I/O
482 config VPL_LOG_CONSOLE
483 bool "Allow log output to the console in VPL"
486 Enables a log driver which writes log records to the console.
487 Generally the console is the serial port or LCD display. Only the
488 log message is shown - other details like level, category, file and
489 line number are omitted.
493 config LOG_ERROR_RETURN
494 bool "Log all functions which return an error"
496 When an error is returned in U-Boot it is sometimes difficult to
497 figure out the root cause. For example, reading from SPI flash may
498 fail due to a problem in the SPI controller or due to the flash part
499 not returning the expected information. This option changes
500 log_ret() to log any errors it sees. With this option disabled,
503 You can add log_ret() to all functions which return an error code.
506 bool "Provide a test for logging"
510 This enables a 'log test' command to test logging. It is normally
511 executed from a pytest and simply outputs logging information
512 in various different ways to test that the logging system works
513 correctly with various settings.
522 bool "Call get_board_type() to get and display the board type"
524 If this option is enabled, checkboard() will call get_board_type()
525 to get a string containing the board type and this will be
526 displayed immediately after the model is shown on the console
529 config DISPLAY_CPUINFO
530 bool "Display information about the CPU during start up"
531 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
533 Display information about the CPU that U-Boot is running on
534 when U-Boot starts up. The function print_cpuinfo() is called
537 config DISPLAY_BOARDINFO
538 bool "Display information about the board during early start up"
539 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
541 Display information about the board that U-Boot is running on
542 when U-Boot starts up. The board function checkboard() is called
545 config DISPLAY_BOARDINFO_LATE
546 bool "Display information about the board during late start up"
548 Display information about the board that U-Boot is running on after
549 the relocation phase. The board function checkboard() is called to do
552 menu "Start-up hooks"
555 bool "General-purpose event-handling mechanism"
558 This enables sending and processing of events, to allow interested
559 parties to be alerted when something happens. This is an attempt to
560 step the flow of weak functions, hooks, functions in board_f.c
561 and board_r.c and the Kconfig options below.
563 See doc/develop/event.rst for more information.
568 bool "Support event registration at runtime"
571 Enable this to support adding an event spy at runtime, without adding
572 it to the EVENT_SPy() linker list. This increases code size slightly
573 but provides more flexibility for boards and subsystems that need it.
576 bool "Enable event debugging assistance"
579 Enable this get usefui features for seeing what is happening with
580 events, such as event-type names. This adds to the code size of
581 U-Boot so can be turned off for production builds.
585 config ARCH_EARLY_INIT_R
586 bool "Call arch-specific init soon after relocation"
588 With this option U-Boot will call arch_early_init_r() soon after
589 relocation. Driver model is running by this point, and the cache
590 is on. Note that board_early_init_r() is called first, if
591 enabled. This can be used to set up architecture-specific devices.
593 config ARCH_MISC_INIT
594 bool "Call arch-specific init after relocation, when console is ready"
596 With this option U-Boot will call arch_misc_init() after
597 relocation to allow miscellaneous arch-dependent initialisation
598 to be performed. This function should be defined by the board
599 and will be called after the console is set up, after relocation.
601 config BOARD_EARLY_INIT_F
602 bool "Call board-specific init before relocation"
604 Some boards need to perform initialisation as soon as possible
605 after boot. With this option, U-Boot calls board_early_init_f()
606 after driver model is ready in the pre-relocation init sequence.
607 Note that the normal serial console is not yet set up, but the
608 debug UART will be available if enabled.
610 config BOARD_EARLY_INIT_R
611 bool "Call board-specific init after relocation"
613 Some boards need to perform initialisation as directly after
614 relocation. With this option, U-Boot calls board_early_init_r()
615 in the post-relocation init sequence.
617 config BOARD_POSTCLK_INIT
618 bool "Call board_postclk_init"
620 Some boards need this to initialize select items, after clocks /
621 timebase and before env / serial.
623 config BOARD_LATE_INIT
624 bool "Execute Board late init"
626 Sometimes board require some initialization code that might
627 require once the actual init done, example saving board specific env,
628 boot-modes etc. which eventually done at late.
630 So this config enable the late init code with the help of board_late_init
631 function which should defined on respective boards.
634 bool "Call set_cpu_clk_info"
639 depends on ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3 || \
640 (FSL_ESDHC_IMX && (ARCH_MX5 || ARCH_MX6 || ARCH_MX7))
643 Enable to call get_clocks() in board_init_f() for platforms other
644 than PowerPC or M68k. This is a legacy option. If not TARGET_BRPPT2
646 config LAST_STAGE_INIT
647 bool "Call board-specific as last setup step"
649 Some boards need to perform initialisation immediately before control
650 is passed to the command-line interpreter (e.g. for initializations
651 that depend on later phases in the init sequence). With this option,
652 U-Boot calls last_stage_init() before the command-line interpreter is
656 bool "Execute Misc Init"
657 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
658 default y if ARCH_OMAP2PLUS && !AM33XX
660 Enabling this option calls 'misc_init_r' function
663 bool "Enable I2C connected system identifier EEPROM"
665 A number of different systems and vendors enable a vendor-specified
666 EEPROM that contains various identifying features.
669 bool "Enumerate PCI buses during init"
672 With this option U-Boot will call pci_init() soon after relocation,
673 which will enumerate PCI buses. This is needed, for instance, in the
674 case of DM PCI-based Ethernet devices, which will not be detected
675 without having the enumeration performed earlier.
678 bool "Reset ethernet PHY during init"
680 Implement reset_phy() in board code if required to reset the ethernet
685 endmenu # Init options
687 menu "Security support"
690 bool # "Support hashing API (SHA1, SHA256, etc.)"
692 This provides a way to hash data in memory using various supported
693 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
694 and the algorithms it supports are defined in common/hash.c. See
695 also CMD_HASH for command-line access.
698 bool "Build Android Verified Boot operations"
701 depends on PARTITION_UUIDS
703 This option enables compilation of bootloader-dependent operations,
704 used by Android Verified Boot 2.0 library (libavb). Includes:
705 * Helpers to process strings in order to build OS bootargs.
706 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
707 * Helpers to alloc/init/free avb ops.
712 hex "Define AVB buffer address"
713 default FASTBOOT_BUF_ADDR
715 AVB requires a buffer for memory transactions. This variable defines the
719 hex "Define AVB buffer SIZE"
720 default FASTBOOT_BUF_SIZE
722 AVB requires a buffer for memory transactions. This variable defines the
728 bool "Build SCP03 - Secure Channel Protocol O3 - controls"
729 depends on OPTEE || SANDBOX
732 This option allows U-Boot to enable and or provision SCP03 on an OPTEE
733 controlled Secured Element.
736 bool # "Support hashing API (SHA1, SHA256, etc.)"
738 This provides a way to hash data in memory using various supported
739 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
740 and the algorithms it supports are defined in common/hash.c. See
741 also CMD_HASH for command-line access.
744 bool # "Support hashing API (SHA1, SHA256, etc.)"
746 This provides a way to hash data in memory using various supported
747 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
748 and the algorithms it supports are defined in common/hash.c. See
749 also CMD_HASH for command-line access.
751 config STACKPROTECTOR
752 bool "Stack Protector buffer overflow detection"
754 Enable stack smash detection through compiler's stack-protector
757 config SPL_STACKPROTECTOR
758 bool "Stack Protector buffer overflow detection for SPL"
759 depends on STACKPROTECTOR && SPL
761 config TPL_STACKPROTECTOR
762 bool "Stack Protector buffer overflow detection for TPL"
763 depends on STACKPROTECTOR && TPL
767 menu "Update support"
774 bool "Auto-update using fitImage via TFTP"
778 This option allows performing update of NOR with data in fitImage
781 config UPDATE_TFTP_CNT_MAX
782 int "The number of connection retries during auto-update"
784 depends on UPDATE_TFTP
786 config UPDATE_TFTP_MSEC_MAX
787 int "Delay in mSec to wait for the TFTP server during auto-update"
789 depends on UPDATE_TFTP
792 bool "Firmware update using fitImage"
797 This option allows performing update of DFU-capable storage with
801 bool "Android A/B updates"
803 If enabled, adds support for the new Android A/B update model. This
804 allows the bootloader to select which slot to boot from based on the
805 information provided by userspace via the Android boot_ctrl HAL. This
806 allows a bootloader to try a new version of the system but roll back
807 to previous version if the new one didn't boot all the way.
814 bool "Support for a bloblist"
816 This enables support for a bloblist in U-Boot, which can be passed
817 from TPL to SPL to U-Boot proper (and potentially to Linux). The
818 blob list supports multiple binary blobs of data, each with a tag,
819 so that different U-Boot components can store data which can survive
820 through to the next phase of the boot.
823 bool "Support for a bloblist in SPL"
824 depends on BLOBLIST && SPL_LIBGENERIC_SUPPORT && SPL_LIBCOMMON_SUPPORT
827 This enables a bloblist in SPL. If this is the first part of U-Boot
828 to run, then the bloblist is set up in SPL and passed to U-Boot
829 proper. If TPL also has a bloblist, then SPL uses the one from there.
832 bool "Support for a bloblist in TPL"
833 depends on BLOBLIST && TPL_LIBGENERIC_SUPPORT && TPL_LIBCOMMON_SUPPORT
836 This enables a bloblist in TPL. The bloblist is set up in TPL and
837 passed to SPL and U-Boot proper.
840 bool "Support for a bloblist in VPL"
841 depends on BLOBLIST && VPL_LIBGENERIC_SUPPORT && VPL_LIBCOMMON_SUPPORT
844 This enables a bloblist in VPL. The bloblist is set up in VPL and
845 passed to SPL and U-Boot proper.
850 prompt "Bloblist location"
852 Select the location of the bloblist, via various means.
854 config BLOBLIST_FIXED
855 bool "Place bloblist at a fixed address in memory"
857 Select this to used a fixed memory address for the bloblist. If the
858 bloblist exists at this address from a previous phase, it used as is.
859 If not it is created at this address in U-Boot.
861 config BLOBLIST_ALLOC
862 bool "Allocate bloblist"
864 Allocate the bloblist using malloc(). This avoids the need to
865 specify a fixed address on systems where this is unknown or can
871 hex "Address of bloblist"
872 default 0xc000 if SANDBOX
873 depends on BLOBLIST_FIXED
875 Sets the address of the bloblist, set up by the first part of U-Boot
876 which runs. Subsequent U-Boot phases typically use the same address.
878 This is not used if BLOBLIST_ALLOC is selected.
881 hex "Size of bloblist"
884 Sets the size of the bloblist in bytes. This must include all
885 overhead (alignment, bloblist header, record header). The bloblist
886 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
887 proper), and this sane bloblist is used for subsequent phases.
889 config BLOBLIST_SIZE_RELOC
890 hex "Size of bloblist after relocation"
891 default BLOBLIST_SIZE if BLOBLIST_FIXED || BLOBLIST_ALLOC
892 default 0 if BLOBLIST_PASSAGE
894 Sets the size of the bloblist in bytes after relocation. Since U-Boot
895 has a lot more memory available then, it is possible to use a larger
896 size than the one set up by SPL. This bloblist is set up during the
904 prompt "Bloblist location in SPL"
906 Select the location of the bloblist, via various means. Typically
907 you should use the same value for SPL as for U-Boot, since they need
908 to look in the same place. But if BLOBLIST_ALLOC is used, then a
909 fresh bloblist will be created each time, since there is no shared
910 address (between phases) for the bloblist.
912 config SPL_BLOBLIST_FIXED
913 bool "Place bloblist at a fixed address in memory"
915 Select this to used a fixed memory address for the bloblist. If the
916 bloblist exists at this address from a previous phase, it used as is.
917 If not it is created at this address in SPL.
919 config SPL_BLOBLIST_ALLOC
920 bool "Allocate bloblist"
922 Allocate the bloblist using malloc(). This avoids the need to
923 specify a fixed address on systems where this is unknown or can
933 prompt "Bloblist location in TPL"
935 Select the location of the bloblist, via various means. Typically
936 you should use the same value for SPL as for U-Boot, since they need
937 to look in the same place. But if BLOBLIST_ALLOC is used, then a
938 fresh bloblist will be created each time, since there is no shared
939 address (between phases) for the bloblist.
941 config TPL_BLOBLIST_FIXED
942 bool "Place bloblist at a fixed address in memory"
944 Select this to used a fixed memory address for the bloblist. If the
945 bloblist exists at this address from a previous phase, it used as is.
946 If not it is created at this address in TPL.
948 config TPL_BLOBLIST_ALLOC
949 bool "Allocate bloblist"
951 Allocate the bloblist using malloc(). This avoids the need to
952 specify a fixed address on systems where this is unknown or can
961 source "common/spl/Kconfig"
963 config IMAGE_SIGN_INFO
968 Enable image_sign_info helper functions.
972 config SPL_IMAGE_SIGN_INFO
977 Enable image_sign_info helper functions in SPL.
982 bool "FDT tools for simplefb support"
985 Enable the fdt tools to manage the simple fb nodes in device tree.
986 These functions can be used by board to indicate to the OS
987 the presence of the simple frame buffer with associated reserved