blob: 6e9f880e2f98c53553d0feafa24453986a7886ae [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# drivers/mtd/maps/Kconfig
Thomas Gleixnere5580fb2005-11-07 11:15:40 +00002# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
Linus Torvalds1da177e2005-04-16 15:20:36 -07003
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 MTD && 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 MTD && 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
David Brownell1d6432f2006-01-08 13:34:22 -080050config MTD_DATAFLASH
51 tristate "Support for AT45xxx DataFlash"
52 depends on MTD && SPI_MASTER && EXPERIMENTAL
53 help
54 This enables access to AT45xxx DataFlash chips, using SPI.
55 Sometimes DataFlash chips are packaged inside MMC-format
56 cards; at this writing, the MMC stack won't handle those.
57
Mike Lavender2f9f7622006-01-08 13:34:27 -080058config MTD_M25P80
59 tristate "Support for M25 SPI Flash"
60 depends on MTD && SPI_MASTER && EXPERIMENTAL
61 help
62 This enables access to ST M25P80 and similar SPI flash chips,
63 used for program and data storage. Set up your spi devices
64 with the right board-specific platform data.
65
Linus Torvalds1da177e2005-04-16 15:20:36 -070066config MTD_SLRAM
67 tristate "Uncached system RAM"
68 depends on MTD
69 help
70 If your CPU cannot cache all of the physical memory in your machine,
71 you can still use it for storage or swap by using this driver to
72 present it to the system as a Memory Technology Device.
73
74config MTD_PHRAM
75 tristate "Physical system RAM"
76 depends on MTD
77 help
78 This is a re-implementation of the slram driver above.
79
80 Use this driver to access physical memory that the kernel proper
81 doesn't have access to, memory beyond the mem=xxx limit, nvram,
82 memory on the video card, etc...
83
84config MTD_LART
85 tristate "28F160xx flash driver for LART"
86 depends on SA1100_LART && MTD
87 help
88 This enables the flash driver for LART. Please note that you do
89 not need any mapping/chip driver for LART. This one does it all
90 for you, so go disable all of those if you enabled some of them (:
91
92config MTD_MTDRAM
93 tristate "Test driver using RAM"
94 depends on MTD
95 help
96 This enables a test MTD device driver which uses vmalloc() to
97 provide storage. You probably want to say 'N' unless you're
98 testing stuff.
99
100config MTDRAM_TOTAL_SIZE
101 int "MTDRAM device size in KiB"
102 depends on MTD_MTDRAM
103 default "4096"
104 help
105 This allows you to configure the total size of the MTD device
106 emulated by the MTDRAM driver. If the MTDRAM driver is built
107 as a module, it is also possible to specify this as a parameter when
108 loading the module.
109
110config MTDRAM_ERASE_SIZE
111 int "MTDRAM erase block size in KiB"
112 depends on MTD_MTDRAM
113 default "128"
114 help
115 This allows you to configure the size of the erase blocks in the
116 device emulated by the MTDRAM driver. If the MTDRAM driver is built
117 as a module, it is also possible to specify this as a parameter when
118 loading the module.
119
120#If not a module (I don't want to test it as a module)
121config MTDRAM_ABS_POS
122 hex "SRAM Hexadecimal Absolute position or 0"
123 depends on MTD_MTDRAM=y
124 default "0"
125 help
126 If you have system RAM accessible by the CPU but not used by Linux
127 in normal operation, you can give the physical address at which the
128 available RAM starts, and the MTDRAM driver will use it instead of
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000129 allocating space from Linux's available memory. Otherwise, leave
Linus Torvalds1da177e2005-04-16 15:20:36 -0700130 this set to zero. Most people will want to leave this as zero.
131
Joern Engelacc8dad2006-04-10 22:54:17 -0700132config MTD_BLOCK2MTD
133 tristate "MTD using block device"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134 depends on MTD
135 help
136 This driver allows a block device to appear as an MTD. It would
137 generally be used in the following cases:
138
139 Using Compact Flash as an MTD, these usually present themselves to
140 the system as an ATA drive.
141 Testing MTD users (eg JFFS2) on large media and media that might
142 be removed during a write (using the floppy drive).
143
Linus Torvalds1da177e2005-04-16 15:20:36 -0700144comment "Disk-On-Chip Device Drivers"
145
146config MTD_DOC2000
147 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
148 depends on MTD
149 select MTD_DOCPROBE
150 select MTD_NAND_IDS
151 ---help---
152 This provides an MTD device driver for the M-Systems DiskOnChip
153 2000 and Millennium devices. Originally designed for the DiskOnChip
154 2000, it also now includes support for the DiskOnChip Millennium.
155 If you have problems with this driver and the DiskOnChip Millennium,
156 you may wish to try the alternative Millennium driver below. To use
157 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
158 in the <file:drivers/mtd/devices/docprobe.c> source code.
159
160 If you use this device, you probably also want to enable the NFTL
161 'NAND Flash Translation Layer' option below, which is used to
162 emulate a block device by using a kind of file system on the flash
163 chips.
164
165 NOTE: This driver is deprecated and will probably be removed soon.
166 Please try the new DiskOnChip driver under "NAND Flash Device
167 Drivers".
168
169config MTD_DOC2001
170 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
171 depends on MTD
172 select MTD_DOCPROBE
173 select MTD_NAND_IDS
174 ---help---
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000175 This provides an alternative MTD device driver for the M-Systems
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176 DiskOnChip Millennium devices. Use this if you have problems with
177 the combined DiskOnChip 2000 and Millennium driver above. To get
178 the DiskOnChip probe code to load and use this driver instead of
179 the other one, you will need to undefine DOC_SINGLE_DRIVER near
180 the beginning of <file:drivers/mtd/devices/docprobe.c>.
181
182 If you use this device, you probably also want to enable the NFTL
183 'NAND Flash Translation Layer' option below, which is used to
184 emulate a block device by using a kind of file system on the flash
185 chips.
186
187 NOTE: This driver is deprecated and will probably be removed soon.
188 Please try the new DiskOnChip driver under "NAND Flash Device
189 Drivers".
190
191config MTD_DOC2001PLUS
192 tristate "M-Systems Disk-On-Chip Millennium Plus"
193 depends on MTD
194 select MTD_DOCPROBE
195 select MTD_NAND_IDS
196 ---help---
197 This provides an MTD device driver for the M-Systems DiskOnChip
198 Millennium Plus devices.
199
200 If you use this device, you probably also want to enable the INFTL
201 'Inverse NAND Flash Translation Layer' option below, which is used
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000202 to emulate a block device by using a kind of file system on the
Linus Torvalds1da177e2005-04-16 15:20:36 -0700203 flash chips.
204
205 NOTE: This driver will soon be replaced by the new DiskOnChip driver
206 under "NAND Flash Device Drivers" (currently that driver does not
207 support all Millennium Plus devices).
208
209config MTD_DOCPROBE
210 tristate
211 select MTD_DOCECC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700212
213config MTD_DOCECC
214 tristate
215
216config MTD_DOCPROBE_ADVANCED
217 bool "Advanced detection options for DiskOnChip"
218 depends on MTD_DOCPROBE
219 help
220 This option allows you to specify nonstandard address at which to
221 probe for a DiskOnChip, or to change the detection options. You
222 are unlikely to need any of this unless you are using LinuxBIOS.
223 Say 'N'.
224
225config MTD_DOCPROBE_ADDRESS
226 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
227 depends on MTD_DOCPROBE
228 default "0x0000" if MTD_DOCPROBE_ADVANCED
229 default "0" if !MTD_DOCPROBE_ADVANCED
230 ---help---
231 By default, the probe for DiskOnChip devices will look for a
232 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
233 This option allows you to specify a single address at which to probe
234 for the device, which is useful if you have other devices in that
235 range which get upset when they are probed.
236
237 (Note that on PowerPC, the normal probe will only check at
238 0xE4000000.)
239
240 Normally, you should leave this set to zero, to allow the probe at
241 the normal addresses.
242
243config MTD_DOCPROBE_HIGH
244 bool "Probe high addresses"
245 depends on MTD_DOCPROBE_ADVANCED
246 help
247 By default, the probe for DiskOnChip devices will look for a
248 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
249 This option changes to make it probe between 0xFFFC8000 and
250 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
251 useful to you. Say 'N'.
252
253config MTD_DOCPROBE_55AA
254 bool "Probe for 0x55 0xAA BIOS Extension Signature"
255 depends on MTD_DOCPROBE_ADVANCED
256 help
257 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
258 continue with probing if it is absent. The signature will always be
259 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
260 Only if you have overwritten the first block of a DiskOnChip
261 Millennium will it be absent. Enable this option if you are using
262 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
263 you have managed to wipe the first block.
264
265endmenu
266