menu "SCSI device support"
config [31mCONFIG_SCSI_MOD[0m
tristate
default y if [31mCONFIG_SCSI[0m=n || [31mCONFIG_SCSI[0m=y
default m if [31mCONFIG_SCSI[0m=m
config [31mCONFIG_RAID_ATTRS[0m
tristate "RAID Transport Class"
default n
depends on [31mCONFIG_BLOCK[0m
depends on [31mCONFIG_SCSI_MOD[0m
---help---
Provides RAID
config [31mCONFIG_SCSI[0m
tristate "SCSI device support"
depends on [31mCONFIG_BLOCK[0m
select [31mCONFIG_SCSI_DMA[0m if [31mCONFIG_HAS_DMA[0m
select [31mCONFIG_SG_POOL[0m
---help---
If you want to use a [31mCONFIG_SCSI[0m hard disk, [31mCONFIG_SCSI[0m tape drive, [31mCONFIG_SCSI[0m CD-[31mCONFIG_ROM[0m or
any other [31mCONFIG_SCSI[0m device under Linux, say Y and make sure that you know
the name of your [31mCONFIG_SCSI[0m host adapter (the card inside your computer
that "speaks" the [31mCONFIG_SCSI[0m protocol, also called [31mCONFIG_SCSI[0m controller),
because you will be asked for it.
You also need to say Y here if you have a device which speaks
the [31mCONFIG_SCSI[0m protocol. Examples of this include the parallel port
version of the IOMEGA ZIP drive, [31mCONFIG_USB[0m storage devices, Fibre
Channel, and FireWire storage.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called scsi_mod.
However, do not compile this as a module if your root file system
(the one containing the directory /) is located on a [31mCONFIG_SCSI[0m device.
config [31mCONFIG_SCSI_DMA[0m
bool
default n
config [31mCONFIG_SCSI_NETLINK[0m
bool
default n
depends on [31mCONFIG_NET[0m
config [31mCONFIG_SCSI_MQ_DEFAULT[0m
bool "SCSI: use blk-mq I/O path by default"
depends on [31mCONFIG_SCSI[0m
---help---
This option enables the new blk-mq based I/O path for [31mCONFIG_SCSI[0m
devices by default. With the option the scsi_mod.use_blk_mq
module/boot option defaults to Y, without it to N, but it can
still be overridden either way.
If unsure say N.
config [31mCONFIG_SCSI_PROC_FS[0m
bool "legacy /proc/scsi/ support"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PROC_FS[0m
default y
---help---
This option enables support for the various files in
/proc/scsi. In Linux 2.6 this has been superseded by
files in sysfs but many legacy applications rely on this.
If unsure say Y.
comment "SCSI support type (disk, tape, CD-ROM)"
depends on [31mCONFIG_SCSI[0m
config [31mCONFIG_BLK_DEV_SD[0m
tristate "SCSI disk support"
depends on [31mCONFIG_SCSI[0m
---help---
If you want to use [31mCONFIG_SCSI[0m hard disks, Fibre Channel disks,
Serial [31mCONFIG_ATA[0m (SATA) or Parallel [31mCONFIG_ATA[0m (PATA) hard disks,
[31mCONFIG_USB[0m storage or the [31mCONFIG_SCSI[0m or parallel port version of
the IOMEGA ZIP drive, say Y and read the [31mCONFIG_SCSI[0m-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.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called sd_mod.
Do not compile this driver as a module if your root file system
(the one containing the directory /) is located on a [31mCONFIG_SCSI[0m disk.
In this case, do not compile the driver for your [31mCONFIG_SCSI[0m host adapter
(below) as a module either.
config [31mCONFIG_CHR_DEV_ST[0m
tristate "SCSI tape support"
depends on [31mCONFIG_SCSI[0m
---help---
If you want to use a [31mCONFIG_SCSI[0m tape drive under Linux, say Y and read the
[31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and
<file:Documentation/scsi/st.txt> in the kernel source. This is NOT
for [31mCONFIG_SCSI[0m CD-ROMs.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>. The module will be called st.
config [31mCONFIG_CHR_DEV_OSST[0m
tristate "SCSI OnStream SC-x0 tape support"
depends on [31mCONFIG_SCSI[0m
---help---
The OnStream SC-x0 [31mCONFIG_SCSI[0m tape drives cannot 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,
you may be able to drive the [31mCONFIG_USB[0m-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 [31mCONFIG_SCSI[0m-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 [31mCONFIG_SCSI[0m-HOWTO
<http://www.tldp.org/docs.html#howto> and
<file:Documentation/scsi/osst.txt> in the kernel source.
More info on the OnStream driver may be found on
<http://sourceforge.net/projects/osst/>
Please also have a look at the standard st docu, as most of it
applies to osst as well.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>. The module will be called osst.
config [31mCONFIG_BLK_DEV_SR[0m
tristate "SCSI CDROM support"
depends on [31mCONFIG_SCSI[0m
---help---
If you want to use a CD or DVD drive attached to your computer
by [31mCONFIG_SCSI[0m, FireWire, [31mCONFIG_USB[0m or ATAPI, say Y and read the [31mCONFIG_SCSI[0m-HOWTO
and the [31mCONFIG_CDROM[0m-HOWTO at <http://www.tldp.org/docs.html#howto>.
Make sure to say Y or [31mCONFIG_M[0m to "ISO 9660 CD-ROM file system support".
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called sr_mod.
config [31mCONFIG_BLK_DEV_SR_VENDOR[0m
bool "Enable vendor-specific extensions (for SCSI CDROM)"
depends on [31mCONFIG_BLK_DEV_SR[0m
help
This enables the usage of vendor specific [31mCONFIG_SCSI[0m commands. This is
required to support multisession CDs with old NEC/[31mCONFIG_TOSHIBA[0m 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.
config [31mCONFIG_CHR_DEV_SG[0m
tristate "SCSI generic support"
depends on [31mCONFIG_SCSI[0m
---help---
If you want to use [31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m protocol:
For scanners, look at SANE (<http://www.sane-project.org/>). For CD
writer software look at Cdrtools
(<http://cdrecord.berlios.de/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/scsi-generic.txt> for more information.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>. The module will be called sg.
If unsure, say N.
config [31mCONFIG_CHR_DEV_SCH[0m
tristate "SCSI media changer support"
depends on [31mCONFIG_SCSI[0m
---help---
This is a driver for [31mCONFIG_SCSI[0m media changers. Most common devices are
tape libraries and MOD/[31mCONFIG_CDROM[0m jukeboxes. *Real* jukeboxes, you
don't need this for those tiny 6-slot cdrom changers. Media
changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
If you have such hardware and want to use it with linux, say Y
here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
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 [31mCONFIG_M[0m here and read <file:Documentation/kbuild/modules.txt> and
<file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
If unsure, say N.
config [31mCONFIG_SCSI_ENCLOSURE[0m
tristate "SCSI Enclosure Support"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_ENCLOSURE_SERVICES[0m
depends on m || [31mCONFIG_SCSI_SAS_ATTRS[0m != m
help
Enclosures are devices sitting on or in [31mCONFIG_SCSI[0m backplanes that
manage devices. If you have a disk cage, the chances are that
it has an enclosure device. Selecting this option will just allow
certain enclosure conditions to be reported and is not required.
config [31mCONFIG_SCSI_CONSTANTS[0m
bool "Verbose SCSI error reporting (kernel size += 36K)"
depends on [31mCONFIG_SCSI[0m
help
The error messages regarding your [31mCONFIG_SCSI[0m hardware will be easier to
understand if you say Y here; it will enlarge your kernel by about
36 KB. If in doubt, say Y.
config [31mCONFIG_SCSI_LOGGING[0m
bool "SCSI logging facility"
depends on [31mCONFIG_SCSI[0m
---help---
This turns on a logging facility that can be used to debug a number
of [31mCONFIG_SCSI[0m 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 <bitmask> > /proc/sys/dev/scsi/logging_level
where <bitmask> is a four byte value representing the logging type
and logging level for each type of logging selected.
There are a number of logging types and you can find them in the
source at <file:drivers/scsi/scsi_logging.h>. The logging levels
are also described in that file and they determine the verbosity of
the logging for each logging type.
If you say N here, it may be harder to track down some types of [31mCONFIG_SCSI[0m
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.
config [31mCONFIG_SCSI_SCAN_ASYNC[0m
bool "Asynchronous SCSI scanning"
depends on [31mCONFIG_SCSI[0m
help
The [31mCONFIG_SCSI[0m subsystem can probe for devices while the rest of the
system continues booting, and even probe devices on different
busses in parallel, leading to a significant speed-up.
You can override this choice by specifying "scsi_mod.scan=sync"
or async on the kernel's command line.
Note that this setting also affects whether resuming from
system suspend will be performed asynchronously.
menu "SCSI Transports"
depends on [31mCONFIG_SCSI[0m
config [31mCONFIG_SCSI_SPI_ATTRS[0m
tristate "Parallel SCSI (SPI) Transport Attributes"
depends on [31mCONFIG_SCSI[0m
help
If you wish to export transport-specific information about
each attached [31mCONFIG_SCSI[0m device to sysfs, say Y. Otherwise, say N.
config [31mCONFIG_SCSI_FC_ATTRS[0m
tristate "FiberChannel Transport Attributes"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_NET[0m
select [31mCONFIG_BLK_DEV_BSGLIB[0m
select [31mCONFIG_SCSI_NETLINK[0m
help
If you wish to export transport-specific information about
each attached FiberChannel device to sysfs, say Y.
Otherwise, say N.
config [31mCONFIG_SCSI_ISCSI_ATTRS[0m
tristate "iSCSI Transport Attributes"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_NET[0m
select [31mCONFIG_BLK_DEV_BSGLIB[0m
help
If you wish to export transport-specific information about
each attached iSCSI device to sysfs, say Y.
Otherwise, say N.
config [31mCONFIG_SCSI_SAS_ATTRS[0m
tristate "SAS Transport Attributes"
depends on [31mCONFIG_SCSI[0m
select [31mCONFIG_BLK_DEV_BSG[0m
help
If you wish to export transport-specific information about
each attached SAS device to sysfs, say Y.
source "drivers/scsi/libsas/Kconfig"
config [31mCONFIG_SCSI_SRP_ATTRS[0m
tristate "SRP Transport Attributes"
depends on [31mCONFIG_SCSI[0m
help
If you wish to export transport-specific information about
each attached SRP device to sysfs, say Y.
endmenu
menuconfig [31mCONFIG_SCSI_LOWLEVEL[0m
bool "SCSI low-level drivers"
depends on [31mCONFIG_SCSI[0m!=n
default y
if [31mCONFIG_SCSI_LOWLEVEL[0m && [31mCONFIG_SCSI[0m
config [31mCONFIG_ISCSI_TCP[0m
tristate "iSCSI Initiator over TCP/IP"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_INET[0m
select [31mCONFIG_CRYPTO[0m
select [31mCONFIG_CRYPTO_MD5[0m
select [31mCONFIG_CRYPTO_CRC32C[0m
select [31mCONFIG_SCSI_ISCSI_ATTRS[0m
help
The iSCSI Driver provides a host with the ability to access storage
through an IP network. The driver uses the iSCSI protocol to transport
[31mCONFIG_SCSI[0m requests and responses over a TCP/IP network between the host
(the "initiator") and "targets". Architecturally, the iSCSI driver
combines with the host's TCP/IP stack, network drivers, and Network
Interface Card (NIC) to provide the same functions as a [31mCONFIG_SCSI[0m or a
Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called iscsi_tcp.
The userspace component needed to initialize the driver, documentation,
and sample configuration files can be found here:
http://open-iscsi.org
config [31mCONFIG_ISCSI_BOOT_SYSFS[0m
tristate "iSCSI Boot Sysfs Interface"
default n
help
This option enables support for exposing iSCSI boot information
via sysfs to userspace. If you wish to export this information,
say Y. Otherwise, say N.
source "drivers/scsi/cxgbi/Kconfig"
source "drivers/scsi/bnx2i/Kconfig"
source "drivers/scsi/bnx2fc/Kconfig"
source "drivers/scsi/be2iscsi/Kconfig"
source "drivers/scsi/cxlflash/Kconfig"
config [31mCONFIG_SGIWD93_SCSI[0m
tristate "SGI WD93C93 SCSI Driver"
depends on [31mCONFIG_SGI_HAS_WD93[0m && [31mCONFIG_SCSI[0m
help
If you have a Western Digital WD93 [31mCONFIG_SCSI[0m controller on
an SGI [31mCONFIG_MIPS[0m system, say Y. Otherwise, say N.
config [31mCONFIG_BLK_DEV_3W_XXXX_RAID[0m
tristate "3ware 5/6/7/8xxx ATA-RAID support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
3ware is the only hardware [31mCONFIG_ATA[0m-Raid product in Linux to date.
This card is 2,4, or 8 channel master mode support only.
[31mCONFIG_SCSI[0m support required!!!
<http://www.3ware.com/>
Please read the comments at the top of
<file:drivers/scsi/3w-xxxx.c>.
config [31mCONFIG_SCSI_HPSA[0m
tristate "HP Smart Array SCSI driver"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_CHECK_SIGNATURE[0m
select [31mCONFIG_SCSI_SAS_ATTRS[0m
help
This driver supports HP Smart Array Controllers (circa 2009).
It is a [31mCONFIG_SCSI[0m alternative to the cciss driver, which is a block
driver. Anyone wishing to use HP Smart Array controllers who
would prefer the devices be presented to linux as [31mCONFIG_SCSI[0m devices,
rather than as generic block devices should say Y here.
config [31mCONFIG_SCSI_3W_9XXX[0m
tristate "3ware 9xxx SATA-RAID support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This driver supports the 9000 series 3ware SATA-RAID cards.
<http://www.amcc.com>
Please read the comments at the top of
<file:drivers/scsi/3w-9xxx.c>.
config [31mCONFIG_SCSI_3W_SAS[0m
tristate "3ware 97xx SAS/SATA-RAID support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
<http://www.lsi.com>
Please read the comments at the top of
<file:drivers/scsi/3w-sas.c>.
config [31mCONFIG_SCSI_ACARD[0m
tristate "ACARD SCSI support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This driver supports the ACARD [31mCONFIG_SCSI[0m host adapter.
Support Chip <ATP870 ATP876 ATP880 ATP885>
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called atp870u.
config [31mCONFIG_SCSI_AHA152X[0m
tristate "Adaptec AHA152X/2825 support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
select [31mCONFIG_CHECK_SIGNATURE[0m
---help---
This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
[31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. You might also want to
read the file <file:Documentation/scsi/aha152x.txt>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called aha152x.
config [31mCONFIG_SCSI_AHA1542[0m
tristate "Adaptec AHA1542 support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_ISA_DMA_API[0m
---help---
This is support for a [31mCONFIG_SCSI[0m host adapter. It is explained in section
3.4 of the [31mCONFIG_SCSI[0m-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>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called aha1542.
config [31mCONFIG_SCSI_AHA1740[0m
tristate "Adaptec AHA1740 support"
depends on [31mCONFIG_EISA[0m && [31mCONFIG_SCSI[0m
---help---
This is support for a [31mCONFIG_SCSI[0m host adapter. It is explained in section
3.5 of the [31mCONFIG_SCSI[0m-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>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called aha1740.
config [31mCONFIG_SCSI_AACRAID[0m
tristate "Adaptec AACRAID support"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PCI[0m
help
This driver supports a variety of Dell, HP, Adaptec, IBM and
ICP storage products. For a list of supported products, refer
to <file:Documentation/scsi/aacraid.txt>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called aacraid.
source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
source "drivers/scsi/aic94xx/Kconfig"
source "drivers/scsi/hisi_sas/Kconfig"
source "drivers/scsi/mvsas/Kconfig"
config [31mCONFIG_SCSI_MVUMI[0m
tristate "Marvell UMI driver"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PCI[0m
help
Module for Marvell Universal Message Interface(UMI) driver
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mvumi.
config [31mCONFIG_SCSI_DPT_I2O[0m
tristate "Adaptec I2O RAID support "
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PCI[0m && [31mCONFIG_VIRT_TO_BUS[0m
help
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:Documentation/scsi/dpti.txt>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called dpt_i2o.
config [31mCONFIG_SCSI_ADVANSYS[0m
tristate "AdvanSys SCSI support"
depends on [31mCONFIG_SCSI[0m
depends on [31mCONFIG_ISA[0m || [31mCONFIG_EISA[0m || [31mCONFIG_PCI[0m
depends on [31mCONFIG_ISA_DMA_API[0m || ![31mCONFIG_ISA[0m
help
This is a driver for all [31mCONFIG_SCSI[0m host adapters manufactured by
AdvanSys. It is documented in the kernel source in
<file:drivers/scsi/advansys.c>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called advansys.
config [31mCONFIG_SCSI_ARCMSR[0m
tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This driver supports all of ARECA's SATA/SAS RAID controller cards.
This is an ARECA-maintained driver by Erich Chen.
If you have any problems, please mail to: <erich@areca.com.tw>.
Areca supports Linux RAID config tools.
Please link <http://www.areca.com.tw>
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called arcmsr (modprobe arcmsr).
source "drivers/scsi/esas2r/Kconfig"
source "drivers/scsi/megaraid/Kconfig.megaraid"
source "drivers/scsi/mpt3sas/Kconfig"
source "drivers/scsi/smartpqi/Kconfig"
source "drivers/scsi/ufs/Kconfig"
config [31mCONFIG_SCSI_HPTIOP[0m
tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PCI[0m
help
This option enables support for HighPoint RocketRAID 3xxx/4xxx
controllers.
To compile this driver as a module, choose [31mCONFIG_M[0m here; the module
will be called hptiop. If unsure, say N.
config [31mCONFIG_SCSI_BUSLOGIC[0m
tristate "BusLogic SCSI support"
depends on ([31mCONFIG_PCI[0m || [31mCONFIG_ISA[0m || [31mCONFIG_MCA[0m) && [31mCONFIG_SCSI[0m && [31mCONFIG_ISA_DMA_API[0m && [31mCONFIG_VIRT_TO_BUS[0m
---help---
This is support for BusLogic MultiMaster and FlashPoint [31mCONFIG_SCSI[0m Host
Adapters. Consult the [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and the files
<file:Documentation/scsi/BusLogic.txt> and
<file:Documentation/scsi/FlashPoint.txt> for more information.
Note that support for FlashPoint is only available for 32-bit
x86 configurations.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called BusLogic.
config [31mCONFIG_SCSI_FLASHPOINT[0m
bool "FlashPoint support"
depends on [31mCONFIG_SCSI_BUSLOGIC[0m && [31mCONFIG_PCI[0m
help
This option allows you to add FlashPoint support to the
BusLogic [31mCONFIG_SCSI[0m driver. The FlashPoint SCCB Manager code is
substantial, so users of MultiMaster Host Adapters may not
wish to include it.
config [31mCONFIG_VMWARE_PVSCSI[0m
tristate "VMware PVSCSI driver support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_X86[0m
help
This driver supports VMware's para virtualized [31mCONFIG_SCSI[0m HBA.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called vmw_pvscsi.
config [31mCONFIG_XEN_SCSI_FRONTEND[0m
tristate "XEN SCSI frontend driver"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_XEN[0m
select [31mCONFIG_XEN_XENBUS_FRONTEND[0m
help
The [31mCONFIG_XEN[0m [31mCONFIG_SCSI[0m frontend driver allows the kernel to access [31mCONFIG_SCSI[0m Devices
within another guest OS (usually Dom0).
Only needed if the kernel is running in a [31mCONFIG_XEN[0m guest and generic
[31mCONFIG_SCSI[0m access to a device is needed.
config [31mCONFIG_HYPERV_STORAGE[0m
tristate "Microsoft Hyper-V virtual storage driver"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_HYPERV[0m
depends on m || [31mCONFIG_SCSI_FC_ATTRS[0m != m
default [31mCONFIG_HYPERV[0m
help
Select this option to enable the Hyper-V virtual storage driver.
config [31mCONFIG_LIBFC[0m
tristate "LibFC module"
depends on [31mCONFIG_SCSI_FC_ATTRS[0m
select [31mCONFIG_CRC32[0m
---help---
Fibre Channel library module
config [31mCONFIG_LIBFCOE[0m
tristate "LibFCoE module"
depends on [31mCONFIG_LIBFC[0m
---help---
Library for Fibre Channel over Ethernet module
config [31mCONFIG_FCOE[0m
tristate "FCoE module"
depends on [31mCONFIG_PCI[0m
depends on [31mCONFIG_LIBFCOE[0m
---help---
Fibre Channel over Ethernet module
config [31mCONFIG_FCOE_FNIC[0m
tristate "Cisco FNIC Driver"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_X86[0m
depends on [31mCONFIG_LIBFCOE[0m
help
This is support for the Cisco [31mCONFIG_PCI[0m-Express FCoE HBA.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called fnic.
config [31mCONFIG_SCSI_SNIC[0m
tristate "Cisco SNIC Driver"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This is support for the Cisco [31mCONFIG_PCI[0m-Express [31mCONFIG_SCSI[0m HBA.
To compile this driver as a module, choose [31mCONFIG_M[0m here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called snic.
config [31mCONFIG_SCSI_SNIC_DEBUG_FS[0m
bool "Cisco SNIC Driver Debugfs Support"
depends on [31mCONFIG_SCSI_SNIC[0m && [31mCONFIG_DEBUG_FS[0m
help
This enables to list debugging information from SNIC Driver
available via debugfs file system
config [31mCONFIG_SCSI_DMX3191D[0m
tristate "DMX3191D SCSI support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is support for Domex DMX3191D [31mCONFIG_SCSI[0m Host Adapters.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called dmx3191d.
config [31mCONFIG_SCSI_EATA[0m
tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
depends on ([31mCONFIG_ISA[0m || [31mCONFIG_EISA[0m || [31mCONFIG_PCI[0m) && [31mCONFIG_SCSI[0m && [31mCONFIG_ISA_DMA_API[0m
---help---
This driver supports all EATA/DMA-compliant [31mCONFIG_SCSI[0m host adapters. DPT
[31mCONFIG_ISA[0m and all [31mCONFIG_EISA[0m I/O addresses are probed looking for the "EATA"
signature. The addresses of all the [31mCONFIG_PCI[0m [31mCONFIG_SCSI[0m controllers reported
by the [31mCONFIG_PCI[0m subsystem are probed as well.
You want to read the start of <file:drivers/scsi/eata.c> and the
[31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called eata.
config [31mCONFIG_SCSI_EATA_TAGGED_QUEUE[0m
bool "enable tagged command queueing"
depends on [31mCONFIG_SCSI_EATA[0m
help
This is a feature of [31mCONFIG_SCSI[0m-2 which improves performance: the host
adapter can send several [31mCONFIG_SCSI[0m commands to a device's queue even if
previous commands haven't finished yet.
This is equivalent to the "eata=tc:y" boot option.
config [31mCONFIG_SCSI_EATA_LINKED_COMMANDS[0m
bool "enable elevator sorting"
depends on [31mCONFIG_SCSI_EATA[0m
help
This option enables elevator sorting for all probed [31mCONFIG_SCSI[0m 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...
This is equivalent to the "eata=lc:y" boot option.
config [31mCONFIG_SCSI_EATA_MAX_TAGS[0m
int "maximum number of queued commands"
depends on [31mCONFIG_SCSI_EATA[0m
default "16"
help
This specifies how many [31mCONFIG_SCSI[0m commands can be maximally queued for
each probed [31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m device is reported at boot time.
This is equivalent to the "eata=mq:8" boot option.
config [31mCONFIG_SCSI_EATA_PIO[0m
tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
depends on ([31mCONFIG_ISA[0m || [31mCONFIG_EISA[0m || [31mCONFIG_PCI[0m) && [31mCONFIG_SCSI[0m && [31mCONFIG_BROKEN[0m
---help---
This driver supports all EATA-PIO protocol compliant [31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called eata_pio.
config [31mCONFIG_SCSI_FUTURE_DOMAIN[0m
tristate "Future Domain 16xx SCSI/AHA-2920A support"
depends on ([31mCONFIG_ISA[0m || [31mCONFIG_PCI[0m) && [31mCONFIG_SCSI[0m
select [31mCONFIG_CHECK_SIGNATURE[0m
---help---
This is support for Future Domain's 16-bit [31mCONFIG_SCSI[0m host adapters
(TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
other adapters based on the Future Domain chipsets (Quantum
[31mCONFIG_ISA[0m-200S, [31mCONFIG_ISA[0m-250MG; Adaptec AHA-2920A; and at least one IBM board).
It is explained in section 3.7 of the [31mCONFIG_SCSI[0m-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.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called fdomain.
config [31mCONFIG_SCSI_GDTH[0m
tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
depends on ([31mCONFIG_ISA[0m || [31mCONFIG_EISA[0m || [31mCONFIG_PCI[0m) && [31mCONFIG_SCSI[0m && [31mCONFIG_ISA_DMA_API[0m
---help---
Formerly called GDT [31mCONFIG_SCSI[0m Disk Array Controller Support.
This is a driver for RAID/[31mCONFIG_SCSI[0m Disk Array Controllers ([31mCONFIG_EISA[0m/[31mCONFIG_ISA[0m/[31mCONFIG_PCI[0m)
manufactured by Intel Corporation/ICP vortex GmbH. It is documented
in the kernel source in <file:drivers/scsi/gdth.c> and
<file:drivers/scsi/gdth.h>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called gdth.
config [31mCONFIG_SCSI_ISCI[0m
tristate "Intel(R) C600 Series Chipset SAS Controller"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
depends on [31mCONFIG_X86[0m
select [31mCONFIG_SCSI_SAS_LIBSAS[0m
---help---
This driver supports the 6Gb/s SAS capabilities of the storage
control unit found in the Intel(R) C600 series chipset.
config [31mCONFIG_SCSI_GENERIC_NCR5380[0m
tristate "Generic NCR5380/53c400 SCSI ISA card support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_HAS_IOPORT_MAP[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
---help---
This is a driver for old [31mCONFIG_ISA[0m card [31mCONFIG_SCSI[0m controllers based on a
NCR 5380, 53C80, 53C400, 53C400A, or [31mCONFIG_DTC[0m 436 device.
Most boards such as the Trantor T130 fit this category, as do
various 8-bit and 16-bit [31mCONFIG_ISA[0m cards bundled with [31mCONFIG_SCSI[0m scanners.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called g_NCR5380.
config [31mCONFIG_SCSI_IPS[0m
tristate "IBM ServeRAID support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
---help---
This is support for the IBM ServeRAID hardware RAID controllers.
See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
for more information. If this driver does not work correctly
without modification please contact the author by email at
<ipslinux@adaptec.com>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ips.
config [31mCONFIG_SCSI_IBMVSCSI[0m
tristate "IBM Virtual SCSI support"
depends on [31mCONFIG_PPC_PSERIES[0m
select [31mCONFIG_SCSI_SRP_ATTRS[0m
help
This is the IBM POWER Virtual [31mCONFIG_SCSI[0m Client
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ibmvscsi.
config [31mCONFIG_SCSI_IBMVSCSIS[0m
tristate "IBM Virtual SCSI Server support"
depends on [31mCONFIG_PPC_PSERIES[0m && [31mCONFIG_TARGET_CORE[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_PCI[0m
help
This is the IBM POWER Virtual [31mCONFIG_SCSI[0m Target Server
This driver uses the SRP protocol for communication betwen servers
guest and/or the host that run on the same server.
More information on VSCSI protocol can be found at www.power.org
The userspace configuration needed to initialize the driver can be
be found here:
https://github.com/powervm/ibmvscsis/wiki/Configuration
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ibmvscsis.
config [31mCONFIG_SCSI_IBMVFC[0m
tristate "IBM Virtual FC support"
depends on [31mCONFIG_PPC_PSERIES[0m && [31mCONFIG_SCSI[0m
depends on [31mCONFIG_SCSI_FC_ATTRS[0m
help
This is the IBM POWER Virtual FC Client
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ibmvfc.
config [31mCONFIG_SCSI_IBMVFC_TRACE[0m
bool "enable driver internal trace"
depends on [31mCONFIG_SCSI_IBMVFC[0m
default y
help
If you say Y here, the driver will trace all commands issued
to the adapter. Performance impact is minimal. Trace can be
dumped using /sys/class/scsi_host/hostXX/trace.
config [31mCONFIG_SCSI_INITIO[0m
tristate "Initio 9100U(W) support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This is support for the Initio 91XXU(W) [31mCONFIG_SCSI[0m host adapter. Please
read the [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called initio.
config [31mCONFIG_SCSI_INIA100[0m
tristate "Initio INI-A100U2W support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
This is support for the Initio INI-A100U2W [31mCONFIG_SCSI[0m host adapter.
Please read the [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called a100u2w.
config [31mCONFIG_SCSI_PPA[0m
tristate "IOMEGA parallel port (ppa - older drives)"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PARPORT_PC[0m
---help---
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 [31mCONFIG_SCSI[0m 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:Documentation/scsi/ppa.txt>. You should also read
the [31mCONFIG_SCSI[0m-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.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ppa.
config [31mCONFIG_SCSI_IMM[0m
tristate "IOMEGA parallel port (imm - newer drives)"
depends on [31mCONFIG_SCSI[0m && [31mCONFIG_PARPORT_PC[0m
---help---
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 [31mCONFIG_SCSI[0m 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:Documentation/scsi/ppa.txt>. You should also read
the [31mCONFIG_SCSI[0m-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.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called imm.
config [31mCONFIG_SCSI_IZIP_EPP16[0m
bool "ppa/imm option - Use slow (but safe) EPP-16"
depends on [31mCONFIG_SCSI_PPA[0m || [31mCONFIG_SCSI_IMM[0m
---help---
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.
config [31mCONFIG_SCSI_IZIP_SLOW_CTR[0m
bool "ppa/imm option - Assume slow parport control register"
depends on [31mCONFIG_SCSI_PPA[0m || [31mCONFIG_SCSI_IMM[0m
help
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.
config [31mCONFIG_SCSI_NCR53C406A[0m
tristate "NCR53c406a SCSI support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m
help
This is support for the NCR53c406a [31mCONFIG_SCSI[0m host adapter. For user
configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
in the kernel source. Also read the [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called NCR53c406.
config [31mCONFIG_SCSI_NCR_D700[0m
tristate "NCR Dual 700 MCA SCSI support"
depends on [31mCONFIG_MCA[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
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 [31mCONFIG_SCSI[0m card, so say N.
config [31mCONFIG_SCSI_LASI700[0m
tristate "HP Lasi SCSI support for 53c700/710"
depends on [31mCONFIG_GSC[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is a driver for the [31mCONFIG_SCSI[0m controller in the Lasi chip found in
many PA-RISC workstations & servers. If you do not know whether you
have a Lasi chip, it is safe to say "Y" here.
config [31mCONFIG_SCSI_SNI_53C710[0m
tristate "SNI RM SCSI support for 53c710"
depends on [31mCONFIG_SNI_RM[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
select [31mCONFIG_53C700_LE_ON_BE[0m
help
This is a driver for the onboard [31mCONFIG_SCSI[0m controller found in older
SNI RM workstations & servers.
config [31mCONFIG_53C700_LE_ON_BE[0m
bool
depends on [31mCONFIG_SCSI_LASI700[0m
default y
config [31mCONFIG_SCSI_STEX[0m
tristate "Promise SuperTrak EX Series support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
---help---
This driver supports Promise SuperTrak EX series storage controllers.
Promise provides Linux RAID configuration utility for these
controllers. Please visit <http://www.promise.com> to download.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called stex.
config [31mCONFIG_53C700_BE_BUS[0m
bool
depends on [31mCONFIG_SCSI_A4000T[0m || [31mCONFIG_SCSI_ZORRO7XX[0m || [31mCONFIG_MVME16x_SCSI[0m || [31mCONFIG_BVME6000_SCSI[0m
default y
config [31mCONFIG_SCSI_SYM53C8XX_2[0m
tristate "SYM53C8XX Version 2 SCSI support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
---help---
This driver supports the whole NCR53C8XX/SYM53C8XX family of
[31mCONFIG_PCI[0m-[31mCONFIG_SCSI[0m 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 [31mCONFIG_PCI[0m-X [31mCONFIG_SCSI[0m
controllers; you need to use the Fusion MPT driver for that.
Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
information.
config [31mCONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE[0m
int "DMA addressing mode"
depends on [31mCONFIG_SCSI_SYM53C8XX_2[0m
default "1"
---help---
This option only applies to [31mCONFIG_PCI[0m-[31mCONFIG_SCSI[0m chips that are [31mCONFIG_PCI[0m DAC
capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
When set to 0, the driver will program the chip to only perform
32-bit DMA. When set to 1, the chip will be able to perform DMA
to addresses up to 1TB. When set to 2, the driver supports the
full 64-bit DMA address range, but can only address 16 segments
of 4 GB each. This limits the total addressable range to 64 GB.
Most machines with less than 4GB of memory should use a setting
of 0 for best performance. If your machine has 4GB of memory
or more, you should set this option to 1 (the default).
The still experimental value 2 (64 bit DMA addressing with 16
x 4GB segments limitation) can be used on systems that require
[31mCONFIG_PCI[0m address bits past bit 39 to be set for the addressing of
memory using [31mCONFIG_PCI[0m DAC cycles.
config [31mCONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS[0m
int "Default tagged command queue depth"
depends on [31mCONFIG_SCSI_SYM53C8XX_2[0m
default "16"
help
This is the default value of the command queue depth the
driver will announce to the generic [31mCONFIG_SCSI[0m 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.
config [31mCONFIG_SCSI_SYM53C8XX_MAX_TAGS[0m
int "Maximum number of queued commands"
depends on [31mCONFIG_SCSI_SYM53C8XX_2[0m
default "64"
help
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.
config [31mCONFIG_SCSI_SYM53C8XX_MMIO[0m
bool "Use memory mapped IO"
depends on [31mCONFIG_SCSI_SYM53C8XX_2[0m
default y
help
Memory mapped IO is faster than Port IO. Most people should
answer Y here, but some machines may have problems. If you have
to answer N here, please report the problem to the maintainer.
config [31mCONFIG_SCSI_IPR[0m
tristate "IBM Power Linux RAID adapter support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_ATA[0m
select [31mCONFIG_FW_LOADER[0m
select [31mCONFIG_IRQ_POLL[0m
---help---
This driver supports the IBM Power Linux family RAID adapters.
This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
as IBM iSeries 5702, 5703, 5709, and 570A.
config [31mCONFIG_SCSI_IPR_TRACE[0m
bool "enable driver internal trace"
depends on [31mCONFIG_SCSI_IPR[0m
default y
help
If you say Y here, the driver will trace all commands issued
to the adapter. Performance impact is minimal. Trace can be
dumped using /sys/bus/class/scsi_host/hostXX/trace.
config [31mCONFIG_SCSI_IPR_DUMP[0m
bool "enable adapter dump support"
depends on [31mCONFIG_SCSI_IPR[0m
default y
help
If you say Y here, the driver will support adapter crash dump.
If you enable this support, the iprdump daemon can be used
to capture adapter failure analysis information.
config [31mCONFIG_SCSI_ZALON[0m
tristate "Zalon SCSI support"
depends on [31mCONFIG_GSC[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
The Zalon is a [31mCONFIG_GSC[0m/HSC bus interface chip that sits between the
PA-RISC processor and the NCR 53c720 [31mCONFIG_SCSI[0m controller on C100,
C110, J200, J210 and some [31mCONFIG_D[0m, K & R-class machines. It's also
used on the add-in Bluefish, Barracuda & Shrike [31mCONFIG_SCSI[0m cards.
Say Y here if you have one of these machines or cards.
config [31mCONFIG_SCSI_NCR_Q720[0m
tristate "NCR Quad 720 MCA SCSI support"
depends on [31mCONFIG_MCA[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is a driver for the MicroChannel Quad 720 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 [31mCONFIG_SCSI[0m card, so say N.
config [31mCONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS[0m
int "default tagged command queue depth"
depends on [31mCONFIG_SCSI_ZALON[0m || [31mCONFIG_SCSI_NCR_Q720[0m
default "8"
---help---
"Tagged command queuing" is a feature of [31mCONFIG_SCSI[0m-2 which improves
performance: the host adapter can send several [31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m
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 [31mCONFIG_SCSI[0m devices.
config [31mCONFIG_SCSI_NCR53C8XX_MAX_TAGS[0m
int "maximum number of queued commands"
depends on [31mCONFIG_SCSI_ZALON[0m || [31mCONFIG_SCSI_NCR_Q720[0m
default "32"
---help---
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.
config [31mCONFIG_SCSI_NCR53C8XX_SYNC[0m
int "synchronous transfers frequency in MHz"
depends on [31mCONFIG_SCSI_ZALON[0m || [31mCONFIG_SCSI_NCR_Q720[0m
default "20"
---help---
The [31mCONFIG_SCSI[0m 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 [31mCONFIG_SCSI[0m
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 [31mCONFIG_NVRAM[0m,
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 [31mCONFIG_SCSI[0m devices, you should come back and decrease the value.
There is no safe option other than using good cabling, right
terminations and [31mCONFIG_SCSI[0m conformant devices.
config [31mCONFIG_SCSI_NCR53C8XX_NO_DISCONNECT[0m
bool "not allow targets to disconnect"
depends on ([31mCONFIG_SCSI_ZALON[0m || [31mCONFIG_SCSI_NCR_Q720[0m) && [31mCONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS[0m=0
help
This option is only provided for safety if you suspect some [31mCONFIG_SCSI[0m
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 [31mCONFIG_SCSI[0m bus. The normal answer therefore is N.
config [31mCONFIG_SCSI_QLOGIC_FAS[0m
tristate "Qlogic FAS SCSI support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m
---help---
This is a driver for the [31mCONFIG_ISA[0m, VLB, and [31mCONFIG_PCMCIA[0m versions of the Qlogic
FastSCSI! cards as well as any other card based on the FASXX chip
(including the Control Concepts [31mCONFIG_SCSI[0m/[31mCONFIG_IDE[0m/SIO/PIO/FDC cards).
This driver does NOT support the [31mCONFIG_PCI[0m versions of these cards. The
[31mCONFIG_PCI[0m versions are supported by the Qlogic ISP driver ("Qlogic ISP
SCSI support"), below.
Information about this driver is contained in
<file:Documentation/scsi/qlogicfas.txt>. You should also read the
[31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called qlogicfas.
config [31mCONFIG_SCSI_QLOGIC_1280[0m
tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
help
Say Y if you have a QLogic ISP1240/1x80/1x160 [31mCONFIG_SCSI[0m host adapter.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called qla1280.
config [31mCONFIG_SCSI_QLOGICPTI[0m
tristate "PTI Qlogic, ISP Driver"
depends on [31mCONFIG_SBUS[0m && [31mCONFIG_SCSI[0m
help
This driver supports [31mCONFIG_SBUS[0m [31mCONFIG_SCSI[0m controllers from PTI or QLogic. These
controllers are known under Solaris as qpti and in the openprom as
PTI,ptisp or QLGC,isp. Note that [31mCONFIG_PCI[0m QLogic [31mCONFIG_SCSI[0m controllers are
driven by a different driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called qlogicpti.
source "drivers/scsi/qla2xxx/Kconfig"
source "drivers/scsi/qla4xxx/Kconfig"
source "drivers/scsi/qedi/Kconfig"
config [31mCONFIG_SCSI_LPFC[0m
tristate "Emulex LightPulse Fibre Channel Support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
depends on [31mCONFIG_SCSI_FC_ATTRS[0m
select [31mCONFIG_CRC_T10DIF[0m
help
This lpfc driver supports the Emulex LightPulse
Family of Fibre Channel [31mCONFIG_PCI[0m host adapters.
config [31mCONFIG_SCSI_LPFC_DEBUG_FS[0m
bool "Emulex LightPulse Fibre Channel debugfs Support"
depends on [31mCONFIG_SCSI_LPFC[0m && [31mCONFIG_DEBUG_FS[0m
help
This makes debugging information from the lpfc driver
available via the debugfs filesystem.
config [31mCONFIG_SCSI_SIM710[0m
tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
depends on ([31mCONFIG_EISA[0m || [31mCONFIG_MCA[0m) && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
---help---
This driver is for NCR53c710 based [31mCONFIG_SCSI[0m host adapters.
It currently supports Compaq [31mCONFIG_EISA[0m cards and NCR [31mCONFIG_MCA[0m cards
config [31mCONFIG_SCSI_SYM53C416[0m
tristate "Symbios 53c416 SCSI support"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_SCSI[0m
---help---
This is support for the sym53c416 [31mCONFIG_SCSI[0m host adapter, the [31mCONFIG_SCSI[0m
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>]
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sym53c416.
config [31mCONFIG_SCSI_DC395x[0m
tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
---help---
This driver supports [31mCONFIG_PCI[0m [31mCONFIG_SCSI[0m host adapters based on the ASIC
TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
This driver works, but is still in experimental status. So better
have a bootable disk and a backup in case of emergency.
Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called dc395x.
config [31mCONFIG_SCSI_AM53C974[0m
tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
---help---
This driver supports [31mCONFIG_PCI[0m [31mCONFIG_SCSI[0m host adapters based on the Am53C974A
chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
PCscsi/PCnet (Am53/79C974) solutions.
This is a new implementation base on the generic esp_scsi driver.
Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
Note that this driver does NOT support Tekram DC390W/U/F, which are
based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called am53c974.
config [31mCONFIG_SCSI_NSP32[0m
tristate "Workbit NinjaSCSI-32Bi/UDE support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m && ![31mCONFIG_64BIT[0m
help
This is support for the Workbit NinjaSCSI-32Bi/UDE [31mCONFIG_PCI[0m/Cardbus
[31mCONFIG_SCSI[0m host adapter. Please read the [31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called nsp32.
config [31mCONFIG_SCSI_WD719X[0m
tristate "Western Digital WD7193/7197/7296 support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_EEPROM_93CX6[0m
---help---
This is a driver for Western Digital WD7193, WD7197 and WD7296 [31mCONFIG_PCI[0m
[31mCONFIG_SCSI[0m controllers (based on WD33C296A chip).
config [31mCONFIG_SCSI_DEBUG[0m
tristate "SCSI debugging host and device simulator"
depends on [31mCONFIG_SCSI[0m
select [31mCONFIG_CRC_T10DIF[0m
help
This pseudo driver simulates one or more hosts ([31mCONFIG_SCSI[0m initiators),
each with one or more targets, each with one or more logical units.
Defaults to one of each, creating a small RAM disk device. Many
parameters found in the /sys/bus/pseudo/drivers/scsi_debug
directory can be tweaked at run time.
See <http://sg.danny.cz/sg/sdebug26.html> for more information.
Mainly used for testing and best as a module. If unsure, say N.
config [31mCONFIG_SCSI_MESH[0m
tristate "MESH (Power Mac internal SCSI) support"
depends on [31mCONFIG_PPC32[0m && [31mCONFIG_PPC_PMAC[0m && [31mCONFIG_SCSI[0m
help
Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
[31mCONFIG_SCSI[0m Hardware) [31mCONFIG_SCSI[0m bus adaptor (the 7200 doesn't, but all of the
other Power Macintoshes do). Say Y to include support for this [31mCONFIG_SCSI[0m
adaptor.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mesh.
config [31mCONFIG_SCSI_MESH_SYNC_RATE[0m
int "maximum synchronous transfer rate (MB/s) (0 = async)"
depends on [31mCONFIG_SCSI_MESH[0m
default "5"
help
On Power Macintoshes (and clones) where the MESH [31mCONFIG_SCSI[0m bus adaptor
drives a bus which is entirely internal to the machine (such as the
7500, 7600, 8500, etc.), the MESH is capable of synchronous
operation at up to 10 MB/s. On machines where the [31mCONFIG_SCSI[0m bus
controlled by the MESH can have external devices connected, it is
usually rated at 5 MB/s. 5 is a safe value here unless you know the
MESH [31mCONFIG_SCSI[0m bus is internal only; in that case you can say 10. Say 0
to disable synchronous operation.
config [31mCONFIG_SCSI_MESH_RESET_DELAY_MS[0m
int "initial bus reset delay (ms) (0 = no reset)"
depends on [31mCONFIG_SCSI_MESH[0m
default "4000"
config [31mCONFIG_SCSI_MAC53C94[0m
tristate "53C94 (Power Mac external SCSI) support"
depends on [31mCONFIG_PPC32[0m && [31mCONFIG_PPC_PMAC[0m && [31mCONFIG_SCSI[0m
help
On Power Macintoshes (and clones) with two [31mCONFIG_SCSI[0m buses, the external
[31mCONFIG_SCSI[0m bus is usually controlled by a 53C94 [31mCONFIG_SCSI[0m bus adaptor. Older
machines which only have one [31mCONFIG_SCSI[0m bus, such as the 7200, also use
the 53C94. Say Y to include support for the 53C94.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mac53c94.
source "drivers/scsi/arm/Kconfig"
config [31mCONFIG_JAZZ_ESP[0m
bool "MIPS JAZZ FAS216 SCSI support"
depends on [31mCONFIG_MACH_JAZZ[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is the driver for the onboard [31mCONFIG_SCSI[0m host adapter of [31mCONFIG_MIPS[0m Magnum
4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
systems.
config [31mCONFIG_A3000_SCSI[0m
tristate "A3000 WD33C93A support"
depends on [31mCONFIG_AMIGA[0m && [31mCONFIG_SCSI[0m
help
If you have an Amiga 3000 and have [31mCONFIG_SCSI[0m devices connected to the
built-in [31mCONFIG_SCSI[0m controller, say Y. Otherwise, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called a3000.
config [31mCONFIG_A2091_SCSI[0m
tristate "A2091/A590 WD33C93A support"
depends on [31mCONFIG_ZORRO[0m && [31mCONFIG_SCSI[0m
help
If you have a Commodore A2091 [31mCONFIG_SCSI[0m controller, say Y. Otherwise,
say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called a2091.
config [31mCONFIG_GVP11_SCSI[0m
tristate "GVP Series II WD33C93A support"
depends on [31mCONFIG_ZORRO[0m && [31mCONFIG_SCSI[0m
---help---
If you have a Great Valley Products Series II [31mCONFIG_SCSI[0m controller,
answer Y. Also say Y if you have a later model of GVP [31mCONFIG_SCSI[0m
controller (such as the GVP A4008 or a Combo board). Otherwise,
answer N. This driver does NOT work for the T-Rex series of
accelerators from TekMagic and GVP-[31mCONFIG_M[0m.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called gvp11.
config [31mCONFIG_SCSI_A4000T[0m
tristate "A4000T NCR53c710 SCSI support"
depends on [31mCONFIG_AMIGA[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
If you have an Amiga 4000T and have [31mCONFIG_SCSI[0m devices connected to the
built-in [31mCONFIG_SCSI[0m controller, say Y. Otherwise, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called a4000t.
config [31mCONFIG_SCSI_ZORRO7XX[0m
tristate "Zorro NCR53c710 SCSI support"
depends on [31mCONFIG_ZORRO[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
Support for various NCR53c710-based [31mCONFIG_SCSI[0m controllers on Zorro
expansion boards for the Amiga.
This includes:
- the Amiga 4091 Zorro III [31mCONFIG_SCSI[0m-2 controller,
- the MacroSystem Development's WarpEngine Amiga [31mCONFIG_SCSI[0m-2 controller
(info at
<http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
- the [31mCONFIG_SCSI[0m controller on the Phase5 Blizzard PowerUP 603e+
accelerator card for the Amiga 1200,
- the [31mCONFIG_SCSI[0m controller on the GVP Turbo 040/060 accelerator.
config [31mCONFIG_ATARI_SCSI[0m
tristate "Atari native SCSI support"
depends on [31mCONFIG_ATARI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
select [31mCONFIG_NVRAM[0m
---help---
If you have an Atari with built-in NCR5380 [31mCONFIG_SCSI[0m controller (TT,
Falcon, ...) say Y to get it supported. Of course also, if you have
a compatible [31mCONFIG_SCSI[0m controller (e.g. for Medusa).
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called atari_scsi.
This driver supports both styles of NCR integration into the
system: the TT style (separate DMA), and the Falcon style (via
ST-DMA, replacing ACSI). It does NOT support other schemes, like
in the Hades (without DMA).
config [31mCONFIG_MAC_SCSI[0m
tristate "Macintosh NCR5380 SCSI"
depends on [31mCONFIG_MAC[0m && [31mCONFIG_SCSI[0m=y
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is the NCR 5380 [31mCONFIG_SCSI[0m controller included on most of the 68030
based Macintoshes. If you have one of these say Y and read the
[31mCONFIG_SCSI[0m-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
config [31mCONFIG_SCSI_MAC_ESP[0m
tristate "Macintosh NCR53c9[46] SCSI"
depends on [31mCONFIG_MAC[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is the NCR 53c9x [31mCONFIG_SCSI[0m controller found on most of the 68040
based Macintoshes.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called mac_esp.
config [31mCONFIG_MVME147_SCSI[0m
bool "WD33C93 SCSI driver for MVME147"
depends on [31mCONFIG_MVME147[0m && [31mCONFIG_SCSI[0m=y
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
Support for the on-board [31mCONFIG_SCSI[0m controller on the Motorola [31mCONFIG_MVME147[0m
single-board computer.
config [31mCONFIG_MVME16x_SCSI[0m
tristate "NCR53C710 SCSI driver for MVME16x"
depends on [31mCONFIG_MVME16x[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
[31mCONFIG_SCSI[0m controller chip. Almost everyone using one of these boards
will want to say Y to this question.
config [31mCONFIG_BVME6000_SCSI[0m
tristate "NCR53C710 SCSI driver for BVME6000"
depends on [31mCONFIG_BVME6000[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
The BVME4000 and [31mCONFIG_BVME6000[0m boards from BVM Ltd use the NCR53C710
[31mCONFIG_SCSI[0m controller chip. Almost everyone using one of these boards
will want to say Y to this question.
config [31mCONFIG_SUN3_SCSI[0m
tristate "Sun3 NCR5380 SCSI"
depends on [31mCONFIG_SUN3[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This option will enable support for the OBIO (onboard io) NCR5380
[31mCONFIG_SCSI[0m controller found in the Sun 3/50 and 3/60, as well as for
"Sun3" type [31mCONFIG_VME[0m scsi controllers also based on the NCR5380.
General Linux information on the Sun 3 series (now discontinued)
is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
config [31mCONFIG_SUN3X_ESP[0m
bool "Sun3x ESP SCSI"
depends on [31mCONFIG_SUN3X[0m && [31mCONFIG_SCSI[0m=y
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
The ESP was an on-board [31mCONFIG_SCSI[0m controller used on Sun 3/80
machines. Say Y here to compile in support for it.
config [31mCONFIG_SCSI_SUNESP[0m
tristate "Sparc ESP Scsi Driver"
depends on [31mCONFIG_SBUS[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SPI_ATTRS[0m
help
This is the driver for the Sun ESP [31mCONFIG_SCSI[0m host adapter. The ESP
chipset is present in most [31mCONFIG_SPARC[0m [31mCONFIG_SBUS[0m-based computers and
supports the Emulex family of ESP [31mCONFIG_SCSI[0m chips (esp100, esp100A,
esp236, fas101, fas236) as well as the Qlogic fas366 [31mCONFIG_SCSI[0m chip.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sun_esp.
config [31mCONFIG_ZFCP[0m
tristate "FCP host bus adapter driver for IBM eServer zSeries"
depends on [31mCONFIG_S390[0m && [31mCONFIG_QDIO[0m && [31mCONFIG_SCSI[0m
depends on [31mCONFIG_SCSI_FC_ATTRS[0m
help
If you want to access [31mCONFIG_SCSI[0m devices attached to your IBM eServer
zSeries by means of Fibre Channel interfaces say Y.
For details please refer to the documentation provided by IBM at
<http://oss.software.ibm.com/developerworks/opensource/linux390>
This driver is also available as a module. This module will be
called zfcp. If you want to compile it as a module, say [31mCONFIG_M[0m here
and read <file:Documentation/kbuild/modules.txt>.
config [31mCONFIG_SCSI_PMCRAID[0m
tristate "PMC SIERRA Linux MaxRAID adapter support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_NET[0m
---help---
This driver supports the PMC SIERRA MaxRAID adapters.
config [31mCONFIG_SCSI_PM8001[0m
tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
select [31mCONFIG_SCSI_SAS_LIBSAS[0m
help
This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
based host adapters.
config [31mCONFIG_SCSI_BFA_FC[0m
tristate "Brocade BFA Fibre Channel Support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SCSI[0m
depends on [31mCONFIG_SCSI_FC_ATTRS[0m
help
This bfa driver supports all Brocade PCIe FC/[31mCONFIG_FCOE[0m host adapters.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called bfa.
config [31mCONFIG_SCSI_VIRTIO[0m
tristate "virtio-scsi support"
depends on [31mCONFIG_VIRTIO[0m
help
This is the virtual HBA driver for virtio. If the kernel will
be used in a virtual machine, say Y or [31mCONFIG_M[0m.
source "drivers/scsi/csiostor/Kconfig"
endif # [31mCONFIG_SCSI_LOWLEVEL[0m
source "drivers/scsi/pcmcia/Kconfig"
source "drivers/scsi/device_handler/Kconfig"
source "drivers/scsi/osd/Kconfig"
endmenu