Version:  2.6.34 2.6.35 2.6.36 2.6.37 2.6.38 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14

Linux/drivers/mtd/devices/Kconfig

  1 menu "Self-contained MTD device drivers"
  2         depends on MTD!=n
  3         depends on HAS_IOMEM
  4 
  5 config 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 
 23 config 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 
 31 config 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 
 39 config 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 
 53 config 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 
 61 config 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 
 71 config 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 
 81 config MTD_M25P80
 82         tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
 83         depends on SPI_MASTER
 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 
 98 config MTD_SPEAR_SMI
 99         tristate "SPEAR MTD NOR Support through SMI controller"
100         depends on PLAT_SPEAR
101         default y
102         help
103           This enable SNOR support on SPEAR platforms using SMI controller
104 
105 config MTD_SST25L
106         tristate "Support SST25L (non JEDEC) SPI Flash chips"
107         depends on SPI_MASTER
108         help
109           This enables access to the non JEDEC SST25L SPI flash chips, used
110           for program and data storage.
111 
112           Set up your spi devices with the right board-specific platform data,
113           if you want to specify device partitioning.
114 
115 config MTD_BCM47XXSFLASH
116         tristate "R/O support for serial flash on BCMA bus"
117         depends on BCMA_SFLASH
118         help
119           BCMA bus can have various flash memories attached, they are
120           registered by bcma as platform devices. This enables driver for
121           serial flash memories (only read-only mode is implemented).
122 
123 config MTD_SLRAM
124         tristate "Uncached system RAM"
125         help
126           If your CPU cannot cache all of the physical memory in your machine,
127           you can still use it for storage or swap by using this driver to
128           present it to the system as a Memory Technology Device.
129 
130 config MTD_PHRAM
131         tristate "Physical system RAM"
132         help
133           This is a re-implementation of the slram driver above.
134 
135           Use this driver to access physical memory that the kernel proper
136           doesn't have access to, memory beyond the mem=xxx limit, nvram,
137           memory on the video card, etc...
138 
139 config MTD_LART
140         tristate "28F160xx flash driver for LART"
141         depends on SA1100_LART
142         help
143           This enables the flash driver for LART. Please note that you do
144           not need any mapping/chip driver for LART. This one does it all
145           for you, so go disable all of those if you enabled some of them (:
146 
147 config MTD_MTDRAM
148         tristate "Test driver using RAM"
149         help
150           This enables a test MTD device driver which uses vmalloc() to
151           provide storage.  You probably want to say 'N' unless you're
152           testing stuff.
153 
154 config MTDRAM_TOTAL_SIZE
155         int "MTDRAM device size in KiB"
156         depends on MTD_MTDRAM
157         default "4096"
158         help
159           This allows you to configure the total size of the MTD device
160           emulated by the MTDRAM driver.  If the MTDRAM driver is built
161           as a module, it is also possible to specify this as a parameter when
162           loading the module.
163 
164 config MTDRAM_ERASE_SIZE
165         int "MTDRAM erase block size in KiB"
166         depends on MTD_MTDRAM
167         default "128"
168         help
169           This allows you to configure the size of the erase blocks in the
170           device 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 
174 #If not a module (I don't want to test it as a module)
175 config MTDRAM_ABS_POS
176         hex "SRAM Hexadecimal Absolute position or 0"
177         depends on MTD_MTDRAM=y
178         default "0"
179         help
180           If you have system RAM accessible by the CPU but not used by Linux
181           in normal operation, you can give the physical address at which the
182           available RAM starts, and the MTDRAM driver will use it instead of
183           allocating space from Linux's available memory. Otherwise, leave
184           this set to zero. Most people will want to leave this as zero.
185 
186 config MTD_BLOCK2MTD
187         tristate "MTD using block device"
188         depends on BLOCK
189         help
190           This driver allows a block device to appear as an MTD. It would
191           generally be used in the following cases:
192 
193           Using Compact Flash as an MTD, these usually present themselves to
194           the system as an ATA drive.
195           Testing MTD users (eg JFFS2) on large media and media that might
196           be removed during a write (using the floppy drive).
197 
198 comment "Disk-On-Chip Device Drivers"
199 
200 config MTD_DOCG3
201         tristate "M-Systems Disk-On-Chip G3"
202         select BCH
203         select BCH_CONST_PARAMS
204         select BITREVERSE
205         ---help---
206           This provides an MTD device driver for the M-Systems DiskOnChip
207           G3 devices.
208 
209           The driver provides access to G3 DiskOnChip, distributed by
210           M-Systems and now Sandisk. The support is very experimental,
211           and doesn't give access to any write operations.
212 
213 if MTD_DOCG3
214 config BCH_CONST_M
215         default 14
216 config BCH_CONST_T
217         default 4
218 endif
219 
220 endmenu

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us