Fork of the vendor (Boundary Devices) u-boot for Reform 2, with minor tweaks. The goal is to migrate to mainstream u-boot or barebox ASAP. The main impediment so far is the 4GB RAM config.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

486 regels
16 KiB

  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see the file Documentation/kbuild/kconfig-language.txt in the
  4. # Linux kernel source tree.
  5. #
  6. mainmenu "U-Boot $UBOOTVERSION Configuration"
  7. config UBOOTVERSION
  8. string
  9. option env="UBOOTVERSION"
  10. # Allow defaults in arch-specific code to override any given here
  11. source "arch/Kconfig"
  12. menu "General setup"
  13. config BROKEN
  14. bool
  15. help
  16. This option cannot be enabled. It is used as dependency
  17. for broken and incomplete features.
  18. config LOCALVERSION
  19. string "Local version - append to U-Boot release"
  20. help
  21. Append an extra string to the end of your U-Boot version.
  22. This will show up in your boot log, for example.
  23. The string you set here will be appended after the contents of
  24. any files with a filename matching localversion* in your
  25. object and source tree, in that order. Your total string can
  26. be a maximum of 64 characters.
  27. config LOCALVERSION_AUTO
  28. bool "Automatically append version information to the version string"
  29. default y
  30. help
  31. This will try to automatically determine if the current tree is a
  32. release tree by looking for Git tags that belong to the current
  33. top of tree revision.
  34. A string of the format -gxxxxxxxx will be added to the localversion
  35. if a Git-based tree is found. The string generated by this will be
  36. appended after any matching localversion* files, and after the value
  37. set in CONFIG_LOCALVERSION.
  38. (The actual string used here is the first eight characters produced
  39. by running the command:
  40. $ git rev-parse --verify HEAD
  41. which is done within the script "scripts/setlocalversion".)
  42. config CC_OPTIMIZE_FOR_SIZE
  43. bool "Optimize for size"
  44. default y
  45. help
  46. Enabling this option will pass "-Os" instead of "-O2" to gcc
  47. resulting in a smaller U-Boot image.
  48. This option is enabled by default for U-Boot.
  49. config CC_COVERAGE
  50. bool "Enable code coverage analysis"
  51. depends on SANDBOX
  52. help
  53. Enabling this option will pass "--coverage" to gcc to compile
  54. and link code instrumented for coverage analysis.
  55. config DISTRO_DEFAULTS
  56. bool "Select defaults suitable for booting general purpose Linux distributions"
  57. imply USE_BOOTCOMMAND
  58. select CMD_BOOTZ if ARM && !ARM64
  59. select CMD_BOOTI if ARM64
  60. select CMD_DHCP if CMD_NET
  61. select CMD_PING if CMD_NET
  62. select CMD_PXE if NET
  63. select CMD_ENV_EXISTS
  64. select CMD_EXT2
  65. select CMD_EXT4
  66. select CMD_FAT
  67. select CMD_FS_GENERIC
  68. imply CMD_MII if NET
  69. select CMD_PART if PARTITIONS
  70. select HUSH_PARSER
  71. select CMDLINE_EDITING
  72. select AUTO_COMPLETE
  73. select SYS_LONGHELP
  74. select SUPPORT_RAW_INITRD
  75. select ENV_VARS_UBOOT_CONFIG
  76. help
  77. Select this to enable various options and commands which are suitable
  78. for building u-boot for booting general purpose Linux distributions.
  79. config ENV_VARS_UBOOT_CONFIG
  80. bool "Add arch, board, vendor and soc variables to default environment"
  81. help
  82. Define this in order to add variables describing the
  83. U-Boot build configuration to the default environment.
  84. These will be named arch, cpu, board, vendor, and soc.
  85. Enabling this option will cause the following to be defined:
  86. - CONFIG_SYS_ARCH
  87. - CONFIG_SYS_CPU
  88. - CONFIG_SYS_BOARD
  89. - CONFIG_SYS_VENDOR
  90. - CONFIG_SYS_SOC
  91. config NR_DRAM_BANKS
  92. int "Number of DRAM banks"
  93. default 4
  94. help
  95. This defines the number of DRAM banks.
  96. config SYS_BOOT_GET_CMDLINE
  97. bool "Enable kernel command line setup"
  98. help
  99. Enables allocating and saving kernel cmdline in space between
  100. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  101. config SYS_BOOT_GET_KBD
  102. bool "Enable kernel board information setup"
  103. help
  104. Enables allocating and saving a kernel copy of the bd_info in
  105. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  106. config SYS_MALLOC_F
  107. bool "Enable malloc() pool before relocation"
  108. default y if DM
  109. help
  110. Before relocation, memory is very limited on many platforms. Still,
  111. we can provide a small malloc() pool if needed. Driver model in
  112. particular needs this to operate, so that it can allocate the
  113. initial serial device and any others that are needed.
  114. config SYS_MALLOC_F_LEN
  115. hex "Size of malloc() pool before relocation"
  116. depends on SYS_MALLOC_F
  117. default 0x1000 if AM33XX
  118. default 0x400
  119. help
  120. Before relocation, memory is very limited on many platforms. Still,
  121. we can provide a small malloc() pool if needed. Driver model in
  122. particular needs this to operate, so that it can allocate the
  123. initial serial device and any others that are needed.
  124. config SPL_SYS_MALLOC_F_LEN
  125. hex "Size of malloc() pool in SPL before relocation"
  126. depends on SYS_MALLOC_F
  127. default SYS_MALLOC_F_LEN
  128. help
  129. Before relocation, memory is very limited on many platforms. Still,
  130. we can provide a small malloc() pool if needed. Driver model in
  131. particular needs this to operate, so that it can allocate the
  132. initial serial device and any others that are needed.
  133. config TPL_SYS_MALLOC_F_LEN
  134. hex "Size of malloc() pool in TPL before relocation"
  135. depends on SYS_MALLOC_F
  136. default SYS_MALLOC_F_LEN
  137. help
  138. Before relocation, memory is very limited on many platforms. Still,
  139. we can provide a small malloc() pool if needed. Driver model in
  140. particular needs this to operate, so that it can allocate the
  141. initial serial device and any others that are needed.
  142. menuconfig EXPERT
  143. bool "Configure standard U-Boot features (expert users)"
  144. default y
  145. help
  146. This option allows certain base U-Boot options and settings
  147. to be disabled or tweaked. This is for specialized
  148. environments which can tolerate a "non-standard" U-Boot.
  149. Use this only if you really know what you are doing.
  150. if EXPERT
  151. config SYS_MALLOC_CLEAR_ON_INIT
  152. bool "Init with zeros the memory reserved for malloc (slow)"
  153. default y
  154. help
  155. This setting is enabled by default. The reserved malloc
  156. memory is initialized with zeros, so first malloc calls
  157. will return the pointer to the zeroed memory. But this
  158. slows the boot time.
  159. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  160. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  161. Then the boot time can be significantly reduced.
  162. Warning:
  163. When disabling this, please check if malloc calls, maybe
  164. should be replaced by calloc - if one expects zeroed memory.
  165. config TOOLS_DEBUG
  166. bool "Enable debug information for tools"
  167. help
  168. Enable generation of debug information for tools such as mkimage.
  169. This can be used for debugging purposes. With debug information
  170. it is possible to set breakpoints on particular lines, single-step
  171. debug through the source code, etc.
  172. endif # EXPERT
  173. config PHYS_64BIT
  174. bool "64bit physical address support"
  175. help
  176. Say Y here to support 64bit physical memory address.
  177. This can be used not only for 64bit SoCs, but also for
  178. large physical address extention on 32bit SoCs.
  179. config BUILD_ROM
  180. bool "Build U-Boot as BIOS replacement"
  181. depends on X86
  182. help
  183. This option allows to build a ROM version of U-Boot.
  184. The build process generally requires several binary blobs
  185. which are not shipped in the U-Boot source tree.
  186. Please, see doc/README.x86 for details.
  187. endmenu # General setup
  188. menu "Boot images"
  189. config ANDROID_BOOT_IMAGE
  190. bool "Enable support for Android Boot Images"
  191. default y if FASTBOOT
  192. help
  193. This enables support for booting images which use the Android
  194. image format header.
  195. config FIT
  196. bool "Support Flattened Image Tree"
  197. select MD5
  198. select SHA1
  199. help
  200. This option allows you to boot the new uImage structure,
  201. Flattened Image Tree. FIT is formally a FDT, which can include
  202. images of various types (kernel, FDT blob, ramdisk, etc.)
  203. in a single blob. To boot this new uImage structure,
  204. pass the address of the blob to the "bootm" command.
  205. FIT is very flexible, supporting compression, multiple images,
  206. multiple configurations, verification through hashing and also
  207. verified boot (secure boot using RSA).
  208. if FIT
  209. config FIT_ENABLE_SHA256_SUPPORT
  210. bool "Support SHA256 checksum of FIT image contents"
  211. select SHA256
  212. default y
  213. help
  214. Enable this to support SHA256 checksum of FIT image contents. A
  215. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  216. the image contents have not been corrupted. SHA256 is recommended
  217. for use in secure applications since (as at 2016) there is no known
  218. feasible attack that could produce a 'collision' with differing
  219. input data. Use this for the highest security. Note that only the
  220. SHA256 variant is supported: SHA512 and others are not currently
  221. supported in U-Boot.
  222. config FIT_SIGNATURE
  223. bool "Enable signature verification of FIT uImages"
  224. depends on DM
  225. select RSA
  226. select HASH
  227. help
  228. This option enables signature verification of FIT uImages,
  229. using a hash signed and verified using RSA. If
  230. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  231. hashing is available using hardware, then the RSA library will use
  232. it. See doc/uImage.FIT/signature.txt for more details.
  233. WARNING: When relying on signed FIT images with a required signature
  234. check the legacy image format is disabled by default, so that
  235. unsigned images cannot be loaded. If a board needs the legacy image
  236. format support in this case, enable it using
  237. CONFIG_IMAGE_FORMAT_LEGACY.
  238. config FIT_VERBOSE
  239. bool "Show verbose messages when FIT images fail"
  240. help
  241. Generally a system will have valid FIT images so debug messages
  242. are a waste of code space. If you are debugging your images then
  243. you can enable this option to get more verbose information about
  244. failures.
  245. config FIT_BEST_MATCH
  246. bool "Select the best match for the kernel device tree"
  247. help
  248. When no configuration is explicitly selected, default to the
  249. one whose fdt's compatibility field best matches that of
  250. U-Boot itself. A match is considered "best" if it matches the
  251. most specific compatibility entry of U-Boot's fdt's root node.
  252. The order of entries in the configuration's fdt is ignored.
  253. config FIT_IMAGE_POST_PROCESS
  254. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  255. depends on TI_SECURE_DEVICE
  256. help
  257. Allows doing any sort of manipulation to blobs after they got extracted
  258. from FIT images like stripping off headers or modifying the size of the
  259. blob, verification, authentication, decryption etc. in a platform or
  260. board specific way. In order to use this feature a platform or board-
  261. specific implementation of board_fit_image_post_process() must be
  262. provided. Also, anything done during this post-processing step would
  263. need to be comprehended in how the images were prepared before being
  264. injected into the FIT creation (i.e. the blobs would have been pre-
  265. processed before being added to the FIT image).
  266. if SPL
  267. config SPL_FIT
  268. bool "Support Flattened Image Tree within SPL"
  269. depends on SPL
  270. select SPL_OF_LIBFDT
  271. config SPL_FIT_PRINT
  272. bool "Support FIT printing within SPL"
  273. depends on SPL_FIT
  274. help
  275. Support printing the content of the fitImage in a verbose manner in SPL.
  276. config SPL_FIT_SIGNATURE
  277. bool "Enable signature verification of FIT firmware within SPL"
  278. depends on SPL_DM
  279. select SPL_FIT
  280. select SPL_RSA
  281. config SPL_LOAD_FIT
  282. bool "Enable SPL loading U-Boot as a FIT"
  283. select SPL_FIT
  284. help
  285. Normally with the SPL framework a legacy image is generated as part
  286. of the build. This contains U-Boot along with information as to
  287. where it should be loaded. This option instead enables generation
  288. of a FIT (Flat Image Tree) which provides more flexibility. In
  289. particular it can handle selecting from multiple device tree
  290. and passing the correct one to U-Boot.
  291. config SPL_LOAD_FIT_FULL
  292. bool "Enable SPL loading U-Boot as a FIT"
  293. select SPL_FIT
  294. help
  295. Normally with the SPL framework a legacy image is generated as part
  296. of the build. This contains U-Boot along with information as to
  297. where it should be loaded. This option instead enables generation
  298. of a FIT (Flat Image Tree) which provides more flexibility. In
  299. particular it can handle selecting from multiple device tree
  300. and passing the correct one to U-Boot.
  301. config SPL_FIT_IMAGE_POST_PROCESS
  302. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  303. depends on SPL_LOAD_FIT
  304. help
  305. Allows doing any sort of manipulation to blobs after they got extracted
  306. from the U-Boot FIT image like stripping off headers or modifying the
  307. size of the blob, verification, authentication, decryption etc. in a
  308. platform or board specific way. In order to use this feature a platform
  309. or board-specific implementation of board_fit_image_post_process() must
  310. be provided. Also, anything done during this post-processing step would
  311. need to be comprehended in how the images were prepared before being
  312. injected into the FIT creation (i.e. the blobs would have been pre-
  313. processed before being added to the FIT image).
  314. config SPL_FIT_SOURCE
  315. string ".its source file for U-Boot FIT image"
  316. depends on SPL_FIT
  317. help
  318. Specifies a (platform specific) FIT source file to generate the
  319. U-Boot FIT image. This could specify further image to load and/or
  320. execute.
  321. config SPL_FIT_GENERATOR
  322. string ".its file generator script for U-Boot FIT image"
  323. depends on SPL_FIT
  324. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  325. help
  326. Specifies a (platform specific) script file to generate the FIT
  327. source file used to build the U-Boot FIT image file. This gets
  328. passed a list of supported device tree file stub names to
  329. include in the generated image.
  330. endif # SPL
  331. endif # FIT
  332. config IMAGE_FORMAT_LEGACY
  333. bool "Enable support for the legacy image format"
  334. default y if !FIT_SIGNATURE
  335. help
  336. This option enables the legacy image format. It is enabled by
  337. default for backward compatibility, unless FIT_SIGNATURE is
  338. set where it is disabled so that unsigned images cannot be
  339. loaded. If a board needs the legacy image format support in this
  340. case, enable it here.
  341. config OF_BOARD_SETUP
  342. bool "Set up board-specific details in device tree before boot"
  343. depends on OF_LIBFDT
  344. help
  345. This causes U-Boot to call ft_board_setup() before booting into
  346. the Operating System. This function can set up various
  347. board-specific information in the device tree for use by the OS.
  348. The device tree is then passed to the OS.
  349. config OF_SYSTEM_SETUP
  350. bool "Set up system-specific details in device tree before boot"
  351. depends on OF_LIBFDT
  352. help
  353. This causes U-Boot to call ft_system_setup() before booting into
  354. the Operating System. This function can set up various
  355. system-specific information in the device tree for use by the OS.
  356. The device tree is then passed to the OS.
  357. config OF_STDOUT_VIA_ALIAS
  358. bool "Update the device-tree stdout alias from U-Boot"
  359. depends on OF_LIBFDT
  360. help
  361. This uses U-Boot's serial alias from the aliases node to update
  362. the device tree passed to the OS. The "linux,stdout-path" property
  363. in the chosen node is set to point to the correct serial node.
  364. This option currently references CONFIG_CONS_INDEX, which is
  365. incorrect when used with device tree as this option does not
  366. exist / should not be used.
  367. config SYS_EXTRA_OPTIONS
  368. string "Extra Options (DEPRECATED)"
  369. help
  370. The old configuration infrastructure (= mkconfig + boards.cfg)
  371. provided the extra options field. If you have something like
  372. "HAS_BAR,BAZ=64", the optional options
  373. #define CONFIG_HAS
  374. #define CONFIG_BAZ 64
  375. will be defined in include/config.h.
  376. This option was prepared for the smooth migration from the old
  377. configuration to Kconfig. Since this option will be removed sometime,
  378. new boards should not use this option.
  379. config SYS_TEXT_BASE
  380. depends on !NIOS2 && !XTENSA
  381. depends on !EFI_APP
  382. default 0x80800000 if ARCH_OMAP2PLUS
  383. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  384. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  385. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  386. hex "Text Base"
  387. help
  388. The address in memory that U-Boot will be running from, initially.
  389. config SYS_CLK_FREQ
  390. depends on ARC || ARCH_SUNXI
  391. int "CPU clock frequency"
  392. help
  393. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  394. config ARCH_FIXUP_FDT_MEMORY
  395. bool "Enable arch_fixup_memory_banks() call"
  396. default y
  397. help
  398. Enable FDT memory map syncup before OS boot. This feature can be
  399. used for booting OS with different memory setup where the part of
  400. the memory location should be used for different purpose.
  401. endmenu # Boot images
  402. source "api/Kconfig"
  403. source "common/Kconfig"
  404. source "cmd/Kconfig"
  405. source "disk/Kconfig"
  406. source "dts/Kconfig"
  407. source "env/Kconfig"
  408. source "net/Kconfig"
  409. source "drivers/Kconfig"
  410. source "fs/Kconfig"
  411. source "lib/Kconfig"
  412. source "test/Kconfig"