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"
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.
70 comment "PC-card bridges"
73 tristate "CardBus yenta-compatible bridge support"
75 select CARDBUS if !EXPERT
76 select PCCARD_NONSTATIC if PCMCIA != n
78 This option enables support for CardBus host bridges. Virtually
79 all modern PCMCIA bridges are CardBus compatible. A "bridge" is
80 the hardware inside your computer that PCMCIA cards are plugged
83 To compile this driver as modules, choose M here: the
84 module will be called yenta_socket.
90 bool "Special initialization for O2Micro bridges" if EXPERT
95 bool "Special initialization for Ricoh bridges" if EXPERT
100 bool "Special initialization for TI and EnE bridges" if EXPERT
103 config YENTA_ENE_TUNE
105 bool "Auto-tune EnE bridges for CB cards" if EXPERT
106 depends on YENTA_TI && CARDBUS
110 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
114 tristate "Cirrus PD6729 compatible bridge support"
115 depends on PCMCIA && PCI
116 select PCCARD_NONSTATIC
118 This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
119 device, found in some older laptops and PCMCIA card readers.
122 tristate "i82092 compatible bridge support"
123 depends on PCMCIA && PCI
124 select PCCARD_NONSTATIC
126 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
127 found in some older laptops and more commonly in evaluation boards for the
131 tristate "i82365 compatible bridge support"
132 depends on PCMCIA && ISA
133 select PCCARD_NONSTATIC
135 Say Y here to include support for ISA-bus PCMCIA host bridges that
136 are register compatible with the Intel i82365. These are found on
137 older laptops and ISA-bus card readers for desktop systems. A
138 "bridge" is the hardware inside your computer that PCMCIA cards are
139 plugged into. If unsure, say N.
142 tristate "Databook TCIC host bridge support"
143 depends on PCMCIA && ISA
144 select PCCARD_NONSTATIC
146 Say Y here to include support for the Databook TCIC family of PCMCIA
147 host bridges. These are only found on a handful of old systems.
148 "Bridge" is the name used for the hardware inside your computer that
149 PCMCIA cards are plugged into. If unsure, say N.
151 config PCMCIA_ALCHEMY_DEVBOARD
152 tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
153 depends on MIPS_ALCHEMY && PCMCIA
155 Enable this driver of you want PCMCIA support on your Alchemy
156 Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
157 board. NOT suitable for the PB1000!
159 This driver is also available as a module called db1xxx_ss.ko
161 config PCMCIA_XXS1500
162 tristate "MyCable XXS1500 PCMCIA socket support"
163 depends on PCMCIA && MIPS_XXS1500
165 Support for the PCMCIA/CF socket interface on MyCable XXS1500
168 This driver is also available as a module called xxs1500_ss.ko
170 config PCMCIA_BCM63XX
171 tristate "bcm63xx pcmcia support"
172 depends on BCM63XX && PCMCIA
174 config PCMCIA_SOC_COMMON
177 config PCMCIA_SA11XX_BASE
181 tristate "SA1100 support"
182 depends on ARM && ARCH_SA1100 && PCMCIA
183 select PCMCIA_SOC_COMMON
184 select PCMCIA_SA11XX_BASE
186 Say Y here to include support for SA11x0-based PCMCIA or CF
187 sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
188 Xscale(R) embedded machines.
190 This driver is also available as a module called sa1100_cs.
193 tristate "SA1111 support"
194 depends on ARM && SA1111 && PCMCIA
195 select PCMCIA_SOC_COMMON
196 select PCMCIA_SA11XX_BASE if ARCH_SA1100
197 select PCMCIA_PXA2XX if ARCH_LUBBOCK && SA1111
198 select PCMCIA_MAX1600 if ASSABET_NEPONSET
199 select PCMCIA_MAX1600 if ARCH_LUBBOCK && SA1111
201 Say Y here to include support for SA1111-based PCMCIA or CF
202 sockets, found on the Jornada 720, Graphicsmaster and other
203 StrongARM(R)/Xscale(R) embedded machines.
205 This driver is also available as a module called sa1111_cs.
208 tristate "PXA2xx support"
209 depends on ARM && ARCH_PXA && PCMCIA
210 depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \
211 || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \
212 || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \
213 || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \
214 || MACH_COLIBRI320 || MACH_H4700)
215 select PCMCIA_SOC_COMMON
216 select PCMCIA_MAX1600 if MACH_MAINSTONE
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 && !PARISC
242 config PCMCIA_VRC4171
243 tristate "NEC VRC4171 Card Controllers support"
244 depends on CPU_VR41XX && ISA && PCMCIA
246 config PCMCIA_VRC4173
247 tristate "NEC VRC4173 CARDU support"
248 depends on CPU_VR41XX && PCI && PCMCIA
251 tristate "OMAP CompactFlash Controller"
252 depends on PCMCIA && ARCH_OMAP16XX
254 Say Y here to support the CompactFlash controller on OMAP.
255 Note that this doesn't support "True IDE" mode.
258 tristate "AT91 CompactFlash Controller"
260 depends on PCMCIA && ARCH_AT91
262 Say Y here to support the CompactFlash controller on AT91 chips.
263 Or choose M to compile the driver as a module named "at91_cf".
266 tristate "Electra CompactFlash Controller"
267 depends on PCMCIA && PPC_PASEMI
269 Say Y here to support the CompactFlash controller on the
270 PA Semi Electra eval board.
272 config PCCARD_NONSTATIC