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.
30 This string is displayed in the command line to the left of the
33 menu "Autoboot options"
39 This enables the autoboot. See doc/README.autoboot for detail.
42 bool "Stop autobooting via specific input key / string"
45 This option enables stopping (aborting) of the automatic
46 boot feature only by issuing a specific input key or
47 string. If not enabled, any input key will abort the
48 U-Boot automatic booting process and bring the device
49 to the U-Boot prompt for user input.
51 config AUTOBOOT_PROMPT
52 string "Autoboot stop prompt"
53 depends on AUTOBOOT_KEYED
54 default "Autoboot in %d seconds\\n"
56 This string is displayed before the boot delay selected by
57 CONFIG_BOOTDELAY starts. If it is not defined there is no
58 output indicating that autoboot is in progress.
60 Note that this define is used as the (only) argument to a
61 printf() call, so it may contain '%' format specifications,
62 provided that it also includes, sepearated by commas exactly
63 like in a printf statement, the required arguments. It is
64 the responsibility of the user to select only such arguments
65 that are valid in the given context.
67 config AUTOBOOT_ENCRYPTION
68 bool "Enable encryption in autoboot stopping"
69 depends on AUTOBOOT_KEYED
72 config AUTOBOOT_DELAY_STR
73 string "Delay autobooting via specific input key / string"
74 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
76 This option delays the automatic boot feature by issuing
77 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
78 or the environment variable "bootdelaykey" is specified
79 and this string is received from console input before
80 autoboot starts booting, U-Boot gives a command prompt. The
81 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
82 used, otherwise it never times out.
84 config AUTOBOOT_STOP_STR
85 string "Stop autobooting via specific input key / string"
86 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
88 This option enables stopping (aborting) of the automatic
89 boot feature only by issuing a specific input key or
90 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
91 variable "bootstopkey" is specified and this string is
92 received from console input before autoboot starts booting,
93 U-Boot gives a command prompt. The U-Boot prompt never
94 times out, even if CONFIG_BOOT_RETRY_TIME is used.
96 config AUTOBOOT_KEYED_CTRLC
97 bool "Enable Ctrl-C autoboot interruption"
98 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
101 This option allows for the boot sequence to be interrupted
102 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
103 Setting this variable provides an escape sequence from the
104 limited "password" strings.
106 config AUTOBOOT_STOP_STR_SHA256
107 string "Stop autobooting via SHA256 encrypted password"
108 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
110 This option adds the feature to only stop the autobooting,
111 and therefore boot into the U-Boot prompt, when the input
112 string / password matches a values that is encypted via
113 a SHA256 hash and saved in the environment.
117 source "cmd/fastboot/Kconfig"
134 Print ".config" contents.
136 If this option is enabled, the ".config" file contents are embedded
137 in the U-Boot image and can be printed on the console by the "config"
138 command. This provides information of which options are enabled on
145 Print console devices and information.
150 Print information about available CPUs. This normally shows the
151 number of CPUs, type (e.g. manufacturer, architecture, product or
152 internal name) and clock frequency. Other information may be
153 available depending on the CPU driver.
159 Print GPL license text
169 Run the command stored in the environment "bootcmd", i.e.
170 "bootd" does the same thing as "run bootcmd".
176 Boot an application image from the memory.
181 Boot the Linux zImage
188 Boot an AArch64 Linux Kernel image from memory.
192 depends on EFI_LOADER
195 Boot an EFI image from memory.
197 config CMD_BOOTEFI_HELLO_COMPILE
198 bool "Compile a standard EFI hello world binary for testing"
199 depends on CMD_BOOTEFI && (ARM || X86)
202 This compiles a standard EFI hello world application with U-Boot so
203 that it can be used with the test/py testing framework. This is useful
204 for testing that EFI is working at a basic level, and for bringing
205 up EFI support on a new architecture.
207 No additional space will be required in the resulting U-Boot binary
208 when this option is enabled.
210 config CMD_BOOTEFI_HELLO
211 bool "Allow booting a standard EFI hello world for testing"
212 depends on CMD_BOOTEFI_HELLO_COMPILE
214 This adds a standard EFI hello world application to U-Boot so that
215 it can be used with the 'bootefi hello' command. This is useful
216 for testing that EFI is working at a basic level, and for bringing
217 up EFI support on a new architecture.
223 Add an ANSI terminal boot menu command.
226 bool "bootelf, bootvx"
229 Boot an ELF/vxWorks image from the memory.
232 bool "Flattened Device Tree utility commands"
236 Do FDT related setup before booting into the Operating System.
242 Start an application at a given address.
248 Run the command in the given environment variable.
254 Print header information for application image.
260 List all images found in flash
266 Extract a part of a multi-image.
273 menu "Environment commands"
276 bool "ask for env variable"
278 Ask for environment variable
296 Edit environment variable.
301 Allow for searching environment variables
307 Save all environment variables into the compiled-in persistent
310 config CMD_ENV_EXISTS
314 Check if a variable is defined in the environment for use in
317 config CMD_ENV_CALLBACK
318 bool "env callbacks - print callbacks and their associated variables"
320 Some environment variable have callbacks defined by
321 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
322 For example changing "baudrate" adjust the serial baud rate. This
323 command lists the currently defined callbacks.
326 bool "env flags -print variables that have non-default flags"
328 Some environment variables have special flags that control their
329 behaviour. For example, serial# can only be written once and cannot
330 be deleted. This command shows the variables that have special
335 menu "Memory commands"
338 bool "md, mm, nm, mw, cp, cmp, base, loop"
343 mm - memory modify (auto-incrementing address)
344 nm - memory modify (constant address)
345 mw - memory write (fill)
348 base - print or set address offset
349 loop - initialize loop on address range
359 bool "eeprom - EEPROM subsystem"
361 (deprecated, needs conversion to driver model)
362 Provides commands to read and write EEPROM (Electrically Erasable
363 Programmable Read Only Memory) chips that are connected over an
366 config CMD_EEPROM_LAYOUT
367 bool "Enable layout-aware eeprom commands"
368 depends on CMD_EEPROM
370 (deprecated, needs conversion to driver model)
371 When enabled, additional eeprom sub-commands become available.
373 eeprom print - prints the contents of the eeprom in a human-readable
374 way (eeprom layout fields, and data formatted to be fit for human
377 eeprom update - allows user to update eeprom fields by specifying
378 the field name, and providing the new data in a human readable format
379 (same format as displayed by the eeprom print command).
381 Both commands can either auto detect the layout, or be told which
385 __weak int parse_layout_version(char *str)
386 - override to provide your own layout name parsing
387 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
389 - override to setup the layout metadata based on the version
390 __weak int eeprom_layout_detect(unsigned char *data)
391 - override to provide your own algorithm for detecting layout
394 - contains various printing and updating functions for common
395 types of eeprom fields. Can be used for defining
398 config EEPROM_LAYOUT_HELP_STRING
399 string "Tells user what layout names are supported"
400 depends on CMD_EEPROM_LAYOUT
401 default "<not defined>"
403 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
411 Compute MD5 checksum.
416 depends on CMD_MD5SUM
418 Add -v option to verify data against an MD5 checksum.
423 Infinite write loop on address range
428 Simple RAM read/write test.
433 mdc - memory display cyclic
434 mwc - memory write cyclic
439 Display memory information.
443 menu "Compression commands"
449 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
455 Uncompress a zip-compressed memory region.
460 Compress a memory region with zlib deflate method.
464 menu "Device access commands"
467 bool "clk - Show clock frequencies"
470 Shows clock frequences by calling a sock_clk_dump() hook function.
471 This is depreated in favour of using the CLK uclass and accessing
472 clock values from associated drivers. However currently no command
476 bool "dm - Access to driver model information"
480 Provides access to driver model data structures and information,
481 such as a list of devices, list of uclasses and the state of each
482 device (e.g. activated). This is not required for operation, but
483 can be useful to see the state of driver model for debugging or
487 bool "demo - Demonstration commands for driver model"
490 Provides a 'demo' command which can be used to play around with
491 driver model. To use this properly you will need to enable one or
492 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
493 Otherwise you will always get an empty list of devices. The demo
494 devices are defined in the sandbox device tree, so the easiest
495 option is to use sandbox and pass the -d point to sandbox's
499 bool "ide - Support for IDE drivers"
502 Provides an 'ide' command which allows accessing the IDE drive,
503 reseting the IDE interface, printing the partition table and
504 geting device info. It also enables the 'diskboot' command which
505 permits booting from an IDE drive.
508 bool "io - Support for performing I/O accesses"
510 Provides an 'iod' command to display I/O space and an 'iow' command
511 to write values to the I/O space. This can be useful for manually
512 checking the state of devices during boot when debugging device
516 bool "iotrace - Support for tracing I/O activity"
518 Provides an 'iotrace' command which supports recording I/O reads and
519 writes in a trace buffer in memory . It also maintains a checksum
520 of the trace records (even if space is exhausted) so that the
521 sequence of I/O accesses can be verified.
523 When debugging drivers it is useful to see what I/O accesses were
524 done and in what order.
526 Even if the individual accesses are of little interest it can be
527 useful to verify that the access pattern is consistent each time
528 an operation is performed. In this case a checksum can be used to
529 characterise the operation of a driver. The checksum can be compared
530 across different runs of the operation to verify that the driver is
533 In particular, when performing major refactoring of the driver, where
534 the access pattern should not change, the checksum provides assurance
535 that the refactoring work has not broken the driver.
537 This works by sneaking into the io.h heder for an architecture and
538 redirecting I/O accesses through iotrace's tracing mechanism.
540 For now no commands are provided to examine the trace buffer. The
541 format is fairly simple, so 'md' is a reasonable substitute.
543 Note: The checksum feature is only useful for I/O regions where the
544 contents do not change outside of software control. Where this is not
545 suitable you can fall back to manually comparing the addresses. It
546 might be useful to enhance tracing to only checksum the accesses and
547 not the data read/written.
553 Load a binary file over serial line.
559 Load an S-Record file over serial line
562 bool "flinfo, erase, protect"
566 flinfo - print FLASH memory information
568 protect - enable or disable FLASH write protection
571 bool "GPT (GUID Partition Table) command"
572 select PARTITION_UUIDS
575 Enable the 'gpt' command to ready and write GPT style partition
579 #depends on FLASH_CFI_DRIVER
582 ARM Ltd reference designs flash partition access
587 MMC memory mapped support.
591 default y if NAND_SUNXI
596 config CMD_NAND_TRIMFFS
597 bool "nand write.trimffs"
598 default y if ARCH_SUNXI
600 Allows one to skip empty pages when flashing something on a NAND.
602 config CMD_NAND_LOCK_UNLOCK
603 bool "nand lock/unlock"
605 NAND locking support.
607 config CMD_NAND_TORTURE
610 NAND torture support.
616 select PARTITION_UUIDS
618 Read and display information about the partition table on
643 select USB_FUNCTION_DFU
645 Enables the command "dfu" which is used to have U-Boot create a DFU
646 class device via USB.
648 config CMD_USB_MASS_STORAGE
649 bool "UMS usb mass storage"
651 USB mass storage support
659 config CMD_FPGA_LOADBP
660 bool "fpga loadbp - load partial bitstream (Xilinx only)"
663 Supports loading an FPGA device from a bitstream buffer containing
666 config CMD_FPGA_LOADFS
667 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
670 Supports loading an FPGA device from a FAT filesystem.
672 config CMD_FPGA_LOADMK
673 bool "fpga loadmk - load bitstream from image"
676 Supports loading an FPGA device from a image generated by mkimage.
678 config CMD_FPGA_LOADP
679 bool "fpga loadp - load partial bitstream"
682 Supports loading an FPGA device from a bitstream buffer containing
686 bool "fpgad - dump FPGA registers"
688 (legacy, needs conversion to driver model)
689 Provides a way to dump FPGA registers by calling the board-specific
690 fpga_get_reg() function. This functions similarly to the 'md'
694 bool "fuse - support for the fuse subssystem"
696 (deprecated - needs conversion to driver model)
697 This allows reading, sensing, programming or overriding fuses
698 which control the behaviour of the device. The command uses the
701 config CMD_REMOTEPROC
703 depends on REMOTEPROC
705 Support for Remote Processor control
713 bool "fdcboot - Boot from floppy device"
715 The 'fdtboot' command allows booting an image from a floppy disk.
720 menu "Shell scripting commands"
732 Return true/false on integer compare.
738 Run script from memory
744 Evaluate boolean and math expressions and store the result in an env
746 Also supports loading the value at a memory location into a variable.
747 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
751 menu "Network commands"
754 bool "bootp, tftpboot"
759 bootp - boot image via network using BOOTP/TFTP protocol
760 tftpboot - boot image via network using TFTP protocol
765 TFTP put command, for uploading files to a server
770 Act as a TFTP server and boot the first received file
775 Boot image via network using RARP/TFTP protocol
780 Boot image via network using DHCP/TFTP protocol
786 Boot image via network using PXE protocol
792 Boot image via network using NFS protocol.
797 Enable MII utility commands.
802 Send ICMP ECHO_REQUEST to network host
807 Perform CDP network configuration
812 Synchronize RTC via network
817 Lookup the IP of a hostname
819 config CMD_LINK_LOCAL
822 Acquire a network IP address using the link-local protocol
827 Allow control of L2 Ethernet switch commands. These are supported
828 by the vsc9953 Ethernet driver at present. Sub-commands allow
829 operations such as enabling / disabling a port and
830 viewing/maintaining the filtering database (FDB)
837 bool "Enable 'bmp' command"
838 depends on LCD || DM_VIDEO || VIDEO
840 This provides a way to obtain information about a BMP-format iamge
841 and to display it. BMP (which presumably stands for BitMaP) is a
842 file format defined by Microsoft which supports images of various
843 depths, formats and compression methods. Headers on the file
844 determine the formats used. This command can be used by first loading
845 the image into RAM, then using this command to look at it or display
849 bool "Enable board-specific commands"
851 (deprecated: instead, please define a Kconfig option for each command)
853 Some boards have board-specific commands which are only enabled
854 during developemnt and need to be turned off for production. This
855 option provides a way to control this. The commands that are enabled
856 vary depending on the board.
858 config CMD_BKOPS_ENABLE
859 bool "mmc bkops enable"
863 Enable command for setting manual background operations handshake
864 on a eMMC device. The feature is optionally available on eMMC devices
865 conforming to standard >= 4.41.
867 config CMD_BLOCK_CACHE
868 bool "blkcache - control and stats for block cache"
869 depends on BLOCK_CACHE
870 default y if BLOCK_CACHE
872 Enable the blkcache command, which can be used to control the
873 operation of the cache functions.
874 This is most useful when fine-tuning the operation of the cache
875 during development, but also allows the cache to be disabled when
876 it might hurt performance (e.g. when using the ums command).
879 bool "icache or dcache"
881 Enable the "icache" and "dcache" commands
884 bool "Enable the 'display' command, for character displays"
886 (this needs porting to driver model)
887 This enables the 'display' command which allows a string to be
888 displayed on a simple board-specific display. Implement
889 display_putc() to use it.
895 Enable the 'led' command which allows for control of LEDs supported
896 by the board. The LEDs can be listed with 'led list' and controlled
897 with led on/off/togle/blink. Any LED drivers can be controlled with
898 this command, e.g. led_gpio.
904 Enable the 'date' command for getting/setting the time/date in RTC
910 Run commands and summarize execution time.
913 bool "gettime - read elapsed time"
915 Enable the 'gettime' command which reads the elapsed time since
916 U-Boot started running. This shows the time in seconds and
917 milliseconds. See also the 'bootstage' command which provides more
918 flexibility for boot timing.
920 # TODO: rename to CMD_SLEEP
925 Delay execution for some time
930 Access the system timer.
933 bool "getdcr, setdcr, getidcr, setidcr"
937 getdcr - Get an AMCC PPC 4xx DCR's value
938 setdcr - Set an AMCC PPC 4xx DCR's value
939 getidcr - Get a register value via indirect DCR addressing
940 setidcr - Set a register value via indirect DCR addressing
946 This provides basic access to the U-Boot's sound support. The main
947 feature is to play a beep.
949 sound init - set up sound system
950 sound play - play a sound
956 This provides access to the QEMU firmware interface. The main
957 feature is to allow easy loading of files passed to qemu-system
958 via -kernel / -initrd
960 source "cmd/mvebu/Kconfig"
965 bool "Enable the 'bootstage' command"
968 Add a 'bootstage' command which supports printing a report
969 and un/stashing of bootstage data.
971 menu "Power commands"
973 bool "Enable Driver Model PMIC command"
976 This is the pmic command, based on a driver model pmic's API.
977 Command features are unchanged:
978 - list - list pmic devices
979 - pmic dev <id> - show or [set] operating pmic device (NEW)
980 - pmic dump - dump registers
981 - pmic read address - read byte of register at address
982 - pmic write address - write byte to register at address
983 The only one change for this command is 'dev' subcommand.
986 bool "Enable Driver Model REGULATOR command"
987 depends on DM_REGULATOR
989 This command is based on driver model regulator's API.
990 User interface features:
991 - list - list regulator devices
992 - regulator dev <id> - show or [set] operating regulator device
993 - regulator info - print constraints info
994 - regulator status - print operating status
995 - regulator value <val] <-f> - print/[set] voltage value [uV]
996 - regulator current <val> - print/[set] current value [uA]
997 - regulator mode <id> - print/[set] operating mode id
998 - regulator enable - enable the regulator output
999 - regulator disable - disable the regulator output
1001 The '-f' (force) option can be used for set the value which exceeds
1002 the limits, which are found in device-tree and are kept in regulator's
1003 uclass platdata structure.
1007 menu "Security commands"
1009 bool "Enable the 'aes' command"
1012 This provides a means to encrypt and decrypt data using the AES
1013 (Advanced Encryption Standard). This algorithm uses a symetric key
1014 and is widely used as a streaming cipher. Different key lengths are
1015 supported by the algorithm but this command only supports 128 bits
1019 bool "Enable the 'blob' command"
1021 This is used with the Freescale secure boot mechanism.
1023 Freescale's SEC block has built-in Blob Protocol which provides
1024 a method for protecting user-defined data across system power
1025 cycles. SEC block protects data in a data structure called a Blob,
1026 which provides both confidentiality and integrity protection.
1028 Encapsulating data as a blob
1029 Each time that the Blob Protocol is used to protect data, a
1030 different randomly generated key is used to encrypt the data.
1031 This random key is itself encrypted using a key which is derived
1032 from SoC's non-volatile secret key and a 16 bit Key identifier.
1033 The resulting encrypted key along with encrypted data is called a
1034 blob. The non-volatile secure key is available for use only during
1037 During decapsulation, the reverse process is performed to get back
1041 blob enc - encapsulating data as a cryptgraphic blob
1042 blob dec - decapsulating cryptgraphic blob to get the data
1046 blob enc src dst len km
1048 Encapsulate and create blob of data $len bytes long
1049 at address $src and store the result at address $dst.
1050 $km is the 16 byte key modifier is also required for
1051 generation/use as key for cryptographic operation. Key
1052 modifier should be 16 byte long.
1054 blob dec src dst len km
1056 Decapsulate the blob of data at address $src and
1057 store result of $len byte at addr $dst.
1058 $km is the 16 byte key modifier is also required for
1059 generation/use as key for cryptographic operation. Key
1060 modifier should be 16 byte long.
1063 bool "Support 'hash' command"
1066 This provides a way to hash data in memory using various supported
1067 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1068 saved to memory or to an environment variable. It is also possible
1069 to verify a hash against data in memory.
1072 bool "Enable the 'tpm' command"
1075 This provides a means to talk to a TPM from the command line. A wide
1076 range of commands if provided - see 'tpm help' for details. The
1077 command requires a suitable TPM on your board and the correct driver
1081 bool "Enable the 'tpm test' command"
1084 This provides a a series of tests to confirm that the TPM is working
1085 correctly. The tests cover initialisation, non-volatile RAM, extend,
1086 global lock and checking that timing is within expectations. The
1087 tests pass correctly on Infineon TPMs but may need to be adjusted
1092 menu "Firmware commands"
1094 bool "Enable crosec command"
1098 Enable command-line access to the Chrome OS EC (Embedded
1099 Controller). This provides the 'crosec' command which has
1100 a number of sub-commands for performing EC tasks such as
1101 updating its flash, accessing a small saved context area
1102 and talking to the I2C bus behind the EC (if there is one).
1105 menu "Filesystem commands"
1107 bool "Enable the 'cbfs' command"
1110 Define this to enable support for reading from a Coreboot
1111 filesystem. This is a ROM-based filesystem used for accessing files
1112 on systems that use coreboot as the first boot-loader and then load
1113 U-Boot to actually boot the Operating System. Available commands are
1114 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1117 bool "Enable the 'cramfs' command"
1118 depends on FS_CRAMFS
1120 This provides commands for dealing with CRAMFS (Compressed ROM
1121 filesystem). CRAMFS is useful when space is tight since files are
1122 compressed. Two commands are provided:
1124 cramfsls - lists files in a cramfs image
1125 cramfsload - loads a file from a cramfs image
1128 bool "ext2 command support"
1130 Enables EXT2 FS command
1133 bool "ext4 command support"
1135 Enables EXT4 FS command
1137 config CMD_EXT4_WRITE
1139 bool "ext4 write command support"
1141 Enables EXT4 FS write command
1144 bool "FAT command support"
1146 Support for the FAT fs
1148 config CMD_FS_GENERIC
1149 bool "filesystem commands"
1151 Enables filesystem commands (e.g. load, ls) that work for multiple
1155 bool "fsuuid command"
1157 Enables fsuuid command for filesystem UUID.
1160 bool "jffs2 command"
1163 Enables commands to support the JFFS2 (Journalling Flash File System
1164 version 2) filesystem. This enables fsload, ls and fsinfo which
1165 provide the ability to load files, list directories and obtain
1166 filesystem information.
1169 depends on ARCH_SUNXI
1170 bool "MTD partition support"
1172 MTD partition support
1174 config MTDIDS_DEFAULT
1175 string "Default MTD IDs"
1176 depends on CMD_MTDPARTS
1178 Defines a default MTD ID
1180 config MTDPARTS_DEFAULT
1181 string "Default MTD partition scheme"
1182 depends on CMD_MTDPARTS
1184 Defines a default MTD partitioning scheme in the Linux MTD command
1185 line partitions format
1189 menu "Debug commands"
1194 The bedbug (emBEDded deBUGger) command provides debugging features
1195 for some PowerPC processors. For details please see the
1196 docuemntation in doc/README.beddbug
1199 bool "diag - Board diagnostics"
1201 This command provides access to board diagnostic tests. These are
1202 called Power-on Self Tests (POST). The command allows listing of
1203 available tests and running either all the tests, or specific tests
1207 bool "irq - Show information about interrupts"
1208 depends on !ARM && !MIPS && !SH && !MPC512X
1210 This enables two commands:
1212 interrupts - enable or disable interrupts
1213 irqinfo - print device-specific interrupt information
1216 bool "kgdb - Allow debugging of U-Boot with gdb"
1218 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1219 over a serial link for debugging purposes. This allows
1220 single-stepping, inspecting variables, etc. This is supported only
1221 on PowerPC at present.
1226 tristate "Enable UBI - Unsorted block images commands"
1229 default y if NAND_SUNXI
1231 UBI is a software layer above MTD layer which admits use of LVM-like
1232 logical volumes on top of MTD devices, hides some complexities of
1233 flash chips like wear and bad blocks and provides some other useful
1234 capabilities. Please, consult the MTD web site for more details
1235 (www.linux-mtd.infradead.org). Activate this option if you want
1236 to use U-Boot UBI commands.
1239 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1242 select RBTREE if ARCH_SUNXI
1243 select LZO if ARCH_SUNXI
1244 default y if NAND_SUNXI
1246 UBIFS is a file system for flash devices which works on top of UBI.