How to configure the Linux kernel/Device drivers/SCSI device support

Howto configure the Linux kernel / drivers / scsi

SCSI device support

 * In general it is a good idea to enable 'SCSI device support even if you don't use scsi disks
 * often cameras, USB drives, mp3 mplayers, etc. use scsi disk as the device's connection
 * so enable: SCSI device support, SCSI /dev/proc support, and SCSI disk support


 * Option: SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI device support
 * 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 have a device which speaks the SCSI protocol. Examples of this include the parallel port version of the IOMEGA ZIP drive, USB storage devices, Fibre Channel, FireWire storage and the IDE-SCSI emulation driver.
 * To compile this driver as a module, choose M here and read . 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 SCSI device.


 * Option: SCSI_PROC_FS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) legacy /proc/scsi/ support
 * depends on SCSI && PROC_FS
 * default y
 * 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 unusure say Y.

"SCSI support type (disk, tape, CD-ROM)"
 * depends on SCSI


 * Option: BLK_DEV_SD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI disk support
 * depends on SCSI
 * If you want to use SCSI hard disks, Fibre Channel disks, USB storage or the SCSI or parallel port version of the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from . This is NOT for SCSI CD-ROMs.
 * To compile this driver as a module, choose M here and read . 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 SCSI disk. In this case, do not compile the driver for your SCSI host adapter (below) as a module either.


 * Option: RAID_ATTRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) RAID Transport Class
 * default n
 * Provides RAID


 * Option: CHR_DEV_ST
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI tape support
 * depends on SCSI
 * If you want to use a SCSI tape drive under Linux, say Y and read the SCSI-HOWTO, available from , and  in the kernel source. This is NOT for SCSI CD-ROMs.
 * To compile this driver as a module, choose M here and read . The module will be called st.


 * Option: CHR_DEV_OSST
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI OnStream SC-x0 tape support
 * depends on SCSI
 * 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   and   in the kernel source. More info on the OnStream driver may be found on  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 M here and read . The module will be called osst.


 * Option: BLK_DEV_SR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI CDROM support
 * depends on SCSI
 * If you want to use a SCSI or FireWire CD-ROM under Linux, say Y and read the SCSI-HOWTO and the CDROM-HOWTO at . Also make sure to say Y or M to "ISO 9660 CD-ROM file system support" later.
 * To compile this driver as a module, choose M here and read . The module will be called sr_mod.


 * Option: BLK_DEV_SR_VENDOR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Enable vendor-specific extensions (for SCSI CDROM)
 * depends on BLK_DEV_SR
 * 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.


 * Option: CHR_DEV_SG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI generic support
 * depends on SCSI
 * 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 (). For CD writer software look at Cdrtools () and for burning a "disk at once": CDRDAO (). Cdparanoia is a high quality digital reader of audio CDs (). 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 M here and read <file:Documentation/scsi/scsi.txt>. The module will be called sg.
 * If unsure, say N.


 * Option: CHR_DEV_SCH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI media changer support
 * depends on SCSI
 * This is a driver for SCSI media changers. Most common devices are tape libraries and MOD/CDROM 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-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 M here and read <file:Documentation/modules.txt> and <file:Documentation/scsi.txt>. The module will be called ch.o. If unsure, say N.

"Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
 * depends on SCSI


 * Option: SCSI_MULTI_LUN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Probe all LUNs on each SCSI device
 * depends on SCSI
 * 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. The max_luns boot/module parameter allows to override this setting.


 * Option: SCSI_CONSTANTS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Verbose SCSI error reporting (kernel size +=12K)
 * depends on SCSI
 * 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.


 * Option: SCSI_LOGGING
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) SCSI logging facility
 * depends on SCSI
 * 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.

SCSI Transport Attributes

 * depends on SCSI


 * Option: SCSI_SPI_ATTRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Parallel SCSI (SPI) Transport Attributes
 * depends on SCSI
 * If you wish to export transport-specific information about each attached SCSI device to sysfs, say Y. Otherwise, say N.


 * Option: SCSI_FC_ATTRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) FiberChannel Transport Attributes
 * depends on SCSI
 * If you wish to export transport-specific information about each attached FiberChannel device to sysfs, say Y. Otherwise, say N.


 * Option: SCSI_ISCSI_ATTRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) iSCSI Transport Attributes
 * depends on SCSI && NET
 * If you wish to export transport-specific information about each attached iSCSI device to sysfs, say Y. Otherwise, say N.


 * Option: SCSI_SAS_ATTRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SAS Transport Attributes
 * depends on SCSI
 * If you wish to export transport-specific information about each attached SAS device to sysfs, say Y.

