Commit 6deb5359 authored by Jakub Kicinski's avatar Jakub Kicinski
Browse files

net: remove unused ATM protocols and legacy ATM device drivers



Remove the ATM protocol modules and PCI/SBUS ATM device drivers
that are no longer in active use.

The ATM core protocol stack, PPPoATM, BR2684, and USB DSL modem
drivers (drivers/usb/atm/) are retained in-tree to maintain PPP
over ATM (PPPoA) and PPPoE-over-BR2684 support for DSL connections.
The Solos ADSL2+ PCI driver is also retained.

Removed ATM protocol modules:
 - net/atm/clip.c - Classical IP over ATM (RFC 2225)
 - net/atm/lec.c - LAN Emulation Client (LANE)
 - net/atm/mpc.c, mpoa_caches.c, mpoa_proc.c - Multi-Protocol Over ATM

Removed PCI/SBUS ATM device drivers (drivers/atm/):
 - adummy, atmtcp - software/testing ATM devices
 - eni - Efficient Networks ENI155P (OC-3, ~1995)
 - fore200e - FORE Systems 200E PCI/SBUS (OC-3, ~1999)
 - he - ForeRunner HE (OC-3/OC-12, ~2000)
 - idt77105 - IDT 77105 25 Mbps ATM PHY
 - idt77252 - IDT 77252 NICStAR II (OC-3, ~2000)
 - iphase - Interphase ATM PCI (OC-3/DS3/E3)
 - lanai - Efficient Networks Speedstream 3010
 - nicstar - IDT 77201 NICStAR (155/25 Mbps, ~1999)
 - suni - PMC S/UNI SONET PHY library

Also clean up references in:
 - net/bridge/ - remove ATM LANE hook (br_fdb_test_addr_hook,
   br_fdb_test_addr)
 - net/core/dev.c - remove br_fdb_test_addr_hook export
 - defconfig files - remove ATM driver config options

The removed code is moved to an out-of-tree module package (mod-orphan).

Acked-by: default avatarAndy Shevchenko <andriy.shevchenko@intel.com>
Reviewed-by: default avatarSimon Horman <horms@kernel.org>
Reviewed-by: default avatarNikolay Aleksandrov <razor@blackwall.org>
Link: https://patch.msgid.link/20260422041846.2035118-1-kuba@kernel.org


Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
parent dd8d4bc2
Loading
Loading
Loading
Loading
+0 −2
Original line number Diff line number Diff line
@@ -835,14 +835,12 @@ networking/e100 networking/device_drivers/ethernet/intel/e100
networking/e1000 networking/device_drivers/ethernet/intel/e1000
networking/e1000e networking/device_drivers/ethernet/intel/e1000e
networking/fm10k networking/device_drivers/ethernet/intel/fm10k
networking/fore200e networking/device_drivers/atm/fore200e
networking/hinic networking/device_drivers/ethernet/huawei/hinic
networking/i40e networking/device_drivers/ethernet/intel/i40e
networking/iavf networking/device_drivers/ethernet/intel/iavf
networking/ice networking/device_drivers/ethernet/intel/ice
networking/igb networking/device_drivers/ethernet/intel/igb
networking/igbvf networking/device_drivers/ethernet/intel/igbvf
networking/iphase networking/device_drivers/atm/iphase
networking/ixgbe networking/device_drivers/ethernet/intel/ixgbe
networking/ixgbevf networking/device_drivers/ethernet/intel/ixgbevf
networking/netdev-FAQ process/maintainer-netdev
+0 −66
Original line number Diff line number Diff line
.. SPDX-License-Identifier: GPL-2.0

=============================================
FORE Systems PCA-200E/SBA-200E ATM NIC driver
=============================================

This driver adds support for the FORE Systems 200E-series ATM adapters
to the Linux operating system. It is based on the earlier PCA-200E driver
written by Uwe Dannowski.

The driver simultaneously supports PCA-200E and SBA-200E adapters on
i386, alpha (untested), powerpc, sparc and sparc64 archs.

The intent is to enable the use of different models of FORE adapters at the
same time, by hosts that have several bus interfaces (such as PCI+SBUS,
or PCI+EISA).

Only PCI and SBUS devices are currently supported by the driver, but support
for other bus interfaces such as EISA should not be too hard to add.


