2 tristate "Memory Technology Device (MTD) support"
5 Memory Technology Devices are flash, RAM and similar chips, often
6 used for solid state file systems on embedded devices. This option
7 will provide the generic support for MTD drivers to register
8 themselves with the kernel and for potential users of MTD devices
9 to enumerate the devices which are present and obtain a handle on
10 them. It will also allow you to select individual drivers for
11 particular hardware and users of MTD devices. If unsure, say N.
16 tristate "MTD tests support (DANGEROUS)"
19 This option includes various MTD tests into compilation. The tests
20 should normally be compiled as kernel modules. The modules perform
21 various checks and verifications when loaded.
23 WARNING: some of the tests will ERASE entire MTD device which they
24 test. Do not use these tests unless you really know what you do.
26 config MTD_CMDLINE_PARTS
27 tristate "Command line partition table parsing"
30 Allow generic configuration of the MTD partition tables via the kernel
31 command line. Multiple flash resources are supported for hardware where
32 different kinds of flash memory are available.
34 You will still need the parsing functions to be called by the driver
35 for your particular device. It won't happen automatically. The
36 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
39 The format for the command line is as follows:
41 mtdparts=<mtddef>[;<mtddef]
42 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
43 <partdef> := <size>[@offset][<name>][ro]
44 <mtd-id> := unique id used in mapping driver/device
45 <size> := standard linux memsize OR "-" to denote all
49 Due to the way Linux handles the command line, no spaces are
50 allowed in the partition definition, including mtd id's and partition
55 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
58 Same flash, but 2 named partitions, the first one being read-only:
59 mtdparts=sa1100:256k(ARMboot)ro,-(root)
63 menu "Partition parsers"
64 source "drivers/mtd/parsers/Kconfig"
67 comment "User Modules And Translation Layers"
70 # MTD block device support is select'ed if needed
76 tristate "Caching block device access to MTD devices"
80 Although most flash chips have an erase size too large to be useful
81 as block devices, it is possible to use MTD devices which are based
82 on RAM chips in this manner. This block device is a user of MTD
83 devices performing that function.
85 At the moment, it is also required for the Journalling Flash File
86 System(s) to obtain a handle on the MTD device when it's mounted
87 (although JFFS and JFFS2 don't actually use any of the functionality
88 of the mtdblock device).
90 Later, it may be extended to perform read/erase/modify/write cycles
91 on flash chips to emulate a smaller block size. Needless to say,
92 this is very unsafe, but could be useful for file systems which are
93 almost never written to.
95 You do not need this option for use with the DiskOnChip devices. For
96 those, enable NFTL support (CONFIG_NFTL) instead.
99 tristate "Readonly block device access to MTD devices"
100 depends on MTD_BLOCK!=y && BLOCK
103 This allows you to mount read-only file systems (such as cramfs)
104 from an MTD device, without the overhead (and danger) of the caching
107 You do not need this option for use with the DiskOnChip devices. For
108 those, enable NFTL support (CONFIG_NFTL) instead.
111 tristate "FTL (Flash Translation Layer) support"
115 This provides support for the original Flash Translation Layer which
116 is part of the PCMCIA specification. It uses a kind of pseudo-
117 file system on a flash device to emulate a block device with
118 512-byte sectors, on top of which you put a 'normal' file system.
120 You may find that the algorithms used in this code are patented
121 unless you live in the Free World where software patents aren't
122 legal - in the USA you are only permitted to use this on PCMCIA
123 hardware, although under the terms of the GPL you're obviously
124 permitted to copy, modify and distribute the code as you wish. Just
128 tristate "NFTL (NAND Flash Translation Layer) support"
132 This provides support for the NAND Flash Translation Layer which is
133 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
134 file system on a flash device to emulate a block device with
135 512-byte sectors, on top of which you put a 'normal' file system.
137 You may find that the algorithms used in this code are patented
138 unless you live in the Free World where software patents aren't
139 legal - in the USA you are only permitted to use this on DiskOnChip
140 hardware, although under the terms of the GPL you're obviously
141 permitted to copy, modify and distribute the code as you wish. Just
145 bool "Write support for NFTL"
148 Support for writing to the NAND Flash Translation Layer, as used
152 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
156 This provides support for the Inverse NAND Flash Translation
157 Layer which is used on M-Systems' newer DiskOnChip devices. It
158 uses a kind of pseudo-file system on a flash device to emulate
159 a block device with 512-byte sectors, on top of which you put
160 a 'normal' file system.
162 You may find that the algorithms used in this code are patented
163 unless you live in the Free World where software patents aren't
164 legal - in the USA you are only permitted to use this on DiskOnChip
165 hardware, although under the terms of the GPL you're obviously
166 permitted to copy, modify and distribute the code as you wish. Just
170 tristate "Resident Flash Disk (Flash Translation Layer) support"
174 This provides support for the flash translation layer known
175 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
176 of General Software. There is a blurb at:
178 http://www.gensw.com/pages/prod/bios/rfd.htm
181 tristate "NAND SSFDC (SmartMedia) read only translation layer"
185 This enables read only access to SmartMedia formatted NAND
186 flash. You can mount it with FAT file system.
189 tristate "SmartMedia/xD new translation layer"
192 select MTD_NAND_ECC_SW_HAMMING
194 This enables EXPERIMENTAL R/W support for SmartMedia/xD
195 FTL (Flash translation layer).
196 Write support is only lightly tested, therefore this driver
197 isn't recommended to use with valuable data (anyway if you have
198 valuable data, do backups regardless of software/hardware you
199 use, because you never know what will eat your data...)
200 If you only need R/O access, you can use older R/O driver
204 tristate "Log panic/oops to an MTD buffer"
206 This enables panic and oops messages to be logged to a circular
207 buffer in a flash partition where it can be read back at some
211 tristate "Swap on MTD device support"
212 depends on MTD && SWAP
215 Provides volatile block device driver on top of mtd partition
216 suitable for swapping. The mapping of written blocks is not saved.
217 The driver provides wear leveling by storing erase counter into the
220 config MTD_PARTITIONED_MASTER
221 bool "Retain master device when partitioned"
225 For historical reasons, by default, either a master is present or
226 several partitions are present, but not both. The concern was that
227 data listed in multiple partitions was dangerous; however, SCSI does
228 this and it is frequently useful for applications. This config option
229 leaves the master in even if the device is partitioned. It also makes
230 the parent of the partition device be the master device, rather than
231 what lies behind the master.
233 source "drivers/mtd/chips/Kconfig"
235 source "drivers/mtd/maps/Kconfig"
237 source "drivers/mtd/devices/Kconfig"
239 source "drivers/mtd/nand/Kconfig"
241 source "drivers/mtd/lpddr/Kconfig"
243 source "drivers/mtd/spi-nor/Kconfig"
245 source "drivers/mtd/ubi/Kconfig"
247 source "drivers/mtd/hyperbus/Kconfig"