mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-18 13:16:55 +07:00
61414f5ec9
Add support for the DEC FDDIcontroller 700 (DEFZA), Digital Equipment Corporation's first-generation FDDI network interface adapter, made for TURBOchannel and based on a discrete version of what eventually became Motorola's widely used CAMEL chipset. The CAMEL chipset is present for example in the DEC FDDIcontroller TURBOchannel, EISA and PCI adapters (DEFTA/DEFEA/DEFPA) that we support with the `defxx' driver, however the host bus interface logic and the firmware API are different in the DEFZA and hence a separate driver is required. There isn't much to say about the driver except that it works, but there is one peculiarity to mention. The adapter implements two Tx/Rx queue pairs. Of these one pair is the usual network Tx/Rx queue pair, in this case used by the adapter to exchange frames with the ring, via the RMC (Ring Memory Controller) chip. The Tx queue is handled directly by the RMC chip and resides in onboard packet memory. The Rx queue is maintained via DMA in host memory by adapter's firmware copying received data stored by the RMC in onboard packet memory. The other pair is used to communicate SMT frames with adapter's firmware. Any SMT frame received from the RMC via the Rx queue must be queued back by the driver to the SMT Rx queue for the firmware to process. Similarly the firmware uses the SMT Tx queue to supply the driver with SMT frames that must be queued back to the Tx queue for the RMC to send to the ring. This solution was chosen because the designers ran out of PCB space and could not squeeze in more logic onto the board that would be required to handle this SMT frame traffic without the need to involve the driver, as with the later DEFTA/DEFEA/DEFPA adapters. Finally the driver does some Frame Control byte decoding, so to avoid magic numbers some macros are added to <linux/if_fddi.h>. Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org> Signed-off-by: David S. Miller <davem@davemloft.net>
89 lines
2.8 KiB
Plaintext
89 lines
2.8 KiB
Plaintext
#
|
|
# FDDI network device configuration
|
|
#
|
|
|
|
config FDDI
|
|
tristate "FDDI driver support"
|
|
depends on PCI || EISA || TC
|
|
---help---
|
|
Fiber Distributed Data Interface is a high speed local area network
|
|
design; essentially a replacement for high speed Ethernet. FDDI can
|
|
run over copper or fiber. If you are connected to such a network and
|
|
want a driver for the FDDI card in your computer, say Y here (and
|
|
then also Y to the driver for your FDDI card, below). Most people
|
|
will say N.
|
|
|
|
if FDDI
|
|
|
|
config DEFZA
|
|
tristate "DEC FDDIcontroller 700/700-C (DEFZA-xx) support"
|
|
depends on FDDI && TC
|
|
help
|
|
This is support for the DEC FDDIcontroller 700 (DEFZA-AA, fiber)
|
|
and 700-C (DEFZA-CA, copper) TURBOchannel network cards which
|
|
can connect you to a local FDDI network.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called defza. If unsure, say N.
|
|
|
|
config DEFXX
|
|
tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
|
|
depends on FDDI && (PCI || EISA || TC)
|
|
---help---
|
|
This is support for the DIGITAL series of TURBOchannel (DEFTA),
|
|
EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
|
|
to a local FDDI network.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called defxx. If unsure, say N.
|
|
|
|
config DEFXX_MMIO
|
|
bool
|
|
prompt "Use MMIO instead of PIO" if PCI || EISA
|
|
depends on DEFXX
|
|
default n if PCI || EISA
|
|
default y
|
|
---help---
|
|
This instructs the driver to use EISA or PCI memory-mapped I/O
|
|
(MMIO) as appropriate instead of programmed I/O ports (PIO).
|
|
Enabling this gives an improvement in processing time in parts
|
|
of the driver, but it may cause problems with EISA (DEFEA)
|
|
adapters. TURBOchannel does not have the concept of I/O ports,
|
|
so MMIO is always used for these (DEFTA) adapters.
|
|
|
|
If unsure, say N.
|
|
|
|
config SKFP
|
|
tristate "SysKonnect FDDI PCI support"
|
|
depends on FDDI && PCI
|
|
select BITREVERSE
|
|
---help---
|
|
Say Y here if you have a SysKonnect FDDI PCI adapter.
|
|
The following adapters are supported by this driver:
|
|
- SK-5521 (SK-NET FDDI-UP)
|
|
- SK-5522 (SK-NET FDDI-UP DAS)
|
|
- SK-5541 (SK-NET FDDI-FP)
|
|
- SK-5543 (SK-NET FDDI-LP)
|
|
- SK-5544 (SK-NET FDDI-LP DAS)
|
|
- SK-5821 (SK-NET FDDI-UP64)
|
|
- SK-5822 (SK-NET FDDI-UP64 DAS)
|
|
- SK-5841 (SK-NET FDDI-FP64)
|
|
- SK-5843 (SK-NET FDDI-LP64)
|
|
- SK-5844 (SK-NET FDDI-LP64 DAS)
|
|
- Netelligent 100 FDDI DAS Fibre SC
|
|
- Netelligent 100 FDDI SAS Fibre SC
|
|
- Netelligent 100 FDDI DAS UTP
|
|
- Netelligent 100 FDDI SAS UTP
|
|
- Netelligent 100 FDDI SAS Fibre MIC
|
|
|
|
Read <file:Documentation/networking/skfp.txt> for information about
|
|
the driver.
|
|
|
|
Questions concerning this driver can be addressed to:
|
|
<linux@syskonnect.de>
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called skfp. This is recommended.
|
|
|
|
endif # FDDI
|