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.ko. 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_SLRAM 108 tristate "Uncached system RAM" 109 help 110 If your CPU cannot cache all of the physical memory in your machine, 111 you can still use it for storage or swap by using this driver to 112 present it to the system as a Memory Technology Device. 113 114config MTD_PHRAM 115 tristate "Physical system RAM" 116 help 117 This is a re-implementation of the slram driver above. 118 119 Use this driver to access physical memory that the kernel proper 120 doesn't have access to, memory beyond the mem=xxx limit, nvram, 121 memory on the video card, etc... 122 123config MTD_PS3VRAM 124 tristate "PS3 video RAM" 125 depends on FB_PS3 126 help 127 This driver allows you to use excess PS3 video RAM as volatile 128 storage or system swap. 129 130config MTD_LART 131 tristate "28F160xx flash driver for LART" 132 depends on SA1100_LART 133 help 134 This enables the flash driver for LART. Please note that you do 135 not need any mapping/chip driver for LART. This one does it all 136 for you, so go disable all of those if you enabled some of them (: 137 138config MTD_MTDRAM 139 tristate "Test driver using RAM" 140 help 141 This enables a test MTD device driver which uses vmalloc() to 142 provide storage. You probably want to say 'N' unless you're 143 testing stuff. 144 145config MTDRAM_TOTAL_SIZE 146 int "MTDRAM device size in KiB" 147 depends on MTD_MTDRAM 148 default "4096" 149 help 150 This allows you to configure the total size of the MTD device 151 emulated by the MTDRAM driver. If the MTDRAM driver is built 152 as a module, it is also possible to specify this as a parameter when 153 loading the module. 154 155config MTDRAM_ERASE_SIZE 156 int "MTDRAM erase block size in KiB" 157 depends on MTD_MTDRAM 158 default "128" 159 help 160 This allows you to configure the size of the erase blocks in the 161 device emulated by the MTDRAM driver. If the MTDRAM driver is built 162 as a module, it is also possible to specify this as a parameter when 163 loading the module. 164 165#If not a module (I don't want to test it as a module) 166config MTDRAM_ABS_POS 167 hex "SRAM Hexadecimal Absolute position or 0" 168 depends on MTD_MTDRAM=y 169 default "0" 170 help 171 If you have system RAM accessible by the CPU but not used by Linux 172 in normal operation, you can give the physical address at which the 173 available RAM starts, and the MTDRAM driver will use it instead of 174 allocating space from Linux's available memory. Otherwise, leave 175 this set to zero. Most people will want to leave this as zero. 176 177config MTD_BLOCK2MTD 178 tristate "MTD using block device" 179 depends on BLOCK 180 help 181 This driver allows a block device to appear as an MTD. It would 182 generally be used in the following cases: 183 184 Using Compact Flash as an MTD, these usually present themselves to 185 the system as an ATA drive. 186 Testing MTD users (eg JFFS2) on large media and media that might 187 be removed during a write (using the floppy drive). 188 189comment "Disk-On-Chip Device Drivers" 190 191config MTD_DOC2000 192 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)" 193 select MTD_DOCPROBE 194 select MTD_NAND_IDS 195 ---help--- 196 This provides an MTD device driver for the M-Systems DiskOnChip 197 2000 and Millennium devices. Originally designed for the DiskOnChip 198 2000, it also now includes support for the DiskOnChip Millennium. 199 If you have problems with this driver and the DiskOnChip Millennium, 200 you may wish to try the alternative Millennium driver below. To use 201 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER 202 in the <file:drivers/mtd/devices/docprobe.c> source code. 203 204 If you use this device, you probably also want to enable the NFTL 205 'NAND Flash Translation Layer' option below, which is used to 206 emulate a block device by using a kind of file system on the flash 207 chips. 208 209 NOTE: This driver is deprecated and will probably be removed soon. 210 Please try the new DiskOnChip driver under "NAND Flash Device 211 Drivers". 212 213config MTD_DOC2001 214 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)" 215 select MTD_DOCPROBE 216 select MTD_NAND_IDS 217 ---help--- 218 This provides an alternative MTD device driver for the M-Systems 219 DiskOnChip Millennium devices. Use this if you have problems with 220 the combined DiskOnChip 2000 and Millennium driver above. To get 221 the DiskOnChip probe code to load and use this driver instead of 222 the other one, you will need to undefine DOC_SINGLE_DRIVER near 223 the beginning of <file:drivers/mtd/devices/docprobe.c>. 224 225 If you use this device, you probably also want to enable the NFTL 226 'NAND Flash Translation Layer' option below, which is used to 227 emulate a block device by using a kind of file system on the flash 228 chips. 229 230 NOTE: This driver is deprecated and will probably be removed soon. 231 Please try the new DiskOnChip driver under "NAND Flash Device 232 Drivers". 233 234config MTD_DOC2001PLUS 235 tristate "M-Systems Disk-On-Chip Millennium Plus" 236 select MTD_DOCPROBE 237 select MTD_NAND_IDS 238 ---help--- 239 This provides an MTD device driver for the M-Systems DiskOnChip 240 Millennium Plus devices. 241 242 If you use this device, you probably also want to enable the INFTL 243 'Inverse NAND Flash Translation Layer' option below, which is used 244 to emulate a block device by using a kind of file system on the 245 flash chips. 246 247 NOTE: This driver will soon be replaced by the new DiskOnChip driver 248 under "NAND Flash Device Drivers" (currently that driver does not 249 support all Millennium Plus devices). 250 251config MTD_DOCPROBE 252 tristate 253 select MTD_DOCECC 254 255config MTD_DOCECC 256 tristate 257 258config MTD_DOCPROBE_ADVANCED 259 bool "Advanced detection options for DiskOnChip" 260 depends on MTD_DOCPROBE 261 help 262 This option allows you to specify nonstandard address at which to 263 probe for a DiskOnChip, or to change the detection options. You 264 are unlikely to need any of this unless you are using LinuxBIOS. 265 Say 'N'. 266 267config MTD_DOCPROBE_ADDRESS 268 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED 269 depends on MTD_DOCPROBE 270 default "0x0000" if MTD_DOCPROBE_ADVANCED 271 default "0" if !MTD_DOCPROBE_ADVANCED 272 ---help--- 273 By default, the probe for DiskOnChip devices will look for a 274 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 275 This option allows you to specify a single address at which to probe 276 for the device, which is useful if you have other devices in that 277 range which get upset when they are probed. 278 279 (Note that on PowerPC, the normal probe will only check at 280 0xE4000000.) 281 282 Normally, you should leave this set to zero, to allow the probe at 283 the normal addresses. 284 285config MTD_DOCPROBE_HIGH 286 bool "Probe high addresses" 287 depends on MTD_DOCPROBE_ADVANCED 288 help 289 By default, the probe for DiskOnChip devices will look for a 290 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 291 This option changes to make it probe between 0xFFFC8000 and 292 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be 293 useful to you. Say 'N'. 294 295config MTD_DOCPROBE_55AA 296 bool "Probe for 0x55 0xAA BIOS Extension Signature" 297 depends on MTD_DOCPROBE_ADVANCED 298 help 299 Check for the 0x55 0xAA signature of a DiskOnChip, and do not 300 continue with probing if it is absent. The signature will always be 301 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium. 302 Only if you have overwritten the first block of a DiskOnChip 303 Millennium will it be absent. Enable this option if you are using 304 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which 305 you have managed to wipe the first block. 306 307endmenu 308 309