SCSI low-level drivers

 * depends on SCSI!=n

compile this driver as a module, choose M here: themodule will be called iscsi_tcp. userspace component needed to initialize the driver, documentation,and sample configuration files can be found here:
 * Option: ISCSI_TCP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) iSCSI Initiator over TCP/IP
 * depends on SCSI && INET
 * select CRYPTO
 * select CRYPTO_MD5
 * select CRYPTO_CRC32C
 * select SCSI_ISCSI_ATTRS
 * The iSCSI Driver provides a host with the ability to access storagethrough an IP network. The driver uses the iSCSI protocol to transportSCSI requests and responses over a TCP/IP network between the host(the "initiator") and "targets". Architecturally, the iSCSI drivercombines with the host's TCP/IP stack, network drivers, and NetworkInterface Card (NIC) to provide the same functions as a SCSI or aFibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
 * //linux-iscsi.sf.net


 * Option: SGIWD93_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SGI WD93C93 SCSI Driver
 * depends on SGI_IP22 && SCSI help If you have a Western Digital WD93 SCSI controller on an SGI MIPS system, say Y.  Otherwise, say N.


 * Option: SCSI_DECNCR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) DEC NCR53C94 Scsi Driver
 * depends on MACH_DECSTATION && SCSI && TC
 * Say Y here to support the NCR53C94 SCSI controller chips on IOASIC based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.


 * Option: SCSI_DECSII
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) DEC SII Scsi Driver
 * depends on MACH_DECSTATION && SCSI && 32BIT


 * Option: BLK_DEV_3W_XXXX_RAID
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) 3ware 5/6/7/8xxx ATA-RAID support
 * depends on PCI && SCSI
 * 3ware is the only hardware ATA-Raid product in Linux to date. This card is 2,4, or 8 channel master mode support only. SCSI support required!!!
 * <http://www.3ware.com/>
 * Please read the comments at the top of <file:drivers/scsi/3w-xxxx.c>.


 * Option: SCSI_3W_9XXX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) 3ware 9xxx SATA-RAID support
 * depends on PCI && SCSI
 * 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>.


 * Option: SCSI_7000FASST
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) 7000FASST SCSI support
 * depends on ISA && SCSI && ISA_DMA_API
 * This driver supports the Western Digital 7000 SCSI host adapter family. Some information is in the source: <file:drivers/scsi/wd7000.c>.
 * To compile this driver as a module, choose M here: the module will be called wd7000.


 * Option: SCSI_ACARD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) ACARD SCSI support
 * depends on PCI && SCSI
 * This driver supports the ACARD SCSI host adapter. Support Chip <ATP870 ATP876 ATP880 ATP885> To compile this driver as a module, choose M here: the module will be called atp870u.


 * Option: SCSI_AHA152X
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec AHA152X/2825 support
 * depends on ISA && SCSI && !64BIT
 * 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:Documentation/scsi/aha152x.txt>.
 * To compile this driver as a module, choose M here: the module will be called aha152x.


 * Option: SCSI_AHA1542
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec AHA1542 support
 * depends on ISA && SCSI && ISA_DMA_API
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called aha1542.


 * Option: SCSI_AHA1740
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec AHA1740 support
 * depends on EISA && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called aha1740.


 * Option: SCSI_AACRAID
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec AACRAID support
 * depends on SCSI && PCI


 * Option: Howto configure the Linux kernel/drivers/scsi/aic7xxx.aic7xxx"


 * Option: SCSI_AIC7XXX_OLD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec AIC7xxx support (old driver)
 * depends on (ISA || EISA || PCI ) && SCSI
 * 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:Documentation/scsi/aic7xxx_old.txt> 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.
 * To compile this driver as a module, choose M here: the module will be called aic7xxx_old.


 * Option: Howto configure the Linux kernel/drivers/scsi/aic7xxx.aic79xx"


 * All the I2O code and drivers do not seem to be 64bit safe.


 * Option: SCSI_DPT_I2O
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Adaptec I2O RAID support 
 * depends on !64BIT && SCSI && PCI
 * 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 M here: the module will be called dpt_i2o.


 * Option: SCSI_ADVANSYS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) AdvanSys SCSI support
 * depends on (ISA || EISA || PCI) && SCSI && BROKEN
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called advansys.


 * Option: SCSI_IN2000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Always IN2000 SCSI support
 * depends on ISA && SCSI
 * This is support for an ISA bus SCSI host adapter. You'll find more information in <file:Documentation/scsi/in2000.txt>. If it doesn't work out of the box, you may have to change the jumpers for IRQ or address selection.
 * To compile this driver as a module, choose M here: the module will be called in2000.


 * Option: Howto configure the Linux kernel/drivers/scsi/megaraid.megaraid"


 * Option: SCSI_SATA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Serial ATA (SATA) support
 * depends on SCSI
 * This driver family supports Serial ATA host controllers and devices.
 * If unsure, say N.


 * Option: SCSI_SATA_AHCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) AHCI SATA support
 * depends on SCSI_SATA && PCI
 * This option enables support for AHCI Serial ATA.
 * If unsure, say N.


 * Option: SCSI_SATA_SVW
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) ServerWorks Frodo / Apple K2 SATA support
 * depends on SCSI_SATA && PCI
 * This option enables support for Broadcom/Serverworks/Apple K2 SATA support.
 * If unsure, say N.


 * Option: SCSI_ATA_PIIX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Intel PIIX/ICH SATA support
 * depends on SCSI_SATA && PCI
 * This option enables support for ICH5 Serial ATA. If PATA support was enabled previously, this enables support for select Intel PIIX/ICH PATA host controllers.
 * If unsure, say N.


 * Option: SCSI_SATA_MV
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Marvell SATA support (HIGHLY EXPERIMENTAL)
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for the Marvell Serial ATA family. Currently supports 88SX[56]0[48][01] chips.
 * If unsure, say N.


 * Option: SCSI_SATA_NV
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NVIDIA SATA support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for NVIDIA Serial ATA.
 * If unsure, say N.


 * Option: SCSI_PDC_ADMA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Pacific Digital ADMA support
 * depends on SCSI_SATA && PCI
 * This option enables support for Pacific Digital ADMA controllers
 * If unsure, say N.


 * Option: SCSI_SATA_QSTOR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Pacific Digital SATA QStor support
 * depends on SCSI_SATA && PCI
 * This option enables support for Pacific Digital Serial ATA QStor.
 * If unsure, say N.


 * Option: SCSI_SATA_PROMISE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Promise SATA TX2/TX4 support
 * depends on SCSI_SATA && PCI
 * This option enables support for Promise Serial ATA TX2/TX4.
 * If unsure, say N.


 * Option: SCSI_SATA_SX4
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Promise SATA SX4 support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for Promise Serial ATA SX4.
 * If unsure, say N.


 * Option: SCSI_SATA_SIL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Silicon Image SATA support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for Silicon Image Serial ATA.
 * If unsure, say N.


 * Option: SCSI_SATA_SIL24
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Silicon Image 3124/3132 SATA support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for Silicon Image 3124/3132 Serial ATA.
 * If unsure, say N.


 * Option: SCSI_SATA_SIS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SiS 964/180 SATA support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for SiS Serial ATA 964/180.
 * If unsure, say N.


 * Option: SCSI_SATA_ULI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) ULi Electronics SATA support
 * depends on SCSI_SATA && PCI && EXPERIMENTAL
 * This option enables support for ULi Electronics SATA.
 * If unsure, say N.


 * Option: SCSI_SATA_VIA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) VIA SATA support
 * depends on SCSI_SATA && PCI
 * This option enables support for VIA Serial ATA.
 * If unsure, say N.


 * Option: SCSI_SATA_VITESSE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) VITESSE VSC-7174 SATA support
 * depends on SCSI_SATA && PCI
 * This option enables support for Vitesse VSC7174 Serial ATA.
 * If unsure, say N.


 * Option: SCSI_SATA_INTEL_COMBINED
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
 * default y


 * Option: SCSI_BUSLOGIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BusLogic SCSI support
 * depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
 * 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:Documentation/scsi/BusLogic.txt> and <file:Documentation/scsi/FlashPoint.txt> for more information.
 * To compile this driver as a module, choose M here: the module will be called BusLogic.


 * Option: SCSI_OMIT_FLASHPOINT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Omit FlashPoint support
 * depends on SCSI_BUSLOGIC
 * 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.


 * Option: SCSI_DMX3191D
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) DMX3191D SCSI support
 * depends on PCI && SCSI
 * This is support for Domex DMX3191D SCSI Host Adapters.
 * To compile this driver as a module, choose M here: the module will be called dmx3191d.


 * Option: SCSI_DTC3280
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) DTC3180/3280 SCSI support
 * depends on ISA && SCSI
 * 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:Documentation/scsi/dtc3x80.txt>.
 * To compile this driver as a module, choose M here: the module will be called dtc.


 * Option: SCSI_EATA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
 * depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
 * 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. 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>.
 * To compile this driver as a module, choose M here: the module will be called eata.


 * Option: SCSI_EATA_TAGGED_QUEUE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable tagged command queueing
 * depends on SCSI_EATA
 * 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. This is equivalent to the "eata=tc:y" boot option.


 * Option: SCSI_EATA_LINKED_COMMANDS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable elevator sorting
 * depends on SCSI_EATA
 * 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... This is equivalent to the "eata=lc:y" boot option.

