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