Blame view
drivers/mtd/Kconfig
11.4 KB
ec98c681a Use menuconfig ob... |
1 |
menuconfig MTD |
1da177e4c Linux-2.6.12-rc2 |
2 |
tristate "Memory Technology Device (MTD) support" |
e25df1205 [S390] Kconfig: m... |
3 |
depends on HAS_IOMEM |
1da177e4c Linux-2.6.12-rc2 |
4 5 6 7 8 9 |
help Memory Technology Devices are flash, RAM and similar chips, often used for solid state file systems on embedded devices. This option will provide the generic support for MTD drivers to register themselves with the kernel and for potential users of MTD devices to enumerate the devices which are present and obtain a handle on |
97894cda5 [MTD] core: Clean... |
10 |
them. It will also allow you to select individual drivers for |
1da177e4c Linux-2.6.12-rc2 |
11 |
particular hardware and users of MTD devices. If unsure, say N. |
ec98c681a Use menuconfig ob... |
12 |
if MTD |
80f53da0a mtd: fix order of... |
13 |
config MTD_TESTS |
48e546b7f mtd: tests: annot... |
14 |
tristate "MTD tests support (DANGEROUS)" |
80f53da0a mtd: fix order of... |
15 16 17 18 19 |
depends on m help This option includes various MTD tests into compilation. The tests should normally be compiled as kernel modules. The modules perform various checks and verifications when loaded. |
48e546b7f mtd: tests: annot... |
20 21 |
WARNING: some of the tests will ERASE entire MTD device which they test. Do not use these tests unless you really know what you do. |
1da177e4c Linux-2.6.12-rc2 |
22 23 |
config MTD_REDBOOT_PARTS tristate "RedBoot partition table parsing" |
1da177e4c Linux-2.6.12-rc2 |
24 25 26 27 28 29 30 31 32 |
---help--- RedBoot is a ROM monitor and bootloader which deals with multiple 'images' in flash devices by putting a table one of the erase blocks on the device, similar to a partition table, which gives the offsets, lengths and names of all the images stored in the flash. If you need code which can detect and parse this table, and register MTD 'partitions' corresponding to each image in the table, enable |
97894cda5 [MTD] core: Clean... |
33 |
this option. |
1da177e4c Linux-2.6.12-rc2 |
34 35 |
You will still need the parsing functions to be called by the driver |
97894cda5 [MTD] core: Clean... |
36 37 |
for your particular device. It won't happen automatically. The SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for |
1da177e4c Linux-2.6.12-rc2 |
38 |
example. |
b7b6e08f9 mtd: Fix MTD_OF_P... |
39 |
if MTD_REDBOOT_PARTS |
1da177e4c Linux-2.6.12-rc2 |
40 41 |
config MTD_REDBOOT_DIRECTORY_BLOCK int "Location of RedBoot partition table" |
1da177e4c Linux-2.6.12-rc2 |
42 43 44 45 46 47 48 |
default "-1" ---help--- This option is the Linux counterpart to the CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time option. The option specifies which Flash sectors holds the RedBoot |
4992a9e88 Trivial typo fixe... |
49 |
partition table. A zero or positive value gives an absolute |
1da177e4c Linux-2.6.12-rc2 |
50 51 |
erase block number. A negative value specifies a number of sectors before the end of the device. |
97894cda5 [MTD] core: Clean... |
52 |
|
1da177e4c Linux-2.6.12-rc2 |
53 54 |
For example "2" means block number 2, "-1" means the last block and "-2" means the penultimate block. |
97894cda5 [MTD] core: Clean... |
55 |
|
1da177e4c Linux-2.6.12-rc2 |
56 |
config MTD_REDBOOT_PARTS_UNALLOCATED |
e55a3e8ae kconfig: remove l... |
57 |
bool "Include unallocated flash regions" |
1da177e4c Linux-2.6.12-rc2 |
58 59 60 61 62 |
help If you need to register each unallocated flash region as a MTD 'partition', enable this option. config MTD_REDBOOT_PARTS_READONLY |
e55a3e8ae kconfig: remove l... |
63 |
bool "Force read-only for RedBoot system images" |
1da177e4c Linux-2.6.12-rc2 |
64 65 66 |
help If you need to force read-only for 'RedBoot', 'RedBoot Config' and 'FIS directory' images, enable this option. |
b7b6e08f9 mtd: Fix MTD_OF_P... |
67 |
endif # MTD_REDBOOT_PARTS |
1da177e4c Linux-2.6.12-rc2 |
68 69 |
config MTD_CMDLINE_PARTS bool "Command line partition table parsing" |
6a8a98b22 mtd: kill CONFIG_... |
70 |
depends on MTD = "y" |
1da177e4c Linux-2.6.12-rc2 |
71 |
---help--- |
4992a9e88 Trivial typo fixe... |
72 |
Allow generic configuration of the MTD partition tables via the kernel |
1da177e4c Linux-2.6.12-rc2 |
73 |
command line. Multiple flash resources are supported for hardware where |
97894cda5 [MTD] core: Clean... |
74 |
different kinds of flash memory are available. |
1da177e4c Linux-2.6.12-rc2 |
75 76 |
You will still need the parsing functions to be called by the driver |
97894cda5 [MTD] core: Clean... |
77 78 |
for your particular device. It won't happen automatically. The SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for |
1da177e4c Linux-2.6.12-rc2 |
79 80 81 82 83 84 85 86 |
example. The format for the command line is as follows: mtdparts=<mtddef>[;<mtddef] <mtddef> := <mtd-id>:<partdef>[,<partdef>] <partdef> := <size>[@offset][<name>][ro] <mtd-id> := unique id used in mapping driver/device |
97894cda5 [MTD] core: Clean... |
87 |
<size> := standard linux memsize OR "-" to denote all |
1da177e4c Linux-2.6.12-rc2 |
88 89 |
remaining space <name> := (NAME) |
97894cda5 [MTD] core: Clean... |
90 91 |
Due to the way Linux handles the command line, no spaces are allowed in the partition definition, including mtd id's and partition |
1da177e4c Linux-2.6.12-rc2 |
92 93 94 95 96 97 98 99 100 101 102 103 104 105 |
names. Examples: 1 flash resource (mtd-id "sa1100"), with 1 single writable partition: mtdparts=sa1100:- Same flash, but 2 named partitions, the first one being read-only: mtdparts=sa1100:256k(ARMboot)ro,-(root) If unsure, say 'N'. config MTD_AFS_PARTS tristate "ARM Firmware Suite partition parsing" |
b7b6e08f9 mtd: Fix MTD_OF_P... |
106 |
depends on ARM |
1da177e4c Linux-2.6.12-rc2 |
107 108 109 110 111 112 113 114 115 116 117 |
---help--- The ARM Firmware Suite allows the user to divide flash devices into multiple 'images'. Each such image has a header containing its name and offset/size etc. If you need code which can detect and parse these tables, and register MTD 'partitions' corresponding to each image detected, enable this option. You will still need the parsing functions to be called by the driver for your particular device. It won't happen automatically. The |
adf004009 ARM: 6906/1: MTD:... |
118 |
'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example. |
1da177e4c Linux-2.6.12-rc2 |
119 |
|
9a310d211 [MTD] Factor out ... |
120 |
config MTD_OF_PARTS |
d6137bade mtd: make ofpart ... |
121 122 |
tristate "OpenFirmware partitioning information support" default Y |
b7b6e08f9 mtd: Fix MTD_OF_P... |
123 |
depends on OF |
9a310d211 [MTD] Factor out ... |
124 125 126 |
help This provides a partition parsing function which derives the partition map from the children of the flash node, |
395cf9691 doc: fix broken r... |
127 |
as described in Documentation/devicetree/booting-without-of.txt. |
9a310d211 [MTD] Factor out ... |
128 |
|
f0797881d [MTD] AR7 mtd par... |
129 130 |
config MTD_AR7_PARTS tristate "TI AR7 partitioning support" |
f0797881d [MTD] AR7 mtd par... |
131 132 |
---help--- TI AR7 partitioning support |
70a3c167c mtd: maps: bcm963... |
133 134 135 136 137 138 139 |
config MTD_BCM63XX_PARTS tristate "BCM63XX CFE partitioning support" depends on BCM63XX select CRC32 help This provides partions parsing for BCM63xx devices with CFE bootloaders. |
1da177e4c Linux-2.6.12-rc2 |
140 |
comment "User Modules And Translation Layers" |
1da177e4c Linux-2.6.12-rc2 |
141 142 143 |
config MTD_CHAR tristate "Direct char device access to MTD devices" |
1da177e4c Linux-2.6.12-rc2 |
144 145 146 147 148 |
help This provides a character device for each MTD device present in the system, allowing the user to read and write directly to the memory chips, and also use ioctl() to obtain information about the device, or to erase parts of it. |
34a82443b [MTD] dataflash O... |
149 150 151 152 |
config HAVE_MTD_OTP bool help Enable access to OTP regions using MTD_CHAR. |
f6a7ecb18 [MTD] add MTD_BLK... |
153 154 |
config MTD_BLKDEVS tristate "Common interface to block layer for MTD 'translation layers'" |
ec98c681a Use menuconfig ob... |
155 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
156 |
default n |
1da177e4c Linux-2.6.12-rc2 |
157 158 |
config MTD_BLOCK tristate "Caching block device access to MTD devices" |
ec98c681a Use menuconfig ob... |
159 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
160 |
select MTD_BLKDEVS |
1da177e4c Linux-2.6.12-rc2 |
161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 |
---help--- Although most flash chips have an erase size too large to be useful as block devices, it is possible to use MTD devices which are based on RAM chips in this manner. This block device is a user of MTD devices performing that function. At the moment, it is also required for the Journalling Flash File System(s) to obtain a handle on the MTD device when it's mounted (although JFFS and JFFS2 don't actually use any of the functionality of the mtdblock device). Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, this is very unsafe, but could be useful for file systems which are almost never written to. You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (CONFIG_NFTL) instead. config MTD_BLOCK_RO tristate "Readonly block device access to MTD devices" |
ec98c681a Use menuconfig ob... |
182 |
depends on MTD_BLOCK!=y && BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
183 |
select MTD_BLKDEVS |
1da177e4c Linux-2.6.12-rc2 |
184 185 186 187 188 189 190 191 192 193 |
help This allows you to mount read-only file systems (such as cramfs) from an MTD device, without the overhead (and danger) of the caching driver. You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (CONFIG_NFTL) instead. config FTL tristate "FTL (Flash Translation Layer) support" |
ec98c681a Use menuconfig ob... |
194 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
195 |
select MTD_BLKDEVS |
1da177e4c Linux-2.6.12-rc2 |
196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 |
---help--- This provides support for the original Flash Translation Layer which is part of the PCMCIA specification. It uses a kind of pseudo- file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on PCMCIA hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. config NFTL tristate "NFTL (NAND Flash Translation Layer) support" |
ec98c681a Use menuconfig ob... |
211 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
212 |
select MTD_BLKDEVS |
1da177e4c Linux-2.6.12-rc2 |
213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 |
---help--- This provides support for the NAND Flash Translation Layer which is used on M-Systems' DiskOnChip devices. It uses a kind of pseudo- file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on DiskOnChip hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. config NFTL_RW bool "Write support for NFTL" depends on NFTL help Support for writing to the NAND Flash Translation Layer, as used on the DiskOnChip. config INFTL tristate "INFTL (Inverse NAND Flash Translation Layer) support" |
ec98c681a Use menuconfig ob... |
235 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
236 |
select MTD_BLKDEVS |
1da177e4c Linux-2.6.12-rc2 |
237 |
---help--- |
97894cda5 [MTD] core: Clean... |
238 |
This provides support for the Inverse NAND Flash Translation |
1da177e4c Linux-2.6.12-rc2 |
239 240 241 242 243 244 245 246 247 248 249 |
Layer which is used on M-Systems' newer DiskOnChip devices. It uses a kind of pseudo-file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on DiskOnChip hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. |
e27a9960a [MTD] Add Residen... |
250 251 |
config RFD_FTL tristate "Resident Flash Disk (Flash Translation Layer) support" |
ec98c681a Use menuconfig ob... |
252 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
253 |
select MTD_BLKDEVS |
e27a9960a [MTD] Add Residen... |
254 |
---help--- |
97894cda5 [MTD] core: Clean... |
255 256 |
This provides support for the flash translation layer known as the Resident Flash Disk (RFD), as used by the Embedded BIOS |
cd5f6346b [MTD] Add initial... |
257 258 259 |
of General Software. There is a blurb at: http://www.gensw.com/pages/prod/bios/rfd.htm |
e27a9960a [MTD] Add Residen... |
260 |
|
51197abf2 [MTD] Add SSFDC (... |
261 |
config SSFDC |
892e4fba1 [MTD] Fix depende... |
262 |
tristate "NAND SSFDC (SmartMedia) read only translation layer" |
ec98c681a Use menuconfig ob... |
263 |
depends on BLOCK |
f6a7ecb18 [MTD] add MTD_BLK... |
264 |
select MTD_BLKDEVS |
51197abf2 [MTD] Add SSFDC (... |
265 266 267 |
help This enables read only access to SmartMedia formatted NAND flash. You can mount it with FAT file system. |
7d17c02a0 mtd: Add new Smar... |
268 269 270 |
config SM_FTL tristate "SmartMedia/xD new translation layer" |
e5f710cfc mtd: nand: split ... |
271 |
depends on EXPERIMENTAL && BLOCK |
7d17c02a0 mtd: Add new Smar... |
272 |
select MTD_BLKDEVS |
e5f710cfc mtd: nand: split ... |
273 |
select MTD_NAND_ECC |
7d17c02a0 mtd: Add new Smar... |
274 |
help |
6f92355c6 mtd: update descr... |
275 |
This enables EXPERIMENTAL R/W support for SmartMedia/xD |
7de6f798e mtd: Make SM_FTL ... |
276 |
FTL (Flash translation layer). |
6f92355c6 mtd: update descr... |
277 278 279 280 281 282 |
Write support is only lightly tested, therefore this driver isn't recommended to use with valuable data (anyway if you have valuable data, do backups regardless of software/hardware you use, because you never know what will eat your data...) If you only need R/O access, you can use older R/O driver (CONFIG_SSFDC) |
7d17c02a0 mtd: Add new Smar... |
283 |
|
4b23aff08 [MTD] oops and pa... |
284 285 |
config MTD_OOPS tristate "Log panic/oops to an MTD buffer" |
4b23aff08 [MTD] oops and pa... |
286 287 288 289 |
help This enables panic and oops messages to be logged to a circular buffer in a flash partition where it can be read back at some later point. |
256331d53 [MTD] mtdoops: Do... |
290 291 |
To use, add console=ttyMTDx to the kernel command line, where x is the MTD device number to use. |
a32159024 mtd: Add mtdswap ... |
292 293 294 295 296 297 298 299 300 |
config MTD_SWAP tristate "Swap on MTD device support" depends on MTD && SWAP select MTD_BLKDEVS help Provides volatile block device driver on top of mtd partition suitable for swapping. The mapping of written blocks is not saved. The driver provides wear leveling by storing erase counter into the OOB. |
1da177e4c Linux-2.6.12-rc2 |
301 302 303 304 305 306 307 |
source "drivers/mtd/chips/Kconfig" source "drivers/mtd/maps/Kconfig" source "drivers/mtd/devices/Kconfig" source "drivers/mtd/nand/Kconfig" |
cd5f6346b [MTD] Add initial... |
308 |
source "drivers/mtd/onenand/Kconfig" |
60f26520e [MTD] LPDDR Makef... |
309 |
source "drivers/mtd/lpddr/Kconfig" |
801c135ce UBI: Unsorted Blo... |
310 |
source "drivers/mtd/ubi/Kconfig" |
ec98c681a Use menuconfig ob... |
311 |
endif # MTD |