"maximum number of queued commands"
 * Option: SCSI_EATA_MAX_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_EATA
 * default "16"
 * 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. This is equivalent to the "eata=mq:8" boot option.


 * Option: SCSI_EATA_PIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) EATA-PIO (old DPT PM2001, PM2012A) support
 * depends on (ISA || EISA || PCI) && SCSI && BROKEN
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called eata_pio.


 * Option: SCSI_FUTURE_DOMAIN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Future Domain 16xx SCSI/AHA-2920A support
 * depends on (ISA || PCI) && SCSI
 * 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.
 * To compile this driver as a module, choose M here: the module will be called fdomain.


 * Option: SCSI_FD_MCS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Future Domain MCS-600/700 SCSI support
 * depends on MCA_LEGACY && SCSI
 * 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.
 * To compile this driver as a module, choose M here: the module will be called fd_mcs.


 * Option: SCSI_GDTH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
 * depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
 * Formerly called GDT SCSI Disk Array Controller Support.
 * This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 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 M here: the module will be called gdth.


 * Option: SCSI_GENERIC_NCR5380
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Generic NCR5380/53c400 SCSI PIO support
 * depends on ISA && SCSI
 * This is a driver for the old NCR 53c80 series of SCSI controllers on boards using PIO. Most boards such as the Trantor T130 fit this category, along with a large number of ISA 8bit controllers shipped for free with SCSI scanners. If you have a PAS16, T128 or DMX3191 you should select the specific driver for that card rather than generic 5380 support.
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called g_NCR5380.


 * Option: SCSI_GENERIC_NCR5380_MMIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Generic NCR5380/53c400 SCSI MMIO support
 * depends on ISA && SCSI
 * This is a driver for the old NCR 53c80 series of SCSI controllers on boards using memory mapped I/O. 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>.
 * To compile this driver as a module, choose M here: the module will be called g_NCR5380_mmio.


 * Option: SCSI_GENERIC_NCR53C400
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Enable NCR53c400 extensions
 * depends on SCSI_GENERIC_NCR5380
 * 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:Documentation/scsi/g_NCR5380.txt> for details.


 * Option: SCSI_IBMMCA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IBMMCA SCSI support
 * depends on MCA_LEGACY && SCSI
 * 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= ' kernel option, where 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.
 * To compile this driver as a module, choose M here: the module will be called ibmmca.


 * Option: IBMMCA_SCSI_ORDER_STANDARD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Standard SCSI-order
 * depends on SCSI_IBMMCA
 * 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.


 * Option: IBMMCA_SCSI_DEV_RESET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Reset SCSI-devices at boottime
 * depends on SCSI_IBMMCA
 * 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.


 * Option: SCSI_IPS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IBM ServeRAID support
 * depends on PCI && SCSI
 * 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@adaptec.com>.
 * To compile this driver as a module, choose M here: the module will be called ips.


 * Option: SCSI_IBMVSCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IBM Virtual SCSI support
 * depends on PPC_PSERIES || PPC_ISERIES
 * This is the IBM POWER Virtual SCSI Client
 * To compile this driver as a module, choose M here: the module will be called ibmvscsic.


 * Option: SCSI_INITIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Initio 9100U(W) support
 * depends on PCI && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called initio.


 * Option: SCSI_INIA100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Initio INI-A100U2W support
 * depends on PCI && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called a100u2w.


 * Option: SCSI_PPA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IOMEGA parallel port (ppa - older drives)
 * depends on SCSI && PARPORT
 * 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:Documentation/scsi/ppa.txt>. 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.
 * To compile this driver as a module, choose M here: the module will be called ppa.


 * Option: SCSI_IMM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IOMEGA parallel port (imm - newer drives)
 * depends on SCSI && PARPORT
 * 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:Documentation/scsi/ppa.txt>. 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.
 * To compile this driver as a module, choose M here: the module will be called imm.


 * Option: SCSI_IZIP_EPP16
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) ppa/imm option - Use slow (but safe) EPP-16
 * depends on PARPORT && (SCSI_PPA || SCSI_IMM)
 * 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.


 * Option: SCSI_IZIP_SLOW_CTR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) ppa/imm option - Assume slow parport control register
 * depends on PARPORT && (SCSI_PPA || SCSI_IMM)
 * 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.


 * Option: SCSI_NCR53C406A
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NCR53c406a SCSI support
 * depends on ISA && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called NCR53c406.


 * Option: SCSI_NCR_D700
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NCR Dual 700 MCA SCSI support
 * depends on MCA && SCSI
 * select SCSI_SPI_ATTRS
 * 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.


 * Option: SCSI_LASI700
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) HP Lasi SCSI support for 53c700/710
 * depends on GSC && SCSI
 * select SCSI_SPI_ATTRS
 * This is a driver for the SCSI 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.


 * Option: 53C700_LE_ON_BE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on SCSI_LASI700
 * default y


 * Option: SCSI_SYM53C8XX_2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SYM53C8XX Version 2 SCSI support
 * depends on PCI && SCSI
 * select SCSI_SPI_ATTRS
 * 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; you need to use the Fusion MPT driver for that.
 * Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more information.