Firmware Copyright Notice
-------------------------

Please read the fore200e_firmware_copyright file present
in the linux/drivers/atm directory for details and restrictions.


Firmware Updates
----------------

The FORE Systems 200E-series driver is shipped with firmware data being
uploaded to the ATM adapters at system boot time or at module loading time.
The supplied firmware images should work with all adapters.

However, if you encounter problems (the firmware doesn't start or the driver
is unable to read the PROM data), you may consider trying another firmware
version. Alternative binary firmware images can be found somewhere on the
ForeThought CD-ROM supplied with your adapter by FORE Systems.

You can also get the latest firmware images from FORE Systems at
https://en.wikipedia.org/wiki/FORE_Systems. Register TACTics Online and go to
the 'software updates' pages. The firmware binaries are part of
the various ForeThought software distributions.

Notice that different versions of the PCA-200E firmware exist, depending
on the endianness of the host architecture. The driver is shipped with
both little and big endian PCA firmware images.

Name and location of the new firmware images can be set at kernel
configuration time:

1. Copy the new firmware binary files (with .bin, .bin1 or .bin2 suffix)
   to some directory, such as linux/drivers/atm.

2. Reconfigure your kernel to set the new firmware name and location.
   Expected pathnames are absolute or relative to the drivers/atm directory.

3. Rebuild and re-install your kernel or your module.


Feedback
--------

Feedback is welcome. Please send success stories/bug reports/
patches/improvement/comments/flames to <lizzi@cnam.fr>.
+0 −2
Original line number Diff line number Diff line
@@ -9,5 +9,3 @@ Contents:
   :maxdepth: 2

   cxacru
   fore200e
   iphase
+0 −193
Original line number Diff line number Diff line
.. SPDX-License-Identifier: GPL-2.0

==================================
ATM (i)Chip IA Linux Driver Source
==================================

			      READ ME FIRST

--------------------------------------------------------------------------------

		     Read This Before You Begin!

--------------------------------------------------------------------------------

Description
===========

This is the README file for the Interphase PCI ATM (i)Chip IA Linux driver
source release.

The features and limitations of this driver are as follows:

    - A single VPI (VPI value of 0) is supported.
    - Supports 4K VCs for the server board (with 512K control memory) and 1K
      VCs for the client board (with 128K control memory).
    - UBR, ABR and CBR service categories are supported.
    - Only AAL5 is supported.
    - Supports setting of PCR on the VCs.
    - Multiple adapters in a system are supported.
    - All variants of Interphase ATM PCI (i)Chip adapter cards are supported,
      including x575 (OC3, control memory 128K , 512K and packet memory 128K,
      512K and 1M), x525 (UTP25) and x531 (DS3 and E3). See
      http://www.iphase.com/
      for details.
    - Only x86 platforms are supported.
    - SMP is supported.


Before You Start
================


Installation
------------

1. Installing the adapters in the system

   To install the ATM adapters in the system, follow the steps below.

       a. Login as root.
       b. Shut down the system and power off the system.
       c. Install one or more ATM adapters in the system.
       d. Connect each adapter to a port on an ATM switch. The green 'Link'
	  LED on the front panel of the adapter will be on if the adapter is
	  connected to the switch properly when the system is powered up.
       e. Power on and boot the system.

2. [ Removed ]

3. Rebuild kernel with ABR support

   [ a. and b. removed ]

    c. Reconfigure the kernel, choose the Interphase ia driver through "make
       menuconfig" or "make xconfig".
    d. Rebuild the kernel, loadable modules and the atm tools.
    e. Install the new built kernel and modules and reboot.

4. Load the adapter hardware driver (ia driver) if it is built as a module

       a. Login as root.
       b. Change directory to /lib/modules/<kernel-version>/atm.
       c. Run "insmod suni.o;insmod iphase.o"
	  The yellow 'status' LED on the front panel of the adapter will blink
	  while the driver is loaded in the system.
       d. To verify that the 'ia' driver is loaded successfully, run the
	  following command::

	      cat /proc/atm/devices

	  If the driver is loaded successfully, the output of the command will
	  be similar to the following lines::

	      Itf Type    ESI/"MAC"addr AAL(TX,err,RX,err,drop) ...
	      0   ia      xxxxxxxxx  0 ( 0 0 0 0 0 )  5 ( 0 0 0 0 0 )

	  You can also check the system log file /var/log/messages for messages
	  related to the ATM driver.

