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 config MTD_BCM47XX_PARTS
82 tristate "BCM47XX partitioning support"
83 depends on BCM47XX || ARCH_BCM_5301X
85 This provides partitions parser for devices based on BCM47xx
88 menu "Partition parsers"
89 source "drivers/mtd/parsers/Kconfig"
92 comment "User Modules And Translation Layers"
95 # MTD block device support is select'ed if needed
101 tristate "Caching block device access to MTD devices"
105 Although most flash chips have an erase size too large to be useful
106 as block devices, it is possible to use MTD devices which are based
107 on RAM chips in this manner. This block device is a user of MTD
108 devices performing that function.
110 At the moment, it is also required for the Journalling Flash File
111 System(s) to obtain a handle on the MTD device when it's mounted
112 (although JFFS and JFFS2 don't actually use any of the functionality
113 of the mtdblock device).
115 Later, it may be extended to perform read/erase/modify/write cycles
116 on flash chips to emulate a smaller block size. Needless to say,
117 this is very unsafe, but could be useful for file systems which are
118 almost never written to.
120 You do not need this option for use with the DiskOnChip devices. For
121 those, enable NFTL support (CONFIG_NFTL) instead.
124 tristate "Readonly block device access to MTD devices"
125 depends on MTD_BLOCK!=y && BLOCK
128 This allows you to mount read-only file systems (such as cramfs)
129 from an MTD device, without the overhead (and danger) of the caching
132 You do not need this option for use with the DiskOnChip devices. For
133 those, enable NFTL support (CONFIG_NFTL) instead.
136 tristate "FTL (Flash Translation Layer) support"
140 This provides support for the original Flash Translation Layer which
141 is part of the PCMCIA specification. It uses a kind of pseudo-
142 file system on a flash device to emulate a block device with
143 512-byte sectors, on top of which you put a 'normal' file system.
145 You may find that the algorithms used in this code are patented
146 unless you live in the Free World where software patents aren't
147 legal - in the USA you are only permitted to use this on PCMCIA
148 hardware, although under the terms of the GPL you're obviously
149 permitted to copy, modify and distribute the code as you wish. Just
153 tristate "NFTL (NAND Flash Translation Layer) support"
157 This provides support for the NAND Flash Translation Layer which is
158 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
159 file system on a flash device to emulate a block device with
160 512-byte sectors, on top of which you put 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 bool "Write support for NFTL"
173 Support for writing to the NAND Flash Translation Layer, as used
177 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
181 This provides support for the Inverse NAND Flash Translation
182 Layer which is used on M-Systems' newer DiskOnChip devices. It
183 uses a kind of pseudo-file system on a flash device to emulate
184 a block device with 512-byte sectors, on top of which you put
185 a 'normal' file system.
187 You may find that the algorithms used in this code are patented
188 unless you live in the Free World where software patents aren't
189 legal - in the USA you are only permitted to use this on DiskOnChip
190 hardware, although under the terms of the GPL you're obviously
191 permitted to copy, modify and distribute the code as you wish. Just
195 tristate "Resident Flash Disk (Flash Translation Layer) support"
199 This provides support for the flash translation layer known
200 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
201 of General Software. There is a blurb at:
203 http://www.gensw.com/pages/prod/bios/rfd.htm
206 tristate "NAND SSFDC (SmartMedia) read only translation layer"
210 This enables read only access to SmartMedia formatted NAND
211 flash. You can mount it with FAT file system.
214 tristate "SmartMedia/xD new translation layer"
217 select MTD_NAND_ECC_SW_HAMMING
219 This enables EXPERIMENTAL R/W support for SmartMedia/xD
220 FTL (Flash translation layer).
221 Write support is only lightly tested, therefore this driver
222 isn't recommended to use with valuable data (anyway if you have
223 valuable data, do backups regardless of software/hardware you
224 use, because you never know what will eat your data...)
225 If you only need R/O access, you can use older R/O driver
229 tristate "Log panic/oops to an MTD buffer"
231 This enables panic and oops messages to be logged to a circular
232 buffer in a flash partition where it can be read back at some
236 tristate "Swap on MTD device support"
237 depends on MTD && SWAP
240 Provides volatile block device driver on top of mtd partition
241 suitable for swapping. The mapping of written blocks is not saved.
242 The driver provides wear leveling by storing erase counter into the
245 config MTD_PARTITIONED_MASTER
246 bool "Retain master device when partitioned"
250 For historical reasons, by default, either a master is present or
251 several partitions are present, but not both. The concern was that
252 data listed in multiple partitions was dangerous; however, SCSI does
253 this and it is frequently useful for applications. This config option
254 leaves the master in even if the device is partitioned. It also makes
255 the parent of the partition device be the master device, rather than
256 what lies behind the master.
258 source "drivers/mtd/chips/Kconfig"
260 source "drivers/mtd/maps/Kconfig"
262 source "drivers/mtd/devices/Kconfig"
264 source "drivers/mtd/nand/Kconfig"
266 source "drivers/mtd/lpddr/Kconfig"
268 source "drivers/mtd/spi-nor/Kconfig"
270 source "drivers/mtd/ubi/Kconfig"
272 source "drivers/mtd/hyperbus/Kconfig"