diff options
Diffstat (limited to 'drivers/pcmcia/Kconfig')
-rw-r--r-- | drivers/pcmcia/Kconfig | 203 |
1 files changed, 203 insertions, 0 deletions
diff --git a/drivers/pcmcia/Kconfig b/drivers/pcmcia/Kconfig new file mode 100644 index 000000000000..6375ebc85020 --- /dev/null +++ b/drivers/pcmcia/Kconfig | |||
@@ -0,0 +1,203 @@ | |||
1 | # | ||
2 | # PCMCIA bus subsystem configuration | ||
3 | # | ||
4 | # Right now the non-CardBus choices are not supported | ||
5 | # by the integrated kernel driver. | ||
6 | # | ||
7 | |||
8 | menu "PCCARD (PCMCIA/CardBus) support" | ||
9 | |||
10 | config PCCARD | ||
11 | tristate "PCCard (PCMCIA/CardBus) support" | ||
12 | select HOTPLUG | ||
13 | ---help--- | ||
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. | ||
19 | |||
20 | To compile this driver as modules, choose M here: the | ||
21 | module will be called pcmcia_core. | ||
22 | |||
23 | if PCCARD | ||
24 | |||
25 | config PCMCIA_DEBUG | ||
26 | bool "Enable PCCARD debugging" | ||
27 | help | ||
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. | ||
32 | |||
33 | The kernel command line options are: | ||
34 | pcmcia_core.pc_debug=N | ||
35 | ds.pc_debug=N | ||
36 | sa11xx_core.pc_debug=N | ||
37 | |||
38 | The module option is called pc_debug=N | ||
39 | |||
40 | In all the above examples, N is the debugging verbosity | ||
41 | level. | ||
42 | |||
43 | config PCMCIA | ||
44 | tristate "16-bit PCMCIA support" | ||
45 | default y | ||
46 | ---help--- | ||
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. | ||
50 | |||
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>. | ||
55 | |||
56 | To compile this driver as modules, choose M here: the | ||
57 | module will be called pcmcia. | ||
58 | |||
59 | If unsure, say Y. | ||
60 | |||
61 | config CARDBUS | ||
62 | bool "32-bit CardBus support" | ||
63 | depends on PCI | ||
64 | default y | ||
65 | ---help--- | ||
66 | CardBus is a bus mastering architecture for PC-cards, which allows | ||
67 | for 32 bit PC-cards (the original PCMCIA standard specifies only | ||
68 | a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. | ||
69 | |||
70 | To use 32 bit PC-cards, you also need a CardBus compatible host | ||
71 | bridge. Virtually all modern PCMCIA bridges do this, and most of | ||
72 | them are "yenta-compatible", so say Y or M there, too. | ||
73 | |||
74 | If unsure, say Y. | ||
75 | |||
76 | comment "PC-card bridges" | ||
77 | |||
78 | config YENTA | ||
79 | tristate "CardBus yenta-compatible bridge support" | ||
80 | depends on PCI | ||
81 | #fixme: remove dependendcy on CARDBUS | ||
82 | depends on CARDBUS | ||
83 | select PCCARD_NONSTATIC | ||
84 | ---help--- | ||
85 | This option enables support for CardBus host bridges. Virtually | ||
86 | all modern PCMCIA bridges are CardBus compatible. A "bridge" is | ||
87 | the hardware inside your computer that PCMCIA cards are plugged | ||
88 | into. | ||
89 | |||
90 | To compile this driver as modules, choose M here: the | ||
91 | module will be called yenta_socket. | ||
92 | |||
93 | If unsure, say Y. | ||
94 | |||
95 | config PD6729 | ||
96 | tristate "Cirrus PD6729 compatible bridge support" | ||
97 | depends on PCMCIA && PCI | ||
98 | select PCCARD_NONSTATIC | ||
99 | help | ||
100 | This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge | ||
101 | device, found in some older laptops and PCMCIA card readers. | ||
102 | |||
103 | config I82092 | ||
104 | tristate "i82092 compatible bridge support" | ||
105 | depends on PCMCIA && PCI | ||
106 | select PCCARD_NONSTATIC | ||
107 | help | ||
108 | This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device, | ||
109 | found in some older laptops and more commonly in evaluation boards for the | ||
110 | chip. | ||
111 | |||
112 | config I82365 | ||
113 | tristate "i82365 compatible bridge support" | ||
114 | depends on PCMCIA && ISA | ||
115 | select PCCARD_NONSTATIC | ||
116 | help | ||
117 | Say Y here to include support for ISA-bus PCMCIA host bridges that | ||
118 | are register compatible with the Intel i82365. These are found on | ||
119 | older laptops and ISA-bus card readers for desktop systems. A | ||
120 | "bridge" is the hardware inside your computer that PCMCIA cards are | ||
121 | plugged into. If unsure, say N. | ||
122 | |||
123 | config TCIC | ||
124 | tristate "Databook TCIC host bridge support" | ||
125 | depends on PCMCIA | ||
126 | select PCCARD_NONSTATIC | ||
127 | help | ||
128 | Say Y here to include support for the Databook TCIC family of PCMCIA | ||
129 | host bridges. These are only found on a handful of old systems. | ||
130 | "Bridge" is the name used for the hardware inside your computer that | ||
131 | PCMCIA cards are plugged into. If unsure, say N. | ||
132 | |||
133 | config HD64465_PCMCIA | ||
134 | tristate "HD64465 host bridge support" | ||
135 | depends on HD64465 && PCMCIA | ||
136 | |||
137 | config PCMCIA_AU1X00 | ||
138 | tristate "Au1x00 pcmcia support" | ||
139 | depends on SOC_AU1X00 && PCMCIA | ||
140 | |||
141 | config PCMCIA_SA1100 | ||
142 | tristate "SA1100 support" | ||
143 | depends on ARM && ARCH_SA1100 && PCMCIA | ||
144 | help | ||
145 | Say Y here to include support for SA11x0-based PCMCIA or CF | ||
146 | sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/ | ||
147 | Xscale(R) embedded machines. | ||
148 | |||
149 | This driver is also available as a module called sa1100_cs. | ||
150 | |||
151 | config PCMCIA_SA1111 | ||
152 | tristate "SA1111 support" | ||
153 | depends on ARM && ARCH_SA1100 && SA1111 && PCMCIA | ||
154 | help | ||
155 | Say Y here to include support for SA1111-based PCMCIA or CF | ||
156 | sockets, found on the Jornada 720, Graphicsmaster and other | ||
157 | StrongARM(R)/Xscale(R) embedded machines. | ||
158 | |||
159 | This driver is also available as a module called sa1111_cs. | ||
160 | |||
161 | config PCMCIA_PXA2XX | ||
162 | tristate "PXA2xx support" | ||
163 | depends on ARM && ARCH_PXA && PCMCIA | ||
164 | help | ||
165 | Say Y here to include support for the PXA2xx PCMCIA controller | ||
166 | |||
167 | config PCMCIA_PROBE | ||
168 | bool | ||
169 | default y if ISA && !ARCH_SA1100 && !ARCH_CLPS711X | ||
170 | |||
171 | config M32R_PCC | ||
172 | bool "M32R PCMCIA I/F" | ||
173 | depends on M32R && CHIP_M32700 && PCMCIA | ||
174 | help | ||
175 | Say Y here to use the M32R PCMCIA controller. | ||
176 | |||
177 | config M32R_CFC | ||
178 | bool "M32R CF I/F Controller" | ||
179 | depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_OPSPUT) | ||
180 | help | ||
181 | Say Y here to use the M32R CompactFlash controller. | ||
182 | |||
183 | config M32R_CFC_NUM | ||
184 | int "M32R CF I/F number" | ||
185 | depends on M32R_CFC | ||
186 | default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_OPSPUT | ||
187 | help | ||
188 | Set the number of M32R CF slots. | ||
189 | |||
190 | config PCMCIA_VRC4171 | ||
191 | tristate "NEC VRC4171 Card Controllers support" | ||
192 | depends on VRC4171 && PCMCIA | ||
193 | |||
194 | config PCMCIA_VRC4173 | ||
195 | tristate "NEC VRC4173 CARDU support" | ||
196 | depends on CPU_VR41XX && PCI && PCMCIA | ||
197 | |||
198 | config PCCARD_NONSTATIC | ||
199 | tristate | ||
200 | |||
201 | endif # PCCARD | ||
202 | |||
203 | endmenu | ||