2 bool "Support block devices"
6 Enable support for block devices, such as SCSI, MMC and USB
7 flash sticks. These provide a block-level interface which permits
8 reading, writing and (in some cases) erasing blocks. Block
9 devices often have a partition table which allows the device to
10 be partitioned into several areas, called 'partitions' in U-Boot.
11 A filesystem can be placed in each partition.
14 bool "Support block devices in SPL"
15 depends on SPL_DM && BLK
18 Enable support for block devices, such as SCSI, MMC and USB
19 flash sticks. These provide a block-level interface which permits
20 reading, writing and (in some cases) erasing blocks. Block
21 devices often have a partition table which allows the device to
22 be partitioned into several areas, called 'partitions' in U-Boot.
23 A filesystem can be placed in each partition.
26 bool "Use block device cache"
29 This option enables a disk-block cache for all block devices.
30 This is most useful when accessing filesystems under U-Boot since
31 it will prevent repeated reads from directory structures and other
32 filesystem data structures.
35 bool "Support IDE controllers"
37 Enables support for IDE (Integrated Drive Electronics) hard drives.
38 This allows access to raw blocks and filesystems on an IDE drive
39 from U-Boot. See also CMD_IDE which provides an 'ide' command for
40 performing various IDE operations.
43 bool "Xilinx SystemACE support"
45 Adding this option adds support for Xilinx SystemACE chips attached
46 via some sort of local bus. The address of the chip must also be
47 defined in the CONFIG_SYS_SYSTEMACE_BASE macro.
49 When SystemACE support is added, the "ace" device type becomes
50 available to the fat commands, i.e. fatls.
52 config SYS_SYSTEMACE_BASE
53 hex "Base address of SystemACE chip"
56 config SYS_SYSTEMACE_WIDTH
57 int "Word size of access to the of SystemACE chip"