2 # PCMCIA bus subsystem configuration
4 # Right now the non-CardBus choices are not supported
5 # by the integrated kernel driver.
8 menu "PCCARD (PCMCIA/CardBus) support"
11 tristate "PCCard (PCMCIA/CardBus) support"
14 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
15 computer. These are credit-card size devices such as network cards,
16 modems or hard drives often used with laptops computers. There are
17 actually two varieties of these cards: the older 16 bit PCMCIA cards
18 and the newer 32 bit CardBus cards.
20 To compile this driver as modules, choose M here: the
21 module will be called pcmcia_core.
26 bool "Enable PCCARD debugging"
28 Say Y here to enable PCMCIA subsystem debugging. You
29 will need to choose the debugging level either via the
30 kernel command line, or module options depending whether
31 you build the PCMCIA as modules.
33 The kernel command line options are:
34 pcmcia_core.pc_debug=N
36 sa11xx_core.pc_debug=N
38 The module option is called pc_debug=N
40 In all the above examples, N is the debugging verbosity
44 tristate "16-bit PCMCIA support"
47 This option enables support for 16-bit PCMCIA cards. Most older
48 PC-cards are such 16-bit PCMCIA cards, so unless you know you're
49 only using 32-bit CardBus cards, say Y or M here.
51 To use 16-bit PCMCIA cards, you will need supporting software from
52 David Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
53 for location). Please also read the PCMCIA-HOWTO, available from
54 <http://www.tldp.org/docs.html#howto>.
56 To compile this driver as modules, choose M here: the
57 module will be called pcmcia.
61 config PCMCIA_LOAD_CIS
62 bool "Load CIS updates from userspace (EXPERIMENTAL)"
63 depends on PCMCIA && EXPERIMENTAL
67 Some PCMCIA cards require an updated Card Information Structure (CIS)
68 to be loaded from userspace to work correctly. If you say Y here,
69 and your userspace is arranged correctly, this will be loaded
70 automatically using the in-kernel firmware loader and the hotplug
71 subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
76 bool "32-bit CardBus support"
80 CardBus is a bus mastering architecture for PC-cards, which allows
81 for 32 bit PC-cards (the original PCMCIA standard specifies only
82 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
84 To use 32 bit PC-cards, you also need a CardBus compatible host
85 bridge. Virtually all modern PCMCIA bridges do this, and most of
86 them are "yenta-compatible", so say Y or M there, too.
90 comment "PC-card bridges"
93 tristate "CardBus yenta-compatible bridge support"
95 #fixme: remove dependendcy on CARDBUS
97 select PCCARD_NONSTATIC
99 This option enables support for CardBus host bridges. Virtually
100 all modern PCMCIA bridges are CardBus compatible. A "bridge" is
101 the hardware inside your computer that PCMCIA cards are plugged
104 To compile this driver as modules, choose M here: the
105 module will be called yenta_socket.
110 tristate "Cirrus PD6729 compatible bridge support"
111 depends on PCMCIA && PCI
112 select PCCARD_NONSTATIC
114 This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
115 device, found in some older laptops and PCMCIA card readers.
118 tristate "i82092 compatible bridge support"
119 depends on PCMCIA && PCI
120 select PCCARD_NONSTATIC
122 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
123 found in some older laptops and more commonly in evaluation boards for the
127 tristate "i82365 compatible bridge support"
128 depends on PCMCIA && ISA
129 select PCCARD_NONSTATIC
131 Say Y here to include support for ISA-bus PCMCIA host bridges that
132 are register compatible with the Intel i82365. These are found on
133 older laptops and ISA-bus card readers for desktop systems. A
134 "bridge" is the hardware inside your computer that PCMCIA cards are
135 plugged into. If unsure, say N.
138 tristate "Databook TCIC host bridge support"
140 select PCCARD_NONSTATIC
142 Say Y here to include support for the Databook TCIC family of PCMCIA
143 host bridges. These are only found on a handful of old systems.
144 "Bridge" is the name used for the hardware inside your computer that
145 PCMCIA cards are plugged into. If unsure, say N.
147 config HD64465_PCMCIA
148 tristate "HD64465 host bridge support"
149 depends on HD64465 && PCMCIA
152 tristate "Au1x00 pcmcia support"
153 depends on SOC_AU1X00 && PCMCIA
156 tristate "SA1100 support"
157 depends on ARM && ARCH_SA1100 && PCMCIA
159 Say Y here to include support for SA11x0-based PCMCIA or CF
160 sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
161 Xscale(R) embedded machines.
163 This driver is also available as a module called sa1100_cs.
166 tristate "SA1111 support"
167 depends on ARM && ARCH_SA1100 && SA1111 && PCMCIA
169 Say Y here to include support for SA1111-based PCMCIA or CF
170 sockets, found on the Jornada 720, Graphicsmaster and other
171 StrongARM(R)/Xscale(R) embedded machines.
173 This driver is also available as a module called sa1111_cs.
176 tristate "PXA2xx support"
177 depends on ARM && ARCH_PXA && PCMCIA
179 Say Y here to include support for the PXA2xx PCMCIA controller
183 default y if ISA && !ARCH_SA1100 && !ARCH_CLPS711X
186 bool "M32R PCMCIA I/F"
187 depends on M32R && CHIP_M32700 && PCMCIA
188 select PCCARD_NONSTATIC
190 Say Y here to use the M32R PCMCIA controller.
193 bool "M32R CF I/F Controller"
194 depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT)
195 select PCCARD_NONSTATIC
197 Say Y here to use the M32R CompactFlash controller.
200 int "M32R CF I/F number"
202 default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT
204 Set the number of M32R CF slots.
206 config PCMCIA_VRC4171
207 tristate "NEC VRC4171 Card Controllers support"
208 depends on VRC4171 && PCMCIA
210 config PCMCIA_VRC4173
211 tristate "NEC VRC4173 CARDU support"
212 depends on CPU_VR41XX && PCI && PCMCIA
214 config PCCARD_NONSTATIC