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"
304 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
307 Support booting Enea OSE images via the bootm command.
310 bool "Support booting Plan9 OS images"
314 Support booting Plan9 images via the bootm command.
317 bool "Support booting RTEMS OS images"
321 Support booting RTEMS images via the bootm command.
324 bool "Support booting VxWorks OS images"
328 Support booting VxWorks images via the bootm command.
332 depends on EFI_LOADER
335 Boot an EFI image from memory.
337 config CMD_BOOTEFI_HELLO_COMPILE
338 bool "Compile a standard EFI hello world binary for testing"
339 depends on CMD_BOOTEFI && !CPU_V7M
342 This compiles a standard EFI hello world application with U-Boot so
343 that it can be used with the test/py testing framework. This is useful
344 for testing that EFI is working at a basic level, and for bringing
345 up EFI support on a new architecture.
347 No additional space will be required in the resulting U-Boot binary
348 when this option is enabled.
350 config CMD_BOOTEFI_HELLO
351 bool "Allow booting a standard EFI hello world for testing"
352 depends on CMD_BOOTEFI_HELLO_COMPILE
354 This adds a standard EFI hello world application to U-Boot so that
355 it can be used with the 'bootefi hello' command. This is useful
356 for testing that EFI is working at a basic level, and for bringing
357 up EFI support on a new architecture.
359 source lib/efi_selftest/Kconfig
365 Add an ANSI terminal boot menu command.
370 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
371 image into RAM, dump image structure information, etc. Those dtb/dtbo
372 files should be merged in one dtb further, which needs to be passed to
373 the kernel, as part of a boot process.
376 bool "bootelf, bootvx"
379 Boot an ELF/vxWorks image from the memory.
382 bool "Flattened Device Tree utility commands"
386 Do FDT related setup before booting into the Operating System.
392 Start an application at a given address.
398 Run the command in the given environment variable.
404 Print header information for application image.
409 List all images found in flash
415 Extract a part of a multi-image.
418 bool "spl export - Export boot information for Falcon boot"
421 Falcon mode allows booting directly from SPL into an Operating
422 System such as Linux, thus skipping U-Boot proper. See
423 doc/README.falcon for full information about how to use this
426 config CMD_SPL_NAND_OFS
427 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
428 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
431 This provides the offset of the command line arguments for Linux
432 when booting from NAND in Falcon mode. See doc/README.falcon
433 for full information about how to use this option (and also see
434 board/gateworks/gw_ventana/README for an example).
436 config CMD_SPL_NOR_OFS
437 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
438 depends on CMD_SPL && SPL_NOR_SUPPORT
441 This provides the offset of the command line arguments or dtb for
442 Linux when booting from NOR in Falcon mode.
444 config CMD_SPL_WRITE_SIZE
445 hex "Size of argument area"
449 This provides the size of the command-line argument area in NAND
450 flash used by Falcon-mode boot. See the documentation until CMD_SPL
454 bool "fitImage update command"
456 Implements the 'fitupd' command, which allows to automatically
457 store software updates present on a TFTP server in NOR Flash
459 config CMD_THOR_DOWNLOAD
460 bool "thor - TIZEN 'thor' download"
463 Implements the 'thor' download protocol. This is a way of
464 downloading a software update over USB from an attached host.
465 There is no documentation about this within the U-Boot source code
466 but you should be able to find something on the interwebs.
469 bool "zboot - x86 boot command"
471 With x86 machines it is common to boot a bzImage file which
472 contains both a kernel and a setup.bin file. The latter includes
473 configuration information from the dark ages which x86 boards still
474 need to pick things out of.
476 Consider using FIT in preference to this since it supports directly
477 booting both 32- and 64-bit kernels, as well as secure boot.
478 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
482 menu "Environment commands"
485 bool "ask for env variable"
487 Ask for environment variable
505 Edit environment variable.
510 Allow for searching environment variables
516 Save all environment variables into the compiled-in persistent
522 depends on CMD_SAVEENV
524 Erase environment variables from the compiled-in persistent
527 config CMD_ENV_EXISTS
531 Check if a variable is defined in the environment for use in
534 config CMD_ENV_CALLBACK
535 bool "env callbacks - print callbacks and their associated variables"
537 Some environment variable have callbacks defined by
538 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
539 For example changing "baudrate" adjust the serial baud rate. This
540 command lists the currently defined callbacks.
543 bool "env flags -print variables that have non-default flags"
545 Some environment variables have special flags that control their
546 behaviour. For example, serial# can only be written once and cannot
547 be deleted. This command shows the variables that have special
550 config CMD_NVEDIT_EFI
551 bool "env [set|print] -e - set/print UEFI variables"
552 depends on EFI_LOADER
555 UEFI variables are encoded as some form of U-Boot variables.
556 If enabled, we are allowed to set/print UEFI variables using
557 "env" command with "-e" option without knowing details.
559 config CMD_NVEDIT_INFO
560 bool "env info - print or evaluate environment information"
562 Print environment information:
563 - env_valid : is environment valid
564 - env_ready : is environment imported into hash table
565 - env_use_default : is default environment used
567 This command can be optionally used for evaluation in scripts:
568 [-d] : evaluate whether default environment is used
569 [-p] : evaluate whether environment can be persisted
570 The result of multiple evaluations will be combined with AND.
574 menu "Memory commands"
579 Compute binary operations (xor, or, and) of byte arrays of arbitrary
580 size from memory and store the result in memory or the environment.
593 Add -v option to verify data against a crc32 checksum.
596 bool "eeprom - EEPROM subsystem"
598 (deprecated, needs conversion to driver model)
599 Provides commands to read and write EEPROM (Electrically Erasable
600 Programmable Read Only Memory) chips that are connected over an
603 config CMD_EEPROM_LAYOUT
604 bool "Enable layout-aware eeprom commands"
605 depends on CMD_EEPROM
607 (deprecated, needs conversion to driver model)
608 When enabled, additional eeprom sub-commands become available.
610 eeprom print - prints the contents of the eeprom in a human-readable
611 way (eeprom layout fields, and data formatted to be fit for human
614 eeprom update - allows user to update eeprom fields by specifying
615 the field name, and providing the new data in a human readable format
616 (same format as displayed by the eeprom print command).
618 Both commands can either auto detect the layout, or be told which
622 __weak int parse_layout_version(char *str)
623 - override to provide your own layout name parsing
624 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
626 - override to setup the layout metadata based on the version
627 __weak int eeprom_layout_detect(unsigned char *data)
628 - override to provide your own algorithm for detecting layout
631 - contains various printing and updating functions for common
632 types of eeprom fields. Can be used for defining
635 config EEPROM_LAYOUT_HELP_STRING
636 string "Tells user what layout names are supported"
637 depends on CMD_EEPROM_LAYOUT
638 default "<not defined>"
640 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
646 Infinite write loop on address range
653 Compute MD5 checksum.
658 depends on CMD_MD5SUM
660 Add -v option to verify data against an MD5 checksum.
665 Display memory information.
668 bool "md, mm, nm, mw, cp, cmp, base, loop"
673 mm - memory modify (auto-incrementing address)
674 nm - memory modify (constant address)
675 mw - memory write (fill)
678 base - print or set address offset
679 loop - initialize loop on address range
682 bool "Enable cyclic md/mw commands"
683 depends on CMD_MEMORY
685 Add the "mdc" and "mwc" memory commands. These are cyclic
690 This command will print 4 bytes (10,11,12,13) each 500 ms.
692 => mwc.l 100 12345678 10
693 This command will write 12345678 to address 100 all 10 ms.
698 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
700 random - fill memory with random data
705 Simple RAM read/write test.
709 config SYS_ALT_MEMTEST
710 bool "Alternative test"
712 Use a more complete alternative memory test.
719 mdc - memory display cyclic
720 mwc - memory write cyclic
726 Compute SHA1 checksum.
728 config SHA1SUM_VERIFY
730 depends on CMD_SHA1SUM
732 Add -v option to verify data against a SHA1 checksum.
735 bool "strings - display strings in memory"
737 This works similarly to the Unix 'strings' command except that it
738 works with a memory range. String of printable characters found
739 within the range are displayed. The minimum number of characters
740 for a sequence to be considered a string can be provided.
744 menu "Compression commands"
748 default y if CMD_BOOTI
751 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
756 default y if CMD_BOOTI
758 Uncompress a zip-compressed memory region.
763 Compress a memory region with zlib deflate method.
767 menu "Device access commands"
770 #depends on FLASH_CFI_DRIVER
773 ARM Ltd reference designs flash partition access
776 bool "adc - Access Analog to Digital Converters info and data"
780 Shows ADC device info and permit printing one-shot analog converted
781 data from a named Analog to Digital Converter.
786 depends on PARTITIONS
788 Read/modify/write the fields of Bootloader Control Block, usually
789 stored on the flash "misc" partition with its structure defined in:
790 https://android.googlesource.com/platform/bootable/recovery/+/master/
791 bootloader_message/include/bootloader_message/bootloader_message.h
793 Some real-life use-cases include (but are not limited to):
794 - Determine the "boot reason" (and act accordingly):
795 https://source.android.com/devices/bootloader/boot-reason
796 - Get/pass a list of commands from/to recovery:
797 https://android.googlesource.com/platform/bootable/recovery
798 - Inspect/dump the contents of the BCB fields
801 bool "bind/unbind - Bind or unbind a device to/from a driver"
804 Bind or unbind a device to/from a driver from the command line.
805 This is useful in situations where a device may be handled by several
806 drivers. For example, this can be used to bind a UDC to the usb ether
807 gadget driver from the command line.
810 bool "clk - Show clock frequencies"
813 Shows clock frequences by calling a sock_clk_dump() hook function.
814 This is depreated in favour of using the CLK uclass and accessing
815 clock values from associated drivers. However currently no command
819 bool "demo - Demonstration commands for driver model"
822 Provides a 'demo' command which can be used to play around with
823 driver model. To use this properly you will need to enable one or
824 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
825 Otherwise you will always get an empty list of devices. The demo
826 devices are defined in the sandbox device tree, so the easiest
827 option is to use sandbox and pass the -d point to sandbox's
834 Enables the command "dfu" which is used to have U-Boot create a DFU
835 class device via USB. This command requires that the "dfu_alt_info"
836 environment variable be set and define the alt settings to expose to
840 bool "dm - Access to driver model information"
843 Provides access to driver model data structures and information,
844 such as a list of devices, list of uclasses and the state of each
845 device (e.g. activated). This is not required for operation, but
846 can be useful to see the state of driver model for debugging or
850 bool "fastboot - Android fastboot support"
853 This enables the command "fastboot" which enables the Android
854 fastboot mode for the platform. Fastboot is a protocol for
855 downloading images, flashing and device control used on
856 Android devices. Fastboot requires either the network stack
857 enabled or support for acting as a USB device.
859 See doc/android/fastboot.txt for more information.
862 bool "flinfo, erase, protect"
864 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
867 flinfo - print FLASH memory information
869 protect - enable or disable FLASH write protection
878 config CMD_FPGA_LOADBP
879 bool "fpga loadbp - load partial bitstream (Xilinx only)"
882 Supports loading an FPGA device from a bitstream buffer containing
885 config CMD_FPGA_LOADFS
886 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
889 Supports loading an FPGA device from a FAT filesystem.
891 config CMD_FPGA_LOADMK
892 bool "fpga loadmk - load bitstream from image"
895 Supports loading an FPGA device from a image generated by mkimage.
897 config CMD_FPGA_LOADP
898 bool "fpga loadp - load partial bitstream"
901 Supports loading an FPGA device from a bitstream buffer containing
904 config CMD_FPGA_LOAD_SECURE
905 bool "fpga loads - loads secure bitstreams (Xilinx only)"
908 Enables the fpga loads command which is used to load secure
909 (authenticated or encrypted or both) bitstreams on to FPGA.
912 bool "fpgad - dump FPGA registers"
914 (legacy, needs conversion to driver model)
915 Provides a way to dump FPGA registers by calling the board-specific
916 fpga_get_reg() function. This functions similarly to the 'md'
920 bool "fuse - support for the fuse subssystem"
922 (deprecated - needs conversion to driver model)
923 This allows reading, sensing, programming or overriding fuses
924 which control the behaviour of the device. The command uses the
933 bool "GPT (GUID Partition Table) command"
935 select HAVE_BLOCK_DEVICE
936 select PARTITION_UUIDS
939 Enable the 'gpt' command to ready and write GPT style partition
943 bool "GPT Random UUID generation"
946 Enable the generation of partitions with random UUIDs if none
949 config CMD_GPT_RENAME
950 bool "GPT partition renaming commands"
953 Enables the 'gpt' command to interchange names on two GPT
954 partitions via the 'gpt swap' command or to rename single
955 partitions via the 'rename' command.
958 bool "ide - Support for IDE drivers"
961 Provides an 'ide' command which allows accessing the IDE drive,
962 reseting the IDE interface, printing the partition table and
963 geting device info. It also enables the 'diskboot' command which
964 permits booting from an IDE drive.
967 bool "io - Support for performing I/O accesses"
969 Provides an 'iod' command to display I/O space and an 'iow' command
970 to write values to the I/O space. This can be useful for manually
971 checking the state of devices during boot when debugging device
975 bool "iotrace - Support for tracing I/O activity"
977 Provides an 'iotrace' command which supports recording I/O reads and
978 writes in a trace buffer in memory . It also maintains a checksum
979 of the trace records (even if space is exhausted) so that the
980 sequence of I/O accesses can be verified.
982 When debugging drivers it is useful to see what I/O accesses were
983 done and in what order.
985 Even if the individual accesses are of little interest it can be
986 useful to verify that the access pattern is consistent each time
987 an operation is performed. In this case a checksum can be used to
988 characterise the operation of a driver. The checksum can be compared
989 across different runs of the operation to verify that the driver is
992 In particular, when performing major refactoring of the driver, where
993 the access pattern should not change, the checksum provides assurance
994 that the refactoring work has not broken the driver.
996 This works by sneaking into the io.h heder for an architecture and
997 redirecting I/O accesses through iotrace's tracing mechanism.
999 For now no commands are provided to examine the trace buffer. The
1000 format is fairly simple, so 'md' is a reasonable substitute.
1002 Note: The checksum feature is only useful for I/O regions where the
1003 contents do not change outside of software control. Where this is not
1004 suitable you can fall back to manually comparing the addresses. It
1005 might be useful to enhance tracing to only checksum the accesses and
1006 not the data read/written.
1016 bool "w1 - Support for Dallas 1-Wire protocol"
1018 Dallas 1-wire protocol support
1024 Load a binary file over serial line.
1030 Load an S-Record file over serial line
1035 MMC memory mapped support.
1038 bool "Enable support for RPMB in the mmc command"
1041 Enable the commands for reading, writing and programming the
1042 key for the Replay Protection Memory Block partition in eMMC.
1044 config CMD_MMC_SWRITE
1046 depends on CMD_MMC && MMC_WRITE
1049 Enable support for the "mmc swrite" command to write Android sparse
1055 select MTD_PARTITIONS
1057 MTD commands support.
1061 default y if NAND_SUNXI
1062 depends on MTD_RAW_NAND
1067 config CMD_NAND_TRIMFFS
1068 bool "nand write.trimffs"
1069 default y if ARCH_SUNXI
1071 Allows one to skip empty pages when flashing something on a NAND.
1073 config CMD_NAND_LOCK_UNLOCK
1074 bool "nand lock/unlock"
1076 NAND locking support.
1078 config CMD_NAND_TORTURE
1081 NAND torture support.
1090 NVM Express device support
1093 bool "onenand - access to onenand device"
1096 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1097 various useful features. This command allows reading, writing,
1098 and erasing blocks. It allso provides a way to show and change
1099 bad blocks, and test the device.
1104 Enable the 'osd' command which allows to query information from and
1105 write text data to a on-screen display (OSD) device; a virtual device
1106 associated with a display capable of displaying a text overlay on the
1107 display it's associated with..
1111 select HAVE_BLOCK_DEVICE
1112 select PARTITION_UUIDS
1114 Read and display information about the partition table on
1118 bool "pci - Access PCI devices"
1120 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1121 used on some devices to allow the CPU to communicate with its
1122 peripherals. Sub-commands allow bus enumeration, displaying and
1123 changing configuration space and a few other features.
1126 bool "pinmux - show pins muxing"
1127 default y if PINCTRL
1129 Parse all available pin-controllers and show pins muxing. This
1130 is useful for debug purpoer to check the pin muxing and to know if
1131 a pin is configured as a GPIO or as an alternate function.
1136 Poweroff/Shutdown the system
1139 bool "read - Read binary data from a partition"
1141 Provides low-level access to the data in a partition.
1143 config CMD_REMOTEPROC
1145 depends on REMOTEPROC
1147 Support for Remote Processor control
1150 bool "sata - Access SATA subsystem"
1153 SATA (Serial Advanced Technology Attachment) is a serial bus
1154 standard for connecting to hard drives and other storage devices.
1155 This command provides information about attached devices and allows
1156 reading, writing and other operations.
1158 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1159 Attachment, where AT refers to an IBM AT (Advanced Technology)
1160 computer released in 1984.
1163 bool "saves - Save a file over serial in S-Record format"
1165 Provides a way to save a binary file using the Motorola S-Record
1166 format over the serial line.
1169 bool "scsi - Access to SCSI devices"
1172 This provides a 'scsi' command which provides access to SCSI (Small
1173 Computer System Interface) devices. The command provides a way to
1174 scan the bus, reset the bus, read and write data and get information
1178 bool "sdram - Print SDRAM configuration information"
1180 Provides information about attached SDRAM. This assumed that the
1181 SDRAM has an EEPROM with information that can be read using the
1182 I2C bus. This is only available on some boards.
1186 depends on DM_SPI_FLASH || SPI_FLASH
1187 default y if DM_SPI_FLASH
1192 bool "sf test - Allow testing of SPI flash"
1195 Provides a way to test that SPI flash is working correctly. The
1196 test is destructive, in that an area of SPI flash must be provided
1197 for the test to use. Performance information is also provided,
1198 measuring the performance of reading, writing and erasing in
1199 Mbps (Million Bits Per Second). This value should approximately
1200 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1201 everything is working properly.
1204 bool "sspi - Command to access spi device"
1207 SPI utility command.
1209 config DEFAULT_SPI_BUS
1210 int "default spi bus used by sspi command"
1214 config DEFAULT_SPI_MODE
1215 hex "default spi mode used by sspi command (see include/spi.h)"
1220 bool "tsi148 - Command to access tsi148 device"
1222 This provides various sub-commands to initialise and configure the
1223 Turndra tsi148 device. See the command help for full details.
1226 bool "Enable UFS - Universal Flash Subsystem commands"
1229 "This provides commands to initialise and configure universal flash
1233 bool "universe - Command to set up the Turndra Universe controller"
1235 This allows setting up the VMEbus provided by this controller.
1236 See the command help for full details.
1240 select HAVE_BLOCK_DEVICE
1246 select USB_FUNCTION_SDP
1248 Enables the command "sdp" which is used to have U-Boot emulating the
1249 Serial Download Protocol (SDP) via USB.
1253 depends on USB_FUNCTION_ROCKUSB
1255 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1256 read/write info, image to/from devices. This enable rockusb command
1257 support to communication with rockusb device. for more detail about
1258 this command, please read doc/README.rockusb.
1260 config CMD_USB_MASS_STORAGE
1261 bool "UMS usb mass storage"
1262 select USB_FUNCTION_MASS_STORAGE
1264 USB mass storage support
1271 VirtIO block device support
1277 This provides commands to control the watchdog timer devices.
1283 Enable the command "axi" for accessing AXI (Advanced eXtensible
1284 Interface) busses, a on-chip interconnect specification for managing
1285 functional blocks in SoC designs, which is also often used in designs
1286 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1290 menu "Shell scripting commands"
1296 Echo args to console
1302 Return true/false on integer compare.
1308 Run script from memory
1314 Evaluate boolean and math expressions and store the result in an env
1316 Also supports loading the value at a memory location into a variable.
1317 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1321 menu "Android support commands"
1323 config CMD_AB_SELECT
1326 depends on ANDROID_AB
1328 On Android devices with more than one boot slot (multiple copies of
1329 the kernel and system images) this provides a command to select which
1330 slot should be used to boot from and register the boot attempt. This
1331 is used by the new A/B update model where one slot is updated in the
1332 background while running from the other slot.
1339 bool "Network commands"
1349 bootp - boot image via network using BOOTP/TFTP protocol
1353 depends on CMD_BOOTP
1355 Boot image via network using DHCP/TFTP protocol
1357 config BOOTP_BOOTPATH
1358 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1360 depends on CMD_BOOTP
1362 Even though the config is called BOOTP_BOOTPATH, it stores the
1363 path in the variable 'rootpath'.
1366 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1368 depends on CMD_BOOTP
1370 The primary DNS server is stored as 'dnsip'. If two servers are
1371 returned, you must set BOOTP_DNS2 to store that second server IP
1375 bool "Store 'dnsip2' from BOOTP/DHCP server"
1376 depends on BOOTP_DNS
1378 If a DHCP client requests the DNS server IP from a DHCP server,
1379 it is possible that more than one DNS serverip is offered to the
1380 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1381 server IP will be stored in the additional environment
1382 variable "dnsip2". The first DNS serverip is always
1383 stored in the variable "dnsip", when BOOTP_DNS is defined.
1385 config BOOTP_GATEWAY
1386 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1388 depends on CMD_BOOTP
1390 config BOOTP_HOSTNAME
1391 bool "Request & store 'hostname' from BOOTP/DHCP server"
1393 depends on CMD_BOOTP
1395 The name may or may not be qualified with the local domain name.
1397 config BOOTP_PREFER_SERVERIP
1398 bool "serverip variable takes precedent over DHCP server IP."
1399 depends on CMD_BOOTP
1401 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1403 With this option enabled, the 'serverip' variable in the environment
1404 takes precedence over DHCP server IP and will only be set by the DHCP
1405 server if not already set in the environment.
1407 config BOOTP_SUBNETMASK
1408 bool "Request & store 'netmask' from BOOTP/DHCP server"
1410 depends on CMD_BOOTP
1412 config BOOTP_NTPSERVER
1413 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1414 depends on CMD_BOOTP
1419 Selecting this will allow capturing all Ethernet packets and store
1420 them in physical memory in a PCAP formated file,
1421 later to be analyzed by PCAP reader application (IE. WireShark).
1424 bool "Send PXE client arch to BOOTP/DHCP server"
1426 depends on CMD_BOOTP && CMD_PXE
1428 Supported for ARM, ARM64, and x86 for now.
1430 config BOOTP_PXE_CLIENTARCH
1432 depends on BOOTP_PXE
1433 default 0x16 if ARM64
1437 config BOOTP_VCI_STRING
1439 depends on CMD_BOOTP
1440 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1441 default "U-Boot.armv8" if ARM64
1442 default "U-Boot.arm" if ARM
1449 tftpboot - boot image via network using TFTP protocol
1453 depends on CMD_TFTPBOOT
1455 TFTP put command, for uploading files to a server
1459 depends on CMD_TFTPBOOT
1461 Act as a TFTP server and boot the first received file
1463 config NET_TFTP_VARS
1464 bool "Control TFTP timeout and count through environment"
1465 depends on CMD_TFTPBOOT
1468 If set, allows controlling the TFTP timeout through the
1469 environment variable tftptimeout, and the TFTP maximum
1470 timeout count through the variable tftptimeoutcountmax.
1471 If unset, timeout and maximum are hard-defined as 1 second
1472 and 10 timouts per TFTP transfer.
1477 Boot image via network using RARP/TFTP protocol
1483 Boot image via network using NFS protocol.
1489 If set, allows 802.3(clause 22) MII Management functions interface access
1490 The management interface specified in Clause 22 provides
1491 a simple, two signal, serial interface to connect a
1492 Station Management entity and a managed PHY for providing access
1493 to management parameters and services.
1494 The interface is referred to as the MII management interface.
1500 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1501 The MDIO interface is orthogonal to the MII interface and extends
1502 it by adding access to more registers through indirect addressing.
1507 Send ICMP ECHO_REQUEST to network host
1512 Perform CDP network configuration
1517 Synchronize RTC via network
1522 Lookup the IP of a hostname
1524 config CMD_LINK_LOCAL
1528 Acquire a network IP address using the link-local protocol
1535 Allow control of L2 Ethernet switch commands. These are supported
1536 by the vsc9953 Ethernet driver at present. Sub-commands allow
1537 operations such as enabling / disabling a port and
1538 viewing/maintaining the filtering database (FDB)
1544 Boot image via network using PXE protocol
1549 Wait for wake-on-lan Magic Packet
1553 menu "Misc commands"
1556 bool "Enable 'bmp' command"
1557 depends on LCD || DM_VIDEO || VIDEO
1559 This provides a way to obtain information about a BMP-format image
1560 and to display it. BMP (which presumably stands for BitMaP) is a
1561 file format defined by Microsoft which supports images of various
1562 depths, formats and compression methods. Headers on the file
1563 determine the formats used. This command can be used by first loading
1564 the image into RAM, then using this command to look at it or display
1567 config CMD_BOOTCOUNT
1569 depends on BOOTCOUNT_LIMIT
1571 Enable the bootcount command, which allows interrogation and
1572 reset of the bootcounter.
1575 bool "Enable board-specific commands"
1577 (deprecated: instead, please define a Kconfig option for each command)
1579 Some boards have board-specific commands which are only enabled
1580 during developemnt and need to be turned off for production. This
1581 option provides a way to control this. The commands that are enabled
1582 vary depending on the board.
1584 config CMD_BKOPS_ENABLE
1585 bool "mmc bkops enable"
1589 Enable command for setting manual background operations handshake
1590 on a eMMC device. The feature is optionally available on eMMC devices
1591 conforming to standard >= 4.41.
1593 config CMD_BLOCK_CACHE
1594 bool "blkcache - control and stats for block cache"
1595 depends on BLOCK_CACHE
1596 default y if BLOCK_CACHE
1598 Enable the blkcache command, which can be used to control the
1599 operation of the cache functions.
1600 This is most useful when fine-tuning the operation of the cache
1601 during development, but also allows the cache to be disabled when
1602 it might hurt performance (e.g. when using the ums command).
1605 bool "icache or dcache"
1607 Enable the "icache" and "dcache" commands
1609 config CMD_CONITRACE
1610 bool "conitrace - trace console input codes"
1612 Enable the 'conitrace' command which displays the codes received
1613 from the console input as hexadecimal numbers.
1616 bool "Enable clear screen command 'cls'"
1617 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1620 Enable the 'cls' command which clears the screen contents
1621 on video frame buffer.
1624 bool "efidebug - display/configure UEFI environment"
1625 depends on EFI_LOADER
1626 select EFI_DEVICE_PATH_TO_TEXT
1629 Enable the 'efidebug' command which provides a subset of UEFI
1630 shell utility with simplified functionality. It will be useful
1631 particularly for managing boot parameters as well as examining
1632 various EFI status for debugging.
1634 config CMD_EXCEPTION
1635 bool "exception - raise exception"
1636 depends on ARM || RISCV || X86
1638 Enable the 'exception' command which allows to raise an exception.
1645 Enable the 'led' command which allows for control of LEDs supported
1646 by the board. The LEDs can be listed with 'led list' and controlled
1647 with led on/off/togle/blink. Any LED drivers can be controlled with
1648 this command, e.g. led_gpio.
1655 Enable the 'date' command for getting/setting the time/date in RTC
1661 Run commands and summarize execution time.
1664 bool "gettime - read elapsed time"
1666 Enable the 'gettime' command which reads the elapsed time since
1667 U-Boot started running. This shows the time in seconds and
1668 milliseconds. See also the 'bootstage' command which provides more
1669 flexibility for boot timing.
1676 Print bytes from the hardware random number generator.
1678 # TODO: rename to CMD_SLEEP
1683 Delay execution for some time
1686 bool "support for multiprocessor"
1688 This provides an option to brinup
1689 different processors in multiprocessor
1695 Access the system timer.
1701 This provides basic access to the U-Boot's sound support. The main
1702 feature is to play a beep.
1704 sound init - set up sound system
1705 sound play - play a sound
1711 Boot image via local extlinux.conf file
1717 This provides access to the QEMU firmware interface. The main
1718 feature is to allow easy loading of files passed to qemu-system
1719 via -kernel / -initrd
1721 source "cmd/mvebu/Kconfig"
1724 bool "terminal - provides a way to attach a serial terminal"
1726 Provides a 'cu'-like serial terminal command. This can be used to
1727 access other serial ports from the system console. The terminal
1728 is very simple with no special processing of characters. As with
1729 cu, you can press ~. (tilde followed by period) to exit.
1732 bool "uuid, guid - generation of unique IDs"
1735 This enables two commands:
1737 uuid - generate random Universally Unique Identifier
1738 guid - generate Globally Unique Identifier based on random UUID
1740 The two commands are very similar except for the endianness of the
1745 source "cmd/ti/Kconfig"
1747 config CMD_BOOTSTAGE
1748 bool "Enable the 'bootstage' command"
1749 depends on BOOTSTAGE
1751 Add a 'bootstage' command which supports printing a report
1752 and un/stashing of bootstage data.
1754 menu "Power commands"
1756 bool "Enable Driver Model PMIC command"
1759 This is the pmic command, based on a driver model pmic's API.
1760 Command features are unchanged:
1761 - list - list pmic devices
1762 - pmic dev <id> - show or [set] operating pmic device (NEW)
1763 - pmic dump - dump registers
1764 - pmic read address - read byte of register at address
1765 - pmic write address - write byte to register at address
1766 The only one change for this command is 'dev' subcommand.
1768 config CMD_REGULATOR
1769 bool "Enable Driver Model REGULATOR command"
1770 depends on DM_REGULATOR
1772 This command is based on driver model regulator's API.
1773 User interface features:
1774 - list - list regulator devices
1775 - regulator dev <id> - show or [set] operating regulator device
1776 - regulator info - print constraints info
1777 - regulator status - print operating status
1778 - regulator value <val] <-f> - print/[set] voltage value [uV]
1779 - regulator current <val> - print/[set] current value [uA]
1780 - regulator mode <id> - print/[set] operating mode id
1781 - regulator enable - enable the regulator output
1782 - regulator disable - disable the regulator output
1784 The '-f' (force) option can be used for set the value which exceeds
1785 the limits, which are found in device-tree and are kept in regulator's
1786 uclass platdata structure.
1790 menu "Security commands"
1792 bool "Enable the 'aes' command"
1795 This provides a means to encrypt and decrypt data using the AES
1796 (Advanced Encryption Standard). This algorithm uses a symetric key
1797 and is widely used as a streaming cipher. Different key lengths are
1798 supported by the algorithm but this command only supports 128 bits
1802 bool "Enable the 'blob' command"
1804 This is used with the Freescale secure boot mechanism.
1806 Freescale's SEC block has built-in Blob Protocol which provides
1807 a method for protecting user-defined data across system power
1808 cycles. SEC block protects data in a data structure called a Blob,
1809 which provides both confidentiality and integrity protection.
1811 Encapsulating data as a blob
1812 Each time that the Blob Protocol is used to protect data, a
1813 different randomly generated key is used to encrypt the data.
1814 This random key is itself encrypted using a key which is derived
1815 from SoC's non-volatile secret key and a 16 bit Key identifier.
1816 The resulting encrypted key along with encrypted data is called a
1817 blob. The non-volatile secure key is available for use only during
1820 During decapsulation, the reverse process is performed to get back
1824 blob enc - encapsulating data as a cryptgraphic blob
1825 blob dec - decapsulating cryptgraphic blob to get the data
1829 blob enc src dst len km
1831 Encapsulate and create blob of data $len bytes long
1832 at address $src and store the result at address $dst.
1833 $km is the 16 byte key modifier is also required for
1834 generation/use as key for cryptographic operation. Key
1835 modifier should be 16 byte long.
1837 blob dec src dst len km
1839 Decapsulate the blob of data at address $src and
1840 store result of $len byte at addr $dst.
1841 $km is the 16 byte key modifier is also required for
1842 generation/use as key for cryptographic operation. Key
1843 modifier should be 16 byte long.
1846 bool "Support 'hash' command"
1849 This provides a way to hash data in memory using various supported
1850 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1851 saved to memory or to an environment variable. It is also possible
1852 to verify a hash against data in memory.
1855 bool "Support the 'hvc' command"
1856 depends on ARM_SMCCC
1858 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1859 development and testing.
1862 bool "Support the 'smc' command"
1863 depends on ARM_SMCCC
1865 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1866 development and testing.
1872 Add -v option to verify data against a hash.
1882 bool "Enable the 'tpm' command"
1883 depends on TPM_V1 || TPM_V2
1884 select CMD_TPM_V1 if TPM_V1
1885 select CMD_TPM_V2 if TPM_V2
1887 This provides a means to talk to a TPM from the command line. A wide
1888 range of commands if provided - see 'tpm help' for details. The
1889 command requires a suitable TPM on your board and the correct driver
1895 bool "Enable the 'tpm test' command"
1898 This provides a a series of tests to confirm that the TPMv1.x is
1899 working correctly. The tests cover initialisation, non-volatile RAM,
1900 extend, global lock and checking that timing is within expectations.
1901 The tests pass correctly on Infineon TPMs but may need to be adjusted
1908 menu "Firmware commands"
1910 bool "Enable crosec command"
1914 Enable command-line access to the Chrome OS EC (Embedded
1915 Controller). This provides the 'crosec' command which has
1916 a number of sub-commands for performing EC tasks such as
1917 updating its flash, accessing a small saved context area
1918 and talking to the I2C bus behind the EC (if there is one).
1921 menu "Filesystem commands"
1923 bool "Enable the 'btrsubvol' command"
1926 This enables the 'btrsubvol' command to list subvolumes
1927 of a BTRFS filesystem. There are no special commands for
1928 listing BTRFS directories or loading BTRFS files - this
1929 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1930 when BTRFS is enabled (see FS_BTRFS).
1933 bool "Enable the 'cbfs' command"
1936 Define this to enable support for reading from a Coreboot
1937 filesystem. This is a ROM-based filesystem used for accessing files
1938 on systems that use coreboot as the first boot-loader and then load
1939 U-Boot to actually boot the Operating System. Available commands are
1940 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1943 bool "Enable the 'cramfs' command"
1944 depends on FS_CRAMFS
1946 This provides commands for dealing with CRAMFS (Compressed ROM
1947 filesystem). CRAMFS is useful when space is tight since files are
1948 compressed. Two commands are provided:
1950 cramfsls - lists files in a cramfs image
1951 cramfsload - loads a file from a cramfs image
1954 bool "ext2 command support"
1957 Enables EXT2 FS command
1960 bool "ext4 command support"
1963 Enables EXT4 FS command
1965 config CMD_EXT4_WRITE
1967 bool "ext4 write command support"
1970 Enables EXT4 FS write command
1973 bool "FAT command support"
1976 Support for the FAT fs
1978 config CMD_FS_GENERIC
1979 bool "filesystem commands"
1981 Enables filesystem commands (e.g. load, ls) that work for multiple
1985 bool "fsuuid command"
1987 Enables fsuuid command for filesystem UUID.
1990 bool "jffs2 command"
1993 Enables commands to support the JFFS2 (Journalling Flash File System
1994 version 2) filesystem. This enables fsload, ls and fsinfo which
1995 provide the ability to load files, list directories and obtain
1996 filesystem information.
1999 bool "MTD partition support"
2002 MTD partitioning tool support.
2003 It is strongly encouraged to avoid using this command
2004 anymore along with 'sf', 'nand', 'onenand'. One can still
2005 declare the partitions in the mtdparts environment variable
2006 but better use the MTD stack and the 'mtd' command instead.
2008 config CMD_MTDPARTS_SPREAD
2009 bool "Padd partition size to take account of bad blocks"
2010 depends on CMD_MTDPARTS
2012 This enables the 'spread' sub-command of the mtdparts command.
2013 This command will modify the existing mtdparts variable by increasing
2014 the size of the partitions such that 1) each partition's net size is
2015 at least as large as the size specified in the mtdparts variable and
2016 2) each partition starts on a good block.
2018 config CMD_MTDPARTS_SHOW_NET_SIZES
2019 bool "Show net size (w/o bad blocks) of partitions"
2020 depends on CMD_MTDPARTS
2022 Adds two columns to the printed partition table showing the
2023 effective usable size of a partition, if bad blocks are taken
2026 config MTDIDS_DEFAULT
2027 string "Default MTD IDs"
2028 depends on MTD || SPI_FLASH
2030 Defines a default MTD IDs list for use with MTD partitions in the
2031 Linux MTD command line partitions format.
2033 config MTDPARTS_DEFAULT
2034 string "Default MTD partition scheme"
2035 depends on MTD || SPI_FLASH
2037 Defines a default MTD partitioning scheme in the Linux MTD command
2038 line partitions format
2041 bool "reiser - Access to reiserfs filesystems"
2043 This provides two commands which operate on a resierfs filesystem,
2044 commonly used some years ago:
2046 reiserls - list files
2047 reiserload - load a file
2050 bool "yaffs2 - Access of YAFFS2 filesystem"
2054 This provides commands for accessing a YAFFS2 filesystem. Yet
2055 Another Flash Filesystem 2 is a filesystem designed specifically
2056 for NAND flash. It incorporates bad-block management and ensures
2057 that device writes are sequential regardless of filesystem
2061 bool "zfs - Access of ZFS filesystem"
2063 This provides commands to accessing a ZFS filesystem, commonly used
2064 on Solaris systems. Two sub-commands are provided:
2066 zfsls - list files in a directory
2067 zfsload - load a file
2069 See doc/README.zfs for more details.
2073 menu "Debug commands"
2078 The bedbug (emBEDded deBUGger) command provides debugging features
2079 for some PowerPC processors. For details please see the
2080 docuemntation in doc/README.beddbug
2083 bool "diag - Board diagnostics"
2085 This command provides access to board diagnostic tests. These are
2086 called Power-on Self Tests (POST). The command allows listing of
2087 available tests and running either all the tests, or specific tests
2091 bool "irq - Show information about interrupts"
2092 depends on !ARM && !MIPS && !SH
2094 This enables two commands:
2096 interrupts - enable or disable interrupts
2097 irqinfo - print device-specific interrupt information
2100 bool "kgdb - Allow debugging of U-Boot with gdb"
2103 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2104 over a serial link for debugging purposes. This allows
2105 single-stepping, inspecting variables, etc. This is supported only
2106 on PowerPC at present.
2109 bool "log - Generation, control and access to logging"
2112 This provides access to logging features. It allows the output of
2113 log data to be controlled to a limited extent (setting up the default
2114 maximum log level for emitting of records). It also provides access
2115 to a command used for testing the log system.
2118 bool "trace - Support tracing of function calls and timing"
2120 Enables a command to control using of function tracing within
2121 U-Boot. This allows recording of call traces including timing
2122 information. The command can write data to memory for exporting
2123 for analysis (e.g. using bootchart). See doc/README.trace for full
2127 bool "avb - Android Verified Boot 2.0 operations"
2128 depends on AVB_VERIFY
2131 Enables a "avb" command to perform verification of partitions using
2132 Android Verified Boot 2.0 functionality. It includes such subcommands:
2133 avb init - initialize avb2 subsystem
2134 avb read_rb - read rollback index
2135 avb write_rb - write rollback index
2136 avb is_unlocked - check device lock state
2137 avb get_uuid - read and print uuid of a partition
2138 avb read_part - read data from partition
2139 avb read_part_hex - read data from partition and output to stdout
2140 avb write_part - write data to partition
2141 avb verify - run full verification chain
2145 tristate "Enable UBI - Unsorted block images commands"
2148 UBI is a software layer above MTD layer which admits use of LVM-like
2149 logical volumes on top of MTD devices, hides some complexities of
2150 flash chips like wear and bad blocks and provides some other useful
2151 capabilities. Please, consult the MTD web site for more details
2152 (www.linux-mtd.infradead.org). Activate this option if you want
2153 to use U-Boot UBI commands.
2154 It is also strongly encouraged to also enable CONFIG_MTD to get full
2158 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2160 default y if CMD_UBI
2163 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob