1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
69 menu "Autoboot options"
75 This enables the autoboot. See doc/README.autoboot for detail.
78 bool "Stop autobooting via specific input key / string"
81 This option enables stopping (aborting) of the automatic
82 boot feature only by issuing a specific input key or
83 string. If not enabled, any input key will abort the
84 U-Boot automatic booting process and bring the device
85 to the U-Boot prompt for user input.
87 config AUTOBOOT_PROMPT
88 string "Autoboot stop prompt"
89 depends on AUTOBOOT_KEYED
90 default "Autoboot in %d seconds\\n"
92 This string is displayed before the boot delay selected by
93 CONFIG_BOOTDELAY starts. If it is not defined there is no
94 output indicating that autoboot is in progress.
96 Note that this define is used as the (only) argument to a
97 printf() call, so it may contain '%' format specifications,
98 provided that it also includes, sepearated by commas exactly
99 like in a printf statement, the required arguments. It is
100 the responsibility of the user to select only such arguments
101 that are valid in the given context.
103 config AUTOBOOT_ENCRYPTION
104 bool "Enable encryption in autoboot stopping"
105 depends on AUTOBOOT_KEYED
107 This option allows a string to be entered into U-Boot to stop the
108 autoboot. The string itself is hashed and compared against the hash
109 in the environment variable 'bootstopkeysha256'. If it matches then
110 boot stops and a command-line prompt is presented.
112 This provides a way to ship a secure production device which can also
113 be accessed at the U-Boot command line.
115 config AUTOBOOT_DELAY_STR
116 string "Delay autobooting via specific input key / string"
117 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
119 This option delays the automatic boot feature by issuing
120 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
121 or the environment variable "bootdelaykey" is specified
122 and this string is received from console input before
123 autoboot starts booting, U-Boot gives a command prompt. The
124 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
125 used, otherwise it never times out.
127 config AUTOBOOT_STOP_STR
128 string "Stop autobooting via specific input key / string"
129 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
131 This option enables stopping (aborting) of the automatic
132 boot feature only by issuing a specific input key or
133 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
134 variable "bootstopkey" is specified and this string is
135 received from console input before autoboot starts booting,
136 U-Boot gives a command prompt. The U-Boot prompt never
137 times out, even if CONFIG_BOOT_RETRY_TIME is used.
139 config AUTOBOOT_KEYED_CTRLC
140 bool "Enable Ctrl-C autoboot interruption"
141 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
144 This option allows for the boot sequence to be interrupted
145 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
146 Setting this variable provides an escape sequence from the
147 limited "password" strings.
149 config AUTOBOOT_STOP_STR_SHA256
150 string "Stop autobooting via SHA256 encrypted password"
151 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
153 This option adds the feature to only stop the autobooting,
154 and therefore boot into the U-Boot prompt, when the input
155 string / password matches a values that is encypted via
156 a SHA256 hash and saved in the environment.
158 config AUTOBOOT_USE_MENUKEY
159 bool "Allow a specify key to run a menu from the environment"
160 depends on !AUTOBOOT_KEYED
162 If a specific key is pressed to stop autoboot, then the commands in
163 the environment variable 'menucmd' are executed before boot starts.
165 config AUTOBOOT_MENUKEY
166 int "ASCII value of boot key to show a menu"
168 depends on AUTOBOOT_USE_MENUKEY
170 If this key is pressed to stop autoboot, then the commands in the
171 environment variable 'menucmd' will be executed before boot starts.
172 For example, 33 means "!" in ASCII, so pressing ! at boot would take
175 config AUTOBOOT_MENU_SHOW
176 bool "Show a menu on boot"
177 depends on CMD_BOOTMENU
179 This enables the boot menu, controlled by environment variables
180 defined by the board. The menu starts after running the 'preboot'
181 environmnent variable (if enabled) and before handling the boot delay.
182 See README.bootmenu for more details.
204 Print ".config" contents.
206 If this option is enabled, the ".config" file contents are embedded
207 in the U-Boot image and can be printed on the console by the "config"
208 command. This provides information of which options are enabled on
215 Print console devices and information.
220 Print information about available CPUs. This normally shows the
221 number of CPUs, type (e.g. manufacturer, architecture, product or
222 internal name) and clock frequency. Other information may be
223 available depending on the CPU driver.
229 Print GPL license text
234 Provides access to the Intel Power-Management Controller (PMC) so
235 that its state can be examined. This does not currently support
236 changing the state but it is still useful for debugging and seeing
253 Run the command stored in the environment "bootcmd", i.e.
254 "bootd" does the same thing as "run bootcmd".
260 Boot an application image from the memory.
265 Boot the Linux zImage
269 depends on ARM64 || RISCV
272 Boot an AArch64 Linux Kernel image from memory.
275 bool "Support booting Linux OS images"
276 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
279 Support booting the Linux kernel directly via a command such as bootm
283 bool "Support booting NetBSD (non-EFI) loader images"
287 Support booting NetBSD via the bootm command.
289 config BOOTM_OPENRTOS
290 bool "Support booting OPENRTOS / FreeRTOS images"
293 Support booting OPENRTOS / FreeRTOS via the bootm command.
296 bool "Support booting Enea OSE images"
299 Support booting Enea OSE images via the bootm command.
302 bool "Support booting Plan9 OS images"
306 Support booting Plan9 images via the bootm command.
309 bool "Support booting RTEMS OS images"
313 Support booting RTEMS images via the bootm command.
316 bool "Support booting VxWorks OS images"
320 Support booting VxWorks images via the bootm command.
324 depends on EFI_LOADER
327 Boot an EFI image from memory.
329 config CMD_BOOTEFI_HELLO_COMPILE
330 bool "Compile a standard EFI hello world binary for testing"
331 depends on CMD_BOOTEFI && !CPU_V7M
334 This compiles a standard EFI hello world application with U-Boot so
335 that it can be used with the test/py testing framework. This is useful
336 for testing that EFI is working at a basic level, and for bringing
337 up EFI support on a new architecture.
339 No additional space will be required in the resulting U-Boot binary
340 when this option is enabled.
342 config CMD_BOOTEFI_HELLO
343 bool "Allow booting a standard EFI hello world for testing"
344 depends on CMD_BOOTEFI_HELLO_COMPILE
346 This adds a standard EFI hello world application to U-Boot so that
347 it can be used with the 'bootefi hello' command. This is useful
348 for testing that EFI is working at a basic level, and for bringing
349 up EFI support on a new architecture.
351 source lib/efi_selftest/Kconfig
357 Add an ANSI terminal boot menu command.
362 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
363 image into RAM, dump image structure information, etc. Those dtb/dtbo
364 files should be merged in one dtb further, which needs to be passed to
365 the kernel, as part of a boot process.
368 bool "bootelf, bootvx"
371 Boot an ELF/vxWorks image from the memory.
374 bool "Flattened Device Tree utility commands"
378 Do FDT related setup before booting into the Operating System.
384 Start an application at a given address.
390 Run the command in the given environment variable.
396 Print header information for application image.
401 List all images found in flash
407 Extract a part of a multi-image.
410 bool "spl export - Export boot information for Falcon boot"
413 Falcon mode allows booting directly from SPL into an Operating
414 System such as Linux, thus skipping U-Boot proper. See
415 doc/README.falcon for full information about how to use this
418 config CMD_SPL_NAND_OFS
419 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
420 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
423 This provides the offset of the command line arguments for Linux
424 when booting from NAND in Falcon mode. See doc/README.falcon
425 for full information about how to use this option (and also see
426 board/gateworks/gw_ventana/README for an example).
428 config CMD_SPL_NOR_OFS
429 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
430 depends on CMD_SPL && SPL_NOR_SUPPORT
433 This provides the offset of the command line arguments or dtb for
434 Linux when booting from NOR in Falcon mode.
436 config CMD_SPL_WRITE_SIZE
437 hex "Size of argument area"
441 This provides the size of the command-line argument area in NAND
442 flash used by Falcon-mode boot. See the documentation until CMD_SPL
446 bool "fitImage update command"
448 Implements the 'fitupd' command, which allows to automatically
449 store software updates present on a TFTP server in NOR Flash
451 config CMD_THOR_DOWNLOAD
452 bool "thor - TIZEN 'thor' download"
455 Implements the 'thor' download protocol. This is a way of
456 downloading a software update over USB from an attached host.
457 There is no documentation about this within the U-Boot source code
458 but you should be able to find something on the interwebs.
461 bool "zboot - x86 boot command"
463 With x86 machines it is common to boot a bzImage file which
464 contains both a kernel and a setup.bin file. The latter includes
465 configuration information from the dark ages which x86 boards still
466 need to pick things out of.
468 Consider using FIT in preference to this since it supports directly
469 booting both 32- and 64-bit kernels, as well as secure boot.
470 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
474 menu "Environment commands"
477 bool "ask for env variable"
479 Ask for environment variable
497 Edit environment variable.
502 Allow for searching environment variables
508 Save all environment variables into the compiled-in persistent
514 depends on CMD_SAVEENV
516 Erase environment variables from the compiled-in persistent
519 config CMD_ENV_EXISTS
523 Check if a variable is defined in the environment for use in
526 config CMD_ENV_CALLBACK
527 bool "env callbacks - print callbacks and their associated variables"
529 Some environment variable have callbacks defined by
530 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
531 For example changing "baudrate" adjust the serial baud rate. This
532 command lists the currently defined callbacks.
535 bool "env flags -print variables that have non-default flags"
537 Some environment variables have special flags that control their
538 behaviour. For example, serial# can only be written once and cannot
539 be deleted. This command shows the variables that have special
542 config CMD_NVEDIT_EFI
543 bool "env [set|print] -e - set/print UEFI variables"
544 depends on EFI_LOADER
547 UEFI variables are encoded as some form of U-Boot variables.
548 If enabled, we are allowed to set/print UEFI variables using
549 "env" command with "-e" option without knowing details.
551 config CMD_NVEDIT_INFO
552 bool "env info - print or evaluate environment information"
554 Print environment information:
555 - env_valid : is environment valid
556 - env_ready : is environment imported into hash table
557 - env_use_default : is default environment used
559 This command can be optionally used for evaluation in scripts:
560 [-d] : evaluate whether default environment is used
561 [-p] : evaluate whether environment can be persisted
562 The result of multiple evaluations will be combined with AND.
566 menu "Memory commands"
571 Compute binary operations (xor, or, and) of byte arrays of arbitrary
572 size from memory and store the result in memory or the environment.
585 Add -v option to verify data against a crc32 checksum.
588 bool "eeprom - EEPROM subsystem"
590 (deprecated, needs conversion to driver model)
591 Provides commands to read and write EEPROM (Electrically Erasable
592 Programmable Read Only Memory) chips that are connected over an
595 config CMD_EEPROM_LAYOUT
596 bool "Enable layout-aware eeprom commands"
597 depends on CMD_EEPROM
599 (deprecated, needs conversion to driver model)
600 When enabled, additional eeprom sub-commands become available.
602 eeprom print - prints the contents of the eeprom in a human-readable
603 way (eeprom layout fields, and data formatted to be fit for human
606 eeprom update - allows user to update eeprom fields by specifying
607 the field name, and providing the new data in a human readable format
608 (same format as displayed by the eeprom print command).
610 Both commands can either auto detect the layout, or be told which
614 __weak int parse_layout_version(char *str)
615 - override to provide your own layout name parsing
616 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
618 - override to setup the layout metadata based on the version
619 __weak int eeprom_layout_detect(unsigned char *data)
620 - override to provide your own algorithm for detecting layout
623 - contains various printing and updating functions for common
624 types of eeprom fields. Can be used for defining
627 config EEPROM_LAYOUT_HELP_STRING
628 string "Tells user what layout names are supported"
629 depends on CMD_EEPROM_LAYOUT
630 default "<not defined>"
632 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
638 Infinite write loop on address range
645 Compute MD5 checksum.
650 depends on CMD_MD5SUM
652 Add -v option to verify data against an MD5 checksum.
657 Display memory information.
660 bool "md, mm, nm, mw, cp, cmp, base, loop"
665 mm - memory modify (auto-incrementing address)
666 nm - memory modify (constant address)
667 mw - memory write (fill)
670 base - print or set address offset
671 loop - initialize loop on address range
674 bool "Enable cyclic md/mw commands"
675 depends on CMD_MEMORY
677 Add the "mdc" and "mwc" memory commands. These are cyclic
682 This command will print 4 bytes (10,11,12,13) each 500 ms.
684 => mwc.l 100 12345678 10
685 This command will write 12345678 to address 100 all 10 ms.
690 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
692 random - fill memory with random data
697 Simple RAM read/write test.
701 config SYS_ALT_MEMTEST
702 bool "Alternative test"
704 Use a more complete alternative memory test.
711 mdc - memory display cyclic
712 mwc - memory write cyclic
718 Compute SHA1 checksum.
720 config SHA1SUM_VERIFY
722 depends on CMD_SHA1SUM
724 Add -v option to verify data against a SHA1 checksum.
727 bool "strings - display strings in memory"
729 This works similarly to the Unix 'strings' command except that it
730 works with a memory range. String of printable characters found
731 within the range are displayed. The minimum number of characters
732 for a sequence to be considered a string can be provided.
736 menu "Compression commands"
740 default y if CMD_BOOTI
743 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
748 default y if CMD_BOOTI
750 Uncompress a zip-compressed memory region.
755 Compress a memory region with zlib deflate method.
759 menu "Device access commands"
762 #depends on FLASH_CFI_DRIVER
765 ARM Ltd reference designs flash partition access
768 bool "adc - Access Analog to Digital Converters info and data"
772 Shows ADC device info and permit printing one-shot analog converted
773 data from a named Analog to Digital Converter.
778 depends on PARTITIONS
780 Read/modify/write the fields of Bootloader Control Block, usually
781 stored on the flash "misc" partition with its structure defined in:
782 https://android.googlesource.com/platform/bootable/recovery/+/master/
783 bootloader_message/include/bootloader_message/bootloader_message.h
785 Some real-life use-cases include (but are not limited to):
786 - Determine the "boot reason" (and act accordingly):
787 https://source.android.com/devices/bootloader/boot-reason
788 - Get/pass a list of commands from/to recovery:
789 https://android.googlesource.com/platform/bootable/recovery
790 - Inspect/dump the contents of the BCB fields
793 bool "bind/unbind - Bind or unbind a device to/from a driver"
796 Bind or unbind a device to/from a driver from the command line.
797 This is useful in situations where a device may be handled by several
798 drivers. For example, this can be used to bind a UDC to the usb ether
799 gadget driver from the command line.
802 bool "clk - Show clock frequencies"
805 Shows clock frequences by calling a sock_clk_dump() hook function.
806 This is depreated in favour of using the CLK uclass and accessing
807 clock values from associated drivers. However currently no command
811 bool "demo - Demonstration commands for driver model"
814 Provides a 'demo' command which can be used to play around with
815 driver model. To use this properly you will need to enable one or
816 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
817 Otherwise you will always get an empty list of devices. The demo
818 devices are defined in the sandbox device tree, so the easiest
819 option is to use sandbox and pass the -d point to sandbox's
826 Enables the command "dfu" which is used to have U-Boot create a DFU
827 class device via USB. This command requires that the "dfu_alt_info"
828 environment variable be set and define the alt settings to expose to
832 bool "dm - Access to driver model information"
835 Provides access to driver model data structures and information,
836 such as a list of devices, list of uclasses and the state of each
837 device (e.g. activated). This is not required for operation, but
838 can be useful to see the state of driver model for debugging or
842 bool "fastboot - Android fastboot support"
845 This enables the command "fastboot" which enables the Android
846 fastboot mode for the platform. Fastboot is a protocol for
847 downloading images, flashing and device control used on
848 Android devices. Fastboot requires either the network stack
849 enabled or support for acting as a USB device.
851 See doc/android/fastboot.txt for more information.
854 bool "fdcboot - Boot from floppy device"
856 The 'fdtboot' command allows booting an image from a floppy disk.
859 bool "flinfo, erase, protect"
861 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
864 flinfo - print FLASH memory information
866 protect - enable or disable FLASH write protection
875 config CMD_FPGA_LOADBP
876 bool "fpga loadbp - load partial bitstream (Xilinx only)"
879 Supports loading an FPGA device from a bitstream buffer containing
882 config CMD_FPGA_LOADFS
883 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
886 Supports loading an FPGA device from a FAT filesystem.
888 config CMD_FPGA_LOADMK
889 bool "fpga loadmk - load bitstream from image"
892 Supports loading an FPGA device from a image generated by mkimage.
894 config CMD_FPGA_LOADP
895 bool "fpga loadp - load partial bitstream"
898 Supports loading an FPGA device from a bitstream buffer containing
901 config CMD_FPGA_LOAD_SECURE
902 bool "fpga loads - loads secure bitstreams (Xilinx only)"
905 Enables the fpga loads command which is used to load secure
906 (authenticated or encrypted or both) bitstreams on to FPGA.
909 bool "fpgad - dump FPGA registers"
911 (legacy, needs conversion to driver model)
912 Provides a way to dump FPGA registers by calling the board-specific
913 fpga_get_reg() function. This functions similarly to the 'md'
917 bool "fuse - support for the fuse subssystem"
919 (deprecated - needs conversion to driver model)
920 This allows reading, sensing, programming or overriding fuses
921 which control the behaviour of the device. The command uses the
930 bool "GPT (GUID Partition Table) command"
932 select HAVE_BLOCK_DEVICE
933 select PARTITION_UUIDS
936 Enable the 'gpt' command to ready and write GPT style partition
940 bool "GPT Random UUID generation"
943 Enable the generation of partitions with random UUIDs if none
946 config CMD_GPT_RENAME
947 bool "GPT partition renaming commands"
950 Enables the 'gpt' command to interchange names on two GPT
951 partitions via the 'gpt swap' command or to rename single
952 partitions via the 'rename' command.
955 bool "ide - Support for IDE drivers"
958 Provides an 'ide' command which allows accessing the IDE drive,
959 reseting the IDE interface, printing the partition table and
960 geting device info. It also enables the 'diskboot' command which
961 permits booting from an IDE drive.
964 bool "io - Support for performing I/O accesses"
966 Provides an 'iod' command to display I/O space and an 'iow' command
967 to write values to the I/O space. This can be useful for manually
968 checking the state of devices during boot when debugging device
972 bool "iotrace - Support for tracing I/O activity"
974 Provides an 'iotrace' command which supports recording I/O reads and
975 writes in a trace buffer in memory . It also maintains a checksum
976 of the trace records (even if space is exhausted) so that the
977 sequence of I/O accesses can be verified.
979 When debugging drivers it is useful to see what I/O accesses were
980 done and in what order.
982 Even if the individual accesses are of little interest it can be
983 useful to verify that the access pattern is consistent each time
984 an operation is performed. In this case a checksum can be used to
985 characterise the operation of a driver. The checksum can be compared
986 across different runs of the operation to verify that the driver is
989 In particular, when performing major refactoring of the driver, where
990 the access pattern should not change, the checksum provides assurance
991 that the refactoring work has not broken the driver.
993 This works by sneaking into the io.h heder for an architecture and
994 redirecting I/O accesses through iotrace's tracing mechanism.
996 For now no commands are provided to examine the trace buffer. The
997 format is fairly simple, so 'md' is a reasonable substitute.
999 Note: The checksum feature is only useful for I/O regions where the
1000 contents do not change outside of software control. Where this is not
1001 suitable you can fall back to manually comparing the addresses. It
1002 might be useful to enhance tracing to only checksum the accesses and
1003 not the data read/written.
1013 bool "w1 - Support for Dallas 1-Wire protocol"
1015 Dallas 1-wire protocol support
1021 Load a binary file over serial line.
1027 Load an S-Record file over serial line
1032 MMC memory mapped support.
1035 bool "Enable support for RPMB in the mmc command"
1038 Enable the commands for reading, writing and programming the
1039 key for the Replay Protection Memory Block partition in eMMC.
1041 config CMD_MMC_SWRITE
1043 depends on CMD_MMC && MMC_WRITE
1046 Enable support for the "mmc swrite" command to write Android sparse
1052 select MTD_PARTITIONS
1054 MTD commands support.
1058 default y if NAND_SUNXI
1059 depends on MTD_RAW_NAND
1064 config CMD_NAND_TRIMFFS
1065 bool "nand write.trimffs"
1066 default y if ARCH_SUNXI
1068 Allows one to skip empty pages when flashing something on a NAND.
1070 config CMD_NAND_LOCK_UNLOCK
1071 bool "nand lock/unlock"
1073 NAND locking support.
1075 config CMD_NAND_TORTURE
1078 NAND torture support.
1087 NVM Express device support
1090 bool "onenand - access to onenand device"
1093 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1094 various useful features. This command allows reading, writing,
1095 and erasing blocks. It allso provides a way to show and change
1096 bad blocks, and test the device.
1101 Enable the 'osd' command which allows to query information from and
1102 write text data to a on-screen display (OSD) device; a virtual device
1103 associated with a display capable of displaying a text overlay on the
1104 display it's associated with..
1108 select HAVE_BLOCK_DEVICE
1109 select PARTITION_UUIDS
1111 Read and display information about the partition table on
1115 bool "pci - Access PCI devices"
1117 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1118 used on some devices to allow the CPU to communicate with its
1119 peripherals. Sub-commands allow bus enumeration, displaying and
1120 changing configuration space and a few other features.
1123 bool "pinmux - show pins muxing"
1124 default y if PINCTRL
1126 Parse all available pin-controllers and show pins muxing. This
1127 is useful for debug purpoer to check the pin muxing and to know if
1128 a pin is configured as a GPIO or as an alternate function.
1133 Poweroff/Shutdown the system
1136 bool "read - Read binary data from a partition"
1138 Provides low-level access to the data in a partition.
1140 config CMD_REMOTEPROC
1142 depends on REMOTEPROC
1144 Support for Remote Processor control
1147 bool "sata - Access SATA subsystem"
1150 SATA (Serial Advanced Technology Attachment) is a serial bus
1151 standard for connecting to hard drives and other storage devices.
1152 This command provides information about attached devices and allows
1153 reading, writing and other operations.
1155 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1156 Attachment, where AT refers to an IBM AT (Advanced Technology)
1157 computer released in 1984.
1160 bool "saves - Save a file over serial in S-Record format"
1162 Provides a way to save a binary file using the Motorola S-Record
1163 format over the serial line.
1166 bool "scsi - Access to SCSI devices"
1169 This provides a 'scsi' command which provides access to SCSI (Small
1170 Computer System Interface) devices. The command provides a way to
1171 scan the bus, reset the bus, read and write data and get information
1175 bool "sdram - Print SDRAM configuration information"
1177 Provides information about attached SDRAM. This assumed that the
1178 SDRAM has an EEPROM with information that can be read using the
1179 I2C bus. This is only available on some boards.
1183 depends on DM_SPI_FLASH || SPI_FLASH
1184 default y if DM_SPI_FLASH
1189 bool "sf test - Allow testing of SPI flash"
1192 Provides a way to test that SPI flash is working correctly. The
1193 test is destructive, in that an area of SPI flash must be provided
1194 for the test to use. Performance information is also provided,
1195 measuring the performance of reading, writing and erasing in
1196 Mbps (Million Bits Per Second). This value should approximately
1197 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1198 everything is working properly.
1201 bool "sspi - Command to access spi device"
1204 SPI utility command.
1206 config DEFAULT_SPI_BUS
1207 int "default spi bus used by sspi command"
1211 config DEFAULT_SPI_MODE
1212 hex "default spi mode used by sspi command (see include/spi.h)"
1217 bool "tsi148 - Command to access tsi148 device"
1219 This provides various sub-commands to initialise and configure the
1220 Turndra tsi148 device. See the command help for full details.
1223 bool "Enable UFS - Universal Flash Subsystem commands"
1226 "This provides commands to initialise and configure universal flash
1230 bool "universe - Command to set up the Turndra Universe controller"
1232 This allows setting up the VMEbus provided by this controller.
1233 See the command help for full details.
1237 select HAVE_BLOCK_DEVICE
1243 select USB_FUNCTION_SDP
1245 Enables the command "sdp" which is used to have U-Boot emulating the
1246 Serial Download Protocol (SDP) via USB.
1250 depends on USB_FUNCTION_ROCKUSB
1252 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1253 read/write info, image to/from devices. This enable rockusb command
1254 support to communication with rockusb device. for more detail about
1255 this command, please read doc/README.rockusb.
1257 config CMD_USB_MASS_STORAGE
1258 bool "UMS usb mass storage"
1259 select USB_FUNCTION_MASS_STORAGE
1261 USB mass storage support
1268 VirtIO block device support
1274 This provides commands to control the watchdog timer devices.
1280 Enable the command "axi" for accessing AXI (Advanced eXtensible
1281 Interface) busses, a on-chip interconnect specification for managing
1282 functional blocks in SoC designs, which is also often used in designs
1283 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1287 menu "Shell scripting commands"
1293 Echo args to console
1299 Return true/false on integer compare.
1305 Run script from memory
1311 Evaluate boolean and math expressions and store the result in an env
1313 Also supports loading the value at a memory location into a variable.
1314 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1318 menu "Android support commands"
1320 config CMD_AB_SELECT
1323 depends on ANDROID_AB
1325 On Android devices with more than one boot slot (multiple copies of
1326 the kernel and system images) this provides a command to select which
1327 slot should be used to boot from and register the boot attempt. This
1328 is used by the new A/B update model where one slot is updated in the
1329 background while running from the other slot.
1336 bool "Network commands"
1346 bootp - boot image via network using BOOTP/TFTP protocol
1350 depends on CMD_BOOTP
1352 Boot image via network using DHCP/TFTP protocol
1354 config BOOTP_BOOTPATH
1355 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1357 depends on CMD_BOOTP
1359 Even though the config is called BOOTP_BOOTPATH, it stores the
1360 path in the variable 'rootpath'.
1363 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1365 depends on CMD_BOOTP
1367 The primary DNS server is stored as 'dnsip'. If two servers are
1368 returned, you must set BOOTP_DNS2 to store that second server IP
1372 bool "Store 'dnsip2' from BOOTP/DHCP server"
1373 depends on BOOTP_DNS
1375 If a DHCP client requests the DNS server IP from a DHCP server,
1376 it is possible that more than one DNS serverip is offered to the
1377 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1378 server IP will be stored in the additional environment
1379 variable "dnsip2". The first DNS serverip is always
1380 stored in the variable "dnsip", when BOOTP_DNS is defined.
1382 config BOOTP_GATEWAY
1383 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1385 depends on CMD_BOOTP
1387 config BOOTP_HOSTNAME
1388 bool "Request & store 'hostname' from BOOTP/DHCP server"
1390 depends on CMD_BOOTP
1392 The name may or may not be qualified with the local domain name.
1394 config BOOTP_PREFER_SERVERIP
1395 bool "serverip variable takes precedent over DHCP server IP."
1396 depends on CMD_BOOTP
1398 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1400 With this option enabled, the 'serverip' variable in the environment
1401 takes precedence over DHCP server IP and will only be set by the DHCP
1402 server if not already set in the environment.
1404 config BOOTP_SUBNETMASK
1405 bool "Request & store 'netmask' from BOOTP/DHCP server"
1407 depends on CMD_BOOTP
1409 config BOOTP_NTPSERVER
1410 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1411 depends on CMD_BOOTP
1416 Selecting this will allow capturing all Ethernet packets and store
1417 them in physical memory in a PCAP formated file,
1418 later to be analyzed by PCAP reader application (IE. WireShark).
1421 bool "Send PXE client arch to BOOTP/DHCP server"
1423 depends on CMD_BOOTP && CMD_PXE
1425 Supported for ARM, ARM64, and x86 for now.
1427 config BOOTP_PXE_CLIENTARCH
1429 depends on BOOTP_PXE
1430 default 0x16 if ARM64
1434 config BOOTP_VCI_STRING
1436 depends on CMD_BOOTP
1437 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1438 default "U-Boot.armv8" if ARM64
1439 default "U-Boot.arm" if ARM
1446 tftpboot - boot image via network using TFTP protocol
1450 depends on CMD_TFTPBOOT
1452 TFTP put command, for uploading files to a server
1456 depends on CMD_TFTPBOOT
1458 Act as a TFTP server and boot the first received file
1460 config NET_TFTP_VARS
1461 bool "Control TFTP timeout and count through environment"
1462 depends on CMD_TFTPBOOT
1465 If set, allows controlling the TFTP timeout through the
1466 environment variable tftptimeout, and the TFTP maximum
1467 timeout count through the variable tftptimeoutcountmax.
1468 If unset, timeout and maximum are hard-defined as 1 second
1469 and 10 timouts per TFTP transfer.
1474 Boot image via network using RARP/TFTP protocol
1480 Boot image via network using NFS protocol.
1486 If set, allows 802.3(clause 22) MII Management functions interface access
1487 The management interface specified in Clause 22 provides
1488 a simple, two signal, serial interface to connect a
1489 Station Management entity and a managed PHY for providing access
1490 to management parameters and services.
1491 The interface is referred to as the MII management interface.
1497 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1498 The MDIO interface is orthogonal to the MII interface and extends
1499 it by adding access to more registers through indirect addressing.
1504 Send ICMP ECHO_REQUEST to network host
1509 Perform CDP network configuration
1514 Synchronize RTC via network
1519 Lookup the IP of a hostname
1521 config CMD_LINK_LOCAL
1525 Acquire a network IP address using the link-local protocol
1532 Allow control of L2 Ethernet switch commands. These are supported
1533 by the vsc9953 Ethernet driver at present. Sub-commands allow
1534 operations such as enabling / disabling a port and
1535 viewing/maintaining the filtering database (FDB)
1541 Boot image via network using PXE protocol
1546 Wait for wake-on-lan Magic Packet
1550 menu "Misc commands"
1553 bool "Enable 'bmp' command"
1554 depends on LCD || DM_VIDEO || VIDEO
1556 This provides a way to obtain information about a BMP-format image
1557 and to display it. BMP (which presumably stands for BitMaP) is a
1558 file format defined by Microsoft which supports images of various
1559 depths, formats and compression methods. Headers on the file
1560 determine the formats used. This command can be used by first loading
1561 the image into RAM, then using this command to look at it or display
1564 config CMD_BOOTCOUNT
1566 depends on BOOTCOUNT_LIMIT
1568 Enable the bootcount command, which allows interrogation and
1569 reset of the bootcounter.
1572 bool "Enable board-specific commands"
1574 (deprecated: instead, please define a Kconfig option for each command)
1576 Some boards have board-specific commands which are only enabled
1577 during developemnt and need to be turned off for production. This
1578 option provides a way to control this. The commands that are enabled
1579 vary depending on the board.
1581 config CMD_BKOPS_ENABLE
1582 bool "mmc bkops enable"
1586 Enable command for setting manual background operations handshake
1587 on a eMMC device. The feature is optionally available on eMMC devices
1588 conforming to standard >= 4.41.
1590 config CMD_BLOCK_CACHE
1591 bool "blkcache - control and stats for block cache"
1592 depends on BLOCK_CACHE
1593 default y if BLOCK_CACHE
1595 Enable the blkcache command, which can be used to control the
1596 operation of the cache functions.
1597 This is most useful when fine-tuning the operation of the cache
1598 during development, but also allows the cache to be disabled when
1599 it might hurt performance (e.g. when using the ums command).
1602 bool "icache or dcache"
1604 Enable the "icache" and "dcache" commands
1606 config CMD_CONITRACE
1607 bool "conitrace - trace console input codes"
1609 Enable the 'conitrace' command which displays the codes received
1610 from the console input as hexadecimal numbers.
1613 bool "Enable clear screen command 'cls'"
1614 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1617 Enable the 'cls' command which clears the screen contents
1618 on video frame buffer.
1621 bool "efidebug - display/configure UEFI environment"
1622 depends on EFI_LOADER
1623 select EFI_DEVICE_PATH_TO_TEXT
1626 Enable the 'efidebug' command which provides a subset of UEFI
1627 shell utility with simplified functionality. It will be useful
1628 particularly for managing boot parameters as well as examining
1629 various EFI status for debugging.
1631 config CMD_EXCEPTION
1632 bool "exception - raise exception"
1633 depends on ARM || RISCV || X86
1635 Enable the 'exception' command which allows to raise an exception.
1642 Enable the 'led' command which allows for control of LEDs supported
1643 by the board. The LEDs can be listed with 'led list' and controlled
1644 with led on/off/togle/blink. Any LED drivers can be controlled with
1645 this command, e.g. led_gpio.
1652 Enable the 'date' command for getting/setting the time/date in RTC
1658 Run commands and summarize execution time.
1661 bool "gettime - read elapsed time"
1663 Enable the 'gettime' command which reads the elapsed time since
1664 U-Boot started running. This shows the time in seconds and
1665 milliseconds. See also the 'bootstage' command which provides more
1666 flexibility for boot timing.
1668 # TODO: rename to CMD_SLEEP
1673 Delay execution for some time
1676 bool "support for multiprocessor"
1678 This provides an option to brinup
1679 different processors in multiprocessor
1685 Access the system timer.
1691 This provides basic access to the U-Boot's sound support. The main
1692 feature is to play a beep.
1694 sound init - set up sound system
1695 sound play - play a sound
1701 Boot image via local extlinux.conf file
1707 This provides access to the QEMU firmware interface. The main
1708 feature is to allow easy loading of files passed to qemu-system
1709 via -kernel / -initrd
1711 source "cmd/mvebu/Kconfig"
1714 bool "terminal - provides a way to attach a serial terminal"
1716 Provides a 'cu'-like serial terminal command. This can be used to
1717 access other serial ports from the system console. The terminal
1718 is very simple with no special processing of characters. As with
1719 cu, you can press ~. (tilde followed by period) to exit.
1722 bool "uuid, guid - generation of unique IDs"
1725 This enables two commands:
1727 uuid - generate random Universally Unique Identifier
1728 guid - generate Globally Unique Identifier based on random UUID
1730 The two commands are very similar except for the endianness of the
1735 source "cmd/ti/Kconfig"
1737 config CMD_BOOTSTAGE
1738 bool "Enable the 'bootstage' command"
1739 depends on BOOTSTAGE
1741 Add a 'bootstage' command which supports printing a report
1742 and un/stashing of bootstage data.
1744 menu "Power commands"
1746 bool "Enable Driver Model PMIC command"
1749 This is the pmic command, based on a driver model pmic's API.
1750 Command features are unchanged:
1751 - list - list pmic devices
1752 - pmic dev <id> - show or [set] operating pmic device (NEW)
1753 - pmic dump - dump registers
1754 - pmic read address - read byte of register at address
1755 - pmic write address - write byte to register at address
1756 The only one change for this command is 'dev' subcommand.
1758 config CMD_REGULATOR
1759 bool "Enable Driver Model REGULATOR command"
1760 depends on DM_REGULATOR
1762 This command is based on driver model regulator's API.
1763 User interface features:
1764 - list - list regulator devices
1765 - regulator dev <id> - show or [set] operating regulator device
1766 - regulator info - print constraints info
1767 - regulator status - print operating status
1768 - regulator value <val] <-f> - print/[set] voltage value [uV]
1769 - regulator current <val> - print/[set] current value [uA]
1770 - regulator mode <id> - print/[set] operating mode id
1771 - regulator enable - enable the regulator output
1772 - regulator disable - disable the regulator output
1774 The '-f' (force) option can be used for set the value which exceeds
1775 the limits, which are found in device-tree and are kept in regulator's
1776 uclass platdata structure.
1780 menu "Security commands"
1782 bool "Enable the 'aes' command"
1785 This provides a means to encrypt and decrypt data using the AES
1786 (Advanced Encryption Standard). This algorithm uses a symetric key
1787 and is widely used as a streaming cipher. Different key lengths are
1788 supported by the algorithm but this command only supports 128 bits
1792 bool "Enable the 'blob' command"
1794 This is used with the Freescale secure boot mechanism.
1796 Freescale's SEC block has built-in Blob Protocol which provides
1797 a method for protecting user-defined data across system power
1798 cycles. SEC block protects data in a data structure called a Blob,
1799 which provides both confidentiality and integrity protection.
1801 Encapsulating data as a blob
1802 Each time that the Blob Protocol is used to protect data, a
1803 different randomly generated key is used to encrypt the data.
1804 This random key is itself encrypted using a key which is derived
1805 from SoC's non-volatile secret key and a 16 bit Key identifier.
1806 The resulting encrypted key along with encrypted data is called a
1807 blob. The non-volatile secure key is available for use only during
1810 During decapsulation, the reverse process is performed to get back
1814 blob enc - encapsulating data as a cryptgraphic blob
1815 blob dec - decapsulating cryptgraphic blob to get the data
1819 blob enc src dst len km
1821 Encapsulate and create blob of data $len bytes long
1822 at address $src and store the result at address $dst.
1823 $km is the 16 byte key modifier is also required for
1824 generation/use as key for cryptographic operation. Key
1825 modifier should be 16 byte long.
1827 blob dec src dst len km
1829 Decapsulate the blob of data at address $src and
1830 store result of $len byte at addr $dst.
1831 $km is the 16 byte key modifier is also required for
1832 generation/use as key for cryptographic operation. Key
1833 modifier should be 16 byte long.
1836 bool "Support 'hash' command"
1839 This provides a way to hash data in memory using various supported
1840 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1841 saved to memory or to an environment variable. It is also possible
1842 to verify a hash against data in memory.
1845 bool "Support the 'hvc' command"
1846 depends on ARM_SMCCC
1848 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1849 development and testing.
1852 bool "Support the 'smc' command"
1853 depends on ARM_SMCCC
1855 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1856 development and testing.
1862 Add -v option to verify data against a hash.
1872 bool "Enable the 'tpm' command"
1873 depends on TPM_V1 || TPM_V2
1874 select CMD_TPM_V1 if TPM_V1
1875 select CMD_TPM_V2 if TPM_V2
1877 This provides a means to talk to a TPM from the command line. A wide
1878 range of commands if provided - see 'tpm help' for details. The
1879 command requires a suitable TPM on your board and the correct driver
1885 bool "Enable the 'tpm test' command"
1888 This provides a a series of tests to confirm that the TPMv1.x is
1889 working correctly. The tests cover initialisation, non-volatile RAM,
1890 extend, global lock and checking that timing is within expectations.
1891 The tests pass correctly on Infineon TPMs but may need to be adjusted
1898 menu "Firmware commands"
1900 bool "Enable crosec command"
1904 Enable command-line access to the Chrome OS EC (Embedded
1905 Controller). This provides the 'crosec' command which has
1906 a number of sub-commands for performing EC tasks such as
1907 updating its flash, accessing a small saved context area
1908 and talking to the I2C bus behind the EC (if there is one).
1911 menu "Filesystem commands"
1913 bool "Enable the 'btrsubvol' command"
1916 This enables the 'btrsubvol' command to list subvolumes
1917 of a BTRFS filesystem. There are no special commands for
1918 listing BTRFS directories or loading BTRFS files - this
1919 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1920 when BTRFS is enabled (see FS_BTRFS).
1923 bool "Enable the 'cbfs' command"
1926 Define this to enable support for reading from a Coreboot
1927 filesystem. This is a ROM-based filesystem used for accessing files
1928 on systems that use coreboot as the first boot-loader and then load
1929 U-Boot to actually boot the Operating System. Available commands are
1930 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1933 bool "Enable the 'cramfs' command"
1934 depends on FS_CRAMFS
1936 This provides commands for dealing with CRAMFS (Compressed ROM
1937 filesystem). CRAMFS is useful when space is tight since files are
1938 compressed. Two commands are provided:
1940 cramfsls - lists files in a cramfs image
1941 cramfsload - loads a file from a cramfs image
1944 bool "ext2 command support"
1947 Enables EXT2 FS command
1950 bool "ext4 command support"
1953 Enables EXT4 FS command
1955 config CMD_EXT4_WRITE
1957 bool "ext4 write command support"
1960 Enables EXT4 FS write command
1963 bool "FAT command support"
1966 Support for the FAT fs
1968 config CMD_FS_GENERIC
1969 bool "filesystem commands"
1971 Enables filesystem commands (e.g. load, ls) that work for multiple
1975 bool "fsuuid command"
1977 Enables fsuuid command for filesystem UUID.
1980 bool "jffs2 command"
1983 Enables commands to support the JFFS2 (Journalling Flash File System
1984 version 2) filesystem. This enables fsload, ls and fsinfo which
1985 provide the ability to load files, list directories and obtain
1986 filesystem information.
1989 bool "MTD partition support"
1992 MTD partitioning tool support.
1993 It is strongly encouraged to avoid using this command
1994 anymore along with 'sf', 'nand', 'onenand'. One can still
1995 declare the partitions in the mtdparts environment variable
1996 but better use the MTD stack and the 'mtd' command instead.
1998 config CMD_MTDPARTS_SPREAD
1999 bool "Padd partition size to take account of bad blocks"
2000 depends on CMD_MTDPARTS
2002 This enables the 'spread' sub-command of the mtdparts command.
2003 This command will modify the existing mtdparts variable by increasing
2004 the size of the partitions such that 1) each partition's net size is
2005 at least as large as the size specified in the mtdparts variable and
2006 2) each partition starts on a good block.
2008 config CMD_MTDPARTS_SHOW_NET_SIZES
2009 bool "Show net size (w/o bad blocks) of partitions"
2010 depends on CMD_MTDPARTS
2012 Adds two columns to the printed partition table showing the
2013 effective usable size of a partition, if bad blocks are taken
2016 config MTDIDS_DEFAULT
2017 string "Default MTD IDs"
2018 depends on MTD || SPI_FLASH
2020 Defines a default MTD IDs list for use with MTD partitions in the
2021 Linux MTD command line partitions format.
2023 config MTDPARTS_DEFAULT
2024 string "Default MTD partition scheme"
2025 depends on MTD || SPI_FLASH
2027 Defines a default MTD partitioning scheme in the Linux MTD command
2028 line partitions format
2031 bool "reiser - Access to reiserfs filesystems"
2033 This provides two commands which operate on a resierfs filesystem,
2034 commonly used some years ago:
2036 reiserls - list files
2037 reiserload - load a file
2040 bool "yaffs2 - Access of YAFFS2 filesystem"
2044 This provides commands for accessing a YAFFS2 filesystem. Yet
2045 Another Flash Filesystem 2 is a filesystem designed specifically
2046 for NAND flash. It incorporates bad-block management and ensures
2047 that device writes are sequential regardless of filesystem
2051 bool "zfs - Access of ZFS filesystem"
2053 This provides commands to accessing a ZFS filesystem, commonly used
2054 on Solaris systems. Two sub-commands are provided:
2056 zfsls - list files in a directory
2057 zfsload - load a file
2059 See doc/README.zfs for more details.
2063 menu "Debug commands"
2068 The bedbug (emBEDded deBUGger) command provides debugging features
2069 for some PowerPC processors. For details please see the
2070 docuemntation in doc/README.beddbug
2073 bool "diag - Board diagnostics"
2075 This command provides access to board diagnostic tests. These are
2076 called Power-on Self Tests (POST). The command allows listing of
2077 available tests and running either all the tests, or specific tests
2081 bool "irq - Show information about interrupts"
2082 depends on !ARM && !MIPS && !SH
2084 This enables two commands:
2086 interrupts - enable or disable interrupts
2087 irqinfo - print device-specific interrupt information
2090 bool "kgdb - Allow debugging of U-Boot with gdb"
2093 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2094 over a serial link for debugging purposes. This allows
2095 single-stepping, inspecting variables, etc. This is supported only
2096 on PowerPC at present.
2099 bool "log - Generation, control and access to logging"
2102 This provides access to logging features. It allows the output of
2103 log data to be controlled to a limited extent (setting up the default
2104 maximum log level for emitting of records). It also provides access
2105 to a command used for testing the log system.
2108 bool "trace - Support tracing of function calls and timing"
2110 Enables a command to control using of function tracing within
2111 U-Boot. This allows recording of call traces including timing
2112 information. The command can write data to memory for exporting
2113 for analysis (e.g. using bootchart). See doc/README.trace for full
2117 bool "avb - Android Verified Boot 2.0 operations"
2118 depends on AVB_VERIFY
2121 Enables a "avb" command to perform verification of partitions using
2122 Android Verified Boot 2.0 functionality. It includes such subcommands:
2123 avb init - initialize avb2 subsystem
2124 avb read_rb - read rollback index
2125 avb write_rb - write rollback index
2126 avb is_unlocked - check device lock state
2127 avb get_uuid - read and print uuid of a partition
2128 avb read_part - read data from partition
2129 avb read_part_hex - read data from partition and output to stdout
2130 avb write_part - write data to partition
2131 avb verify - run full verification chain
2135 tristate "Enable UBI - Unsorted block images commands"
2138 UBI is a software layer above MTD layer which admits use of LVM-like
2139 logical volumes on top of MTD devices, hides some complexities of
2140 flash chips like wear and bad blocks and provides some other useful
2141 capabilities. Please, consult the MTD web site for more details
2142 (www.linux-mtd.infradead.org). Activate this option if you want
2143 to use U-Boot UBI commands.
2144 It is also strongly encouraged to also enable CONFIG_MTD to get full
2148 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2150 default y if CMD_UBI
2153 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob