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
362 Add -v option to verify data against a crc32 checksum.
365 bool "eeprom - EEPROM subsystem"
367 (deprecated, needs conversion to driver model)
368 Provides commands to read and write EEPROM (Electrically Erasable
369 Programmable Read Only Memory) chips that are connected over an
372 config CMD_EEPROM_LAYOUT
373 bool "Enable layout-aware eeprom commands"
374 depends on CMD_EEPROM
376 (deprecated, needs conversion to driver model)
377 When enabled, additional eeprom sub-commands become available.
379 eeprom print - prints the contents of the eeprom in a human-readable
380 way (eeprom layout fields, and data formatted to be fit for human
383 eeprom update - allows user to update eeprom fields by specifying
384 the field name, and providing the new data in a human readable format
385 (same format as displayed by the eeprom print command).
387 Both commands can either auto detect the layout, or be told which
391 __weak int parse_layout_version(char *str)
392 - override to provide your own layout name parsing
393 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
395 - override to setup the layout metadata based on the version
396 __weak int eeprom_layout_detect(unsigned char *data)
397 - override to provide your own algorithm for detecting layout
400 - contains various printing and updating functions for common
401 types of eeprom fields. Can be used for defining
404 config EEPROM_LAYOUT_HELP_STRING
405 string "Tells user what layout names are supported"
406 depends on CMD_EEPROM_LAYOUT
407 default "<not defined>"
409 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
417 Compute MD5 checksum.
422 depends on CMD_MD5SUM
424 Add -v option to verify data against an MD5 checksum.
430 Compute SHA1 checksum.
432 config SHA1SUM_VERIFY
434 depends on CMD_SHA1SUM
436 Add -v option to verify data against a SHA1 checksum.
441 Infinite write loop on address range
446 Simple RAM read/write test.
451 mdc - memory display cyclic
452 mwc - memory write cyclic
457 Display memory information.
461 menu "Compression commands"
467 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
473 Uncompress a zip-compressed memory region.
478 Compress a memory region with zlib deflate method.
482 menu "Device access commands"
485 bool "clk - Show clock frequencies"
488 Shows clock frequences by calling a sock_clk_dump() hook function.
489 This is depreated in favour of using the CLK uclass and accessing
490 clock values from associated drivers. However currently no command
494 bool "dm - Access to driver model information"
498 Provides access to driver model data structures and information,
499 such as a list of devices, list of uclasses and the state of each
500 device (e.g. activated). This is not required for operation, but
501 can be useful to see the state of driver model for debugging or
505 bool "demo - Demonstration commands for driver model"
508 Provides a 'demo' command which can be used to play around with
509 driver model. To use this properly you will need to enable one or
510 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
511 Otherwise you will always get an empty list of devices. The demo
512 devices are defined in the sandbox device tree, so the easiest
513 option is to use sandbox and pass the -d point to sandbox's
517 bool "ide - Support for IDE drivers"
520 Provides an 'ide' command which allows accessing the IDE drive,
521 reseting the IDE interface, printing the partition table and
522 geting device info. It also enables the 'diskboot' command which
523 permits booting from an IDE drive.
526 bool "io - Support for performing I/O accesses"
528 Provides an 'iod' command to display I/O space and an 'iow' command
529 to write values to the I/O space. This can be useful for manually
530 checking the state of devices during boot when debugging device
534 bool "iotrace - Support for tracing I/O activity"
536 Provides an 'iotrace' command which supports recording I/O reads and
537 writes in a trace buffer in memory . It also maintains a checksum
538 of the trace records (even if space is exhausted) so that the
539 sequence of I/O accesses can be verified.
541 When debugging drivers it is useful to see what I/O accesses were
542 done and in what order.
544 Even if the individual accesses are of little interest it can be
545 useful to verify that the access pattern is consistent each time
546 an operation is performed. In this case a checksum can be used to
547 characterise the operation of a driver. The checksum can be compared
548 across different runs of the operation to verify that the driver is
551 In particular, when performing major refactoring of the driver, where
552 the access pattern should not change, the checksum provides assurance
553 that the refactoring work has not broken the driver.
555 This works by sneaking into the io.h heder for an architecture and
556 redirecting I/O accesses through iotrace's tracing mechanism.
558 For now no commands are provided to examine the trace buffer. The
559 format is fairly simple, so 'md' is a reasonable substitute.
561 Note: The checksum feature is only useful for I/O regions where the
562 contents do not change outside of software control. Where this is not
563 suitable you can fall back to manually comparing the addresses. It
564 might be useful to enhance tracing to only checksum the accesses and
565 not the data read/written.
571 Load a binary file over serial line.
577 Load an S-Record file over serial line
580 bool "flinfo, erase, protect"
584 flinfo - print FLASH memory information
586 protect - enable or disable FLASH write protection
589 bool "GPT (GUID Partition Table) command"
590 select PARTITION_UUIDS
593 Enable the 'gpt' command to ready and write GPT style partition
597 #depends on FLASH_CFI_DRIVER
600 ARM Ltd reference designs flash partition access
605 MMC memory mapped support.
609 default y if NAND_SUNXI
614 config CMD_NAND_TRIMFFS
615 bool "nand write.trimffs"
616 default y if ARCH_SUNXI
618 Allows one to skip empty pages when flashing something on a NAND.
620 config CMD_NAND_LOCK_UNLOCK
621 bool "nand lock/unlock"
623 NAND locking support.
625 config CMD_NAND_TORTURE
628 NAND torture support.
634 select PARTITION_UUIDS
636 Read and display information about the partition table on
661 select USB_FUNCTION_DFU
663 Enables the command "dfu" which is used to have U-Boot create a DFU
664 class device via USB.
666 config CMD_USB_MASS_STORAGE
667 bool "UMS usb mass storage"
669 USB mass storage support
677 config CMD_FPGA_LOADBP
678 bool "fpga loadbp - load partial bitstream (Xilinx only)"
681 Supports loading an FPGA device from a bitstream buffer containing
684 config CMD_FPGA_LOADFS
685 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
688 Supports loading an FPGA device from a FAT filesystem.
690 config CMD_FPGA_LOADMK
691 bool "fpga loadmk - load bitstream from image"
694 Supports loading an FPGA device from a image generated by mkimage.
696 config CMD_FPGA_LOADP
697 bool "fpga loadp - load partial bitstream"
700 Supports loading an FPGA device from a bitstream buffer containing
704 bool "fpgad - dump FPGA registers"
706 (legacy, needs conversion to driver model)
707 Provides a way to dump FPGA registers by calling the board-specific
708 fpga_get_reg() function. This functions similarly to the 'md'
712 bool "fuse - support for the fuse subssystem"
714 (deprecated - needs conversion to driver model)
715 This allows reading, sensing, programming or overriding fuses
716 which control the behaviour of the device. The command uses the
719 config CMD_REMOTEPROC
721 depends on REMOTEPROC
723 Support for Remote Processor control
731 bool "fdcboot - Boot from floppy device"
733 The 'fdtboot' command allows booting an image from a floppy disk.
738 menu "Shell scripting commands"
750 Return true/false on integer compare.
756 Run script from memory
762 Evaluate boolean and math expressions and store the result in an env
764 Also supports loading the value at a memory location into a variable.
765 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
769 menu "Network commands"
772 bool "bootp, tftpboot"
777 bootp - boot image via network using BOOTP/TFTP protocol
778 tftpboot - boot image via network using TFTP protocol
783 TFTP put command, for uploading files to a server
788 Act as a TFTP server and boot the first received file
793 Boot image via network using RARP/TFTP protocol
798 Boot image via network using DHCP/TFTP protocol
804 Boot image via network using PXE protocol
810 Boot image via network using NFS protocol.
815 Enable MII utility commands.
820 Send ICMP ECHO_REQUEST to network host
825 Perform CDP network configuration
830 Synchronize RTC via network
835 Lookup the IP of a hostname
837 config CMD_LINK_LOCAL
840 Acquire a network IP address using the link-local protocol
845 Allow control of L2 Ethernet switch commands. These are supported
846 by the vsc9953 Ethernet driver at present. Sub-commands allow
847 operations such as enabling / disabling a port and
848 viewing/maintaining the filtering database (FDB)
855 bool "Enable 'bmp' command"
856 depends on LCD || DM_VIDEO || VIDEO
858 This provides a way to obtain information about a BMP-format iamge
859 and to display it. BMP (which presumably stands for BitMaP) is a
860 file format defined by Microsoft which supports images of various
861 depths, formats and compression methods. Headers on the file
862 determine the formats used. This command can be used by first loading
863 the image into RAM, then using this command to look at it or display
867 bool "Enable board-specific commands"
869 (deprecated: instead, please define a Kconfig option for each command)
871 Some boards have board-specific commands which are only enabled
872 during developemnt and need to be turned off for production. This
873 option provides a way to control this. The commands that are enabled
874 vary depending on the board.
876 config CMD_BKOPS_ENABLE
877 bool "mmc bkops enable"
881 Enable command for setting manual background operations handshake
882 on a eMMC device. The feature is optionally available on eMMC devices
883 conforming to standard >= 4.41.
885 config CMD_BLOCK_CACHE
886 bool "blkcache - control and stats for block cache"
887 depends on BLOCK_CACHE
888 default y if BLOCK_CACHE
890 Enable the blkcache command, which can be used to control the
891 operation of the cache functions.
892 This is most useful when fine-tuning the operation of the cache
893 during development, but also allows the cache to be disabled when
894 it might hurt performance (e.g. when using the ums command).
897 bool "icache or dcache"
899 Enable the "icache" and "dcache" commands
902 bool "Enable the 'display' command, for character displays"
904 (this needs porting to driver model)
905 This enables the 'display' command which allows a string to be
906 displayed on a simple board-specific display. Implement
907 display_putc() to use it.
913 Enable the 'led' command which allows for control of LEDs supported
914 by the board. The LEDs can be listed with 'led list' and controlled
915 with led on/off/togle/blink. Any LED drivers can be controlled with
916 this command, e.g. led_gpio.
922 Enable the 'date' command for getting/setting the time/date in RTC
928 Run commands and summarize execution time.
931 bool "gettime - read elapsed time"
933 Enable the 'gettime' command which reads the elapsed time since
934 U-Boot started running. This shows the time in seconds and
935 milliseconds. See also the 'bootstage' command which provides more
936 flexibility for boot timing.
938 # TODO: rename to CMD_SLEEP
943 Delay execution for some time
948 Access the system timer.
951 bool "getdcr, setdcr, getidcr, setidcr"
955 getdcr - Get an AMCC PPC 4xx DCR's value
956 setdcr - Set an AMCC PPC 4xx DCR's value
957 getidcr - Get a register value via indirect DCR addressing
958 setidcr - Set a register value via indirect DCR addressing
964 This provides basic access to the U-Boot's sound support. The main
965 feature is to play a beep.
967 sound init - set up sound system
968 sound play - play a sound
974 This provides access to the QEMU firmware interface. The main
975 feature is to allow easy loading of files passed to qemu-system
976 via -kernel / -initrd
978 source "cmd/mvebu/Kconfig"
983 bool "Enable the 'bootstage' command"
986 Add a 'bootstage' command which supports printing a report
987 and un/stashing of bootstage data.
989 menu "Power commands"
991 bool "Enable Driver Model PMIC command"
994 This is the pmic command, based on a driver model pmic's API.
995 Command features are unchanged:
996 - list - list pmic devices
997 - pmic dev <id> - show or [set] operating pmic device (NEW)
998 - pmic dump - dump registers
999 - pmic read address - read byte of register at address
1000 - pmic write address - write byte to register at address
1001 The only one change for this command is 'dev' subcommand.
1003 config CMD_REGULATOR
1004 bool "Enable Driver Model REGULATOR command"
1005 depends on DM_REGULATOR
1007 This command is based on driver model regulator's API.
1008 User interface features:
1009 - list - list regulator devices
1010 - regulator dev <id> - show or [set] operating regulator device
1011 - regulator info - print constraints info
1012 - regulator status - print operating status
1013 - regulator value <val] <-f> - print/[set] voltage value [uV]
1014 - regulator current <val> - print/[set] current value [uA]
1015 - regulator mode <id> - print/[set] operating mode id
1016 - regulator enable - enable the regulator output
1017 - regulator disable - disable the regulator output
1019 The '-f' (force) option can be used for set the value which exceeds
1020 the limits, which are found in device-tree and are kept in regulator's
1021 uclass platdata structure.
1025 menu "Security commands"
1027 bool "Enable the 'aes' command"
1030 This provides a means to encrypt and decrypt data using the AES
1031 (Advanced Encryption Standard). This algorithm uses a symetric key
1032 and is widely used as a streaming cipher. Different key lengths are
1033 supported by the algorithm but this command only supports 128 bits
1037 bool "Enable the 'blob' command"
1039 This is used with the Freescale secure boot mechanism.
1041 Freescale's SEC block has built-in Blob Protocol which provides
1042 a method for protecting user-defined data across system power
1043 cycles. SEC block protects data in a data structure called a Blob,
1044 which provides both confidentiality and integrity protection.
1046 Encapsulating data as a blob
1047 Each time that the Blob Protocol is used to protect data, a
1048 different randomly generated key is used to encrypt the data.
1049 This random key is itself encrypted using a key which is derived
1050 from SoC's non-volatile secret key and a 16 bit Key identifier.
1051 The resulting encrypted key along with encrypted data is called a
1052 blob. The non-volatile secure key is available for use only during
1055 During decapsulation, the reverse process is performed to get back
1059 blob enc - encapsulating data as a cryptgraphic blob
1060 blob dec - decapsulating cryptgraphic blob to get the data
1064 blob enc src dst len km
1066 Encapsulate and create blob of data $len bytes long
1067 at address $src and store the result at address $dst.
1068 $km is the 16 byte key modifier is also required for
1069 generation/use as key for cryptographic operation. Key
1070 modifier should be 16 byte long.
1072 blob dec src dst len km
1074 Decapsulate the blob of data at address $src and
1075 store result of $len byte at addr $dst.
1076 $km is the 16 byte key modifier is also required for
1077 generation/use as key for cryptographic operation. Key
1078 modifier should be 16 byte long.
1081 bool "Support 'hash' command"
1084 This provides a way to hash data in memory using various supported
1085 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1086 saved to memory or to an environment variable. It is also possible
1087 to verify a hash against data in memory.
1093 Add -v option to verify data against a hash.
1096 bool "Enable the 'tpm' command"
1099 This provides a means to talk to a TPM from the command line. A wide
1100 range of commands if provided - see 'tpm help' for details. The
1101 command requires a suitable TPM on your board and the correct driver
1105 bool "Enable the 'tpm test' command"
1108 This provides a a series of tests to confirm that the TPM is working
1109 correctly. The tests cover initialisation, non-volatile RAM, extend,
1110 global lock and checking that timing is within expectations. The
1111 tests pass correctly on Infineon TPMs but may need to be adjusted
1116 menu "Firmware commands"
1118 bool "Enable crosec command"
1122 Enable command-line access to the Chrome OS EC (Embedded
1123 Controller). This provides the 'crosec' command which has
1124 a number of sub-commands for performing EC tasks such as
1125 updating its flash, accessing a small saved context area
1126 and talking to the I2C bus behind the EC (if there is one).
1129 menu "Filesystem commands"
1131 bool "Enable the 'cbfs' command"
1134 Define this to enable support for reading from a Coreboot
1135 filesystem. This is a ROM-based filesystem used for accessing files
1136 on systems that use coreboot as the first boot-loader and then load
1137 U-Boot to actually boot the Operating System. Available commands are
1138 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1141 bool "Enable the 'cramfs' command"
1142 depends on FS_CRAMFS
1144 This provides commands for dealing with CRAMFS (Compressed ROM
1145 filesystem). CRAMFS is useful when space is tight since files are
1146 compressed. Two commands are provided:
1148 cramfsls - lists files in a cramfs image
1149 cramfsload - loads a file from a cramfs image
1152 bool "ext2 command support"
1154 Enables EXT2 FS command
1157 bool "ext4 command support"
1159 Enables EXT4 FS command
1161 config CMD_EXT4_WRITE
1163 bool "ext4 write command support"
1165 Enables EXT4 FS write command
1168 bool "FAT command support"
1171 Support for the FAT fs
1173 config CMD_FS_GENERIC
1174 bool "filesystem commands"
1176 Enables filesystem commands (e.g. load, ls) that work for multiple
1180 bool "fsuuid command"
1182 Enables fsuuid command for filesystem UUID.
1185 bool "jffs2 command"
1188 Enables commands to support the JFFS2 (Journalling Flash File System
1189 version 2) filesystem. This enables fsload, ls and fsinfo which
1190 provide the ability to load files, list directories and obtain
1191 filesystem information.
1194 depends on ARCH_SUNXI
1195 bool "MTD partition support"
1197 MTD partition support
1199 config MTDIDS_DEFAULT
1200 string "Default MTD IDs"
1201 depends on CMD_MTDPARTS
1203 Defines a default MTD ID
1205 config MTDPARTS_DEFAULT
1206 string "Default MTD partition scheme"
1207 depends on CMD_MTDPARTS
1209 Defines a default MTD partitioning scheme in the Linux MTD command
1210 line partitions format
1214 menu "Debug commands"
1219 The bedbug (emBEDded deBUGger) command provides debugging features
1220 for some PowerPC processors. For details please see the
1221 docuemntation in doc/README.beddbug
1224 bool "diag - Board diagnostics"
1226 This command provides access to board diagnostic tests. These are
1227 called Power-on Self Tests (POST). The command allows listing of
1228 available tests and running either all the tests, or specific tests
1232 bool "irq - Show information about interrupts"
1233 depends on !ARM && !MIPS && !SH && !MPC512X
1235 This enables two commands:
1237 interrupts - enable or disable interrupts
1238 irqinfo - print device-specific interrupt information
1241 bool "kgdb - Allow debugging of U-Boot with gdb"
1243 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1244 over a serial link for debugging purposes. This allows
1245 single-stepping, inspecting variables, etc. This is supported only
1246 on PowerPC at present.
1251 tristate "Enable UBI - Unsorted block images commands"
1254 default y if NAND_SUNXI
1256 UBI is a software layer above MTD layer which admits use of LVM-like
1257 logical volumes on top of MTD devices, hides some complexities of
1258 flash chips like wear and bad blocks and provides some other useful
1259 capabilities. Please, consult the MTD web site for more details
1260 (www.linux-mtd.infradead.org). Activate this option if you want
1261 to use U-Boot UBI commands.
1264 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1267 select RBTREE if ARCH_SUNXI
1268 select LZO if ARCH_SUNXI
1269 default y if NAND_SUNXI
1271 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob