2 # PCCARD (PCMCIA/CardBus) bus subsystem configuration
6 tristate "PCCard (PCMCIA/CardBus) support"
9 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
10 computer. These are credit-card size devices such as network cards,
11 modems or hard drives often used with laptops computers. There are
12 actually two varieties of these cards: 16 bit PCMCIA and 32 bit
15 To compile this driver as modules, choose M here: the
16 module will be called pcmcia_core.
21 tristate "16-bit PCMCIA support"
25 This option enables support for 16-bit PCMCIA cards. Most older
26 PC-cards are such 16-bit PCMCIA cards, so unless you know you're
27 only using 32-bit CardBus cards, say Y or M here.
29 To use 16-bit PCMCIA cards, you will need supporting software in
30 most cases. (see the file <file:Documentation/Changes> for
31 location and details).
33 To compile this driver as modules, choose M here: the
34 module will be called pcmcia.
38 config PCMCIA_LOAD_CIS
39 bool "Load CIS updates from userspace (EXPERIMENTAL)"
40 depends on PCMCIA && EXPERIMENTAL
44 Some PCMCIA cards require an updated Card Information Structure (CIS)
45 to be loaded from userspace to work correctly. If you say Y here,
46 and your userspace is arranged correctly, this will be loaded
47 automatically using the in-kernel firmware loader and the hotplug
48 subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
53 bool "32-bit CardBus support"
57 CardBus is a bus mastering architecture for PC-cards, which allows
58 for 32 bit PC-cards (the original PCMCIA standard specifies only
59 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
61 To use 32 bit PC-cards, you also need a CardBus compatible host
62 bridge. Virtually all modern PCMCIA bridges do this, and most of
63 them are "yenta-compatible", so say Y or M there, too.
67 comment "PC-card bridges"
70 tristate "CardBus yenta-compatible bridge support"
72 select CARDBUS if !EXPERT
73 select PCCARD_NONSTATIC if PCMCIA != n
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
80 To compile this driver as modules, choose M here: the
81 module will be called yenta_socket.
87 bool "Special initialization for O2Micro bridges" if EXPERT
92 bool "Special initialization for Ricoh bridges" if EXPERT
97 bool "Special initialization for TI and EnE bridges" if EXPERT
100 config YENTA_ENE_TUNE
102 bool "Auto-tune EnE bridges for CB cards" if EXPERT
103 depends on YENTA_TI && CARDBUS
107 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
111 tristate "Cirrus PD6729 compatible bridge support"
112 depends on PCMCIA && PCI
113 select PCCARD_NONSTATIC
115 This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
116 device, found in some older laptops and PCMCIA card readers.
119 tristate "i82092 compatible bridge support"
120 depends on PCMCIA && PCI
121 select PCCARD_NONSTATIC
123 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
124 found in some older laptops and more commonly in evaluation boards for the
128 tristate "i82365 compatible bridge support"
129 depends on PCMCIA && ISA
130 select PCCARD_NONSTATIC
132 Say Y here to include support for ISA-bus PCMCIA host bridges that
133 are register compatible with the Intel i82365. These are found on
134 older laptops and ISA-bus card readers for desktop systems. A
135 "bridge" is the hardware inside your computer that PCMCIA cards are
136 plugged into. If unsure, say N.
139 tristate "Databook TCIC host bridge support"
140 depends on PCMCIA && ISA
141 select PCCARD_NONSTATIC
143 Say Y here to include support for the Databook TCIC family of PCMCIA
144 host bridges. These are only found on a handful of old systems.
145 "Bridge" is the name used for the hardware inside your computer that
146 PCMCIA cards are plugged into. If unsure, say N.
149 tristate "MPC8xx PCMCIA support"
150 depends on PCCARD && PPC && 8xx
151 select PCCARD_IODYN if PCMCIA != n
153 Say Y here to include support for PowerPC 8xx series PCMCIA
156 This driver is also available as a module called m8xx_pcmcia.
158 config PCMCIA_ALCHEMY_DEVBOARD
159 tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
160 depends on MIPS_ALCHEMY && PCMCIA
161 select 64BIT_PHYS_ADDR
163 Enable this driver of you want PCMCIA support on your Alchemy
164 Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
165 board. NOT suitable for the PB1000!
167 This driver is also available as a module called db1xxx_ss.ko
169 config PCMCIA_XXS1500
170 tristate "MyCable XXS1500 PCMCIA socket support"
171 depends on PCMCIA && MIPS_XXS1500
172 select 64BIT_PHYS_ADDR
174 Support for the PCMCIA/CF socket interface on MyCable XXS1500
177 This driver is also available as a module called xxs1500_ss.ko
179 config PCMCIA_BCM63XX
180 tristate "bcm63xx pcmcia support"
181 depends on BCM63XX && PCMCIA
183 config PCMCIA_SOC_COMMON
187 tristate "SA1100 support"
188 depends on ARM && ARCH_SA1100 && PCMCIA
189 select PCMCIA_SOC_COMMON
191 Say Y here to include support for SA11x0-based PCMCIA or CF
192 sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
193 Xscale(R) embedded machines.
195 This driver is also available as a module called sa1100_cs.
198 tristate "SA1111 support"
199 depends on ARM && ARCH_SA1100 && SA1111 && PCMCIA
200 select PCMCIA_SOC_COMMON
202 Say Y here to include support for SA1111-based PCMCIA or CF
203 sockets, found on the Jornada 720, Graphicsmaster and other
204 StrongARM(R)/Xscale(R) embedded machines.
206 This driver is also available as a module called sa1111_cs.
209 tristate "PXA2xx support"
210 depends on ARM && ARCH_PXA && PCMCIA
211 depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \
212 || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \
213 || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \
214 || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \
216 select PCMCIA_SOC_COMMON
218 Say Y here to include support for the PXA2xx PCMCIA controller
221 bool "Enable debugging"
222 depends on (PCMCIA_SA1111 || PCMCIA_SA1100 || PCMCIA_PXA2XX)
224 Say Y here to enable debugging for the SoC PCMCIA layer.
225 You will need to choose the debugging level either via the
226 kernel command line, or module options depending whether
227 you build the drivers as modules.
229 The kernel command line options are:
230 sa11xx_core.pc_debug=N
231 pxa2xx_core.pc_debug=N
233 The module option is called pc_debug=N
235 In all the above examples, N is the debugging verbosity
240 default y if ISA && !ARCH_SA1100 && !ARCH_CLPS711X && !PARISC
243 bool "M32R PCMCIA I/F"
244 depends on M32R && CHIP_M32700 && PCMCIA
246 Say Y here to use the M32R PCMCIA controller.
249 bool "M32R CF I/F Controller"
250 depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT)
252 Say Y here to use the M32R CompactFlash controller.
255 int "M32R CF I/F number"
257 default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT
259 Set the number of M32R CF slots.
261 config PCMCIA_VRC4171
262 tristate "NEC VRC4171 Card Controllers support"
263 depends on CPU_VR41XX && ISA && PCMCIA
265 config PCMCIA_VRC4173
266 tristate "NEC VRC4173 CARDU support"
267 depends on CPU_VR41XX && PCI && PCMCIA
270 tristate "OMAP CompactFlash Controller"
271 depends on PCMCIA && ARCH_OMAP16XX
273 Say Y here to support the CompactFlash controller on OMAP.
274 Note that this doesn't support "True IDE" mode.
277 tristate "Blackfin CompactFlash PCMCIA Driver"
278 depends on PCMCIA && BLACKFIN
280 Say Y here to support the CompactFlash PCMCIA driver for Blackfin.
284 tristate "AT91 CompactFlash Controller"
285 depends on PCMCIA && ARCH_AT91RM9200
287 Say Y here to support the CompactFlash controller on AT91 chips.
288 Or choose M to compile the driver as a module named "at91_cf".
291 tristate "Electra CompactFlash Controller"
292 depends on PCMCIA && PPC_PASEMI
294 Say Y here to support the CompactFlash controller on the
295 PA Semi Electra eval board.
297 config PCCARD_NONSTATIC