drivers/mtd/devices/Kconfig

   1 # drivers/mtd/maps/Kconfig
   2 # $Id: Kconfig,v 1.15 2004/12/22 17:51:15 joern 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 MTD && 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 MTD && 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 config MTD_SLRAM
  51         tristate "Uncached system RAM"
  52         depends on MTD
  53         help
  54           If your CPU cannot cache all of the physical memory in your machine,
  55           you can still use it for storage or swap by using this driver to
  56           present it to the system as a Memory Technology Device.
  57
  58 config MTD_PHRAM
  59         tristate "Physical system RAM"
  60         depends on MTD
  61         help
  62           This is a re-implementation of the slram driver above.
  63
  64           Use this driver to access physical memory that the kernel proper
  65           doesn't have access to, memory beyond the mem=xxx limit, nvram,
  66           memory on the video card, etc...
  67
  68 config MTD_LART
  69         tristate "28F160xx flash driver for LART"
  70         depends on SA1100_LART && MTD
  71         help
  72           This enables the flash driver for LART. Please note that you do
  73           not need any mapping/chip driver for LART. This one does it all
  74           for you, so go disable all of those if you enabled some of them (:
  75
  76 config MTD_MTDRAM
  77         tristate "Test driver using RAM"
  78         depends on MTD
  79         help
  80           This enables a test MTD device driver which uses vmalloc() to
  81           provide storage.  You probably want to say 'N' unless you're
  82           testing stuff.
  83
  84 config MTDRAM_TOTAL_SIZE
  85         int "MTDRAM device size in KiB"
  86         depends on MTD_MTDRAM
  87         default "4096"
  88         help
  89           This allows you to configure the total size of the MTD device
  90           emulated by the MTDRAM driver.  If the MTDRAM driver is built
  91           as a module, it is also possible to specify this as a parameter when
  92           loading the module.
  93
  94 config MTDRAM_ERASE_SIZE
  95         int "MTDRAM erase block size in KiB"
  96         depends on MTD_MTDRAM
  97         default "128"
  98         help
  99           This allows you to configure the size of the erase blocks in the
 100           device emulated by the MTDRAM driver.  If the MTDRAM driver is built
 101           as a module, it is also possible to specify this as a parameter when
 102           loading the module.
 103
 104 #If not a module (I don't want to test it as a module)
 105 config MTDRAM_ABS_POS
 106         hex "SRAM Hexadecimal Absolute position or 0"
 107         depends on MTD_MTDRAM=y
 108         default "0"
 109         help
 110           If you have system RAM accessible by the CPU but not used by Linux
 111           in normal operation, you can give the physical address at which the
 112           available RAM starts, and the MTDRAM driver will use it instead of
 113           allocating space from Linux's available memory. Otherwise, leave
 114           this set to zero. Most people will want to leave this as zero.
 115
 116 config MTD_BLKMTD
 117         tristate "MTD emulation using block device"
 118         depends on MTD
 119         help
 120           This driver allows a block device to appear as an MTD. It would
 121           generally be used in the following cases:
 122
 123           Using Compact Flash as an MTD, these usually present themselves to
 124           the system as an ATA drive.
 125           Testing MTD users (eg JFFS2) on large media and media that might
 126           be removed during a write (using the floppy drive).
 127
 128 config MTD_BLOCK2MTD
 129         tristate "MTD using block device (rewrite)"
 130         depends on MTD && EXPERIMENTAL
 131         help
 132           This driver is basically the same at MTD_BLKMTD above, but
 133           experienced some interface changes plus serious speedups.  In
 134           the long term, it should replace MTD_BLKMTD.  Right now, you
 135           shouldn't entrust important data to it yet.
 136
 137 comment "Disk-On-Chip Device Drivers"
 138
 139 config MTD_DOC2000
 140         tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
 141         depends on MTD
 142         select MTD_DOCPROBE
 143         select MTD_NAND_IDS
 144         ---help---
 145           This provides an MTD device driver for the M-Systems DiskOnChip
 146           2000 and Millennium devices.  Originally designed for the DiskOnChip
 147           2000, it also now includes support for the DiskOnChip Millennium.
 148           If you have problems with this driver and the DiskOnChip Millennium,
 149           you may wish to try the alternative Millennium driver below. To use
 150           the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
 151           in the <file:drivers/mtd/devices/docprobe.c> source code.
 152
 153           If you use this device, you probably also want to enable the NFTL
 154           'NAND Flash Translation Layer' option below, which is used to
 155           emulate a block device by using a kind of file system on the flash
 156           chips.
 157
 158           NOTE: This driver is deprecated and will probably be removed soon.
 159           Please try the new DiskOnChip driver under "NAND Flash Device
 160           Drivers".
 161
 162 config MTD_DOC2001
 163         tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
 164         depends on MTD
 165         select MTD_DOCPROBE
 166         select MTD_NAND_IDS
 167         ---help---
 168           This provides an alternative MTD device driver for the M-Systems
 169           DiskOnChip Millennium devices.  Use this if you have problems with
 170           the combined DiskOnChip 2000 and Millennium driver above.  To get
 171           the DiskOnChip probe code to load and use this driver instead of
 172           the other one, you will need to undefine DOC_SINGLE_DRIVER near
 173           the beginning of <file:drivers/mtd/devices/docprobe.c>.
 174
 175           If you use this device, you probably also want to enable the NFTL
 176           'NAND Flash Translation Layer' option below, which is used to
 177           emulate a block device by using a kind of file system on the flash
 178           chips.
 179
 180           NOTE: This driver is deprecated and will probably be removed soon.
 181           Please try the new DiskOnChip driver under "NAND Flash Device
 182           Drivers".
 183
 184 config MTD_DOC2001PLUS
 185         tristate "M-Systems Disk-On-Chip Millennium Plus"
 186         depends on MTD
 187         select MTD_DOCPROBE
 188         select MTD_NAND_IDS
 189         ---help---
 190           This provides an MTD device driver for the M-Systems DiskOnChip
 191           Millennium Plus devices.
 192
 193           If you use this device, you probably also want to enable the INFTL
 194           'Inverse NAND Flash Translation Layer' option below, which is used
 195           to emulate a block device by using a kind of file system on the
 196           flash chips.
 197
 198           NOTE: This driver will soon be replaced by the new DiskOnChip driver
 199           under "NAND Flash Device Drivers" (currently that driver does not
 200           support all Millennium Plus devices).
 201
 202 config MTD_DOCPROBE
 203         tristate
 204         select MTD_DOCECC
 205
 206 config MTD_DOCECC
 207         tristate
 208
 209 config MTD_DOCPROBE_ADVANCED
 210         bool "Advanced detection options for DiskOnChip"
 211         depends on MTD_DOCPROBE
 212         help
 213           This option allows you to specify nonstandard address at which to
 214           probe for a DiskOnChip, or to change the detection options.  You
 215           are unlikely to need any of this unless you are using LinuxBIOS.
 216           Say 'N'.
 217
 218 config MTD_DOCPROBE_ADDRESS
 219         hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
 220         depends on MTD_DOCPROBE
 221         default "0x0000" if MTD_DOCPROBE_ADVANCED
 222         default "0" if !MTD_DOCPROBE_ADVANCED
 223         ---help---
 224           By default, the probe for DiskOnChip devices will look for a
 225           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 226           This option allows you to specify a single address at which to probe
 227           for the device, which is useful if you have other devices in that
 228           range which get upset when they are probed.
 229
 230           (Note that on PowerPC, the normal probe will only check at
 231           0xE4000000.)
 232
 233           Normally, you should leave this set to zero, to allow the probe at
 234           the normal addresses.
 235
 236 config MTD_DOCPROBE_HIGH
 237         bool "Probe high addresses"
 238         depends on MTD_DOCPROBE_ADVANCED
 239         help
 240           By default, the probe for DiskOnChip devices will look for a
 241           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 242           This option changes to make it probe between 0xFFFC8000 and
 243           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
 244           useful to you.  Say 'N'.
 245
 246 config MTD_DOCPROBE_55AA
 247         bool "Probe for 0x55 0xAA BIOS Extension Signature"
 248         depends on MTD_DOCPROBE_ADVANCED
 249         help
 250           Check for the 0x55 0xAA signature of a DiskOnChip, and do not
 251           continue with probing if it is absent.  The signature will always be
 252           present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
 253           Only if you have overwritten the first block of a DiskOnChip
 254           Millennium will it be absent.  Enable this option if you are using
 255           LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
 256           you have managed to wipe the first block.
 257
 258 endmenu
 259