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