5. Ia Driver Configuration

5.1 Configuration of adapter buffers
    The (i)Chip boards have 3 different packet RAM size variants: 128K, 512K and
    1M. The RAM size decides the number of buffers and buffer size. The default
    size and number of buffers are set as following:

	=========  =======  ======   ======   ======   ======   ======
	 Total     Rx RAM   Tx RAM   Rx Buf   Tx Buf   Rx buf   Tx buf
	 RAM size  size     size     size     size     cnt      cnt
	=========  =======  ======   ======   ======   ======   ======
	   128K      64K      64K      10K      10K       6        6
	   512K     256K     256K      10K      10K      25       25
	     1M     512K     512K      10K      10K      51       51
	=========  =======  ======   ======   ======   ======   ======

       These setting should work well in most environments, but can be
       changed by typing the following command::

	   insmod <IA_DIR>/ia.o IA_RX_BUF=<RX_CNT> IA_RX_BUF_SZ=<RX_SIZE> \
		   IA_TX_BUF=<TX_CNT> IA_TX_BUF_SZ=<TX_SIZE>

       Where:

	    - RX_CNT = number of receive buffers in the range (1-128)
	    - RX_SIZE = size of receive buffers in the range (48-64K)
	    - TX_CNT = number of transmit buffers in the range (1-128)
	    - TX_SIZE = size of transmit buffers in the range (48-64K)

	    1. Transmit and receive buffer size must be a multiple of 4.
	    2. Care should be taken so that the memory required for the
	       transmit and receive buffers is less than or equal to the
	       total adapter packet memory.

5.2 Turn on ia debug trace

    When the ia driver is built with the CONFIG_ATM_IA_DEBUG flag, the driver
    can provide more debug trace if needed. There is a bit mask variable,
    IADebugFlag, which controls the output of the traces. You can find the bit
    map of the IADebugFlag in iphase.h.
    The debug trace can be turn on through the insmod command line option, for
    example, "insmod iphase.o IADebugFlag=0xffffffff" can turn on all the debug
    traces together with loading the driver.

6. Ia Driver Test Using ttcp_atm and PVC

   For the PVC setup, the test machines can either be connected back-to-back or
   through a switch. If connected through the switch, the switch must be
   configured for the PVC(s).

   a. For UBR test:

      At the test machine intended to receive data, type::

	 ttcp_atm -r -a -s 0.100

      At the other test machine, type::

	 ttcp_atm -t -a -s 0.100 -n 10000

      Run "ttcp_atm -h" to display more options of the ttcp_atm tool.
   b. For ABR test:

      It is the same as the UBR testing, but with an extra command option::

	 -Pabr:max_pcr=<xxx>

      where:

	     xxx = the maximum peak cell rate, from 170 - 353207.

      This option must be set on both the machines.

   c. For CBR test:

      It is the same as the UBR testing, but with an extra command option::

	 -Pcbr:max_pcr=<xxx>

      where:

	     xxx = the maximum peak cell rate, from 170 - 353207.

      This option may only be set on the transmit machine.


Outstanding Issues
==================



Contact Information
-------------------

::

     Customer Support:
	 United States:	Telephone:	(214) 654-5555
			Fax:		(214) 654-5500
			E-Mail:		intouch@iphase.com
	 Europe:	Telephone:	33 (0)1 41 15 44 00
			Fax:		33 (0)1 41 15 12 13
     World Wide Web:	http://www.iphase.com
     Anonymous FTP:	ftp.iphase.com
+2 −0
Original line number Diff line number Diff line
@@ -4151,10 +4151,12 @@ L: netdev@vger.kernel.org
S:	Maintained
W:	http://linux-atm.sourceforge.net
F:	drivers/atm/
F:	drivers/usb/atm/
F:	include/linux/atm*
F:	include/linux/sonet.h
F:	include/uapi/linux/atm*
F:	include/uapi/linux/sonet.h
F:	net/atm/
ATMEL MACB ETHERNET DRIVER
M:	Nicolas Ferre <nicolas.ferre@microchip.com>
Loading