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.
263 bool "Support booting UEFI FIT images"
264 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
267 Support booting UEFI FIT images via the bootm command.
272 Boot the Linux zImage
276 depends on ARM64 || RISCV
279 Boot an AArch64 Linux Kernel image from memory.
282 bool "Support booting Linux OS images"
283 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
286 Support booting the Linux kernel directly via a command such as bootm
290 bool "Support booting NetBSD (non-EFI) loader images"
294 Support booting NetBSD via the bootm command.
296 config BOOTM_OPENRTOS
297 bool "Support booting OPENRTOS / FreeRTOS images"
300 Support booting OPENRTOS / FreeRTOS via the bootm command.
303 bool "Support booting Enea OSE images"
306 Support booting Enea OSE images via the bootm command.
309 bool "Support booting Plan9 OS images"
313 Support booting Plan9 images via the bootm command.
316 bool "Support booting RTEMS OS images"
320 Support booting RTEMS images via the bootm command.
323 bool "Support booting VxWorks OS images"
327 Support booting VxWorks images via the bootm command.
331 depends on EFI_LOADER
334 Boot an EFI image from memory.
336 config CMD_BOOTEFI_HELLO_COMPILE
337 bool "Compile a standard EFI hello world binary for testing"
338 depends on CMD_BOOTEFI && !CPU_V7M
341 This compiles a standard EFI hello world application with U-Boot so
342 that it can be used with the test/py testing framework. This is useful
343 for testing that EFI is working at a basic level, and for bringing
344 up EFI support on a new architecture.
346 No additional space will be required in the resulting U-Boot binary
347 when this option is enabled.
349 config CMD_BOOTEFI_HELLO
350 bool "Allow booting a standard EFI hello world for testing"
351 depends on CMD_BOOTEFI_HELLO_COMPILE
353 This adds a standard EFI hello world application to U-Boot so that
354 it can be used with the 'bootefi hello' command. This is useful
355 for testing that EFI is working at a basic level, and for bringing
356 up EFI support on a new architecture.
358 source lib/efi_selftest/Kconfig
364 Add an ANSI terminal boot menu command.
369 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
370 image into RAM, dump image structure information, etc. Those dtb/dtbo
371 files should be merged in one dtb further, which needs to be passed to
372 the kernel, as part of a boot process.
375 bool "bootelf, bootvx"
378 Boot an ELF/vxWorks image from the memory.
381 bool "Flattened Device Tree utility commands"
385 Do FDT related setup before booting into the Operating System.
391 Start an application at a given address.
397 Run the command in the given environment variable.
403 Print header information for application image.
408 List all images found in flash
414 Extract a part of a multi-image.
417 bool "spl export - Export boot information for Falcon boot"
420 Falcon mode allows booting directly from SPL into an Operating
421 System such as Linux, thus skipping U-Boot proper. See
422 doc/README.falcon for full information about how to use this
425 config CMD_SPL_NAND_OFS
426 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
427 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
430 This provides the offset of the command line arguments for Linux
431 when booting from NAND in Falcon mode. See doc/README.falcon
432 for full information about how to use this option (and also see
433 board/gateworks/gw_ventana/README for an example).
435 config CMD_SPL_NOR_OFS
436 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
437 depends on CMD_SPL && SPL_NOR_SUPPORT
440 This provides the offset of the command line arguments or dtb for
441 Linux when booting from NOR in Falcon mode.
443 config CMD_SPL_WRITE_SIZE
444 hex "Size of argument area"
448 This provides the size of the command-line argument area in NAND
449 flash used by Falcon-mode boot. See the documentation until CMD_SPL
453 bool "fitImage update command"
455 Implements the 'fitupd' command, which allows to automatically
456 store software updates present on a TFTP server in NOR Flash
458 config CMD_THOR_DOWNLOAD
459 bool "thor - TIZEN 'thor' download"
462 Implements the 'thor' download protocol. This is a way of
463 downloading a software update over USB from an attached host.
464 There is no documentation about this within the U-Boot source code
465 but you should be able to find something on the interwebs.
468 bool "zboot - x86 boot command"
470 With x86 machines it is common to boot a bzImage file which
471 contains both a kernel and a setup.bin file. The latter includes
472 configuration information from the dark ages which x86 boards still
473 need to pick things out of.
475 Consider using FIT in preference to this since it supports directly
476 booting both 32- and 64-bit kernels, as well as secure boot.
477 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
481 menu "Environment commands"
484 bool "ask for env variable"
486 Ask for environment variable
504 Edit environment variable.
509 Allow for searching environment variables
515 Save all environment variables into the compiled-in persistent
521 depends on CMD_SAVEENV
523 Erase environment variables from the compiled-in persistent
526 config CMD_ENV_EXISTS
530 Check if a variable is defined in the environment for use in
533 config CMD_ENV_CALLBACK
534 bool "env callbacks - print callbacks and their associated variables"
536 Some environment variable have callbacks defined by
537 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
538 For example changing "baudrate" adjust the serial baud rate. This
539 command lists the currently defined callbacks.
542 bool "env flags -print variables that have non-default flags"
544 Some environment variables have special flags that control their
545 behaviour. For example, serial# can only be written once and cannot
546 be deleted. This command shows the variables that have special
549 config CMD_NVEDIT_EFI
550 bool "env [set|print] -e - set/print UEFI variables"
551 depends on EFI_LOADER
554 UEFI variables are encoded as some form of U-Boot variables.
555 If enabled, we are allowed to set/print UEFI variables using
556 "env" command with "-e" option without knowing details.
558 config CMD_NVEDIT_INFO
559 bool "env info - print or evaluate environment information"
561 Print environment information:
562 - env_valid : is environment valid
563 - env_ready : is environment imported into hash table
564 - env_use_default : is default environment used
566 This command can be optionally used for evaluation in scripts:
567 [-d] : evaluate whether default environment is used
568 [-p] : evaluate whether environment can be persisted
569 The result of multiple evaluations will be combined with AND.
573 menu "Memory commands"
578 Compute binary operations (xor, or, and) of byte arrays of arbitrary
579 size from memory and store the result in memory or the environment.
592 Add -v option to verify data against a crc32 checksum.
595 bool "eeprom - EEPROM subsystem"
597 (deprecated, needs conversion to driver model)
598 Provides commands to read and write EEPROM (Electrically Erasable
599 Programmable Read Only Memory) chips that are connected over an
602 config CMD_EEPROM_LAYOUT
603 bool "Enable layout-aware eeprom commands"
604 depends on CMD_EEPROM
606 (deprecated, needs conversion to driver model)
607 When enabled, additional eeprom sub-commands become available.
609 eeprom print - prints the contents of the eeprom in a human-readable
610 way (eeprom layout fields, and data formatted to be fit for human
613 eeprom update - allows user to update eeprom fields by specifying
614 the field name, and providing the new data in a human readable format
615 (same format as displayed by the eeprom print command).
617 Both commands can either auto detect the layout, or be told which
621 __weak int parse_layout_version(char *str)
622 - override to provide your own layout name parsing
623 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
625 - override to setup the layout metadata based on the version
626 __weak int eeprom_layout_detect(unsigned char *data)
627 - override to provide your own algorithm for detecting layout
630 - contains various printing and updating functions for common
631 types of eeprom fields. Can be used for defining
634 config EEPROM_LAYOUT_HELP_STRING
635 string "Tells user what layout names are supported"
636 depends on CMD_EEPROM_LAYOUT
637 default "<not defined>"
639 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
645 Infinite write loop on address range
652 Compute MD5 checksum.
657 depends on CMD_MD5SUM
659 Add -v option to verify data against an MD5 checksum.
664 Display memory information.
667 bool "md, mm, nm, mw, cp, cmp, base, loop"
672 mm - memory modify (auto-incrementing address)
673 nm - memory modify (constant address)
674 mw - memory write (fill)
677 base - print or set address offset
678 loop - initialize loop on address range
681 bool "Enable cyclic md/mw commands"
682 depends on CMD_MEMORY
684 Add the "mdc" and "mwc" memory commands. These are cyclic
689 This command will print 4 bytes (10,11,12,13) each 500 ms.
691 => mwc.l 100 12345678 10
692 This command will write 12345678 to address 100 all 10 ms.
697 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
699 random - fill memory with random data
704 Simple RAM read/write test.
708 config SYS_ALT_MEMTEST
709 bool "Alternative test"
711 Use a more complete alternative memory test.
718 mdc - memory display cyclic
719 mwc - memory write cyclic
725 Compute SHA1 checksum.
727 config SHA1SUM_VERIFY
729 depends on CMD_SHA1SUM
731 Add -v option to verify data against a SHA1 checksum.
734 bool "strings - display strings in memory"
736 This works similarly to the Unix 'strings' command except that it
737 works with a memory range. String of printable characters found
738 within the range are displayed. The minimum number of characters
739 for a sequence to be considered a string can be provided.
743 menu "Compression commands"
747 default y if CMD_BOOTI
750 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
755 default y if CMD_BOOTI
757 Uncompress a zip-compressed memory region.
762 Compress a memory region with zlib deflate method.
766 menu "Device access commands"
769 #depends on FLASH_CFI_DRIVER
772 ARM Ltd reference designs flash partition access
775 bool "adc - Access Analog to Digital Converters info and data"
779 Shows ADC device info and permit printing one-shot analog converted
780 data from a named Analog to Digital Converter.
785 depends on PARTITIONS
787 Read/modify/write the fields of Bootloader Control Block, usually
788 stored on the flash "misc" partition with its structure defined in:
789 https://android.googlesource.com/platform/bootable/recovery/+/master/
790 bootloader_message/include/bootloader_message/bootloader_message.h
792 Some real-life use-cases include (but are not limited to):
793 - Determine the "boot reason" (and act accordingly):
794 https://source.android.com/devices/bootloader/boot-reason
795 - Get/pass a list of commands from/to recovery:
796 https://android.googlesource.com/platform/bootable/recovery
797 - Inspect/dump the contents of the BCB fields
800 bool "bind/unbind - Bind or unbind a device to/from a driver"
803 Bind or unbind a device to/from a driver from the command line.
804 This is useful in situations where a device may be handled by several
805 drivers. For example, this can be used to bind a UDC to the usb ether
806 gadget driver from the command line.
809 bool "clk - Show clock frequencies"
812 Shows clock frequences by calling a sock_clk_dump() hook function.
813 This is depreated in favour of using the CLK uclass and accessing
814 clock values from associated drivers. However currently no command
818 bool "demo - Demonstration commands for driver model"
821 Provides a 'demo' command which can be used to play around with
822 driver model. To use this properly you will need to enable one or
823 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
824 Otherwise you will always get an empty list of devices. The demo
825 devices are defined in the sandbox device tree, so the easiest
826 option is to use sandbox and pass the -d point to sandbox's
833 Enables the command "dfu" which is used to have U-Boot create a DFU
834 class device via USB. This command requires that the "dfu_alt_info"
835 environment variable be set and define the alt settings to expose to
839 bool "dm - Access to driver model information"
842 Provides access to driver model data structures and information,
843 such as a list of devices, list of uclasses and the state of each
844 device (e.g. activated). This is not required for operation, but
845 can be useful to see the state of driver model for debugging or
849 bool "fastboot - Android fastboot support"
852 This enables the command "fastboot" which enables the Android
853 fastboot mode for the platform. Fastboot is a protocol for
854 downloading images, flashing and device control used on
855 Android devices. Fastboot requires either the network stack
856 enabled or support for acting as a USB device.
858 See doc/android/fastboot.txt for more information.
861 bool "fdcboot - Boot from floppy device"
863 The 'fdtboot' command allows booting an image from a floppy disk.
866 bool "flinfo, erase, protect"
868 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
871 flinfo - print FLASH memory information
873 protect - enable or disable FLASH write protection
882 config CMD_FPGA_LOADBP
883 bool "fpga loadbp - load partial bitstream (Xilinx only)"
886 Supports loading an FPGA device from a bitstream buffer containing
889 config CMD_FPGA_LOADFS
890 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
893 Supports loading an FPGA device from a FAT filesystem.
895 config CMD_FPGA_LOADMK
896 bool "fpga loadmk - load bitstream from image"
899 Supports loading an FPGA device from a image generated by mkimage.
901 config CMD_FPGA_LOADP
902 bool "fpga loadp - load partial bitstream"
905 Supports loading an FPGA device from a bitstream buffer containing
908 config CMD_FPGA_LOAD_SECURE
909 bool "fpga loads - loads secure bitstreams (Xilinx only)"
912 Enables the fpga loads command which is used to load secure
913 (authenticated or encrypted or both) bitstreams on to FPGA.
916 bool "fpgad - dump FPGA registers"
918 (legacy, needs conversion to driver model)
919 Provides a way to dump FPGA registers by calling the board-specific
920 fpga_get_reg() function. This functions similarly to the 'md'
924 bool "fuse - support for the fuse subssystem"
926 (deprecated - needs conversion to driver model)
927 This allows reading, sensing, programming or overriding fuses
928 which control the behaviour of the device. The command uses the
937 bool "GPT (GUID Partition Table) command"
939 select HAVE_BLOCK_DEVICE
940 select PARTITION_UUIDS
943 Enable the 'gpt' command to ready and write GPT style partition
947 bool "GPT Random UUID generation"
950 Enable the generation of partitions with random UUIDs if none
953 config CMD_GPT_RENAME
954 bool "GPT partition renaming commands"
957 Enables the 'gpt' command to interchange names on two GPT
958 partitions via the 'gpt swap' command or to rename single
959 partitions via the 'rename' command.
962 bool "ide - Support for IDE drivers"
965 Provides an 'ide' command which allows accessing the IDE drive,
966 reseting the IDE interface, printing the partition table and
967 geting device info. It also enables the 'diskboot' command which
968 permits booting from an IDE drive.
971 bool "io - Support for performing I/O accesses"
973 Provides an 'iod' command to display I/O space and an 'iow' command
974 to write values to the I/O space. This can be useful for manually
975 checking the state of devices during boot when debugging device
979 bool "iotrace - Support for tracing I/O activity"
981 Provides an 'iotrace' command which supports recording I/O reads and
982 writes in a trace buffer in memory . It also maintains a checksum
983 of the trace records (even if space is exhausted) so that the
984 sequence of I/O accesses can be verified.
986 When debugging drivers it is useful to see what I/O accesses were
987 done and in what order.
989 Even if the individual accesses are of little interest it can be
990 useful to verify that the access pattern is consistent each time
991 an operation is performed. In this case a checksum can be used to
992 characterise the operation of a driver. The checksum can be compared
993 across different runs of the operation to verify that the driver is
996 In particular, when performing major refactoring of the driver, where
997 the access pattern should not change, the checksum provides assurance
998 that the refactoring work has not broken the driver.
1000 This works by sneaking into the io.h heder for an architecture and
1001 redirecting I/O accesses through iotrace's tracing mechanism.
1003 For now no commands are provided to examine the trace buffer. The
1004 format is fairly simple, so 'md' is a reasonable substitute.
1006 Note: The checksum feature is only useful for I/O regions where the
1007 contents do not change outside of software control. Where this is not
1008 suitable you can fall back to manually comparing the addresses. It
1009 might be useful to enhance tracing to only checksum the accesses and
1010 not the data read/written.
1020 bool "w1 - Support for Dallas 1-Wire protocol"
1022 Dallas 1-wire protocol support
1028 Load a binary file over serial line.
1034 Load an S-Record file over serial line
1039 MMC memory mapped support.
1042 bool "Enable support for RPMB in the mmc command"
1045 Enable the commands for reading, writing and programming the
1046 key for the Replay Protection Memory Block partition in eMMC.
1048 config CMD_MMC_SWRITE
1050 depends on CMD_MMC && MMC_WRITE
1053 Enable support for the "mmc swrite" command to write Android sparse
1059 select MTD_PARTITIONS
1061 MTD commands support.
1065 default y if NAND_SUNXI
1066 depends on MTD_RAW_NAND
1071 config CMD_NAND_TRIMFFS
1072 bool "nand write.trimffs"
1073 default y if ARCH_SUNXI
1075 Allows one to skip empty pages when flashing something on a NAND.
1077 config CMD_NAND_LOCK_UNLOCK
1078 bool "nand lock/unlock"
1080 NAND locking support.
1082 config CMD_NAND_TORTURE
1085 NAND torture support.
1094 NVM Express device support
1097 bool "onenand - access to onenand device"
1100 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1101 various useful features. This command allows reading, writing,
1102 and erasing blocks. It allso provides a way to show and change
1103 bad blocks, and test the device.
1108 Enable the 'osd' command which allows to query information from and
1109 write text data to a on-screen display (OSD) device; a virtual device
1110 associated with a display capable of displaying a text overlay on the
1111 display it's associated with..
1115 select HAVE_BLOCK_DEVICE
1116 select PARTITION_UUIDS
1118 Read and display information about the partition table on
1122 bool "pci - Access PCI devices"
1124 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1125 used on some devices to allow the CPU to communicate with its
1126 peripherals. Sub-commands allow bus enumeration, displaying and
1127 changing configuration space and a few other features.
1130 bool "pinmux - show pins muxing"
1131 default y if PINCTRL
1133 Parse all available pin-controllers and show pins muxing. This
1134 is useful for debug purpoer to check the pin muxing and to know if
1135 a pin is configured as a GPIO or as an alternate function.
1140 Poweroff/Shutdown the system
1143 bool "read - Read binary data from a partition"
1145 Provides low-level access to the data in a partition.
1147 config CMD_REMOTEPROC
1149 depends on REMOTEPROC
1151 Support for Remote Processor control
1154 bool "sata - Access SATA subsystem"
1157 SATA (Serial Advanced Technology Attachment) is a serial bus
1158 standard for connecting to hard drives and other storage devices.
1159 This command provides information about attached devices and allows
1160 reading, writing and other operations.
1162 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1163 Attachment, where AT refers to an IBM AT (Advanced Technology)
1164 computer released in 1984.
1167 bool "saves - Save a file over serial in S-Record format"
1169 Provides a way to save a binary file using the Motorola S-Record
1170 format over the serial line.
1173 bool "scsi - Access to SCSI devices"
1176 This provides a 'scsi' command which provides access to SCSI (Small
1177 Computer System Interface) devices. The command provides a way to
1178 scan the bus, reset the bus, read and write data and get information
1182 bool "sdram - Print SDRAM configuration information"
1184 Provides information about attached SDRAM. This assumed that the
1185 SDRAM has an EEPROM with information that can be read using the
1186 I2C bus. This is only available on some boards.
1190 depends on DM_SPI_FLASH || SPI_FLASH
1191 default y if DM_SPI_FLASH
1196 bool "sf test - Allow testing of SPI flash"
1199 Provides a way to test that SPI flash is working correctly. The
1200 test is destructive, in that an area of SPI flash must be provided
1201 for the test to use. Performance information is also provided,
1202 measuring the performance of reading, writing and erasing in
1203 Mbps (Million Bits Per Second). This value should approximately
1204 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1205 everything is working properly.
1208 bool "sspi - Command to access spi device"
1211 SPI utility command.
1213 config DEFAULT_SPI_BUS
1214 int "default spi bus used by sspi command"
1218 config DEFAULT_SPI_MODE
1219 hex "default spi mode used by sspi command (see include/spi.h)"
1224 bool "tsi148 - Command to access tsi148 device"
1226 This provides various sub-commands to initialise and configure the
1227 Turndra tsi148 device. See the command help for full details.
1230 bool "Enable UFS - Universal Flash Subsystem commands"
1233 "This provides commands to initialise and configure universal flash
1237 bool "universe - Command to set up the Turndra Universe controller"
1239 This allows setting up the VMEbus provided by this controller.
1240 See the command help for full details.
1244 select HAVE_BLOCK_DEVICE
1250 select USB_FUNCTION_SDP
1252 Enables the command "sdp" which is used to have U-Boot emulating the
1253 Serial Download Protocol (SDP) via USB.
1257 depends on USB_FUNCTION_ROCKUSB
1259 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1260 read/write info, image to/from devices. This enable rockusb command
1261 support to communication with rockusb device. for more detail about
1262 this command, please read doc/README.rockusb.
1264 config CMD_USB_MASS_STORAGE
1265 bool "UMS usb mass storage"
1266 select USB_FUNCTION_MASS_STORAGE
1268 USB mass storage support
1275 VirtIO block device support
1281 This provides commands to control the watchdog timer devices.
1287 Enable the command "axi" for accessing AXI (Advanced eXtensible
1288 Interface) busses, a on-chip interconnect specification for managing
1289 functional blocks in SoC designs, which is also often used in designs
1290 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1294 menu "Shell scripting commands"
1300 Echo args to console
1306 Return true/false on integer compare.
1312 Run script from memory
1318 Evaluate boolean and math expressions and store the result in an env
1320 Also supports loading the value at a memory location into a variable.
1321 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1325 menu "Android support commands"
1327 config CMD_AB_SELECT
1330 depends on ANDROID_AB
1332 On Android devices with more than one boot slot (multiple copies of
1333 the kernel and system images) this provides a command to select which
1334 slot should be used to boot from and register the boot attempt. This
1335 is used by the new A/B update model where one slot is updated in the
1336 background while running from the other slot.
1343 bool "Network commands"
1353 bootp - boot image via network using BOOTP/TFTP protocol
1357 depends on CMD_BOOTP
1359 Boot image via network using DHCP/TFTP protocol
1361 config BOOTP_BOOTPATH
1362 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1364 depends on CMD_BOOTP
1366 Even though the config is called BOOTP_BOOTPATH, it stores the
1367 path in the variable 'rootpath'.
1370 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1372 depends on CMD_BOOTP
1374 The primary DNS server is stored as 'dnsip'. If two servers are
1375 returned, you must set BOOTP_DNS2 to store that second server IP
1379 bool "Store 'dnsip2' from BOOTP/DHCP server"
1380 depends on BOOTP_DNS
1382 If a DHCP client requests the DNS server IP from a DHCP server,
1383 it is possible that more than one DNS serverip is offered to the
1384 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1385 server IP will be stored in the additional environment
1386 variable "dnsip2". The first DNS serverip is always
1387 stored in the variable "dnsip", when BOOTP_DNS is defined.
1389 config BOOTP_GATEWAY
1390 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1392 depends on CMD_BOOTP
1394 config BOOTP_HOSTNAME
1395 bool "Request & store 'hostname' from BOOTP/DHCP server"
1397 depends on CMD_BOOTP
1399 The name may or may not be qualified with the local domain name.
1401 config BOOTP_PREFER_SERVERIP
1402 bool "serverip variable takes precedent over DHCP server IP."
1403 depends on CMD_BOOTP
1405 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1407 With this option enabled, the 'serverip' variable in the environment
1408 takes precedence over DHCP server IP and will only be set by the DHCP
1409 server if not already set in the environment.
1411 config BOOTP_SUBNETMASK
1412 bool "Request & store 'netmask' from BOOTP/DHCP server"
1414 depends on CMD_BOOTP
1416 config BOOTP_NTPSERVER
1417 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1418 depends on CMD_BOOTP
1423 Selecting this will allow capturing all Ethernet packets and store
1424 them in physical memory in a PCAP formated file,
1425 later to be analyzed by PCAP reader application (IE. WireShark).
1428 bool "Send PXE client arch to BOOTP/DHCP server"
1430 depends on CMD_BOOTP && CMD_PXE
1432 Supported for ARM, ARM64, and x86 for now.
1434 config BOOTP_PXE_CLIENTARCH
1436 depends on BOOTP_PXE
1437 default 0x16 if ARM64
1441 config BOOTP_VCI_STRING
1443 depends on CMD_BOOTP
1444 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1445 default "U-Boot.armv8" if ARM64
1446 default "U-Boot.arm" if ARM
1453 tftpboot - boot image via network using TFTP protocol
1457 depends on CMD_TFTPBOOT
1459 TFTP put command, for uploading files to a server
1463 depends on CMD_TFTPBOOT
1465 Act as a TFTP server and boot the first received file
1467 config NET_TFTP_VARS
1468 bool "Control TFTP timeout and count through environment"
1469 depends on CMD_TFTPBOOT
1472 If set, allows controlling the TFTP timeout through the
1473 environment variable tftptimeout, and the TFTP maximum
1474 timeout count through the variable tftptimeoutcountmax.
1475 If unset, timeout and maximum are hard-defined as 1 second
1476 and 10 timouts per TFTP transfer.
1481 Boot image via network using RARP/TFTP protocol
1487 Boot image via network using NFS protocol.
1493 If set, allows 802.3(clause 22) MII Management functions interface access
1494 The management interface specified in Clause 22 provides
1495 a simple, two signal, serial interface to connect a
1496 Station Management entity and a managed PHY for providing access
1497 to management parameters and services.
1498 The interface is referred to as the MII management interface.
1504 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1505 The MDIO interface is orthogonal to the MII interface and extends
1506 it by adding access to more registers through indirect addressing.
1511 Send ICMP ECHO_REQUEST to network host
1516 Perform CDP network configuration
1521 Synchronize RTC via network
1526 Lookup the IP of a hostname
1528 config CMD_LINK_LOCAL
1532 Acquire a network IP address using the link-local protocol
1539 Allow control of L2 Ethernet switch commands. These are supported
1540 by the vsc9953 Ethernet driver at present. Sub-commands allow
1541 operations such as enabling / disabling a port and
1542 viewing/maintaining the filtering database (FDB)
1548 Boot image via network using PXE protocol
1553 Wait for wake-on-lan Magic Packet
1557 menu "Misc commands"
1560 bool "Enable 'bmp' command"
1561 depends on LCD || DM_VIDEO || VIDEO
1563 This provides a way to obtain information about a BMP-format image
1564 and to display it. BMP (which presumably stands for BitMaP) is a
1565 file format defined by Microsoft which supports images of various
1566 depths, formats and compression methods. Headers on the file
1567 determine the formats used. This command can be used by first loading
1568 the image into RAM, then using this command to look at it or display
1571 config CMD_BOOTCOUNT
1573 depends on BOOTCOUNT_LIMIT
1575 Enable the bootcount command, which allows interrogation and
1576 reset of the bootcounter.
1579 bool "Enable board-specific commands"
1581 (deprecated: instead, please define a Kconfig option for each command)
1583 Some boards have board-specific commands which are only enabled
1584 during developemnt and need to be turned off for production. This
1585 option provides a way to control this. The commands that are enabled
1586 vary depending on the board.
1588 config CMD_BKOPS_ENABLE
1589 bool "mmc bkops enable"
1593 Enable command for setting manual background operations handshake
1594 on a eMMC device. The feature is optionally available on eMMC devices
1595 conforming to standard >= 4.41.
1597 config CMD_BLOCK_CACHE
1598 bool "blkcache - control and stats for block cache"
1599 depends on BLOCK_CACHE
1600 default y if BLOCK_CACHE
1602 Enable the blkcache command, which can be used to control the
1603 operation of the cache functions.
1604 This is most useful when fine-tuning the operation of the cache
1605 during development, but also allows the cache to be disabled when
1606 it might hurt performance (e.g. when using the ums command).
1609 bool "icache or dcache"
1611 Enable the "icache" and "dcache" commands
1613 config CMD_CONITRACE
1614 bool "conitrace - trace console input codes"
1616 Enable the 'conitrace' command which displays the codes received
1617 from the console input as hexadecimal numbers.
1620 bool "Enable clear screen command 'cls'"
1621 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1624 Enable the 'cls' command which clears the screen contents
1625 on video frame buffer.
1628 bool "efidebug - display/configure UEFI environment"
1629 depends on EFI_LOADER
1630 select EFI_DEVICE_PATH_TO_TEXT
1633 Enable the 'efidebug' command which provides a subset of UEFI
1634 shell utility with simplified functionality. It will be useful
1635 particularly for managing boot parameters as well as examining
1636 various EFI status for debugging.
1638 config CMD_EXCEPTION
1639 bool "exception - raise exception"
1640 depends on ARM || RISCV || X86
1642 Enable the 'exception' command which allows to raise an exception.
1649 Enable the 'led' command which allows for control of LEDs supported
1650 by the board. The LEDs can be listed with 'led list' and controlled
1651 with led on/off/togle/blink. Any LED drivers can be controlled with
1652 this command, e.g. led_gpio.
1659 Enable the 'date' command for getting/setting the time/date in RTC
1665 Run commands and summarize execution time.
1668 bool "gettime - read elapsed time"
1670 Enable the 'gettime' command which reads the elapsed time since
1671 U-Boot started running. This shows the time in seconds and
1672 milliseconds. See also the 'bootstage' command which provides more
1673 flexibility for boot timing.
1680 Print bytes from the hardware random number generator.
1682 # TODO: rename to CMD_SLEEP
1687 Delay execution for some time
1690 bool "support for multiprocessor"
1692 This provides an option to brinup
1693 different processors in multiprocessor
1699 Access the system timer.
1705 This provides basic access to the U-Boot's sound support. The main
1706 feature is to play a beep.
1708 sound init - set up sound system
1709 sound play - play a sound
1715 Boot image via local extlinux.conf file
1721 This provides access to the QEMU firmware interface. The main
1722 feature is to allow easy loading of files passed to qemu-system
1723 via -kernel / -initrd
1725 source "cmd/mvebu/Kconfig"
1728 bool "terminal - provides a way to attach a serial terminal"
1730 Provides a 'cu'-like serial terminal command. This can be used to
1731 access other serial ports from the system console. The terminal
1732 is very simple with no special processing of characters. As with
1733 cu, you can press ~. (tilde followed by period) to exit.
1736 bool "uuid, guid - generation of unique IDs"
1739 This enables two commands:
1741 uuid - generate random Universally Unique Identifier
1742 guid - generate Globally Unique Identifier based on random UUID
1744 The two commands are very similar except for the endianness of the
1749 source "cmd/ti/Kconfig"
1751 config CMD_BOOTSTAGE
1752 bool "Enable the 'bootstage' command"
1753 depends on BOOTSTAGE
1755 Add a 'bootstage' command which supports printing a report
1756 and un/stashing of bootstage data.
1758 menu "Power commands"
1760 bool "Enable Driver Model PMIC command"
1763 This is the pmic command, based on a driver model pmic's API.
1764 Command features are unchanged:
1765 - list - list pmic devices
1766 - pmic dev <id> - show or [set] operating pmic device (NEW)
1767 - pmic dump - dump registers
1768 - pmic read address - read byte of register at address
1769 - pmic write address - write byte to register at address
1770 The only one change for this command is 'dev' subcommand.
1772 config CMD_REGULATOR
1773 bool "Enable Driver Model REGULATOR command"
1774 depends on DM_REGULATOR
1776 This command is based on driver model regulator's API.
1777 User interface features:
1778 - list - list regulator devices
1779 - regulator dev <id> - show or [set] operating regulator device
1780 - regulator info - print constraints info
1781 - regulator status - print operating status
1782 - regulator value <val] <-f> - print/[set] voltage value [uV]
1783 - regulator current <val> - print/[set] current value [uA]
1784 - regulator mode <id> - print/[set] operating mode id
1785 - regulator enable - enable the regulator output
1786 - regulator disable - disable the regulator output
1788 The '-f' (force) option can be used for set the value which exceeds
1789 the limits, which are found in device-tree and are kept in regulator's
1790 uclass platdata structure.
1794 menu "Security commands"
1796 bool "Enable the 'aes' command"
1799 This provides a means to encrypt and decrypt data using the AES
1800 (Advanced Encryption Standard). This algorithm uses a symetric key
1801 and is widely used as a streaming cipher. Different key lengths are
1802 supported by the algorithm but this command only supports 128 bits
1806 bool "Enable the 'blob' command"
1808 This is used with the Freescale secure boot mechanism.
1810 Freescale's SEC block has built-in Blob Protocol which provides
1811 a method for protecting user-defined data across system power
1812 cycles. SEC block protects data in a data structure called a Blob,
1813 which provides both confidentiality and integrity protection.
1815 Encapsulating data as a blob
1816 Each time that the Blob Protocol is used to protect data, a
1817 different randomly generated key is used to encrypt the data.
1818 This random key is itself encrypted using a key which is derived
1819 from SoC's non-volatile secret key and a 16 bit Key identifier.
1820 The resulting encrypted key along with encrypted data is called a
1821 blob. The non-volatile secure key is available for use only during
1824 During decapsulation, the reverse process is performed to get back
1828 blob enc - encapsulating data as a cryptgraphic blob
1829 blob dec - decapsulating cryptgraphic blob to get the data
1833 blob enc src dst len km
1835 Encapsulate and create blob of data $len bytes long
1836 at address $src and store the result at address $dst.
1837 $km is the 16 byte key modifier is also required for
1838 generation/use as key for cryptographic operation. Key
1839 modifier should be 16 byte long.
1841 blob dec src dst len km
1843 Decapsulate the blob of data at address $src and
1844 store result of $len byte at addr $dst.
1845 $km is the 16 byte key modifier is also required for
1846 generation/use as key for cryptographic operation. Key
1847 modifier should be 16 byte long.
1850 bool "Support 'hash' command"
1853 This provides a way to hash data in memory using various supported
1854 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1855 saved to memory or to an environment variable. It is also possible
1856 to verify a hash against data in memory.
1859 bool "Support the 'hvc' command"
1860 depends on ARM_SMCCC
1862 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1863 development and testing.
1866 bool "Support the 'smc' command"
1867 depends on ARM_SMCCC
1869 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1870 development and testing.
1876 Add -v option to verify data against a hash.
1886 bool "Enable the 'tpm' command"
1887 depends on TPM_V1 || TPM_V2
1888 select CMD_TPM_V1 if TPM_V1
1889 select CMD_TPM_V2 if TPM_V2
1891 This provides a means to talk to a TPM from the command line. A wide
1892 range of commands if provided - see 'tpm help' for details. The
1893 command requires a suitable TPM on your board and the correct driver
1899 bool "Enable the 'tpm test' command"
1902 This provides a a series of tests to confirm that the TPMv1.x is
1903 working correctly. The tests cover initialisation, non-volatile RAM,
1904 extend, global lock and checking that timing is within expectations.
1905 The tests pass correctly on Infineon TPMs but may need to be adjusted
1912 menu "Firmware commands"
1914 bool "Enable crosec command"
1918 Enable command-line access to the Chrome OS EC (Embedded
1919 Controller). This provides the 'crosec' command which has
1920 a number of sub-commands for performing EC tasks such as
1921 updating its flash, accessing a small saved context area
1922 and talking to the I2C bus behind the EC (if there is one).
1925 menu "Filesystem commands"
1927 bool "Enable the 'btrsubvol' command"
1930 This enables the 'btrsubvol' command to list subvolumes
1931 of a BTRFS filesystem. There are no special commands for
1932 listing BTRFS directories or loading BTRFS files - this
1933 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1934 when BTRFS is enabled (see FS_BTRFS).
1937 bool "Enable the 'cbfs' command"
1940 Define this to enable support for reading from a Coreboot
1941 filesystem. This is a ROM-based filesystem used for accessing files
1942 on systems that use coreboot as the first boot-loader and then load
1943 U-Boot to actually boot the Operating System. Available commands are
1944 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1947 bool "Enable the 'cramfs' command"
1948 depends on FS_CRAMFS
1950 This provides commands for dealing with CRAMFS (Compressed ROM
1951 filesystem). CRAMFS is useful when space is tight since files are
1952 compressed. Two commands are provided:
1954 cramfsls - lists files in a cramfs image
1955 cramfsload - loads a file from a cramfs image
1958 bool "ext2 command support"
1961 Enables EXT2 FS command
1964 bool "ext4 command support"
1967 Enables EXT4 FS command
1969 config CMD_EXT4_WRITE
1971 bool "ext4 write command support"
1974 Enables EXT4 FS write command
1977 bool "FAT command support"
1980 Support for the FAT fs
1982 config CMD_FS_GENERIC
1983 bool "filesystem commands"
1985 Enables filesystem commands (e.g. load, ls) that work for multiple
1989 bool "fsuuid command"
1991 Enables fsuuid command for filesystem UUID.
1994 bool "jffs2 command"
1997 Enables commands to support the JFFS2 (Journalling Flash File System
1998 version 2) filesystem. This enables fsload, ls and fsinfo which
1999 provide the ability to load files, list directories and obtain
2000 filesystem information.
2003 bool "MTD partition support"
2006 MTD partitioning tool support.
2007 It is strongly encouraged to avoid using this command
2008 anymore along with 'sf', 'nand', 'onenand'. One can still
2009 declare the partitions in the mtdparts environment variable
2010 but better use the MTD stack and the 'mtd' command instead.
2012 config CMD_MTDPARTS_SPREAD
2013 bool "Padd partition size to take account of bad blocks"
2014 depends on CMD_MTDPARTS
2016 This enables the 'spread' sub-command of the mtdparts command.
2017 This command will modify the existing mtdparts variable by increasing
2018 the size of the partitions such that 1) each partition's net size is
2019 at least as large as the size specified in the mtdparts variable and
2020 2) each partition starts on a good block.
2022 config CMD_MTDPARTS_SHOW_NET_SIZES
2023 bool "Show net size (w/o bad blocks) of partitions"
2024 depends on CMD_MTDPARTS
2026 Adds two columns to the printed partition table showing the
2027 effective usable size of a partition, if bad blocks are taken
2030 config MTDIDS_DEFAULT
2031 string "Default MTD IDs"
2032 depends on MTD || SPI_FLASH
2034 Defines a default MTD IDs list for use with MTD partitions in the
2035 Linux MTD command line partitions format.
2037 config MTDPARTS_DEFAULT
2038 string "Default MTD partition scheme"
2039 depends on MTD || SPI_FLASH
2041 Defines a default MTD partitioning scheme in the Linux MTD command
2042 line partitions format
2045 bool "reiser - Access to reiserfs filesystems"
2047 This provides two commands which operate on a resierfs filesystem,
2048 commonly used some years ago:
2050 reiserls - list files
2051 reiserload - load a file
2054 bool "yaffs2 - Access of YAFFS2 filesystem"
2058 This provides commands for accessing a YAFFS2 filesystem. Yet
2059 Another Flash Filesystem 2 is a filesystem designed specifically
2060 for NAND flash. It incorporates bad-block management and ensures
2061 that device writes are sequential regardless of filesystem
2065 bool "zfs - Access of ZFS filesystem"
2067 This provides commands to accessing a ZFS filesystem, commonly used
2068 on Solaris systems. Two sub-commands are provided:
2070 zfsls - list files in a directory
2071 zfsload - load a file
2073 See doc/README.zfs for more details.
2077 menu "Debug commands"
2082 The bedbug (emBEDded deBUGger) command provides debugging features
2083 for some PowerPC processors. For details please see the
2084 docuemntation in doc/README.beddbug
2087 bool "diag - Board diagnostics"
2089 This command provides access to board diagnostic tests. These are
2090 called Power-on Self Tests (POST). The command allows listing of
2091 available tests and running either all the tests, or specific tests
2095 bool "irq - Show information about interrupts"
2096 depends on !ARM && !MIPS && !SH
2098 This enables two commands:
2100 interrupts - enable or disable interrupts
2101 irqinfo - print device-specific interrupt information
2104 bool "kgdb - Allow debugging of U-Boot with gdb"
2107 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2108 over a serial link for debugging purposes. This allows
2109 single-stepping, inspecting variables, etc. This is supported only
2110 on PowerPC at present.
2113 bool "log - Generation, control and access to logging"
2116 This provides access to logging features. It allows the output of
2117 log data to be controlled to a limited extent (setting up the default
2118 maximum log level for emitting of records). It also provides access
2119 to a command used for testing the log system.
2122 bool "trace - Support tracing of function calls and timing"
2124 Enables a command to control using of function tracing within
2125 U-Boot. This allows recording of call traces including timing
2126 information. The command can write data to memory for exporting
2127 for analysis (e.g. using bootchart). See doc/README.trace for full
2131 bool "avb - Android Verified Boot 2.0 operations"
2132 depends on AVB_VERIFY
2135 Enables a "avb" command to perform verification of partitions using
2136 Android Verified Boot 2.0 functionality. It includes such subcommands:
2137 avb init - initialize avb2 subsystem
2138 avb read_rb - read rollback index
2139 avb write_rb - write rollback index
2140 avb is_unlocked - check device lock state
2141 avb get_uuid - read and print uuid of a partition
2142 avb read_part - read data from partition
2143 avb read_part_hex - read data from partition and output to stdout
2144 avb write_part - write data to partition
2145 avb verify - run full verification chain
2149 tristate "Enable UBI - Unsorted block images commands"
2152 UBI is a software layer above MTD layer which admits use of LVM-like
2153 logical volumes on top of MTD devices, hides some complexities of
2154 flash chips like wear and bad blocks and provides some other useful
2155 capabilities. Please, consult the MTD web site for more details
2156 (www.linux-mtd.infradead.org). Activate this option if you want
2157 to use U-Boot UBI commands.
2158 It is also strongly encouraged to also enable CONFIG_MTD to get full
2162 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2164 default y if CMD_UBI
2167 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob