drivers/mtd/Kconfig

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