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