"DMA addressing mode"
 * Option: SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_SYM53C8XX_2
 * default "1"
 * This option only applies to PCI-SCSI chips that are PCI 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 PCI address bits past bit 39 to be set for the addressing of memory using PCI DAC cycles.

"default tagged command queue depth"
 * Option: SCSI_SYM53C8XX_DEFAULT_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_SYM53C8XX_2
 * default "16"
 * 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.

"maximum number of queued commands"
 * Option: SCSI_SYM53C8XX_MAX_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_SYM53C8XX_2
 * default "64"
 * 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.


 * Option: SCSI_SYM53C8XX_IOMAPPED
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) use port IO
 * depends on SCSI_SYM53C8XX_2
 * If you say Y here, the driver will use port IO to access the card. This is significantly slower then using memory mapped IO.  Most people should answer N.


 * Option: SCSI_IPR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) IBM Power Linux RAID adapter support
 * depends on PCI && SCSI
 * select FW_LOADER
 * 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.


 * Option: SCSI_IPR_TRACE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable driver internal trace
 * depends on SCSI_IPR
 * 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.


 * Option: SCSI_IPR_DUMP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable adapter dump support
 * depends on SCSI_IPR
 * 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.


 * Option: SCSI_ZALON
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Zalon SCSI support
 * depends on GSC && SCSI
 * select SCSI_SPI_ATTRS
 * The Zalon is a GSC/HSC bus interface chip that sits between the PA-RISC processor and the NCR 53c720 SCSI controller on C100, C110, J200, J210 and some D, K & R-class machines. It's also used on the add-in Bluefish, Barracuda & Shrike SCSI cards. Say Y here if you have one of these machines or cards.


 * Option: SCSI_NCR_Q720
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NCR Quad 720 MCA SCSI support
 * depends on MCA && SCSI
 * select SCSI_SPI_ATTRS
 * 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 SCSI card, so say N.

" default tagged command queue depth"
 * Option: SCSI_NCR53C8XX_DEFAULT_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_ZALON || SCSI_NCR_Q720
 * default "8"
 * 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"
 * Option: SCSI_NCR53C8XX_MAX_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_ZALON || SCSI_NCR_Q720
 * default "32"
 * 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.

" synchronous transfers frequency in MHz"
 * Option: SCSI_NCR53C8XX_SYNC
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_ZALON || SCSI_NCR_Q720
 * default "20"
 * 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.


 * Option: SCSI_NCR53C8XX_PROFILE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)   enable profiling
 * depends on SCSI_ZALON || SCSI_NCR_Q720
 * 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.


 * Option: SCSI_NCR53C8XX_NO_DISCONNECT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)   not allow targets to disconnect
 * depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
 * 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.


 * Option: SCSI_MCA_53C9X
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NCR MCA 53C9x SCSI support
 * depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
 * 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.
 * To compile this driver as a module, choose M here: the module will be called mca_53c9x.


 * Option: SCSI_PAS16
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) PAS16 SCSI support
 * depends on ISA && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called pas16.


 * Option: SCSI_PSI240I
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) PSI240i support
 * depends on ISA && SCSI
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called psi240i.


 * Option: SCSI_QLOGIC_FAS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Qlogic FAS SCSI support
 * depends on ISA && SCSI
 * 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:Documentation/scsi/qlogicfas.txt>. You should also read the SCSI-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
 * To compile this driver as a module, choose M here: the module will be called qlogicfas.


 * Option: SCSI_QLOGIC_FC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Qlogic ISP FC SCSI support
 * depends on PCI && SCSI
 * This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
 * To compile this driver as a module, choose M here: the module will be called qlogicfc.


 * Option: SCSI_QLOGIC_FC_FIRMWARE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Include loadable firmware in driver
 * depends on SCSI_QLOGIC_FC help Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with expanded LUN addressing and FcTape (FCP-2) support, in the qlogicfc driver. This is required on some platforms.


 * Option: SCSI_QLOGIC_1280
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Qlogic QLA 1240/1x80/1x160 SCSI support
 * depends on PCI && SCSI
 * Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
 * To compile this driver as a module, choose M here: the module will be called qla1280.


 * Option: SCSI_QLOGICPTI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) PTI Qlogic, ISP Driver
 * depends on SBUS && SCSI
 * This driver supports SBUS SCSI 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 PCI QLogic SCSI controllers are driven by a different driver.
 * To compile this driver as a module, choose M here: the module will be called qlogicpti.


 * Option: Howto configure the Linux kernel/drivers/scsi/qla2xxx


 * Option: SCSI_LPFC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Emulex LightPulse Fibre Channel Support
 * depends on PCI && SCSI
 * select SCSI_FC_ATTRS
 * This lpfc driver supports the Emulex LightPulse        Family of Fibre Channel PCI host adapters.


 * Option: SCSI_SEAGATE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Seagate ST-02 and Future Domain TMC-8xx SCSI support
 * depends on X86 && ISA && SCSI && BROKEN
 * 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>.
 * To compile this driver as a module, choose M here: the module will be called seagate.


 * definitely looks not 64bit safe:


 * Option: SCSI_SIM710
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Simple 53c710 SCSI support (Compaq, NCR machines)
 * depends on (EISA || MCA) && SCSI
 * select SCSI_SPI_ATTRS
 * This driver for NCR53c710 based SCSI host adapters.
 * It currently supports Compaq EISA cards and NCR MCA cards


 * Option: 53C700_IO_MAPPED
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on SCSI_SIM710
 * default y


 * Option: SCSI_SYM53C416
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Symbios 53c416 SCSI support
 * depends on ISA && SCSI
 * 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=, [sym53c416_1= , ]
 * To compile this driver as a module, choose M here: the module will be called sym53c416.


 * Option: SCSI_DC395x
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)
 * depends on PCI && SCSI && EXPERIMENTAL
 * This driver supports PCI SCSI 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 M here: the module will be called dc395x.


 * Option: SCSI_DC390T
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Tekram DC390(T) and Am53/79C974 SCSI support
 * depends on PCI && SCSI
 * 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: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 M here: the module will be called tmscsim.


 * Option: SCSI_T128
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Trantor T128/T128F/T228 SCSI support
 * depends on ISA && SCSI
 * 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.
 * To compile this driver as a module, choose M here: the module will be called t128.


 * Option: SCSI_U14_34F
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) UltraStor 14F/34F support
 * depends on ISA && SCSI && ISA_DMA_API
 * 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.
 * To compile this driver as a module, choose M here: the module will be called u14-34f.


 * Option: SCSI_U14_34F_TAGGED_QUEUE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable tagged command queueing
 * depends on SCSI_U14_34F
 * 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. This is equivalent to the "u14-34f=tc:y" boot option.


 * Option: SCSI_U14_34F_LINKED_COMMANDS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) enable elevator sorting
 * depends on SCSI_U14_34F
 * 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... This is equivalent to the "u14-34f=lc:y" boot option.

"maximum number of queued commands"
 * Option: SCSI_U14_34F_MAX_TAGS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_U14_34F
 * default "8"
 * 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. This is equivalent to the "u14-34f=mq:8" boot option.


 * Option: SCSI_ULTRASTOR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) UltraStor SCSI support
 * depends on X86 && ISA && SCSI
 * 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.
 * To compile this driver as a module, choose M here: the module will be called ultrastor.


 * Option: SCSI_NSP32
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Workbit NinjaSCSI-32Bi/UDE support
 * depends on PCI && SCSI && !64BIT
 * This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus SCSI host adapter. Please read the SCSI-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
 * To compile this driver as a module, choose M here: the module will be called nsp32.


 * Option: SCSI_DEBUG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) SCSI debugging host simulator
 * depends on SCSI
 * This is a host adapter simulator that can simulate multiple hosts each with multiple dummy SCSI devices (disks). It defaults to one host adapter with one dummy SCSI disk. Each dummy disk uses kernel RAM as storage (i.e. it is a ramdisk). To save space when multiple dummy disks are simulated, they share the same kernel RAM for their storage. See <http://www.torque.net/sg/sdebug.html> for more information. This driver is primarily of use to those testing the SCSI and block subsystems. If unsure, say N.


 * Option: SCSI_MESH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) MESH (Power Mac internal SCSI) support
 * depends on PPC32 && PPC_PMAC && SCSI
 * Many Power Macintoshes and clones have a MESH (Macintosh Enhanced SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the other Power Macintoshes do). Say Y to include support for this SCSI adaptor.
 * To compile this driver as a module, choose M here: the module will be called mesh.

