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
175 Run the command stored in the environment "bootcmd", i.e.
176 "bootd" does the same thing as "run bootcmd".
182 Boot an application image from the memory.
187 Boot the Linux zImage
194 Boot an AArch64 Linux Kernel image from memory.
198 depends on EFI_LOADER
201 Boot an EFI image from memory.
203 config CMD_BOOTEFI_HELLO_COMPILE
204 bool "Compile a standard EFI hello world binary for testing"
205 depends on CMD_BOOTEFI && (ARM || X86)
208 This compiles a standard EFI hello world application with U-Boot so
209 that it can be used with the test/py testing framework. This is useful
210 for testing that EFI is working at a basic level, and for bringing
211 up EFI support on a new architecture.
213 No additional space will be required in the resulting U-Boot binary
214 when this option is enabled.
216 config CMD_BOOTEFI_HELLO
217 bool "Allow booting a standard EFI hello world for testing"
218 depends on CMD_BOOTEFI_HELLO_COMPILE
220 This adds a standard EFI hello world application to U-Boot so that
221 it can be used with the 'bootefi hello' command. This is useful
222 for testing that EFI is working at a basic level, and for bringing
223 up EFI support on a new architecture.
229 Add an ANSI terminal boot menu command.
232 bool "bootelf, bootvx"
235 Boot an ELF/vxWorks image from the memory.
238 bool "Flattened Device Tree utility commands"
242 Do FDT related setup before booting into the Operating System.
248 Start an application at a given address.
254 Run the command in the given environment variable.
260 Print header information for application image.
266 List all images found in flash
272 Extract a part of a multi-image.
277 Poweroff/Shutdown the system
281 menu "Environment commands"
284 bool "ask for env variable"
286 Ask for environment variable
304 Edit environment variable.
309 Allow for searching environment variables
315 Save all environment variables into the compiled-in persistent
318 config CMD_ENV_EXISTS
322 Check if a variable is defined in the environment for use in
325 config CMD_ENV_CALLBACK
326 bool "env callbacks - print callbacks and their associated variables"
328 Some environment variable have callbacks defined by
329 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
330 For example changing "baudrate" adjust the serial baud rate. This
331 command lists the currently defined callbacks.
334 bool "env flags -print variables that have non-default flags"
336 Some environment variables have special flags that control their
337 behaviour. For example, serial# can only be written once and cannot
338 be deleted. This command shows the variables that have special
343 menu "Memory commands"
346 bool "md, mm, nm, mw, cp, cmp, base, loop"
351 mm - memory modify (auto-incrementing address)
352 nm - memory modify (constant address)
353 mw - memory write (fill)
356 base - print or set address offset
357 loop - initialize loop on address range
370 Add -v option to verify data against a crc32 checksum.
373 bool "eeprom - EEPROM subsystem"
375 (deprecated, needs conversion to driver model)
376 Provides commands to read and write EEPROM (Electrically Erasable
377 Programmable Read Only Memory) chips that are connected over an
380 config CMD_EEPROM_LAYOUT
381 bool "Enable layout-aware eeprom commands"
382 depends on CMD_EEPROM
384 (deprecated, needs conversion to driver model)
385 When enabled, additional eeprom sub-commands become available.
387 eeprom print - prints the contents of the eeprom in a human-readable
388 way (eeprom layout fields, and data formatted to be fit for human
391 eeprom update - allows user to update eeprom fields by specifying
392 the field name, and providing the new data in a human readable format
393 (same format as displayed by the eeprom print command).
395 Both commands can either auto detect the layout, or be told which
399 __weak int parse_layout_version(char *str)
400 - override to provide your own layout name parsing
401 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
403 - override to setup the layout metadata based on the version
404 __weak int eeprom_layout_detect(unsigned char *data)
405 - override to provide your own algorithm for detecting layout
408 - contains various printing and updating functions for common
409 types of eeprom fields. Can be used for defining
412 config EEPROM_LAYOUT_HELP_STRING
413 string "Tells user what layout names are supported"
414 depends on CMD_EEPROM_LAYOUT
415 default "<not defined>"
417 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
425 Compute MD5 checksum.
430 depends on CMD_MD5SUM
432 Add -v option to verify data against an MD5 checksum.
438 Compute SHA1 checksum.
440 config SHA1SUM_VERIFY
442 depends on CMD_SHA1SUM
444 Add -v option to verify data against a SHA1 checksum.
449 Infinite write loop on address range
454 Simple RAM read/write test.
459 mdc - memory display cyclic
460 mwc - memory write cyclic
465 Display memory information.
469 menu "Compression commands"
475 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
481 Uncompress a zip-compressed memory region.
486 Compress a memory region with zlib deflate method.
490 menu "Device access commands"
493 #depends on FLASH_CFI_DRIVER
496 ARM Ltd reference designs flash partition access
499 bool "clk - Show clock frequencies"
502 Shows clock frequences by calling a sock_clk_dump() hook function.
503 This is depreated in favour of using the CLK uclass and accessing
504 clock values from associated drivers. However currently no command
508 bool "demo - Demonstration commands for driver model"
511 Provides a 'demo' command which can be used to play around with
512 driver model. To use this properly you will need to enable one or
513 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
514 Otherwise you will always get an empty list of devices. The demo
515 devices are defined in the sandbox device tree, so the easiest
516 option is to use sandbox and pass the -d point to sandbox's
521 select USB_FUNCTION_DFU
523 Enables the command "dfu" which is used to have U-Boot create a DFU
524 class device via USB.
527 bool "dm - Access to driver model information"
531 Provides access to driver model data structures and information,
532 such as a list of devices, list of uclasses and the state of each
533 device (e.g. activated). This is not required for operation, but
534 can be useful to see the state of driver model for debugging or
538 bool "fdcboot - Boot from floppy device"
540 The 'fdtboot' command allows booting an image from a floppy disk.
543 bool "flinfo, erase, protect"
547 flinfo - print FLASH memory information
549 protect - enable or disable FLASH write protection
557 config CMD_FPGA_LOADBP
558 bool "fpga loadbp - load partial bitstream (Xilinx only)"
561 Supports loading an FPGA device from a bitstream buffer containing
564 config CMD_FPGA_LOADFS
565 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
568 Supports loading an FPGA device from a FAT filesystem.
570 config CMD_FPGA_LOADMK
571 bool "fpga loadmk - load bitstream from image"
574 Supports loading an FPGA device from a image generated by mkimage.
576 config CMD_FPGA_LOADP
577 bool "fpga loadp - load partial bitstream"
580 Supports loading an FPGA device from a bitstream buffer containing
584 bool "fpgad - dump FPGA registers"
586 (legacy, needs conversion to driver model)
587 Provides a way to dump FPGA registers by calling the board-specific
588 fpga_get_reg() function. This functions similarly to the 'md'
592 bool "fuse - support for the fuse subssystem"
594 (deprecated - needs conversion to driver model)
595 This allows reading, sensing, programming or overriding fuses
596 which control the behaviour of the device. The command uses the
605 bool "GPT (GUID Partition Table) command"
606 select PARTITION_UUIDS
609 Enable the 'gpt' command to ready and write GPT style partition
612 config CMD_GPT_RENAME
613 bool "GPT partition renaming commands"
616 Enables the 'gpt' command to interchange names on two GPT
617 partitions via the 'gpt swap' command or to rename single
618 partitions via the 'rename' command.
621 bool "ide - Support for IDE drivers"
624 Provides an 'ide' command which allows accessing the IDE drive,
625 reseting the IDE interface, printing the partition table and
626 geting device info. It also enables the 'diskboot' command which
627 permits booting from an IDE drive.
630 bool "io - Support for performing I/O accesses"
632 Provides an 'iod' command to display I/O space and an 'iow' command
633 to write values to the I/O space. This can be useful for manually
634 checking the state of devices during boot when debugging device
638 bool "iotrace - Support for tracing I/O activity"
640 Provides an 'iotrace' command which supports recording I/O reads and
641 writes in a trace buffer in memory . It also maintains a checksum
642 of the trace records (even if space is exhausted) so that the
643 sequence of I/O accesses can be verified.
645 When debugging drivers it is useful to see what I/O accesses were
646 done and in what order.
648 Even if the individual accesses are of little interest it can be
649 useful to verify that the access pattern is consistent each time
650 an operation is performed. In this case a checksum can be used to
651 characterise the operation of a driver. The checksum can be compared
652 across different runs of the operation to verify that the driver is
655 In particular, when performing major refactoring of the driver, where
656 the access pattern should not change, the checksum provides assurance
657 that the refactoring work has not broken the driver.
659 This works by sneaking into the io.h heder for an architecture and
660 redirecting I/O accesses through iotrace's tracing mechanism.
662 For now no commands are provided to examine the trace buffer. The
663 format is fairly simple, so 'md' is a reasonable substitute.
665 Note: The checksum feature is only useful for I/O regions where the
666 contents do not change outside of software control. Where this is not
667 suitable you can fall back to manually comparing the addresses. It
668 might be useful to enhance tracing to only checksum the accesses and
669 not the data read/written.
680 Load a binary file over serial line.
686 Load an S-Record file over serial line
691 MMC memory mapped support.
695 default y if NAND_SUNXI
700 config CMD_NAND_TRIMFFS
701 bool "nand write.trimffs"
702 default y if ARCH_SUNXI
704 Allows one to skip empty pages when flashing something on a NAND.
706 config CMD_NAND_LOCK_UNLOCK
707 bool "nand lock/unlock"
709 NAND locking support.
711 config CMD_NAND_TORTURE
714 NAND torture support.
719 bool "mmc_spi - Set up MMC SPI device"
721 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
722 Peripheral Interface) device. The device provides a means of
723 accessing an MMC device via SPI using a single data line, limited
724 to 20MHz. It is useful since it reduces the amount of protocol code
728 bool "onenand - access to onenand device"
730 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
731 various useful features. This command allows reading, writing,
732 and erasing blocks. It allso provides a way to show and change
733 bad blocks, and test the device.
737 select PARTITION_UUIDS
739 Read and display information about the partition table on
743 bool "pci - Access PCI devices"
745 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
746 used on some devices to allow the CPU to communicate with its
747 peripherals. Sub-commands allow bus enumeration, displaying and
748 changing configuration space and a few other features.
751 bool "pinit - Set up PCMCIA device"
753 Provides a means to initialise a PCMCIA (Personal Computer Memory
754 Card International Association) device. This is an old standard from
755 about 1990. These devices are typically removable memory or network
756 cards using a standard 68-pin connector.
759 bool "read - Read binary data from a partition"
761 Provides low-level access to the data in a partition.
763 config CMD_REMOTEPROC
765 depends on REMOTEPROC
767 Support for Remote Processor control
770 bool "sata - Access SATA subsystem"
773 SATA (Serial Advanced Technology Attachment) is a serial bus
774 standard for connecting to hard drives and other storage devices.
775 This command provides information about attached devices and allows
776 reading, writing and other operations.
778 SATA replaces PATA (originally just ATA), which stands for Parallel AT
779 Attachment, where AT refers to an IBM AT (Advanced Technology)
780 computer released in 1984.
783 bool "saves - Save a file over serial in S-Record format"
785 Provides a way to save a binary file using the Motorola S-Record
786 format over the serial line.
789 bool "sdram - Print SDRAM configuration information"
791 Provides information about attached SDRAM. This assumed that the
792 SDRAM has an EEPROM with information that can be read using the
793 I2C bus. This is only available on some boards.
801 bool "sf test - Allow testing of SPI flash"
803 Provides a way to test that SPI flash is working correctly. The
804 test is destructive, in that an area of SPI flash must be provided
805 for the test to use. Performance information is also provided,
806 measuring the performance of reading, writing and erasing in
807 Mbps (Million Bits Per Second). This value should approximately
808 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
809 everything is working properly.
821 config CMD_USB_MASS_STORAGE
822 bool "UMS usb mass storage"
824 USB mass storage support
829 menu "Shell scripting commands"
841 Return true/false on integer compare.
847 Run script from memory
853 Evaluate boolean and math expressions and store the result in an env
855 Also supports loading the value at a memory location into a variable.
856 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
860 menu "Network commands"
863 bool "bootp, tftpboot"
868 bootp - boot image via network using BOOTP/TFTP protocol
869 tftpboot - boot image via network using TFTP protocol
874 TFTP put command, for uploading files to a server
879 Act as a TFTP server and boot the first received file
884 Boot image via network using RARP/TFTP protocol
889 Boot image via network using DHCP/TFTP protocol
895 Boot image via network using PXE protocol
901 Boot image via network using NFS protocol.
906 Enable MII utility commands.
911 Send ICMP ECHO_REQUEST to network host
916 Perform CDP network configuration
921 Synchronize RTC via network
926 Lookup the IP of a hostname
928 config CMD_LINK_LOCAL
931 Acquire a network IP address using the link-local protocol
936 Allow control of L2 Ethernet switch commands. These are supported
937 by the vsc9953 Ethernet driver at present. Sub-commands allow
938 operations such as enabling / disabling a port and
939 viewing/maintaining the filtering database (FDB)
946 bool "Enable 'bmp' command"
947 depends on LCD || DM_VIDEO || VIDEO
949 This provides a way to obtain information about a BMP-format iamge
950 and to display it. BMP (which presumably stands for BitMaP) is a
951 file format defined by Microsoft which supports images of various
952 depths, formats and compression methods. Headers on the file
953 determine the formats used. This command can be used by first loading
954 the image into RAM, then using this command to look at it or display
958 bool "Enable board-specific commands"
960 (deprecated: instead, please define a Kconfig option for each command)
962 Some boards have board-specific commands which are only enabled
963 during developemnt and need to be turned off for production. This
964 option provides a way to control this. The commands that are enabled
965 vary depending on the board.
967 config CMD_BKOPS_ENABLE
968 bool "mmc bkops enable"
972 Enable command for setting manual background operations handshake
973 on a eMMC device. The feature is optionally available on eMMC devices
974 conforming to standard >= 4.41.
976 config CMD_BLOCK_CACHE
977 bool "blkcache - control and stats for block cache"
978 depends on BLOCK_CACHE
979 default y if BLOCK_CACHE
981 Enable the blkcache command, which can be used to control the
982 operation of the cache functions.
983 This is most useful when fine-tuning the operation of the cache
984 during development, but also allows the cache to be disabled when
985 it might hurt performance (e.g. when using the ums command).
988 bool "icache or dcache"
990 Enable the "icache" and "dcache" commands
993 bool "Enable the 'display' command, for character displays"
995 (this needs porting to driver model)
996 This enables the 'display' command which allows a string to be
997 displayed on a simple board-specific display. Implement
998 display_putc() to use it.
1004 Enable the 'led' command which allows for control of LEDs supported
1005 by the board. The LEDs can be listed with 'led list' and controlled
1006 with led on/off/togle/blink. Any LED drivers can be controlled with
1007 this command, e.g. led_gpio.
1013 Enable the 'date' command for getting/setting the time/date in RTC
1019 Run commands and summarize execution time.
1022 bool "gettime - read elapsed time"
1024 Enable the 'gettime' command which reads the elapsed time since
1025 U-Boot started running. This shows the time in seconds and
1026 milliseconds. See also the 'bootstage' command which provides more
1027 flexibility for boot timing.
1029 # TODO: rename to CMD_SLEEP
1034 Delay execution for some time
1039 Access the system timer.
1045 This provides basic access to the U-Boot's sound support. The main
1046 feature is to play a beep.
1048 sound init - set up sound system
1049 sound play - play a sound
1055 This provides access to the QEMU firmware interface. The main
1056 feature is to allow easy loading of files passed to qemu-system
1057 via -kernel / -initrd
1059 source "cmd/mvebu/Kconfig"
1063 config CMD_BOOTSTAGE
1064 bool "Enable the 'bootstage' command"
1065 depends on BOOTSTAGE
1067 Add a 'bootstage' command which supports printing a report
1068 and un/stashing of bootstage data.
1070 menu "Power commands"
1072 bool "Enable Driver Model PMIC command"
1075 This is the pmic command, based on a driver model pmic's API.
1076 Command features are unchanged:
1077 - list - list pmic devices
1078 - pmic dev <id> - show or [set] operating pmic device (NEW)
1079 - pmic dump - dump registers
1080 - pmic read address - read byte of register at address
1081 - pmic write address - write byte to register at address
1082 The only one change for this command is 'dev' subcommand.
1084 config CMD_REGULATOR
1085 bool "Enable Driver Model REGULATOR command"
1086 depends on DM_REGULATOR
1088 This command is based on driver model regulator's API.
1089 User interface features:
1090 - list - list regulator devices
1091 - regulator dev <id> - show or [set] operating regulator device
1092 - regulator info - print constraints info
1093 - regulator status - print operating status
1094 - regulator value <val] <-f> - print/[set] voltage value [uV]
1095 - regulator current <val> - print/[set] current value [uA]
1096 - regulator mode <id> - print/[set] operating mode id
1097 - regulator enable - enable the regulator output
1098 - regulator disable - disable the regulator output
1100 The '-f' (force) option can be used for set the value which exceeds
1101 the limits, which are found in device-tree and are kept in regulator's
1102 uclass platdata structure.
1106 menu "Security commands"
1108 bool "Enable the 'aes' command"
1111 This provides a means to encrypt and decrypt data using the AES
1112 (Advanced Encryption Standard). This algorithm uses a symetric key
1113 and is widely used as a streaming cipher. Different key lengths are
1114 supported by the algorithm but this command only supports 128 bits
1118 bool "Enable the 'blob' command"
1120 This is used with the Freescale secure boot mechanism.
1122 Freescale's SEC block has built-in Blob Protocol which provides
1123 a method for protecting user-defined data across system power
1124 cycles. SEC block protects data in a data structure called a Blob,
1125 which provides both confidentiality and integrity protection.
1127 Encapsulating data as a blob
1128 Each time that the Blob Protocol is used to protect data, a
1129 different randomly generated key is used to encrypt the data.
1130 This random key is itself encrypted using a key which is derived
1131 from SoC's non-volatile secret key and a 16 bit Key identifier.
1132 The resulting encrypted key along with encrypted data is called a
1133 blob. The non-volatile secure key is available for use only during
1136 During decapsulation, the reverse process is performed to get back
1140 blob enc - encapsulating data as a cryptgraphic blob
1141 blob dec - decapsulating cryptgraphic blob to get the data
1145 blob enc src dst len km
1147 Encapsulate and create blob of data $len bytes long
1148 at address $src and store the result at address $dst.
1149 $km is the 16 byte key modifier is also required for
1150 generation/use as key for cryptographic operation. Key
1151 modifier should be 16 byte long.
1153 blob dec src dst len km
1155 Decapsulate the blob of data at address $src and
1156 store result of $len byte at addr $dst.
1157 $km is the 16 byte key modifier is also required for
1158 generation/use as key for cryptographic operation. Key
1159 modifier should be 16 byte long.
1162 bool "Support 'hash' command"
1165 This provides a way to hash data in memory using various supported
1166 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1167 saved to memory or to an environment variable. It is also possible
1168 to verify a hash against data in memory.
1174 Add -v option to verify data against a hash.
1177 bool "Enable the 'tpm' command"
1180 This provides a means to talk to a TPM from the command line. A wide
1181 range of commands if provided - see 'tpm help' for details. The
1182 command requires a suitable TPM on your board and the correct driver
1186 bool "Enable the 'tpm test' command"
1189 This provides a a series of tests to confirm that the TPM is working
1190 correctly. The tests cover initialisation, non-volatile RAM, extend,
1191 global lock and checking that timing is within expectations. The
1192 tests pass correctly on Infineon TPMs but may need to be adjusted
1197 menu "Firmware commands"
1199 bool "Enable crosec command"
1203 Enable command-line access to the Chrome OS EC (Embedded
1204 Controller). This provides the 'crosec' command which has
1205 a number of sub-commands for performing EC tasks such as
1206 updating its flash, accessing a small saved context area
1207 and talking to the I2C bus behind the EC (if there is one).
1210 menu "Filesystem commands"
1212 bool "Enable the 'cbfs' command"
1215 Define this to enable support for reading from a Coreboot
1216 filesystem. This is a ROM-based filesystem used for accessing files
1217 on systems that use coreboot as the first boot-loader and then load
1218 U-Boot to actually boot the Operating System. Available commands are
1219 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1222 bool "Enable the 'cramfs' command"
1223 depends on FS_CRAMFS
1225 This provides commands for dealing with CRAMFS (Compressed ROM
1226 filesystem). CRAMFS is useful when space is tight since files are
1227 compressed. Two commands are provided:
1229 cramfsls - lists files in a cramfs image
1230 cramfsload - loads a file from a cramfs image
1233 bool "ext2 command support"
1235 Enables EXT2 FS command
1238 bool "ext4 command support"
1240 Enables EXT4 FS command
1242 config CMD_EXT4_WRITE
1244 bool "ext4 write command support"
1246 Enables EXT4 FS write command
1249 bool "FAT command support"
1252 Support for the FAT fs
1254 config CMD_FS_GENERIC
1255 bool "filesystem commands"
1257 Enables filesystem commands (e.g. load, ls) that work for multiple
1261 bool "fsuuid command"
1263 Enables fsuuid command for filesystem UUID.
1266 bool "jffs2 command"
1269 Enables commands to support the JFFS2 (Journalling Flash File System
1270 version 2) filesystem. This enables fsload, ls and fsinfo which
1271 provide the ability to load files, list directories and obtain
1272 filesystem information.
1275 bool "MTD partition support"
1277 MTD partition support
1279 config MTDIDS_DEFAULT
1280 string "Default MTD IDs"
1281 depends on CMD_MTDPARTS
1283 Defines a default MTD ID
1285 config MTDPARTS_DEFAULT
1286 string "Default MTD partition scheme"
1287 depends on CMD_MTDPARTS
1289 Defines a default MTD partitioning scheme in the Linux MTD command
1290 line partitions format
1292 config CMD_MTDPARTS_SPREAD
1293 bool "Padd partition size to take account of bad blocks"
1294 depends on CMD_MTDPARTS
1296 This enables the 'spread' sub-command of the mtdparts command.
1297 This command will modify the existing mtdparts variable by increasing
1298 the size of the partitions such that 1) each partition's net size is
1299 at least as large as the size specified in the mtdparts variable and
1300 2) each partition starts on a good block.
1303 bool "reiser - Access to reiserfs filesystems"
1305 This provides two commands which operate on a resierfs filesystem,
1306 commonly used some years ago:
1308 reiserls - list files
1309 reiserload - load a file
1312 bool "scsi - Access to SCSI devices"
1315 This provides a 'scsi' command which provides access to SCSI (Small
1316 Computer System Interface) devices. The command provides a way to
1317 scan the bus, reset the bus, read and write data and get information
1322 menu "Debug commands"
1327 The bedbug (emBEDded deBUGger) command provides debugging features
1328 for some PowerPC processors. For details please see the
1329 docuemntation in doc/README.beddbug
1332 bool "diag - Board diagnostics"
1334 This command provides access to board diagnostic tests. These are
1335 called Power-on Self Tests (POST). The command allows listing of
1336 available tests and running either all the tests, or specific tests
1340 bool "irq - Show information about interrupts"
1341 depends on !ARM && !MIPS && !SH
1343 This enables two commands:
1345 interrupts - enable or disable interrupts
1346 irqinfo - print device-specific interrupt information
1349 bool "kgdb - Allow debugging of U-Boot with gdb"
1351 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1352 over a serial link for debugging purposes. This allows
1353 single-stepping, inspecting variables, etc. This is supported only
1354 on PowerPC at present.
1359 tristate "Enable UBI - Unsorted block images commands"
1363 default y if NAND_SUNXI
1365 UBI is a software layer above MTD layer which admits use of LVM-like
1366 logical volumes on top of MTD devices, hides some complexities of
1367 flash chips like wear and bad blocks and provides some other useful
1368 capabilities. Please, consult the MTD web site for more details
1369 (www.linux-mtd.infradead.org). Activate this option if you want
1370 to use U-Boot UBI commands.
1373 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1377 default y if CMD_UBI
1379 UBIFS is a file system for flash devices which works on top of UBI.