blob: 30cba15948b431376ba559006f0ef8bfbc05facc [file] [log] [blame]
Simon Glassee2b2432015-03-02 17:04:37 -07001menu "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
Robert P. J. Day57247d92016-08-31 12:49:13 -040012 add up all the accumulated time and report it.
Simon Glassee2b2432015-03-02 17:04:37 -070013
14 Normally, IDs are defined in bootstage.h but a small number of
Robert P. J. Day57247d92016-08-31 12:49:13 -040015 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
Simon Glassee2b2432015-03-02 17:04:37 -070016 as the ID.
17
Robert P. J. Day57247d92016-08-31 12:49:13 -040018 Calls to show_boot_progress() will also result in log entries but
Simon Glassee2b2432015-03-02 17:04:37 -070019 these will not have names.
20
Simon Glass824bb1b2017-05-22 05:05:35 -060021config 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
Simon Glassc0126bd2018-11-06 15:21:28 -070030config TPL_BOOTSTAGE
31 bool "Boot timing and reported in TPL"
32 depends on BOOTSTAGE
33 help
34 Enable recording of boot time in SPL. To make this visible to U-Boot
35 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
36 information when TPL finishes and load it when U-Boot proper starts
37 up.
38
Simon Glassee2b2432015-03-02 17:04:37 -070039config BOOTSTAGE_REPORT
40 bool "Display a detailed boot timing report before booting the OS"
41 depends on BOOTSTAGE
42 help
43 Enable output of a boot time report just before the OS is booted.
44 This shows how long it took U-Boot to go through each stage of the
45 boot process. The report looks something like this:
46
47 Timer summary in microseconds:
48 Mark Elapsed Stage
49 0 0 reset
50 3,575,678 3,575,678 board_init_f start
51 3,575,695 17 arch_cpu_init A9
52 3,575,777 82 arch_cpu_init done
53 3,659,598 83,821 board_init_r start
54 3,910,375 250,777 main_loop
55 29,916,167 26,005,792 bootm_start
56 30,361,327 445,160 start_kernel
57
Simon Glass03ecac32017-05-22 05:05:27 -060058config 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
Simon Glassd69bb0e2017-09-05 19:49:49 -060065config SPL_BOOTSTAGE_RECORD_COUNT
66 int "Number of boot stage records to store for SPL"
67 default 5
68 help
69 This is the size of the bootstage record list and is the maximum
70 number of bootstage records that can be recorded.
71
Simon Glass59d04522019-05-18 11:59:52 -060072config TPL_BOOTSTAGE_RECORD_COUNT
73 int "Number of boot stage records to store for TPL"
74 default 5
75 help
76 This is the size of the bootstage record list and is the maximum
77 number of bootstage records that can be recorded.
78
Simon Glassee2b2432015-03-02 17:04:37 -070079config BOOTSTAGE_FDT
80 bool "Store boot timing information in the OS device tree"
81 depends on BOOTSTAGE
82 help
83 Stash the bootstage information in the FDT. A root 'bootstage'
84 node is created with each bootstage id as a child. Each child
85 has a 'name' property and either 'mark' containing the
Robert P. J. Day57247d92016-08-31 12:49:13 -040086 mark time in microseconds, or 'accum' containing the
Simon Glassee2b2432015-03-02 17:04:37 -070087 accumulated time for that bootstage id in microseconds.
88 For example:
89
90 bootstage {
91 154 {
92 name = "board_init_f";
93 mark = <3575678>;
94 };
95 170 {
96 name = "lcd";
97 accum = <33482>;
98 };
99 };
100
101 Code in the Linux kernel can find this in /proc/devicetree.
102
103config BOOTSTAGE_STASH
104 bool "Stash the boot timing information in memory before booting OS"
105 depends on BOOTSTAGE
106 help
107 Some OSes do not support device tree. Bootstage can instead write
108 the boot timing information in a binary format at a given address.
109 This happens through a call to bootstage_stash(), typically in
110 the CPU's cleanup_before_linux() function. You can use the
111 'bootstage stash' and 'bootstage unstash' commands to do this on
112 the command line.
113
114config BOOTSTAGE_STASH_ADDR
115 hex "Address to stash boot timing information"
116 default 0
117 help
118 Provide an address which will not be overwritten by the OS when it
119 starts, so that it can read this information when ready.
120
121config BOOTSTAGE_STASH_SIZE
122 hex "Size of boot timing stash region"
Nobuhiro Iwamatsufad6a2b2017-04-02 07:48:12 +0900123 default 0x1000
Simon Glassee2b2432015-03-02 17:04:37 -0700124 help
125 This should be large enough to hold the bootstage stash. A value of
126 4096 (4KiB) is normally plenty.
127
Simon Glass9f531462019-07-20 20:51:12 -0600128config SHOW_BOOT_PROGRESS
129 bool "Show boot progress in a board-specific manner"
130 help
131 Defining this option allows to add some board-specific code (calling
132 a user-provided function show_boot_progress(int) that enables you to
133 show the system's boot progress on some display (for example, some
134 LEDs) on your board. At the moment, the following checkpoints are
135 implemented:
136
137 Legacy uImage format:
138
139 Arg Where When
140 1 common/cmd_bootm.c before attempting to boot an image
141 -1 common/cmd_bootm.c Image header has bad magic number
142 2 common/cmd_bootm.c Image header has correct magic number
143 -2 common/cmd_bootm.c Image header has bad checksum
144 3 common/cmd_bootm.c Image header has correct checksum
145 -3 common/cmd_bootm.c Image data has bad checksum
146 4 common/cmd_bootm.c Image data has correct checksum
147 -4 common/cmd_bootm.c Image is for unsupported architecture
148 5 common/cmd_bootm.c Architecture check OK
149 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
150 6 common/cmd_bootm.c Image Type check OK
151 -6 common/cmd_bootm.c gunzip uncompression error
152 -7 common/cmd_bootm.c Unimplemented compression type
153 7 common/cmd_bootm.c Uncompression OK
154 8 common/cmd_bootm.c No uncompress/copy overwrite error
155 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
156
157 9 common/image.c Start initial ramdisk verification
158 -10 common/image.c Ramdisk header has bad magic number
159 -11 common/image.c Ramdisk header has bad checksum
160 10 common/image.c Ramdisk header is OK
161 -12 common/image.c Ramdisk data has bad checksum
162 11 common/image.c Ramdisk data has correct checksum
163 12 common/image.c Ramdisk verification complete, start loading
164 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
165 13 common/image.c Start multifile image verification
166 14 common/image.c No initial ramdisk, no multifile, continue.
167
168 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
169
170 -30 arch/powerpc/lib/board.c Fatal error, hang the system
171 -31 post/post.c POST test failed, detected by post_output_backlog()
172 -32 post/post.c POST test failed, detected by post_run_single()
173
174 34 common/cmd_doc.c before loading a Image from a DOC device
175 -35 common/cmd_doc.c Bad usage of "doc" command
176 35 common/cmd_doc.c correct usage of "doc" command
177 -36 common/cmd_doc.c No boot device
178 36 common/cmd_doc.c correct boot device
179 -37 common/cmd_doc.c Unknown Chip ID on boot device
180 37 common/cmd_doc.c correct chip ID found, device available
181 -38 common/cmd_doc.c Read Error on boot device
182 38 common/cmd_doc.c reading Image header from DOC device OK
183 -39 common/cmd_doc.c Image header has bad magic number
184 39 common/cmd_doc.c Image header has correct magic number
185 -40 common/cmd_doc.c Error reading Image from DOC device
186 40 common/cmd_doc.c Image header has correct magic number
187 41 common/cmd_ide.c before loading a Image from a IDE device
188 -42 common/cmd_ide.c Bad usage of "ide" command
189 42 common/cmd_ide.c correct usage of "ide" command
190 -43 common/cmd_ide.c No boot device
191 43 common/cmd_ide.c boot device found
192 -44 common/cmd_ide.c Device not available
193 44 common/cmd_ide.c Device available
194 -45 common/cmd_ide.c wrong partition selected
195 45 common/cmd_ide.c partition selected
196 -46 common/cmd_ide.c Unknown partition table
197 46 common/cmd_ide.c valid partition table found
198 -47 common/cmd_ide.c Invalid partition type
199 47 common/cmd_ide.c correct partition type
200 -48 common/cmd_ide.c Error reading Image Header on boot device
201 48 common/cmd_ide.c reading Image Header from IDE device OK
202 -49 common/cmd_ide.c Image header has bad magic number
203 49 common/cmd_ide.c Image header has correct magic number
204 -50 common/cmd_ide.c Image header has bad checksum
205 50 common/cmd_ide.c Image header has correct checksum
206 -51 common/cmd_ide.c Error reading Image from IDE device
207 51 common/cmd_ide.c reading Image from IDE device OK
208 52 common/cmd_nand.c before loading a Image from a NAND device
209 -53 common/cmd_nand.c Bad usage of "nand" command
210 53 common/cmd_nand.c correct usage of "nand" command
211 -54 common/cmd_nand.c No boot device
212 54 common/cmd_nand.c boot device found
213 -55 common/cmd_nand.c Unknown Chip ID on boot device
214 55 common/cmd_nand.c correct chip ID found, device available
215 -56 common/cmd_nand.c Error reading Image Header on boot device
216 56 common/cmd_nand.c reading Image Header from NAND device OK
217 -57 common/cmd_nand.c Image header has bad magic number
218 57 common/cmd_nand.c Image header has correct magic number
219 -58 common/cmd_nand.c Error reading Image from NAND device
220 58 common/cmd_nand.c reading Image from NAND device OK
221
222 -60 common/env_common.c Environment has a bad CRC, using default
223
224 64 net/eth.c starting with Ethernet configuration.
225 -64 net/eth.c no Ethernet found.
226 65 net/eth.c Ethernet found.
227
228 -80 common/cmd_net.c usage wrong
229 80 common/cmd_net.c before calling net_loop()
230 -81 common/cmd_net.c some error in net_loop() occurred
231 81 common/cmd_net.c net_loop() back without error
232 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
233 82 common/cmd_net.c trying automatic boot
234 83 common/cmd_net.c running "source" command
235 -83 common/cmd_net.c some error in automatic boot or "source" command
236 84 common/cmd_net.c end without errors
237
238 FIT uImage format:
239
240 Arg Where When
241 100 common/cmd_bootm.c Kernel FIT Image has correct format
242 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
243 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
244 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
245 102 common/cmd_bootm.c Kernel unit name specified
246 -103 common/cmd_bootm.c Can't get kernel subimage node offset
247 103 common/cmd_bootm.c Found configuration node
248 104 common/cmd_bootm.c Got kernel subimage node offset
249 -104 common/cmd_bootm.c Kernel subimage hash verification failed
250 105 common/cmd_bootm.c Kernel subimage hash verification OK
251 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
252 106 common/cmd_bootm.c Architecture check OK
253 -106 common/cmd_bootm.c Kernel subimage has wrong type
254 107 common/cmd_bootm.c Kernel subimage type OK
255 -107 common/cmd_bootm.c Can't get kernel subimage data/size
256 108 common/cmd_bootm.c Got kernel subimage data/size
257 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
258 -109 common/cmd_bootm.c Can't get kernel subimage type
259 -110 common/cmd_bootm.c Can't get kernel subimage comp
260 -111 common/cmd_bootm.c Can't get kernel subimage os
261 -112 common/cmd_bootm.c Can't get kernel subimage load address
262 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
263
264 120 common/image.c Start initial ramdisk verification
265 -120 common/image.c Ramdisk FIT image has incorrect format
266 121 common/image.c Ramdisk FIT image has correct format
267 122 common/image.c No ramdisk subimage unit name, using configuration
268 -122 common/image.c Can't get configuration for ramdisk subimage
269 123 common/image.c Ramdisk unit name specified
270 -124 common/image.c Can't get ramdisk subimage node offset
271 125 common/image.c Got ramdisk subimage node offset
272 -125 common/image.c Ramdisk subimage hash verification failed
273 126 common/image.c Ramdisk subimage hash verification OK
274 -126 common/image.c Ramdisk subimage for unsupported architecture
275 127 common/image.c Architecture check OK
276 -127 common/image.c Can't get ramdisk subimage data/size
277 128 common/image.c Got ramdisk subimage data/size
278 129 common/image.c Can't get ramdisk load address
279 -129 common/image.c Got ramdisk load address
280
281 -130 common/cmd_doc.c Incorrect FIT image format
282 131 common/cmd_doc.c FIT image format OK
283
284 -140 common/cmd_ide.c Incorrect FIT image format
285 141 common/cmd_ide.c FIT image format OK
286
287 -150 common/cmd_nand.c Incorrect FIT image format
288 151 common/cmd_nand.c FIT image format OK
289
Simon Glassee2b2432015-03-02 17:04:37 -0700290endmenu
291
Peng Fand14739f2016-06-17 17:39:50 +0800292menu "Boot media"
293
294config NOR_BOOT
295 bool "Support for booting from NOR flash"
296 depends on NOR
297 help
298 Enabling this will make a U-Boot binary that is capable of being
299 booted via NOR. In this case we will enable certain pinmux early
300 as the ROM only partially sets up pinmux. We also default to using
301 NOR for environment.
302
Peng Fanfaaef732016-06-17 17:39:51 +0800303config NAND_BOOT
304 bool "Support for booting from NAND flash"
305 default n
Miquel Raynal88718be2019-10-03 19:50:03 +0200306 imply MTD_RAW_NAND
Peng Fanfaaef732016-06-17 17:39:51 +0800307 help
308 Enabling this will make a U-Boot binary that is capable of being
309 booted via NAND flash. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400310 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800311
312config ONENAND_BOOT
313 bool "Support for booting from ONENAND"
314 default n
Miquel Raynal88718be2019-10-03 19:50:03 +0200315 imply MTD_RAW_NAND
Peng Fanfaaef732016-06-17 17:39:51 +0800316 help
317 Enabling this will make a U-Boot binary that is capable of being
318 booted via ONENAND. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400319 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800320
321config QSPI_BOOT
322 bool "Support for booting from QSPI flash"
323 default n
324 help
325 Enabling this will make a U-Boot binary that is capable of being
326 booted via QSPI flash. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400327 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800328
329config SATA_BOOT
330 bool "Support for booting from SATA"
331 default n
332 help
333 Enabling this will make a U-Boot binary that is capable of being
334 booted via SATA. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400335 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800336
337config SD_BOOT
338 bool "Support for booting from SD/EMMC"
339 default n
340 help
341 Enabling this will make a U-Boot binary that is capable of being
342 booted via SD/EMMC. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400343 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800344
345config SPI_BOOT
346 bool "Support for booting from SPI flash"
347 default n
348 help
349 Enabling this will make a U-Boot binary that is capable of being
350 booted via SPI flash. This is not a must, some SoCs need this,
Robert P. J. Day57247d92016-08-31 12:49:13 -0400351 some not.
Peng Fanfaaef732016-06-17 17:39:51 +0800352
Peng Fand14739f2016-06-17 17:39:50 +0800353endmenu
354
Heiko Schocherbb597c02016-06-07 08:31:14 +0200355config BOOTDELAY
356 int "delay in seconds before automatically booting"
Tom Rini5e4e8742016-06-13 09:00:30 -0400357 default 2
Masahiro Yamada41598c82016-06-20 17:33:39 +0900358 depends on AUTOBOOT
Heiko Schocherbb597c02016-06-07 08:31:14 +0200359 help
360 Delay before automatically running bootcmd;
Masahiro Yamada2fbb8462016-06-27 16:23:01 +0900361 set to 0 to autoboot with no delay, but you can stop it by key input.
Heiko Schocherbb597c02016-06-07 08:31:14 +0200362 set to -1 to disable autoboot.
363 set to -2 to autoboot with no delay and not check for abort
Heiko Schocherbb597c02016-06-07 08:31:14 +0200364
Alex Kiernanb27dc8e2018-07-05 12:38:16 +0000365 If this value is >= 0 then it is also used for the default delay
366 before starting the default entry in bootmenu. If it is < 0 then
367 a default value of 10s is used.
368
Masahiro Yamada90609702016-06-27 16:23:00 +0900369 See doc/README.autoboot for details.
370
Sam Protsenko5abc1a42017-08-14 20:22:17 +0300371config USE_BOOTARGS
372 bool "Enable boot arguments"
373 help
374 Provide boot arguments to bootm command. Boot arguments are specified
375 in CONFIG_BOOTARGS option. Enable this option to be able to specify
376 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
377 will be undefined and won't take any space in U-Boot image.
378
379config BOOTARGS
380 string "Boot arguments"
381 depends on USE_BOOTARGS
382 help
383 This can be used to pass arguments to the bootm command. The value of
384 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
385 this value will also override the "chosen" node in FDT blob.
386
Tom Rinib6251db2017-11-06 18:15:11 -0500387config USE_BOOTCOMMAND
388 bool "Enable a default value for bootcmd"
389 help
390 Provide a default value for the bootcmd entry in the environment. If
391 autoboot is enabled this is what will be run automatically. Enable
392 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
393 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
394 won't take any space in U-Boot image.
395
396config BOOTCOMMAND
397 string "bootcmd value"
398 depends on USE_BOOTCOMMAND
399 default "run distro_bootcmd" if DISTRO_DEFAULTS
400 help
401 This is the string of commands that will be used as bootcmd and if
402 AUTOBOOT is set, automatically run.
403
Masahiro Yamada607d06d2019-02-14 11:05:33 +0900404config USE_PREBOOT
405 bool "Enable preboot"
406 help
407 When this option is enabled, the existence of the environment
408 variable "preboot" will be checked immediately before starting the
409 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
410 entering interactive mode.
411
412 This feature is especially useful when "preboot" is automatically
413 generated or modified. For example, the boot code can modify the
414 "preboot" when a user holds down a certain combination of keys.
415
416config PREBOOT
417 string "preboot default value"
418 depends on USE_PREBOOT
Patrick Delaunayce3772c2019-04-18 17:32:38 +0200419 default ""
Masahiro Yamada607d06d2019-02-14 11:05:33 +0900420 help
421 This is the default of "preboot" environment variable.
422
Simon Glass98af8792016-10-17 20:12:35 -0600423menu "Console"
424
Tom Rini4880b022016-11-29 09:14:56 -0500425config MENU
426 bool
427 help
428 This is the library functionality to provide a text-based menu of
429 choices for the user to make choices with.
430
Simon Glass9854a872015-11-08 23:47:48 -0700431config CONSOLE_RECORD
432 bool "Console recording"
433 help
434 This provides a way to record console output (and provide console
Robert P. J. Day57247d92016-08-31 12:49:13 -0400435 input) through circular buffers. This is mostly useful for testing.
Simon Glass9854a872015-11-08 23:47:48 -0700436 Console output is recorded even when the console is silent.
437 To enable console recording, call console_record_reset_enable()
438 from your code.
439
440config CONSOLE_RECORD_OUT_SIZE
441 hex "Output buffer size"
442 depends on CONSOLE_RECORD
443 default 0x400 if CONSOLE_RECORD
444 help
445 Set the size of the console output buffer. When this fills up, no
446 more data will be recorded until some is removed. The buffer is
447 allocated immediately after the malloc() region is ready.
448
449config CONSOLE_RECORD_IN_SIZE
450 hex "Input buffer size"
451 depends on CONSOLE_RECORD
452 default 0x100 if CONSOLE_RECORD
453 help
454 Set the size of the console input buffer. When this contains data,
455 tstc() and getc() will use this in preference to real device input.
456 The buffer is allocated immediately after the malloc() region is
457 ready.
Siva Durga Prasad Paladugu4d255072016-07-19 10:42:22 +0530458
Christian Gmeiner83f6f602018-09-10 12:43:16 +0200459config DISABLE_CONSOLE
460 bool "Add functionality to disable console completely"
461 help
462 Disable console (in & out).
463
Siva Durga Prasad Paladugua4d88922016-07-29 15:31:47 +0530464config IDENT_STRING
465 string "Board specific string to be added to uboot version string"
466 help
467 This options adds the board specific name to u-boot version.
468
Masahiro Yamadab44b3022017-09-16 14:10:40 +0900469config LOGLEVEL
470 int "loglevel"
Tom Rini6a3e65d2017-10-04 16:44:30 -0400471 default 4
Marek Bykowski2aa69c92020-02-03 11:43:32 +0100472 range 0 10
Masahiro Yamadab44b3022017-09-16 14:10:40 +0900473 help
474 All Messages with a loglevel smaller than the console loglevel will
475 be compiled in. The loglevels are defined as follows:
476
Simon Glass6fc7e932019-02-16 20:24:34 -0700477 0 - emergency
478 1 - alert
479 2 - critical
480 3 - error
481 4 - warning
482 5 - note
483 6 - info
484 7 - debug
485 8 - debug content
486 9 - debug hardware I/O
Masahiro Yamadab44b3022017-09-16 14:10:40 +0900487
488config SPL_LOGLEVEL
489 int
490 default LOGLEVEL
491
Simon Glass4d8d3052018-11-15 18:43:49 -0700492config TPL_LOGLEVEL
493 int
494 default LOGLEVEL
495
Simon Glass98af8792016-10-17 20:12:35 -0600496config SILENT_CONSOLE
497 bool "Support a silent console"
498 help
499 This option allows the console to be silenced, meaning that no
500 output will appear on the console devices. This is controlled by
Chris Packhamf7597732019-01-11 15:30:50 +1300501 setting the environment variable 'silent' to a non-empty value.
Simon Glass98af8792016-10-17 20:12:35 -0600502 Note this also silences the console when booting Linux.
503
504 When the console is set up, the variable is checked, and the
505 GD_FLG_SILENT flag is set. Changing the environment variable later
506 will update the flag.
507
508config SILENT_U_BOOT_ONLY
509 bool "Only silence the U-Boot console"
510 depends on SILENT_CONSOLE
511 help
512 Normally when the U-Boot console is silenced, Linux's console is
513 also silenced (assuming the board boots into Linux). This option
514 allows the linux console to operate normally, even if U-Boot's
515 is silenced.
516
517config SILENT_CONSOLE_UPDATE_ON_SET
518 bool "Changes to the 'silent' environment variable update immediately"
519 depends on SILENT_CONSOLE
520 default y if SILENT_CONSOLE
521 help
522 When the 'silent' environment variable is changed, update the
523 console silence flag immediately. This allows 'setenv' to be used
524 to silence or un-silence the console.
525
526 The effect is that any change to the variable will affect the
527 GD_FLG_SILENT flag.
528
529config SILENT_CONSOLE_UPDATE_ON_RELOC
530 bool "Allow flags to take effect on relocation"
531 depends on SILENT_CONSOLE
532 help
533 In some cases the environment is not available until relocation
534 (e.g. NAND). This option makes the value of the 'silent'
535 environment variable take effect at relocation.
536
Simon Glass8f925582016-10-17 20:12:36 -0600537config PRE_CONSOLE_BUFFER
538 bool "Buffer characters before the console is available"
539 help
540 Prior to the console being initialised (i.e. serial UART
541 initialised etc) all console output is silently discarded.
542 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
543 buffer any console messages prior to the console being
544 initialised to a buffer. The buffer is a circular buffer, so
545 if it overflows, earlier output is discarded.
546
547 Note that this is not currently supported in SPL. It would be
548 useful to be able to share the pre-console buffer with SPL.
549
550config PRE_CON_BUF_SZ
551 int "Sets the size of the pre-console buffer"
552 depends on PRE_CONSOLE_BUFFER
553 default 4096
554 help
555 The size of the pre-console buffer affects how much console output
556 can be held before it overflows and starts discarding earlier
557 output. Normally there is very little output at this early stage,
558 unless debugging is enabled, so allow enough for ~10 lines of
559 text.
560
561 This is a useful feature if you are using a video console and
562 want to see the full boot output on the console. Without this
563 option only the post-relocation output will be displayed.
564
565config PRE_CON_BUF_ADDR
566 hex "Address of the pre-console buffer"
567 depends on PRE_CONSOLE_BUFFER
568 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
569 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
Jagan Teki38070172020-01-23 19:42:19 +0530570 default 0x0f000000 if ROCKCHIP_RK3288
Jagan Teki61853a72020-04-02 17:11:23 +0530571 default 0x0f200000 if ROCKCHIP_RK3399
Simon Glass8f925582016-10-17 20:12:36 -0600572 help
573 This sets the start address of the pre-console buffer. This must
574 be in available memory and is accessed before relocation and
575 possibly before DRAM is set up. Therefore choose an address
576 carefully.
577
578 We should consider removing this option and allocating the memory
579 in board_init_f_init_reserve() instead.
580
Simon Glassef26d602016-10-17 20:12:37 -0600581config CONSOLE_MUX
582 bool "Enable console multiplexing"
583 default y if DM_VIDEO || VIDEO || LCD
584 help
585 This allows multiple devices to be used for each console 'file'.
586 For example, stdout can be set to go to serial and video.
587 Similarly, stdin can be set to come from serial and keyboard.
588 Input can be provided from either source. Console multiplexing
589 adds a small amount of size to U-Boot. Changes to the environment
590 variables stdout, stdin and stderr will take effect immediately.
591
592config SYS_CONSOLE_IS_IN_ENV
593 bool "Select console devices from the environment"
594 default y if CONSOLE_MUX
595 help
596 This allows multiple input/output devices to be set at boot time.
597 For example, if stdout is set to "serial,video" then output will
598 be sent to both the serial and video devices on boot. The
599 environment variables can be updated after boot to change the
600 input/output devices.
601
Simon Glass84f2a5d2016-10-17 20:12:59 -0600602config SYS_CONSOLE_OVERWRITE_ROUTINE
603 bool "Allow board control over console overwriting"
604 help
605 If this is enabled, and the board-specific function
606 overwrite_console() returns 1, the stdin, stderr and stdout are
607 switched to the serial port, else the settings in the environment
608 are used. If this is not enabled, the console will not be switched
609 to serial.
610
Simon Glass3505bc52016-10-17 20:12:58 -0600611config SYS_CONSOLE_ENV_OVERWRITE
612 bool "Update environment variables during console init"
613 help
614 The console environment variables (stdout, stdin, stderr) can be
615 used to determine the correct console devices on start-up. This
616 option writes the console devices to these variables on console
617 start-up (after relocation). This causes the environment to be
618 updated to match the console devices actually chosen.
619
Simon Glassf3f3eff2016-10-17 20:13:00 -0600620config SYS_CONSOLE_INFO_QUIET
621 bool "Don't display the console devices on boot"
622 help
623 Normally U-Boot displays the current settings for stdout, stdin
624 and stderr on boot when the post-relocation console is set up.
Chris Packhamf7597732019-01-11 15:30:50 +1300625 Enable this option to suppress this output. It can be obtained by
Simon Glassf3f3eff2016-10-17 20:13:00 -0600626 calling stdio_print_current_devices() from board code.
627
Simon Glass869588d2016-10-17 20:13:02 -0600628config SYS_STDIO_DEREGISTER
629 bool "Allow deregistering stdio devices"
630 default y if USB_KEYBOARD
631 help
632 Generally there is no need to deregister stdio devices since they
633 are never deactivated. But if a stdio device is used which can be
634 removed (for example a USB keyboard) then this option can be
635 enabled to ensure this is handled correctly.
636
Simon Glass98af8792016-10-17 20:12:35 -0600637endmenu
638
Simon Glasse9c8d492017-12-04 13:48:24 -0700639menu "Logging"
640
641config LOG
642 bool "Enable logging support"
Michal Simek563273d2018-07-23 15:55:11 +0200643 depends on DM
Simon Glasse9c8d492017-12-04 13:48:24 -0700644 help
645 This enables support for logging of status and debug messages. These
646 can be displayed on the console, recorded in a memory buffer, or
647 discarded if not needed. Logging supports various categories and
648 levels of severity.
649
650config SPL_LOG
651 bool "Enable logging support in SPL"
Simon Glassc0126bd2018-11-06 15:21:28 -0700652 depends on LOG
653 help
654 This enables support for logging of status and debug messages. These
655 can be displayed on the console, recorded in a memory buffer, or
656 discarded if not needed. Logging supports various categories and
657 levels of severity.
658
659config TPL_LOG
660 bool "Enable logging support in TPL"
661 depends on LOG
Simon Glasse9c8d492017-12-04 13:48:24 -0700662 help
663 This enables support for logging of status and debug messages. These
664 can be displayed on the console, recorded in a memory buffer, or
665 discarded if not needed. Logging supports various categories and
666 levels of severity.
667
668config LOG_MAX_LEVEL
669 int "Maximum log level to record"
670 depends on LOG
671 default 5
672 help
673 This selects the maximum log level that will be recorded. Any value
674 higher than this will be ignored. If possible log statements below
675 this level will be discarded at build time. Levels:
676
Simon Glass6fc7e932019-02-16 20:24:34 -0700677 0 - emergency
678 1 - alert
679 2 - critical
680 3 - error
681 4 - warning
682 5 - note
683 6 - info
Simon Glasse9c8d492017-12-04 13:48:24 -0700684 7 - debug
Simon Glass6fc7e932019-02-16 20:24:34 -0700685 8 - debug content
686 9 - debug hardware I/O
Simon Glasse9c8d492017-12-04 13:48:24 -0700687
688config SPL_LOG_MAX_LEVEL
689 int "Maximum log level to record in SPL"
690 depends on SPL_LOG
691 default 3
692 help
693 This selects the maximum log level that will be recorded. Any value
694 higher than this will be ignored. If possible log statements below
695 this level will be discarded at build time. Levels:
696
Simon Glass6fc7e932019-02-16 20:24:34 -0700697 0 - emergency
698 1 - alert
699 2 - critical
700 3 - error
701 4 - warning
702 5 - note
703 6 - info
Simon Glasse9c8d492017-12-04 13:48:24 -0700704 7 - debug
Simon Glass6fc7e932019-02-16 20:24:34 -0700705 8 - debug content
706 9 - debug hardware I/O
Simon Glasse9c8d492017-12-04 13:48:24 -0700707
Simon Glass4d8d3052018-11-15 18:43:49 -0700708config TPL_LOG_MAX_LEVEL
709 int "Maximum log level to record in TPL"
710 depends on TPL_LOG
711 default 3
712 help
713 This selects the maximum log level that will be recorded. Any value
714 higher than this will be ignored. If possible log statements below
715 this level will be discarded at build time. Levels:
716
Simon Glass6fc7e932019-02-16 20:24:34 -0700717 0 - emergency
718 1 - alert
719 2 - critical
720 3 - error
721 4 - warning
722 5 - note
723 6 - info
Simon Glass4d8d3052018-11-15 18:43:49 -0700724 7 - debug
Simon Glass6fc7e932019-02-16 20:24:34 -0700725 8 - debug content
726 9 - debug hardware I/O
Simon Glass4d8d3052018-11-15 18:43:49 -0700727
Simon Glassf0b05c92019-02-16 20:24:35 -0700728config LOG_DEFAULT_LEVEL
729 int "Default logging level to display"
730 default 6
731 help
732 This is the default logging level set when U-Boot starts. It can
733 be adjusted later using the 'log level' command. Note that setting
Andy Shevchenko69264f42019-06-12 15:35:24 +0300734 this to a value above LOG_MAX_LEVEL will be ineffective, since the
Simon Glassf0b05c92019-02-16 20:24:35 -0700735 higher levels are not compiled in to U-Boot.
736
737 0 - emergency
738 1 - alert
739 2 - critical
740 3 - error
741 4 - warning
742 5 - note
743 6 - info
744 7 - debug
745 8 - debug content
746 9 - debug hardware I/O
747
Simon Glassc6d47532017-12-04 13:48:25 -0700748config LOG_CONSOLE
749 bool "Allow log output to the console"
750 depends on LOG
751 default y
752 help
753 Enables a log driver which writes log records to the console.
754 Generally the console is the serial port or LCD display. Only the
755 log message is shown - other details like level, category, file and
756 line number are omitted.
757
Simon Glass4d8d3052018-11-15 18:43:49 -0700758config SPL_LOG_CONSOLE
Simon Glassc6d47532017-12-04 13:48:25 -0700759 bool "Allow log output to the console in SPL"
Simon Glass4d8d3052018-11-15 18:43:49 -0700760 depends on SPL_LOG
761 default y
762 help
763 Enables a log driver which writes log records to the console.
764 Generally the console is the serial port or LCD display. Only the
765 log message is shown - other details like level, category, file and
766 line number are omitted.
767
768config TPL_LOG_CONSOLE
Simon South54b6aba2019-10-02 10:55:06 -0400769 bool "Allow log output to the console in TPL"
Simon Glass4d8d3052018-11-15 18:43:49 -0700770 depends on TPL_LOG
Simon Glassc6d47532017-12-04 13:48:25 -0700771 default y
772 help
773 Enables a log driver which writes log records to the console.
774 Generally the console is the serial port or LCD display. Only the
775 log message is shown - other details like level, category, file and
776 line number are omitted.
777
Heinrich Schuchardtbefadde2020-02-26 21:48:16 +0100778config LOG_SYSLOG
779 bool "Log output to syslog server"
780 depends on LOG && NET
781 help
782 Enables a log driver which broadcasts log records via UDP port 514
783 to syslog servers.
784
Simon Glassef11ed82017-12-04 13:48:27 -0700785config LOG_TEST
786 bool "Provide a test for logging"
Heinrich Schuchardtd1a02f52020-02-26 21:48:15 +0100787 depends on LOG && UNIT_TEST
Simon Glassef11ed82017-12-04 13:48:27 -0700788 default y if SANDBOX
789 help
790 This enables a 'log test' command to test logging. It is normally
791 executed from a pytest and simply outputs logging information
792 in various different ways to test that the logging system works
Chris Packhamf7597732019-01-11 15:30:50 +1300793 correctly with various settings.
Simon Glassef11ed82017-12-04 13:48:27 -0700794
Simon Glass3707c6e2017-12-28 13:14:23 -0700795config LOG_ERROR_RETURN
796 bool "Log all functions which return an error"
797 depends on LOG
798 help
799 When an error is returned in U-Boot it is sometimes difficult to
Chris Packhamf7597732019-01-11 15:30:50 +1300800 figure out the root cause. For example, reading from SPI flash may
Simon Glass3707c6e2017-12-28 13:14:23 -0700801 fail due to a problem in the SPI controller or due to the flash part
802 not returning the expected information. This option changes
803 log_ret() to log any errors it sees. With this option disabled,
804 log_ret() is a nop.
805
806 You can add log_ret() to all functions which return an error code.
807
Simon Glasse9c8d492017-12-04 13:48:24 -0700808endmenu
809
Adam Fordd021e942018-02-06 07:58:59 -0600810config SUPPORT_RAW_INITRD
811 bool "Enable raw initrd images"
812 help
813 Note, defining the SUPPORT_RAW_INITRD allows user to supply
814 kernel with raw initrd images. The syntax is slightly different, the
815 address of the initrd must be augmented by it's size, in the following
816 format: "<initrd address>:<initrd size>".
817
Jagan Tekid259c002016-10-08 18:00:10 +0530818config DEFAULT_FDT_FILE
819 string "Default fdt file"
820 help
821 This option is used to set the default fdt file to boot OS.
822
Adam Ford8ccf98b2018-07-29 13:13:29 -0500823config MISC_INIT_R
824 bool "Execute Misc Init"
825 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
826 default y if ARCH_OMAP2PLUS && !AM33XX
827 help
828 Enabling this option calls 'misc_init_r' function
829
Heiko Schocher9dd1d0a2016-09-09 08:12:49 +0200830config VERSION_VARIABLE
831 bool "add U-Boot environment variable vers"
832 default n
833 help
834 If this variable is defined, an environment variable
835 named "ver" is created by U-Boot showing the U-Boot
836 version as printed by the "version" command.
837 Any change to this variable will be reverted at the
838 next reset.
Simon Glassc2ae7d82016-09-12 23:18:22 -0600839
Jagan Tekide70fef2017-01-21 11:48:32 +0100840config BOARD_LATE_INIT
Michal Simek8eb55e12018-08-20 08:24:14 +0200841 bool "Execute Board late init"
Jagan Tekide70fef2017-01-21 11:48:32 +0100842 help
843 Sometimes board require some initialization code that might
844 require once the actual init done, example saving board specific env,
845 boot-modes etc. which eventually done at late.
846
847 So this config enable the late init code with the help of board_late_init
848 function which should defined on respective boards.
849
Lokesh Vutla19a97472016-10-08 14:41:44 -0400850config DISPLAY_CPUINFO
851 bool "Display information about the CPU during start up"
Alexey Brodkinf31414a2018-10-02 11:43:28 +0300852 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
Lokesh Vutla19a97472016-10-08 14:41:44 -0400853 help
854 Display information about the CPU that U-Boot is running on
855 when U-Boot starts up. The function print_cpuinfo() is called
856 to do this.
857
Lokesh Vutla84351792016-10-11 21:33:46 -0400858config DISPLAY_BOARDINFO
Mario Six78eba692018-03-28 14:38:17 +0200859 bool "Display information about the board during early start up"
Alexey Brodkinf31414a2018-10-02 11:43:28 +0300860 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
Lokesh Vutla84351792016-10-11 21:33:46 -0400861 help
862 Display information about the board that U-Boot is running on
863 when U-Boot starts up. The board function checkboard() is called
864 to do this.
865
Mario Six78eba692018-03-28 14:38:17 +0200866config DISPLAY_BOARDINFO_LATE
867 bool "Display information about the board during late start up"
868 help
869 Display information about the board that U-Boot is running on after
870 the relocation phase. The board function checkboard() is called to do
871 this.
872
Philipp Tomsich2acc24f2018-11-30 22:13:25 +0100873config BOUNCE_BUFFER
874 bool "Include bounce buffer API"
875 help
876 Some peripherals support DMA from a subset of physically
877 addressable memory only. To support such peripherals, the
878 bounce buffer API uses a temporary buffer: it copies data
879 to/from DMA regions while managing cache operations.
880
881 A second possible use of bounce buffers is their ability to
882 provide aligned buffers for DMA operations.
883
Simon Glassbed44f42019-01-11 18:37:06 -0700884config BOARD_TYPES
885 bool "Call get_board_type() to get and display the board type"
886 help
887 If this option is enabled, checkboard() will call get_board_type()
888 to get a string containing the board type and this will be
889 displayed immediately after the model is shown on the console
890 early in boot.
891
Simon Glassa4211922017-01-23 13:31:19 -0700892menu "Start-up hooks"
893
894config ARCH_EARLY_INIT_R
895 bool "Call arch-specific init soon after relocation"
Simon Glassa4211922017-01-23 13:31:19 -0700896 help
897 With this option U-Boot will call arch_early_init_r() soon after
898 relocation. Driver model is running by this point, and the cache
899 is on. Note that board_early_init_r() is called first, if
900 enabled. This can be used to set up architecture-specific devices.
901
Simon Glass45856012017-01-23 13:31:21 -0700902config ARCH_MISC_INIT
903 bool "Call arch-specific init after relocation, when console is ready"
904 help
905 With this option U-Boot will call arch_misc_init() after
906 relocation to allow miscellaneous arch-dependent initialisation
907 to be performed. This function should be defined by the board
Chris Packhamf7597732019-01-11 15:30:50 +1300908 and will be called after the console is set up, after relocation.
Simon Glass45856012017-01-23 13:31:21 -0700909
Simon Glassa5d67542017-01-23 13:31:20 -0700910config BOARD_EARLY_INIT_F
911 bool "Call board-specific init before relocation"
Simon Glassa5d67542017-01-23 13:31:20 -0700912 help
913 Some boards need to perform initialisation as soon as possible
914 after boot. With this option, U-Boot calls board_early_init_f()
915 after driver model is ready in the pre-relocation init sequence.
916 Note that the normal serial console is not yet set up, but the
917 debug UART will be available if enabled.
918
Mario Six02ddc142018-03-28 14:38:15 +0200919config BOARD_EARLY_INIT_R
920 bool "Call board-specific init after relocation"
921 help
922 Some boards need to perform initialisation as directly after
923 relocation. With this option, U-Boot calls board_early_init_r()
924 in the post-relocation init sequence.
925
Mario Six2aeb22d2018-03-28 14:38:16 +0200926config LAST_STAGE_INIT
927 bool "Call board-specific as last setup step"
928 help
929 Some boards need to perform initialisation immediately before control
930 is passed to the command-line interpreter (e.g. for initializations
931 that depend on later phases in the init sequence). With this option,
932 U-Boot calls last_stage_init() before the command-line interpreter is
933 started.
934
Simon Glassa4211922017-01-23 13:31:19 -0700935endmenu
936
Simon Glassd70f9192017-05-17 09:05:34 -0600937menu "Security support"
938
939config HASH
940 bool # "Support hashing API (SHA1, SHA256, etc.)"
941 help
942 This provides a way to hash data in memory using various supported
943 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
944 and the algorithms it supports are defined in common/hash.c. See
945 also CMD_HASH for command-line access.
946
Igor Opaniukb0aa74a2018-07-17 14:33:25 +0300947config AVB_VERIFY
948 bool "Build Android Verified Boot operations"
949 depends on LIBAVB && FASTBOOT
Eugeniu Rosca87c814d2018-08-14 02:43:05 +0200950 depends on PARTITION_UUIDS
Igor Opaniukb0aa74a2018-07-17 14:33:25 +0300951 help
952 This option enables compilation of bootloader-dependent operations,
953 used by Android Verified Boot 2.0 library (libavb). Includes:
954 * Helpers to process strings in order to build OS bootargs.
955 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
956 * Helpers to alloc/init/free avb ops.
957
Simon Glassc0126bd2018-11-06 15:21:28 -0700958config SPL_HASH
959 bool # "Support hashing API (SHA1, SHA256, etc.)"
960 help
961 This provides a way to hash data in memory using various supported
962 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
963 and the algorithms it supports are defined in common/hash.c. See
964 also CMD_HASH for command-line access.
965
966config TPL_HASH
967 bool # "Support hashing API (SHA1, SHA256, etc.)"
968 help
969 This provides a way to hash data in memory using various supported
970 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
971 and the algorithms it supports are defined in common/hash.c. See
972 also CMD_HASH for command-line access.
973
Simon Glassd70f9192017-05-17 09:05:34 -0600974endmenu
975
Marek Vasutb254c522018-02-10 16:22:06 +0100976menu "Update support"
977
978config UPDATE_TFTP
979 bool "Auto-update using fitImage via TFTP"
980 depends on FIT
981 help
982 This option allows performing update of NOR with data in fitImage
983 sent via TFTP boot.
984
985config UPDATE_TFTP_CNT_MAX
986 int "The number of connection retries during auto-update"
987 default 0
988 depends on UPDATE_TFTP
989
990config UPDATE_TFTP_MSEC_MAX
991 int "Delay in mSec to wait for the TFTP server during auto-update"
992 default 100
993 depends on UPDATE_TFTP
994
Ruslan Trofymenkod65e8da2019-07-05 15:37:32 +0300995config ANDROID_AB
996 bool "Android A/B updates"
997 default n
998 help
999 If enabled, adds support for the new Android A/B update model. This
1000 allows the bootloader to select which slot to boot from based on the
1001 information provided by userspace via the Android boot_ctrl HAL. This
1002 allows a bootloader to try a new version of the system but roll back
1003 to previous version if the new one didn't boot all the way.
1004
Marek Vasutb254c522018-02-10 16:22:06 +01001005endmenu
1006
Simon Glass9f407d42018-11-15 18:43:50 -07001007menu "Blob list"
1008
1009config BLOBLIST
1010 bool "Support for a bloblist"
1011 help
1012 This enables support for a bloblist in U-Boot, which can be passed
1013 from TPL to SPL to U-Boot proper (and potentially to Linux). The
1014 blob list supports multiple binary blobs of data, each with a tag,
1015 so that different U-Boot components can store data which can survive
1016 through to the next stage of the boot.
1017
1018config SPL_BLOBLIST
1019 bool "Support for a bloblist in SPL"
1020 depends on BLOBLIST
1021 default y if SPL
1022 help
1023 This enables a bloblist in SPL. If this is the first part of U-Boot
1024 to run, then the bloblist is set up in SPL and passed to U-Boot
1025 proper. If TPL also has a bloblist, then SPL uses the one from there.
1026
1027config TPL_BLOBLIST
1028 bool "Support for a bloblist in TPL"
1029 depends on BLOBLIST
1030 default y if TPL
1031 help
1032 This enables a bloblist in TPL. The bloblist is set up in TPL and
1033 passed to SPL and U-Boot proper.
1034
1035config BLOBLIST_SIZE
1036 hex "Size of bloblist"
1037 depends on BLOBLIST
1038 default 0x400
1039 help
1040 Sets the size of the bloblist in bytes. This must include all
1041 overhead (alignment, bloblist header, record header). The bloblist
1042 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
1043 proper), and this sane bloblist is used for subsequent stages.
1044
1045config BLOBLIST_ADDR
1046 hex "Address of bloblist"
1047 depends on BLOBLIST
1048 default 0xe000 if SANDBOX
1049 help
1050 Sets the address of the bloblist, set up by the first part of U-Boot
1051 which runs. Subsequent U-Boot stages typically use the same address.
1052
1053endmenu
1054
Simon Glassc2ae7d82016-09-12 23:18:22 -06001055source "common/spl/Kconfig"
AKASHI Takahirob983cc22020-02-21 15:12:55 +09001056
1057config IMAGE_SIGN_INFO
1058 bool
1059 select SHA1
1060 select SHA256
1061 help
1062 Enable image_sign_info helper functions.
Heinrich Schuchardt64411642020-04-15 18:46:21 +02001063
1064if IMAGE_SIGN_INFO
1065
1066config SPL_IMAGE_SIGN_INFO
1067 bool
1068 select SHA1
1069 select SHA256
1070 help
1071 Enable image_sign_info helper functions in SPL.
1072
1073endif