Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Infrared-port device drivers" |
2 | depends on IRDA!=n | |
3 | ||
4 | comment "SIR device drivers" | |
5 | ||
6 | config IRTTY_SIR | |
7 | tristate "IrTTY (uses Linux serial driver)" | |
8 | depends on IRDA | |
9 | help | |
10 | Say Y here if you want to build support for the IrTTY line | |
11 | discipline. To compile it as a module, choose M here: the module | |
12 | will be called irtty-sir. IrTTY makes it possible to use Linux's | |
13 | own serial driver for all IrDA ports that are 16550 compatible. | |
14 | Most IrDA chips are 16550 compatible so you should probably say Y | |
15 | to this option. Using IrTTY will however limit the speed of the | |
16 | connection to 115200 bps (IrDA SIR mode). | |
17 | ||
18 | If unsure, say Y. | |
19 | ||
20 | comment "Dongle support" | |
21 | ||
22 | config DONGLE | |
23 | bool "Serial dongle support" | |
24 | depends on IRTTY_SIR | |
25 | help | |
26 | Say Y here if you have an infrared device that connects to your | |
27 | computer's serial port. These devices are called dongles. Then say Y | |
28 | or M to the driver for your particular dongle below. | |
29 | ||
30 | Note that the answer to this question won't directly affect the | |
31 | kernel: saying N will just cause the configurator to skip all | |
32 | the questions about serial dongles. | |
33 | ||
34 | config ESI_DONGLE | |
35 | tristate "ESI JetEye PC dongle" | |
56bc348c | 36 | depends on IRTTY_SIR && DONGLE && IRDA |
1da177e4 LT |
37 | help |
38 | Say Y here if you want to build support for the Extended Systems | |
39 | JetEye PC dongle. To compile it as a module, choose M here. The ESI | |
40 | dongle attaches to the normal 9-pin serial port connector, and can | |
41 | currently only be used by IrTTY. To activate support for ESI | |
42 | dongles you will have to start irattach like this: | |
43 | "irattach -d esi". | |
44 | ||
45 | config ACTISYS_DONGLE | |
46 | tristate "ACTiSYS IR-220L and IR220L+ dongle" | |
56bc348c | 47 | depends on IRTTY_SIR && DONGLE && IRDA |
1da177e4 LT |
48 | help |
49 | Say Y here if you want to build support for the ACTiSYS IR-220L and | |
50 | IR220L+ dongles. To compile it as a module, choose M here. The | |
51 | ACTiSYS dongles attaches to the normal 9-pin serial port connector, | |
52 | and can currently only be used by IrTTY. To activate support for | |
53 | ACTiSYS dongles you will have to start irattach like this: | |
54 | "irattach -d actisys" or "irattach -d actisys+". | |
55 | ||
56 | config TEKRAM_DONGLE | |
57 | tristate "Tekram IrMate 210B dongle" | |
56bc348c | 58 | depends on IRTTY_SIR && DONGLE && IRDA |
1da177e4 LT |
59 | help |
60 | Say Y here if you want to build support for the Tekram IrMate 210B | |
61 | dongle. To compile it as a module, choose M here. The Tekram dongle | |
62 | attaches to the normal 9-pin serial port connector, and can | |
63 | currently only be used by IrTTY. To activate support for Tekram | |
64 | dongles you will have to start irattach like this: | |
65 | "irattach -d tekram". | |
66 | ||
0ac81ae3 DB |
67 | config TOIM3232_DONGLE |
68 | tristate "TOIM3232 IrDa dongle" | |
56bc348c | 69 | depends on IRTTY_SIR && DONGLE && IRDA |
0ac81ae3 DB |
70 | help |
71 | Say Y here if you want to build support for the Vishay/Temic | |
72 | TOIM3232 and TOIM4232 based dongles. | |
73 | To compile it as a module, choose M here. | |
74 | ||
1da177e4 LT |
75 | config LITELINK_DONGLE |
76 | tristate "Parallax LiteLink dongle" | |
56bc348c | 77 | depends on IRTTY_SIR && DONGLE && IRDA |
1da177e4 LT |
78 | help |
79 | Say Y here if you want to build support for the Parallax Litelink | |
80 | dongle. To compile it as a module, choose M here. The Parallax | |
81 | dongle attaches to the normal 9-pin serial port connector, and can | |
82 | currently only be used by IrTTY. To activate support for Parallax | |
83 | dongles you will have to start irattach like this: | |
84 | "irattach -d litelink". | |
85 | ||
86 | config MA600_DONGLE | |
87 | tristate "Mobile Action MA600 dongle" | |
56bc348c | 88 | depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL |
1da177e4 LT |
89 | help |
90 | Say Y here if you want to build support for the Mobile Action MA600 | |
91 | dongle. To compile it as a module, choose M here. The MA600 dongle | |
92 | attaches to the normal 9-pin serial port connector, and can | |
93 | currently only be used by IrTTY. The driver should also support | |
94 | the MA620 USB version of the dongle, if the integrated USB-to-RS232 | |
95 | converter is supported by usbserial. To activate support for | |
96 | MA600 dongle you will have to start irattach like this: | |
97 | "irattach -d ma600". | |
98 | ||
99 | config GIRBIL_DONGLE | |
100 | tristate "Greenwich GIrBIL dongle" | |
56bc348c | 101 | depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL |
1da177e4 LT |
102 | help |
103 | Say Y here if you want to build support for the Greenwich GIrBIL | |
104 | dongle. If you want to compile it as a module, choose M here. | |
105 | The Greenwich dongle attaches to the normal 9-pin serial port | |
106 | connector, and can currently only be used by IrTTY. To activate | |
107 | support for Greenwich dongles you will have to start irattach | |
108 | like this: "irattach -d girbil". | |
109 | ||
110 | config MCP2120_DONGLE | |
111 | tristate "Microchip MCP2120" | |
56bc348c | 112 | depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL |
1da177e4 LT |
113 | help |
114 | Say Y here if you want to build support for the Microchip MCP2120 | |
115 | dongle. If you want to compile it as a module, choose M here. | |
116 | The MCP2120 dongle attaches to the normal 9-pin serial port | |
117 | connector, and can currently only be used by IrTTY. To activate | |
118 | support for MCP2120 dongles you will have to start irattach | |
119 | like this: "irattach -d mcp2120". | |
120 | ||
121 | You must build this dongle yourself. For more information see: | |
122 | <http://www.eyetap.org/~tangf/irda_sir_linux.html> | |
123 | ||
124 | config OLD_BELKIN_DONGLE | |
125 | tristate "Old Belkin dongle" | |
56bc348c | 126 | depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL |
1da177e4 LT |
127 | help |
128 | Say Y here if you want to build support for the Adaptec Airport 1000 | |
129 | and 2000 dongles. If you want to compile it as a module, choose | |
130 | M here. Some information is contained in the comments | |
131 | at the top of <file:drivers/net/irda/old_belkin.c>. | |
132 | ||
133 | config ACT200L_DONGLE | |
134 | tristate "ACTiSYS IR-200L dongle" | |
56bc348c | 135 | depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL |
1da177e4 LT |
136 | help |
137 | Say Y here if you want to build support for the ACTiSYS IR-200L | |
138 | dongle. If you want to compile it as a module, choose M here. | |
139 | The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial | |
140 | port connector, and can currently only be used by IrTTY. | |
141 | To activate support for ACTiSYS IR-200L dongle you will have to | |
142 | start irattach like this: "irattach -d act200l". | |
143 | ||
a2af421f AVL |
144 | config KINGSUN_DONGLE |
145 | tristate "KingSun/DonShine DS-620 IrDA-USB dongle" | |
146 | depends on IRDA && USB && EXPERIMENTAL | |
147 | help | |
148 | Say Y or M here if you want to build support for the KingSun/DonShine | |
149 | DS-620 IrDA-USB bridge device driver. | |
150 | ||
151 | This USB bridge does not conform to the IrDA-USB device class | |
152 | specification, and therefore needs its own specific driver. This | |
153 | dongle supports SIR speed only (9600 bps). | |
154 | ||
155 | To compile it as a module, choose M here: the module will be called | |
156 | kingsun-sir. | |
157 | ||
e97e2ddf SO |
158 | config EP7211_DONGLE |
159 | tristate "EP7211 I/R support" | |
160 | depends on IRTTY_SIR && ARCH_EP7211 && IRDA && EXPERIMENTAL | |
161 | help | |
162 | Say Y here if you want to build support for the Cirrus logic | |
163 | EP7211 chipset's infrared module. | |
164 | ||
4a1d7c25 AVL |
165 | config KSDAZZLE_DONGLE |
166 | tristate "KingSun Dazzle IrDA-USB dongle (EXPERIMENTAL)" | |
167 | depends on IRDA && USB && EXPERIMENTAL | |
168 | help | |
169 | Say Y or M here if you want to build support for the KingSun Dazzle | |
170 | IrDA-USB bridge device driver. | |
171 | ||
172 | This USB bridge does not conform to the IrDA-USB device class | |
173 | specification, and therefore needs its own specific driver. This | |
174 | dongle supports SIR speeds only (9600 through 115200 bps). | |
e97e2ddf | 175 | |
4a1d7c25 AVL |
176 | To compile it as a module, choose M here: the module will be called |
177 | ksdazzle-sir. | |
e97e2ddf | 178 | |
1da177e4 LT |
179 | comment "Old SIR device drivers" |
180 | ||
181 | config IRPORT_SIR | |
182 | tristate "IrPORT (IrDA serial driver)" | |
183 | depends on IRDA && BROKEN_ON_SMP | |
184 | ---help--- | |
185 | Say Y here if you want to build support for the IrPORT IrDA device | |
186 | driver. To compile it as a module, choose M here: the module will be | |
187 | called irport. IrPORT can be used instead of IrTTY and sometimes | |
188 | this can be better. One example is if your IrDA port does not | |
189 | have echo-canceling, which will work OK with IrPORT since this | |
190 | driver is working in half-duplex mode only. You don't need to use | |
191 | irattach with IrPORT, but you just insert it the same way as FIR | |
192 | drivers (insmod irport io=0x3e8 irq=11). Notice that IrPORT is a | |
193 | SIR device driver which means that speed is limited to 115200 bps. | |
194 | ||
195 | If unsure, say Y. | |
196 | ||
197 | comment "Old Serial dongle support" | |
198 | ||
199 | config DONGLE_OLD | |
200 | bool "Old Serial dongle support" | |
65e480ac | 201 | depends on IRPORT_SIR && BROKEN_ON_SMP |
1da177e4 LT |
202 | help |
203 | Say Y here if you have an infrared device that connects to your | |
204 | computer's serial port. These devices are called dongles. Then say Y | |
205 | or M to the driver for your particular dongle below. | |
206 | ||
207 | Note that the answer to this question won't directly affect the | |
208 | kernel: saying N will just cause the configurator to skip all | |
209 | the questions about serial dongles. | |
210 | ||
211 | config ESI_DONGLE_OLD | |
212 | tristate "ESI JetEye PC dongle" | |
213 | depends on DONGLE_OLD && IRDA | |
214 | help | |
215 | Say Y here if you want to build support for the Extended Systems | |
216 | JetEye PC dongle. To compile it as a module, choose M here. The ESI | |
217 | dongle attaches to the normal 9-pin serial port connector, and can | |
218 | currently only be used by IrTTY. To activate support for ESI | |
219 | dongles you will have to start irattach like this: | |
220 | "irattach -d esi". | |
221 | ||
222 | config ACTISYS_DONGLE_OLD | |
223 | tristate "ACTiSYS IR-220L and IR220L+ dongle" | |
224 | depends on DONGLE_OLD && IRDA | |
225 | help | |
226 | Say Y here if you want to build support for the ACTiSYS IR-220L and | |
227 | IR220L+ dongles. To compile it as a module, choose M here. The | |
228 | ACTiSYS dongles attaches to the normal 9-pin serial port connector, | |
229 | and can currently only be used by IrTTY. To activate support for | |
230 | ACTiSYS dongles you will have to start irattach like this: | |
231 | "irattach -d actisys" or "irattach -d actisys+". | |
232 | ||
233 | config TEKRAM_DONGLE_OLD | |
234 | tristate "Tekram IrMate 210B dongle" | |
235 | depends on DONGLE_OLD && IRDA | |
236 | help | |
237 | Say Y here if you want to build support for the Tekram IrMate 210B | |
238 | dongle. To compile it as a module, choose M here. The Tekram dongle | |
239 | attaches to the normal 9-pin serial port connector, and can | |
240 | currently only be used by IrTTY. To activate support for Tekram | |
241 | dongles you will have to start irattach like this: | |
242 | "irattach -d tekram". | |
243 | ||
244 | config GIRBIL_DONGLE_OLD | |
245 | tristate "Greenwich GIrBIL dongle" | |
246 | depends on DONGLE_OLD && IRDA | |
247 | help | |
248 | Say Y here if you want to build support for the Greenwich GIrBIL | |
249 | dongle. To compile it as a module, choose M here. The Greenwich | |
250 | dongle attaches to the normal 9-pin serial port connector, and can | |
251 | currently only be used by IrTTY. To activate support for Greenwich | |
252 | dongles you will have to insert "irattach -d girbil" in the | |
253 | /etc/irda/drivers script. | |
254 | ||
255 | config LITELINK_DONGLE_OLD | |
256 | tristate "Parallax LiteLink dongle" | |
257 | depends on DONGLE_OLD && IRDA | |
258 | help | |
259 | Say Y here if you want to build support for the Parallax Litelink | |
260 | dongle. To compile it as a module, choose M here. The Parallax | |
261 | dongle attaches to the normal 9-pin serial port connector, and can | |
262 | currently only be used by IrTTY. To activate support for Parallax | |
263 | dongles you will have to start irattach like this: | |
264 | "irattach -d litelink". | |
265 | ||
266 | config MCP2120_DONGLE_OLD | |
267 | tristate "Microchip MCP2120" | |
268 | depends on DONGLE_OLD && IRDA | |
269 | help | |
270 | Say Y here if you want to build support for the Microchip MCP2120 | |
271 | dongle. To compile it as a module, choose M here. The MCP2120 dongle | |
272 | attaches to the normal 9-pin serial port connector, and can | |
273 | currently only be used by IrTTY. To activate support for MCP2120 | |
274 | dongles you will have to insert "irattach -d mcp2120" in the | |
275 | /etc/irda/drivers script. | |
276 | ||
277 | You must build this dongle yourself. For more information see: | |
278 | <http://www.eyetap.org/~tangf/irda_sir_linux.html> | |
279 | ||
280 | config OLD_BELKIN_DONGLE_OLD | |
281 | tristate "Old Belkin dongle" | |
282 | depends on DONGLE_OLD && IRDA | |
283 | help | |
284 | Say Y here if you want to build support for the Adaptec Airport 1000 | |
285 | and 2000 dongles. To compile it as a module, choose M here: the module | |
286 | will be called old_belkin. Some information is contained in the | |
287 | comments at the top of <file:drivers/net/irda/old_belkin.c>. | |
288 | ||
289 | config ACT200L_DONGLE_OLD | |
290 | tristate "ACTiSYS IR-200L dongle (EXPERIMENTAL)" | |
291 | depends on DONGLE_OLD && EXPERIMENTAL && IRDA | |
292 | help | |
293 | Say Y here if you want to build support for the ACTiSYS IR-200L | |
294 | dongle. To compile it as a module, choose M here. The ACTiSYS | |
295 | IR-200L dongle attaches to the normal 9-pin serial port connector, | |
296 | and can currently only be used by IrTTY. To activate support for | |
297 | ACTiSYS IR-200L dongles you will have to start irattach like this: | |
298 | "irattach -d act200l". | |
299 | ||
300 | config MA600_DONGLE_OLD | |
301 | tristate "Mobile Action MA600 dongle (EXPERIMENTAL)" | |
302 | depends on DONGLE_OLD && EXPERIMENTAL && IRDA | |
303 | ---help--- | |
304 | Say Y here if you want to build support for the Mobile Action MA600 | |
305 | dongle. To compile it as a module, choose M here. The MA600 dongle | |
306 | attaches to the normal 9-pin serial port connector, and can | |
307 | currently only be tested on IrCOMM. To activate support for MA600 | |
308 | dongles you will have to insert "irattach -d ma600" in the | |
309 | /etc/irda/drivers script. Note: irutils 0.9.15 requires no | |
310 | modification. irutils 0.9.9 needs modification. For more | |
311 | information, download the following tar gzip file. | |
312 | ||
313 | There is a pre-compiled module on | |
314 | <http://engsvr.ust.hk/~eetwl95/ma600.html> | |
315 | ||
316 | config EP7211_IR | |
317 | tristate "EP7211 I/R support" | |
318 | depends on DONGLE_OLD && ARCH_EP7211 && IRDA | |
319 | ||
320 | comment "FIR device drivers" | |
321 | ||
322 | config USB_IRDA | |
323 | tristate "IrDA USB dongles" | |
324 | depends on IRDA && USB | |
778e6398 | 325 | select FW_LOADER |
1da177e4 LT |
326 | ---help--- |
327 | Say Y here if you want to build support for the USB IrDA FIR Dongle | |
328 | device driver. To compile it as a module, choose M here: the module | |
329 | will be called irda-usb. IrDA-USB support the various IrDA USB | |
47c51431 | 330 | dongles available and most of their peculiarities. Those dongles |
1da177e4 LT |
331 | plug in the USB port of your computer, are plug and play, and |
332 | support SIR and FIR (4Mbps) speeds. On the other hand, those | |
333 | dongles tend to be less efficient than a FIR chipset. | |
334 | ||
335 | Please note that the driver is still experimental. And of course, | |
336 | you will need both USB and IrDA support in your kernel... | |
337 | ||
338 | config SIGMATEL_FIR | |
339 | tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)" | |
340 | depends on IRDA && USB && EXPERIMENTAL | |
341 | select CRC32 | |
342 | ---help--- | |
343 | Say Y here if you want to build support for the SigmaTel STIr4200 | |
344 | USB IrDA FIR bridge device driver. | |
345 | ||
346 | USB bridge based on the SigmaTel STIr4200 don't conform to the | |
347 | IrDA-USB device class specification, and therefore need their | |
348 | own specific driver. Those dongles support SIR and FIR (4Mbps) | |
349 | speeds. | |
350 | ||
351 | To compile it as a module, choose M here: the module will be called | |
352 | stir4200. | |
353 | ||
354 | config NSC_FIR | |
355 | tristate "NSC PC87108/PC87338" | |
56c3b7d7 | 356 | depends on IRDA && ISA_DMA_API |
1da177e4 LT |
357 | help |
358 | Say Y here if you want to build support for the NSC PC87108 and | |
359 | PC87338 IrDA chipsets. This driver supports SIR, | |
360 | MIR and FIR (4Mbps) speeds. | |
361 | ||
362 | To compile it as a module, choose M here: the module will be called | |
363 | nsc-ircc. | |
364 | ||
365 | config WINBOND_FIR | |
366 | tristate "Winbond W83977AF (IR)" | |
56c3b7d7 | 367 | depends on IRDA && ISA_DMA_API |
1da177e4 LT |
368 | help |
369 | Say Y here if you want to build IrDA support for the Winbond | |
370 | W83977AF super-io chipset. This driver should be used for the IrDA | |
371 | chipset in the Corel NetWinder. The driver supports SIR, MIR and | |
372 | FIR (4Mbps) speeds. | |
373 | ||
374 | To compile it as a module, choose M here: the module will be called | |
375 | w83977af_ir. | |
376 | ||
377 | config TOSHIBA_FIR | |
378 | tristate "Toshiba Type-O IR Port" | |
43a41513 | 379 | depends on IRDA && PCI && !64BIT && VIRT_TO_BUS |
1da177e4 LT |
380 | help |
381 | Say Y here if you want to build support for the Toshiba Type-O IR | |
382 | and Donau oboe chipsets. These chipsets are used by the Toshiba | |
383 | Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops. | |
384 | To compile it as a module, choose M here: the module will be called | |
385 | donauboe. | |
386 | ||
387 | config AU1000_FIR | |
388 | tristate "Alchemy Au1000 SIR/FIR" | |
caf430f3 | 389 | depends on SOC_AU1000 && IRDA |
1da177e4 LT |
390 | |
391 | config SMC_IRCC_FIR | |
392 | tristate "SMSC IrCC (EXPERIMENTAL)" | |
56c3b7d7 | 393 | depends on EXPERIMENTAL && IRDA && ISA_DMA_API |
1da177e4 LT |
394 | help |
395 | Say Y here if you want to build support for the SMC Infrared | |
396 | Communications Controller. It is used in a wide variety of | |
397 | laptops (Fujitsu, Sony, Compaq and some Toshiba). | |
398 | To compile it as a module, choose M here: the module will be called | |
399 | smsc-ircc2.o. | |
400 | ||
401 | config ALI_FIR | |
402 | tristate "ALi M5123 FIR (EXPERIMENTAL)" | |
56c3b7d7 | 403 | depends on EXPERIMENTAL && IRDA && ISA_DMA_API |
1da177e4 LT |
404 | help |
405 | Say Y here if you want to build support for the ALi M5123 FIR | |
406 | Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C, | |
47c51431 | 407 | M1535, M1535D, M1535+, M1535D South Bridge. This driver supports |
1da177e4 LT |
408 | SIR, MIR and FIR (4Mbps) speeds. |
409 | ||
410 | To compile it as a module, choose M here: the module will be called | |
411 | ali-ircc. | |
412 | ||
413 | config VLSI_FIR | |
414 | tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)" | |
415 | depends on EXPERIMENTAL && IRDA && PCI | |
416 | help | |
417 | Say Y here if you want to build support for the VLSI 82C147 | |
418 | PCI-IrDA Controller. This controller is used by the HP OmniBook 800 | |
419 | and 5500 notebooks. The driver provides support for SIR, MIR and | |
420 | FIR (4Mbps) speeds. | |
421 | ||
422 | To compile it as a module, choose M here: the module will be called | |
423 | vlsi_ir. | |
424 | ||
425 | config SA1100_FIR | |
426 | tristate "SA1100 Internal IR" | |
427 | depends on ARCH_SA1100 && IRDA | |
428 | ||
429 | config VIA_FIR | |
430 | tristate "VIA VT8231/VT1211 SIR/MIR/FIR" | |
56c3b7d7 | 431 | depends on IRDA && ISA_DMA_API |
1da177e4 LT |
432 | help |
433 | Say Y here if you want to build support for the VIA VT8231 | |
434 | and VIA VT1211 IrDA controllers, found on the motherboards using | |
392a8b7e | 435 | those VIA chipsets. To use this controller, you will need |
1da177e4 LT |
436 | to plug a specific 5 pins FIR IrDA dongle in the specific |
437 | motherboard connector. The driver provides support for SIR, MIR | |
438 | and FIR (4Mbps) speeds. | |
439 | ||
440 | You will need to specify the 'dongle_id' module parameter to | |
441 | indicate the FIR dongle attached to the controller. | |
442 | ||
443 | To compile it as a module, choose M here: the module will be called | |
444 | via-ircc. | |
445 | ||
6f475c01 NP |
446 | config PXA_FICP |
447 | tristate "Intel PXA2xx Internal FICP" | |
448 | depends on ARCH_PXA && IRDA | |
449 | help | |
450 | Say Y or M here if you want to build support for the PXA2xx | |
451 | built-in IRDA interface which can support both SIR and FIR. | |
452 | This driver relies on platform specific helper routines so | |
453 | available capabilities may vary from one PXA2xx target to | |
454 | another. | |
455 | ||
c6ae522e SO |
456 | config MCS_FIR |
457 | tristate "MosChip MCS7780 IrDA-USB dongle" | |
458 | depends on IRDA && USB && EXPERIMENTAL | |
459 | help | |
460 | Say Y or M here if you want to build support for the MosChip | |
461 | MCS7780 IrDA-USB bridge device driver. | |
462 | ||
463 | USB bridge based on the MosChip MCS7780 don't conform to the | |
464 | IrDA-USB device class specification, and therefore need their | |
465 | own specific driver. Those dongles support SIR and FIR (4Mbps) | |
466 | speeds. | |
467 | ||
468 | To compile it as a module, choose M here: the module will be called | |
469 | mcs7780. | |
470 | ||
1da177e4 LT |
471 | endmenu |
472 |