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