| Kconfig (292dd876ee765c478b27c93cc51e93a558ed58bf) | Kconfig (acc8dadc0b3f007e6e60da77feb2efe2a19c5cda) |
|---|---|
| 1# drivers/mtd/maps/Kconfig 2# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $ 3 4menu "Self-contained MTD device drivers" 5 depends on MTD!=n 6 7config MTD_PMC551 8 tristate "Ramix PMC551 PCI Mezzanine RAM card support" --- 115 unchanged lines hidden (view full) --- 124 default "0" 125 help 126 If you have system RAM accessible by the CPU but not used by Linux 127 in normal operation, you can give the physical address at which the 128 available RAM starts, and the MTDRAM driver will use it instead of 129 allocating space from Linux's available memory. Otherwise, leave 130 this set to zero. Most people will want to leave this as zero. 131 | 1# drivers/mtd/maps/Kconfig 2# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $ 3 4menu "Self-contained MTD device drivers" 5 depends on MTD!=n 6 7config MTD_PMC551 8 tristate "Ramix PMC551 PCI Mezzanine RAM card support" --- 115 unchanged lines hidden (view full) --- 124 default "0" 125 help 126 If you have system RAM accessible by the CPU but not used by Linux 127 in normal operation, you can give the physical address at which the 128 available RAM starts, and the MTDRAM driver will use it instead of 129 allocating space from Linux's available memory. Otherwise, leave 130 this set to zero. Most people will want to leave this as zero. 131 |
| 132config MTD_BLKMTD 133 tristate "MTD emulation using block device" | 132config MTD_BLOCK2MTD 133 tristate "MTD using block device" |
| 134 depends on MTD 135 help 136 This driver allows a block device to appear as an MTD. It would 137 generally be used in the following cases: 138 139 Using Compact Flash as an MTD, these usually present themselves to 140 the system as an ATA drive. 141 Testing MTD users (eg JFFS2) on large media and media that might 142 be removed during a write (using the floppy drive). 143 | 134 depends on MTD 135 help 136 This driver allows a block device to appear as an MTD. It would 137 generally be used in the following cases: 138 139 Using Compact Flash as an MTD, these usually present themselves to 140 the system as an ATA drive. 141 Testing MTD users (eg JFFS2) on large media and media that might 142 be removed during a write (using the floppy drive). 143 |
| 144config MTD_BLOCK2MTD 145 tristate "MTD using block device (rewrite)" 146 depends on MTD && EXPERIMENTAL 147 help 148 This driver is basically the same at MTD_BLKMTD above, but 149 experienced some interface changes plus serious speedups. In 150 the long term, it should replace MTD_BLKMTD. Right now, you 151 shouldn't entrust important data to it yet. 152 | |
| 153comment "Disk-On-Chip Device Drivers" 154 155config MTD_DOC2000 156 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)" 157 depends on MTD 158 select MTD_DOCPROBE 159 select MTD_NAND_IDS 160 ---help--- --- 116 unchanged lines hidden --- | 144comment "Disk-On-Chip Device Drivers" 145 146config MTD_DOC2000 147 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)" 148 depends on MTD 149 select MTD_DOCPROBE 150 select MTD_NAND_IDS 151 ---help--- --- 116 unchanged lines hidden --- |