1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
69 menu "Autoboot options"
75 This enables the autoboot. See doc/README.autoboot for detail.
78 bool "Stop autobooting via specific input key / string"
81 This option enables stopping (aborting) of the automatic
82 boot feature only by issuing a specific input key or
83 string. If not enabled, any input key will abort the
84 U-Boot automatic booting process and bring the device
85 to the U-Boot prompt for user input.
87 config AUTOBOOT_PROMPT
88 string "Autoboot stop prompt"
89 depends on AUTOBOOT_KEYED
90 default "Autoboot in %d seconds\\n"
92 This string is displayed before the boot delay selected by
93 CONFIG_BOOTDELAY starts. If it is not defined there is no
94 output indicating that autoboot is in progress.
96 Note that this define is used as the (only) argument to a
97 printf() call, so it may contain '%' format specifications,
98 provided that it also includes, sepearated by commas exactly
99 like in a printf statement, the required arguments. It is
100 the responsibility of the user to select only such arguments
101 that are valid in the given context.
103 config AUTOBOOT_ENCRYPTION
104 bool "Enable encryption in autoboot stopping"
105 depends on AUTOBOOT_KEYED
107 This option allows a string to be entered into U-Boot to stop the
108 autoboot. The string itself is hashed and compared against the hash
109 in the environment variable 'bootstopkeysha256'. If it matches then
110 boot stops and a command-line prompt is presented.
112 This provides a way to ship a secure production device which can also
113 be accessed at the U-Boot command line.
115 config AUTOBOOT_DELAY_STR
116 string "Delay autobooting via specific input key / string"
117 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
119 This option delays the automatic boot feature by issuing
120 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
121 or the environment variable "bootdelaykey" is specified
122 and this string is received from console input before
123 autoboot starts booting, U-Boot gives a command prompt. The
124 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
125 used, otherwise it never times out.
127 config AUTOBOOT_STOP_STR
128 string "Stop autobooting via specific input key / string"
129 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
131 This option enables stopping (aborting) of the automatic
132 boot feature only by issuing a specific input key or
133 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
134 variable "bootstopkey" is specified and this string is
135 received from console input before autoboot starts booting,
136 U-Boot gives a command prompt. The U-Boot prompt never
137 times out, even if CONFIG_BOOT_RETRY_TIME is used.
139 config AUTOBOOT_KEYED_CTRLC
140 bool "Enable Ctrl-C autoboot interruption"
141 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
144 This option allows for the boot sequence to be interrupted
145 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
146 Setting this variable provides an escape sequence from the
147 limited "password" strings.
149 config AUTOBOOT_STOP_STR_SHA256
150 string "Stop autobooting via SHA256 encrypted password"
151 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
153 This option adds the feature to only stop the autobooting,
154 and therefore boot into the U-Boot prompt, when the input
155 string / password matches a values that is encypted via
156 a SHA256 hash and saved in the environment.
158 config AUTOBOOT_USE_MENUKEY
159 bool "Allow a specify key to run a menu from the environment"
160 depends on !AUTOBOOT_KEYED
162 If a specific key is pressed to stop autoboot, then the commands in
163 the environment variable 'menucmd' are executed before boot starts.
165 config AUTOBOOT_MENUKEY
166 int "ASCII value of boot key to show a menu"
168 depends on AUTOBOOT_USE_MENUKEY
170 If this key is pressed to stop autoboot, then the commands in the
171 environment variable 'menucmd' will be executed before boot starts.
172 For example, 33 means "!" in ASCII, so pressing ! at boot would take
175 config AUTOBOOT_MENU_SHOW
176 bool "Show a menu on boot"
177 depends on CMD_BOOTMENU
179 This enables the boot menu, controlled by environment variables
180 defined by the board. The menu starts after running the 'preboot'
181 environmnent variable (if enabled) and before handling the boot delay.
182 See README.bootmenu for more details.
204 Print ".config" contents.
206 If this option is enabled, the ".config" file contents are embedded
207 in the U-Boot image and can be printed on the console by the "config"
208 command. This provides information of which options are enabled on
215 Print console devices and information.
220 Print information about available CPUs. This normally shows the
221 number of CPUs, type (e.g. manufacturer, architecture, product or
222 internal name) and clock frequency. Other information may be
223 available depending on the CPU driver.
229 Print GPL license text
234 Provides access to the Intel Power-Management Controller (PMC) so
235 that its state can be examined. This does not currently support
236 changing the state but it is still useful for debugging and seeing
253 Run the command stored in the environment "bootcmd", i.e.
254 "bootd" does the same thing as "run bootcmd".
260 Boot an application image from the memory.
265 Boot the Linux zImage
269 depends on ARM64 || RISCV
272 Boot an AArch64 Linux Kernel image from memory.
275 bool "Support booting Linux OS images"
276 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
279 Support booting the Linux kernel directly via a command such as bootm
283 bool "Support booting NetBSD (non-EFI) loader images"
287 Support booting NetBSD via the bootm command.
289 config BOOTM_OPENRTOS
290 bool "Support booting OPENRTOS / FreeRTOS images"
293 Support booting OPENRTOS / FreeRTOS via the bootm command.
296 bool "Support booting Enea OSE images"
297 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
300 Support booting Enea OSE images via the bootm command.
303 bool "Support booting Plan9 OS images"
307 Support booting Plan9 images via the bootm command.
310 bool "Support booting RTEMS OS images"
314 Support booting RTEMS images via the bootm command.
317 bool "Support booting VxWorks OS images"
321 Support booting VxWorks images via the bootm command.
325 depends on EFI_LOADER
328 Boot an EFI image from memory.
330 config CMD_BOOTEFI_HELLO_COMPILE
331 bool "Compile a standard EFI hello world binary for testing"
332 depends on CMD_BOOTEFI && !CPU_V7M
335 This compiles a standard EFI hello world application with U-Boot so
336 that it can be used with the test/py testing framework. This is useful
337 for testing that EFI is working at a basic level, and for bringing
338 up EFI support on a new architecture.
340 No additional space will be required in the resulting U-Boot binary
341 when this option is enabled.
343 config CMD_BOOTEFI_HELLO
344 bool "Allow booting a standard EFI hello world for testing"
345 depends on CMD_BOOTEFI_HELLO_COMPILE
347 This adds a standard EFI hello world application to U-Boot so that
348 it can be used with the 'bootefi hello' command. This is useful
349 for testing that EFI is working at a basic level, and for bringing
350 up EFI support on a new architecture.
352 source lib/efi_selftest/Kconfig
358 Add an ANSI terminal boot menu command.
363 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
364 image into RAM, dump image structure information, etc. Those dtb/dtbo
365 files should be merged in one dtb further, which needs to be passed to
366 the kernel, as part of a boot process.
369 bool "bootelf, bootvx"
372 Boot an ELF/vxWorks image from the memory.
375 bool "Flattened Device Tree utility commands"
379 Do FDT related setup before booting into the Operating System.
385 Start an application at a given address.
391 Run the command in the given environment variable.
397 Print header information for application image.
402 List all images found in flash
408 Extract a part of a multi-image.
411 bool "spl export - Export boot information for Falcon boot"
414 Falcon mode allows booting directly from SPL into an Operating
415 System such as Linux, thus skipping U-Boot proper. See
416 doc/README.falcon for full information about how to use this
419 config CMD_SPL_NAND_OFS
420 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
421 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
424 This provides the offset of the command line arguments for Linux
425 when booting from NAND in Falcon mode. See doc/README.falcon
426 for full information about how to use this option (and also see
427 board/gateworks/gw_ventana/README for an example).
429 config CMD_SPL_NOR_OFS
430 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
431 depends on CMD_SPL && SPL_NOR_SUPPORT
434 This provides the offset of the command line arguments or dtb for
435 Linux when booting from NOR in Falcon mode.
437 config CMD_SPL_WRITE_SIZE
438 hex "Size of argument area"
442 This provides the size of the command-line argument area in NAND
443 flash used by Falcon-mode boot. See the documentation until CMD_SPL
447 bool "fitImage update command"
449 Implements the 'fitupd' command, which allows to automatically
450 store software updates present on a TFTP server in NOR Flash
452 config CMD_THOR_DOWNLOAD
453 bool "thor - TIZEN 'thor' download"
456 Implements the 'thor' download protocol. This is a way of
457 downloading a software update over USB from an attached host.
458 There is no documentation about this within the U-Boot source code
459 but you should be able to find something on the interwebs.
462 bool "zboot - x86 boot command"
464 With x86 machines it is common to boot a bzImage file which
465 contains both a kernel and a setup.bin file. The latter includes
466 configuration information from the dark ages which x86 boards still
467 need to pick things out of.
469 Consider using FIT in preference to this since it supports directly
470 booting both 32- and 64-bit kernels, as well as secure boot.
471 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
475 menu "Environment commands"
478 bool "ask for env variable"
480 Ask for environment variable
498 Edit environment variable.
503 Allow for searching environment variables
509 Save all environment variables into the compiled-in persistent
515 depends on CMD_SAVEENV
517 Erase environment variables from the compiled-in persistent
520 config CMD_ENV_EXISTS
524 Check if a variable is defined in the environment for use in
527 config CMD_ENV_CALLBACK
528 bool "env callbacks - print callbacks and their associated variables"
530 Some environment variable have callbacks defined by
531 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
532 For example changing "baudrate" adjust the serial baud rate. This
533 command lists the currently defined callbacks.
536 bool "env flags -print variables that have non-default flags"
538 Some environment variables have special flags that control their
539 behaviour. For example, serial# can only be written once and cannot
540 be deleted. This command shows the variables that have special
543 config CMD_NVEDIT_EFI
544 bool "env [set|print] -e - set/print UEFI variables"
545 depends on EFI_LOADER
548 UEFI variables are encoded as some form of U-Boot variables.
549 If enabled, we are allowed to set/print UEFI variables using
550 "env" command with "-e" option without knowing details.
552 config CMD_NVEDIT_INFO
553 bool "env info - print or evaluate environment information"
555 Print environment information:
556 - env_valid : is environment valid
557 - env_ready : is environment imported into hash table
558 - env_use_default : is default environment used
560 This command can be optionally used for evaluation in scripts:
561 [-d] : evaluate whether default environment is used
562 [-p] : evaluate whether environment can be persisted
563 The result of multiple evaluations will be combined with AND.
567 menu "Memory commands"
572 Compute binary operations (xor, or, and) of byte arrays of arbitrary
573 size from memory and store the result in memory or the environment.
586 Add -v option to verify data against a crc32 checksum.
589 bool "eeprom - EEPROM subsystem"
591 (deprecated, needs conversion to driver model)
592 Provides commands to read and write EEPROM (Electrically Erasable
593 Programmable Read Only Memory) chips that are connected over an
596 config CMD_EEPROM_LAYOUT
597 bool "Enable layout-aware eeprom commands"
598 depends on CMD_EEPROM
600 (deprecated, needs conversion to driver model)
601 When enabled, additional eeprom sub-commands become available.
603 eeprom print - prints the contents of the eeprom in a human-readable
604 way (eeprom layout fields, and data formatted to be fit for human
607 eeprom update - allows user to update eeprom fields by specifying
608 the field name, and providing the new data in a human readable format
609 (same format as displayed by the eeprom print command).
611 Both commands can either auto detect the layout, or be told which
615 __weak int parse_layout_version(char *str)
616 - override to provide your own layout name parsing
617 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
619 - override to setup the layout metadata based on the version
620 __weak int eeprom_layout_detect(unsigned char *data)
621 - override to provide your own algorithm for detecting layout
624 - contains various printing and updating functions for common
625 types of eeprom fields. Can be used for defining
628 config EEPROM_LAYOUT_HELP_STRING
629 string "Tells user what layout names are supported"
630 depends on CMD_EEPROM_LAYOUT
631 default "<not defined>"
633 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
639 Infinite write loop on address range
646 Compute MD5 checksum.
651 depends on CMD_MD5SUM
653 Add -v option to verify data against an MD5 checksum.
658 Display memory information.
661 bool "md, mm, nm, mw, cp, cmp, base, loop"
666 mm - memory modify (auto-incrementing address)
667 nm - memory modify (constant address)
668 mw - memory write (fill)
671 base - print or set address offset
672 loop - initialize loop on address range
675 bool "Enable cyclic md/mw commands"
676 depends on CMD_MEMORY
678 Add the "mdc" and "mwc" memory commands. These are cyclic
683 This command will print 4 bytes (10,11,12,13) each 500 ms.
685 => mwc.l 100 12345678 10
686 This command will write 12345678 to address 100 all 10 ms.
691 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
693 random - fill memory with random data
698 Simple RAM read/write test.
702 config SYS_ALT_MEMTEST
703 bool "Alternative test"
705 Use a more complete alternative memory test.
712 mdc - memory display cyclic
713 mwc - memory write cyclic
719 Compute SHA1 checksum.
721 config SHA1SUM_VERIFY
723 depends on CMD_SHA1SUM
725 Add -v option to verify data against a SHA1 checksum.
728 bool "strings - display strings in memory"
730 This works similarly to the Unix 'strings' command except that it
731 works with a memory range. String of printable characters found
732 within the range are displayed. The minimum number of characters
733 for a sequence to be considered a string can be provided.
737 menu "Compression commands"
741 default y if CMD_BOOTI
744 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
749 default y if CMD_BOOTI
751 Uncompress a zip-compressed memory region.
756 Compress a memory region with zlib deflate method.
760 menu "Device access commands"
763 #depends on FLASH_CFI_DRIVER
766 ARM Ltd reference designs flash partition access
769 bool "adc - Access Analog to Digital Converters info and data"
773 Shows ADC device info and permit printing one-shot analog converted
774 data from a named Analog to Digital Converter.
779 depends on PARTITIONS
781 Read/modify/write the fields of Bootloader Control Block, usually
782 stored on the flash "misc" partition with its structure defined in:
783 https://android.googlesource.com/platform/bootable/recovery/+/master/
784 bootloader_message/include/bootloader_message/bootloader_message.h
786 Some real-life use-cases include (but are not limited to):
787 - Determine the "boot reason" (and act accordingly):
788 https://source.android.com/devices/bootloader/boot-reason
789 - Get/pass a list of commands from/to recovery:
790 https://android.googlesource.com/platform/bootable/recovery
791 - Inspect/dump the contents of the BCB fields
794 bool "bind/unbind - Bind or unbind a device to/from a driver"
797 Bind or unbind a device to/from a driver from the command line.
798 This is useful in situations where a device may be handled by several
799 drivers. For example, this can be used to bind a UDC to the usb ether
800 gadget driver from the command line.
803 bool "clk - Show clock frequencies"
806 Shows clock frequences by calling a sock_clk_dump() hook function.
807 This is depreated in favour of using the CLK uclass and accessing
808 clock values from associated drivers. However currently no command
812 bool "demo - Demonstration commands for driver model"
815 Provides a 'demo' command which can be used to play around with
816 driver model. To use this properly you will need to enable one or
817 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
818 Otherwise you will always get an empty list of devices. The demo
819 devices are defined in the sandbox device tree, so the easiest
820 option is to use sandbox and pass the -d point to sandbox's
827 Enables the command "dfu" which is used to have U-Boot create a DFU
828 class device via USB. This command requires that the "dfu_alt_info"
829 environment variable be set and define the alt settings to expose to
833 bool "dm - Access to driver model information"
836 Provides access to driver model data structures and information,
837 such as a list of devices, list of uclasses and the state of each
838 device (e.g. activated). This is not required for operation, but
839 can be useful to see the state of driver model for debugging or
843 bool "fastboot - Android fastboot support"
846 This enables the command "fastboot" which enables the Android
847 fastboot mode for the platform. Fastboot is a protocol for
848 downloading images, flashing and device control used on
849 Android devices. Fastboot requires either the network stack
850 enabled or support for acting as a USB device.
852 See doc/android/fastboot.txt for more information.
855 bool "fdcboot - Boot from floppy device"
857 The 'fdtboot' command allows booting an image from a floppy disk.
860 bool "flinfo, erase, protect"
862 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
865 flinfo - print FLASH memory information
867 protect - enable or disable FLASH write protection
876 config CMD_FPGA_LOADBP
877 bool "fpga loadbp - load partial bitstream (Xilinx only)"
880 Supports loading an FPGA device from a bitstream buffer containing
883 config CMD_FPGA_LOADFS
884 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
887 Supports loading an FPGA device from a FAT filesystem.
889 config CMD_FPGA_LOADMK
890 bool "fpga loadmk - load bitstream from image"
893 Supports loading an FPGA device from a image generated by mkimage.
895 config CMD_FPGA_LOADP
896 bool "fpga loadp - load partial bitstream"
899 Supports loading an FPGA device from a bitstream buffer containing
902 config CMD_FPGA_LOAD_SECURE
903 bool "fpga loads - loads secure bitstreams (Xilinx only)"
906 Enables the fpga loads command which is used to load secure
907 (authenticated or encrypted or both) bitstreams on to FPGA.
910 bool "fpgad - dump FPGA registers"
912 (legacy, needs conversion to driver model)
913 Provides a way to dump FPGA registers by calling the board-specific
914 fpga_get_reg() function. This functions similarly to the 'md'
918 bool "fuse - support for the fuse subssystem"
920 (deprecated - needs conversion to driver model)
921 This allows reading, sensing, programming or overriding fuses
922 which control the behaviour of the device. The command uses the
931 bool "GPT (GUID Partition Table) command"
933 select HAVE_BLOCK_DEVICE
934 select PARTITION_UUIDS
937 Enable the 'gpt' command to ready and write GPT style partition
941 bool "GPT Random UUID generation"
944 Enable the generation of partitions with random UUIDs if none
947 config CMD_GPT_RENAME
948 bool "GPT partition renaming commands"
951 Enables the 'gpt' command to interchange names on two GPT
952 partitions via the 'gpt swap' command or to rename single
953 partitions via the 'rename' command.
956 bool "ide - Support for IDE drivers"
959 Provides an 'ide' command which allows accessing the IDE drive,
960 reseting the IDE interface, printing the partition table and
961 geting device info. It also enables the 'diskboot' command which
962 permits booting from an IDE drive.
965 bool "io - Support for performing I/O accesses"
967 Provides an 'iod' command to display I/O space and an 'iow' command
968 to write values to the I/O space. This can be useful for manually
969 checking the state of devices during boot when debugging device
973 bool "iotrace - Support for tracing I/O activity"
975 Provides an 'iotrace' command which supports recording I/O reads and
976 writes in a trace buffer in memory . It also maintains a checksum
977 of the trace records (even if space is exhausted) so that the
978 sequence of I/O accesses can be verified.
980 When debugging drivers it is useful to see what I/O accesses were
981 done and in what order.
983 Even if the individual accesses are of little interest it can be
984 useful to verify that the access pattern is consistent each time
985 an operation is performed. In this case a checksum can be used to
986 characterise the operation of a driver. The checksum can be compared
987 across different runs of the operation to verify that the driver is
990 In particular, when performing major refactoring of the driver, where
991 the access pattern should not change, the checksum provides assurance
992 that the refactoring work has not broken the driver.
994 This works by sneaking into the io.h heder for an architecture and
995 redirecting I/O accesses through iotrace's tracing mechanism.
997 For now no commands are provided to examine the trace buffer. The
998 format is fairly simple, so 'md' is a reasonable substitute.
1000 Note: The checksum feature is only useful for I/O regions where the
1001 contents do not change outside of software control. Where this is not
1002 suitable you can fall back to manually comparing the addresses. It
1003 might be useful to enhance tracing to only checksum the accesses and
1004 not the data read/written.
1014 bool "w1 - Support for Dallas 1-Wire protocol"
1016 Dallas 1-wire protocol support
1022 Load a binary file over serial line.
1028 Load an S-Record file over serial line
1033 MMC memory mapped support.
1036 bool "Enable support for RPMB in the mmc command"
1039 Enable the commands for reading, writing and programming the
1040 key for the Replay Protection Memory Block partition in eMMC.
1042 config CMD_MMC_SWRITE
1044 depends on CMD_MMC && MMC_WRITE
1047 Enable support for the "mmc swrite" command to write Android sparse
1053 select MTD_PARTITIONS
1055 MTD commands support.
1059 default y if NAND_SUNXI
1060 depends on MTD_RAW_NAND
1065 config CMD_NAND_TRIMFFS
1066 bool "nand write.trimffs"
1067 default y if ARCH_SUNXI
1069 Allows one to skip empty pages when flashing something on a NAND.
1071 config CMD_NAND_LOCK_UNLOCK
1072 bool "nand lock/unlock"
1074 NAND locking support.
1076 config CMD_NAND_TORTURE
1079 NAND torture support.
1088 NVM Express device support
1091 bool "onenand - access to onenand device"
1094 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1095 various useful features. This command allows reading, writing,
1096 and erasing blocks. It allso provides a way to show and change
1097 bad blocks, and test the device.
1102 Enable the 'osd' command which allows to query information from and
1103 write text data to a on-screen display (OSD) device; a virtual device
1104 associated with a display capable of displaying a text overlay on the
1105 display it's associated with..
1109 select HAVE_BLOCK_DEVICE
1110 select PARTITION_UUIDS
1112 Read and display information about the partition table on
1116 bool "pci - Access PCI devices"
1118 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1119 used on some devices to allow the CPU to communicate with its
1120 peripherals. Sub-commands allow bus enumeration, displaying and
1121 changing configuration space and a few other features.
1124 bool "pinmux - show pins muxing"
1125 default y if PINCTRL
1127 Parse all available pin-controllers and show pins muxing. This
1128 is useful for debug purpoer to check the pin muxing and to know if
1129 a pin is configured as a GPIO or as an alternate function.
1134 Poweroff/Shutdown the system
1137 bool "read - Read binary data from a partition"
1139 Provides low-level access to the data in a partition.
1141 config CMD_REMOTEPROC
1143 depends on REMOTEPROC
1145 Support for Remote Processor control
1148 bool "sata - Access SATA subsystem"
1151 SATA (Serial Advanced Technology Attachment) is a serial bus
1152 standard for connecting to hard drives and other storage devices.
1153 This command provides information about attached devices and allows
1154 reading, writing and other operations.
1156 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1157 Attachment, where AT refers to an IBM AT (Advanced Technology)
1158 computer released in 1984.
1161 bool "saves - Save a file over serial in S-Record format"
1163 Provides a way to save a binary file using the Motorola S-Record
1164 format over the serial line.
1167 bool "scsi - Access to SCSI devices"
1170 This provides a 'scsi' command which provides access to SCSI (Small
1171 Computer System Interface) devices. The command provides a way to
1172 scan the bus, reset the bus, read and write data and get information
1176 bool "sdram - Print SDRAM configuration information"
1178 Provides information about attached SDRAM. This assumed that the
1179 SDRAM has an EEPROM with information that can be read using the
1180 I2C bus. This is only available on some boards.
1184 depends on DM_SPI_FLASH || SPI_FLASH
1185 default y if DM_SPI_FLASH
1190 bool "sf test - Allow testing of SPI flash"
1193 Provides a way to test that SPI flash is working correctly. The
1194 test is destructive, in that an area of SPI flash must be provided
1195 for the test to use. Performance information is also provided,
1196 measuring the performance of reading, writing and erasing in
1197 Mbps (Million Bits Per Second). This value should approximately
1198 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1199 everything is working properly.
1202 bool "sspi - Command to access spi device"
1205 SPI utility command.
1207 config DEFAULT_SPI_BUS
1208 int "default spi bus used by sspi command"
1212 config DEFAULT_SPI_MODE
1213 hex "default spi mode used by sspi command (see include/spi.h)"
1218 bool "tsi148 - Command to access tsi148 device"
1220 This provides various sub-commands to initialise and configure the
1221 Turndra tsi148 device. See the command help for full details.
1224 bool "Enable UFS - Universal Flash Subsystem commands"
1227 "This provides commands to initialise and configure universal flash
1231 bool "universe - Command to set up the Turndra Universe controller"
1233 This allows setting up the VMEbus provided by this controller.
1234 See the command help for full details.
1238 select HAVE_BLOCK_DEVICE
1244 select USB_FUNCTION_SDP
1246 Enables the command "sdp" which is used to have U-Boot emulating the
1247 Serial Download Protocol (SDP) via USB.
1251 depends on USB_FUNCTION_ROCKUSB
1253 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1254 read/write info, image to/from devices. This enable rockusb command
1255 support to communication with rockusb device. for more detail about
1256 this command, please read doc/README.rockusb.
1258 config CMD_USB_MASS_STORAGE
1259 bool "UMS usb mass storage"
1260 select USB_FUNCTION_MASS_STORAGE
1262 USB mass storage support
1269 VirtIO block device support
1275 This provides commands to control the watchdog timer devices.
1281 Enable the command "axi" for accessing AXI (Advanced eXtensible
1282 Interface) busses, a on-chip interconnect specification for managing
1283 functional blocks in SoC designs, which is also often used in designs
1284 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1288 menu "Shell scripting commands"
1294 Echo args to console
1300 Return true/false on integer compare.
1306 Run script from memory
1312 Evaluate boolean and math expressions and store the result in an env
1314 Also supports loading the value at a memory location into a variable.
1315 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1319 menu "Android support commands"
1321 config CMD_AB_SELECT
1324 depends on ANDROID_AB
1326 On Android devices with more than one boot slot (multiple copies of
1327 the kernel and system images) this provides a command to select which
1328 slot should be used to boot from and register the boot attempt. This
1329 is used by the new A/B update model where one slot is updated in the
1330 background while running from the other slot.
1337 bool "Network commands"
1347 bootp - boot image via network using BOOTP/TFTP protocol
1351 depends on CMD_BOOTP
1353 Boot image via network using DHCP/TFTP protocol
1355 config BOOTP_BOOTPATH
1356 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1358 depends on CMD_BOOTP
1360 Even though the config is called BOOTP_BOOTPATH, it stores the
1361 path in the variable 'rootpath'.
1364 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1366 depends on CMD_BOOTP
1368 The primary DNS server is stored as 'dnsip'. If two servers are
1369 returned, you must set BOOTP_DNS2 to store that second server IP
1373 bool "Store 'dnsip2' from BOOTP/DHCP server"
1374 depends on BOOTP_DNS
1376 If a DHCP client requests the DNS server IP from a DHCP server,
1377 it is possible that more than one DNS serverip is offered to the
1378 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1379 server IP will be stored in the additional environment
1380 variable "dnsip2". The first DNS serverip is always
1381 stored in the variable "dnsip", when BOOTP_DNS is defined.
1383 config BOOTP_GATEWAY
1384 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1386 depends on CMD_BOOTP
1388 config BOOTP_HOSTNAME
1389 bool "Request & store 'hostname' from BOOTP/DHCP server"
1391 depends on CMD_BOOTP
1393 The name may or may not be qualified with the local domain name.
1395 config BOOTP_PREFER_SERVERIP
1396 bool "serverip variable takes precedent over DHCP server IP."
1397 depends on CMD_BOOTP
1399 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1401 With this option enabled, the 'serverip' variable in the environment
1402 takes precedence over DHCP server IP and will only be set by the DHCP
1403 server if not already set in the environment.
1405 config BOOTP_SUBNETMASK
1406 bool "Request & store 'netmask' from BOOTP/DHCP server"
1408 depends on CMD_BOOTP
1410 config BOOTP_NTPSERVER
1411 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1412 depends on CMD_BOOTP
1417 Selecting this will allow capturing all Ethernet packets and store
1418 them in physical memory in a PCAP formated file,
1419 later to be analyzed by PCAP reader application (IE. WireShark).
1422 bool "Send PXE client arch to BOOTP/DHCP server"
1424 depends on CMD_BOOTP && CMD_PXE
1426 Supported for ARM, ARM64, and x86 for now.
1428 config BOOTP_PXE_CLIENTARCH
1430 depends on BOOTP_PXE
1431 default 0x16 if ARM64
1435 config BOOTP_VCI_STRING
1437 depends on CMD_BOOTP
1438 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1439 default "U-Boot.armv8" if ARM64
1440 default "U-Boot.arm" if ARM
1447 tftpboot - boot image via network using TFTP protocol
1451 depends on CMD_TFTPBOOT
1453 TFTP put command, for uploading files to a server
1457 depends on CMD_TFTPBOOT
1459 Act as a TFTP server and boot the first received file
1461 config NET_TFTP_VARS
1462 bool "Control TFTP timeout and count through environment"
1463 depends on CMD_TFTPBOOT
1466 If set, allows controlling the TFTP timeout through the
1467 environment variable tftptimeout, and the TFTP maximum
1468 timeout count through the variable tftptimeoutcountmax.
1469 If unset, timeout and maximum are hard-defined as 1 second
1470 and 10 timouts per TFTP transfer.
1475 Boot image via network using RARP/TFTP protocol
1481 Boot image via network using NFS protocol.
1487 If set, allows 802.3(clause 22) MII Management functions interface access
1488 The management interface specified in Clause 22 provides
1489 a simple, two signal, serial interface to connect a
1490 Station Management entity and a managed PHY for providing access
1491 to management parameters and services.
1492 The interface is referred to as the MII management interface.
1498 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1499 The MDIO interface is orthogonal to the MII interface and extends
1500 it by adding access to more registers through indirect addressing.
1505 Send ICMP ECHO_REQUEST to network host
1510 Perform CDP network configuration
1515 Synchronize RTC via network
1520 Lookup the IP of a hostname
1522 config CMD_LINK_LOCAL
1526 Acquire a network IP address using the link-local protocol
1533 Allow control of L2 Ethernet switch commands. These are supported
1534 by the vsc9953 Ethernet driver at present. Sub-commands allow
1535 operations such as enabling / disabling a port and
1536 viewing/maintaining the filtering database (FDB)
1542 Boot image via network using PXE protocol
1547 Wait for wake-on-lan Magic Packet
1551 menu "Misc commands"
1554 bool "Enable 'bmp' command"
1555 depends on LCD || DM_VIDEO || VIDEO
1557 This provides a way to obtain information about a BMP-format image
1558 and to display it. BMP (which presumably stands for BitMaP) is a
1559 file format defined by Microsoft which supports images of various
1560 depths, formats and compression methods. Headers on the file
1561 determine the formats used. This command can be used by first loading
1562 the image into RAM, then using this command to look at it or display
1565 config CMD_BOOTCOUNT
1567 depends on BOOTCOUNT_LIMIT
1569 Enable the bootcount command, which allows interrogation and
1570 reset of the bootcounter.
1573 bool "Enable board-specific commands"
1575 (deprecated: instead, please define a Kconfig option for each command)
1577 Some boards have board-specific commands which are only enabled
1578 during developemnt and need to be turned off for production. This
1579 option provides a way to control this. The commands that are enabled
1580 vary depending on the board.
1582 config CMD_BKOPS_ENABLE
1583 bool "mmc bkops enable"
1587 Enable command for setting manual background operations handshake
1588 on a eMMC device. The feature is optionally available on eMMC devices
1589 conforming to standard >= 4.41.
1591 config CMD_BLOCK_CACHE
1592 bool "blkcache - control and stats for block cache"
1593 depends on BLOCK_CACHE
1594 default y if BLOCK_CACHE
1596 Enable the blkcache command, which can be used to control the
1597 operation of the cache functions.
1598 This is most useful when fine-tuning the operation of the cache
1599 during development, but also allows the cache to be disabled when
1600 it might hurt performance (e.g. when using the ums command).
1603 bool "icache or dcache"
1605 Enable the "icache" and "dcache" commands
1607 config CMD_CONITRACE
1608 bool "conitrace - trace console input codes"
1610 Enable the 'conitrace' command which displays the codes received
1611 from the console input as hexadecimal numbers.
1614 bool "Enable clear screen command 'cls'"
1615 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1618 Enable the 'cls' command which clears the screen contents
1619 on video frame buffer.
1622 bool "efidebug - display/configure UEFI environment"
1623 depends on EFI_LOADER
1624 select EFI_DEVICE_PATH_TO_TEXT
1627 Enable the 'efidebug' command which provides a subset of UEFI
1628 shell utility with simplified functionality. It will be useful
1629 particularly for managing boot parameters as well as examining
1630 various EFI status for debugging.
1632 config CMD_EXCEPTION
1633 bool "exception - raise exception"
1634 depends on ARM || RISCV || X86
1636 Enable the 'exception' command which allows to raise an exception.
1643 Enable the 'led' command which allows for control of LEDs supported
1644 by the board. The LEDs can be listed with 'led list' and controlled
1645 with led on/off/togle/blink. Any LED drivers can be controlled with
1646 this command, e.g. led_gpio.
1653 Enable the 'date' command for getting/setting the time/date in RTC
1659 Run commands and summarize execution time.
1662 bool "gettime - read elapsed time"
1664 Enable the 'gettime' command which reads the elapsed time since
1665 U-Boot started running. This shows the time in seconds and
1666 milliseconds. See also the 'bootstage' command which provides more
1667 flexibility for boot timing.
1669 # TODO: rename to CMD_SLEEP
1674 Delay execution for some time
1677 bool "support for multiprocessor"
1679 This provides an option to brinup
1680 different processors in multiprocessor
1686 Access the system timer.
1692 This provides basic access to the U-Boot's sound support. The main
1693 feature is to play a beep.
1695 sound init - set up sound system
1696 sound play - play a sound
1702 Boot image via local extlinux.conf file
1708 This provides access to the QEMU firmware interface. The main
1709 feature is to allow easy loading of files passed to qemu-system
1710 via -kernel / -initrd
1712 source "cmd/mvebu/Kconfig"
1715 bool "terminal - provides a way to attach a serial terminal"
1717 Provides a 'cu'-like serial terminal command. This can be used to
1718 access other serial ports from the system console. The terminal
1719 is very simple with no special processing of characters. As with
1720 cu, you can press ~. (tilde followed by period) to exit.
1723 bool "uuid, guid - generation of unique IDs"
1726 This enables two commands:
1728 uuid - generate random Universally Unique Identifier
1729 guid - generate Globally Unique Identifier based on random UUID
1731 The two commands are very similar except for the endianness of the
1736 source "cmd/ti/Kconfig"
1738 config CMD_BOOTSTAGE
1739 bool "Enable the 'bootstage' command"
1740 depends on BOOTSTAGE
1742 Add a 'bootstage' command which supports printing a report
1743 and un/stashing of bootstage data.
1745 menu "Power commands"
1747 bool "Enable Driver Model PMIC command"
1750 This is the pmic command, based on a driver model pmic's API.
1751 Command features are unchanged:
1752 - list - list pmic devices
1753 - pmic dev <id> - show or [set] operating pmic device (NEW)
1754 - pmic dump - dump registers
1755 - pmic read address - read byte of register at address
1756 - pmic write address - write byte to register at address
1757 The only one change for this command is 'dev' subcommand.
1759 config CMD_REGULATOR
1760 bool "Enable Driver Model REGULATOR command"
1761 depends on DM_REGULATOR
1763 This command is based on driver model regulator's API.
1764 User interface features:
1765 - list - list regulator devices
1766 - regulator dev <id> - show or [set] operating regulator device
1767 - regulator info - print constraints info
1768 - regulator status - print operating status
1769 - regulator value <val] <-f> - print/[set] voltage value [uV]
1770 - regulator current <val> - print/[set] current value [uA]
1771 - regulator mode <id> - print/[set] operating mode id
1772 - regulator enable - enable the regulator output
1773 - regulator disable - disable the regulator output
1775 The '-f' (force) option can be used for set the value which exceeds
1776 the limits, which are found in device-tree and are kept in regulator's
1777 uclass platdata structure.
1781 menu "Security commands"
1783 bool "Enable the 'aes' command"
1786 This provides a means to encrypt and decrypt data using the AES
1787 (Advanced Encryption Standard). This algorithm uses a symetric key
1788 and is widely used as a streaming cipher. Different key lengths are
1789 supported by the algorithm but this command only supports 128 bits
1793 bool "Enable the 'blob' command"
1795 This is used with the Freescale secure boot mechanism.
1797 Freescale's SEC block has built-in Blob Protocol which provides
1798 a method for protecting user-defined data across system power
1799 cycles. SEC block protects data in a data structure called a Blob,
1800 which provides both confidentiality and integrity protection.
1802 Encapsulating data as a blob
1803 Each time that the Blob Protocol is used to protect data, a
1804 different randomly generated key is used to encrypt the data.
1805 This random key is itself encrypted using a key which is derived
1806 from SoC's non-volatile secret key and a 16 bit Key identifier.
1807 The resulting encrypted key along with encrypted data is called a
1808 blob. The non-volatile secure key is available for use only during
1811 During decapsulation, the reverse process is performed to get back
1815 blob enc - encapsulating data as a cryptgraphic blob
1816 blob dec - decapsulating cryptgraphic blob to get the data
1820 blob enc src dst len km
1822 Encapsulate and create blob of data $len bytes long
1823 at address $src and store the result at address $dst.
1824 $km is the 16 byte key modifier is also required for
1825 generation/use as key for cryptographic operation. Key
1826 modifier should be 16 byte long.
1828 blob dec src dst len km
1830 Decapsulate the blob of data at address $src and
1831 store result of $len byte at addr $dst.
1832 $km is the 16 byte key modifier is also required for
1833 generation/use as key for cryptographic operation. Key
1834 modifier should be 16 byte long.
1837 bool "Support 'hash' command"
1840 This provides a way to hash data in memory using various supported
1841 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1842 saved to memory or to an environment variable. It is also possible
1843 to verify a hash against data in memory.
1846 bool "Support the 'hvc' command"
1847 depends on ARM_SMCCC
1849 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1850 development and testing.
1853 bool "Support the 'smc' command"
1854 depends on ARM_SMCCC
1856 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1857 development and testing.
1863 Add -v option to verify data against a hash.
1873 bool "Enable the 'tpm' command"
1874 depends on TPM_V1 || TPM_V2
1875 select CMD_TPM_V1 if TPM_V1
1876 select CMD_TPM_V2 if TPM_V2
1878 This provides a means to talk to a TPM from the command line. A wide
1879 range of commands if provided - see 'tpm help' for details. The
1880 command requires a suitable TPM on your board and the correct driver
1886 bool "Enable the 'tpm test' command"
1889 This provides a a series of tests to confirm that the TPMv1.x is
1890 working correctly. The tests cover initialisation, non-volatile RAM,
1891 extend, global lock and checking that timing is within expectations.
1892 The tests pass correctly on Infineon TPMs but may need to be adjusted
1899 menu "Firmware commands"
1901 bool "Enable crosec command"
1905 Enable command-line access to the Chrome OS EC (Embedded
1906 Controller). This provides the 'crosec' command which has
1907 a number of sub-commands for performing EC tasks such as
1908 updating its flash, accessing a small saved context area
1909 and talking to the I2C bus behind the EC (if there is one).
1912 menu "Filesystem commands"
1914 bool "Enable the 'btrsubvol' command"
1917 This enables the 'btrsubvol' command to list subvolumes
1918 of a BTRFS filesystem. There are no special commands for
1919 listing BTRFS directories or loading BTRFS files - this
1920 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1921 when BTRFS is enabled (see FS_BTRFS).
1924 bool "Enable the 'cbfs' command"
1927 Define this to enable support for reading from a Coreboot
1928 filesystem. This is a ROM-based filesystem used for accessing files
1929 on systems that use coreboot as the first boot-loader and then load
1930 U-Boot to actually boot the Operating System. Available commands are
1931 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1934 bool "Enable the 'cramfs' command"
1935 depends on FS_CRAMFS
1937 This provides commands for dealing with CRAMFS (Compressed ROM
1938 filesystem). CRAMFS is useful when space is tight since files are
1939 compressed. Two commands are provided:
1941 cramfsls - lists files in a cramfs image
1942 cramfsload - loads a file from a cramfs image
1945 bool "ext2 command support"
1948 Enables EXT2 FS command
1951 bool "ext4 command support"
1954 Enables EXT4 FS command
1956 config CMD_EXT4_WRITE
1958 bool "ext4 write command support"
1961 Enables EXT4 FS write command
1964 bool "FAT command support"
1967 Support for the FAT fs
1969 config CMD_FS_GENERIC
1970 bool "filesystem commands"
1972 Enables filesystem commands (e.g. load, ls) that work for multiple
1976 bool "fsuuid command"
1978 Enables fsuuid command for filesystem UUID.
1981 bool "jffs2 command"
1984 Enables commands to support the JFFS2 (Journalling Flash File System
1985 version 2) filesystem. This enables fsload, ls and fsinfo which
1986 provide the ability to load files, list directories and obtain
1987 filesystem information.
1990 bool "MTD partition support"
1993 MTD partitioning tool support.
1994 It is strongly encouraged to avoid using this command
1995 anymore along with 'sf', 'nand', 'onenand'. One can still
1996 declare the partitions in the mtdparts environment variable
1997 but better use the MTD stack and the 'mtd' command instead.
1999 config CMD_MTDPARTS_SPREAD
2000 bool "Padd partition size to take account of bad blocks"
2001 depends on CMD_MTDPARTS
2003 This enables the 'spread' sub-command of the mtdparts command.
2004 This command will modify the existing mtdparts variable by increasing
2005 the size of the partitions such that 1) each partition's net size is
2006 at least as large as the size specified in the mtdparts variable and
2007 2) each partition starts on a good block.
2009 config CMD_MTDPARTS_SHOW_NET_SIZES
2010 bool "Show net size (w/o bad blocks) of partitions"
2011 depends on CMD_MTDPARTS
2013 Adds two columns to the printed partition table showing the
2014 effective usable size of a partition, if bad blocks are taken
2017 config MTDIDS_DEFAULT
2018 string "Default MTD IDs"
2019 depends on MTD || SPI_FLASH
2021 Defines a default MTD IDs list for use with MTD partitions in the
2022 Linux MTD command line partitions format.
2024 config MTDPARTS_DEFAULT
2025 string "Default MTD partition scheme"
2026 depends on MTD || SPI_FLASH
2028 Defines a default MTD partitioning scheme in the Linux MTD command
2029 line partitions format
2032 bool "reiser - Access to reiserfs filesystems"
2034 This provides two commands which operate on a resierfs filesystem,
2035 commonly used some years ago:
2037 reiserls - list files
2038 reiserload - load a file
2041 bool "yaffs2 - Access of YAFFS2 filesystem"
2045 This provides commands for accessing a YAFFS2 filesystem. Yet
2046 Another Flash Filesystem 2 is a filesystem designed specifically
2047 for NAND flash. It incorporates bad-block management and ensures
2048 that device writes are sequential regardless of filesystem
2052 bool "zfs - Access of ZFS filesystem"
2054 This provides commands to accessing a ZFS filesystem, commonly used
2055 on Solaris systems. Two sub-commands are provided:
2057 zfsls - list files in a directory
2058 zfsload - load a file
2060 See doc/README.zfs for more details.
2064 menu "Debug commands"
2069 The bedbug (emBEDded deBUGger) command provides debugging features
2070 for some PowerPC processors. For details please see the
2071 docuemntation in doc/README.beddbug
2074 bool "diag - Board diagnostics"
2076 This command provides access to board diagnostic tests. These are
2077 called Power-on Self Tests (POST). The command allows listing of
2078 available tests and running either all the tests, or specific tests
2082 bool "irq - Show information about interrupts"
2083 depends on !ARM && !MIPS && !SH
2085 This enables two commands:
2087 interrupts - enable or disable interrupts
2088 irqinfo - print device-specific interrupt information
2091 bool "kgdb - Allow debugging of U-Boot with gdb"
2094 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2095 over a serial link for debugging purposes. This allows
2096 single-stepping, inspecting variables, etc. This is supported only
2097 on PowerPC at present.
2100 bool "log - Generation, control and access to logging"
2103 This provides access to logging features. It allows the output of
2104 log data to be controlled to a limited extent (setting up the default
2105 maximum log level for emitting of records). It also provides access
2106 to a command used for testing the log system.
2109 bool "trace - Support tracing of function calls and timing"
2111 Enables a command to control using of function tracing within
2112 U-Boot. This allows recording of call traces including timing
2113 information. The command can write data to memory for exporting
2114 for analysis (e.g. using bootchart). See doc/README.trace for full
2118 bool "avb - Android Verified Boot 2.0 operations"
2119 depends on AVB_VERIFY
2122 Enables a "avb" command to perform verification of partitions using
2123 Android Verified Boot 2.0 functionality. It includes such subcommands:
2124 avb init - initialize avb2 subsystem
2125 avb read_rb - read rollback index
2126 avb write_rb - write rollback index
2127 avb is_unlocked - check device lock state
2128 avb get_uuid - read and print uuid of a partition
2129 avb read_part - read data from partition
2130 avb read_part_hex - read data from partition and output to stdout
2131 avb write_part - write data to partition
2132 avb verify - run full verification chain
2136 tristate "Enable UBI - Unsorted block images commands"
2139 UBI is a software layer above MTD layer which admits use of LVM-like
2140 logical volumes on top of MTD devices, hides some complexities of
2141 flash chips like wear and bad blocks and provides some other useful
2142 capabilities. Please, consult the MTD web site for more details
2143 (www.linux-mtd.infradead.org). Activate this option if you want
2144 to use U-Boot UBI commands.
2145 It is also strongly encouraged to also enable CONFIG_MTD to get full
2149 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2151 default y if CMD_UBI
2154 UBIFS is a file system for flash devices which works on top of UBI.
projects / J-u-boot.git / blob