Kconfig 9.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455
  1. menu "Command line interface"
  2. config HUSH_PARSER
  3. bool "Use hush shell"
  4. select SYS_HUSH_PARSER
  5. help
  6. This option enables the "hush" shell (from Busybox) as command line
  7. interpreter, thus enabling powerful command line syntax like
  8. if...then...else...fi conditionals or `&&' and '||'
  9. constructs ("shell scripts").
  10. If disabled, you get the old, much simpler behaviour with a somewhat
  11. smaller memory footprint.
  12. config SYS_HUSH_PARSER
  13. bool
  14. help
  15. Backward compatibility.
  16. comment "Commands"
  17. menu "Info commands"
  18. config CMD_BDI
  19. bool "bdinfo"
  20. help
  21. Print board info
  22. config CMD_CONSOLE
  23. bool "coninfo"
  24. help
  25. Print console devices and information.
  26. config CMD_LICENSE
  27. bool "license"
  28. help
  29. Print GPL license text
  30. endmenu
  31. menu "Boot commands"
  32. config CMD_BOOTD
  33. bool "bootd"
  34. help
  35. Run the command stored in the environment "bootcmd", i.e.
  36. "bootd" does the same thing as "run bootcmd".
  37. config CMD_BOOTM
  38. bool "bootm"
  39. default y
  40. help
  41. Boot an application image from the memory.
  42. config CMD_GO
  43. bool "go"
  44. default y
  45. help
  46. Start an application at a given address.
  47. config CMD_RUN
  48. bool "run"
  49. help
  50. Run the command in the given environment variable.
  51. config CMD_IMI
  52. bool "iminfo"
  53. help
  54. Print header information for application image.
  55. config CMD_IMLS
  56. bool "imls"
  57. help
  58. List all images found in flash
  59. config CMD_XIMG
  60. bool "imxtract"
  61. help
  62. Extract a part of a multi-image.
  63. endmenu
  64. menu "Environment commands"
  65. config CMD_EXPORTENV
  66. bool "env export"
  67. default y
  68. help
  69. Export environments.
  70. config CMD_IMPORTENV
  71. bool "env import"
  72. default y
  73. help
  74. Import environments.
  75. config CMD_EDITENV
  76. bool "editenv"
  77. help
  78. Edit environment variable.
  79. config CMD_SAVEENV
  80. bool "saveenv"
  81. help
  82. Run the command in the given environment variable.
  83. endmenu
  84. menu "Memory commands"
  85. config CMD_MEMORY
  86. bool "md, mm, nm, mw, cp, cmp, base, loop"
  87. help
  88. Memeory commands.
  89. md - memory display
  90. mm - memory modify (auto-incrementing address)
  91. nm - memory modify (constant address)
  92. mw - memory write (fill)
  93. cp - memory copy
  94. cmp - memory compare
  95. base - print or set address offset
  96. loop - initinite loop on address range
  97. config CMD_CRC32
  98. bool "crc32"
  99. default y
  100. help
  101. Compute CRC32.
  102. config LOOPW
  103. bool "loopw"
  104. help
  105. Infinite write loop on address range
  106. config CMD_MEMTEST
  107. bool "memtest"
  108. help
  109. Simple RAM read/write test.
  110. config CMD_MX_CYCLIC
  111. bool "mdc, mwc"
  112. help
  113. mdc - memory display cyclic
  114. mwc - memory write cyclic
  115. config CMD_MEMINFO
  116. bool "meminfo"
  117. help
  118. Display memory information.
  119. endmenu
  120. menu "Device access commands"
  121. config CMD_DM
  122. bool "dm - Access to driver model information"
  123. depends on DM
  124. default y
  125. help
  126. Provides access to driver model data structures and information,
  127. such as a list of devices, list of uclasses and the state of each
  128. device (e.g. activated). This is not required for operation, but
  129. can be useful to see the state of driver model for debugging or
  130. interest.
  131. config CMD_DEMO
  132. bool "demo - Demonstration commands for driver model"
  133. depends on DM
  134. help
  135. Provides a 'demo' command which can be used to play around with
  136. driver model. To use this properly you will need to enable one or
  137. both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
  138. Otherwise you will always get an empty list of devices. The demo
  139. devices are defined in the sandbox device tree, so the easiest
  140. option is to use sandbox and pass the -d point to sandbox's
  141. u-boot.dtb file.
  142. config CMD_LOADB
  143. bool "loadb"
  144. help
  145. Load a binary file over serial line.
  146. config CMD_LOADS
  147. bool "loads"
  148. help
  149. Load an S-Record file over serial line
  150. config CMD_FLASH
  151. bool "flinfo, erase, protect"
  152. help
  153. NOR flash support.
  154. flinfo - print FLASH memory information
  155. erase - FLASH memory
  156. protect - enable or disable FLASH write protection
  157. config CMD_ARMFLASH
  158. depends on FLASH_CFI_DRIVER
  159. bool "armflash"
  160. help
  161. ARM Ltd reference designs flash partition access
  162. config CMD_NAND
  163. bool "nand"
  164. help
  165. NAND support.
  166. config CMD_SPI
  167. bool "sspi"
  168. help
  169. SPI utility command.
  170. config CMD_I2C
  171. bool "i2c"
  172. help
  173. I2C support.
  174. config CMD_USB
  175. bool "usb"
  176. help
  177. USB support.
  178. config CMD_FPGA
  179. bool "fpga"
  180. help
  181. FPGA support.
  182. endmenu
  183. menu "Shell scripting commands"
  184. config CMD_ECHO
  185. bool "echo"
  186. help
  187. Echo args to console
  188. config CMD_ITEST
  189. bool "itest"
  190. help
  191. Return true/false on integer compare.
  192. config CMD_SOURCE
  193. bool "source"
  194. help
  195. Run script from memory
  196. endmenu
  197. menu "Network commands"
  198. config CMD_NET
  199. bool "bootp, tftpboot"
  200. help
  201. Network commands.
  202. bootp - boot image via network using BOOTP/TFTP protocol
  203. tftpboot - boot image via network using TFTP protocol
  204. config CMD_TFTPPUT
  205. bool "tftp put"
  206. help
  207. TFTP put command, for uploading files to a server
  208. config CMD_TFTPSRV
  209. bool "tftpsrv"
  210. help
  211. Act as a TFTP server and boot the first received file
  212. config CMD_RARP
  213. bool "rarpboot"
  214. help
  215. Boot image via network using RARP/TFTP protocol
  216. config CMD_DHCP
  217. bool "dhcp"
  218. help
  219. Boot image via network using DHCP/TFTP protocol
  220. config CMD_NFS
  221. bool "nfs"
  222. help
  223. Boot image via network using NFS protocol.
  224. config CMD_PING
  225. bool "ping"
  226. help
  227. Send ICMP ECHO_REQUEST to network host
  228. config CMD_CDP
  229. bool "cdp"
  230. help
  231. Perform CDP network configuration
  232. config CMD_SNTP
  233. bool "sntp"
  234. help
  235. Synchronize RTC via network
  236. config CMD_DNS
  237. bool "dns"
  238. help
  239. Lookup the IP of a hostname
  240. config CMD_LINK_LOCAL
  241. bool "linklocal"
  242. help
  243. Acquire a network IP address using the link-local protocol
  244. endmenu
  245. menu "Misc commands"
  246. config CMD_TIME
  247. bool "time"
  248. help
  249. Run commands and summarize execution time.
  250. # TODO: rename to CMD_SLEEP
  251. config CMD_MISC
  252. bool "sleep"
  253. help
  254. Delay execution for some time
  255. config CMD_TIMER
  256. bool "timer"
  257. help
  258. Access the system timer.
  259. config CMD_SETGETDCR
  260. bool "getdcr, setdcr, getidcr, setidcr"
  261. depends on 4xx
  262. help
  263. getdcr - Get an AMCC PPC 4xx DCR's value
  264. setdcr - Set an AMCC PPC 4xx DCR's value
  265. getidcr - Get a register value via indirect DCR addressing
  266. setidcr - Set a register value via indirect DCR addressing
  267. config CMD_SOUND
  268. bool "sound"
  269. depends on SOUND
  270. help
  271. This provides basic access to the U-Boot's sound support. The main
  272. feature is to play a beep.
  273. sound init - set up sound system
  274. sound play - play a sound
  275. endmenu
  276. menu "Boot timing"
  277. config BOOTSTAGE
  278. bool "Boot timing and reporting"
  279. help
  280. Enable recording of boot time while booting. To use it, insert
  281. calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
  282. bootstage.h. Only a single entry is recorded for each ID. You can
  283. give the entry a name with bootstage_mark_name(). You can also
  284. record elapsed time in a particular stage using bootstage_start()
  285. before starting and bootstage_accum() when finished. Bootstage will
  286. add up all the accumated time and report it.
  287. Normally, IDs are defined in bootstage.h but a small number of
  288. additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
  289. as the ID.
  290. Calls to show_boot_progress() wil also result in log entries but
  291. these will not have names.
  292. config BOOTSTAGE_REPORT
  293. bool "Display a detailed boot timing report before booting the OS"
  294. depends on BOOTSTAGE
  295. help
  296. Enable output of a boot time report just before the OS is booted.
  297. This shows how long it took U-Boot to go through each stage of the
  298. boot process. The report looks something like this:
  299. Timer summary in microseconds:
  300. Mark Elapsed Stage
  301. 0 0 reset
  302. 3,575,678 3,575,678 board_init_f start
  303. 3,575,695 17 arch_cpu_init A9
  304. 3,575,777 82 arch_cpu_init done
  305. 3,659,598 83,821 board_init_r start
  306. 3,910,375 250,777 main_loop
  307. 29,916,167 26,005,792 bootm_start
  308. 30,361,327 445,160 start_kernel
  309. config BOOTSTAGE_USER_COUNT
  310. hex "Number of boot ID numbers available for user use"
  311. default 20
  312. help
  313. This is the number of available user bootstage records.
  314. Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
  315. a new ID will be allocated from this stash. If you exceed
  316. the limit, recording will stop.
  317. config CMD_BOOTSTAGE
  318. bool "Enable the 'bootstage' command"
  319. depends on BOOTSTAGE
  320. help
  321. Add a 'bootstage' command which supports printing a report
  322. and un/stashing of bootstage data.
  323. config BOOTSTAGE_FDT
  324. bool "Store boot timing information in the OS device tree"
  325. depends on BOOTSTAGE
  326. help
  327. Stash the bootstage information in the FDT. A root 'bootstage'
  328. node is created with each bootstage id as a child. Each child
  329. has a 'name' property and either 'mark' containing the
  330. mark time in microsecond, or 'accum' containing the
  331. accumulated time for that bootstage id in microseconds.
  332. For example:
  333. bootstage {
  334. 154 {
  335. name = "board_init_f";
  336. mark = <3575678>;
  337. };
  338. 170 {
  339. name = "lcd";
  340. accum = <33482>;
  341. };
  342. };
  343. Code in the Linux kernel can find this in /proc/devicetree.
  344. config BOOTSTAGE_STASH
  345. bool "Stash the boot timing information in memory before booting OS"
  346. depends on BOOTSTAGE
  347. help
  348. Some OSes do not support device tree. Bootstage can instead write
  349. the boot timing information in a binary format at a given address.
  350. This happens through a call to bootstage_stash(), typically in
  351. the CPU's cleanup_before_linux() function. You can use the
  352. 'bootstage stash' and 'bootstage unstash' commands to do this on
  353. the command line.
  354. config BOOTSTAGE_STASH_ADDR
  355. hex "Address to stash boot timing information"
  356. default 0
  357. help
  358. Provide an address which will not be overwritten by the OS when it
  359. starts, so that it can read this information when ready.
  360. config BOOTSTAGE_STASH_SIZE
  361. hex "Size of boot timing stash region"
  362. default 4096
  363. help
  364. This should be large enough to hold the bootstage stash. A value of
  365. 4096 (4KiB) is normally plenty.
  366. endmenu
  367. endmenu