drivers/mtd/Kconfig

   1 # $Id: Kconfig,v 1.11 2005/11/07 11:14:19 gleixner Exp $
   2
   3 menuconfig MTD
   4         tristate "Memory Technology Device (MTD) support"
   5         depends on HAS_IOMEM
   6         help
   7           Memory Technology Devices are flash, RAM and similar chips, often
   8           used for solid state file systems on embedded devices. This option
   9           will provide the generic support for MTD drivers to register
  10           themselves with the kernel and for potential users of MTD devices
  11           to enumerate the devices which are present and obtain a handle on
  12           them. It will also allow you to select individual drivers for
  13           particular hardware and users of MTD devices. If unsure, say N.
  14
  15 if MTD
  16
  17 config MTD_DEBUG
  18         bool "Debugging"
  19         help
  20           This turns on low-level debugging for the entire MTD sub-system.
  21           Normally, you should say 'N'.
  22
  23 config MTD_DEBUG_VERBOSE
  24         int "Debugging verbosity (0 = quiet, 3 = noisy)"
  25         depends on MTD_DEBUG
  26         default "0"
  27         help
  28           Determines the verbosity level of the MTD debugging messages.
  29
  30 config MTD_CONCAT
  31         tristate "MTD concatenating support"
  32         help
  33           Support for concatenating several MTD devices into a single
  34           (virtual) one. This allows you to have -for example- a JFFS(2)
  35           file system spanning multiple physical flash chips. If unsure,
  36           say 'Y'.
  37
  38 config MTD_PARTITIONS
  39         bool "MTD partitioning support"
  40         help
  41           If you have a device which needs to divide its flash chip(s) up
  42           into multiple 'partitions', each of which appears to the user as
  43           a separate MTD device, you require this option to be enabled. If
  44           unsure, say 'Y'.
  45
  46           Note, however, that you don't need this option for the DiskOnChip
  47           devices. Partitioning on NFTL 'devices' is a different - that's the
  48           'normal' form of partitioning used on a block device.
  49
  50 config MTD_REDBOOT_PARTS
  51         tristate "RedBoot partition table parsing"
  52         depends on MTD_PARTITIONS
  53         ---help---
  54           RedBoot is a ROM monitor and bootloader which deals with multiple
  55           'images' in flash devices by putting a table one of the erase
  56           blocks on the device, similar to a partition table, which gives
  57           the offsets, lengths and names of all the images stored in the
  58           flash.
  59
  60           If you need code which can detect and parse this table, and register
  61           MTD 'partitions' corresponding to each image in the table, enable
  62           this option.
  63
  64           You will still need the parsing functions to be called by the driver
  65           for your particular device. It won't happen automatically. The
  66           SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
  67           example.
  68
  69 config MTD_REDBOOT_DIRECTORY_BLOCK
  70         int "Location of RedBoot partition table"
  71         depends on MTD_REDBOOT_PARTS
  72         default "-1"
  73         ---help---
  74           This option is the Linux counterpart to the
  75           CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
  76           option.
  77
  78           The option specifies which Flash sectors holds the RedBoot
  79           partition table.  A zero or positive value gives an absolute
  80           erase block number. A negative value specifies a number of
  81           sectors before the end of the device.
  82
  83           For example "2" means block number 2, "-1" means the last
  84           block and "-2" means the penultimate block.
  85
  86 config MTD_REDBOOT_PARTS_UNALLOCATED
  87         bool "Include unallocated flash regions"
  88         depends on MTD_REDBOOT_PARTS
  89         help
  90           If you need to register each unallocated flash region as a MTD
  91           'partition', enable this option.
  92
  93 config MTD_REDBOOT_PARTS_READONLY
  94         bool "Force read-only for RedBoot system images"
  95         depends on MTD_REDBOOT_PARTS
  96         help
  97           If you need to force read-only for 'RedBoot', 'RedBoot Config' and
  98           'FIS directory' images, enable this option.
  99
 100 config MTD_CMDLINE_PARTS
 101         bool "Command line partition table parsing"
 102         depends on MTD_PARTITIONS = "y" && MTD = "y"
 103         ---help---
 104           Allow generic configuration of the MTD partition tables via the kernel
 105           command line. Multiple flash resources are supported for hardware where
 106           different kinds of flash memory are available.
 107
 108           You will still need the parsing functions to be called by the driver
 109           for your particular device. It won't happen automatically. The
 110           SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
 111           example.
 112
 113           The format for the command line is as follows:
 114
 115           mtdparts=<mtddef>[;<mtddef]
 116           <mtddef>  := <mtd-id>:<partdef>[,<partdef>]
 117           <partdef> := <size>[@offset][<name>][ro]
 118           <mtd-id>  := unique id used in mapping driver/device
 119           <size>    := standard linux memsize OR "-" to denote all
 120           remaining space
 121           <name>    := (NAME)
 122
 123           Due to the way Linux handles the command line, no spaces are
 124           allowed in the partition definition, including mtd id's and partition
 125           names.
 126
 127           Examples:
 128
 129           1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
 130           mtdparts=sa1100:-
 131
 132           Same flash, but 2 named partitions, the first one being read-only:
 133           mtdparts=sa1100:256k(ARMboot)ro,-(root)
 134
 135           If unsure, say 'N'.
 136
 137 config MTD_AFS_PARTS
 138         tristate "ARM Firmware Suite partition parsing"
 139         depends on ARM && MTD_PARTITIONS
 140         ---help---
 141           The ARM Firmware Suite allows the user to divide flash devices into
 142           multiple 'images'. Each such image has a header containing its name
 143           and offset/size etc.
 144
 145           If you need code which can detect and parse these tables, and
 146           register MTD 'partitions' corresponding to each image detected,
 147           enable this option.
 148
 149           You will still need the parsing functions to be called by the driver
 150           for your particular device. It won't happen automatically. The
 151           'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
 152
 153 config MTD_OF_PARTS
 154         tristate "Flash partition map based on OF description"
 155         depends on PPC_OF && MTD_PARTITIONS
 156         help
 157           This provides a partition parsing function which derives
 158           the partition map from the children of the flash node,
 159           as described in Documentation/powerpc/booting-without-of.txt.
 160
 161 comment "User Modules And Translation Layers"
 162
 163 config MTD_CHAR
 164         tristate "Direct char device access to MTD devices"
 165         help
 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.
 170
 171 config MTD_BLKDEVS
 172         tristate "Common interface to block layer for MTD 'translation layers'"
 173         depends on BLOCK
 174         default n
 175
 176 config MTD_BLOCK
 177         tristate "Caching block device access to MTD devices"
 178         depends on BLOCK
 179         select MTD_BLKDEVS
 180         ---help---
 181           Although most flash chips have an erase size too large to be useful
 182           as block devices, it is possible to use MTD devices which are based
 183           on RAM chips in this manner. This block device is a user of MTD
 184           devices performing that function.
 185
 186           At the moment, it is also required for the Journalling Flash File
 187           System(s) to obtain a handle on the MTD device when it's mounted
 188           (although JFFS and JFFS2 don't actually use any of the functionality
 189           of the mtdblock device).
 190
 191           Later, it may be extended to perform read/erase/modify/write cycles
 192           on flash chips to emulate a smaller block size. Needless to say,
 193           this is very unsafe, but could be useful for file systems which are
 194           almost never written to.
 195
 196           You do not need this option for use with the DiskOnChip devices. For
 197           those, enable NFTL support (CONFIG_NFTL) instead.
 198
 199 config MTD_BLOCK_RO
 200         tristate "Readonly block device access to MTD devices"
 201         depends on MTD_BLOCK!=y && BLOCK
 202         select MTD_BLKDEVS
 203         help
 204           This allows you to mount read-only file systems (such as cramfs)
 205           from an MTD device, without the overhead (and danger) of the caching
 206           driver.
 207
 208           You do not need this option for use with the DiskOnChip devices. For
 209           those, enable NFTL support (CONFIG_NFTL) instead.
 210
 211 config FTL
 212         tristate "FTL (Flash Translation Layer) support"
 213         depends on BLOCK
 214         select MTD_BLKDEVS
 215         ---help---
 216           This provides support for the original Flash Translation Layer which
 217           is part of the PCMCIA specification. It uses a kind of pseudo-
 218           file system on a flash device to emulate a block device with
 219           512-byte sectors, on top of which you put a 'normal' file system.
 220
 221           You may find that the algorithms used in this code are patented
 222           unless you live in the Free World where software patents aren't
 223           legal - in the USA you are only permitted to use this on PCMCIA
 224           hardware, although under the terms of the GPL you're obviously
 225           permitted to copy, modify and distribute the code as you wish. Just
 226           not use it.
 227
 228 config NFTL
 229         tristate "NFTL (NAND Flash Translation Layer) support"
 230         depends on BLOCK
 231         select MTD_BLKDEVS
 232         ---help---
 233           This provides support for the NAND Flash Translation Layer which is
 234           used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
 235           file system on a flash device to emulate a block device with
 236           512-byte sectors, on top of which you put a 'normal' file system.
 237
 238           You may find that the algorithms used in this code are patented
 239           unless you live in the Free World where software patents aren't
 240           legal - in the USA you are only permitted to use this on DiskOnChip
 241           hardware, although under the terms of the GPL you're obviously
 242           permitted to copy, modify and distribute the code as you wish. Just
 243           not use it.
 244
 245 config NFTL_RW
 246         bool "Write support for NFTL"
 247         depends on NFTL
 248         help
 249           Support for writing to the NAND Flash Translation Layer, as used
 250           on the DiskOnChip.
 251
 252 config INFTL
 253         tristate "INFTL (Inverse NAND Flash Translation Layer) support"
 254         depends on BLOCK
 255         select MTD_BLKDEVS
 256         ---help---
 257           This provides support for the Inverse NAND Flash Translation
 258           Layer which is used on M-Systems' newer DiskOnChip devices. It
 259           uses a kind of pseudo-file system on a flash device to emulate
 260           a block device with 512-byte sectors, on top of which you put
 261           a 'normal' file system.
 262
 263           You may find that the algorithms used in this code are patented
 264           unless you live in the Free World where software patents aren't
 265           legal - in the USA you are only permitted to use this on DiskOnChip
 266           hardware, although under the terms of the GPL you're obviously
 267           permitted to copy, modify and distribute the code as you wish. Just
 268           not use it.
 269
 270 config RFD_FTL
 271         tristate "Resident Flash Disk (Flash Translation Layer) support"
 272         depends on BLOCK
 273         select MTD_BLKDEVS
 274         ---help---
 275           This provides support for the flash translation layer known
 276           as the Resident Flash Disk (RFD), as used by the Embedded BIOS
 277           of General Software. There is a blurb at:
 278
 279                 http://www.gensw.com/pages/prod/bios/rfd.htm
 280
 281 config SSFDC
 282         tristate "NAND SSFDC (SmartMedia) read only translation layer"
 283         depends on BLOCK
 284         select MTD_BLKDEVS
 285         help
 286           This enables read only access to SmartMedia formatted NAND
 287           flash. You can mount it with FAT file system.
 288
 289 config MTD_OOPS
 290         tristate "Log panic/oops to an MTD buffer"
 291         depends on MTD
 292         help
 293           This enables panic and oops messages to be logged to a circular
 294           buffer in a flash partition where it can be read back at some
 295           later point.
 296
 297           To use, add console=ttyMTDx to the kernel command line,
 298           where x is the MTD device number to use.
 299
 300 source "drivers/mtd/chips/Kconfig"
 301
 302 source "drivers/mtd/maps/Kconfig"
 303
 304 source "drivers/mtd/devices/Kconfig"
 305
 306 source "drivers/mtd/nand/Kconfig"
 307
 308 source "drivers/mtd/onenand/Kconfig"
 309
 310 source "drivers/mtd/ubi/Kconfig"
 311
 312 endif # MTD