mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-07 09:09:23 +00:00
795e272e54
Recent versions of the PCI Express specification have deprecated support for I/O transactions and actually some PCIe host bridges, such as Power Systems Host Bridge 4 (PHB4), do not implement them. Conversely a DEFEA adapter can have its MMIO decoding disabled with ECU (EISA Configuration Utility) and therefore not available for us with the resource allocation infrastructure we implement. However either I/O address space will always be available for use with the DEFEA (EISA) and DEFPA (PCI) adapters and both have double address decoding implemented in hardware for Control and Status Register access. The two kinds of adapters can be present both at once in a single mixed PCI/EISA system. For the DEFTA (TURBOchannel) variant there is no issue as there has been no port I/O address space defined for that bus. To make people's life easier and the driver more robust remove the DEFXX_MMIO configuration option so as to rather than making the choice for the I/O address space to use at build time for all the adapters installed in the system let the driver choose the most suitable address space dynamically on a case-by-case basis at run time. Make MMIO the default and resort to port I/O should the default fail for some reason. This way multiple adapters installed in one system can use different I/O address spaces each, in particular in the presence of DEFEA adapters in a pure-EISA or a mixed EISA/PCI system (it is expected that DEFPA boards will use MMIO in normal circumstances). The choice of the I/O address space to use continues being reported by the driver on startup, e.g.: eisa 00:05: EISA: slot 5: DEC3002 detected defxx: v1.12 2021/03/10 Lawrence V. Stefani and others 00:05: DEFEA at I/O addr = 0x5000, IRQ = 10, Hardware addr = 00-00-f8-c8-b3-b6 00:05: registered as fddi0 and: defxx: v1.12 2021/03/10 Lawrence V. Stefani and others 0031:02:04.0: DEFPA at MMIO addr = 0x620c080020000, IRQ = 57, Hardware addr = 00-60-6d-93-91-98 0031:02:04.0: registered as fddi0 and: defxx: v1.12 2021/03/10 Lawrence V. Stefani and others tc2: DEFTA at MMIO addr = 0x1f100000, IRQ = 21, Hardware addr = 08-00-2b-b0-8b-1e tc2: registered as fddi0 so there is no need to add further information. The change is supposed to cause a negligible performance hit as I/O accessors will now have code executed conditionally at run time. Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk> Signed-off-by: David S. Miller <davem@davemloft.net>
73 lines
2.3 KiB
Text
73 lines
2.3 KiB
Text
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# 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 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/device_drivers/fddi/skfp.rst>
|
|
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
|