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 "fdcboot - Boot from floppy device"
864 The 'fdtboot' command allows booting an image from a floppy disk.
867 bool "flinfo, erase, protect"
869 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
872 flinfo - print FLASH memory information
874 protect - enable or disable FLASH write protection
883 config CMD_FPGA_LOADBP
884 bool "fpga loadbp - load partial bitstream (Xilinx only)"
887 Supports loading an FPGA device from a bitstream buffer containing
890 config CMD_FPGA_LOADFS
891 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
894 Supports loading an FPGA device from a FAT filesystem.
896 config CMD_FPGA_LOADMK
897 bool "fpga loadmk - load bitstream from image"
900 Supports loading an FPGA device from a image generated by mkimage.
902 config CMD_FPGA_LOADP
903 bool "fpga loadp - load partial bitstream"
906 Supports loading an FPGA device from a bitstream buffer containing
909 config CMD_FPGA_LOAD_SECURE
910 bool "fpga loads - loads secure bitstreams (Xilinx only)"
913 Enables the fpga loads command which is used to load secure
914 (authenticated or encrypted or both) bitstreams on to FPGA.
917 bool "fpgad - dump FPGA registers"
919 (legacy, needs conversion to driver model)
920 Provides a way to dump FPGA registers by calling the board-specific
921 fpga_get_reg() function. This functions similarly to the 'md'
925 bool "fuse - support for the fuse subssystem"
927 (deprecated - needs conversion to driver model)
928 This allows reading, sensing, programming or overriding fuses
929 which control the behaviour of the device. The command uses the
938 bool "GPT (GUID Partition Table) command"
940 select HAVE_BLOCK_DEVICE
941 select PARTITION_UUIDS
944 Enable the 'gpt' command to ready and write GPT style partition
948 bool "GPT Random UUID generation"
951 Enable the generation of partitions with random UUIDs if none
954 config CMD_GPT_RENAME
955 bool "GPT partition renaming commands"
958 Enables the 'gpt' command to interchange names on two GPT
959 partitions via the 'gpt swap' command or to rename single
960 partitions via the 'rename' command.
963 bool "ide - Support for IDE drivers"
966 Provides an 'ide' command which allows accessing the IDE drive,
967 reseting the IDE interface, printing the partition table and
968 geting device info. It also enables the 'diskboot' command which
969 permits booting from an IDE drive.
972 bool "io - Support for performing I/O accesses"
974 Provides an 'iod' command to display I/O space and an 'iow' command
975 to write values to the I/O space. This can be useful for manually
976 checking the state of devices during boot when debugging device
980 bool "iotrace - Support for tracing I/O activity"
982 Provides an 'iotrace' command which supports recording I/O reads and
983 writes in a trace buffer in memory . It also maintains a checksum
984 of the trace records (even if space is exhausted) so that the
985 sequence of I/O accesses can be verified.
987 When debugging drivers it is useful to see what I/O accesses were
988 done and in what order.
990 Even if the individual accesses are of little interest it can be
991 useful to verify that the access pattern is consistent each time
992 an operation is performed. In this case a checksum can be used to
993 characterise the operation of a driver. The checksum can be compared
994 across different runs of the operation to verify that the driver is
997 In particular, when performing major refactoring of the driver, where
998 the access pattern should not change, the checksum provides assurance
999 that the refactoring work has not broken the driver.
1001 This works by sneaking into the io.h heder for an architecture and
1002 redirecting I/O accesses through iotrace's tracing mechanism.
1004 For now no commands are provided to examine the trace buffer. The
1005 format is fairly simple, so 'md' is a reasonable substitute.
1007 Note: The checksum feature is only useful for I/O regions where the
1008 contents do not change outside of software control. Where this is not
1009 suitable you can fall back to manually comparing the addresses. It
1010 might be useful to enhance tracing to only checksum the accesses and
1011 not the data read/written.
1021 bool "w1 - Support for Dallas 1-Wire protocol"
1023 Dallas 1-wire protocol support
1029 Load a binary file over serial line.
1035 Load an S-Record file over serial line
1040 MMC memory mapped support.
1043 bool "Enable support for RPMB in the mmc command"
1046 Enable the commands for reading, writing and programming the
1047 key for the Replay Protection Memory Block partition in eMMC.
1049 config CMD_MMC_SWRITE
1051 depends on CMD_MMC && MMC_WRITE
1054 Enable support for the "mmc swrite" command to write Android sparse
1060 select MTD_PARTITIONS
1062 MTD commands support.
1066 default y if NAND_SUNXI
1067 depends on MTD_RAW_NAND
1072 config CMD_NAND_TRIMFFS
1073 bool "nand write.trimffs"
1074 default y if ARCH_SUNXI
1076 Allows one to skip empty pages when flashing something on a NAND.
1078 config CMD_NAND_LOCK_UNLOCK
1079 bool "nand lock/unlock"
1081 NAND locking support.
1083 config CMD_NAND_TORTURE
1086 NAND torture support.
1095 NVM Express device support
1098 bool "onenand - access to onenand device"
1101 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1102 various useful features. This command allows reading, writing,
1103 and erasing blocks. It allso provides a way to show and change
1104 bad blocks, and test the device.
1109 Enable the 'osd' command which allows to query information from and
1110 write text data to a on-screen display (OSD) device; a virtual device
1111 associated with a display capable of displaying a text overlay on the
1112 display it's associated with..
1116 select HAVE_BLOCK_DEVICE
1117 select PARTITION_UUIDS
1119 Read and display information about the partition table on
1123 bool "pci - Access PCI devices"
1125 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1126 used on some devices to allow the CPU to communicate with its
1127 peripherals. Sub-commands allow bus enumeration, displaying and
1128 changing configuration space and a few other features.
1131 bool "pinmux - show pins muxing"
1132 default y if PINCTRL
1134 Parse all available pin-controllers and show pins muxing. This
1135 is useful for debug purpoer to check the pin muxing and to know if
1136 a pin is configured as a GPIO or as an alternate function.
1141 Poweroff/Shutdown the system
1144 bool "read - Read binary data from a partition"
1146 Provides low-level access to the data in a partition.
1148 config CMD_REMOTEPROC
1150 depends on REMOTEPROC
1152 Support for Remote Processor control
1155 bool "sata - Access SATA subsystem"
1158 SATA (Serial Advanced Technology Attachment) is a serial bus
1159 standard for connecting to hard drives and other storage devices.
1160 This command provides information about attached devices and allows
1161 reading, writing and other operations.
1163 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1164 Attachment, where AT refers to an IBM AT (Advanced Technology)
1165 computer released in 1984.
1168 bool "saves - Save a file over serial in S-Record format"
1170 Provides a way to save a binary file using the Motorola S-Record
1171 format over the serial line.
1174 bool "scsi - Access to SCSI devices"
1177 This provides a 'scsi' command which provides access to SCSI (Small
1178 Computer System Interface) devices. The command provides a way to
1179 scan the bus, reset the bus, read and write data and get information
1183 bool "sdram - Print SDRAM configuration information"
1185 Provides information about attached SDRAM. This assumed that the
1186 SDRAM has an EEPROM with information that can be read using the
1187 I2C bus. This is only available on some boards.
1191 depends on DM_SPI_FLASH || SPI_FLASH
1192 default y if DM_SPI_FLASH
1197 bool "sf test - Allow testing of SPI flash"
1200 Provides a way to test that SPI flash is working correctly. The
1201 test is destructive, in that an area of SPI flash must be provided
1202 for the test to use. Performance information is also provided,
1203 measuring the performance of reading, writing and erasing in
1204 Mbps (Million Bits Per Second). This value should approximately
1205 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1206 everything is working properly.
1209 bool "sspi - Command to access spi device"
1212 SPI utility command.
1214 config DEFAULT_SPI_BUS
1215 int "default spi bus used by sspi command"
1219 config DEFAULT_SPI_MODE
1220 hex "default spi mode used by sspi command (see include/spi.h)"
1225 bool "tsi148 - Command to access tsi148 device"
1227 This provides various sub-commands to initialise and configure the
1228 Turndra tsi148 device. See the command help for full details.
1231 bool "Enable UFS - Universal Flash Subsystem commands"
1234 "This provides commands to initialise and configure universal flash
1238 bool "universe - Command to set up the Turndra Universe controller"
1240 This allows setting up the VMEbus provided by this controller.
1241 See the command help for full details.
1245 select HAVE_BLOCK_DEVICE
1251 select USB_FUNCTION_SDP
1253 Enables the command "sdp" which is used to have U-Boot emulating the
1254 Serial Download Protocol (SDP) via USB.
1258 depends on USB_FUNCTION_ROCKUSB
1260 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1261 read/write info, image to/from devices. This enable rockusb command
1262 support to communication with rockusb device. for more detail about
1263 this command, please read doc/README.rockusb.
1265 config CMD_USB_MASS_STORAGE
1266 bool "UMS usb mass storage"
1267 select USB_FUNCTION_MASS_STORAGE
1269 USB mass storage support
1276 VirtIO block device support
1282 This provides commands to control the watchdog timer devices.
1288 Enable the command "axi" for accessing AXI (Advanced eXtensible
1289 Interface) busses, a on-chip interconnect specification for managing
1290 functional blocks in SoC designs, which is also often used in designs
1291 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1295 menu "Shell scripting commands"
1301 Echo args to console
1307 Return true/false on integer compare.
1313 Run script from memory
1319 Evaluate boolean and math expressions and store the result in an env
1321 Also supports loading the value at a memory location into a variable.
1322 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1326 menu "Android support commands"
1328 config CMD_AB_SELECT
1331 depends on ANDROID_AB
1333 On Android devices with more than one boot slot (multiple copies of
1334 the kernel and system images) this provides a command to select which
1335 slot should be used to boot from and register the boot attempt. This
1336 is used by the new A/B update model where one slot is updated in the
1337 background while running from the other slot.
1344 bool "Network commands"
1354 bootp - boot image via network using BOOTP/TFTP protocol
1358 depends on CMD_BOOTP
1360 Boot image via network using DHCP/TFTP protocol
1362 config BOOTP_BOOTPATH
1363 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1365 depends on CMD_BOOTP
1367 Even though the config is called BOOTP_BOOTPATH, it stores the
1368 path in the variable 'rootpath'.
1371 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1373 depends on CMD_BOOTP
1375 The primary DNS server is stored as 'dnsip'. If two servers are
1376 returned, you must set BOOTP_DNS2 to store that second server IP
1380 bool "Store 'dnsip2' from BOOTP/DHCP server"
1381 depends on BOOTP_DNS
1383 If a DHCP client requests the DNS server IP from a DHCP server,
1384 it is possible that more than one DNS serverip is offered to the
1385 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1386 server IP will be stored in the additional environment
1387 variable "dnsip2". The first DNS serverip is always
1388 stored in the variable "dnsip", when BOOTP_DNS is defined.
1390 config BOOTP_GATEWAY
1391 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1393 depends on CMD_BOOTP
1395 config BOOTP_HOSTNAME
1396 bool "Request & store 'hostname' from BOOTP/DHCP server"
1398 depends on CMD_BOOTP
1400 The name may or may not be qualified with the local domain name.
1402 config BOOTP_PREFER_SERVERIP
1403 bool "serverip variable takes precedent over DHCP server IP."
1404 depends on CMD_BOOTP
1406 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1408 With this option enabled, the 'serverip' variable in the environment
1409 takes precedence over DHCP server IP and will only be set by the DHCP
1410 server if not already set in the environment.
1412 config BOOTP_SUBNETMASK
1413 bool "Request & store 'netmask' from BOOTP/DHCP server"
1415 depends on CMD_BOOTP
1417 config BOOTP_NTPSERVER
1418 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1419 depends on CMD_BOOTP
1424 Selecting this will allow capturing all Ethernet packets and store
1425 them in physical memory in a PCAP formated file,
1426 later to be analyzed by PCAP reader application (IE. WireShark).
1429 bool "Send PXE client arch to BOOTP/DHCP server"
1431 depends on CMD_BOOTP && CMD_PXE
1433 Supported for ARM, ARM64, and x86 for now.
1435 config BOOTP_PXE_CLIENTARCH
1437 depends on BOOTP_PXE
1438 default 0x16 if ARM64
1442 config BOOTP_VCI_STRING
1444 depends on CMD_BOOTP
1445 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1446 default "U-Boot.armv8" if ARM64
1447 default "U-Boot.arm" if ARM
1454 tftpboot - boot image via network using TFTP protocol
1458 depends on CMD_TFTPBOOT
1460 TFTP put command, for uploading files to a server
1464 depends on CMD_TFTPBOOT
1466 Act as a TFTP server and boot the first received file
1468 config NET_TFTP_VARS
1469 bool "Control TFTP timeout and count through environment"
1470 depends on CMD_TFTPBOOT
1473 If set, allows controlling the TFTP timeout through the
1474 environment variable tftptimeout, and the TFTP maximum
1475 timeout count through the variable tftptimeoutcountmax.
1476 If unset, timeout and maximum are hard-defined as 1 second
1477 and 10 timouts per TFTP transfer.
1482 Boot image via network using RARP/TFTP protocol
1488 Boot image via network using NFS protocol.
1494 If set, allows 802.3(clause 22) MII Management functions interface access
1495 The management interface specified in Clause 22 provides
1496 a simple, two signal, serial interface to connect a
1497 Station Management entity and a managed PHY for providing access
1498 to management parameters and services.
1499 The interface is referred to as the MII management interface.
1505 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1506 The MDIO interface is orthogonal to the MII interface and extends
1507 it by adding access to more registers through indirect addressing.
1512 Send ICMP ECHO_REQUEST to network host
1517 Perform CDP network configuration
1522 Synchronize RTC via network
1527 Lookup the IP of a hostname
1529 config CMD_LINK_LOCAL
1533 Acquire a network IP address using the link-local protocol
1540 Allow control of L2 Ethernet switch commands. These are supported
1541 by the vsc9953 Ethernet driver at present. Sub-commands allow
1542 operations such as enabling / disabling a port and
1543 viewing/maintaining the filtering database (FDB)
1549 Boot image via network using PXE protocol
1554 Wait for wake-on-lan Magic Packet
1558 menu "Misc commands"
1561 bool "Enable 'bmp' command"
1562 depends on LCD || DM_VIDEO || VIDEO
1564 This provides a way to obtain information about a BMP-format image
1565 and to display it. BMP (which presumably stands for BitMaP) is a
1566 file format defined by Microsoft which supports images of various
1567 depths, formats and compression methods. Headers on the file
1568 determine the formats used. This command can be used by first loading
1569 the image into RAM, then using this command to look at it or display
1572 config CMD_BOOTCOUNT
1574 depends on BOOTCOUNT_LIMIT
1576 Enable the bootcount command, which allows interrogation and
1577 reset of the bootcounter.
1580 bool "Enable board-specific commands"
1582 (deprecated: instead, please define a Kconfig option for each command)
1584 Some boards have board-specific commands which are only enabled
1585 during developemnt and need to be turned off for production. This
1586 option provides a way to control this. The commands that are enabled
1587 vary depending on the board.
1589 config CMD_BKOPS_ENABLE
1590 bool "mmc bkops enable"
1594 Enable command for setting manual background operations handshake
1595 on a eMMC device. The feature is optionally available on eMMC devices
1596 conforming to standard >= 4.41.
1598 config CMD_BLOCK_CACHE
1599 bool "blkcache - control and stats for block cache"
1600 depends on BLOCK_CACHE
1601 default y if BLOCK_CACHE
1603 Enable the blkcache command, which can be used to control the
1604 operation of the cache functions.
1605 This is most useful when fine-tuning the operation of the cache
1606 during development, but also allows the cache to be disabled when
1607 it might hurt performance (e.g. when using the ums command).
1610 bool "icache or dcache"
1612 Enable the "icache" and "dcache" commands
1614 config CMD_CONITRACE
1615 bool "conitrace - trace console input codes"
1617 Enable the 'conitrace' command which displays the codes received
1618 from the console input as hexadecimal numbers.
1621 bool "Enable clear screen command 'cls'"
1622 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1625 Enable the 'cls' command which clears the screen contents
1626 on video frame buffer.
1629 bool "efidebug - display/configure UEFI environment"
1630 depends on EFI_LOADER
1631 select EFI_DEVICE_PATH_TO_TEXT
1634 Enable the 'efidebug' command which provides a subset of UEFI
1635 shell utility with simplified functionality. It will be useful
1636 particularly for managing boot parameters as well as examining
1637 various EFI status for debugging.
1639 config CMD_EXCEPTION
1640 bool "exception - raise exception"
1641 depends on ARM || RISCV || X86
1643 Enable the 'exception' command which allows to raise an exception.
1650 Enable the 'led' command which allows for control of LEDs supported
1651 by the board. The LEDs can be listed with 'led list' and controlled
1652 with led on/off/togle/blink. Any LED drivers can be controlled with
1653 this command, e.g. led_gpio.
1660 Enable the 'date' command for getting/setting the time/date in RTC
1666 Run commands and summarize execution time.
1669 bool "gettime - read elapsed time"
1671 Enable the 'gettime' command which reads the elapsed time since
1672 U-Boot started running. This shows the time in seconds and
1673 milliseconds. See also the 'bootstage' command which provides more
1674 flexibility for boot timing.
1681 Print bytes from the hardware random number generator.
1683 # TODO: rename to CMD_SLEEP
1688 Delay execution for some time
1691 bool "support for multiprocessor"
1693 This provides an option to brinup
1694 different processors in multiprocessor
1700 Access the system timer.
1706 This provides basic access to the U-Boot's sound support. The main
1707 feature is to play a beep.
1709 sound init - set up sound system
1710 sound play - play a sound
1716 Boot image via local extlinux.conf file
1722 This provides access to the QEMU firmware interface. The main
1723 feature is to allow easy loading of files passed to qemu-system
1724 via -kernel / -initrd
1726 source "cmd/mvebu/Kconfig"
1729 bool "terminal - provides a way to attach a serial terminal"
1731 Provides a 'cu'-like serial terminal command. This can be used to
1732 access other serial ports from the system console. The terminal
1733 is very simple with no special processing of characters. As with
1734 cu, you can press ~. (tilde followed by period) to exit.
1737 bool "uuid, guid - generation of unique IDs"
1740 This enables two commands:
1742 uuid - generate random Universally Unique Identifier
1743 guid - generate Globally Unique Identifier based on random UUID
1745 The two commands are very similar except for the endianness of the
1750 source "cmd/ti/Kconfig"
1752 config CMD_BOOTSTAGE
1753 bool "Enable the 'bootstage' command"
1754 depends on BOOTSTAGE
1756 Add a 'bootstage' command which supports printing a report
1757 and un/stashing of bootstage data.
1759 menu "Power commands"
1761 bool "Enable Driver Model PMIC command"
1764 This is the pmic command, based on a driver model pmic's API.
1765 Command features are unchanged:
1766 - list - list pmic devices
1767 - pmic dev <id> - show or [set] operating pmic device (NEW)
1768 - pmic dump - dump registers
1769 - pmic read address - read byte of register at address
1770 - pmic write address - write byte to register at address
1771 The only one change for this command is 'dev' subcommand.
1773 config CMD_REGULATOR
1774 bool "Enable Driver Model REGULATOR command"
1775 depends on DM_REGULATOR
1777 This command is based on driver model regulator's API.
1778 User interface features:
1779 - list - list regulator devices
1780 - regulator dev <id> - show or [set] operating regulator device
1781 - regulator info - print constraints info
1782 - regulator status - print operating status
1783 - regulator value <val] <-f> - print/[set] voltage value [uV]
1784 - regulator current <val> - print/[set] current value [uA]
1785 - regulator mode <id> - print/[set] operating mode id
1786 - regulator enable - enable the regulator output
1787 - regulator disable - disable the regulator output
1789 The '-f' (force) option can be used for set the value which exceeds
1790 the limits, which are found in device-tree and are kept in regulator's
1791 uclass platdata structure.
1795 menu "Security commands"
1797 bool "Enable the 'aes' command"
1800 This provides a means to encrypt and decrypt data using the AES
1801 (Advanced Encryption Standard). This algorithm uses a symetric key
1802 and is widely used as a streaming cipher. Different key lengths are
1803 supported by the algorithm but this command only supports 128 bits
1807 bool "Enable the 'blob' command"
1809 This is used with the Freescale secure boot mechanism.
1811 Freescale's SEC block has built-in Blob Protocol which provides
1812 a method for protecting user-defined data across system power
1813 cycles. SEC block protects data in a data structure called a Blob,
1814 which provides both confidentiality and integrity protection.
1816 Encapsulating data as a blob
1817 Each time that the Blob Protocol is used to protect data, a
1818 different randomly generated key is used to encrypt the data.
1819 This random key is itself encrypted using a key which is derived
1820 from SoC's non-volatile secret key and a 16 bit Key identifier.
1821 The resulting encrypted key along with encrypted data is called a
1822 blob. The non-volatile secure key is available for use only during
1825 During decapsulation, the reverse process is performed to get back
1829 blob enc - encapsulating data as a cryptgraphic blob
1830 blob dec - decapsulating cryptgraphic blob to get the data
1834 blob enc src dst len km
1836 Encapsulate and create blob of data $len bytes long
1837 at address $src and store the result at address $dst.
1838 $km is the 16 byte key modifier is also required for
1839 generation/use as key for cryptographic operation. Key
1840 modifier should be 16 byte long.
1842 blob dec src dst len km
1844 Decapsulate the blob of data at address $src and
1845 store result of $len byte at addr $dst.
1846 $km is the 16 byte key modifier is also required for
1847 generation/use as key for cryptographic operation. Key
1848 modifier should be 16 byte long.
1851 bool "Support 'hash' command"
1854 This provides a way to hash data in memory using various supported
1855 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1856 saved to memory or to an environment variable. It is also possible
1857 to verify a hash against data in memory.
1860 bool "Support the 'hvc' command"
1861 depends on ARM_SMCCC
1863 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1864 development and testing.
1867 bool "Support the 'smc' command"
1868 depends on ARM_SMCCC
1870 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1871 development and testing.
1877 Add -v option to verify data against a hash.
1887 bool "Enable the 'tpm' command"
1888 depends on TPM_V1 || TPM_V2
1889 select CMD_TPM_V1 if TPM_V1
1890 select CMD_TPM_V2 if TPM_V2
1892 This provides a means to talk to a TPM from the command line. A wide
1893 range of commands if provided - see 'tpm help' for details. The
1894 command requires a suitable TPM on your board and the correct driver
1900 bool "Enable the 'tpm test' command"
1903 This provides a a series of tests to confirm that the TPMv1.x is
1904 working correctly. The tests cover initialisation, non-volatile RAM,
1905 extend, global lock and checking that timing is within expectations.
1906 The tests pass correctly on Infineon TPMs but may need to be adjusted
1913 menu "Firmware commands"
1915 bool "Enable crosec command"
1919 Enable command-line access to the Chrome OS EC (Embedded
1920 Controller). This provides the 'crosec' command which has
1921 a number of sub-commands for performing EC tasks such as
1922 updating its flash, accessing a small saved context area
1923 and talking to the I2C bus behind the EC (if there is one).
1926 menu "Filesystem commands"
1928 bool "Enable the 'btrsubvol' command"
1931 This enables the 'btrsubvol' command to list subvolumes
1932 of a BTRFS filesystem. There are no special commands for
1933 listing BTRFS directories or loading BTRFS files - this
1934 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1935 when BTRFS is enabled (see FS_BTRFS).
1938 bool "Enable the 'cbfs' command"
1941 Define this to enable support for reading from a Coreboot
1942 filesystem. This is a ROM-based filesystem used for accessing files
1943 on systems that use coreboot as the first boot-loader and then load
1944 U-Boot to actually boot the Operating System. Available commands are
1945 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1948 bool "Enable the 'cramfs' command"
1949 depends on FS_CRAMFS
1951 This provides commands for dealing with CRAMFS (Compressed ROM
1952 filesystem). CRAMFS is useful when space is tight since files are
1953 compressed. Two commands are provided:
1955 cramfsls - lists files in a cramfs image
1956 cramfsload - loads a file from a cramfs image
1959 bool "ext2 command support"
1962 Enables EXT2 FS command
1965 bool "ext4 command support"
1968 Enables EXT4 FS command
1970 config CMD_EXT4_WRITE
1972 bool "ext4 write command support"
1975 Enables EXT4 FS write command
1978 bool "FAT command support"
1981 Support for the FAT fs
1983 config CMD_FS_GENERIC
1984 bool "filesystem commands"
1986 Enables filesystem commands (e.g. load, ls) that work for multiple
1990 bool "fsuuid command"
1992 Enables fsuuid command for filesystem UUID.
1995 bool "jffs2 command"
1998 Enables commands to support the JFFS2 (Journalling Flash File System
1999 version 2) filesystem. This enables fsload, ls and fsinfo which
2000 provide the ability to load files, list directories and obtain
2001 filesystem information.
2004 bool "MTD partition support"
2007 MTD partitioning tool support.
2008 It is strongly encouraged to avoid using this command
2009 anymore along with 'sf', 'nand', 'onenand'. One can still
2010 declare the partitions in the mtdparts environment variable
2011 but better use the MTD stack and the 'mtd' command instead.
2013 config CMD_MTDPARTS_SPREAD
2014 bool "Padd partition size to take account of bad blocks"
2015 depends on CMD_MTDPARTS
2017 This enables the 'spread' sub-command of the mtdparts command.
2018 This command will modify the existing mtdparts variable by increasing
2019 the size of the partitions such that 1) each partition's net size is
2020 at least as large as the size specified in the mtdparts variable and
2021 2) each partition starts on a good block.
2023 config CMD_MTDPARTS_SHOW_NET_SIZES
2024 bool "Show net size (w/o bad blocks) of partitions"
2025 depends on CMD_MTDPARTS
2027 Adds two columns to the printed partition table showing the
2028 effective usable size of a partition, if bad blocks are taken
2031 config MTDIDS_DEFAULT
2032 string "Default MTD IDs"
2033 depends on MTD || SPI_FLASH
2035 Defines a default MTD IDs list for use with MTD partitions in the
2036 Linux MTD command line partitions format.
2038 config MTDPARTS_DEFAULT
2039 string "Default MTD partition scheme"
2040 depends on MTD || SPI_FLASH
2042 Defines a default MTD partitioning scheme in the Linux MTD command
2043 line partitions format
2046 bool "reiser - Access to reiserfs filesystems"
2048 This provides two commands which operate on a resierfs filesystem,
2049 commonly used some years ago:
2051 reiserls - list files
2052 reiserload - load a file
2055 bool "yaffs2 - Access of YAFFS2 filesystem"
2059 This provides commands for accessing a YAFFS2 filesystem. Yet
2060 Another Flash Filesystem 2 is a filesystem designed specifically
2061 for NAND flash. It incorporates bad-block management and ensures
2062 that device writes are sequential regardless of filesystem
2066 bool "zfs - Access of ZFS filesystem"
2068 This provides commands to accessing a ZFS filesystem, commonly used
2069 on Solaris systems. Two sub-commands are provided:
2071 zfsls - list files in a directory
2072 zfsload - load a file
2074 See doc/README.zfs for more details.
2078 menu "Debug commands"
2083 The bedbug (emBEDded deBUGger) command provides debugging features
2084 for some PowerPC processors. For details please see the
2085 docuemntation in doc/README.beddbug
2088 bool "diag - Board diagnostics"
2090 This command provides access to board diagnostic tests. These are
2091 called Power-on Self Tests (POST). The command allows listing of
2092 available tests and running either all the tests, or specific tests
2096 bool "irq - Show information about interrupts"
2097 depends on !ARM && !MIPS && !SH
2099 This enables two commands:
2101 interrupts - enable or disable interrupts
2102 irqinfo - print device-specific interrupt information
2105 bool "kgdb - Allow debugging of U-Boot with gdb"
2108 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2109 over a serial link for debugging purposes. This allows
2110 single-stepping, inspecting variables, etc. This is supported only
2111 on PowerPC at present.
2114 bool "log - Generation, control and access to logging"
2117 This provides access to logging features. It allows the output of
2118 log data to be controlled to a limited extent (setting up the default
2119 maximum log level for emitting of records). It also provides access
2120 to a command used for testing the log system.
2123 bool "trace - Support tracing of function calls and timing"
2125 Enables a command to control using of function tracing within
2126 U-Boot. This allows recording of call traces including timing
2127 information. The command can write data to memory for exporting
2128 for analysis (e.g. using bootchart). See doc/README.trace for full
2132 bool "avb - Android Verified Boot 2.0 operations"
2133 depends on AVB_VERIFY
2136 Enables a "avb" command to perform verification of partitions using
2137 Android Verified Boot 2.0 functionality. It includes such subcommands:
2138 avb init - initialize avb2 subsystem
2139 avb read_rb - read rollback index
2140 avb write_rb - write rollback index
2141 avb is_unlocked - check device lock state
2142 avb get_uuid - read and print uuid of a partition
2143 avb read_part - read data from partition
2144 avb read_part_hex - read data from partition and output to stdout
2145 avb write_part - write data to partition
2146 avb verify - run full verification chain
2150 tristate "Enable UBI - Unsorted block images commands"
2153 UBI is a software layer above MTD layer which admits use of LVM-like
2154 logical volumes on top of MTD devices, hides some complexities of
2155 flash chips like wear and bad blocks and provides some other useful
2156 capabilities. Please, consult the MTD web site for more details
2157 (www.linux-mtd.infradead.org). Activate this option if you want
2158 to use U-Boot UBI commands.
2159 It is also strongly encouraged to also enable CONFIG_MTD to get full
2163 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2165 default y if CMD_UBI
2168 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob