2 tristate "Memory Technology Device (MTD) support"
6 Memory Technology Devices are flash, RAM and similar chips, often
7 used for solid state file systems on embedded devices. This option
8 will provide the generic support for MTD drivers to register
9 themselves with the kernel and for potential users of MTD devices
10 to enumerate the devices which are present and obtain a handle on
11 them. It will also allow you to select individual drivers for
12 particular hardware and users of MTD devices. If unsure, say N.
19 This turns on low-level debugging for the entire MTD sub-system.
20 Normally, you should say 'N'.
22 config MTD_DEBUG_VERBOSE
23 int "Debugging verbosity (0 = quiet, 3 = noisy)"
27 Determines the verbosity level of the MTD debugging messages.
30 tristate "MTD tests support"
33 This option includes various MTD tests into compilation. The tests
34 should normally be compiled as kernel modules. The modules perform
35 various checks and verifications when loaded.
42 config MTD_REDBOOT_PARTS
43 tristate "RedBoot partition table parsing"
45 RedBoot is a ROM monitor and bootloader which deals with multiple
46 'images' in flash devices by putting a table one of the erase
47 blocks on the device, similar to a partition table, which gives
48 the offsets, lengths and names of all the images stored in the
51 If you need code which can detect and parse this table, and register
52 MTD 'partitions' corresponding to each image in the table, enable
55 You will still need the parsing functions to be called by the driver
56 for your particular device. It won't happen automatically. The
57 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
62 config MTD_REDBOOT_DIRECTORY_BLOCK
63 int "Location of RedBoot partition table"
66 This option is the Linux counterpart to the
67 CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
70 The option specifies which Flash sectors holds the RedBoot
71 partition table. A zero or positive value gives an absolute
72 erase block number. A negative value specifies a number of
73 sectors before the end of the device.
75 For example "2" means block number 2, "-1" means the last
76 block and "-2" means the penultimate block.
78 config MTD_REDBOOT_PARTS_UNALLOCATED
79 bool "Include unallocated flash regions"
81 If you need to register each unallocated flash region as a MTD
82 'partition', enable this option.
84 config MTD_REDBOOT_PARTS_READONLY
85 bool "Force read-only for RedBoot system images"
87 If you need to force read-only for 'RedBoot', 'RedBoot Config' and
88 'FIS directory' images, enable this option.
90 endif # MTD_REDBOOT_PARTS
92 config MTD_CMDLINE_PARTS
93 bool "Command line partition table parsing"
94 depends on MTD_PARTITIONS = "y" && MTD = "y"
96 Allow generic configuration of the MTD partition tables via the kernel
97 command line. Multiple flash resources are supported for hardware where
98 different kinds of flash memory are available.
100 You will still need the parsing functions to be called by the driver
101 for your particular device. It won't happen automatically. The
102 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
105 The format for the command line is as follows:
107 mtdparts=<mtddef>[;<mtddef]
108 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
109 <partdef> := <size>[@offset][<name>][ro]
110 <mtd-id> := unique id used in mapping driver/device
111 <size> := standard linux memsize OR "-" to denote all
115 Due to the way Linux handles the command line, no spaces are
116 allowed in the partition definition, including mtd id's and partition
121 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
124 Same flash, but 2 named partitions, the first one being read-only:
125 mtdparts=sa1100:256k(ARMboot)ro,-(root)
130 tristate "ARM Firmware Suite partition parsing"
133 The ARM Firmware Suite allows the user to divide flash devices into
134 multiple 'images'. Each such image has a header containing its name
137 If you need code which can detect and parse these tables, and
138 register MTD 'partitions' corresponding to each image detected,
141 You will still need the parsing functions to be called by the driver
142 for your particular device. It won't happen automatically. The
143 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for
150 This provides a partition parsing function which derives
151 the partition map from the children of the flash node,
152 as described in Documentation/powerpc/booting-without-of.txt.
155 tristate "TI AR7 partitioning support"
157 TI AR7 partitioning support
159 endif # MTD_PARTITIONS
161 comment "User Modules And Translation Layers"
164 tristate "Direct char device access to MTD devices"
166 This provides a character device for each MTD device present in
167 the system, allowing the user to read and write directly to the
168 memory chips, and also use ioctl() to obtain information about
169 the device, or to erase parts of it.
174 Enable access to OTP regions using MTD_CHAR.
177 tristate "Common interface to block layer for MTD 'translation layers'"
182 tristate "Caching block device access to MTD devices"
186 Although most flash chips have an erase size too large to be useful
187 as block devices, it is possible to use MTD devices which are based
188 on RAM chips in this manner. This block device is a user of MTD
189 devices performing that function.
191 At the moment, it is also required for the Journalling Flash File
192 System(s) to obtain a handle on the MTD device when it's mounted
193 (although JFFS and JFFS2 don't actually use any of the functionality
194 of the mtdblock device).
196 Later, it may be extended to perform read/erase/modify/write cycles
197 on flash chips to emulate a smaller block size. Needless to say,
198 this is very unsafe, but could be useful for file systems which are
199 almost never written to.
201 You do not need this option for use with the DiskOnChip devices. For
202 those, enable NFTL support (CONFIG_NFTL) instead.
205 tristate "Readonly block device access to MTD devices"
206 depends on MTD_BLOCK!=y && BLOCK
209 This allows you to mount read-only file systems (such as cramfs)
210 from an MTD device, without the overhead (and danger) of the caching
213 You do not need this option for use with the DiskOnChip devices. For
214 those, enable NFTL support (CONFIG_NFTL) instead.
217 tristate "FTL (Flash Translation Layer) support"
221 This provides support for the original Flash Translation Layer which
222 is part of the PCMCIA specification. It uses a kind of pseudo-
223 file system on a flash device to emulate a block device with
224 512-byte sectors, on top of which you put a 'normal' file system.
226 You may find that the algorithms used in this code are patented
227 unless you live in the Free World where software patents aren't
228 legal - in the USA you are only permitted to use this on PCMCIA
229 hardware, although under the terms of the GPL you're obviously
230 permitted to copy, modify and distribute the code as you wish. Just
234 tristate "NFTL (NAND Flash Translation Layer) support"
238 This provides support for the NAND Flash Translation Layer which is
239 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
240 file system on a flash device to emulate a block device with
241 512-byte sectors, on top of which you put a 'normal' file system.
243 You may find that the algorithms used in this code are patented
244 unless you live in the Free World where software patents aren't
245 legal - in the USA you are only permitted to use this on DiskOnChip
246 hardware, although under the terms of the GPL you're obviously
247 permitted to copy, modify and distribute the code as you wish. Just
251 bool "Write support for NFTL"
254 Support for writing to the NAND Flash Translation Layer, as used
258 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
262 This provides support for the Inverse NAND Flash Translation
263 Layer which is used on M-Systems' newer DiskOnChip devices. It
264 uses a kind of pseudo-file system on a flash device to emulate
265 a block device with 512-byte sectors, on top of which you put
266 a 'normal' file system.
268 You may find that the algorithms used in this code are patented
269 unless you live in the Free World where software patents aren't
270 legal - in the USA you are only permitted to use this on DiskOnChip
271 hardware, although under the terms of the GPL you're obviously
272 permitted to copy, modify and distribute the code as you wish. Just
276 tristate "Resident Flash Disk (Flash Translation Layer) support"
280 This provides support for the flash translation layer known
281 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
282 of General Software. There is a blurb at:
284 http://www.gensw.com/pages/prod/bios/rfd.htm
287 tristate "NAND SSFDC (SmartMedia) read only translation layer"
291 This enables read only access to SmartMedia formatted NAND
292 flash. You can mount it with FAT file system.
296 tristate "SmartMedia/xD new translation layer"
297 depends on EXPERIMENTAL && BLOCK
301 This enables EXPERIMENTAL R/W support for SmartMedia/xD
302 FTL (Flash translation layer).
303 Write support is only lightly tested, therefore this driver
304 isn't recommended to use with valuable data (anyway if you have
305 valuable data, do backups regardless of software/hardware you
306 use, because you never know what will eat your data...)
307 If you only need R/O access, you can use older R/O driver
311 tristate "Log panic/oops to an MTD buffer"
313 This enables panic and oops messages to be logged to a circular
314 buffer in a flash partition where it can be read back at some
317 To use, add console=ttyMTDx to the kernel command line,
318 where x is the MTD device number to use.
321 tristate "Swap on MTD device support"
322 depends on MTD && SWAP
325 Provides volatile block device driver on top of mtd partition
326 suitable for swapping. The mapping of written blocks is not saved.
327 The driver provides wear leveling by storing erase counter into the
330 source "drivers/mtd/chips/Kconfig"
332 source "drivers/mtd/maps/Kconfig"
334 source "drivers/mtd/devices/Kconfig"
336 source "drivers/mtd/nand/Kconfig"
338 source "drivers/mtd/onenand/Kconfig"
340 source "drivers/mtd/lpddr/Kconfig"
342 source "drivers/mtd/ubi/Kconfig"