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