Commit | Line | Data |
---|---|---|
33f810b2 JK |
1 | # |
2 | # FDDI network device configuration | |
3 | # | |
4 | ||
5 | config FDDI | |
6 | tristate "FDDI driver support" | |
7 | depends on PCI || EISA || TC | |
8 | ---help--- | |
9 | Fiber Distributed Data Interface is a high speed local area network | |
10 | design; essentially a replacement for high speed Ethernet. FDDI can | |
11 | run over copper or fiber. If you are connected to such a network and | |
12 | want a driver for the FDDI card in your computer, say Y here (and | |
13 | then also Y to the driver for your FDDI card, below). Most people | |
14 | will say N. | |
15 | ||
16 | if FDDI | |
17 | ||
18 | config DEFXX | |
19 | tristate "Digital DEFTA/DEFEA/DEFPA adapter support" | |
20 | depends on FDDI && (PCI || EISA || TC) | |
21 | ---help--- | |
22 | This is support for the DIGITAL series of TURBOchannel (DEFTA), | |
23 | EISA (DEFEA) and PCI (DEFPA) controllers which can connect you | |
24 | to a local FDDI network. | |
25 | ||
26 | To compile this driver as a module, choose M here: the module | |
27 | will be called defxx. If unsure, say N. | |
28 | ||
29 | config DEFXX_MMIO | |
30 | bool | |
31 | prompt "Use MMIO instead of PIO" if PCI || EISA | |
32 | depends on DEFXX | |
33 | default n if PCI || EISA | |
34 | default y | |
35 | ---help--- | |
36 | This instructs the driver to use EISA or PCI memory-mapped I/O | |
37 | (MMIO) as appropriate instead of programmed I/O ports (PIO). | |
38 | Enabling this gives an improvement in processing time in parts | |
39 | of the driver, but it may cause problems with EISA (DEFEA) | |
40 | adapters. TURBOchannel does not have the concept of I/O ports, | |
41 | so MMIO is always used for these (DEFTA) adapters. | |
42 | ||
43 | If unsure, say N. | |
44 | ||
45 | config SKFP | |
46 | tristate "SysKonnect FDDI PCI support" | |
47 | depends on FDDI && PCI | |
48 | select BITREVERSE | |
49 | ---help--- | |
50 | Say Y here if you have a SysKonnect FDDI PCI adapter. | |
51 | The following adapters are supported by this driver: | |
52 | - SK-5521 (SK-NET FDDI-UP) | |
53 | - SK-5522 (SK-NET FDDI-UP DAS) | |
54 | - SK-5541 (SK-NET FDDI-FP) | |
55 | - SK-5543 (SK-NET FDDI-LP) | |
56 | - SK-5544 (SK-NET FDDI-LP DAS) | |
57 | - SK-5821 (SK-NET FDDI-UP64) | |
58 | - SK-5822 (SK-NET FDDI-UP64 DAS) | |
59 | - SK-5841 (SK-NET FDDI-FP64) | |
60 | - SK-5843 (SK-NET FDDI-LP64) | |
61 | - SK-5844 (SK-NET FDDI-LP64 DAS) | |
62 | - Netelligent 100 FDDI DAS Fibre SC | |
63 | - Netelligent 100 FDDI SAS Fibre SC | |
64 | - Netelligent 100 FDDI DAS UTP | |
65 | - Netelligent 100 FDDI SAS UTP | |
66 | - Netelligent 100 FDDI SAS Fibre MIC | |
67 | ||
68 | Read <file:Documentation/networking/skfp.txt> for information about | |
69 | the driver. | |
70 | ||
71 | Questions concerning this driver can be addressed to: | |
72 | <linux@syskonnect.de> | |
73 | ||
74 | To compile this driver as a module, choose M here: the module | |
75 | will be called skfp. This is recommended. | |
76 | ||
77 | endif # FDDI |