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.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
 
 
 
 
 
 

372 lines
13 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 LOCALVERSION
  14. string "Local version - append to U-Boot release"
  15. help
  16. Append an extra string to the end of your U-Boot version.
  17. This will show up in your boot log, for example.
  18. The string you set here will be appended after the contents of
  19. any files with a filename matching localversion* in your
  20. object and source tree, in that order. Your total string can
  21. be a maximum of 64 characters.
  22. config LOCALVERSION_AUTO
  23. bool "Automatically append version information to the version string"
  24. default y
  25. help
  26. This will try to automatically determine if the current tree is a
  27. release tree by looking for Git tags that belong to the current
  28. top of tree revision.
  29. A string of the format -gxxxxxxxx will be added to the localversion
  30. if a Git-based tree is found. The string generated by this will be
  31. appended after any matching localversion* files, and after the value
  32. set in CONFIG_LOCALVERSION.
  33. (The actual string used here is the first eight characters produced
  34. by running the command:
  35. $ git rev-parse --verify HEAD
  36. which is done within the script "scripts/setlocalversion".)
  37. config CC_OPTIMIZE_FOR_SIZE
  38. bool "Optimize for size"
  39. default y
  40. help
  41. Enabling this option will pass "-Os" instead of "-O2" to gcc
  42. resulting in a smaller U-Boot image.
  43. This option is enabled by default for U-Boot.
  44. config DISTRO_DEFAULTS
  45. bool "Select defaults suitable for booting general purpose Linux distributions"
  46. default y if ARCH_SUNXI || TEGRA
  47. default y if ARCH_LS2080A
  48. default y if ARCH_MESON
  49. default y if ARCH_ROCKCHIP
  50. default n
  51. select CMD_BOOTZ if ARM && !ARM64
  52. select CMD_BOOTI if ARM64
  53. select CMD_DHCP
  54. select CMD_PXE
  55. select CMD_EXT2
  56. select CMD_EXT4
  57. select CMD_FAT
  58. select CMD_FS_GENERIC
  59. select CMD_MII
  60. select CMD_PING
  61. select CMD_PART
  62. select HUSH_PARSER
  63. help
  64. Select this to enable various options and commands which are suitable
  65. for building u-boot for booting general purpose Linux distributions.
  66. config SYS_MALLOC_F
  67. bool "Enable malloc() pool before relocation"
  68. default y if DM
  69. help
  70. Before relocation, memory is very limited on many platforms. Still,
  71. we can provide a small malloc() pool if needed. Driver model in
  72. particular needs this to operate, so that it can allocate the
  73. initial serial device and any others that are needed.
  74. config SYS_MALLOC_F_LEN
  75. hex "Size of malloc() pool before relocation"
  76. depends on SYS_MALLOC_F
  77. default 0x400
  78. help
  79. Before relocation, memory is very limited on many platforms. Still,
  80. we can provide a small malloc() pool if needed. Driver model in
  81. particular needs this to operate, so that it can allocate the
  82. initial serial device and any others that are needed.
  83. menuconfig EXPERT
  84. bool "Configure standard U-Boot features (expert users)"
  85. default y
  86. help
  87. This option allows certain base U-Boot options and settings
  88. to be disabled or tweaked. This is for specialized
  89. environments which can tolerate a "non-standard" U-Boot.
  90. Use this only if you really know what you are doing.
  91. if EXPERT
  92. config SYS_MALLOC_CLEAR_ON_INIT
  93. bool "Init with zeros the memory reserved for malloc (slow)"
  94. default y
  95. help
  96. This setting is enabled by default. The reserved malloc
  97. memory is initialized with zeros, so first malloc calls
  98. will return the pointer to the zeroed memory. But this
  99. slows the boot time.
  100. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  101. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  102. Then the boot time can be significantly reduced.
  103. Warning:
  104. When disabling this, please check if malloc calls, maybe
  105. should be replaced by calloc - if one expects zeroed memory.
  106. config TOOLS_DEBUG
  107. bool "Enable debug information for tools"
  108. help
  109. Enable generation of debug information for tools such as mkimage.
  110. This can be used for debugging purposes. With debug information
  111. it is possible to set breakpoints on particular lines, single-step
  112. debug through the source code, etc.
  113. endif # EXPERT
  114. config PHYS_64BIT
  115. bool "64bit physical address support"
  116. help
  117. Say Y here to support 64bit physical memory address.
  118. This can be used not only for 64bit SoCs, but also for
  119. large physical address extention on 32bit SoCs.
  120. endmenu # General setup
  121. menu "Boot images"
  122. config FIT
  123. bool "Support Flattened Image Tree"
  124. select MD5
  125. select SHA1
  126. help
  127. This option allows you to boot the new uImage structure,
  128. Flattened Image Tree. FIT is formally a FDT, which can include
  129. images of various types (kernel, FDT blob, ramdisk, etc.)
  130. in a single blob. To boot this new uImage structure,
  131. pass the address of the blob to the "bootm" command.
  132. FIT is very flexible, supporting compression, multiple images,
  133. multiple configurations, verification through hashing and also
  134. verified boot (secure boot using RSA).
  135. if FIT
  136. config FIT_ENABLE_SHA256_SUPPORT
  137. bool "Support SHA256 checksum of FIT image contents"
  138. select SHA256
  139. default y
  140. help
  141. Enable this to support SHA256 checksum of FIT image contents. A
  142. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  143. the image contents have not been corrupted. SHA256 is recommended
  144. for use in secure applications since (as at 2016) there is no known
  145. feasible attack that could produce a 'collision' with differing
  146. input data. Use this for the highest security. Note that only the
  147. SHA256 variant is supported: SHA512 and others are not currently
  148. supported in U-Boot.
  149. config FIT_SIGNATURE
  150. bool "Enable signature verification of FIT uImages"
  151. depends on DM
  152. select RSA
  153. help
  154. This option enables signature verification of FIT uImages,
  155. using a hash signed and verified using RSA. If
  156. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  157. hashing is available using hardware, then the RSA library will use
  158. it. See doc/uImage.FIT/signature.txt for more details.
  159. WARNING: When relying on signed FIT images with a required signature
  160. check the legacy image format is disabled by default, so that
  161. unsigned images cannot be loaded. If a board needs the legacy image
  162. format support in this case, enable it using
  163. CONFIG_IMAGE_FORMAT_LEGACY.
  164. config FIT_VERBOSE
  165. bool "Show verbose messages when FIT images fail"
  166. help
  167. Generally a system will have valid FIT images so debug messages
  168. are a waste of code space. If you are debugging your images then
  169. you can enable this option to get more verbose information about
  170. failures.
  171. config FIT_BEST_MATCH
  172. bool "Select the best match for the kernel device tree"
  173. help
  174. When no configuration is explicitly selected, default to the
  175. one whose fdt's compatibility field best matches that of
  176. U-Boot itself. A match is considered "best" if it matches the
  177. most specific compatibility entry of U-Boot's fdt's root node.
  178. The order of entries in the configuration's fdt is ignored.
  179. config FIT_IMAGE_POST_PROCESS
  180. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  181. depends on TI_SECURE_DEVICE
  182. help
  183. Allows doing any sort of manipulation to blobs after they got extracted
  184. from FIT images like stripping off headers or modifying the size of the
  185. blob, verification, authentication, decryption etc. in a platform or
  186. board specific way. In order to use this feature a platform or board-
  187. specific implementation of board_fit_image_post_process() must be
  188. provided. Also, anything done during this post-processing step would
  189. need to be comprehended in how the images were prepared before being
  190. injected into the FIT creation (i.e. the blobs would have been pre-
  191. processed before being added to the FIT image).
  192. if SPL
  193. config SPL_FIT
  194. bool "Support Flattened Image Tree within SPL"
  195. depends on SPL
  196. select SPL_OF_LIBFDT
  197. config SPL_FIT_SIGNATURE
  198. bool "Enable signature verification of FIT firmware within SPL"
  199. depends on SPL_DM
  200. select SPL_FIT
  201. select SPL_RSA
  202. config SPL_LOAD_FIT
  203. bool "Enable SPL loading U-Boot as a FIT"
  204. select SPL_FIT
  205. help
  206. Normally with the SPL framework a legacy image is generated as part
  207. of the build. This contains U-Boot along with information as to
  208. where it should be loaded. This option instead enables generation
  209. of a FIT (Flat Image Tree) which provides more flexibility. In
  210. particular it can handle selecting from multiple device tree
  211. and passing the correct one to U-Boot.
  212. config SPL_FIT_IMAGE_POST_PROCESS
  213. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  214. depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
  215. help
  216. Allows doing any sort of manipulation to blobs after they got extracted
  217. from the U-Boot FIT image like stripping off headers or modifying the
  218. size of the blob, verification, authentication, decryption etc. in a
  219. platform or board specific way. In order to use this feature a platform
  220. or board-specific implementation of board_fit_image_post_process() must
  221. be provided. Also, anything done during this post-processing step would
  222. need to be comprehended in how the images were prepared before being
  223. injected into the FIT creation (i.e. the blobs would have been pre-
  224. processed before being added to the FIT image).
  225. config SPL_FIT_SOURCE
  226. string ".its source file for U-Boot FIT image"
  227. depends on SPL_FIT
  228. help
  229. Specifies a (platform specific) FIT source file to generate the
  230. U-Boot FIT image. This could specify further image to load and/or
  231. execute.
  232. config SPL_FIT_GENERATOR
  233. string ".its file generator script for U-Boot FIT image"
  234. depends on SPL_FIT
  235. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  236. help
  237. Specifies a (platform specific) script file to generate the FIT
  238. source file used to build the U-Boot FIT image file. This gets
  239. passed a list of supported device tree file stub names to
  240. include in the generated image.
  241. endif # SPL
  242. endif # FIT
  243. config OF_BOARD_SETUP
  244. bool "Set up board-specific details in device tree before boot"
  245. depends on OF_LIBFDT
  246. help
  247. This causes U-Boot to call ft_board_setup() before booting into
  248. the Operating System. This function can set up various
  249. board-specific information in the device tree for use by the OS.
  250. The device tree is then passed to the OS.
  251. config OF_SYSTEM_SETUP
  252. bool "Set up system-specific details in device tree before boot"
  253. depends on OF_LIBFDT
  254. help
  255. This causes U-Boot to call ft_system_setup() before booting into
  256. the Operating System. This function can set up various
  257. system-specific information in the device tree for use by the OS.
  258. The device tree is then passed to the OS.
  259. config OF_STDOUT_VIA_ALIAS
  260. bool "Update the device-tree stdout alias from U-Boot"
  261. depends on OF_LIBFDT
  262. help
  263. This uses U-Boot's serial alias from the aliases node to update
  264. the device tree passed to the OS. The "linux,stdout-path" property
  265. in the chosen node is set to point to the correct serial node.
  266. This option currently references CONFIG_CONS_INDEX, which is
  267. incorrect when used with device tree as this option does not
  268. exist / should not be used.
  269. config SYS_EXTRA_OPTIONS
  270. string "Extra Options (DEPRECATED)"
  271. help
  272. The old configuration infrastructure (= mkconfig + boards.cfg)
  273. provided the extra options field. If you have something like
  274. "HAS_BAR,BAZ=64", the optional options
  275. #define CONFIG_HAS
  276. #define CONFIG_BAZ 64
  277. will be defined in include/config.h.
  278. This option was prepared for the smooth migration from the old
  279. configuration to Kconfig. Since this option will be removed sometime,
  280. new boards should not use this option.
  281. config SYS_TEXT_BASE
  282. depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
  283. (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
  284. ARCH_ZYNQ || ARCH_KEYSTONE
  285. depends on !EFI_APP
  286. hex "Text Base"
  287. help
  288. TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
  289. config SYS_CLK_FREQ
  290. depends on ARC || ARCH_SUNXI
  291. int "CPU clock frequency"
  292. help
  293. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  294. config ARCH_FIXUP_FDT_MEMORY
  295. bool "Enable arch_fixup_memory_banks() call"
  296. default y
  297. help
  298. Enable FDT memory map syncup before OS boot. This feature can be
  299. used for booting OS with different memory setup where the part of
  300. the memory location should be used for different purpose.
  301. endmenu # Boot images
  302. source "api/Kconfig"
  303. source "common/Kconfig"
  304. source "cmd/Kconfig"
  305. source "disk/Kconfig"
  306. source "dts/Kconfig"
  307. source "net/Kconfig"
  308. source "drivers/Kconfig"
  309. source "fs/Kconfig"
  310. source "lib/Kconfig"
  311. source "test/Kconfig"
  312. source "scripts/Kconfig"