Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712
  1. source "common/Kconfig.boot"
  2. menu "Console"
  3. config MENU
  4. bool
  5. help
  6. This is the library functionality to provide a text-based menu of
  7. choices for the user to make choices with.
  8. config CONSOLE_RECORD
  9. bool "Console recording"
  10. help
  11. This provides a way to record console output (and provide console
  12. input) through circular buffers. This is mostly useful for testing.
  13. Console output is recorded even when the console is silent.
  14. To enable console recording, call console_record_reset_enable()
  15. from your code.
  16. config CONSOLE_RECORD_OUT_SIZE
  17. hex "Output buffer size"
  18. depends on CONSOLE_RECORD
  19. default 0x400 if CONSOLE_RECORD
  20. help
  21. Set the size of the console output buffer. When this fills up, no
  22. more data will be recorded until some is removed. The buffer is
  23. allocated immediately after the malloc() region is ready.
  24. config CONSOLE_RECORD_IN_SIZE
  25. hex "Input buffer size"
  26. depends on CONSOLE_RECORD
  27. default 0x100 if CONSOLE_RECORD
  28. help
  29. Set the size of the console input buffer. When this contains data,
  30. tstc() and getc() will use this in preference to real device input.
  31. The buffer is allocated immediately after the malloc() region is
  32. ready.
  33. config DISABLE_CONSOLE
  34. bool "Add functionality to disable console completely"
  35. help
  36. Disable console (in & out).
  37. config IDENT_STRING
  38. string "Board specific string to be added to uboot version string"
  39. help
  40. This options adds the board specific name to u-boot version.
  41. config LOGLEVEL
  42. int "loglevel"
  43. default 4
  44. range 0 10
  45. help
  46. All Messages with a loglevel smaller than the console loglevel will
  47. be compiled in. The loglevels are defined as follows:
  48. 0 - emergency
  49. 1 - alert
  50. 2 - critical
  51. 3 - error
  52. 4 - warning
  53. 5 - note
  54. 6 - info
  55. 7 - debug
  56. 8 - debug content
  57. 9 - debug hardware I/O
  58. config SPL_LOGLEVEL
  59. int
  60. default LOGLEVEL
  61. config TPL_LOGLEVEL
  62. int
  63. default LOGLEVEL
  64. config SILENT_CONSOLE
  65. bool "Support a silent console"
  66. help
  67. This option allows the console to be silenced, meaning that no
  68. output will appear on the console devices. This is controlled by
  69. setting the environment variable 'silent' to a non-empty value.
  70. Note this also silences the console when booting Linux.
  71. When the console is set up, the variable is checked, and the
  72. GD_FLG_SILENT flag is set. Changing the environment variable later
  73. will update the flag.
  74. config SILENT_U_BOOT_ONLY
  75. bool "Only silence the U-Boot console"
  76. depends on SILENT_CONSOLE
  77. help
  78. Normally when the U-Boot console is silenced, Linux's console is
  79. also silenced (assuming the board boots into Linux). This option
  80. allows the linux console to operate normally, even if U-Boot's
  81. is silenced.
  82. config SILENT_CONSOLE_UPDATE_ON_SET
  83. bool "Changes to the 'silent' environment variable update immediately"
  84. depends on SILENT_CONSOLE
  85. default y if SILENT_CONSOLE
  86. help
  87. When the 'silent' environment variable is changed, update the
  88. console silence flag immediately. This allows 'setenv' to be used
  89. to silence or un-silence the console.
  90. The effect is that any change to the variable will affect the
  91. GD_FLG_SILENT flag.
  92. config SILENT_CONSOLE_UPDATE_ON_RELOC
  93. bool "Allow flags to take effect on relocation"
  94. depends on SILENT_CONSOLE
  95. help
  96. In some cases the environment is not available until relocation
  97. (e.g. NAND). This option makes the value of the 'silent'
  98. environment variable take effect at relocation.
  99. config PRE_CONSOLE_BUFFER
  100. bool "Buffer characters before the console is available"
  101. help
  102. Prior to the console being initialised (i.e. serial UART
  103. initialised etc) all console output is silently discarded.
  104. Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
  105. buffer any console messages prior to the console being
  106. initialised to a buffer. The buffer is a circular buffer, so
  107. if it overflows, earlier output is discarded.
  108. Note that this is not currently supported in SPL. It would be
  109. useful to be able to share the pre-console buffer with SPL.
  110. config PRE_CON_BUF_SZ
  111. int "Sets the size of the pre-console buffer"
  112. depends on PRE_CONSOLE_BUFFER
  113. default 4096
  114. help
  115. The size of the pre-console buffer affects how much console output
  116. can be held before it overflows and starts discarding earlier
  117. output. Normally there is very little output at this early stage,
  118. unless debugging is enabled, so allow enough for ~10 lines of
  119. text.
  120. This is a useful feature if you are using a video console and
  121. want to see the full boot output on the console. Without this
  122. option only the post-relocation output will be displayed.
  123. config PRE_CON_BUF_ADDR
  124. hex "Address of the pre-console buffer"
  125. depends on PRE_CONSOLE_BUFFER
  126. default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
  127. default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
  128. default 0x0f000000 if ROCKCHIP_RK3288
  129. default 0x0f200000 if ROCKCHIP_RK3399
  130. help
  131. This sets the start address of the pre-console buffer. This must
  132. be in available memory and is accessed before relocation and
  133. possibly before DRAM is set up. Therefore choose an address
  134. carefully.
  135. We should consider removing this option and allocating the memory
  136. in board_init_f_init_reserve() instead.
  137. config CONSOLE_MUX
  138. bool "Enable console multiplexing"
  139. default y if DM_VIDEO || VIDEO || LCD
  140. help
  141. This allows multiple devices to be used for each console 'file'.
  142. For example, stdout can be set to go to serial and video.
  143. Similarly, stdin can be set to come from serial and keyboard.
  144. Input can be provided from either source. Console multiplexing
  145. adds a small amount of size to U-Boot. Changes to the environment
  146. variables stdout, stdin and stderr will take effect immediately.
  147. config SYS_CONSOLE_IS_IN_ENV
  148. bool "Select console devices from the environment"
  149. default y if CONSOLE_MUX
  150. help
  151. This allows multiple input/output devices to be set at boot time.
  152. For example, if stdout is set to "serial,video" then output will
  153. be sent to both the serial and video devices on boot. The
  154. environment variables can be updated after boot to change the
  155. input/output devices.
  156. config SYS_CONSOLE_OVERWRITE_ROUTINE
  157. bool "Allow board control over console overwriting"
  158. help
  159. If this is enabled, and the board-specific function
  160. overwrite_console() returns 1, the stdin, stderr and stdout are
  161. switched to the serial port, else the settings in the environment
  162. are used. If this is not enabled, the console will not be switched
  163. to serial.
  164. config SYS_CONSOLE_ENV_OVERWRITE
  165. bool "Update environment variables during console init"
  166. help
  167. The console environment variables (stdout, stdin, stderr) can be
  168. used to determine the correct console devices on start-up. This
  169. option writes the console devices to these variables on console
  170. start-up (after relocation). This causes the environment to be
  171. updated to match the console devices actually chosen.
  172. config SYS_CONSOLE_INFO_QUIET
  173. bool "Don't display the console devices on boot"
  174. help
  175. Normally U-Boot displays the current settings for stdout, stdin
  176. and stderr on boot when the post-relocation console is set up.
  177. Enable this option to suppress this output. It can be obtained by
  178. calling stdio_print_current_devices() from board code.
  179. config SYS_STDIO_DEREGISTER
  180. bool "Allow deregistering stdio devices"
  181. default y if USB_KEYBOARD
  182. help
  183. Generally there is no need to deregister stdio devices since they
  184. are never deactivated. But if a stdio device is used which can be
  185. removed (for example a USB keyboard) then this option can be
  186. enabled to ensure this is handled correctly.
  187. config SPL_SYS_STDIO_DEREGISTER
  188. bool "Allow deregistering stdio devices in SPL"
  189. help
  190. Generally there is no need to deregister stdio devices since they
  191. are never deactivated. But if a stdio device is used which can be
  192. removed (for example a USB keyboard) then this option can be
  193. enabled to ensure this is handled correctly. This is very rarely
  194. needed in SPL.
  195. config SYS_DEVICE_NULLDEV
  196. bool "Enable a null device for stdio"
  197. default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
  198. help
  199. Enable creation of a "nulldev" stdio device. This allows silent
  200. operation of the console by setting stdout to "nulldev". Enable
  201. this to use a serial console under board control.
  202. endmenu
  203. menu "Logging"
  204. config LOG
  205. bool "Enable logging support"
  206. depends on DM
  207. help
  208. This enables support for logging of status and debug messages. These
  209. can be displayed on the console, recorded in a memory buffer, or
  210. discarded if not needed. Logging supports various categories and
  211. levels of severity.
  212. if LOG
  213. config LOG_MAX_LEVEL
  214. int "Maximum log level to record"
  215. default 6
  216. range 0 9
  217. help
  218. This selects the maximum log level that will be recorded. Any value
  219. higher than this will be ignored. If possible log statements below
  220. this level will be discarded at build time. Levels:
  221. 0 - emergency
  222. 1 - alert
  223. 2 - critical
  224. 3 - error
  225. 4 - warning
  226. 5 - note
  227. 6 - info
  228. 7 - debug
  229. 8 - debug content
  230. 9 - debug hardware I/O
  231. config LOG_DEFAULT_LEVEL
  232. int "Default logging level to display"
  233. default LOG_MAX_LEVEL
  234. range 0 LOG_MAX_LEVEL
  235. help
  236. This is the default logging level set when U-Boot starts. It can
  237. be adjusted later using the 'log level' command. Note that setting
  238. this to a value above LOG_MAX_LEVEL will be ineffective, since the
  239. higher levels are not compiled in to U-Boot.
  240. 0 - emergency
  241. 1 - alert
  242. 2 - critical
  243. 3 - error
  244. 4 - warning
  245. 5 - note
  246. 6 - info
  247. 7 - debug
  248. 8 - debug content
  249. 9 - debug hardware I/O
  250. config LOG_CONSOLE
  251. bool "Allow log output to the console"
  252. default y
  253. help
  254. Enables a log driver which writes log records to the console.
  255. Generally the console is the serial port or LCD display. Only the
  256. log message is shown - other details like level, category, file and
  257. line number are omitted.
  258. config LOGF_FILE
  259. bool "Show source file name in log messages by default"
  260. help
  261. Show the source file name in log messages by default. This value
  262. can be overridden using the 'log format' command.
  263. config LOGF_LINE
  264. bool "Show source line number in log messages by default"
  265. help
  266. Show the source line number in log messages by default. This value
  267. can be overridden using the 'log format' command.
  268. config LOGF_FUNC
  269. bool "Show function name in log messages by default"
  270. help
  271. Show the function name in log messages by default. This value can
  272. be overridden using the 'log format' command.
  273. config LOG_SYSLOG
  274. bool "Log output to syslog server"
  275. depends on NET
  276. help
  277. Enables a log driver which broadcasts log records via UDP port 514
  278. to syslog servers.
  279. config SPL_LOG
  280. bool "Enable logging support in SPL"
  281. depends on LOG
  282. help
  283. This enables support for logging of status and debug messages. These
  284. can be displayed on the console, recorded in a memory buffer, or
  285. discarded if not needed. Logging supports various categories and
  286. levels of severity.
  287. if SPL_LOG
  288. config SPL_LOG_MAX_LEVEL
  289. int "Maximum log level to record in SPL"
  290. depends on SPL_LOG
  291. default 3
  292. range 0 9
  293. help
  294. This selects the maximum log level that will be recorded. Any value
  295. higher than this will be ignored. If possible log statements below
  296. this level will be discarded at build time. Levels:
  297. 0 - emergency
  298. 1 - alert
  299. 2 - critical
  300. 3 - error
  301. 4 - warning
  302. 5 - note
  303. 6 - info
  304. 7 - debug
  305. 8 - debug content
  306. 9 - debug hardware I/O
  307. config SPL_LOG_CONSOLE
  308. bool "Allow log output to the console in SPL"
  309. default y
  310. help
  311. Enables a log driver which writes log records to the console.
  312. Generally the console is the serial port or LCD display. Only the
  313. log message is shown - other details like level, category, file and
  314. line number are omitted.
  315. endif
  316. config TPL_LOG
  317. bool "Enable logging support in TPL"
  318. depends on LOG
  319. help
  320. This enables support for logging of status and debug messages. These
  321. can be displayed on the console, recorded in a memory buffer, or
  322. discarded if not needed. Logging supports various categories and
  323. levels of severity.
  324. if TPL_LOG
  325. config TPL_LOG_MAX_LEVEL
  326. int "Maximum log level to record in TPL"
  327. depends on TPL_LOG
  328. default 3
  329. range 0 9
  330. help
  331. This selects the maximum log level that will be recorded. Any value
  332. higher than this will be ignored. If possible log statements below
  333. this level will be discarded at build time. Levels:
  334. 0 - emergency
  335. 1 - alert
  336. 2 - critical
  337. 3 - error
  338. 4 - warning
  339. 5 - note
  340. 6 - info
  341. 7 - debug
  342. 8 - debug content
  343. 9 - debug hardware I/O
  344. config TPL_LOG_CONSOLE
  345. bool "Allow log output to the console in TPL"
  346. default y
  347. help
  348. Enables a log driver which writes log records to the console.
  349. Generally the console is the serial port or LCD display. Only the
  350. log message is shown - other details like level, category, file and
  351. line number are omitted.
  352. endif
  353. config LOG_ERROR_RETURN
  354. bool "Log all functions which return an error"
  355. help
  356. When an error is returned in U-Boot it is sometimes difficult to
  357. figure out the root cause. For example, reading from SPI flash may
  358. fail due to a problem in the SPI controller or due to the flash part
  359. not returning the expected information. This option changes
  360. log_ret() to log any errors it sees. With this option disabled,
  361. log_ret() is a nop.
  362. You can add log_ret() to all functions which return an error code.
  363. config LOG_TEST
  364. bool "Provide a test for logging"
  365. depends on UNIT_TEST
  366. default y if SANDBOX
  367. help
  368. This enables a 'log test' command to test logging. It is normally
  369. executed from a pytest and simply outputs logging information
  370. in various different ways to test that the logging system works
  371. correctly with various settings.
  372. endif
  373. endmenu
  374. menu "Init options"
  375. config BOARD_TYPES
  376. bool "Call get_board_type() to get and display the board type"
  377. help
  378. If this option is enabled, checkboard() will call get_board_type()
  379. to get a string containing the board type and this will be
  380. displayed immediately after the model is shown on the console
  381. early in boot.
  382. config DISPLAY_CPUINFO
  383. bool "Display information about the CPU during start up"
  384. default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
  385. help
  386. Display information about the CPU that U-Boot is running on
  387. when U-Boot starts up. The function print_cpuinfo() is called
  388. to do this.
  389. config DISPLAY_BOARDINFO
  390. bool "Display information about the board during early start up"
  391. default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
  392. help
  393. Display information about the board that U-Boot is running on
  394. when U-Boot starts up. The board function checkboard() is called
  395. to do this.
  396. config DISPLAY_BOARDINFO_LATE
  397. bool "Display information about the board during late start up"
  398. help
  399. Display information about the board that U-Boot is running on after
  400. the relocation phase. The board function checkboard() is called to do
  401. this.
  402. menu "Start-up hooks"
  403. config ARCH_EARLY_INIT_R
  404. bool "Call arch-specific init soon after relocation"
  405. help
  406. With this option U-Boot will call arch_early_init_r() soon after
  407. relocation. Driver model is running by this point, and the cache
  408. is on. Note that board_early_init_r() is called first, if
  409. enabled. This can be used to set up architecture-specific devices.
  410. config ARCH_MISC_INIT
  411. bool "Call arch-specific init after relocation, when console is ready"
  412. help
  413. With this option U-Boot will call arch_misc_init() after
  414. relocation to allow miscellaneous arch-dependent initialisation
  415. to be performed. This function should be defined by the board
  416. and will be called after the console is set up, after relocation.
  417. config BOARD_EARLY_INIT_F
  418. bool "Call board-specific init before relocation"
  419. help
  420. Some boards need to perform initialisation as soon as possible
  421. after boot. With this option, U-Boot calls board_early_init_f()
  422. after driver model is ready in the pre-relocation init sequence.
  423. Note that the normal serial console is not yet set up, but the
  424. debug UART will be available if enabled.
  425. config BOARD_EARLY_INIT_R
  426. bool "Call board-specific init after relocation"
  427. help
  428. Some boards need to perform initialisation as directly after
  429. relocation. With this option, U-Boot calls board_early_init_r()
  430. in the post-relocation init sequence.
  431. config BOARD_LATE_INIT
  432. bool "Execute Board late init"
  433. help
  434. Sometimes board require some initialization code that might
  435. require once the actual init done, example saving board specific env,
  436. boot-modes etc. which eventually done at late.
  437. So this config enable the late init code with the help of board_late_init
  438. function which should defined on respective boards.
  439. config LAST_STAGE_INIT
  440. bool "Call board-specific as last setup step"
  441. help
  442. Some boards need to perform initialisation immediately before control
  443. is passed to the command-line interpreter (e.g. for initializations
  444. that depend on later phases in the init sequence). With this option,
  445. U-Boot calls last_stage_init() before the command-line interpreter is
  446. started.
  447. config MISC_INIT_R
  448. bool "Execute Misc Init"
  449. default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
  450. default y if ARCH_OMAP2PLUS && !AM33XX
  451. help
  452. Enabling this option calls 'misc_init_r' function
  453. config PCI_INIT_R
  454. bool "Enumerate PCI buses during init"
  455. depends on PCI
  456. default y if !DM_PCI
  457. help
  458. With this option U-Boot will call pci_init() soon after relocation,
  459. which will enumerate PCI buses. This is needed, for instance, in the
  460. case of DM PCI-based Ethernet devices, which will not be detected
  461. without having the enumeration performed earlier.
  462. endmenu
  463. endmenu # Init options
  464. menu "Security support"
  465. config HASH
  466. bool # "Support hashing API (SHA1, SHA256, etc.)"
  467. help
  468. This provides a way to hash data in memory using various supported
  469. algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
  470. and the algorithms it supports are defined in common/hash.c. See
  471. also CMD_HASH for command-line access.
  472. config AVB_VERIFY
  473. bool "Build Android Verified Boot operations"
  474. depends on LIBAVB
  475. depends on PARTITION_UUIDS
  476. help
  477. This option enables compilation of bootloader-dependent operations,
  478. used by Android Verified Boot 2.0 library (libavb). Includes:
  479. * Helpers to process strings in order to build OS bootargs.
  480. * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
  481. * Helpers to alloc/init/free avb ops.
  482. if AVB_VERIFY
  483. config AVB_BUF_ADDR
  484. hex "Define AVB buffer address"
  485. default FASTBOOT_BUF_ADDR
  486. help
  487. AVB requires a buffer for memory transactions. This variable defines the
  488. buffer address.
  489. config AVB_BUF_SIZE
  490. hex "Define AVB buffer SIZE"
  491. default FASTBOOT_BUF_SIZE
  492. help
  493. AVB requires a buffer for memory transactions. This variable defines the
  494. buffer size.
  495. endif # AVB_VERIFY
  496. config SPL_HASH
  497. bool # "Support hashing API (SHA1, SHA256, etc.)"
  498. help
  499. This provides a way to hash data in memory using various supported
  500. algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
  501. and the algorithms it supports are defined in common/hash.c. See
  502. also CMD_HASH for command-line access.
  503. config TPL_HASH
  504. bool # "Support hashing API (SHA1, SHA256, etc.)"
  505. help
  506. This provides a way to hash data in memory using various supported
  507. algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
  508. and the algorithms it supports are defined in common/hash.c. See
  509. also CMD_HASH for command-line access.
  510. endmenu
  511. menu "Update support"
  512. config UPDATE_COMMON
  513. bool
  514. default n
  515. select DFU_WRITE_ALT
  516. config UPDATE_TFTP
  517. bool "Auto-update using fitImage via TFTP"
  518. depends on FIT
  519. select UPDATE_COMMON
  520. help
  521. This option allows performing update of NOR with data in fitImage
  522. sent via TFTP boot.
  523. config UPDATE_TFTP_CNT_MAX
  524. int "The number of connection retries during auto-update"
  525. default 0
  526. depends on UPDATE_TFTP
  527. config UPDATE_TFTP_MSEC_MAX
  528. int "Delay in mSec to wait for the TFTP server during auto-update"
  529. default 100
  530. depends on UPDATE_TFTP
  531. config UPDATE_FIT
  532. bool "Firmware update using fitImage"
  533. depends on FIT
  534. depends on DFU
  535. select UPDATE_COMMON
  536. help
  537. This option allows performing update of DFU-capable storage with
  538. data in fitImage.
  539. config ANDROID_AB
  540. bool "Android A/B updates"
  541. default n
  542. help
  543. If enabled, adds support for the new Android A/B update model. This
  544. allows the bootloader to select which slot to boot from based on the
  545. information provided by userspace via the Android boot_ctrl HAL. This
  546. allows a bootloader to try a new version of the system but roll back
  547. to previous version if the new one didn't boot all the way.
  548. endmenu
  549. menu "Blob list"
  550. config BLOBLIST
  551. bool "Support for a bloblist"
  552. help
  553. This enables support for a bloblist in U-Boot, which can be passed
  554. from TPL to SPL to U-Boot proper (and potentially to Linux). The
  555. blob list supports multiple binary blobs of data, each with a tag,
  556. so that different U-Boot components can store data which can survive
  557. through to the next stage of the boot.
  558. config SPL_BLOBLIST
  559. bool "Support for a bloblist in SPL"
  560. depends on BLOBLIST
  561. default y if SPL
  562. help
  563. This enables a bloblist in SPL. If this is the first part of U-Boot
  564. to run, then the bloblist is set up in SPL and passed to U-Boot
  565. proper. If TPL also has a bloblist, then SPL uses the one from there.
  566. config TPL_BLOBLIST
  567. bool "Support for a bloblist in TPL"
  568. depends on BLOBLIST
  569. default y if TPL
  570. help
  571. This enables a bloblist in TPL. The bloblist is set up in TPL and
  572. passed to SPL and U-Boot proper.
  573. config BLOBLIST_SIZE
  574. hex "Size of bloblist"
  575. depends on BLOBLIST
  576. default 0x400
  577. help
  578. Sets the size of the bloblist in bytes. This must include all
  579. overhead (alignment, bloblist header, record header). The bloblist
  580. is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
  581. proper), and this sane bloblist is used for subsequent stages.
  582. config BLOBLIST_ADDR
  583. hex "Address of bloblist"
  584. depends on BLOBLIST
  585. default 0xe000 if SANDBOX
  586. help
  587. Sets the address of the bloblist, set up by the first part of U-Boot
  588. which runs. Subsequent U-Boot stages typically use the same address.
  589. endmenu
  590. source "common/spl/Kconfig"
  591. config IMAGE_SIGN_INFO
  592. bool
  593. select SHA1
  594. select SHA256
  595. help
  596. Enable image_sign_info helper functions.
  597. if IMAGE_SIGN_INFO
  598. config SPL_IMAGE_SIGN_INFO
  599. bool
  600. select SHA1
  601. select SHA256
  602. help
  603. Enable image_sign_info helper functions in SPL.
  604. endif