drivers/mtd/devices/Kconfig

   1 # drivers/mtd/maps/Kconfig
   2 # $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
   3
   4 menu "Self-contained MTD device drivers"
   5         depends on MTD!=n
   6
   7 config MTD_PMC551
   8         tristate "Ramix PMC551 PCI Mezzanine RAM card support"
   9         depends on PCI
  10         ---help---
  11           This provides a MTD device driver for the Ramix PMC551 RAM PCI card
  12           from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
  13           These devices come in memory configurations from 32M - 1G.  If you
  14           have one, you probably want to enable this.
  15
  16           If this driver is compiled as a module you get the ability to select
  17           the size of the aperture window pointing into the devices memory.
  18           What this means is that if you have a 1G card, normally the kernel
  19           will use a 1G memory map as its view of the device.  As a module,
  20           you can select a 1M window into the memory and the driver will
  21           "slide" the window around the PMC551's memory.  This was
  22           particularly useful on the 2.2 kernels on PPC architectures as there
  23           was limited kernel space to deal with.
  24
  25 config MTD_PMC551_BUGFIX
  26         bool "PMC551 256M DRAM Bugfix"
  27         depends on MTD_PMC551
  28         help
  29           Some of Ramix's PMC551 boards with 256M configurations have invalid
  30           column and row mux values.  This option will fix them, but will
  31           break other memory configurations.  If unsure say N.
  32
  33 config MTD_PMC551_DEBUG
  34         bool "PMC551 Debugging"
  35         depends on MTD_PMC551
  36         help
  37           This option makes the PMC551 more verbose during its operation and
  38           is only really useful if you are developing on this driver or
  39           suspect a possible hardware or driver bug.  If unsure say N.
  40
  41 config MTD_MS02NV
  42         tristate "DEC MS02-NV NVRAM module support"
  43         depends on MACH_DECSTATION
  44         help
  45           This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
  46           backed-up NVRAM module.  The module was originally meant as an NFS
  47           accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
  48           DECsystem 5900 equipped with such a module.
  49
  50           If you want to compile this driver as a module ( = code which can be
  51           inserted in and removed from the running kernel whenever you want),
  52           say M here and read <file:Documentation/modules.txt>.  The module will
  53           be called ms02-nv.o.
  54
  55 config MTD_DATAFLASH
  56         tristate "Support for AT45xxx DataFlash"
  57         depends on SPI_MASTER && EXPERIMENTAL
  58         help
  59           This enables access to AT45xxx DataFlash chips, using SPI.
  60           Sometimes DataFlash chips are packaged inside MMC-format
  61           cards; at this writing, the MMC stack won't handle those.
  62
  63 config MTD_DATAFLASH26
  64         tristate "AT91RM9200 DataFlash AT26xxx"
  65         depends on MTD && ARCH_AT91RM9200 && AT91_SPI
  66         help
  67           This enables access to the DataFlash chip (AT26xxx) on an
  68           AT91RM9200-based board.
  69           If you have such a board and such a DataFlash, say 'Y'.
  70
  71 config MTD_M25P80
  72         tristate "Support for M25 SPI Flash"
  73         depends on SPI_MASTER && EXPERIMENTAL
  74         help
  75           This enables access to ST M25P80 and similar SPI flash chips,
  76           used for program and data storage.  Set up your spi devices
  77           with the right board-specific platform data.
  78
  79 config MTD_SLRAM
  80         tristate "Uncached system RAM"
  81         help
  82           If your CPU cannot cache all of the physical memory in your machine,
  83           you can still use it for storage or swap by using this driver to
  84           present it to the system as a Memory Technology Device.
  85
  86 config MTD_PHRAM
  87         tristate "Physical system RAM"
  88         help
  89           This is a re-implementation of the slram driver above.
  90
  91           Use this driver to access physical memory that the kernel proper
  92           doesn't have access to, memory beyond the mem=xxx limit, nvram,
  93           memory on the video card, etc...
  94
  95 config MTD_LART
  96         tristate "28F160xx flash driver for LART"
  97         depends on SA1100_LART
  98         help
  99           This enables the flash driver for LART. Please note that you do
 100           not need any mapping/chip driver for LART. This one does it all
 101           for you, so go disable all of those if you enabled some of them (:
 102
 103 config MTD_MTDRAM
 104         tristate "Test driver using RAM"
 105         help
 106           This enables a test MTD device driver which uses vmalloc() to
 107           provide storage.  You probably want to say 'N' unless you're
 108           testing stuff.
 109
 110 config MTDRAM_TOTAL_SIZE
 111         int "MTDRAM device size in KiB"
 112         depends on MTD_MTDRAM
 113         default "4096"
 114         help
 115           This allows you to configure the total size of the MTD device
 116           emulated by the MTDRAM driver.  If the MTDRAM driver is built
 117           as a module, it is also possible to specify this as a parameter when
 118           loading the module.
 119
 120 config MTDRAM_ERASE_SIZE
 121         int "MTDRAM erase block size in KiB"
 122         depends on MTD_MTDRAM
 123         default "128"
 124         help
 125           This allows you to configure the size of the erase blocks in the
 126           device emulated by the MTDRAM driver.  If the MTDRAM driver is built
 127           as a module, it is also possible to specify this as a parameter when
 128           loading the module.
 129
 130 #If not a module (I don't want to test it as a module)
 131 config MTDRAM_ABS_POS
 132         hex "SRAM Hexadecimal Absolute position or 0"
 133         depends on MTD_MTDRAM=y
 134         default "0"
 135         help
 136           If you have system RAM accessible by the CPU but not used by Linux
 137           in normal operation, you can give the physical address at which the
 138           available RAM starts, and the MTDRAM driver will use it instead of
 139           allocating space from Linux's available memory. Otherwise, leave
 140           this set to zero. Most people will want to leave this as zero.
 141
 142 config MTD_BLOCK2MTD
 143         tristate "MTD using block device"
 144         depends on BLOCK
 145         help
 146           This driver allows a block device to appear as an MTD. It would
 147           generally be used in the following cases:
 148
 149           Using Compact Flash as an MTD, these usually present themselves to
 150           the system as an ATA drive.
 151           Testing MTD users (eg JFFS2) on large media and media that might
 152           be removed during a write (using the floppy drive).
 153
 154 comment "Disk-On-Chip Device Drivers"
 155
 156 config MTD_DOC2000
 157         tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
 158         select MTD_DOCPROBE
 159         select MTD_NAND_IDS
 160         ---help---
 161           This provides an MTD device driver for the M-Systems DiskOnChip
 162           2000 and Millennium devices.  Originally designed for the DiskOnChip
 163           2000, it also now includes support for the DiskOnChip Millennium.
 164           If you have problems with this driver and the DiskOnChip Millennium,
 165           you may wish to try the alternative Millennium driver below. To use
 166           the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
 167           in the <file:drivers/mtd/devices/docprobe.c> source code.
 168
 169           If you use this device, you probably also want to enable the NFTL
 170           'NAND Flash Translation Layer' option below, which is used to
 171           emulate a block device by using a kind of file system on the flash
 172           chips.
 173
 174           NOTE: This driver is deprecated and will probably be removed soon.
 175           Please try the new DiskOnChip driver under "NAND Flash Device
 176           Drivers".
 177
 178 config MTD_DOC2001
 179         tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
 180         select MTD_DOCPROBE
 181         select MTD_NAND_IDS
 182         ---help---
 183           This provides an alternative MTD device driver for the M-Systems
 184           DiskOnChip Millennium devices.  Use this if you have problems with
 185           the combined DiskOnChip 2000 and Millennium driver above.  To get
 186           the DiskOnChip probe code to load and use this driver instead of
 187           the other one, you will need to undefine DOC_SINGLE_DRIVER near
 188           the beginning of <file:drivers/mtd/devices/docprobe.c>.
 189
 190           If you use this device, you probably also want to enable the NFTL
 191           'NAND Flash Translation Layer' option below, which is used to
 192           emulate a block device by using a kind of file system on the flash
 193           chips.
 194
 195           NOTE: This driver is deprecated and will probably be removed soon.
 196           Please try the new DiskOnChip driver under "NAND Flash Device
 197           Drivers".
 198
 199 config MTD_DOC2001PLUS
 200         tristate "M-Systems Disk-On-Chip Millennium Plus"
 201         select MTD_DOCPROBE
 202         select MTD_NAND_IDS
 203         ---help---
 204           This provides an MTD device driver for the M-Systems DiskOnChip
 205           Millennium Plus devices.
 206
 207           If you use this device, you probably also want to enable the INFTL
 208           'Inverse NAND Flash Translation Layer' option below, which is used
 209           to emulate a block device by using a kind of file system on the
 210           flash chips.
 211
 212           NOTE: This driver will soon be replaced by the new DiskOnChip driver
 213           under "NAND Flash Device Drivers" (currently that driver does not
 214           support all Millennium Plus devices).
 215
 216 config MTD_DOCPROBE
 217         tristate
 218         select MTD_DOCECC
 219
 220 config MTD_DOCECC
 221         tristate
 222
 223 config MTD_DOCPROBE_ADVANCED
 224         bool "Advanced detection options for DiskOnChip"
 225         depends on MTD_DOCPROBE
 226         help
 227           This option allows you to specify nonstandard address at which to
 228           probe for a DiskOnChip, or to change the detection options.  You
 229           are unlikely to need any of this unless you are using LinuxBIOS.
 230           Say 'N'.
 231
 232 config MTD_DOCPROBE_ADDRESS
 233         hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
 234         depends on MTD_DOCPROBE
 235         default "0x0000" if MTD_DOCPROBE_ADVANCED
 236         default "0" if !MTD_DOCPROBE_ADVANCED
 237         ---help---
 238           By default, the probe for DiskOnChip devices will look for a
 239           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 240           This option allows you to specify a single address at which to probe
 241           for the device, which is useful if you have other devices in that
 242           range which get upset when they are probed.
 243
 244           (Note that on PowerPC, the normal probe will only check at
 245           0xE4000000.)
 246
 247           Normally, you should leave this set to zero, to allow the probe at
 248           the normal addresses.
 249
 250 config MTD_DOCPROBE_HIGH
 251         bool "Probe high addresses"
 252         depends on MTD_DOCPROBE_ADVANCED
 253         help
 254           By default, the probe for DiskOnChip devices will look for a
 255           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 256           This option changes to make it probe between 0xFFFC8000 and
 257           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
 258           useful to you.  Say 'N'.
 259
 260 config MTD_DOCPROBE_55AA
 261         bool "Probe for 0x55 0xAA BIOS Extension Signature"
 262         depends on MTD_DOCPROBE_ADVANCED
 263         help
 264           Check for the 0x55 0xAA signature of a DiskOnChip, and do not
 265           continue with probing if it is absent.  The signature will always be
 266           present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
 267           Only if you have overwritten the first block of a DiskOnChip
 268           Millennium will it be absent.  Enable this option if you are using
 269           LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
 270           you have managed to wipe the first block.
 271
 272 endmenu
 273