Linux/Unix编程

开发平台：

Unix_Linux

Configure.help：源码内容

This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called rose.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Serial port KISS driver for AX.25
CONFIG_MKISS
KISS is a protocol used for the exchange of data between a computer
and a Terminal Node Controller (a small embedded system commonly
used for networking over AX.25 amateur radio connections; it
connects the computer's serial port with the radio's microphone
input and speaker output).
Although KISS is less advanced than the 6pack protocol, it has
the advantage that it is already supported by most modern TNCs
without the need for a firmware upgrade.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called mkiss.o.
Serial port 6PACK driver for AX.25
CONFIG_6PACK
6pack is a transmission protocol for the data exchange between your
PC and your TNC (the Terminal Node Controller acts as a kind of
modem connecting your computer's serial port to your radio's
microphone input and speaker output). This protocol can be used as
an alternative to KISS for networking over AX.25 amateur radio
connections, but it has some extended functionality.
Note that this driver is still experimental and might cause
problems. For details about the features and the usage of the
driver, read <file:Documentation/networking/6pack.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called 6pack.o.
BPQ Ethernet driver
CONFIG_BPQETHER
AX.25 is the protocol used for computer communication over amateur
radio. If you say Y here, you will be able to send and receive AX.25
traffic over Ethernet (also called "BPQ AX.25"), which could be
useful if some other computer on your local network has a direct
amateur radio connection.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called bpqether.o.
High-speed (DMA) SCC driver for AX.25
CONFIG_DMASCC
This is a driver for high-speed SCC boards, i.e. those supporting
DMA on one port. You usually use those boards to connect your
computer to an amateur radio modem (such as the WA4DSY 56kbps
modem), in order to send and receive AX.25 packet radio network
traffic.
Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
PackeTwin, and S5SCC/DMA boards. They are detected automatically.
If you have one of these cards, say Y here and read the AX25-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
This driver can operate multiple boards simultaneously. If you
compile it as a module (by saying M instead of Y), it will be called
dmascc.o. If you don't pass any parameter to the driver, all
possible I/O addresses are probed. This could irritate other devices
that are currently not in use. You may specify the list of addresses
to be probed by "dmascc=addr1,addr2,..." (when compiled into the
kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
network interfaces will be called dmascc0 and dmascc1 for the board
detected first, dmascc2 and dmascc3 for the second one, and so on.
Before you configure each interface with ifconfig, you MUST set
certain parameters, such as channel access timing, clock mode, and
DMA channel. This is accomplished with a small utility program,
dmascc_cfg, available at
<http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
at least version 1.27 of dmascc_cfg, as older versions will not
work with the current driver.
Z8530 SCC driver for AX.25
CONFIG_SCC
These cards are used to connect your Linux box to an amateur radio
in order to communicate with other computers. If you want to use
this, read <file:Documentation/networking/z8530drv.txt> and the
AX25-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. Also make sure to say Y
to "Amateur Radio AX.25 Level 2" support.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called scc.o.
Support for TRX that feedback the tx signal to rx
CONFIG_SCC_TRXECHO
Some transmitters feed the transmitted signal back to the receive
line. Say Y here to foil this by explicitly disabling the receiver
during data transmission. If in doubt, say Y.
Additional delay for PA0HZP OptoSCC compatible boards
CONFIG_SCC_DELAY
Say Y here if you experience problems with the SCC driver not
working properly; please read
<file:Documentation/networking/z8530drv.txt> for details. If unsure,
say N.
YAM driver for AX.25
CONFIG_YAM
The YAM is a modem for packet radio which connects to the serial
port and includes some of the functions of a Terminal Node
Controller. If you have one of those, say Y here.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called yam.o.
BAYCOM picpar and par96 driver for AX.25
CONFIG_BAYCOM_PAR
This is a driver for Baycom style simple amateur radio modems that
connect to a parallel interface. The driver supports the picpar and
par96 designs. To configure the driver, use the sethdlc utility
available in the standard ax25 utilities package. For information on
the modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_par.o.
BAYCOM EPP driver for AX.25
CONFIG_BAYCOM_EPP
This is a driver for Baycom style simple amateur radio modems that
connect to a parallel interface. The driver supports the EPP
designs. To configure the driver, use the sethdlc utility available
in the standard ax25 utilities package. For information on the
modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_par.o.
BAYCOM ser12 full-duplex driver for AX.25
CONFIG_BAYCOM_SER_FDX
This is one of two drivers for Baycom style simple amateur radio
modems that connect to a serial interface. The driver supports the
ser12 design in full-duplex mode. In addition, it allows the
baudrate to be set between 300 and 4800 baud (however not all modems
support all baudrates). This is the preferred driver. The next
driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
driver and still provided in case this driver does not work with
your serial interface chip. To configure the driver, use the sethdlc
utility available in the standard ax25 utilities package. For
information on the modems, see <http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_ser_fdx.o.
BAYCOM ser12 half-duplex driver for AX.25
CONFIG_BAYCOM_SER_HDX
This is one of two drivers for Baycom style simple amateur radio
modems that connect to a serial interface. The driver supports the
ser12 design in full-duplex mode. This is the old driver. It is
still provided in case your serial interface chip does not work with
the full-duplex driver. This driver is depreciated. To configure
the driver, use the sethdlc utility available in the standard ax25
utilities package. For information on the modems, see
<http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_ser_hdx.o.
Sound card modem driver for AX.25
CONFIG_SOUNDMODEM
This experimental driver allows a standard Sound Blaster or
WindowsSoundSystem compatible sound card to be used as a packet
radio modem (NOT as a telephone modem!), to send digital traffic
over amateur radio.
To configure the driver, use the sethdlc, smdiag and smmixer
utilities available in the standard ax25 utilities package. For
information on how to key the transmitter, see
<http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
<file:Documentation/networking/soundmodem.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called soundmodem.o.
Sound card modem support for Sound Blaster and compatible cards
CONFIG_SOUNDMODEM_SBC
This option enables the soundmodem driver to use Sound Blaster and
compatible cards. If you have a dual mode card (i.e. a WSS cards
with a Sound Blaster emulation) you should say N here and Y to
"Sound card modem support for WSS and Crystal cards", below, because
this usually results in better performance. This option also
supports SB16/32/64 in full-duplex mode.
Sound card modem support for WSS and Crystal cards
CONFIG_SOUNDMODEM_WSS
This option enables the soundmodem driver to use WindowsSoundSystem
compatible cards. These cards feature a codec chip from either
Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
Semiconductors (such as CS4248, CS423x). This option also supports
the WSS full-duplex operation which currently works with Crystal
CS423x chips. If you don't need full-duplex operation, do not enable
it to save performance.
Sound card modem support for 1200 baud AFSK modulation
CONFIG_SOUNDMODEM_AFSK1200
This option enables the soundmodem driver 1200 baud AFSK modem,
compatible to popular modems using TCM3105 or AM7911. The
demodulator requires about 12% of the CPU power of a Pentium 75 CPU
per channel.
Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
CONFIG_SOUNDMODEM_AFSK2400_7
This option enables the soundmodem driver 2400 baud AFSK modem,
compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
crystal. Note that the availability of this driver does _not_ imply
that I recommend building such links. It is only here since users
especially in eastern Europe have asked me to do so. In fact this
modulation scheme has many disadvantages, mainly its incompatibility
with many transceiver designs and the fact that the TCM3105 (if
used) is operated widely outside its specifications.
Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
CONFIG_SOUNDMODEM_AFSK2400_8
This option enables the soundmodem driver 2400 baud AFSK modem,
compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
Note that the availability of this driver does _not_ imply that I
recommend building such links. It is only here since users
especially in eastern Europe have asked me to do so. In fact this
modulation scheme has many disadvantages, mainly its incompatibility
with many transceiver designs and the fact that the TCM3105 (if
used) is operated widely outside its specifications.
Sound card modem support for 2666 baud AFSK modulation
CONFIG_SOUNDMODEM_AFSK2666
This option enables the soundmodem driver 2666 baud AFSK modem.
This modem is experimental, and not compatible to anything
else I know of.
Sound card modem support for 4800 baud 8PSK modulation
CONFIG_SOUNDMODEM_PSK4800
This option enables the soundmodem driver 4800 baud 8PSK modem.
This modem is experimental, and not compatible to anything
else I know of.
Sound card modem support for 4800 baud HAPN-1 modulation
CONFIG_SOUNDMODEM_HAPN4800
This option enables the soundmodem driver 4800 baud HAPN-1
compatible modem. This modulation seems to be widely used 'down
under' and in the Netherlands. Here, nobody uses it, so I could not
test if it works. It is compatible to itself, however :-)
Sound card modem support for 9600 baud FSK G3RUH modulation
CONFIG_SOUNDMODEM_FSK9600
This option enables the soundmodem driver 9600 baud FSK modem,
compatible to the G3RUH standard. The demodulator requires about 4%
of the CPU power of a Pentium 75 CPU per channel. You can say Y to
both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
can only use one protocol at a time, depending on what the other end
can understand).
CCITT X.25 Packet Layer
CONFIG_X25
X.25 is a set of standardized network protocols, similar in scope to
frame relay; the one physical line from your box to the X.25 network
entry point can carry several logical point-to-point connections
(called "virtual circuits") to other computers connected to the X.25
network. Governments, banks, and other organizations tend to use it
to connect to each other or to form Wide Area Networks (WANs). Many
countries have public X.25 networks. X.25 consists of two
protocols: the higher level Packet Layer Protocol (PLP) (say Y here
if you want that) and the lower level data link layer protocol LAPB
(say Y to "LAPB Data Link Driver" below if you want that).
You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
<http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
Information about X.25 for Linux is contained in the files
<file:Documentation/networking/x25.txt> and
<file:Documentation/networking/x25-iface.txt>.
One connects to an X.25 network either with a dedicated network card
using the X.21 protocol (not yet supported by Linux) or one can do
X.25 over a standard telephone line using an ordinary modem (say Y
to "X.25 async driver" below) or over Ethernet using an ordinary
Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
and "LAPB over Ethernet driver" below).
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called x25.o. If unsure, say N.
LAPB Data Link Driver
CONFIG_LAPB
Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
the lower) part of the X.25 protocol. It offers a reliable
connection service to exchange data frames with one other host, and
it is used to transport higher level protocols (mostly X.25 Packet
Layer, the higher part of X.25, but others are possible as well).
Usually, LAPB is used with specialized X.21 network cards, but Linux
currently supports LAPB only over Ethernet connections. If you want
to use LAPB connections over Ethernet, say Y here and to "LAPB over
Ethernet driver" below. Read
<file:Documentation/networking/lapb-module.txt> for technical
details.
If you want to compile this driver as a module though ( = code which
can be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called lapb.o. If unsure, say N.
802.2 LLC
CONFIG_LLC
This is a Logical Link Layer protocol used for X.25 connections over
Ethernet, using ordinary Ethernet cards.
Frame Diverter
CONFIG_NET_DIVERT
The Frame Diverter allows you to divert packets from the
network, that are not aimed at the interface receiving it (in
promisc. mode). Typically, a Linux box setup as an Ethernet bridge
with the Frames Diverter on, can do some *really* transparent www
caching using a Squid proxy for example.
This is very useful when you don't want to change your router's
config (or if you simply don't have access to it).
The other possible usages of diverting Ethernet Frames are
numberous:
- reroute smtp traffic to another interface
- traffic-shape certain network streams
- transparently proxy smtp connections
- etc...
For more informations, please refer to:
<http://diverter.sourceforge.net/>
<http://perso.wanadoo.fr/magpie/EtherDivert.html>
If unsure, say N.
802.1d Ethernet Bridging
CONFIG_BRIDGE
If you say Y here, then your Linux box will be able to act as an
Ethernet bridge, which means that the different Ethernet segments it
is connected to will appear as one Ethernet to the participants.
Several such bridges can work together to create even larger
networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
As this is a standard, Linux bridges will cooperate properly with
other third party bridge products.
In order to use the Ethernet bridge, you'll need the bridge
configuration tools; see <file:Documentation/networking/bridge.txt>
for location. Please read the Bridge mini-HOWTO for more
information.
Note that if your box acts as a bridge, it probably contains several
Ethernet devices, but the kernel is not able to recognize more than
one at boot time without help; for details read the Ethernet-HOWTO,
available from in <http://www.tldp.org/docs.html#howto>.
If you want to compile this code as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called bridge.o.
If unsure, say N.
Packet socket
CONFIG_PACKET
The Packet protocol is used by applications which communicate
directly with network devices without an intermediate network
protocol implemented in the kernel, e.g. tcpdump. If you want them
to work, choose Y.
This driver is also available as a module called af_packet.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>; if you use modprobe
or kmod, you may also want to add "alias net-pf-17 af_packet" to
/etc/modules.conf.
If unsure, say Y.
Packet socket: mmapped IO
CONFIG_PACKET_MMAP
If you say Y here, the Packet protocol driver will use an IO
mechanism that results in faster communication.
If unsure, say N.
Netlink device emulation
CONFIG_NETLINK_DEV
This option will be removed soon. Any programs that want to use
character special nodes like /dev/tap0 or /dev/route (all with major
number 36) need this option, and need to be rewritten soon to use
the real netlink socket.
This is a backward compatibility option, choose Y for now.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
netlink_dev.o
Asynchronous Transfer Mode (ATM)
CONFIG_ATM
ATM is a high-speed networking technology for Local Area Networks
and Wide Area Networks. It uses a fixed packet size and is
connection oriented, allowing for the negotiation of minimum
bandwidth requirements.
In order to participate in an ATM network, your Linux box needs an
ATM networking card. If you have that, say Y here and to the driver
of your ATM card below.
Note that you need a set of user-space programs to actually make use
of ATM. See the file <file:Documentation/networking/atm.txt> for
further details.
Classical IP over ATM
CONFIG_ATM_CLIP
Classical IP over ATM for PVCs and SVCs, supporting InARP and
ATMARP. If you want to communication with other IP hosts on your ATM
network, you will typically either say Y here or to "LAN Emulation
(LANE)" below.
Do NOT send ICMP if no neighbour
CONFIG_ATM_CLIP_NO_ICMP
Normally, an "ICMP host unreachable" message is sent if a neighbour
cannot be reached because there is no VC to it in the kernel's
ATMARP table. This may cause problems when ATMARP table entries are
briefly removed during revalidation. If you say Y here, packets to
such neighbours are silently discarded instead.
RFC1483/2684 Bridged protocols
CONFIG_ATM_BR2684
ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
This device will act like an ethernet from the kernels point of view,
with the traffic being carried by ATM PVCs (currently 1 PVC/device).
This is sometimes used over DSL lines. If in doubt, say N.
Per-VC IP filter kludge
CONFIG_ATM_BR2684_IPFILTER
This is an experimental mechanism for users who need to terminating a
large number of IP-only vcc's. Do not enable this unless you are sure
you know what you are doing.
LAN Emulation (LANE) support
CONFIG_ATM_LANE
LAN Emulation emulates services of existing LANs across an ATM
network. Besides operating as a normal ATM end station client, Linux
LANE client can also act as an proxy client bridging packets between
ELAN and Ethernet segments. You need LANE if you want to try MPOA.
Multi-Protocol Over ATM (MPOA) support
CONFIG_ATM_MPOA
Multi-Protocol Over ATM allows ATM edge devices such as routers,
bridges and ATM attached hosts establish direct ATM VCs across
subnetwork boundaries. These shortcut connections bypass routers
enhancing overall network performance.
ATM over TCP
CONFIG_ATM_TCP
ATM over TCP driver. Useful mainly for development and for
experiments. If unsure, say N.
Efficient Networks ENI155P
CONFIG_ATM_ENI
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.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called eni.o.
Enable extended debugging
CONFIG_ATM_ENI_DEBUG
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.
Fine-tune burst settings
CONFIG_ATM_ENI_TUNE_BURST
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.
Enable 16W TX bursts (discouraged)
CONFIG_ATM_ENI_BURST_TX_16W
Burst sixteen words at once in the send direction. This may work
with recent PCI chipsets, but is known to fail with older chipsets.
Enable 8W TX bursts (recommended)
CONFIG_ATM_ENI_BURST_TX_8W
Burst eight words at once in the send direction. This is the default
setting.
Enable 4W TX bursts (optional)
CONFIG_ATM_ENI_BURST_TX_4W
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.
Enable 2W TX bursts (optional)
CONFIG_ATM_ENI_BURST_TX_2W
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.
Enable 16W RX bursts (discouraged)
CONFIG_ATM_ENI_BURST_RX_16W
Burst sixteen words at once in the receive direction. This may work
with recent PCI chipsets, but is known to fail with older chipsets.
Enable 8W RX bursts (discouraged)
CONFIG_ATM_ENI_BURST_RX_8W
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.
Enable 4W RX bursts (recommended)
CONFIG_ATM_ENI_BURST_RX_4W
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.
Enable 2W RX bursts (optional)
CONFIG_ATM_ENI_BURST_RX_2W
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.
ZeitNet ZN1221/ZN1225
CONFIG_ATM_ZATM
Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
adapters.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called zatm.o.
Enable extended debugging
CONFIG_ATM_ZATM_DEBUG
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.
Fujitsu FireStream (FS50/FS155)
CONFIG_ATM_FIRESTREAM
Driver for the Fujitsu FireStream 155 (MB86697) and
FireStream 50 (MB86695) ATM PCI chips.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
firestream.o.
Enable usec resolution timestamps
CONFIG_ATM_ZATM_EXACT_TS
The uPD98401 SAR chip supports a high-resolution timer (approx. 30
MHz) that is used for very accurate reception timestamps. Because
that timer overflows after 140 seconds, and also to avoid timer
drift, time measurements need to be periodically synchronized with
the normal system time. Enabling this feature will add some general
overhead for timer synchronization and also per-packet overhead for
time conversion.
IDT 77201/11 (NICStAR) (ForeRunnerLE)
CONFIG_ATM_NICSTAR
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.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
nicstar.o.
Use suni PHY driver (155Mbps)
CONFIG_ATM_NICSTAR_USE_SUNI
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).
Use IDT77015 PHY driver (25Mbps)
CONFIG_ATM_NICSTAR_USE_IDT77105
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.
IDT 77252 (NICStAR II)
CONFIG_ATM_IDT77252
Driver for the IDT 77252 ATM PCI chips.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called idt77252.o
Enable debugging messages
CONFIG_ATM_IDT77252_DEBUG
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.
Receive ALL cells in raw queue
CONFIG_ATM_IDT77252_RCV_ALL
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.
Madge Ambassador (Collage PCI 155 Server)
CONFIG_ATM_AMBASSADOR
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.o)
here if you have one of these cards.
Enable debugging messages
CONFIG_ATM_AMBASSADOR_DEBUG
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.
Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
CONFIG_ATM_HORIZON
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.o) here if you have one of these cards.
Enable debugging messages
CONFIG_ATM_HORIZON_DEBUG
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.
Interphase ATM PCI x575/x525/x531
CONFIG_ATM_IA
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:
<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
for more info about the cards. Say Y (or M to compile as a module
named iphase.o) here if you have one of these cards.
See the file <file:Documentation/networking/iphase.txt> for further
details.
Enable debugging messages
CONFIG_ATM_IA_DEBUG
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.
Efficient Networks Speedstream 3010
CONFIG_ATM_LANAI
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).
Linux telephony support
CONFIG_PHONE
Say Y here if you have a telephony card, which for example allows
you to use a regular phone for voice-over-IP applications.
Note: this has nothing to do with modems. You do not need to say Y
here in order to be able to use a modem under Linux.
This support is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
phonedev.o.
Compaq Smart Array support
CONFIG_BLK_CPQ_CISS_DA
This is the driver for Compaq Smart Array 5xxx controllers.
Everyone using these boards should say Y here.
See <file:Documentation/cciss.txt> for the current list of
boards supported by this driver, and for further information
on the use of this driver.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
cciss.o
SCSI tape drive support for Smart Array 5xxx
CONFIG_CISS_SCSI_TAPE
When enabled (Y), this option allows SCSI tape drives and SCSI medium
changers (tape robots) to be accessed via a Compaq 5xxx array
controller. (See Documentation/cciss.txt for more details.)
"SCSI support" and "SCSI tape support" must also be enabled for this
option to work.
When this option is disabled (N), the SCSI portion of the driver
is not compiled.
QuickNet Internet LineJack/PhoneJack support
CONFIG_PHONE_IXJ
Say M if you have a telephony card manufactured by Quicknet
Technologies, Inc. These include the Internet PhoneJACK and
Internet LineJACK Telephony Cards. You will get a module called
ixj.o.
For the ISA versions of these products, you can configure the
cards using the isapnp tools (pnpdump/isapnp) or you can use the
isapnp support. Please read <file:Documentation/telephony/ixj.txt>.
For more information on these cards, see Quicknet's web site at:
<http://www.quicknet.net/>.
If you do not have any Quicknet telephony cards, you can safely
say N here.
QuickNet Internet LineJack/PhoneJack PCMCIA support
CONFIG_PHONE_IXJ_PCMCIA
Say Y here to configure in PCMCIA service support for the Quicknet
cards manufactured by Quicknet Technologies, Inc. This builds an
additional support module for the PCMCIA version of the card.
FORE Systems 200E-series
CONFIG_ATM_FORE200E_MAYBE
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.o) here if you have one of these ATM adapters.
Note that the driver will actually be compiled only if you
additionally enable the support for PCA-200E and/or SBA-200E
cards.
See the file <file:Documentation/networking/fore200e.txt> for
further details.
Enable PCA-200E card support on PCI-based hosts
CONFIG_ATM_FORE200E_PCA
Say Y here if you want your PCA-200E cards to be probed.
Use default PCA-200E firmware
CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
Use the default PCA-200E firmware data shipped with the driver.
Normal users do not have to deal with the firmware stuff, so
they should say Y here.
Pathname of user-supplied binary firmware
CONFIG_ATM_FORE200E_PCA_FW
This defines the pathname of an alternative PCA-200E binary
firmware image supplied by the user. This pathname may be
absolute or relative to the drivers/atm directory.
The driver comes with an adequate firmware image, so normal users do
not have to supply an alternative one. They just say Y to "Use
default PCA-200E firmware" instead.
Enable SBA-200E card support on SBUS-based hosts
CONFIG_ATM_FORE200E_SBA
Say Y here if you want your SBA-200E cards to be probed.
Use default SBA-200E firmware
CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
Use the default SBA-200E firmware data shipped with the driver.
Normal users do not have to deal with the firmware stuff, so
they should say Y here.
Pathname of user-supplied binary firmware
CONFIG_ATM_FORE200E_SBA_FW
This defines the pathname of an alternative SBA-200E binary
firmware image supplied by the user. This pathname may be
absolute or relative to the drivers/atm directory.
The driver comes with an adequate firmware image, so normal users do
not have to supply an alternative one. They just say Y to "Use
default SBA-200E firmware", above.
Maximum number of tx retries
CONFIG_ATM_FORE200E_TX_RETRY
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.
Debugging level (0-3)
CONFIG_ATM_FORE200E_DEBUG
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.
PPP over ATM
CONFIG_PPPOATM
Support PPP (Point to Point Protocol) encapsulated in ATM frames.
This implementation does not yet comply with section 8 of RFC2364,
which can lead to bad results idf the ATM peer loses state and
changes its encapsulation unilaterally.
Fusion MPT device support
CONFIG_FUSION
LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
provides high performance SCSI host initiator, and LAN [1] interface
services to a host system. The Fusion architecture is capable of
duplexing these protocols on high-speed Fibre Channel
(up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
physical medium.
[1] LAN is not supported on parallel SCSI medium.
These drivers require a Fusion MPT compatible PCI adapter installed
in the host system. MPT adapters contain specialized I/O processors
to handle I/O workload, and more importantly to offload this work
from the host CPU(s).
If you have Fusion MPT hardware and want to use it, you can say
Y or M here to add MPT (base + ScsiHost) drivers.
<Y> = build lib (fusion.o), and link [static] into the kernel [2]
proper
<M> = compiled as [dynamic] modules [3] named: (mptbase.o,
mptscsih.o)
[2] In order enable capability to boot the linux kernel
natively from a Fusion MPT target device, you MUST
answer Y here! (currently requires CONFIG_BLK_DEV_SD)
[3] This support is also available as a module ( = code
which can be inserted in and removed from the running
kernel whenever you want). If you want to compile as
modules, say M here and read
<file:Documentation/modules.txt>.
If unsure, say N.
If you say Y or M here you will get a choice of these
additional protocol and support module options: Module Name:
<M> Enhanced SCSI error reporting (isense.o)
<M> Fusion MPT misc device (ioctl) driver (mptctl.o)
<M> Fusion MPT LAN driver (mptlan.o)
---
Fusion MPT is trademark of LSI Logic Corporation, and its
architecture is based on LSI Logic's Message Passing Interface (MPI)
specification.
Fusion MPT enhanced SCSI error reporting [optional] module
CONFIG_FUSION_ISENSE
The isense module (roughly stands for Interpret SENSE data) is
completely optional. It simply provides extra English readable
strings in SCSI Error Report(s) that might be generated from the
Fusion MPT SCSI Host driver, for example when a target device
returns a SCSI check condition on a I/O. Without this module
loaded you might see:
SCSI Error Report =-=-= (ioc0,scsi5:0)
SCSI_Status=02h (CHECK_CONDITION)
Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
SenseKey=2h (NOT READY); FRU=02h
ASC/ASCQ=29h/00h
Where otherwise, if this module had been loaded, you would see:
SCSI Error Report =-=-= (ioc0,scsi5:0)
SCSI_Status=02h (CHECK_CONDITION)
Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
SenseKey=2h (NOT READY); FRU=02h
ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
Say M for "Enhanced SCSI error reporting" to compile this optional module,
creating a driver named: isense.o.
NOTE: Support for building this feature into the kernel is not
available, due to kernel size considerations.
Fusion MPT misc device (ioctl) driver [optional] module
CONFIG_FUSION_CTL
The Fusion MPT misc device driver provides specialized control
of MPT adapters via system ioctl calls. Use of ioctl calls to
the MPT driver requires that you create and use a misc device
node ala:
mknod /dev/mptctl c 10 240
One use of this ioctl interface is to perform an upgrade (reflash)
of the MPT adapter firmware. Refer to readme file(s) distributed
with the Fusion MPT linux driver for additional details.
If enabled by saying M to this, a driver named: mptctl.o
will be compiled.
If unsure whether you really want or need this, say N.
Fusion MPT LAN driver [optional]
CONFIG_FUSION_LAN
This module supports LAN IP traffic over Fibre Channel port(s)
on Fusion MPT compatible hardware (LSIFC9xx chips).
The physical interface used is defined in RFC 2625.
Please refer to that document for details.
Installing this driver requires the knowledge to configure and
activate a new network interface, "fc0", using standard Linux tools.
If enabled by saying M to this, a driver named: mptlan.o
will be compiled.
If unsure whether you really want or need this, say N.
NOTES: This feature is NOT available nor supported for linux-2.2.x
kernels. You must be building a linux-2.3.x or linux-2.4.x kernel
in order to configure this option.
Support for building this feature into the linux kernel is not
yet available.
SCSI support
CONFIG_SCSI
If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
any other SCSI device under Linux, say Y and make sure that you know
the name of your SCSI host adapter (the card inside your computer
that "speaks" the SCSI protocol, also called SCSI controller),
because you will be asked for it.
You also need to say Y here if you want support for the parallel
port version of the 100 MB IOMEGA ZIP drive.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called scsi_mod.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>. However, do not compile this as a
module if your root file system (the one containing the directory /)
is located on a SCSI device.
SCSI disk support
CONFIG_BLK_DEV_SD
If you want to use a SCSI hard disk or the SCSI or parallel port
version of the IOMEGA ZIP drive under Linux, say Y and read the
SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sd_mod.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>. Do not compile this driver as a
module if your root file system (the one containing the directory /)
is located on a SCSI disk. In this case, do not compile the driver
for your SCSI host adapter (below) as a module either.
Maximum number of SCSI disks that can be loaded as modules
CONFIG_SD_EXTRA_DEVS
This controls the amount of additional space allocated in tables for
drivers that are loaded as modules after the kernel is booted. In
the event that the SCSI core itself was loaded as a module, this
value is the number of additional disks that can be loaded after the
first host driver is loaded.
Admittedly this isn't pretty, but there are tons of race conditions
involved with resizing the internal arrays on the fly. Someday this
flag will go away, and everything will work automatically.
If you don't understand what's going on, go with the default.
Maximum number of SCSI tapes that can be loaded as modules
CONFIG_ST_EXTRA_DEVS
This controls the amount of additional space allocated in tables for
drivers that are loaded as modules after the kernel is booted. In
the event that the SCSI core itself was loaded as a module, this
value is the number of additional tapes that can be loaded after the
first host driver is loaded.
Admittedly this isn't pretty, but there are tons of race conditions
involved with resizing the internal arrays on the fly. Someday this
flag will go away, and everything will work automatically.
If you don't understand what's going on, go with the default.
SCSI tape support
CONFIG_CHR_DEV_ST
If you want to use a SCSI tape drive under Linux, say Y and read the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and
<file:drivers/scsi/README.st> in the kernel source. This is NOT for
SCSI CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called st.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>.
OnStream SC-x0 SCSI tape support
CONFIG_CHR_DEV_OSST
The OnStream SC-x0 SCSI tape drives can not be driven by the
standard st driver, but instead need this special osst driver and
use the /dev/osstX char device nodes (major 206). Via usb-storage
and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
as well. Note that there is also a second generation of OnStream
tape drives (ADR-x0) that supports the standard SCSI-2 commands for
tapes (QIC-157) and can be driven by the standard driver st.
For more information, you may have a look at the SCSI-HOWTO
<http://www.tldp.org/docs.html#howto> and
<file:drivers/scsi/README.osst> in the kernel source.
More info on the OnStream driver may be found on
<http://linux1.onstream.nl/test/>
Please also have a look at the standard st docu, as most of it
applies to osst as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called osst.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>.
SCSI CD-ROM support
CONFIG_BLK_DEV_SR
If you want to use a SCSI CD-ROM under Linux, say Y and read the
SCSI-HOWTO and the CD-ROM-HOWTO at
<http://www.tldp.org/docs.html#howto>. Also make sure to say Y
or M to "ISO 9660 CD-ROM file system support" later.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sr_mod.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>.
Maximum number of CD-ROM devices that can be loaded as modules
CONFIG_SR_EXTRA_DEVS
This controls the amount of additional space allocated in tables for
drivers that are loaded as modules after the kernel is booted. In
the event that the SCSI core itself was loaded as a module, this
value is the number of additional CD-ROMs that can be loaded after
the first host driver is loaded.
Admittedly this isn't pretty, but there are tons of race conditions
involved with resizing the internal arrays on the fly. Someday this
flag will go away, and everything will work automatically.
If you don't understand what's going on, go with the default.
Enable vendor-specific extensions (for SCSI CD-ROM)
CONFIG_BLK_DEV_SR_VENDOR
This enables the usage of vendor specific SCSI commands. This is
required to support multisession CDs with old NEC/TOSHIBA cdrom
drives (and HP Writers). If you have such a drive and get the first
session only, try saying Y here; everybody else says N.
SCSI generic support
CONFIG_CHR_DEV_SG
If you want to use SCSI scanners, synthesizers or CD-writers or just
about anything having "SCSI" in its name other than hard disks,
CD-ROMs or tapes, say Y here. These won't be supported by the kernel
directly, so you need some additional software which knows how to
talk to these devices using the SCSI protocol:
For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
writer software look at Cdrtools
(<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
and for burning a "disk at once": CDRDAO
(<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
For other devices, it's possible that you'll have to write the
driver software yourself. Please read the file
<file:Documentation/scsi-generic.txt> for more information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt> and
<file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
say N.
Probe all LUNs on each SCSI device
CONFIG_SCSI_MULTI_LUN
If you have a SCSI device that supports more than one LUN (Logical
Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
can say Y here to force the SCSI driver to probe for multiple LUNs.
A SCSI device with multiple LUNs acts logically like multiple SCSI
devices. The vast majority of SCSI devices have only one LUN, and
so most people can say N here and should in fact do so, because it
is safer.
Verbose SCSI error reporting (kernel size +=12K)
CONFIG_SCSI_CONSTANTS
The error messages regarding your SCSI hardware will be easier to
understand if you say Y here; it will enlarge your kernel by about
12 KB. If in doubt, say Y.
SCSI logging facility
CONFIG_SCSI_LOGGING
This turns on a logging facility that can be used to debug a number
of SCSI related problems.
If you say Y here, no logging output will appear by default, but you
can enable logging by saying Y to "/proc file system support" and
"Sysctl support" below and executing the command
echo "scsi log token [level]" > /proc/scsi/scsi
at boot time after the /proc file system has been mounted.
There are a number of things that can be used for 'token' (you can
find them in the source: <file:drivers/scsi/scsi.c>), and this
allows you to select the types of information you want, and the
level allows you to select the level of verbosity.
If you say N here, it may be harder to track down some types of SCSI
problems. If you say Y here your kernel will be somewhat larger, but
there should be no noticeable performance impact as long as you have
logging turned off.
SGI WD93C93 SCSI Driver
CONFIG_SCSI_SGIWD93
Say Y here to support the on-board WD93C93 SCSI controller found (a)
on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
ARM-based machines.
DEC NCR53C94 SCSI Driver
CONFIG_SCSI_DECNCR
Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
AdvanSys SCSI support
CONFIG_SCSI_ADVANSYS
This is a driver for all SCSI host adapters manufactured by
AdvanSys. It is documented in the kernel source in
<file:drivers/scsi/advansys.c>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
advansys.o.
Adaptec AHA152X/2825 support
CONFIG_SCSI_AHA152X
This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
must be manually specified in this case.
It is explained in section 3.3 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. You might also want to
read the file <file:drivers/scsi/README.aha152x>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called aha152x.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Adaptec AHA1542 support
CONFIG_SCSI_AHA1542
This is support for a SCSI host adapter. It is explained in section
3.4 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. Note that Trantor was
purchased by Adaptec, and some former Trantor products are being
sold under the Adaptec name. If it doesn't work out of the box, you
may have to change some settings in <file:drivers/scsi/aha1542.h>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called aha1542.o.
Adaptec AHA1740 support
CONFIG_SCSI_AHA1740
This is support for a SCSI host adapter. It is explained in section
3.5 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/aha1740.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called aha1740.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Adaptec AIC7xxx support
CONFIG_SCSI_AIC7XXX
This driver supports all of Adaptec's PCI based SCSI controllers
(not the hardware RAID controllers though) as well as the aic7770
based EISA and VLB SCSI controllers (the 274x and 284x series).
This is an Adaptec sponsored driver written by Justin Gibbs. It is
intended to replace the previous aic7xxx driver maintained by Doug
Ledford since Doug is no longer maintaining that driver.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called aic7xxx.o.
Adaptec I2O RAID support
CONFIG_SCSI_DPT_I2O
This driver supports all of Adaptec's I2O based RAID controllers as
well as the DPT SmartRaid V cards. This is an Adaptec maintained
driver by Deanna Bonds. See <file:drivers/scsi/README.dpti>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
dpt_i2o.o.
Default number of TCQ commands per device
CONFIG_AIC7XXX_CMDS_PER_DEVICE
Specify the number of commands you would like to allocate per SCSI
device when Tagged Command Queueing (TCQ) is enabled on that device.
This is an upper bound value for the number of tagged transactions
to be used for any device. The aic7xxx driver will automatically
vary this number based on device behaviour. For devices with a
fixed maximum, the driver will eventually lock to this maximum
and display a console message indicating this value.
Note: Unless you experience some type of device failure, the default
value, no enforced limit, should work for you.
Default: 253
Delay in seconds after SCSI bus reset
CONFIG_AIC7XXX_RESET_DELAY_MS
The number of milliseconds to delay after an initial bus reset.
The bus settle delay following all error recovery actions is
dictated by the SCSI layer and is not affected by this value.
Default: 15000 (15 seconds)
Build Adapter Firmware with Kernel Build
CONFIG_AIC7XXX_BUILD_FIRMWARE
This option should only be enabled if you are modifying the firmware
source to the aic7xxx driver and wish to have the generated firmware
include files updated during a normal kernel build. The assembler
for the firmware requires lex and yacc or their equivalents, as well
as the db v1 library. You may have to install additional packages
or modify the assembler make file or the files it includes if your
build environment is different than that of the author.
Old Adaptec AIC7xxx support
CONFIG_SCSI_AIC7XXX_OLD
WARNING This driver is an older aic7xxx driver and is no longer
under active development. Adaptec, Inc. is writing a new driver to
take the place of this one, and it is recommended that whenever
possible, people should use the new Adaptec written driver instead
of this one. This driver will eventually be phased out entirely.
This is support for the various aic7xxx based Adaptec SCSI
controllers. These include the 274x EISA cards; 284x VLB cards;
2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
motherboard based SCSI controllers from Adaptec. It does not support
the AAA-13x RAID controllers from Adaptec, nor will it likely ever
support them. It does not support the 2920 cards from Adaptec that
use the Future Domain SCSI controller chip. For those cards, you
need the "Future Domain 16xx SCSI support" driver.
In general, if the controller is based on an Adaptec SCSI controller
chip from the aic777x series or the aic78xx series, this driver
should work. The only exception is the 7810 which is specifically
not supported (that's the RAID controller chip on the AAA-13x
cards).
Note that the AHA2920 SCSI host adapter is *not* supported by this
driver; choose "Future Domain 16xx SCSI support" instead if you have
one of those.
Information on the configuration options for this controller can be
found by checking the help file for each of the available
configuration options. You should read
<file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
contacting the maintainer with any questions. The SCSI-HOWTO,
available from <http://www.tldp.org/docs.html#howto>, can also
be of great help.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called aic7xxx_old.o.
Enable tagged command queueing (TCQ) by default
CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
This option causes the aic7xxx driver to attempt to use Tagged
Command Queueing (TCQ) on all devices that claim to support it.
TCQ is a feature of SCSI-2 which improves performance: the host
adapter can send several SCSI commands to a device's queue even if
previous commands haven't finished yet. Because the device is
intelligent, it can optimize its operations (like head positioning)
based on its own request queue. Not all devices implement this
correctly.
If you say Y here, you can still turn off TCQ on troublesome devices
with the use of the tag_info boot parameter. See the file
<file:drivers/scsi/README.aic7xxx> for more information on that and
other aic7xxx setup commands. If this option is turned off, you may
still enable TCQ on known good devices by use of the tag_info boot
parameter.
If you are unsure about your devices then it is safest to say N
here.
However, TCQ can increase performance on some hard drives by as much
as 50% or more, so it is recommended that if you say N here, you
should at least read the <file:drivers/scsi/README.aic7xxx> file so
you will know how to enable this option manually should your drives
prove to be safe in regards to TCQ.
Conversely, certain drives are known to lock up or cause bus resets
when TCQ is enabled on them. If you have a Western Digital
Enterprise SCSI drive for instance, then don't even bother to enable
TCQ on it as the drive will become unreliable, and it will actually
reduce performance.
Default number of TCQ commands per device
CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
Specify the number of commands you would like to allocate per SCSI
device when Tagged Command Queueing (TCQ) is enabled on that device.
Reasonable figures are in the range of 8 to 24 commands per device,
but depending on hardware could be increased or decreased from that
figure. If the number is too high for any particular device, the
driver will automatically compensate usually after only 10 minutes
of uptime. It will not hinder performance if some of your devices
eventually have their command depth reduced, but is a waste of
memory if all of your devices end up reducing this number down to a
more reasonable figure.
NOTE: Certain very broken drives are known to lock up when given
more commands than they like to deal with. Quantum Fireball drives
are the most common in this category. For the Quantum Fireball
drives it is suggested to use no more than 8 commands per device.
Default: 8
Collect statistics to report in /proc
CONFIG_AIC7XXX_OLD_PROC_STATS
This option tells the driver to keep track of how many commands have
been sent to each particular device and report that information to
the user via the /proc/scsi/aic7xxx/n file, where n is the number of
the aic7xxx controller you want the information on. This adds a
small amount of overhead to each and every SCSI command the aic7xxx
driver handles, so if you aren't really interested in this
information, it is best to leave it disabled. This will only work if
you also say Y to "/proc file system support", below.
If unsure, say N.
IBM ServeRAID support
CONFIG_SCSI_IPS
This is support for the IBM ServeRAID hardware RAID controllers.
See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
for more information. If this driver does not work correctly
without modification please contact the author by email at
ipslinux@us.ibm.com.
You can build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
but only a single instance may be loaded. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
The module will be called ips.o.
BusLogic SCSI support
CONFIG_SCSI_BUSLOGIC
This is support for BusLogic MultiMaster and FlashPoint SCSI Host
Adapters. Consult the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and the files
<file:drivers/scsi/README.BusLogic> and
<file:drivers/scsi/README.FlashPoint> for more information. If this
driver does not work correctly without modification, please contact
the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
You can also build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
but only a single instance may be loaded. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
The module will be called BusLogic.o.
Omit BusLogic SCSI FlashPoint support
CONFIG_SCSI_OMIT_FLASHPOINT
This option allows you to omit the FlashPoint support from the
BusLogic SCSI driver. The FlashPoint SCCB Manager code is
substantial, so users of MultiMaster Host Adapters may wish to omit
it.
Compaq Fibre Channel 64-bit/66Mhz HBA support
CONFIG_SCSI_CPQFCTS
Say Y here to compile in support for the Compaq StorageWorks Fibre
Channel 64-bit/66Mhz Host Bus Adapter.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called cpqfc.o.
DMX3191D SCSI support
CONFIG_SCSI_DMX3191D
This is support for Domex DMX3191D SCSI Host Adapters.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dmx3191d.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
DTC3180/3280 SCSI support
CONFIG_SCSI_DTC3280
This is support for DTC 3180/3280 SCSI Host Adapters. Please read
the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and the file
<file:drivers/scsi/README.dtc3x80>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dtc.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
CONFIG_SCSI_EATA_DMA
This is support for the EATA-DMA protocol compliant SCSI Host
Adapters like the SmartCache III/IV, SmartRAID controller families
and the DPT PM2011B and PM2012B controllers.
Note that this driver is obsolete; if you have one of the above
SCSI Host Adapters, you should normally say N here and Y to "EATA
ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
from <http://www.tldp.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called eata_dma.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
EATA-PIO (old DPT PM2001, PM2012A) support
CONFIG_SCSI_EATA_PIO
This driver supports all EATA-PIO protocol compliant SCSI Host
Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
host adapters could also use this driver but are discouraged from
doing so, since this driver only supports hard disks and lacks
numerous features. You might want to have a look at the SCSI-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called eata_pio.o.
UltraStor 14F/34F support
CONFIG_SCSI_U14_34F
This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
The source at <file:drivers/scsi/u14-34f.c> contains some
information about this hardware. If the driver doesn't work out of
the box, you may have to change some settings in
<file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. Note that there is also
another driver for the same hardware: "UltraStor SCSI support",
below. You should say Y to both only if you want 24F support as
well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called u14-34f.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
enable elevator sorting
CONFIG_SCSI_U14_34F_LINKED_COMMANDS
This option enables elevator sorting for all probed SCSI disks and
CD-ROMs. It definitely reduces the average seek distance when doing
random seeks, but this does not necessarily result in a noticeable
performance improvement: your mileage may vary...
The safe answer is N.
maximum number of queued commands
CONFIG_SCSI_U14_34F_MAX_TAGS
This specifies how many SCSI commands can be maximally queued for
each probed SCSI device. You should reduce the default value of 8
only if you have disks with buggy or limited tagged command support.
Minimum is 2 and maximum is 14. This value is also the window size
used by the elevator sorting option above. The effective value used
by the driver for each probed SCSI device is reported at boot time.
Future Domain 16xx SCSI/AHA-2920A support
CONFIG_SCSI_FUTURE_DOMAIN
This is support for Future Domain's 16-bit SCSI host adapters
(TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
other adapters based on the Future Domain chipsets (Quantum
ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
It is explained in section 3.7 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
controller support"). This Future Domain driver works with the older
Adaptec AHA-2920A boards with a Future Domain chip on them.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called fdomain.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Future Domain MCS-600/700 SCSI support
CONFIG_SCSI_FD_MCS
This is support for Future Domain MCS 600/700 MCA SCSI adapters.
Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
is identical to the MCS 700 and hence also supported by this driver.
This driver also supports the Reply SB16/SCSI card (the SCSI part).
It supports multiple adapters in the same system.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called fd_mcs.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Generic NCR5380/53c400 SCSI support
CONFIG_SCSI_GENERIC_NCR5380
This is the generic NCR family of SCSI controllers, not to be
confused with the NCR 53c7 or 8xx controllers. It is explained in
section 3.8 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/g_NCR5380.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called g_NCR5380.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Enable NCR53c400 extensions
CONFIG_SCSI_GENERIC_NCR53C400
This enables certain optimizations for the NCR53c400 SCSI cards.
You might as well try it out. Note that this driver will only probe
for the Trantor T130B in its default configuration; you might have
to pass a command line option to the kernel at boot time if it does
not detect your card. See the file
<file:drivers/scsi/README.g_NCR5380> for details.
# Choice: ncr5380
NCR5380/53c400 mapping method (use Port for T130B)
CONFIG_SCSI_G_NCR5380_PORT
The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
port or memory mapped. You should know what you have. The most
common card, Trantor T130B, uses port mapped mode.
NCR Dual 700 MCA SCSI support
CONFIG_SCSI_NCR_D700
This is a driver for the MicroChannel Dual 700 card produced by
NCR and commonly used in 345x/35xx/4100 class machines. It always
tries to negotiate sync and uses tag command queueing.
Unless you have an NCR manufactured machine, the chances are that
you do not have this SCSI card, so say N.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called NCR_D700.o.
HP LASI SCSI support for 53c700/710
CONFIG_SCSI_LASI700
This is a driver for the lasi baseboard in some parisc machines
which is based on the 53c700 chip. Will also support LASI subsystems
based on the 710 chip using 700 emulation mode.
Unless you know you have a 53c700 or 53c710 based lasi, say N here
NCR53c7,8xx SCSI support
CONFIG_SCSI_NCR53C7xx
This is a driver for the 53c7 and 8xx NCR family of SCSI
controllers, not to be confused with the NCR 5380 controllers. It
is explained in section 3.8 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/53c7,8xx.h>. Please read
<file:drivers/scsi/README.ncr53c7xx> for the available boot time
command line options.
Note: there is another driver for the 53c8xx family of controllers
("NCR53C8XX SCSI support" below). If you want to use them both, you
need to say M to both and build them as modules, but only one may be
active at a time. If you have a 53c8xx board, it's better to use the
other driver.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called 53c7,8xx.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Always negotiate synchronous transfers
CONFIG_SCSI_NCR53C7xx_sync
In general, this is good; however, it is a bit dangerous since there
are some broken SCSI devices out there. Take your chances. Safe bet
is N.
Allow FAST-SCSI [10MHz]
CONFIG_SCSI_NCR53C7xx_FAST
This will enable 10MHz FAST-SCSI transfers with your host
adapter. Some systems have problems with that speed, so it's safest
to say N here.
Allow DISCONNECT
CONFIG_SCSI_NCR53C7xx_DISCONNECT
This enables the disconnect/reconnect feature of the NCR SCSI
controller. When you say Y here, a slow SCSI device will not lock
the SCSI bus while processing a request, allowing simultaneous use
of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
providing much better performance when using slow and fast SCSI
devices at the same time. Some devices, however, do not operate
properly with this option enabled, and will cause your SCSI system
to hang, which might cause a system crash. The safe answer
therefore is to say N.
SYM53C8XX Version 2 SCSI support
CONFIG_SCSI_SYM53C8XX_2
This driver supports the whole NCR53C8XX/SYM53C8XX family of
PCI-SCSI controllers. It also supports the subset of LSI53C10XX
Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
controllers.
If your system has problems using this new major version of the
SYM53C8XX driver, you may switch back to driver version 1.
Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
information.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called sym53c8xx.o.
PCI DMA addressing mode
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
This option only applies to PCI-SCSI chip that are PCI DAC capable
(875A, 895A, 896, 1010-33, 1010-66, 1000).
When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
When set to 1, 40 bit DMA addressing (with upper 24 bits of address
set to zero) is supported. The addressable range is here 1 TB.
When set to 2, full 64 bits of address for DMA are supported, but only
16 segments of 4 GB can be addressed. The addressable range is so
limited to 64 GB.
The safest value is 0 (32 bit DMA addressing) that is guessed to still
fit most of real machines.
The preferred value 1 (40 bit DMA addressing) should make happy
properly engineered PCI DAC capable host bridges. You may configure
this option for Intel platforms with more than 4 GB of memory.
The still experimental value 2 (64 bit DMA addressing with 16 x 4GB
segments limitation) can be used on systems that require PCI address
bits past bit 39 to be set for the addressing of memory using PCI
DAC cycles.
use normal IO
CONFIG_SCSI_SYM53C8XX_IOMAPPED
If you say Y here, the driver will preferently use normal IO rather than
memory mapped IO.
maximum number of queued commands
CONFIG_SCSI_SYM53C8XX_MAX_TAGS
This option allows you to specify the maximum number of commands
that can be queued to any device, when tagged command queuing is
possible. The driver supports up to 256 queued commands per device.
This value is used as a compiled-in hard limit.
default tagged command queue depth
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS
This is the default value of the command queue depth the driver will
announce to the generic SCSI layer for devices that support tagged
command queueing. This value can be changed from the boot command line.
This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
NCR53C8XX SCSI support
CONFIG_SCSI_NCR53C8XX
This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
of PCI-SCSI controllers. This driver supports parity checking,
tagged command queuing and fast synchronous data transfers up to 80
MB/s with wide FAST-40 LVD devices and controllers.
Recent versions of the 53C8XX chips are better supported by the
option "SYM53C8XX SCSI support", below.
Note: there is yet another driver for the 53c8xx family of
controllers ("NCR53c7,8xx SCSI support" above). If you want to use
them both, you need to say M to both and build them as modules, but
only one may be active at a time. If you have a 53c8xx board, you
probably do not want to use the "NCR53c7,8xx SCSI support".
Please read <file:drivers/scsi/README.ncr53c8xx> for more
information.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ncr53c8xx.o.
SYM53C8XX Version 1 SCSI support
CONFIG_SCSI_SYM53C8XX
This driver supports all the features of recent 53C8XX chips (used
in PCI SCSI controllers), notably the hardware phase mismatch
feature of the SYM53C896.
Older versions of the 53C8XX chips are not supported by this
driver. If your system uses either a 810 rev. < 16, a 815, or a 825
rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
driver ("NCR53C8XX SCSI support" above) or configure both the
NCR53C8XX and this SYM53C8XX drivers either as module or linked to
the kernel image.
When both drivers are linked into the kernel, the SYM53C8XX driver
is called first at initialization and you can use the 'excl=ioaddr'
driver boot option to exclude attachment of adapters by the
SYM53C8XX driver. For example, entering
'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
adapters at io address 0xb400 and 0xc000 from being attached by the
SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
The 'excl' option is also supported by the NCR53C8XX driver.
Please read <file:drivers/scsi/README.ncr53c8xx> for more
information.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called sym53c8xx.o.
Synchronous transfer frequency in MHz
CONFIG_SCSI_NCR53C8XX_SYNC
The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
are respectively the maximum data transfer rates in mega-transfers
per second for each class. For example, a FAST-20 Wide 16 device is
able to transfer data at 20 million 16 bit packets per second for a
total rate of 40 MB/s.
You may specify 0 if you want to only use asynchronous data
transfers. This is the safest and slowest option. Otherwise, specify
a value between 5 and 80, depending on the capability of your SCSI
controller. The higher the number, the faster the data transfer.
Note that 80 should normally be ok since the driver decreases the
value automatically according to the controller's capabilities.
Your answer to this question is ignored for controllers with NVRAM,
since the driver will get this information from the user set-up. It
also can be overridden using a boot setup option, as follows
(example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
for FAST-20 synchronous data transfer (20 mega-transfers per
second).
The normal answer therefore is not to go with the default but to
select the maximum value 80 allowing the driver to use the maximum
value supported by each controller. If this causes problems with
your SCSI devices, you should come back and decrease the value.
There is no safe option other than using good cabling, right
terminations and SCSI conformant devices.
Use normal IO
CONFIG_SCSI_NCR53C8XX_IOMAPPED
If you say Y here, the driver will use normal IO, as opposed to
memory mapped IO. Memory mapped IO has less latency than normal IO
and works for most Intel-based hardware. Under Linux/Alpha only
normal IO is currently supported by the driver and so, this option
has no effect on those systems.
The normal answer therefore is N; try Y only if you encounter SCSI
related problems.
Not allow targets to disconnect
CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
This option is only provided for safety if you suspect some SCSI
device of yours to not support properly the target-disconnect
feature. In that case, you would say Y here. In general however, to
not allow targets to disconnect is not reasonable if there is more
than 1 device on a SCSI bus. The normal answer therefore is N.
Default tagged command queue depth
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
"Tagged command queuing" is a feature of SCSI-2 which improves
performance: the host adapter can send several SCSI commands to a
device's queue even if previous commands haven't finished yet.
Because the device is intelligent, it can optimize its operations
(like head positioning) based on its own request queue. Some SCSI
devices don't implement this properly; if you want to disable this
feature, enter 0 or 1 here (it doesn't matter which).
The default value is 8 and should be supported by most hard disks.
This value can be overridden from the boot command line using the
'tags' option as follows (example):
'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4, set queue depth to 16 for target 2 and target 3 on controller 0
and set queue depth to 10 for target 0 / lun 2 on controller 1.
The normal answer therefore is to go with the default 8 and to use
a boot command line option for devices that need to use a different
command queue depth.
There is no safe option other than using good SCSI devices.
Maximum number of queued commands
CONFIG_SCSI_NCR53C8XX_MAX_TAGS
This option allows you to specify the maximum number of commands
that can be queued to any device, when tagged command queuing is
possible. The default value is 32. Minimum is 2, maximum is 64.
Modern hard disks are able to support 64 tags and even more, but
do not seem to be faster when more than 32 tags are being used.
So, the normal answer here is to go with the default value 32 unless
you are using very large hard disks with large cache (>= 1 MB) that
are able to take advantage of more than 32 tagged commands.
There is no safe option and the default answer is recommended.
Assume boards are SYMBIOS compatible
CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
This option allows you to enable some features depending on GPIO
wiring. These General Purpose Input/Output pins can be used for
vendor specific features or implementation of the standard SYMBIOS
features. Genuine SYMBIOS controllers use GPIO0 in output for
controller LED and GPIO3 bit as a flag indicating
singled-ended/differential interface. The Tekram DC-390U/F boards
uses a different GPIO wiring.
Your answer to this question is ignored if all your controllers have
NVRAM, since the driver is able to detect the board type from the
NVRAM format.
If all the controllers in your system are genuine SYMBIOS boards or
use BIOS and drivers from SYMBIOS, you would want to say Y here,
otherwise N. N is the safe answer.
Enable traffic profiling
CONFIG_SCSI_NCR53C8XX_PROFILE
This option allows you to enable profiling information gathering.
These statistics are not very accurate due to the low frequency
of the kernel clock (100 Hz on i386) and have performance impact
on systems that use very fast devices.
The normal answer therefore is N.
Include support for the NCR PQS/PDS SCSI card
CONFIG_SCSI_NCR53C8XX_PQS_PDS
Say Y here if you have a special SCSI adapter produced by NCR
corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
this if you do not have one of these adapters. However, since this
device is detected as a specific PCI device, this option is quite
safe.
The common answer here is N, but answering Y is safe.
IBMMCA SCSI support
CONFIG_SCSI_IBMMCA
This is support for the IBM SCSI adapter found in many of the PS/2
series computers. These machines have an MCA bus, so you need to
answer Y to "MCA support" as well and read
<file:Documentation/mca.txt>.
If the adapter isn't found during boot (a common problem for models
56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
option, where <pun> is the id of the SCSI subsystem (usually 7, but
if that doesn't work check your reference diskette). Owners of
model 95 with a LED-matrix-display can in addition activate some
activity info like under OS/2, but more informative, by setting
'ibmmcascsi=display' as an additional kernel parameter. Try "man
bootparam" or see the documentation of your boot loader about how to
pass options to the kernel.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ibmmca.o.
Standard SCSI-order
CONFIG_IBMMCA_SCSI_ORDER_STANDARD
In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
are assigned to the drive letters, starting with the lowest SCSI-id
(physical number -- pun) to be drive C:, as seen from DOS and
similar operating systems. When looking into papers describing the
ANSI-SCSI-standard, this assignment of drives appears to be wrong.
The SCSI-standard follows a hardware-hierarchy which says that id 7
has the highest priority and id 0 the lowest. Therefore, the host
adapters are still today everywhere placed as SCSI-id 7 by default.
In the SCSI-standard, the drive letters express the priority of the
disk. C: should be the hard disk, or a partition on it, with the
highest priority. This must therefore be the disk with the highest
SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
original definition of the SCSI-standard as also industrial- and
process-control-machines, like VME-CPUs running under realtime-OSes
(e.g. LynxOS, OS9) do.
If you like to run Linux on your MCA-machine with the same
assignment of hard disks as seen from e.g. DOS or OS/2 on your
machine, which is in addition conformant to the SCSI-standard, you
must say Y here. This is also necessary for MCA-Linux users who want
to keep downward compatibility to older releases of the
IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
June 1997).
If you like to have the lowest SCSI-id assigned as drive C:, as
modern SCSI-BIOSes do, which does not conform to the standard, but
is widespread and common in the PC-world of today, you must say N
here. If unsure, say Y.
Reset SCSI-devices at boot time
CONFIG_IBMMCA_SCSI_DEV_RESET
By default, SCSI-devices are reset when the machine is powered on.
However, some devices exist, like special-control-devices,
SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
not reset when switched on. If you say Y here, each device connected
to your SCSI-bus will be issued a reset-command after it has been
probed, while the kernel is booting. This may cause problems with
more modern devices, like hard disks, which do not appreciate these
reset commands, and can cause your system to hang. So say Y only if
you know that one of your older devices needs it; N is the safe
answer.
NCR MCA 53C9x SCSI support
CONFIG_SCSI_MCA_53C9X
Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
controller based on the NCR 53C94. This driver will allow use of
the controller on the 3550, and very possibly others.
If you want to compile this as a module (= code which can be
inserted and removed from the running kernel whenever you want), say
M here and read <file:Documentation/modules.txt>. The module will
be called mca_53c9x.o.
Always IN2000 SCSI support
CONFIG_SCSI_IN2000
This is support for an ISA bus SCSI host adapter. You'll find more
information in <file:drivers/scsi/README.in2000>. If it doesn't work
out of the box, you may have to change the jumpers for IRQ or
address selection.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called in2000.o.
Initio 91XXU(W) SCSI support
CONFIG_SCSI_INITIO
This is support for the Initio 91XXU(W) SCSI host adapter. Please
read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called initio.o.
PAS16 SCSI support
CONFIG_SCSI_PAS16
This is support for a SCSI host adapter. It is explained in section
3.10 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/pas16.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called pas16.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Initio INI-A100U2W SCSI support
CONFIG_SCSI_INIA100
This is support for the Initio INI-A100U2W SCSI host adapter.
Please read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called a100u2w.o.
PCI2000 support
CONFIG_SCSI_PCI2000
This is support for the PCI2000I EIDE interface card which acts as a
SCSI host adapter. Please read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module called pci2000.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
PCI2220i support
CONFIG_SCSI_PCI2220I
This is support for the PCI2220i EIDE interface card which acts as a
SCSI host adapter. Please read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module called pci2220i.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
PSI240i support
CONFIG_SCSI_PSI240I
This is support for the PSI240i EIDE interface card which acts as a
SCSI host adapter. Please read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module called psi240i.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
Qlogic FAS SCSI support
CONFIG_SCSI_QLOGIC_FAS
This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
FastSCSI! cards as well as any other card based on the FASXX chip
(including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
This driver does NOT support the PCI versions of these cards. The
PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
SCSI support"), below.
Information about this driver is contained in
<file:drivers/scsi/README.qlogicfas>. You should also read the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qlogicfas.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Qlogic ISP SCSI support
CONFIG_SCSI_QLOGIC_ISP
This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
card is supported by the "AM53/79C974 PCI SCSI" driver.)
If you say Y here, make sure to choose "BIOS" at the question "PCI
access mode".
Please read the file <file:drivers/scsi/README.qlogicisp>. You
should also read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qlogicisp.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Qlogic ISP FC SCSI support
CONFIG_SCSI_QLOGIC_FC
This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qlogicfc.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Include loadable firmware in driver
CONFIG_SCSI_QLOGIC_FC_FIRMWARE
Say Y to include ISP2100 Fabric Initiator/Target Firmware, with
expanded LUN addressing and FcTape (FCP-2) support, in the
Qlogic QLA 1280 driver. This is required on some platforms.
Qlogic QLA 1280 SCSI support
CONFIG_SCSI_QLOGIC_1280
Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qla1280.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Seagate ST-02 and Future Domain TMC-8xx SCSI support
CONFIG_SCSI_SEAGATE
These are 8-bit SCSI controllers; the ST-01 is also supported by
this driver. It is explained in section 3.9 of the SCSI-HOWTO,
available from <http://www.tldp.org/docs.html#howto>. If it
doesn't work out of the box, you may have to change some settings in
<file:drivers/scsi/seagate.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called seagate.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Trantor T128/T128F/T228 SCSI support
CONFIG_SCSI_T128
This is support for a SCSI host adapter. It is explained in section
3.11 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/t128.h>. Note that Trantor was purchased by
Adaptec, and some former Trantor products are being sold under the
Adaptec name.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called t128.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
UltraStor SCSI support
CONFIG_SCSI_ULTRASTOR
This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
adapter family. This driver is explained in section 3.12 of the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
<file:drivers/scsi/ultrastor.h>.
Note that there is also another driver for the same hardware:
"UltraStor 14F/34F support", above.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ultrastor.o.
7000FASST SCSI support
CONFIG_SCSI_7000FASST
This driver supports the Western Digital 7000 SCSI host adapter
family. Some information is in the source:
<file:drivers/scsi/wd7000.c>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called wd7000.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
ACARD SCSI support
CONFIG_SCSI_ACARD
This driver supports the ACARD 870U/W SCSI host adapter.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called atp870u.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
CONFIG_SCSI_EATA
This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
ISA and all EISA I/O addresses are probed looking for the "EATA"
signature. If you chose "BIOS" at the question "PCI access mode",
the addresses of all the PCI SCSI controllers reported by the PCI
subsystem are probed as well.
You want to read the start of <file:drivers/scsi/eata.c> and the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that there is also another driver for the same hardware
available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
Alphatronix) support". You should say Y to only one of them.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called eata.o.
enable tagged command queueing
CONFIG_SCSI_EATA_TAGGED_QUEUE
This is a feature of SCSI-2 which improves performance: the host
adapter can send several SCSI commands to a device's queue even if
previous commands haven't finished yet. Most EATA adapters negotiate
this feature automatically with the device, even if your answer is
N. The safe answer is N.
enable elevator sorting
CONFIG_SCSI_EATA_LINKED_COMMANDS
This option enables elevator sorting for all probed SCSI disks and
CD-ROMs. It definitely reduces the average seek distance when doing
random seeks, but this does not necessarily result in a noticeable
performance improvement: your mileage may vary...
The safe answer is N.
maximum number of queued commands
CONFIG_SCSI_EATA_MAX_TAGS
This specifies how many SCSI commands can be maximally queued for
each probed SCSI device. You should reduce the default value of 16
only if you have disks with buggy or limited tagged command support.
Minimum is 2 and maximum is 62. This value is also the window size
used by the elevator sorting option above. The effective value used
by the driver for each probed SCSI device is reported at boot time.
NCR53c406a SCSI support
CONFIG_SCSI_NCR53C406A
This is support for the NCR53c406a SCSI host adapter. For user
configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
in the kernel source. Also read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called NCR53c406.o.
Symbios 53c416 SCSI support
CONFIG_SCSI_SYM53C416
This is support for the sym53c416 SCSI host adapter, the SCSI
adapter that comes with some HP scanners. This driver requires that
the sym53c416 is configured first using some sort of PnP
configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
are using isapnp then you need to compile this driver as a module
and then load it using insmod after isapnp has run. The parameters
of the configured card(s) should be passed to the driver. The format
is:
insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
There is support for up to four adapters. If you want to compile
this driver as a module ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt>. The module will be called
sym53c416.o.
Simple 53c710 SCSI support (Compaq, NCR machines)
CONFIG_SCSI_SIM710
This is a simple driver for NCR53c710 based SCSI host adapters.
More complex drivers for this chip are available ("NCR53c7,8xx SCSI
support", above), but they require that the scsi chip be able to do
DMA block moves between memory and on-chip registers, which can
cause problems under certain conditions. This driver is designed to
avoid these problems and is intended to work with any Intel machines
using 53c710 chips, including various Compaq and NCR machines.
Please read the comments at the top of the file
<file:drivers/scsi/sim710.c> for more information.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called sim710.o.
Tekram DC390(T) and Am53/79C974 SCSI support
CONFIG_SCSI_DC390T
This driver supports PCI SCSI host adapters based on the Am53C974A
chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
PCscsi/PCnet (Am53/79C974) solutions.
Documentation can be found in <file:drivers/scsi/README.tmscsim>.
Note that this driver does NOT support Tekram DC390W/U/F, which are
based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
Also note that there is another generic Am53C974 driver,
"AM53/79C974 PCI SCSI support" below. You can pick either one.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called tmscsim.o.
Omit support for other Am53/79C974 based SCSI adapters
CONFIG_SCSI_DC390T_NOGENSUPP
If you say N here, the DC390(T) SCSI driver relies on the DC390
EEPROM to get initial values for its settings, such as speed,
termination, etc. If it can't find this EEPROM, it will use
defaults or the user supplied boot/module parameters. For details
on driver configuration see <file:drivers/scsi/README.tmscsim>.
If you say Y here and if no EEPROM is found, the driver gives up and
thus only supports Tekram DC390(T) adapters. This can be useful if
you have a DC390(T) and another Am53C974 based adapter, which, for
some reason, you want to drive with the other AM53C974 driver.
If unsure, say N.
AM53/79C974 PCI SCSI support
CONFIG_SCSI_AM53C974
This is support for the AM53/79C974 SCSI host adapters. Please read
<file:drivers/scsi/README.AM53C974> for details. Also, the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, is for you.
Note that there is another driver for AM53C974 based adapters:
"Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
can pick either one.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called AM53C974.o.
AMI MegaRAID support
CONFIG_SCSI_MEGARAID
This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
and 467 SCSI host adapters.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called megaraid.o.
Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
CONFIG_SCSI_GDTH
Formerly called GDT SCSI Disk Array Controller Support.
This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
manufactured by Intel/ICP vortex (an Intel Company). It is documented
in the kernel source in <file:drivers/scsi/gdth.c> and
<file:drivers/scsi/gdth.h.>
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called gdth.o.
IOMEGA parallel port (ppa - older drives)
CONFIG_SCSI_PPA
This driver supports older versions of IOMEGA's parallel port ZIP
drive (a 100 MB removable media device).
Note that you can say N here if you have the SCSI version of the ZIP
drive: it will be supported automatically if you said Y to the
generic "SCSI disk support", above.
If you have the ZIP Plus drive or a more recent parallel port ZIP
drive (if the supplied cable with the drive is labeled "AutoDetect")
then you should say N here and Y to "IOMEGA parallel port (imm -
newer drives)", below.
For more information about this driver and how to use it you should
read the file <file:drivers/scsi/README.ppa>. You should also read
the SCSI-HOWTO, which is available from
<http://www.tldp.org/docs.html#howto>. If you use this driver,
you will still be able to use the parallel port for other tasks,
such as a printer; it is safe to compile both drivers into the
kernel.
This driver is also available as a module which can be inserted in
and removed from the running kernel whenever you want. To compile
this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called ppa.o.
IOMEGA parallel port (imm - newer drives)
CONFIG_SCSI_IMM
This driver supports newer versions of IOMEGA's parallel port ZIP
drive (a 100 MB removable media device).
Note that you can say N here if you have the SCSI version of the ZIP
drive: it will be supported automatically if you said Y to the
generic "SCSI disk support", above.
If you have the ZIP Plus drive or a more recent parallel port ZIP
drive (if the supplied cable with the drive is labeled "AutoDetect")
then you should say Y here; if you have an older ZIP drive, say N
here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
For more information about this driver and how to use it you should
read the file <file:drivers/scsi/README.ppa>. You should also read
the SCSI-HOWTO, which is available from
<http://www.tldp.org/docs.html#howto>. If you use this driver,
you will still be able to use the parallel port for other tasks,
such as a printer; it is safe to compile both drivers into the
kernel.
This driver is also available as a module which can be inserted in
and removed from the running kernel whenever you want. To compile
this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called imm.o.
Force the Iomega ZIP drivers to use EPP-16
CONFIG_SCSI_IZIP_EPP16
EPP (Enhanced Parallel Port) is a standard for parallel ports which
allows them to act as expansion buses that can handle up to 64
peripheral devices.
Some parallel port chipsets are slower than their motherboard, and
so we have to control the state of the chipset's FIFO queue every
now and then to avoid data loss. This will be done if you say Y
here.
Generally, saying Y is the safe option and slows things down a bit.
Assume slow parallel port control register
CONFIG_SCSI_IZIP_SLOW_CTR
Some parallel ports are known to have excessive delays between
changing the parallel port control register and good data being
available on the parallel port data/status register. This option
forces a small delay (1.0 usec to be exact) after changing the
control register to let things settle out. Enabling this option may
result in a big drop in performance but some very old parallel ports
(found in 386 vintage machines) will not work properly.
Generally, saying N is fine.
SCSI debugging host simulator
CONFIG_SCSI_DEBUG
This is a host adapter simulator that can be programmed to simulate
a large number of conditions that could occur on a real bus. The
advantage is that many hard to reproduce problems can be tested in a
controlled environment where there is reduced risk of losing
important data. This is primarily of use to people trying to debug
the middle and upper layers of the SCSI subsystem. If unsure, say N.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called scsi_debug.o.
Fibre Channel and FC4 SCSI support
CONFIG_FC4
Fibre Channel is a high speed serial protocol mainly used to
connect large storage devices to the computer; it is compatible with
and intended to replace SCSI.
This is an experimental support for storage arrays connected to your
computer using optical fibre cables and the "X3.269-199X Fibre
Channel Protocol for SCSI" specification. If you want to use this,
you need to say Y here and to "SCSI support" as well as to the
drivers for the storage array itself and for the interface adapter
such as SOC or SOC+. This subsystem could even serve for IP
networking, with some code extensions.
If unsure, say N.
Sun SOC/Sbus
CONFIG_FC4_SOC
Serial Optical Channel is an interface card with one or two Fibre
Optic ports, each of which can be connected to a disk array. Note
that if you have older firmware in the card, you'll need the
microcode from the Solaris driver to make it work.
This support is also available as a module called soc.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
Sun SOC+ (aka SOCAL)
CONFIG_FC4_SOCAL
Serial Optical Channel Plus is an interface card with up to two
Fibre Optic ports. This card supports FC Arbitrated Loop (usually
A5000 or internal FC disks in E[3-6]000 machines through the
Interface Board). You'll probably need the microcode from the
Solaris driver to make it work.
This support is also available as a module called socal.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
SparcSTORAGE Array 100 and 200 series
CONFIG_SCSI_PLUTO
If you never bought a disk array made by Sun, go with N.
This support is also available as a module called pluto.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
Sun Enterprise Network Array (A5000 and EX500)
CONFIG_SCSI_FCAL
This driver drives FC-AL disks connected through a Fibre Channel
card using the drivers/fc4 layer (currently only SOCAL). The most
common is either A5000 array or internal disks in E[3-6]000
machines.
This support is also available as a module called fcal.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>. If unsure, say N.
Acorn SCSI card (aka30) support
CONFIG_SCSI_ACORNSCSI_3
This enables support for the Acorn SCSI card (aka30). If you have an
Acorn system with one of these, say Y. If unsure, say N.
Support SCSI 2 Tagged queueing
CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
Say Y here to enable tagged queuing support on the Acorn SCSI card.
This is a feature of SCSI-2 which improves performance: the host
adapter can send several SCSI commands to a device's queue even if
previous commands haven't finished yet. Some SCSI devices don't
implement this properly, so the safe answer is N.
Support SCSI 2 Synchronous Transfers
CONFIG_SCSI_ACORNSCSI_SYNC
Say Y here to enable synchronous transfer negotiation with all
targets on the Acorn SCSI card.
In general, this improves performance; however some SCSI devices
don't implement it properly, so the safe answer is N.
ARXE SCSI support
CONFIG_SCSI_ARXESCSI
Around 1991, Arxe Systems Limited released a high density floppy
disc interface for the Acorn Archimedes range, to allow the use of
HD discs from the then new A5000 on earlier models. This interface
was either sold on its own or with an integral SCSI controller.
Technical details on this NCR53c94-based device are available at
<http://www.cryton.demon.co.uk/acornbits/scsi_arxe.html>
Say Y here to compile in support for the SCSI controller.
Oak SCSI support
CONFIG_SCSI_OAK1
This enables support for the Oak SCSI card. If you have an Acorn
system with one of these, say Y. If unsure, say N.
Cumana SCSI I support
CONFIG_SCSI_CUMANA_1
This enables support for the Cumana SCSI I card. If you have an
Acorn system with one of these, say Y. If unsure, say N.
Cumana SCSI II support
CONFIG_SCSI_CUMANA_2
This enables support for the Cumana SCSI II card. If you have an
Acorn system with one of these, say Y. If unsure, say N.
EcoSCSI support
CONFIG_SCSI_ECOSCSI
This enables support for the EcoSCSI card -- a small card that sits
in the Econet socket. If you have an Acorn system with one of these,
say Y. If unsure, say N.
EESOX SCSI support
CONFIG_SCSI_EESOXSCSI
This enables support for the EESOX SCSI card. If you have an Acorn
system with one of these, say Y, otherwise say N.
PowerTec SCSI support
CONFIG_SCSI_POWERTECSCSI
This enables support for the Powertec SCSI card on Acorn systems. If
you have one of these, say Y. If unsure, say N.
IEEE 1394 (FireWire) support
CONFIG_IEEE1394
IEEE 1394 describes a high performance serial bus, which is also
known as FireWire(tm) or i.Link(tm) and is used for connecting all
sorts of devices (most notably digital video cameras) to your
computer.
If you have FireWire hardware and want to use it, say Y here. This
is the core support only, you will also need to select a driver for
your IEEE 1394 adapter.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ieee1394.o.
Texas Instruments PCILynx support
CONFIG_IEEE1394_PCILYNX
Say Y here if you have an IEEE-1394 controller with the Texas
Instruments PCILynx chip. Note: this driver is written for revision
2 of this chip and may not work with revision 0.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called pcilynx.o.
Use local RAM on PCILynx board
CONFIG_IEEE1394_PCILYNX_LOCALRAM
This option makes the PCILynx driver use local RAM available on some
PCILynx setups for Packet Control Lists. Local RAM is random access
memory which resides on the PCILynx board as opposed to on your
computer's motherboard. Local RAM may speed up command processing
because no PCI transfers are necessary during use of the Packet
Control Lists.
Note that there are no known PCILynx systems providing local RAM
except for the evaluation boards by Texas Instruments and that the
PCILynx does not reliably report missing RAM. This means that it is
dangerous to say Y here if you are not absolutely sure that your
board provides 64KB of local RAM.
If unsure, say N.
Support for non-IEEE1394 local ports
CONFIG_IEEE1394_PCILYNX_PORTS
This option enables driver code to access the RAM, ROM and AUX ports
of the PCILynx through character devices in /dev. If you don't know
what this is about then you won't need it.
If unsure, say N.
#Adaptec AIC-5800 IEEE 1394 support
#CONFIG_IEEE1394_AIC5800
# Say Y here if you have a IEEE 1394 controller using the Adaptec
# AIC-5800 chip. All Adaptec host adapters (89xx series) use this
# chip, as well as miro's DV boards.
#
# If you want to compile this as a module ( = code which can be
# inserted in and removed from the running kernel whenever you want),
# say M here and read <file:Documentation/modules.txt>. The module
# will be called aic5800.o.
#
OHCI-1394 (Open Host Controller Interface) support
CONFIG_IEEE1394_OHCI1394
Enable this driver if you have an IEEE 1394 controller based on the
OHCI-1394 specification. The current driver is only tested with OHCI
chipsets made by Texas Instruments and NEC. Most third-party vendors
use one of these chipsets. It should work with any OHCI-1394
compliant card, however.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ohci1394.o.
OHCI-1394 Video support
CONFIG_IEEE1394_VIDEO1394
This option enables video device usage for OHCI-1394 cards. Enable
this option only if you have an IEEE 1394 video device connected to
an OHCI-1394 card.
SBP-2 support (Harddisks etc.)
CONFIG_IEEE1394_SBP2
This option enables you to use SBP-2 devices connected to your IEEE
1394 bus. SBP-2 devices include harddrives and DVD devices.
Raw IEEE 1394 I/O support
CONFIG_IEEE1394_RAWIO
Say Y here if you want support for the raw device. This is generally
a good idea, so you should say Y here. The raw device enables
direct communication of user programs with the IEEE 1394 bus and
thus with the attached peripherals.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called raw1394.o.
Excessive debugging output
CONFIG_IEEE1394_VERBOSEDEBUG
If you say Y here, you will get very verbose debugging logs from the
subsystem which includes a dump of the header of every sent and
received packet. This can amount to a high amount of data collected
in a very short time which is usually also saved to disk by the
system logging daemons.
Say Y if you really want or need the debugging output, everyone else
says N.
Network device support
CONFIG_NETDEVICES
You can say N here if you don't intend to connect your Linux box to
any other computer at all or if all your connections will be over a
telephone line with a modem either via UUCP (UUCP is a protocol to
forward mail and news between unix hosts over telephone lines; read
the UUCP-HOWTO, available from
<http://www.tldp.org/docs.html#howto>) or dialing up a shell
account or a BBS, even using term (term is a program which gives you
almost full Internet connectivity if you have a regular dial up
shell account on some Internet connected Unix computer. Read
<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
You'll have to say Y if your computer contains a network card that
you want to use under Linux (make sure you know its name because you
will be asked for it and read the Ethernet-HOWTO (especially if you
plan to use more than one network card under Linux)) or if you want
to use SLIP (Serial Line Internet Protocol is the protocol used to
send Internet traffic over telephone lines or null modem cables) or
CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
and newer replacement for SLIP) or PLIP (Parallel Line Internet
Protocol is mainly used to create a mini network by connecting the
parallel ports of two local machines) or AX.25/KISS (protocol for
sending Internet traffic over amateur radio links).
Make sure to read the NET-3-HOWTO. Eventually, you will have to read
Olaf Kirch's excellent and free book "Network Administrator's
Guide", to be found in <http://www.tldp.org/docs.html#guide>. If
unsure, say Y.
Dummy net driver support
CONFIG_DUMMY
This is essentially a bit-bucket device (i.e. traffic you send to
this device is consigned into oblivion) with a configurable IP
address. It is most commonly used in order to make your currently
inactive SLIP address seem like a real address for local programs.
If you use SLIP or PPP, you might want to say Y here. Since this
thing often comes in handy, the default is Y. It won't enlarge your
kernel either. What a deal. Read about it in the Network
Administrator's Guide, available from
<http://www.tldp.org/docs.html#guide>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called dummy.o. If you want to use more than one dummy
device at a time, you need to compile this driver as a module.
Instead of 'dummy', the devices will then be called 'dummy0',
'dummy1' etc.
Bonding driver support
CONFIG_BONDING
Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
Channels together. This is called 'Etherchannel' by Cisco,
'Trunking' by Sun, and 'Bonding' in Linux.
If you have two Ethernet connections to some other computer, you can
make them behave like one double speed connection using this driver.
Naturally, this has to be supported at the other end as well, either
with a similar Bonding Linux driver, a Cisco 5500 switch or a
SunTrunking SunSoft driver.
This is similar to the EQL driver, but it merges Ethernet segments
instead of serial lines.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called bonding.o.
SLIP (serial line) support
CONFIG_SLIP
Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
connect to your Internet service provider or to connect to some
other local Unix box or if you want to configure your Linux box as a
Slip/CSlip server for other people to dial in. SLIP (Serial Line
Internet Protocol) is a protocol used to send Internet traffic over
serial connections such as telephone lines or null modem cables;
nowadays, the protocol PPP is more commonly used for this same
purpose.
Normally, your access provider has to support SLIP in order for you
to be able to use it, but there is now a SLIP emulator called SLiRP
around (available from
<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection. If
you plan to use SLiRP, make sure to say Y to CSLIP, below. The
NET-3-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, explains how to
configure SLIP. Note that you don't need this option if you just
want to run term (term is a program which gives you almost full
Internet connectivity if you have a regular dial up shell account on
some Internet connected Unix computer. Read
<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
support will enlarge your kernel by about 4 KB. If unsure, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt> as well as
<file:Documentation/networking/net-modules.txt>. The module will be
called slip.o.
CSLIP compressed headers
CONFIG_SLIP_COMPRESSED
This protocol is faster than SLIP because it uses compression on the
TCP/IP headers (not on the data itself), but it has to be supported
on both ends. Ask your access provider if you are not sure and
answer Y, just in case. You will still be able to use plain SLIP. If
you plan to use SLiRP, the SLIP emulator (available from
<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection, you
definitely want to say Y here. The NET-3-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, explains how to configure
CSLIP. This won't enlarge your kernel.
Keepalive and linefill
CONFIG_SLIP_SMART
Adds additional capabilities to the SLIP driver to support the
RELCOM line fill and keepalive monitoring. Ideal on poor quality
analogue lines.
Six bit SLIP encapsulation
CONFIG_SLIP_MODE_SLIP6
Just occasionally you may need to run IP over hostile serial
networks that don't pass all control characters or are only seven
bit. Saying Y here adds an extra mode you can use with SLIP:
"slip6". In this mode, SLIP will only send normal ASCII symbols over
the serial device. Naturally, this has to be supported at the other
end of the link as well. It's good enough, for example, to run IP
over the async ports of a Camtec JNT Pad. If unsure, say N.
PPP (point-to-point protocol) support
CONFIG_PPP
PPP (Point to Point Protocol) is a newer and better SLIP. It serves
the same purpose: sending Internet traffic over telephone (and other
serial) lines. Ask your access provider if they support it, because
otherwise you can't use it; most Internet access providers these
days support PPP rather than SLIP.
To use PPP, you need an additional program called pppd as described
in the PPP-HOWTO, available at
<http://www.tldp.org/docs.html#howto>. Make sure that you have
the version of pppd recommended in <file:Documentation/Changes>.
The PPP option enlarges your kernel by about 16 KB.
There are actually two versions of PPP: the traditional PPP for
asynchronous lines, such as regular analog phone lines, and
synchronous PPP which can be used over digital ISDN lines for
example. If you want to use PPP over phone lines or other
asynchronous serial lines, you need to say Y (or M) here and also to
the next option, "PPP support for async serial ports". For PPP over
synchronous lines, you should say Y (or M) here and to "Support
synchronous PPP", below.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you said Y to "Version information on all symbols" above, then
you cannot compile the PPP driver into the kernel; you can then only
compile it as a module. The module will be called ppp_generic.o.
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt> as well as
<file:Documentation/networking/net-modules.txt>.
PPP multilink support
CONFIG_PPP_MULTILINK
PPP multilink is a protocol (defined in RFC 1990) which allows you
to combine several (logical or physical) lines into one logical PPP
connection, so that you can utilize your full bandwidth.
This has to be supported at the other end as well and you need a
version of the pppd daemon which understands the multilink protocol.
If unsure, say N.
PPP filtering
CONFIG_PPP_FILTER
Say Y here if you want to be able to filter the packets passing over
PPP interfaces. This allows you to control which packets count as
activity (i.e. which packets will reset the idle timer or bring up
a demand-dialled link) and which packets are to be dropped entirely.
You need to say Y here if you wish to use the pass-filter and
active-filter options to pppd.
If unsure, say N.
PPP support for async serial ports
CONFIG_PPP_ASYNC
Say Y (or M) here if you want to be able to use PPP over standard
asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
a modem (not a synchronous or ISDN modem) to contact your ISP, you
need this option.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ppp_async.o.
If unsure, say Y.
PPP support for sync tty ports
CONFIG_PPP_SYNC_TTY
Say Y (or M) here if you want to be able to use PPP over synchronous
(HDLC) tty devices, such as the SyncLink adapter. These devices
are often used for high-speed leased lines like T1/E1.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ppp_synctty.o.
PPP Deflate compression
CONFIG_PPP_DEFLATE
Support for the Deflate compression method for PPP, which uses the
Deflate algorithm (the same algorithm that gzip uses) to compress
each PPP packet before it is sent over the wire. The machine at the
other end of the PPP link (usually your ISP) has to support the
Deflate compression method as well for this to be useful. Even if
they don't support it, it is safe to say Y here.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ppp_deflate.o.
PPP BSD-Compress compression
CONFIG_PPP_BSDCOMP
Support for the BSD-Compress compression method for PPP, which uses
the LZW compression method to compress each PPP packet before it is
sent over the wire. The machine at the other end of the PPP link
(usually your ISP) has to support the BSD-Compress compression
method as well for this to be useful. Even if they don't support it,
it is safe to say Y here.
The PPP Deflate compression method ("PPP Deflate compression",
above) is preferable to BSD-Compress, because it compresses better
and is patent-free.
Note that the BSD compression code will always be compiled as a
module; it is called bsd_comp.o and will show up in the directory
modules once you have said "make modules". If unsure, say N.
PPP over Ethernet
CONFIG_PPPOE
Support for PPP over Ethernet.
This driver requires the current pppd from the "ppp" CVS repository
on cvs.samba.org. The required support will be present in the next
ppp release (2.4.2).
Wireless LAN (non-hamradio)
CONFIG_NET_RADIO
Support for wireless LANs and everything having to do with radio,
but not with amateur radio or FM broadcasting.
Saying Y here also enables the Wireless Extensions (creates
/proc/net/wireless and enables ifconfig access). The Wireless
Extension is a generic API allowing a driver to expose to the user
space configuration and statistics specific to common Wireless LANs.
The beauty of it is that a single set of tool can support all the
variations of Wireless LANs, regardless of their type (as long as
the driver supports Wireless Extension). Another advantage is that
these parameters may be changed on the fly without restarting the
driver (or Linux). If you wish to use Wireless Extensions with
wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
the tools from