Kconfig 32 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219
  1. menu "Command line interface"
  2. config CMDLINE
  3. bool "Support U-Boot commands"
  4. default y
  5. help
  6. Enable U-Boot's command-line functions. This provides a means
  7. to enter commands into U-Boot for a wide variety of purposes. It
  8. also allows scripts (containing commands) to be executed.
  9. Various commands and command categorys can be indivdually enabled.
  10. Depending on the number of commands enabled, this can add
  11. substantially to the size of U-Boot.
  12. config HUSH_PARSER
  13. bool "Use hush shell"
  14. depends on CMDLINE
  15. help
  16. This option enables the "hush" shell (from Busybox) as command line
  17. interpreter, thus enabling powerful command line syntax like
  18. if...then...else...fi conditionals or `&&' and '||'
  19. constructs ("shell scripts").
  20. If disabled, you get the old, much simpler behaviour with a somewhat
  21. smaller memory footprint.
  22. config SYS_PROMPT
  23. string "Shell prompt"
  24. default "=> "
  25. help
  26. This string is displayed in the command line to the left of the
  27. cursor.
  28. menu "Autoboot options"
  29. config AUTOBOOT
  30. bool "Autoboot"
  31. default y
  32. help
  33. This enables the autoboot. See doc/README.autoboot for detail.
  34. config AUTOBOOT_KEYED
  35. bool "Stop autobooting via specific input key / string"
  36. default n
  37. help
  38. This option enables stopping (aborting) of the automatic
  39. boot feature only by issuing a specific input key or
  40. string. If not enabled, any input key will abort the
  41. U-Boot automatic booting process and bring the device
  42. to the U-Boot prompt for user input.
  43. config AUTOBOOT_PROMPT
  44. string "Autoboot stop prompt"
  45. depends on AUTOBOOT_KEYED
  46. default "Autoboot in %d seconds\\n"
  47. help
  48. This string is displayed before the boot delay selected by
  49. CONFIG_BOOTDELAY starts. If it is not defined there is no
  50. output indicating that autoboot is in progress.
  51. Note that this define is used as the (only) argument to a
  52. printf() call, so it may contain '%' format specifications,
  53. provided that it also includes, sepearated by commas exactly
  54. like in a printf statement, the required arguments. It is
  55. the responsibility of the user to select only such arguments
  56. that are valid in the given context.
  57. config AUTOBOOT_ENCRYPTION
  58. bool "Enable encryption in autoboot stopping"
  59. depends on AUTOBOOT_KEYED
  60. default n
  61. config AUTOBOOT_DELAY_STR
  62. string "Delay autobooting via specific input key / string"
  63. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  64. help
  65. This option delays the automatic boot feature by issuing
  66. a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
  67. or the environment variable "bootdelaykey" is specified
  68. and this string is received from console input before
  69. autoboot starts booting, U-Boot gives a command prompt. The
  70. U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
  71. used, otherwise it never times out.
  72. config AUTOBOOT_STOP_STR
  73. string "Stop autobooting via specific input key / string"
  74. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  75. help
  76. This option enables stopping (aborting) of the automatic
  77. boot feature only by issuing a specific input key or
  78. string. If CONFIG_AUTOBOOT_STOP_STR or the environment
  79. variable "bootstopkey" is specified and this string is
  80. received from console input before autoboot starts booting,
  81. U-Boot gives a command prompt. The U-Boot prompt never
  82. times out, even if CONFIG_BOOT_RETRY_TIME is used.
  83. config AUTOBOOT_KEYED_CTRLC
  84. bool "Enable Ctrl-C autoboot interruption"
  85. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  86. default n
  87. help
  88. This option allows for the boot sequence to be interrupted
  89. by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
  90. Setting this variable provides an escape sequence from the
  91. limited "password" strings.
  92. config AUTOBOOT_STOP_STR_SHA256
  93. string "Stop autobooting via SHA256 encrypted password"
  94. depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
  95. help
  96. This option adds the feature to only stop the autobooting,
  97. and therefore boot into the U-Boot prompt, when the input
  98. string / password matches a values that is encypted via
  99. a SHA256 hash and saved in the environment.
  100. endmenu
  101. source "cmd/fastboot/Kconfig"
  102. comment "Commands"
  103. menu "Info commands"
  104. config CMD_BDI
  105. bool "bdinfo"
  106. default y
  107. help
  108. Print board info
  109. config CMD_CONFIG
  110. bool "config"
  111. select BUILD_BIN2C
  112. default SANDBOX
  113. help
  114. Print ".config" contents.
  115. If this option is enabled, the ".config" file contents are embedded
  116. in the U-Boot image and can be printed on the console by the "config"
  117. command. This provides information of which options are enabled on
  118. the running U-Boot.
  119. config CMD_CONSOLE
  120. bool "coninfo"
  121. default y
  122. help
  123. Print console devices and information.
  124. config CMD_CPU
  125. bool "cpu"
  126. help
  127. Print information about available CPUs. This normally shows the
  128. number of CPUs, type (e.g. manufacturer, architecture, product or
  129. internal name) and clock frequency. Other information may be
  130. available depending on the CPU driver.
  131. config CMD_LICENSE
  132. bool "license"
  133. select BUILD_BIN2C
  134. help
  135. Print GPL license text
  136. endmenu
  137. menu "Boot commands"
  138. config CMD_BOOTD
  139. bool "bootd"
  140. default y
  141. help
  142. Run the command stored in the environment "bootcmd", i.e.
  143. "bootd" does the same thing as "run bootcmd".
  144. config CMD_BOOTM
  145. bool "bootm"
  146. default y
  147. help
  148. Boot an application image from the memory.
  149. config CMD_BOOTZ
  150. bool "bootz"
  151. help
  152. Boot the Linux zImage
  153. config CMD_BOOTI
  154. bool "booti"
  155. depends on ARM64
  156. default y
  157. help
  158. Boot an AArch64 Linux Kernel image from memory.
  159. config CMD_BOOTEFI
  160. bool "bootefi"
  161. depends on EFI_LOADER
  162. default y
  163. help
  164. Boot an EFI image from memory.
  165. config CMD_BOOTEFI_HELLO_COMPILE
  166. bool "Compile a standard EFI hello world binary for testing"
  167. depends on CMD_BOOTEFI && (ARM || X86)
  168. default y
  169. help
  170. This compiles a standard EFI hello world application with U-Boot so
  171. that it can be used with the test/py testing framework. This is useful
  172. for testing that EFI is working at a basic level, and for bringing
  173. up EFI support on a new architecture.
  174. No additional space will be required in the resulting U-Boot binary
  175. when this option is enabled.
  176. config CMD_BOOTEFI_HELLO
  177. bool "Allow booting a standard EFI hello world for testing"
  178. depends on CMD_BOOTEFI_HELLO_COMPILE
  179. help
  180. This adds a standard EFI hello world application to U-Boot so that
  181. it can be used with the 'bootefi hello' command. This is useful
  182. for testing that EFI is working at a basic level, and for bringing
  183. up EFI support on a new architecture.
  184. config CMD_BOOTMENU
  185. bool "bootmenu"
  186. select MENU
  187. help
  188. Add an ANSI terminal boot menu command.
  189. config CMD_ELF
  190. bool "bootelf, bootvx"
  191. default y
  192. help
  193. Boot an ELF/vxWorks image from the memory.
  194. config CMD_FDT
  195. bool "Flattened Device Tree utility commands"
  196. default y
  197. depends on OF_LIBFDT
  198. help
  199. Do FDT related setup before booting into the Operating System.
  200. config CMD_GO
  201. bool "go"
  202. default y
  203. help
  204. Start an application at a given address.
  205. config CMD_RUN
  206. bool "run"
  207. default y
  208. help
  209. Run the command in the given environment variable.
  210. config CMD_IMI
  211. bool "iminfo"
  212. default y
  213. help
  214. Print header information for application image.
  215. config CMD_IMLS
  216. bool "imls"
  217. default y
  218. help
  219. List all images found in flash
  220. config CMD_XIMG
  221. bool "imxtract"
  222. default y
  223. help
  224. Extract a part of a multi-image.
  225. config CMD_POWEROFF
  226. bool
  227. endmenu
  228. menu "Environment commands"
  229. config CMD_ASKENV
  230. bool "ask for env variable"
  231. help
  232. Ask for environment variable
  233. config CMD_EXPORTENV
  234. bool "env export"
  235. default y
  236. help
  237. Export environments.
  238. config CMD_IMPORTENV
  239. bool "env import"
  240. default y
  241. help
  242. Import environments.
  243. config CMD_EDITENV
  244. bool "editenv"
  245. default y
  246. help
  247. Edit environment variable.
  248. config CMD_GREPENV
  249. bool "search env"
  250. help
  251. Allow for searching environment variables
  252. config CMD_SAVEENV
  253. bool "saveenv"
  254. default y
  255. help
  256. Save all environment variables into the compiled-in persistent
  257. storage.
  258. config CMD_ENV_EXISTS
  259. bool "env exists"
  260. default y
  261. help
  262. Check if a variable is defined in the environment for use in
  263. shell scripting.
  264. config CMD_ENV_CALLBACK
  265. bool "env callbacks - print callbacks and their associated variables"
  266. help
  267. Some environment variable have callbacks defined by
  268. U_BOOT_ENV_CALLBACK. These are called when the variable changes.
  269. For example changing "baudrate" adjust the serial baud rate. This
  270. command lists the currently defined callbacks.
  271. config CMD_ENV_FLAGS
  272. bool "env flags -print variables that have non-default flags"
  273. help
  274. Some environment variables have special flags that control their
  275. behaviour. For example, serial# can only be written once and cannot
  276. be deleted. This command shows the variables that have special
  277. flags.
  278. endmenu
  279. menu "Memory commands"
  280. config CMD_MEMORY
  281. bool "md, mm, nm, mw, cp, cmp, base, loop"
  282. default y
  283. help
  284. Memory commands.
  285. md - memory display
  286. mm - memory modify (auto-incrementing address)
  287. nm - memory modify (constant address)
  288. mw - memory write (fill)
  289. cp - memory copy
  290. cmp - memory compare
  291. base - print or set address offset
  292. loop - initialize loop on address range
  293. config CMD_CRC32
  294. bool "crc32"
  295. select HASH
  296. default y
  297. help
  298. Compute CRC32.
  299. config CMD_EEPROM
  300. bool "eeprom - EEPROM subsystem"
  301. help
  302. (deprecated, needs conversion to driver model)
  303. Provides commands to read and write EEPROM (Electrically Erasable
  304. Programmable Read Only Memory) chips that are connected over an
  305. I2C bus.
  306. config CMD_EEPROM_LAYOUT
  307. bool "Enable layout-aware eeprom commands"
  308. depends on CMD_EEPROM
  309. help
  310. (deprecated, needs conversion to driver model)
  311. When enabled, additional eeprom sub-commands become available.
  312. eeprom print - prints the contents of the eeprom in a human-readable
  313. way (eeprom layout fields, and data formatted to be fit for human
  314. consumption).
  315. eeprom update - allows user to update eeprom fields by specifying
  316. the field name, and providing the new data in a human readable format
  317. (same format as displayed by the eeprom print command).
  318. Both commands can either auto detect the layout, or be told which
  319. layout to use.
  320. Feature API:
  321. __weak int parse_layout_version(char *str)
  322. - override to provide your own layout name parsing
  323. __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
  324. int layout_version);
  325. - override to setup the layout metadata based on the version
  326. __weak int eeprom_layout_detect(unsigned char *data)
  327. - override to provide your own algorithm for detecting layout
  328. version
  329. eeprom_field.c
  330. - contains various printing and updating functions for common
  331. types of eeprom fields. Can be used for defining
  332. custom layouts.
  333. config EEPROM_LAYOUT_HELP_STRING
  334. string "Tells user what layout names are supported"
  335. depends on CMD_EEPROM_LAYOUT
  336. default "<not defined>"
  337. help
  338. Help printed with the LAYOUT VERSIONS part of the 'eeprom'
  339. command's help.
  340. config CMD_MD5SUM
  341. bool "md5sum"
  342. default n
  343. select MD5
  344. help
  345. Compute MD5 checksum.
  346. config MD5SUM_VERFIY
  347. bool "md5sum -v"
  348. default n
  349. depends on CMD_MD5SUM
  350. help
  351. Add -v option to verify data against an MD5 checksum.
  352. config LOOPW
  353. bool "loopw"
  354. help
  355. Infinite write loop on address range
  356. config CMD_MEMTEST
  357. bool "memtest"
  358. help
  359. Simple RAM read/write test.
  360. config CMD_MX_CYCLIC
  361. bool "mdc, mwc"
  362. help
  363. mdc - memory display cyclic
  364. mwc - memory write cyclic
  365. config CMD_MEMINFO
  366. bool "meminfo"
  367. help
  368. Display memory information.
  369. config CMD_UNZIP
  370. bool "unzip"
  371. help
  372. Uncompress a zip-compressed memory region.
  373. config CMD_ZIP
  374. bool "zip"
  375. help
  376. Compress a memory region with zlib deflate method.
  377. endmenu
  378. menu "Device access commands"
  379. config CMD_CLK
  380. bool "clk - Show clock frequencies"
  381. help
  382. (deprecated)
  383. Shows clock frequences by calling a sock_clk_dump() hook function.
  384. This is depreated in favour of using the CLK uclass and accessing
  385. clock values from associated drivers. However currently no command
  386. exists for this.
  387. config CMD_DM
  388. bool "dm - Access to driver model information"
  389. depends on DM
  390. default y
  391. help
  392. Provides access to driver model data structures and information,
  393. such as a list of devices, list of uclasses and the state of each
  394. device (e.g. activated). This is not required for operation, but
  395. can be useful to see the state of driver model for debugging or
  396. interest.
  397. config CMD_DEMO
  398. bool "demo - Demonstration commands for driver model"
  399. depends on DM
  400. help
  401. Provides a 'demo' command which can be used to play around with
  402. driver model. To use this properly you will need to enable one or
  403. both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
  404. Otherwise you will always get an empty list of devices. The demo
  405. devices are defined in the sandbox device tree, so the easiest
  406. option is to use sandbox and pass the -d point to sandbox's
  407. u-boot.dtb file.
  408. config CMD_IDE
  409. bool "ide - Support for IDE drivers"
  410. select IDE
  411. help
  412. Provides an 'ide' command which allows accessing the IDE drive,
  413. reseting the IDE interface, printing the partition table and
  414. geting device info. It also enables the 'diskboot' command which
  415. permits booting from an IDE drive.
  416. config CMD_IO
  417. bool "io - Support for performing I/O accesses"
  418. help
  419. Provides an 'iod' command to display I/O space and an 'iow' command
  420. to write values to the I/O space. This can be useful for manually
  421. checking the state of devices during boot when debugging device
  422. drivers, etc.
  423. config CMD_IOTRACE
  424. bool "iotrace - Support for tracing I/O activity"
  425. help
  426. Provides an 'iotrace' command which supports recording I/O reads and
  427. writes in a trace buffer in memory . It also maintains a checksum
  428. of the trace records (even if space is exhausted) so that the
  429. sequence of I/O accesses can be verified.
  430. When debugging drivers it is useful to see what I/O accesses were
  431. done and in what order.
  432. Even if the individual accesses are of little interest it can be
  433. useful to verify that the access pattern is consistent each time
  434. an operation is performed. In this case a checksum can be used to
  435. characterise the operation of a driver. The checksum can be compared
  436. across different runs of the operation to verify that the driver is
  437. working properly.
  438. In particular, when performing major refactoring of the driver, where
  439. the access pattern should not change, the checksum provides assurance
  440. that the refactoring work has not broken the driver.
  441. This works by sneaking into the io.h heder for an architecture and
  442. redirecting I/O accesses through iotrace's tracing mechanism.
  443. For now no commands are provided to examine the trace buffer. The
  444. format is fairly simple, so 'md' is a reasonable substitute.
  445. Note: The checksum feature is only useful for I/O regions where the
  446. contents do not change outside of software control. Where this is not
  447. suitable you can fall back to manually comparing the addresses. It
  448. might be useful to enhance tracing to only checksum the accesses and
  449. not the data read/written.
  450. config CMD_LOADB
  451. bool "loadb"
  452. default y
  453. help
  454. Load a binary file over serial line.
  455. config CMD_LOADS
  456. bool "loads"
  457. default y
  458. help
  459. Load an S-Record file over serial line
  460. config CMD_FLASH
  461. bool "flinfo, erase, protect"
  462. default y
  463. help
  464. NOR flash support.
  465. flinfo - print FLASH memory information
  466. erase - FLASH memory
  467. protect - enable or disable FLASH write protection
  468. config CMD_GPT
  469. bool "GPT (GUID Partition Table) command"
  470. select PARTITION_UUIDS
  471. select EFI_PARTITION
  472. help
  473. Enable the 'gpt' command to ready and write GPT style partition
  474. tables.
  475. config CMD_ARMFLASH
  476. #depends on FLASH_CFI_DRIVER
  477. bool "armflash"
  478. help
  479. ARM Ltd reference designs flash partition access
  480. config CMD_MMC
  481. bool "mmc"
  482. help
  483. MMC memory mapped support.
  484. config CMD_NAND
  485. bool "nand"
  486. default y if NAND_SUNXI
  487. help
  488. NAND support.
  489. if CMD_NAND
  490. config CMD_NAND_TRIMFFS
  491. bool "nand write.trimffs"
  492. default y if ARCH_SUNXI
  493. help
  494. Allows one to skip empty pages when flashing something on a NAND.
  495. config CMD_NAND_LOCK_UNLOCK
  496. bool "nand lock/unlock"
  497. help
  498. NAND locking support.
  499. config CMD_NAND_TORTURE
  500. bool "nand torture"
  501. help
  502. NAND torture support.
  503. endif # CMD_NAND
  504. config CMD_PART
  505. bool "part"
  506. select PARTITION_UUIDS
  507. help
  508. Read and display information about the partition table on
  509. various media.
  510. config CMD_SF
  511. bool "sf"
  512. help
  513. SPI Flash support
  514. config CMD_SPI
  515. bool "sspi"
  516. help
  517. SPI utility command.
  518. config CMD_I2C
  519. bool "i2c"
  520. help
  521. I2C support.
  522. config CMD_USB
  523. bool "usb"
  524. help
  525. USB support.
  526. config CMD_DFU
  527. bool "dfu"
  528. select USB_FUNCTION_DFU
  529. help
  530. Enables the command "dfu" which is used to have U-Boot create a DFU
  531. class device via USB.
  532. config CMD_USB_MASS_STORAGE
  533. bool "UMS usb mass storage"
  534. help
  535. USB mass storage support
  536. config CMD_FPGA
  537. bool "fpga"
  538. default y
  539. help
  540. FPGA support.
  541. config CMD_FPGA_LOADBP
  542. bool "fpga loadbp - load partial bitstream (Xilinx only)"
  543. depends on CMD_FPGA
  544. help
  545. Supports loading an FPGA device from a bitstream buffer containing
  546. a partial bitstream.
  547. config CMD_FPGA_LOADFS
  548. bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
  549. depends on CMD_FPGA
  550. help
  551. Supports loading an FPGA device from a FAT filesystem.
  552. config CMD_FPGA_LOADMK
  553. bool "fpga loadmk - load bitstream from image"
  554. depends on CMD_FPGA
  555. help
  556. Supports loading an FPGA device from a image generated by mkimage.
  557. config CMD_FPGA_LOADP
  558. bool "fpga loadp - load partial bitstream"
  559. depends on CMD_FPGA
  560. help
  561. Supports loading an FPGA device from a bitstream buffer containing
  562. a partial bitstream.
  563. config CMD_FPGAD
  564. bool "fpgad - dump FPGA registers"
  565. help
  566. (legacy, needs conversion to driver model)
  567. Provides a way to dump FPGA registers by calling the board-specific
  568. fpga_get_reg() function. This functions similarly to the 'md'
  569. command.
  570. config CMD_FUSE
  571. bool "fuse - support for the fuse subssystem"
  572. help
  573. (deprecated - needs conversion to driver model)
  574. This allows reading, sensing, programming or overriding fuses
  575. which control the behaviour of the device. The command uses the
  576. fuse_...() API.
  577. config CMD_REMOTEPROC
  578. bool "remoteproc"
  579. depends on REMOTEPROC
  580. help
  581. Support for Remote Processor control
  582. config CMD_GPIO
  583. bool "gpio"
  584. help
  585. GPIO support.
  586. config CMD_FDC
  587. bool "fdcboot - Boot from floppy device"
  588. help
  589. The 'fdtboot' command allows booting an image from a floppy disk.
  590. endmenu
  591. menu "Shell scripting commands"
  592. config CMD_ECHO
  593. bool "echo"
  594. default y
  595. help
  596. Echo args to console
  597. config CMD_ITEST
  598. bool "itest"
  599. default y
  600. help
  601. Return true/false on integer compare.
  602. config CMD_SOURCE
  603. bool "source"
  604. default y
  605. help
  606. Run script from memory
  607. config CMD_SETEXPR
  608. bool "setexpr"
  609. default y
  610. help
  611. Evaluate boolean and math expressions and store the result in an env
  612. variable.
  613. Also supports loading the value at a memory location into a variable.
  614. If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
  615. endmenu
  616. menu "Network commands"
  617. config CMD_NET
  618. bool "bootp, tftpboot"
  619. select NET
  620. default y
  621. help
  622. Network commands.
  623. bootp - boot image via network using BOOTP/TFTP protocol
  624. tftpboot - boot image via network using TFTP protocol
  625. config CMD_TFTPPUT
  626. bool "tftp put"
  627. help
  628. TFTP put command, for uploading files to a server
  629. config CMD_TFTPSRV
  630. bool "tftpsrv"
  631. help
  632. Act as a TFTP server and boot the first received file
  633. config CMD_RARP
  634. bool "rarpboot"
  635. help
  636. Boot image via network using RARP/TFTP protocol
  637. config CMD_DHCP
  638. bool "dhcp"
  639. help
  640. Boot image via network using DHCP/TFTP protocol
  641. config CMD_PXE
  642. bool "pxe"
  643. select MENU
  644. help
  645. Boot image via network using PXE protocol
  646. config CMD_NFS
  647. bool "nfs"
  648. default y
  649. help
  650. Boot image via network using NFS protocol.
  651. config CMD_MII
  652. bool "mii"
  653. help
  654. Enable MII utility commands.
  655. config CMD_PING
  656. bool "ping"
  657. help
  658. Send ICMP ECHO_REQUEST to network host
  659. config CMD_CDP
  660. bool "cdp"
  661. help
  662. Perform CDP network configuration
  663. config CMD_SNTP
  664. bool "sntp"
  665. help
  666. Synchronize RTC via network
  667. config CMD_DNS
  668. bool "dns"
  669. help
  670. Lookup the IP of a hostname
  671. config CMD_LINK_LOCAL
  672. bool "linklocal"
  673. help
  674. Acquire a network IP address using the link-local protocol
  675. config CMD_ETHSW
  676. bool "ethsw"
  677. help
  678. Allow control of L2 Ethernet switch commands. These are supported
  679. by the vsc9953 Ethernet driver at present. Sub-commands allow
  680. operations such as enabling / disabling a port and
  681. viewing/maintaining the filtering database (FDB)
  682. endmenu
  683. menu "Misc commands"
  684. config CMD_BMP
  685. bool "Enable 'bmp' command"
  686. depends on LCD || DM_VIDEO || VIDEO
  687. help
  688. This provides a way to obtain information about a BMP-format iamge
  689. and to display it. BMP (which presumably stands for BitMaP) is a
  690. file format defined by Microsoft which supports images of various
  691. depths, formats and compression methods. Headers on the file
  692. determine the formats used. This command can be used by first loading
  693. the image into RAM, then using this command to look at it or display
  694. it.
  695. config CMD_BSP
  696. bool "Enable board-specific commands"
  697. help
  698. (deprecated: instead, please define a Kconfig option for each command)
  699. Some boards have board-specific commands which are only enabled
  700. during developemnt and need to be turned off for production. This
  701. option provides a way to control this. The commands that are enabled
  702. vary depending on the board.
  703. config CMD_BKOPS_ENABLE
  704. bool "mmc bkops enable"
  705. depends on CMD_MMC
  706. default n
  707. help
  708. Enable command for setting manual background operations handshake
  709. on a eMMC device. The feature is optionally available on eMMC devices
  710. conforming to standard >= 4.41.
  711. config CMD_BLOCK_CACHE
  712. bool "blkcache - control and stats for block cache"
  713. depends on BLOCK_CACHE
  714. default y if BLOCK_CACHE
  715. help
  716. Enable the blkcache command, which can be used to control the
  717. operation of the cache functions.
  718. This is most useful when fine-tuning the operation of the cache
  719. during development, but also allows the cache to be disabled when
  720. it might hurt performance (e.g. when using the ums command).
  721. config CMD_CACHE
  722. bool "icache or dcache"
  723. help
  724. Enable the "icache" and "dcache" commands
  725. config CMD_DISPLAY
  726. bool "Enable the 'display' command, for character displays"
  727. help
  728. (this needs porting to driver model)
  729. This enables the 'display' command which allows a string to be
  730. displayed on a simple board-specific display. Implement
  731. display_putc() to use it.
  732. config CMD_LED
  733. bool "led"
  734. default y if LED
  735. help
  736. Enable the 'led' command which allows for control of LEDs supported
  737. by the board. The LEDs can be listed with 'led list' and controlled
  738. with led on/off/togle/blink. Any LED drivers can be controlled with
  739. this command, e.g. led_gpio.
  740. config CMD_DATE
  741. bool "date"
  742. default y if DM_RTC
  743. help
  744. Enable the 'date' command for getting/setting the time/date in RTC
  745. devices.
  746. config CMD_TIME
  747. bool "time"
  748. help
  749. Run commands and summarize execution time.
  750. config CMD_GETTIME
  751. bool "gettime - read elapsed time"
  752. help
  753. Enable the 'gettime' command which reads the elapsed time since
  754. U-Boot started running. This shows the time in seconds and
  755. milliseconds. See also the 'bootstage' command which provides more
  756. flexibility for boot timing.
  757. # TODO: rename to CMD_SLEEP
  758. config CMD_MISC
  759. bool "sleep"
  760. default y
  761. help
  762. Delay execution for some time
  763. config CMD_TIMER
  764. bool "timer"
  765. help
  766. Access the system timer.
  767. config CMD_SETGETDCR
  768. bool "getdcr, setdcr, getidcr, setidcr"
  769. depends on 4xx
  770. default y
  771. help
  772. getdcr - Get an AMCC PPC 4xx DCR's value
  773. setdcr - Set an AMCC PPC 4xx DCR's value
  774. getidcr - Get a register value via indirect DCR addressing
  775. setidcr - Set a register value via indirect DCR addressing
  776. config CMD_SOUND
  777. bool "sound"
  778. depends on SOUND
  779. help
  780. This provides basic access to the U-Boot's sound support. The main
  781. feature is to play a beep.
  782. sound init - set up sound system
  783. sound play - play a sound
  784. config CMD_QFW
  785. bool "qfw"
  786. select QFW
  787. help
  788. This provides access to the QEMU firmware interface. The main
  789. feature is to allow easy loading of files passed to qemu-system
  790. via -kernel / -initrd
  791. source "cmd/mvebu/Kconfig"
  792. endmenu
  793. config CMD_BOOTSTAGE
  794. bool "Enable the 'bootstage' command"
  795. depends on BOOTSTAGE
  796. help
  797. Add a 'bootstage' command which supports printing a report
  798. and un/stashing of bootstage data.
  799. menu "Power commands"
  800. config CMD_PMIC
  801. bool "Enable Driver Model PMIC command"
  802. depends on DM_PMIC
  803. help
  804. This is the pmic command, based on a driver model pmic's API.
  805. Command features are unchanged:
  806. - list - list pmic devices
  807. - pmic dev <id> - show or [set] operating pmic device (NEW)
  808. - pmic dump - dump registers
  809. - pmic read address - read byte of register at address
  810. - pmic write address - write byte to register at address
  811. The only one change for this command is 'dev' subcommand.
  812. config CMD_REGULATOR
  813. bool "Enable Driver Model REGULATOR command"
  814. depends on DM_REGULATOR
  815. help
  816. This command is based on driver model regulator's API.
  817. User interface features:
  818. - list - list regulator devices
  819. - regulator dev <id> - show or [set] operating regulator device
  820. - regulator info - print constraints info
  821. - regulator status - print operating status
  822. - regulator value <val] <-f> - print/[set] voltage value [uV]
  823. - regulator current <val> - print/[set] current value [uA]
  824. - regulator mode <id> - print/[set] operating mode id
  825. - regulator enable - enable the regulator output
  826. - regulator disable - disable the regulator output
  827. The '-f' (force) option can be used for set the value which exceeds
  828. the limits, which are found in device-tree and are kept in regulator's
  829. uclass platdata structure.
  830. endmenu
  831. menu "Security commands"
  832. config CMD_AES
  833. bool "Enable the 'aes' command"
  834. select AES
  835. help
  836. This provides a means to encrypt and decrypt data using the AES
  837. (Advanced Encryption Standard). This algorithm uses a symetric key
  838. and is widely used as a streaming cipher. Different key lengths are
  839. supported by the algorithm but this command only supports 128 bits
  840. at present.
  841. config CMD_BLOB
  842. bool "Enable the 'blob' command"
  843. help
  844. This is used with the Freescale secure boot mechanism.
  845. Freescale's SEC block has built-in Blob Protocol which provides
  846. a method for protecting user-defined data across system power
  847. cycles. SEC block protects data in a data structure called a Blob,
  848. which provides both confidentiality and integrity protection.
  849. Encapsulating data as a blob
  850. Each time that the Blob Protocol is used to protect data, a
  851. different randomly generated key is used to encrypt the data.
  852. This random key is itself encrypted using a key which is derived
  853. from SoC's non-volatile secret key and a 16 bit Key identifier.
  854. The resulting encrypted key along with encrypted data is called a
  855. blob. The non-volatile secure key is available for use only during
  856. secure boot.
  857. During decapsulation, the reverse process is performed to get back
  858. the original data.
  859. Sub-commands:
  860. blob enc - encapsulating data as a cryptgraphic blob
  861. blob dec - decapsulating cryptgraphic blob to get the data
  862. Syntax:
  863. blob enc src dst len km
  864. Encapsulate and create blob of data $len bytes long
  865. at address $src and store the result at address $dst.
  866. $km is the 16 byte key modifier is also required for
  867. generation/use as key for cryptographic operation. Key
  868. modifier should be 16 byte long.
  869. blob dec src dst len km
  870. Decapsulate the blob of data at address $src and
  871. store result of $len byte at addr $dst.
  872. $km is the 16 byte key modifier is also required for
  873. generation/use as key for cryptographic operation. Key
  874. modifier should be 16 byte long.
  875. config CMD_HASH
  876. bool "Support 'hash' command"
  877. select HASH
  878. help
  879. This provides a way to hash data in memory using various supported
  880. algorithms (such as SHA1, MD5, CRC32). The computed digest can be
  881. saved to memory or to an environment variable. It is also possible
  882. to verify a hash against data in memory.
  883. config CMD_TPM
  884. bool "Enable the 'tpm' command"
  885. depends on TPM
  886. help
  887. This provides a means to talk to a TPM from the command line. A wide
  888. range of commands if provided - see 'tpm help' for details. The
  889. command requires a suitable TPM on your board and the correct driver
  890. must be enabled.
  891. config CMD_TPM_TEST
  892. bool "Enable the 'tpm test' command"
  893. depends on CMD_TPM
  894. help
  895. This provides a a series of tests to confirm that the TPM is working
  896. correctly. The tests cover initialisation, non-volatile RAM, extend,
  897. global lock and checking that timing is within expectations. The
  898. tests pass correctly on Infineon TPMs but may need to be adjusted
  899. for other devices.
  900. endmenu
  901. menu "Firmware commands"
  902. config CMD_CROS_EC
  903. bool "Enable crosec command"
  904. depends on CROS_EC
  905. default y
  906. help
  907. Enable command-line access to the Chrome OS EC (Embedded
  908. Controller). This provides the 'crosec' command which has
  909. a number of sub-commands for performing EC tasks such as
  910. updating its flash, accessing a small saved context area
  911. and talking to the I2C bus behind the EC (if there is one).
  912. endmenu
  913. menu "Filesystem commands"
  914. config CMD_CBFS
  915. bool "Enable the 'cbfs' command"
  916. depends on FS_CBFS
  917. help
  918. Define this to enable support for reading from a Coreboot
  919. filesystem. This is a ROM-based filesystem used for accessing files
  920. on systems that use coreboot as the first boot-loader and then load
  921. U-Boot to actually boot the Operating System. Available commands are
  922. cbfsinit, cbfsinfo, cbfsls and cbfsload.
  923. config CMD_CRAMFS
  924. bool "Enable the 'cramfs' command"
  925. depends on FS_CRAMFS
  926. help
  927. This provides commands for dealing with CRAMFS (Compressed ROM
  928. filesystem). CRAMFS is useful when space is tight since files are
  929. compressed. Two commands are provided:
  930. cramfsls - lists files in a cramfs image
  931. cramfsload - loads a file from a cramfs image
  932. config CMD_EXT2
  933. bool "ext2 command support"
  934. help
  935. Enables EXT2 FS command
  936. config CMD_EXT4
  937. bool "ext4 command support"
  938. help
  939. Enables EXT4 FS command
  940. config CMD_EXT4_WRITE
  941. depends on CMD_EXT4
  942. bool "ext4 write command support"
  943. help
  944. Enables EXT4 FS write command
  945. config CMD_FAT
  946. bool "FAT command support"
  947. help
  948. Support for the FAT fs
  949. config CMD_FS_GENERIC
  950. bool "filesystem commands"
  951. help
  952. Enables filesystem commands (e.g. load, ls) that work for multiple
  953. fs types.
  954. config CMD_FS_UUID
  955. bool "fsuuid command"
  956. help
  957. Enables fsuuid command for filesystem UUID.
  958. config CMD_JFFS2
  959. bool "jffs2 command"
  960. help
  961. Enables commands to support the JFFS2 (Journalling Flash File System
  962. version 2) filesystem. This enables fsload, ls and fsinfo which
  963. provide the ability to load files, list directories and obtain
  964. filesystem information.
  965. config CMD_MTDPARTS
  966. depends on ARCH_SUNXI
  967. bool "MTD partition support"
  968. help
  969. MTD partition support
  970. config MTDIDS_DEFAULT
  971. string "Default MTD IDs"
  972. depends on CMD_MTDPARTS
  973. help
  974. Defines a default MTD ID
  975. config MTDPARTS_DEFAULT
  976. string "Default MTD partition scheme"
  977. depends on CMD_MTDPARTS
  978. help
  979. Defines a default MTD partitioning scheme in the Linux MTD command
  980. line partitions format
  981. endmenu
  982. menu "Debug commands"
  983. config CMD_BEDBUG
  984. bool "bedbug"
  985. help
  986. The bedbug (emBEDded deBUGger) command provides debugging features
  987. for some PowerPC processors. For details please see the
  988. docuemntation in doc/README.beddbug
  989. config CMD_DIAG
  990. bool "diag - Board diagnostics"
  991. help
  992. This command provides access to board diagnostic tests. These are
  993. called Power-on Self Tests (POST). The command allows listing of
  994. available tests and running either all the tests, or specific tests
  995. identified by name.
  996. endmenu
  997. config CMD_UBI
  998. tristate "Enable UBI - Unsorted block images commands"
  999. select CRC32
  1000. select MTD_UBI
  1001. default y if NAND_SUNXI
  1002. help
  1003. UBI is a software layer above MTD layer which admits use of LVM-like
  1004. logical volumes on top of MTD devices, hides some complexities of
  1005. flash chips like wear and bad blocks and provides some other useful
  1006. capabilities. Please, consult the MTD web site for more details
  1007. (www.linux-mtd.infradead.org). Activate this option if you want
  1008. to use U-Boot UBI commands.
  1009. config CMD_UBIFS
  1010. tristate "Enable UBIFS - Unsorted block images filesystem commands"
  1011. depends on CMD_UBI
  1012. select CRC32
  1013. select RBTREE if ARCH_SUNXI
  1014. select LZO if ARCH_SUNXI
  1015. default y if NAND_SUNXI
  1016. help
  1017. UBIFS is a file system for flash devices which works on top of UBI.
  1018. endmenu