License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
|
# ATM device configuration
|
|
|
|
|
#
|
|
|
|
|
|
2007-05-11 13:52:57 +08:00
|
|
|
menuconfig ATM_DRIVERS
|
|
|
|
|
bool "ATM drivers"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on NETDEVICES && ATM
|
2007-05-11 13:52:57 +08:00
|
|
|
default y
|
2007-08-18 18:56:21 +08:00
|
|
|
---help---
|
|
|
|
|
Say Y here to get to see options for Asynchronous Transfer Mode
|
|
|
|
|
device drivers. This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
2007-05-11 13:52:57 +08:00
|
|
|
|
2007-06-28 05:09:54 +08:00
|
|
|
if ATM_DRIVERS && NETDEVICES && ATM
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2005-11-30 08:17:11 +08:00
|
|
|
config ATM_DUMMY
|
|
|
|
|
tristate "Dummy ATM driver"
|
|
|
|
|
help
|
|
|
|
|
Dummy ATM driver. Useful for proxy signalling, testing,
|
|
|
|
|
and development. If unsure, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ATM_TCP
|
|
|
|
|
tristate "ATM over TCP"
|
2007-05-11 13:52:57 +08:00
|
|
|
depends on INET
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
ATM over TCP driver. Useful mainly for development and for
|
|
|
|
|
experiments. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config ATM_LANAI
|
|
|
|
|
tristate "Efficient Networks Speedstream 3010"
|
|
|
|
|
depends on PCI && ATM
|
|
|
|
|
help
|
|
|
|
|
Supports ATM cards based on the Efficient Networks "Lanai"
|
|
|
|
|
chipset such as the Speedstream 3010 and the ENI-25p. The
|
|
|
|
|
Speedstream 3060 is currently not supported since we don't
|
|
|
|
|
have the code to drive the on-board Alcatel DSL chipset (yet).
|
|
|
|
|
|
|
|
|
|
config ATM_ENI
|
|
|
|
|
tristate "Efficient Networks ENI155P"
|
2007-05-11 13:52:57 +08:00
|
|
|
depends on PCI
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
Driver for the Efficient Networks ENI155p series and SMC ATM
|
|
|
|
|
Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
|
|
|
|
|
2MB on-board RAM (Efficient calls them "C" and "S", respectively),
|
|
|
|
|
and the FPGA and the ASIC Tonga versions of the board are supported.
|
|
|
|
|
The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
|
|
|
|
|
adapters.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called eni.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_DEBUG
|
|
|
|
|
bool "Enable extended debugging"
|
|
|
|
|
depends on ATM_ENI
|
|
|
|
|
help
|
|
|
|
|
Extended debugging records various events and displays that list
|
|
|
|
|
when an inconsistency is detected. This mechanism is faster than
|
|
|
|
|
generally using printks, but still has some impact on performance.
|
|
|
|
|
Note that extended debugging may create certain race conditions
|
|
|
|
|
itself. Enable this ONLY if you suspect problems with the driver.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_TUNE_BURST
|
|
|
|
|
bool "Fine-tune burst settings"
|
|
|
|
|
depends on ATM_ENI
|
|
|
|
|
---help---
|
|
|
|
|
In order to obtain good throughput, the ENI NIC can transfer
|
|
|
|
|
multiple words of data per PCI bus access cycle. Such a multi-word
|
|
|
|
|
transfer is called a burst.
|
|
|
|
|
|
|
|
|
|
The default settings for the burst sizes are suitable for most PCI
|
|
|
|
|
chipsets. However, in some cases, large bursts may overrun buffers
|
|
|
|
|
in the PCI chipset and cause data corruption. In such cases, large
|
|
|
|
|
bursts must be disabled and only (slower) small bursts can be used.
|
|
|
|
|
The burst sizes can be set independently in the send (TX) and
|
|
|
|
|
receive (RX) direction.
|
|
|
|
|
|
|
|
|
|
Note that enabling many different burst sizes in the same direction
|
|
|
|
|
may increase the cost of setting up a transfer such that the
|
|
|
|
|
resulting throughput is lower than when using only the largest
|
|
|
|
|
available burst size.
|
|
|
|
|
|
|
|
|
|
Also, sometimes larger bursts lead to lower throughput, e.g. on an
|
|
|
|
|
Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
|
|
|
|
|
when going from 8W to 16W bursts.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_TX_16W
|
|
|
|
|
bool "Enable 16W TX bursts (discouraged)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst sixteen words at once in the send direction. This may work
|
|
|
|
|
with recent PCI chipsets, but is known to fail with older chipsets.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_TX_8W
|
|
|
|
|
bool "Enable 8W TX bursts (recommended)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst eight words at once in the send direction. This is the default
|
|
|
|
|
setting.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_TX_4W
|
|
|
|
|
bool "Enable 4W TX bursts (optional)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst four words at once in the send direction. You may want to try
|
|
|
|
|
this if you have disabled 8W bursts. Enabling 4W if 8W is also set
|
|
|
|
|
may or may not improve throughput.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_TX_2W
|
|
|
|
|
bool "Enable 2W TX bursts (optional)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst two words at once in the send direction. You may want to try
|
|
|
|
|
this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
|
|
|
|
|
are also set may or may not improve throughput.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_RX_16W
|
|
|
|
|
bool "Enable 16W RX bursts (discouraged)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst sixteen words at once in the receive direction. This may work
|
|
|
|
|
with recent PCI chipsets, but is known to fail with older chipsets.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_RX_8W
|
|
|
|
|
bool "Enable 8W RX bursts (discouraged)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst eight words at once in the receive direction. This may work
|
|
|
|
|
with recent PCI chipsets, but is known to fail with older chipsets,
|
|
|
|
|
such as the Intel Neptune series.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_RX_4W
|
|
|
|
|
bool "Enable 4W RX bursts (recommended)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst four words at once in the receive direction. This is the
|
|
|
|
|
default setting. Enabling 4W if 8W is also set may or may not
|
|
|
|
|
improve throughput.
|
|
|
|
|
|
|
|
|
|
config ATM_ENI_BURST_RX_2W
|
|
|
|
|
bool "Enable 2W RX bursts (optional)"
|
|
|
|
|
depends on ATM_ENI_TUNE_BURST
|
|
|
|
|
help
|
|
|
|
|
Burst two words at once in the receive direction. You may want to
|
|
|
|
|
try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
|
|
|
|
|
8W are also set may or may not improve throughput.
|
|
|
|
|
|
|
|
|
|
config ATM_FIRESTREAM
|
|
|
|
|
tristate "Fujitsu FireStream (FS50/FS155) "
|
2007-07-16 14:40:05 +08:00
|
|
|
depends on PCI && VIRT_TO_BUS
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Driver for the Fujitsu FireStream 155 (MB86697) and
|
|
|
|
|
FireStream 50 (MB86695) ATM PCI chips.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called firestream.
|
|
|
|
|
|
|
|
|
|
config ATM_ZATM
|
|
|
|
|
tristate "ZeitNet ZN1221/ZN1225"
|
2007-07-16 14:40:05 +08:00
|
|
|
depends on PCI && VIRT_TO_BUS
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
|
|
|
|
|
adapters.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called zatm.
|
|
|
|
|
|
|
|
|
|
config ATM_ZATM_DEBUG
|
|
|
|
|
bool "Enable extended debugging"
|
|
|
|
|
depends on ATM_ZATM
|
|
|
|
|
help
|
|
|
|
|
Extended debugging records various events and displays that list
|
|
|
|
|
when an inconsistency is detected. This mechanism is faster than
|
|
|
|
|
generally using printks, but still has some impact on performance.
|
|
|
|
|
Note that extended debugging may create certain race conditions
|
|
|
|
|
itself. Enable this ONLY if you suspect problems with the driver.
|
|
|
|
|
|
|
|
|
|
config ATM_NICSTAR
|
|
|
|
|
tristate "IDT 77201 (NICStAR) (ForeRunnerLE)"
|
2010-05-29 17:04:25 +08:00
|
|
|
depends on PCI
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The NICStAR chipset family is used in a large number of ATM NICs for
|
|
|
|
|
25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
|
|
|
|
|
series. Say Y if you have one of those.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called nicstar.
|
|
|
|
|
|
|
|
|
|
config ATM_NICSTAR_USE_SUNI
|
|
|
|
|
bool "Use suni PHY driver (155Mbps)"
|
|
|
|
|
depends on ATM_NICSTAR
|
|
|
|
|
help
|
|
|
|
|
Support for the S-UNI and compatible PHYsical layer chips. These are
|
|
|
|
|
found in most 155Mbps NICStAR based ATM cards, namely in the
|
|
|
|
|
ForeRunner LE155 cards. This driver provides detection of cable~
|
|
|
|
|
removal and reinsertion and provides some statistics. This driver
|
|
|
|
|
doesn't have removal capability when compiled as a module, so if you
|
|
|
|
|
need that capability don't include S-UNI support (it's not needed to
|
|
|
|
|
make the card work).
|
|
|
|
|
|
|
|
|
|
config ATM_NICSTAR_USE_IDT77105
|
2019-08-19 13:04:25 +08:00
|
|
|
bool "Use IDT77105 PHY driver (25Mbps)"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on ATM_NICSTAR
|
|
|
|
|
help
|
|
|
|
|
Support for the PHYsical layer chip in ForeRunner LE25 cards. In
|
|
|
|
|
addition to cable removal/reinsertion detection, this driver allows
|
|
|
|
|
you to control the loopback mode of the chip via a dedicated IOCTL.
|
|
|
|
|
This driver is required for proper handling of temporary carrier
|
|
|
|
|
loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
|
|
|
|
|
|
|
|
|
|
config ATM_IDT77252
|
|
|
|
|
tristate "IDT 77252 (NICStAR II)"
|
2007-05-11 13:52:57 +08:00
|
|
|
depends on PCI
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Driver for the IDT 77252 ATM PCI chips.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called idt77252.
|
|
|
|
|
|
|
|
|
|
config ATM_IDT77252_DEBUG
|
|
|
|
|
bool "Enable debugging messages"
|
|
|
|
|
depends on ATM_IDT77252
|
|
|
|
|
help
|
|
|
|
|
Somewhat useful debugging messages are available. The choice of
|
|
|
|
|
messages is controlled by a bitmap. This may be specified as a
|
|
|
|
|
module argument. See the file <file:drivers/atm/idt77252.h> for
|
|
|
|
|
the meanings of the bits in the mask.
|
|
|
|
|
|
|
|
|
|
When active, these messages can have a significant impact on the
|
|
|
|
|
speed of the driver, and the size of your syslog files! When
|
|
|
|
|
inactive, they will have only a modest impact on performance.
|
|
|
|
|
|
|
|
|
|
config ATM_IDT77252_RCV_ALL
|
|
|
|
|
bool "Receive ALL cells in raw queue"
|
|
|
|
|
depends on ATM_IDT77252
|
|
|
|
|
help
|
|
|
|
|
Enable receiving of all cells on the ATM link, that do not match
|
|
|
|
|
an open connection in the raw cell queue of the driver. Useful
|
|
|
|
|
for debugging or special applications only, so the safe answer is N.
|
|
|
|
|
|
|
|
|
|
config ATM_IDT77252_USE_SUNI
|
|
|
|
|
bool
|
|
|
|
|
depends on ATM_IDT77252
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config ATM_AMBASSADOR
|
|
|
|
|
tristate "Madge Ambassador (Collage PCI 155 Server)"
|
2007-07-16 14:40:05 +08:00
|
|
|
depends on PCI && VIRT_TO_BUS
|
2006-12-08 18:36:28 +08:00
|
|
|
select BITREVERSE
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This is a driver for ATMizer based ATM card produced by Madge
|
|
|
|
|
Networks Ltd. Say Y (or M to compile as a module named ambassador)
|
|
|
|
|
here if you have one of these cards.
|
|
|
|
|
|
|
|
|
|
config ATM_AMBASSADOR_DEBUG
|
|
|
|
|
bool "Enable debugging messages"
|
|
|
|
|
depends on ATM_AMBASSADOR
|
|
|
|
|
---help---
|
|
|
|
|
Somewhat useful debugging messages are available. The choice of
|
|
|
|
|
messages is controlled by a bitmap. This may be specified as a
|
|
|
|
|
module argument (kernel command line argument as well?), changed
|
|
|
|
|
dynamically using an ioctl (not yet) or changed by sending the
|
|
|
|
|
string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
|
|
|
|
|
<file:drivers/atm/ambassador.h> for the meanings of the bits in the
|
|
|
|
|
mask.
|
|
|
|
|
|
|
|
|
|
When active, these messages can have a significant impact on the
|
|
|
|
|
speed of the driver, and the size of your syslog files! When
|
|
|
|
|
inactive, they will have only a modest impact on performance.
|
|
|
|
|
|
|
|
|
|
config ATM_HORIZON
|
|
|
|
|
tristate "Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)"
|
2007-07-16 14:40:05 +08:00
|
|
|
depends on PCI && VIRT_TO_BUS
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This is a driver for the Horizon chipset ATM adapter cards once
|
|
|
|
|
produced by Madge Networks Ltd. Say Y (or M to compile as a module
|
|
|
|
|
named horizon) here if you have one of these cards.
|
|
|
|
|
|
|
|
|
|
config ATM_HORIZON_DEBUG
|
|
|
|
|
bool "Enable debugging messages"
|
|
|
|
|
depends on ATM_HORIZON
|
|
|
|
|
---help---
|
|
|
|
|
Somewhat useful debugging messages are available. The choice of
|
|
|
|
|
messages is controlled by a bitmap. This may be specified as a
|
|
|
|
|
module argument (kernel command line argument as well?), changed
|
|
|
|
|
dynamically using an ioctl (not yet) or changed by sending the
|
|
|
|
|
string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
|
|
|
|
|
<file:drivers/atm/horizon.h> for the meanings of the bits in the
|
|
|
|
|
mask.
|
|
|
|
|
|
|
|
|
|
When active, these messages can have a significant impact on the
|
|
|
|
|
speed of the driver, and the size of your syslog files! When
|
|
|
|
|
inactive, they will have only a modest impact on performance.
|
|
|
|
|
|
|
|
|
|
config ATM_IA
|
|
|
|
|
tristate "Interphase ATM PCI x575/x525/x531"
|
2008-06-18 07:21:18 +08:00
|
|
|
depends on PCI
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
This is a driver for the Interphase (i)ChipSAR adapter cards
|
|
|
|
|
which include a variety of variants in term of the size of the
|
|
|
|
|
control memory (128K-1KVC, 512K-4KVC), the size of the packet
|
|
|
|
|
memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
|
|
|
|
|
UTP155, UTP25, DS3 and E3). Go to:
|
2010-10-18 17:03:14 +08:00
|
|
|
<http://www.iphase.com/>
|
2005-04-17 06:20:36 +08:00
|
|
|
for more info about the cards. Say Y (or M to compile as a module
|
|
|
|
|
named iphase) here if you have one of these cards.
|
|
|
|
|
|
|
|
|
|
See the file <file:Documentation/networking/iphase.txt> for further
|
|
|
|
|
details.
|
|
|
|
|
|
|
|
|
|
config ATM_IA_DEBUG
|
|
|
|
|
bool "Enable debugging messages"
|
|
|
|
|
depends on ATM_IA
|
|
|
|
|
---help---
|
|
|
|
|
Somewhat useful debugging messages are available. The choice of
|
|
|
|
|
messages is controlled by a bitmap. This may be specified as a
|
|
|
|
|
module argument (kernel command line argument as well?), changed
|
|
|
|
|
dynamically using an ioctl (Get the debug utility, iadbg, from
|
|
|
|
|
<ftp://ftp.iphase.com/pub/atm/pci/>).
|
|
|
|
|
|
|
|
|
|
See the file <file:drivers/atm/iphase.h> for the meanings of the
|
|
|
|
|
bits in the mask.
|
|
|
|
|
|
|
|
|
|
When active, these messages can have a significant impact on the
|
|
|
|
|
speed of the driver, and the size of your syslog files! When
|
|
|
|
|
inactive, they will have only a modest impact on performance.
|
|
|
|
|
|
2008-06-18 07:23:11 +08:00
|
|
|
config ATM_FORE200E
|
2005-04-17 06:20:36 +08:00
|
|
|
tristate "FORE Systems 200E-series"
|
2008-06-18 07:23:11 +08:00
|
|
|
depends on (PCI || SBUS)
|
|
|
|
|
select FW_LOADER
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
This is a driver for the FORE Systems 200E-series ATM adapter
|
|
|
|
|
cards. It simultaneously supports PCA-200E and SBA-200E models
|
|
|
|
|
on PCI and SBUS hosts. Say Y (or M to compile as a module
|
|
|
|
|
named fore_200e) here if you have one of these ATM adapters.
|
|
|
|
|
|
|
|
|
|
See the file <file:Documentation/networking/fore200e.txt> for
|
|
|
|
|
further details.
|
|
|
|
|
|
|
|
|
|
config ATM_FORE200E_USE_TASKLET
|
|
|
|
|
bool "Defer interrupt work to a tasklet"
|
2008-06-18 07:23:11 +08:00
|
|
|
depends on ATM_FORE200E
|
2005-04-17 06:20:36 +08:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This defers work to be done by the interrupt handler to a
|
2006-07-09 04:30:09 +08:00
|
|
|
tasklet instead of handling everything at interrupt time. This
|
2005-04-17 06:20:36 +08:00
|
|
|
may improve the responsive of the host.
|
|
|
|
|
|
|
|
|
|
config ATM_FORE200E_TX_RETRY
|
|
|
|
|
int "Maximum number of tx retries"
|
2008-06-18 07:23:11 +08:00
|
|
|
depends on ATM_FORE200E
|
2005-04-17 06:20:36 +08:00
|
|
|
default "16"
|
|
|
|
|
---help---
|
|
|
|
|
Specifies the number of times the driver attempts to transmit
|
|
|
|
|
a message before giving up, if the transmit queue of the ATM card
|
|
|
|
|
is transiently saturated.
|
|
|
|
|
|
|
|
|
|
Saturation of the transmit queue may occur only under extreme
|
|
|
|
|
conditions, e.g. when a fast host continuously submits very small
|
|
|
|
|
frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
|
|
|
|
|
|
|
|
|
|
Note that under common conditions, it is unlikely that you encounter
|
|
|
|
|
a saturation of the transmit queue, so the retry mechanism never
|
|
|
|
|
comes into play.
|
|
|
|
|
|
|
|
|
|
config ATM_FORE200E_DEBUG
|
|
|
|
|
int "Debugging level (0-3)"
|
2008-06-18 07:23:11 +08:00
|
|
|
depends on ATM_FORE200E
|
2005-04-17 06:20:36 +08:00
|
|
|
default "0"
|
|
|
|
|
help
|
|
|
|
|
Specifies the level of debugging messages issued by the driver.
|
|
|
|
|
The verbosity of the driver increases with the value of this
|
|
|
|
|
parameter.
|
|
|
|
|
|
|
|
|
|
When active, these messages can have a significant impact on
|
|
|
|
|
the performances of the driver, and the size of your syslog files!
|
|
|
|
|
Keep the debugging level to 0 during normal operations.
|
|
|
|
|
|
|
|
|
|
config ATM_HE
|
|
|
|
|
tristate "ForeRunner HE Series"
|
2007-05-11 13:52:57 +08:00
|
|
|
depends on PCI
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This is a driver for the Marconi ForeRunner HE-series ATM adapter
|
|
|
|
|
cards. It simultaneously supports the 155 and 622 versions.
|
|
|
|
|
|
|
|
|
|
config ATM_HE_USE_SUNI
|
|
|
|
|
bool "Use S/UNI PHY driver"
|
|
|
|
|
depends on ATM_HE
|
|
|
|
|
help
|
|
|
|
|
Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
|
|
|
|
|
HE cards. This driver provides carrier detection some statistics.
|
|
|
|
|
|
2008-12-23 12:09:02 +08:00
|
|
|
config ATM_SOLOS
|
|
|
|
|
tristate "Solos ADSL2+ PCI Multiport card driver"
|
|
|
|
|
depends on PCI
|
2010-05-16 11:12:36 +08:00
|
|
|
select FW_LOADER
|
2008-12-23 12:09:02 +08:00
|
|
|
help
|
|
|
|
|
Support for the Solos multiport ADSL2+ card.
|
|
|
|
|
|
2007-05-11 13:52:57 +08:00
|
|
|
endif # ATM
|