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 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 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 && MTD_SPI_NOR 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 MTD_MCHP23K256 99 tristate "Microchip 23K256 SRAM" 100 depends on SPI_MASTER 101 help 102 This enables access to Microchip 23K256 SRAM chips, using SPI. 103 104 Set up your spi devices with the right board-specific 105 platform data, or a device tree description if you want to 106 specify device partitioning 107 108config MTD_SPEAR_SMI 109 tristate "SPEAR MTD NOR Support through SMI controller" 110 depends on PLAT_SPEAR 111 default y 112 help 113 This enable SNOR support on SPEAR platforms using SMI controller 114 115config MTD_SST25L 116 tristate "Support SST25L (non JEDEC) SPI Flash chips" 117 depends on SPI_MASTER 118 help 119 This enables access to the non JEDEC SST25L SPI flash chips, used 120 for program and data storage. 121 122 Set up your spi devices with the right board-specific platform data, 123 if you want to specify device partitioning. 124 125config MTD_BCM47XXSFLASH 126 tristate "Support for serial flash on BCMA bus" 127 depends on BCMA_SFLASH && (MIPS || ARM) 128 help 129 BCMA bus can have various flash memories attached, they are 130 registered by bcma as platform devices. This enables driver for 131 serial flash memories. 132 133config MTD_SLRAM 134 tristate "Uncached system RAM" 135 help 136 If your CPU cannot cache all of the physical memory in your machine, 137 you can still use it for storage or swap by using this driver to 138 present it to the system as a Memory Technology Device. 139 140config MTD_PHRAM 141 tristate "Physical system RAM" 142 help 143 This is a re-implementation of the slram driver above. 144 145 Use this driver to access physical memory that the kernel proper 146 doesn't have access to, memory beyond the mem=xxx limit, nvram, 147 memory on the video card, etc... 148 149config MTD_LART 150 tristate "28F160xx flash driver for LART" 151 depends on SA1100_LART 152 help 153 This enables the flash driver for LART. Please note that you do 154 not need any mapping/chip driver for LART. This one does it all 155 for you, so go disable all of those if you enabled some of them (: 156 157config MTD_MTDRAM 158 tristate "Test driver using RAM" 159 help 160 This enables a test MTD device driver which uses vmalloc() to 161 provide storage. You probably want to say 'N' unless you're 162 testing stuff. 163 164config MTDRAM_TOTAL_SIZE 165 int "MTDRAM device size in KiB" 166 depends on MTD_MTDRAM 167 default "4096" 168 help 169 This allows you to configure the total size of the MTD device 170 emulated by the MTDRAM driver. If the MTDRAM driver is built 171 as a module, it is also possible to specify this as a parameter when 172 loading the module. 173 174config MTDRAM_ERASE_SIZE 175 int "MTDRAM erase block size in KiB" 176 depends on MTD_MTDRAM 177 default "128" 178 help 179 This allows you to configure the size of the erase blocks in the 180 device emulated by the MTDRAM driver. If the MTDRAM driver is built 181 as a module, it is also possible to specify this as a parameter when 182 loading the module. 183 184config MTD_BLOCK2MTD 185 tristate "MTD using block device" 186 depends on BLOCK 187 help 188 This driver allows a block device to appear as an MTD. It would 189 generally be used in the following cases: 190 191 Using Compact Flash as an MTD, these usually present themselves to 192 the system as an ATA drive. 193 Testing MTD users (eg JFFS2) on large media and media that might 194 be removed during a write (using the floppy drive). 195 196config MTD_POWERNV_FLASH 197 tristate "powernv flash MTD driver" 198 depends on PPC_POWERNV 199 help 200 This provides an MTD device to access flash on powernv OPAL 201 platforms from Linux. This device abstracts away the 202 firmware interface for flash access. 203 204comment "Disk-On-Chip Device Drivers" 205 206config MTD_DOCG3 207 tristate "M-Systems Disk-On-Chip G3" 208 select BCH 209 select BCH_CONST_PARAMS 210 select BITREVERSE 211 ---help--- 212 This provides an MTD device driver for the M-Systems DiskOnChip 213 G3 devices. 214 215 The driver provides access to G3 DiskOnChip, distributed by 216 M-Systems and now Sandisk. The support is very experimental, 217 and doesn't give access to any write operations. 218 219config MTD_ST_SPI_FSM 220 tristate "ST Microelectronics SPI FSM Serial Flash Controller" 221 depends on ARCH_STI 222 help 223 This provides an MTD device driver for the ST Microelectronics 224 SPI Fast Sequence Mode (FSM) Serial Flash Controller and support 225 for a subset of connected Serial Flash devices. 226 227if MTD_DOCG3 228config BCH_CONST_M 229 default 14 230config BCH_CONST_T 231 default 4 232endif 233 234endmenu 235