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)
64 tristate "OpenFirmware partitioning information support"
68 This provides a partition parsing function which derives
69 the partition map from the children of the flash node,
70 as described in Documentation/devicetree/bindings/mtd/partition.txt.
72 config MTD_BCM63XX_PARTS
73 tristate "BCM63XX CFE partitioning support"
74 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
76 select MTD_PARSER_IMAGETAG
78 This provides partition parsing for BCM63xx devices with CFE
81 menu "Partition parsers"
82 source "drivers/mtd/parsers/Kconfig"
85 comment "User Modules And Translation Layers"
88 # MTD block device support is select'ed if needed
94 tristate "Caching block device access to MTD devices"
98 Although most flash chips have an erase size too large to be useful
99 as block devices, it is possible to use MTD devices which are based
100 on RAM chips in this manner. This block device is a user of MTD
101 devices performing that function.
103 At the moment, it is also required for the Journalling Flash File
104 System(s) to obtain a handle on the MTD device when it's mounted
105 (although JFFS and JFFS2 don't actually use any of the functionality
106 of the mtdblock device).
108 Later, it may be extended to perform read/erase/modify/write cycles
109 on flash chips to emulate a smaller block size. Needless to say,
110 this is very unsafe, but could be useful for file systems which are
111 almost never written to.
113 You do not need this option for use with the DiskOnChip devices. For
114 those, enable NFTL support (CONFIG_NFTL) instead.
117 tristate "Readonly block device access to MTD devices"
118 depends on MTD_BLOCK!=y && BLOCK
121 This allows you to mount read-only file systems (such as cramfs)
122 from an MTD device, without the overhead (and danger) of the caching
125 You do not need this option for use with the DiskOnChip devices. For
126 those, enable NFTL support (CONFIG_NFTL) instead.
129 tristate "FTL (Flash Translation Layer) support"
133 This provides support for the original Flash Translation Layer which
134 is part of the PCMCIA specification. It uses a kind of pseudo-
135 file system on a flash device to emulate a block device with
136 512-byte sectors, on top of which you put a 'normal' file system.
138 You may find that the algorithms used in this code are patented
139 unless you live in the Free World where software patents aren't
140 legal - in the USA you are only permitted to use this on PCMCIA
141 hardware, although under the terms of the GPL you're obviously
142 permitted to copy, modify and distribute the code as you wish. Just
146 tristate "NFTL (NAND Flash Translation Layer) support"
150 This provides support for the NAND Flash Translation Layer which is
151 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
152 file system on a flash device to emulate a block device with
153 512-byte sectors, on top of which you put a 'normal' file system.
155 You may find that the algorithms used in this code are patented
156 unless you live in the Free World where software patents aren't
157 legal - in the USA you are only permitted to use this on DiskOnChip
158 hardware, although under the terms of the GPL you're obviously
159 permitted to copy, modify and distribute the code as you wish. Just
163 bool "Write support for NFTL"
166 Support for writing to the NAND Flash Translation Layer, as used
170 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
174 This provides support for the Inverse NAND Flash Translation
175 Layer which is used on M-Systems' newer DiskOnChip devices. It
176 uses a kind of pseudo-file system on a flash device to emulate
177 a block device with 512-byte sectors, on top of which you put
178 a 'normal' file system.
180 You may find that the algorithms used in this code are patented
181 unless you live in the Free World where software patents aren't
182 legal - in the USA you are only permitted to use this on DiskOnChip
183 hardware, although under the terms of the GPL you're obviously
184 permitted to copy, modify and distribute the code as you wish. Just
188 tristate "Resident Flash Disk (Flash Translation Layer) support"
192 This provides support for the flash translation layer known
193 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
194 of General Software. There is a blurb at:
196 http://www.gensw.com/pages/prod/bios/rfd.htm
199 tristate "NAND SSFDC (SmartMedia) read only translation layer"
203 This enables read only access to SmartMedia formatted NAND
204 flash. You can mount it with FAT file system.
207 tristate "SmartMedia/xD new translation layer"
210 select MTD_NAND_ECC_SW_HAMMING
212 This enables EXPERIMENTAL R/W support for SmartMedia/xD
213 FTL (Flash translation layer).
214 Write support is only lightly tested, therefore this driver
215 isn't recommended to use with valuable data (anyway if you have
216 valuable data, do backups regardless of software/hardware you
217 use, because you never know what will eat your data...)
218 If you only need R/O access, you can use older R/O driver
222 tristate "Log panic/oops to an MTD buffer"
224 This enables panic and oops messages to be logged to a circular
225 buffer in a flash partition where it can be read back at some
229 tristate "Swap on MTD device support"
230 depends on MTD && SWAP
233 Provides volatile block device driver on top of mtd partition
234 suitable for swapping. The mapping of written blocks is not saved.
235 The driver provides wear leveling by storing erase counter into the
238 config MTD_PARTITIONED_MASTER
239 bool "Retain master device when partitioned"
243 For historical reasons, by default, either a master is present or
244 several partitions are present, but not both. The concern was that
245 data listed in multiple partitions was dangerous; however, SCSI does
246 this and it is frequently useful for applications. This config option
247 leaves the master in even if the device is partitioned. It also makes
248 the parent of the partition device be the master device, rather than
249 what lies behind the master.
251 source "drivers/mtd/chips/Kconfig"
253 source "drivers/mtd/maps/Kconfig"
255 source "drivers/mtd/devices/Kconfig"
257 source "drivers/mtd/nand/Kconfig"
259 source "drivers/mtd/lpddr/Kconfig"
261 source "drivers/mtd/spi-nor/Kconfig"
263 source "drivers/mtd/ubi/Kconfig"
265 source "drivers/mtd/hyperbus/Kconfig"