"maximum synchronous transfer rate (MB/s) (0 = async)"
 * Option: SCSI_MESH_SYNC_RATE
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_MESH
 * default "5"
 * On Power Macintoshes (and clones) where the MESH SCSI 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 SCSI 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 SCSI bus is internal only; in that case you can say 10. Say 0 to disable synchronous operation.

"initial bus reset delay (ms) (0 = no reset)"
 * Option: SCSI_MESH_RESET_DELAY_MS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SCSI_MESH
 * default "4000"


 * Option: SCSI_MAC53C94
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) 53C94 (Power Mac external SCSI) support
 * depends on PPC32 && PPC_PMAC && SCSI
 * On Power Macintoshes (and clones) with two SCSI buses, the external SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older machines which only have one SCSI 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 M here: the module will be called mac53c94.


 * Option: Howto configure the Linux kernel/drivers/scsi/arm


 * Option: JAZZ_ESP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) MIPS JAZZ FAS216 SCSI support
 * depends on MACH_JAZZ && SCSI
 * This is the driver for the onboard SCSI host adapter of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems.


 * Option: A3000_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) A3000 WD33C93A support
 * depends on AMIGA && SCSI
 * If you have an Amiga 3000 and have SCSI devices connected to the built-in SCSI controller, say Y. Otherwise, say N.
 * To compile this driver as a module, choose M here: the module will be called wd33c93.


 * Option: A2091_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) A2091/A590 WD33C93A support
 * depends on ZORRO && SCSI
 * If you have a Commodore A2091 SCSI controller, say Y. Otherwise, say N.
 * To compile this driver as a module, choose M here: the module will be called wd33c93.


 * Option: GVP11_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) GVP Series II WD33C93A support
 * depends on ZORRO && SCSI
 * If you have a Great Valley Products Series II SCSI controller, answer Y. Also say Y if you have a later model of GVP SCSI 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-M.
 * To compile this driver as a module, choose M here: the module will be called gvp11.


 * Option: CYBERSTORM_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CyberStorm SCSI support
 * depends on ZORRO && SCSI
 * If you have an Amiga with an original (MkI) Phase5 Cyberstorm accelerator board and the optional Cyberstorm SCSI controller, answer Y. Otherwise, say N.


 * Option: CYBERSTORMII_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CyberStorm Mk II SCSI support
 * depends on ZORRO && SCSI
 * If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board and the optional Cyberstorm SCSI controller, say Y. Otherwise, answer N.


 * Option: BLZ2060_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Blizzard 2060 SCSI support
 * depends on ZORRO && SCSI
 * If you have an Amiga with a Phase5 Blizzard 2060 accelerator board and want to use the onboard SCSI controller, say Y. Otherwise, answer N.


 * Option: BLZ1230_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Blizzard 1230IV/1260 SCSI support
 * depends on ZORRO && SCSI
 * If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard 1260 accelerator, and the optional SCSI module, say Y. Otherwise, say N.


 * Option: FASTLANE_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Fastlane SCSI support
 * depends on ZORRO && SCSI
 * If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one in the near future, say Y to this question. Otherwise, say N.


 * Option: SCSI_AMIGA7XX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Amiga NCR53c710 SCSI support (EXPERIMENTAL)
 * depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
 * Support for various NCR53c710-based SCSI controllers on the Amiga. This includes:  - the builtin SCSI controller on the Amiga 4000T,   - the Amiga 4091 Zorro III SCSI-2 controller,   - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller     (info at     <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),   - the SCSI controller on the Phase5 Blizzard PowerUP 603e+     accelerator card for the Amiga 1200,   - the SCSI controller on the GVP Turbo 040/060 accelerator. Note that all of the above SCSI controllers, except for the builtin SCSI controller on the Amiga 4000T, reside on the Zorro expansion bus, so you also have to enable Zorro bus support if you want to use them.


 * Option: OKTAGON_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BSC Oktagon SCSI support (EXPERIMENTAL)
 * depends on ZORRO && SCSI && EXPERIMENTAL
 * If you have the BSC Oktagon SCSI disk controller for the Amiga, say Y to this question. If you're in doubt about whether you have one, see the picture at <http://amiga.resource.cx/exp/search.pl?product=oktagon>.


 * Option: ATARI_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Atari native SCSI support
 * depends on ATARI && SCSI && BROKEN
 * If you have an Atari with built-in NCR5380 SCSI controller (TT, Falcon, ...) say Y to get it supported. Of course also, if you have a compatible SCSI controller (e.g. for Medusa).
 * To compile this driver as a module, choose M 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).


 * Option: ATARI_SCSI_TOSHIBA_DELAY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Long delays for Toshiba CD-ROMs
 * depends on ATARI_SCSI
 * This option increases the delay after a SCSI arbitration to accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to use a Toshiba CD-ROM drive; otherwise, the option is not needed and would impact performance a bit, so say N.


 * Option: ATARI_SCSI_RESET_BOOT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Reset SCSI-devices at boottime
 * depends on ATARI_SCSI
 * Reset the devices on your Atari whenever it boots. This makes the boot process fractionally longer but may assist recovery from errors that leave the devices with SCSI operations partway completed.


 * Option: TT_DMA_EMUL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Hades SCSI DMA emulator
 * depends on ATARI_SCSI && HADES
 * This option enables code which emulates the TT SCSI DMA chip on the Hades. This increases the SCSI transfer rates at least ten times compared to PIO transfers.


 * Option: MAC_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Macintosh NCR5380 SCSI
 * depends on MAC && SCSI=y
 * This is the NCR 5380 SCSI controller included on most of the 68030 based Macintoshes. If you have one of these say Y and read the SCSI-HOWTO, available from <http://www.tldp.org/docs.html#howto>.


 * Option: SCSI_MAC_ESP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Macintosh NCR53c9[46] SCSI
 * depends on MAC && SCSI
 * This is the NCR 53c9x SCSI controller found on most of the 68040 based Macintoshes. If you have one of these say Y and read the SCSI-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
 * To compile this driver as a module, choose M here: the module will be called mac_esp.


 * Option: MVME147_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) WD33C93 SCSI driver for MVME147
 * depends on MVME147 && SCSI=y
 * Support for the on-board SCSI controller on the Motorola MVME147 single-board computer.


 * Option: MVME16x_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) NCR53C710 SCSI driver for MVME16x
 * depends on MVME16x && SCSI && BROKEN
 * The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question.


 * Option: BVME6000_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) NCR53C710 SCSI driver for BVME6000
 * depends on BVME6000 && SCSI && BROKEN
 * The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question.


 * Option: SCSI_NCR53C7xx_FAST
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) allow FAST-SCSI [10 MHz]
 * depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
 * This will enable 10 MHz FAST-SCSI transfers with your host adapter. Some systems have problems with that speed, so it's safest to say N here.


 * Option: SUN3_SCSI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Sun3 NCR5380 SCSI
 * depends on SUN3 && SCSI && BROKEN
 * This option will enable support for the OBIO (onboard io) NCR5380 SCSI controller found in the Sun 3/50 and 3/60, as well as for Sun3 type VME 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>.


 * Option: SUN3X_ESP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Sun3x ESP SCSI
 * depends on SUN3X && SCSI=y
 * The ESP was an on-board SCSI controller used on Sun 3/80 machines. Say Y here to compile in support for it.


 * Option: SCSI_SUNESP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Sparc ESP Scsi Driver
 * depends on SBUS && SCSI
 * This is the driver for the Sun ESP SCSI host adapter. The ESP chipset is present in most SPARC SBUS-based computers.
 * To compile this driver as a module, choose M here: the module will be called esp.


 * bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI


 * Option: ZFCP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) FCP host bus adapter driver for IBM eServer zSeries
 * depends on ARCH_S390 && QDIO && SCSI
 * select SCSI_FC_ATTRS
 * If you want to access SCSI 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://www.ibm.com/developerworks/linux/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 M here and read <file:Documentation/modules.txt>.


 * Option: Howto configure the Linux kernel/drivers/scsi/pcmcia

Linux Kernel Configuration