1# drivers/mtd/maps/Kconfig 2# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $ 3 4menu "Self-contained MTD device drivers" 5 depends on MTD!=n 6 7config MTD_PMC551 8 tristate "Ramix PMC551 PCI Mezzanine RAM card support" 9 depends on PCI 10 ---help--- 11 This provides a MTD device driver for the Ramix PMC551 RAM PCI card 12 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>. 13 These devices come in memory configurations from 32M - 1G. If you 14 have one, you probably want to enable this. 15 16 If this driver is compiled as a module you get the ability to select 17 the size of the aperture window pointing into the devices memory. 18 What this means is that if you have a 1G card, normally the kernel 19 will use a 1G memory map as its view of the device. As a module, 20 you can select a 1M window into the memory and the driver will 21 "slide" the window around the PMC551's memory. This was 22 particularly useful on the 2.2 kernels on PPC architectures as there 23 was limited kernel space to deal with. 24 25config MTD_PMC551_BUGFIX 26 bool "PMC551 256M DRAM Bugfix" 27 depends on MTD_PMC551 28 help 29 Some of Ramix's PMC551 boards with 256M configurations have invalid 30 column and row mux values. This option will fix them, but will 31 break other memory configurations. If unsure say N. 32 33config MTD_PMC551_DEBUG 34 bool "PMC551 Debugging" 35 depends on MTD_PMC551 36 help 37 This option makes the PMC551 more verbose during its operation and 38 is only really useful if you are developing on this driver or 39 suspect a possible hardware or driver bug. If unsure say N. 40 41config MTD_MS02NV 42 tristate "DEC MS02-NV NVRAM module support" 43 depends on MACH_DECSTATION 44 help 45 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery 46 backed-up NVRAM module. The module was originally meant as an NFS 47 accelerator. Say Y here if you have a DECstation 5000/2x0 or a 48 DECsystem 5900 equipped with such a module. 49 50 If you want to compile this driver as a module ( = code which can be 51 inserted in and removed from the running kernel whenever you want), 52 say M here and read <file:Documentation/kbuild/modules.txt>. 53 The module will be called ms02-nv.ko. 54 55config MTD_DATAFLASH 56 tristate "Support for AT45xxx DataFlash" 57 depends on SPI_MASTER && EXPERIMENTAL 58 help 59 This enables access to AT45xxx DataFlash chips, using SPI. 60 Sometimes DataFlash chips are packaged inside MMC-format 61 cards; at this writing, the MMC stack won't handle those. 62 63config MTD_M25P80 64 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)" 65 depends on SPI_MASTER && EXPERIMENTAL 66 help 67 This enables access to most modern SPI flash chips, used for 68 program and data storage. Series supported include Atmel AT26DF, 69 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips 70 are supported as well. See the driver source for the current list, 71 or to add other chips. 72 73 Note that the original DataFlash chips (AT45 series, not AT26DF), 74 need an entirely different driver. 75 76 Set up your spi devices with the right board-specific platform data, 77 if you want to specify device partitioning or to use a device which 78 doesn't support the JEDEC ID instruction. 79 80config M25PXX_USE_FAST_READ 81 bool "Use FAST_READ OPCode allowing SPI CLK <= 50MHz" 82 depends on MTD_M25P80 83 default y 84 help 85 This option enables FAST_READ access supported by ST M25Pxx. 86 87config MTD_SLRAM 88 tristate "Uncached system RAM" 89 help 90 If your CPU cannot cache all of the physical memory in your machine, 91 you can still use it for storage or swap by using this driver to 92 present it to the system as a Memory Technology Device. 93 94config MTD_PHRAM 95 tristate "Physical system RAM" 96 help 97 This is a re-implementation of the slram driver above. 98 99 Use this driver to access physical memory that the kernel proper 100 doesn't have access to, memory beyond the mem=xxx limit, nvram, 101 memory on the video card, etc... 102 103config MTD_LART 104 tristate "28F160xx flash driver for LART" 105 depends on SA1100_LART 106 help 107 This enables the flash driver for LART. Please note that you do 108 not need any mapping/chip driver for LART. This one does it all 109 for you, so go disable all of those if you enabled some of them (: 110 111config MTD_MTDRAM 112 tristate "Test driver using RAM" 113 help 114 This enables a test MTD device driver which uses vmalloc() to 115 provide storage. You probably want to say 'N' unless you're 116 testing stuff. 117 118config MTDRAM_TOTAL_SIZE 119 int "MTDRAM device size in KiB" 120 depends on MTD_MTDRAM 121 default "4096" 122 help 123 This allows you to configure the total size of the MTD device 124 emulated by the MTDRAM driver. If the MTDRAM driver is built 125 as a module, it is also possible to specify this as a parameter when 126 loading the module. 127 128config MTDRAM_ERASE_SIZE 129 int "MTDRAM erase block size in KiB" 130 depends on MTD_MTDRAM 131 default "128" 132 help 133 This allows you to configure the size of the erase blocks in the 134 device emulated by the MTDRAM driver. If the MTDRAM driver is built 135 as a module, it is also possible to specify this as a parameter when 136 loading the module. 137 138#If not a module (I don't want to test it as a module) 139config MTDRAM_ABS_POS 140 hex "SRAM Hexadecimal Absolute position or 0" 141 depends on MTD_MTDRAM=y 142 default "0" 143 help 144 If you have system RAM accessible by the CPU but not used by Linux 145 in normal operation, you can give the physical address at which the 146 available RAM starts, and the MTDRAM driver will use it instead of 147 allocating space from Linux's available memory. Otherwise, leave 148 this set to zero. Most people will want to leave this as zero. 149 150config MTD_BLOCK2MTD 151 tristate "MTD using block device" 152 depends on BLOCK 153 help 154 This driver allows a block device to appear as an MTD. It would 155 generally be used in the following cases: 156 157 Using Compact Flash as an MTD, these usually present themselves to 158 the system as an ATA drive. 159 Testing MTD users (eg JFFS2) on large media and media that might 160 be removed during a write (using the floppy drive). 161 162comment "Disk-On-Chip Device Drivers" 163 164config MTD_DOC2000 165 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)" 166 select MTD_DOCPROBE 167 select MTD_NAND_IDS 168 ---help--- 169 This provides an MTD device driver for the M-Systems DiskOnChip 170 2000 and Millennium devices. Originally designed for the DiskOnChip 171 2000, it also now includes support for the DiskOnChip Millennium. 172 If you have problems with this driver and the DiskOnChip Millennium, 173 you may wish to try the alternative Millennium driver below. To use 174 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER 175 in the <file:drivers/mtd/devices/docprobe.c> source code. 176 177 If you use this device, you probably also want to enable the NFTL 178 'NAND Flash Translation Layer' option below, which is used to 179 emulate a block device by using a kind of file system on the flash 180 chips. 181 182 NOTE: This driver is deprecated and will probably be removed soon. 183 Please try the new DiskOnChip driver under "NAND Flash Device 184 Drivers". 185 186config MTD_DOC2001 187 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)" 188 select MTD_DOCPROBE 189 select MTD_NAND_IDS 190 ---help--- 191 This provides an alternative MTD device driver for the M-Systems 192 DiskOnChip Millennium devices. Use this if you have problems with 193 the combined DiskOnChip 2000 and Millennium driver above. To get 194 the DiskOnChip probe code to load and use this driver instead of 195 the other one, you will need to undefine DOC_SINGLE_DRIVER near 196 the beginning of <file:drivers/mtd/devices/docprobe.c>. 197 198 If you use this device, you probably also want to enable the NFTL 199 'NAND Flash Translation Layer' option below, which is used to 200 emulate a block device by using a kind of file system on the flash 201 chips. 202 203 NOTE: This driver is deprecated and will probably be removed soon. 204 Please try the new DiskOnChip driver under "NAND Flash Device 205 Drivers". 206 207config MTD_DOC2001PLUS 208 tristate "M-Systems Disk-On-Chip Millennium Plus" 209 select MTD_DOCPROBE 210 select MTD_NAND_IDS 211 ---help--- 212 This provides an MTD device driver for the M-Systems DiskOnChip 213 Millennium Plus devices. 214 215 If you use this device, you probably also want to enable the INFTL 216 'Inverse NAND Flash Translation Layer' option below, which is used 217 to emulate a block device by using a kind of file system on the 218 flash chips. 219 220 NOTE: This driver will soon be replaced by the new DiskOnChip driver 221 under "NAND Flash Device Drivers" (currently that driver does not 222 support all Millennium Plus devices). 223 224config MTD_DOCPROBE 225 tristate 226 select MTD_DOCECC 227 228config MTD_DOCECC 229 tristate 230 231config MTD_DOCPROBE_ADVANCED 232 bool "Advanced detection options for DiskOnChip" 233 depends on MTD_DOCPROBE 234 help 235 This option allows you to specify nonstandard address at which to 236 probe for a DiskOnChip, or to change the detection options. You 237 are unlikely to need any of this unless you are using LinuxBIOS. 238 Say 'N'. 239 240config MTD_DOCPROBE_ADDRESS 241 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED 242 depends on MTD_DOCPROBE 243 default "0x0000" if MTD_DOCPROBE_ADVANCED 244 default "0" if !MTD_DOCPROBE_ADVANCED 245 ---help--- 246 By default, the probe for DiskOnChip devices will look for a 247 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 248 This option allows you to specify a single address at which to probe 249 for the device, which is useful if you have other devices in that 250 range which get upset when they are probed. 251 252 (Note that on PowerPC, the normal probe will only check at 253 0xE4000000.) 254 255 Normally, you should leave this set to zero, to allow the probe at 256 the normal addresses. 257 258config MTD_DOCPROBE_HIGH 259 bool "Probe high addresses" 260 depends on MTD_DOCPROBE_ADVANCED 261 help 262 By default, the probe for DiskOnChip devices will look for a 263 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 264 This option changes to make it probe between 0xFFFC8000 and 265 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be 266 useful to you. Say 'N'. 267 268config MTD_DOCPROBE_55AA 269 bool "Probe for 0x55 0xAA BIOS Extension Signature" 270 depends on MTD_DOCPROBE_ADVANCED 271 help 272 Check for the 0x55 0xAA signature of a DiskOnChip, and do not 273 continue with probing if it is absent. The signature will always be 274 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium. 275 Only if you have overwritten the first block of a DiskOnChip 276 Millennium will it be absent. Enable this option if you are using 277 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which 278 you have managed to wipe the first block. 279 280endmenu 281 282