1# 2# PCCARD (PCMCIA/CardBus) bus subsystem configuration 3# 4 5menuconfig PCCARD 6 tristate "PCCard (PCMCIA/CardBus) support" 7 ---help--- 8 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux 9 computer. These are credit-card size devices such as network cards, 10 modems or hard drives often used with laptops computers. There are 11 actually two varieties of these cards: 16 bit PCMCIA and 32 bit 12 CardBus cards. 13 14 To compile this driver as modules, choose M here: the 15 module will be called pcmcia_core. 16 17if PCCARD 18 19config PCMCIA 20 tristate "16-bit PCMCIA support" 21 select CRC32 22 default y 23 ---help--- 24 This option enables support for 16-bit PCMCIA cards. Most older 25 PC-cards are such 16-bit PCMCIA cards, so unless you know you're 26 only using 32-bit CardBus cards, say Y or M here. 27 28 To use 16-bit PCMCIA cards, you will need supporting software in 29 most cases. (see the file <file:Documentation/Changes> for 30 location and details). 31 32 To compile this driver as modules, choose M here: the 33 module will be called pcmcia. 34 35 If unsure, say Y. 36 37config PCMCIA_LOAD_CIS 38 bool "Load CIS updates from userspace" 39 depends on PCMCIA 40 select FW_LOADER 41 default y 42 help 43 Some PCMCIA cards require an updated Card Information Structure (CIS) 44 to be loaded from userspace to work correctly. If you say Y here, 45 and your userspace is arranged correctly, this will be loaded 46 automatically using the in-kernel firmware loader and the hotplug 47 subsystem, instead of relying on cardmgr from pcmcia-cs to do so. 48 49 If unsure, say Y. 50 51config CARDBUS 52 bool "32-bit CardBus support" 53 depends on PCI 54 default y 55 ---help--- 56 CardBus is a bus mastering architecture for PC-cards, which allows 57 for 32 bit PC-cards (the original PCMCIA standard specifies only 58 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. 59 60 To use 32 bit PC-cards, you also need a CardBus compatible host 61 bridge. Virtually all modern PCMCIA bridges do this, and most of 62 them are "yenta-compatible", so say Y or M there, too. 63 64 If unsure, say Y. 65 66comment "PC-card bridges" 67 68config YENTA 69 tristate "CardBus yenta-compatible bridge support" 70 depends on PCI 71 select CARDBUS if !EXPERT 72 select PCCARD_NONSTATIC if PCMCIA != n && ISA 73 select PCCARD_PCI if PCMCIA !=n && !ISA 74 ---help--- 75 This option enables support for CardBus host bridges. Virtually 76 all modern PCMCIA bridges are CardBus compatible. A "bridge" is 77 the hardware inside your computer that PCMCIA cards are plugged 78 into. 79 80 To compile this driver as modules, choose M here: the 81 module will be called yenta_socket. 82 83 If unsure, say Y. 84 85config YENTA_O2 86 default y 87 bool "Special initialization for O2Micro bridges" if EXPERT 88 depends on YENTA 89 90config YENTA_RICOH 91 default y 92 bool "Special initialization for Ricoh bridges" if EXPERT 93 depends on YENTA 94 95config YENTA_TI 96 default y 97 bool "Special initialization for TI and EnE bridges" if EXPERT 98 depends on YENTA 99 100config YENTA_ENE_TUNE 101 default y 102 bool "Auto-tune EnE bridges for CB cards" if EXPERT 103 depends on YENTA_TI && CARDBUS 104 105config YENTA_TOSHIBA 106 default y 107 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT 108 depends on YENTA 109 110config PD6729 111 tristate "Cirrus PD6729 compatible bridge support" 112 depends on PCMCIA && PCI 113 select PCCARD_NONSTATIC if PCMCIA != n && ISA 114 select PCCARD_PCI if PCMCIA !=n && !ISA 115 help 116 This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge 117 device, found in some older laptops and PCMCIA card readers. 118 119config I82092 120 tristate "i82092 compatible bridge support" 121 depends on PCMCIA && PCI 122 select PCCARD_NONSTATIC if PCMCIA != n && ISA 123 select PCCARD_PCI if PCMCIA !=n && !ISA 124 help 125 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device, 126 found in some older laptops and more commonly in evaluation boards for the 127 chip. 128 129config I82365 130 tristate "i82365 compatible bridge support" 131 depends on PCMCIA && ISA 132 select PCCARD_NONSTATIC 133 help 134 Say Y here to include support for ISA-bus PCMCIA host bridges that 135 are register compatible with the Intel i82365. These are found on 136 older laptops and ISA-bus card readers for desktop systems. A 137 "bridge" is the hardware inside your computer that PCMCIA cards are 138 plugged into. If unsure, say N. 139 140config TCIC 141 tristate "Databook TCIC host bridge support" 142 depends on PCMCIA && ISA 143 select PCCARD_NONSTATIC 144 help 145 Say Y here to include support for the Databook TCIC family of PCMCIA 146 host bridges. These are only found on a handful of old systems. 147 "Bridge" is the name used for the hardware inside your computer that 148 PCMCIA cards are plugged into. If unsure, say N. 149 150config PCMCIA_ALCHEMY_DEVBOARD 151 tristate "Alchemy Db/Pb1xxx PCMCIA socket services" 152 depends on MIPS_ALCHEMY && PCMCIA 153 help 154 Enable this driver of you want PCMCIA support on your Alchemy 155 Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300 156 board. NOT suitable for the PB1000! 157 158 This driver is also available as a module called db1xxx_ss.ko 159 160config PCMCIA_XXS1500 161 tristate "MyCable XXS1500 PCMCIA socket support" 162 depends on PCMCIA && MIPS_XXS1500 163 help 164 Support for the PCMCIA/CF socket interface on MyCable XXS1500 165 systems. 166 167 This driver is also available as a module called xxs1500_ss.ko 168 169config PCMCIA_BCM63XX 170 tristate "bcm63xx pcmcia support" 171 depends on BCM63XX && PCMCIA 172 173config PCMCIA_SOC_COMMON 174 tristate 175 176config PCMCIA_SA11XX_BASE 177 tristate 178 179config PCMCIA_SA1100 180 tristate "SA1100 support" 181 depends on ARM && ARCH_SA1100 && PCMCIA 182 select PCMCIA_SOC_COMMON 183 select PCMCIA_SA11XX_BASE 184 help 185 Say Y here to include support for SA11x0-based PCMCIA or CF 186 sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/ 187 Xscale(R) embedded machines. 188 189 This driver is also available as a module called sa1100_cs. 190 191config PCMCIA_SA1111 192 tristate "SA1111 support" 193 depends on ARM && SA1111 && PCMCIA 194 select PCMCIA_SOC_COMMON 195 select PCMCIA_SA11XX_BASE if ARCH_SA1100 196 select PCMCIA_PXA2XX if ARCH_LUBBOCK && SA1111 197 help 198 Say Y here to include support for SA1111-based PCMCIA or CF 199 sockets, found on the Jornada 720, Graphicsmaster and other 200 StrongARM(R)/Xscale(R) embedded machines. 201 202 This driver is also available as a module called sa1111_cs. 203 204config PCMCIA_PXA2XX 205 tristate "PXA2xx support" 206 depends on ARM && ARCH_PXA && PCMCIA 207 depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \ 208 || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \ 209 || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \ 210 || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \ 211 || MACH_COLIBRI320 || MACH_H4700) 212 select PCMCIA_SOC_COMMON 213 help 214 Say Y here to include support for the PXA2xx PCMCIA controller 215 216config PCMCIA_DEBUG 217 bool "Enable debugging" 218 depends on (PCMCIA_SA1111 || PCMCIA_SA1100 || PCMCIA_PXA2XX) 219 help 220 Say Y here to enable debugging for the SoC PCMCIA layer. 221 You will need to choose the debugging level either via the 222 kernel command line, or module options depending whether 223 you build the drivers as modules. 224 225 The kernel command line options are: 226 sa11xx_core.pc_debug=N 227 pxa2xx_core.pc_debug=N 228 229 The module option is called pc_debug=N 230 231 In all the above examples, N is the debugging verbosity 232 level. 233 234config PCMCIA_PROBE 235 bool 236 default y if ISA && !ARCH_SA1100 && !PARISC 237 238config M32R_PCC 239 bool "M32R PCMCIA I/F" 240 depends on M32R && CHIP_M32700 && PCMCIA 241 help 242 Say Y here to use the M32R PCMCIA controller. 243 244config M32R_CFC 245 bool "M32R CF I/F Controller" 246 depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT) 247 help 248 Say Y here to use the M32R CompactFlash controller. 249 250config M32R_CFC_NUM 251 int "M32R CF I/F number" 252 depends on M32R_CFC 253 default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT 254 help 255 Set the number of M32R CF slots. 256 257config PCMCIA_VRC4171 258 tristate "NEC VRC4171 Card Controllers support" 259 depends on CPU_VR41XX && ISA && PCMCIA 260 261config PCMCIA_VRC4173 262 tristate "NEC VRC4173 CARDU support" 263 depends on CPU_VR41XX && PCI && PCMCIA 264 265config OMAP_CF 266 tristate "OMAP CompactFlash Controller" 267 depends on PCMCIA && ARCH_OMAP16XX 268 help 269 Say Y here to support the CompactFlash controller on OMAP. 270 Note that this doesn't support "True IDE" mode. 271 272config BFIN_CFPCMCIA 273 tristate "Blackfin CompactFlash PCMCIA Driver" 274 depends on PCMCIA && BLACKFIN 275 help 276 Say Y here to support the CompactFlash PCMCIA driver for Blackfin. 277 278 279config AT91_CF 280 tristate "AT91 CompactFlash Controller" 281 depends on PCMCIA && ARCH_AT91 282 depends on !ARCH_MULTIPLATFORM 283 help 284 Say Y here to support the CompactFlash controller on AT91 chips. 285 Or choose M to compile the driver as a module named "at91_cf". 286 287config ELECTRA_CF 288 tristate "Electra CompactFlash Controller" 289 depends on PCMCIA && PPC_PASEMI 290 help 291 Say Y here to support the CompactFlash controller on the 292 PA Semi Electra eval board. 293 294config PCCARD_PCI 295 bool 296 297config PCCARD_NONSTATIC 298 bool 299 300config PCCARD_IODYN 301 bool 302 303endif # PCCARD 304