Version:  2.0.40 2.2.26 2.4.37 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18

Linux/drivers/scsi/Kconfig

  1 menu "SCSI device support"
  2 
  3 config SCSI_MOD
  4        tristate
  5        default y if SCSI=n || SCSI=y
  6        default m if SCSI=m
  7 
  8 config RAID_ATTRS
  9         tristate "RAID Transport Class"
 10         default n
 11         depends on BLOCK
 12         depends on SCSI_MOD
 13         ---help---
 14           Provides RAID
 15 
 16 config SCSI
 17         tristate "SCSI device support"
 18         depends on BLOCK
 19         select SCSI_DMA if HAS_DMA
 20         ---help---
 21           If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
 22           any other SCSI device under Linux, say Y and make sure that you know
 23           the name of your SCSI host adapter (the card inside your computer
 24           that "speaks" the SCSI protocol, also called SCSI controller),
 25           because you will be asked for it.
 26 
 27           You also need to say Y here if you have a device which speaks
 28           the SCSI protocol.  Examples of this include the parallel port
 29           version of the IOMEGA ZIP drive, USB storage devices, Fibre
 30           Channel, and FireWire storage.
 31 
 32           To compile this driver as a module, choose M here and read
 33           <file:Documentation/scsi/scsi.txt>.
 34           The module will be called scsi_mod.
 35 
 36           However, do not compile this as a module if your root file system
 37           (the one containing the directory /) is located on a SCSI device.
 38 
 39 config SCSI_DMA
 40         bool
 41         default n
 42 
 43 config SCSI_NETLINK
 44         bool
 45         default n
 46         depends on NET
 47 
 48 config SCSI_MQ_DEFAULT
 49         bool "SCSI: use blk-mq I/O path by default"
 50         depends on SCSI
 51         ---help---
 52           This option enables the new blk-mq based I/O path for SCSI
 53           devices by default.  With the option the scsi_mod.use_blk_mq
 54           module/boot option defaults to Y, without it to N, but it can
 55           still be overriden either way.
 56 
 57           If unsure say N.
 58 
 59 config SCSI_PROC_FS
 60         bool "legacy /proc/scsi/ support"
 61         depends on SCSI && PROC_FS
 62         default y
 63         ---help---
 64           This option enables support for the various files in
 65           /proc/scsi.  In Linux 2.6 this has been superseded by
 66           files in sysfs but many legacy applications rely on this.
 67 
 68           If unsure say Y.
 69 
 70 comment "SCSI support type (disk, tape, CD-ROM)"
 71         depends on SCSI
 72 
 73 config BLK_DEV_SD
 74         tristate "SCSI disk support"
 75         depends on SCSI
 76         ---help---
 77           If you want to use SCSI hard disks, Fibre Channel disks,
 78           Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
 79           USB storage or the SCSI or parallel port version of
 80           the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
 81           the Disk-HOWTO and the Multi-Disk-HOWTO, available from
 82           <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
 83           CD-ROMs.
 84 
 85           To compile this driver as a module, choose M here and read
 86           <file:Documentation/scsi/scsi.txt>.
 87           The module will be called sd_mod.
 88 
 89           Do not compile this driver as a module if your root file system
 90           (the one containing the directory /) is located on a SCSI disk.
 91           In this case, do not compile the driver for your SCSI host adapter
 92           (below) as a module either.
 93 
 94 config CHR_DEV_ST
 95         tristate "SCSI tape support"
 96         depends on SCSI
 97         ---help---
 98           If you want to use a SCSI tape drive under Linux, say Y and read the
 99           SCSI-HOWTO, available from
100           <http://www.tldp.org/docs.html#howto>, and
101           <file:Documentation/scsi/st.txt> in the kernel source.  This is NOT
102           for SCSI CD-ROMs.
103 
104           To compile this driver as a module, choose M here and read
105           <file:Documentation/scsi/scsi.txt>. The module will be called st.
106 
107 config CHR_DEV_OSST
108         tristate "SCSI OnStream SC-x0 tape support"
109         depends on SCSI
110         ---help---
111           The OnStream SC-x0 SCSI tape drives cannot be driven by the
112           standard st driver, but instead need this special osst driver and
113           use the  /dev/osstX char device nodes (major 206).  Via usb-storage,
114           you may be able to drive the USB-x0 and DI-x0 drives as well.
115           Note that there is also a second generation of OnStream
116           tape drives (ADR-x0) that supports the standard SCSI-2 commands for
117           tapes (QIC-157) and can be driven by the standard driver st.
118           For more information, you may have a look at the SCSI-HOWTO
119           <http://www.tldp.org/docs.html#howto>  and
120           <file:Documentation/scsi/osst.txt>  in the kernel source.
121           More info on the OnStream driver may be found on
122           <http://sourceforge.net/projects/osst/>
123           Please also have a look at the standard st docu, as most of it
124           applies to osst as well.
125 
126           To compile this driver as a module, choose M here and read
127           <file:Documentation/scsi/scsi.txt>. The module will be called osst.
128 
129 config BLK_DEV_SR
130         tristate "SCSI CDROM support"
131         depends on SCSI
132         ---help---
133           If you want to use a CD or DVD drive attached to your computer
134           by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
135           and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
136 
137           Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
138 
139           To compile this driver as a module, choose M here and read
140           <file:Documentation/scsi/scsi.txt>.
141           The module will be called sr_mod.
142 
143 config BLK_DEV_SR_VENDOR
144         bool "Enable vendor-specific extensions (for SCSI CDROM)"
145         depends on BLK_DEV_SR
146         help
147           This enables the usage of vendor specific SCSI commands. This is
148           required to support multisession CDs with old NEC/TOSHIBA cdrom
149           drives (and HP Writers). If you have such a drive and get the first
150           session only, try saying Y here; everybody else says N.
151 
152 config CHR_DEV_SG
153         tristate "SCSI generic support"
154         depends on SCSI
155         ---help---
156           If you want to use SCSI scanners, synthesizers or CD-writers or just
157           about anything having "SCSI" in its name other than hard disks,
158           CD-ROMs or tapes, say Y here. These won't be supported by the kernel
159           directly, so you need some additional software which knows how to
160           talk to these devices using the SCSI protocol:
161 
162           For scanners, look at SANE (<http://www.sane-project.org/>). For CD
163           writer software look at Cdrtools
164           (<http://cdrecord.berlios.de/private/cdrecord.html>)
165           and for burning a "disk at once": CDRDAO
166           (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
167           quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
168           For other devices, it's possible that you'll have to write the
169           driver software yourself. Please read the file
170           <file:Documentation/scsi/scsi-generic.txt> for more information.
171 
172           To compile this driver as a module, choose M here and read
173           <file:Documentation/scsi/scsi.txt>. The module will be called sg.
174 
175           If unsure, say N.
176 
177 config CHR_DEV_SCH
178         tristate "SCSI media changer support"
179         depends on SCSI
180         ---help---
181           This is a driver for SCSI media changers.  Most common devices are
182           tape libraries and MOD/CDROM jukeboxes.  *Real* jukeboxes, you
183           don't need this for those tiny 6-slot cdrom changers.  Media
184           changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
185           If you have such hardware and want to use it with linux, say Y
186           here.  Check <file:Documentation/scsi/scsi-changer.txt> for details.
187         
188           If you want to compile this as a module ( = code which can be
189           inserted in and removed from the running kernel whenever you want),
190           say M here and read <file:Documentation/kbuild/modules.txt> and
191           <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
192           If unsure, say N.
193 
194 config SCSI_ENCLOSURE
195         tristate "SCSI Enclosure Support"
196         depends on SCSI && ENCLOSURE_SERVICES
197         help
198           Enclosures are devices sitting on or in SCSI backplanes that
199           manage devices.  If you have a disk cage, the chances are that
200           it has an enclosure device.  Selecting this option will just allow
201           certain enclosure conditions to be reported and is not required.
202 
203 config SCSI_CONSTANTS
204         bool "Verbose SCSI error reporting (kernel size +=12K)"
205         depends on SCSI
206         help
207           The error messages regarding your SCSI hardware will be easier to
208           understand if you say Y here; it will enlarge your kernel by about
209           12 KB. If in doubt, say Y.
210 
211 config SCSI_LOGGING
212         bool "SCSI logging facility"
213         depends on SCSI
214         ---help---
215           This turns on a logging facility that can be used to debug a number
216           of SCSI related problems.
217 
218           If you say Y here, no logging output will appear by default, but you
219           can enable logging by saying Y to "/proc file system support" and
220           "Sysctl support" below and executing the command
221 
222           echo <bitmask> > /proc/sys/dev/scsi/logging_level
223 
224           where <bitmask> is a four byte value representing the logging type
225           and logging level for each type of logging selected.
226 
227           There are a number of logging types and you can find them in the
228           source at <file:drivers/scsi/scsi_logging.h>. The logging levels
229           are also described in that file and they determine the verbosity of
230           the logging for each logging type.
231 
232           If you say N here, it may be harder to track down some types of SCSI
233           problems. If you say Y here your kernel will be somewhat larger, but
234           there should be no noticeable performance impact as long as you have
235           logging turned off.
236 
237 config SCSI_SCAN_ASYNC
238         bool "Asynchronous SCSI scanning"
239         depends on SCSI
240         help
241           The SCSI subsystem can probe for devices while the rest of the
242           system continues booting, and even probe devices on different
243           busses in parallel, leading to a significant speed-up.
244 
245           If you have built SCSI as modules, enabling this option can
246           be a problem as the devices may not have been found by the
247           time your system expects them to have been.  You can load the
248           scsi_wait_scan module to ensure that all scans have completed.
249           If you build your SCSI drivers into the kernel, then everything
250           will work fine if you say Y here.
251 
252           You can override this choice by specifying "scsi_mod.scan=sync"
253           or async on the kernel's command line.
254 
255           Note that this setting also affects whether resuming from
256           system suspend will be performed asynchronously.
257 
258 menu "SCSI Transports"
259         depends on SCSI
260 
261 config SCSI_SPI_ATTRS
262         tristate "Parallel SCSI (SPI) Transport Attributes"
263         depends on SCSI
264         help
265           If you wish to export transport-specific information about
266           each attached SCSI device to sysfs, say Y.  Otherwise, say N.
267 
268 config SCSI_FC_ATTRS
269         tristate "FiberChannel Transport Attributes"
270         depends on SCSI && NET
271         select SCSI_NETLINK
272         help
273           If you wish to export transport-specific information about
274           each attached FiberChannel device to sysfs, say Y.
275           Otherwise, say N.
276 
277 config SCSI_ISCSI_ATTRS
278         tristate "iSCSI Transport Attributes"
279         depends on SCSI && NET
280         select BLK_DEV_BSGLIB
281         help
282           If you wish to export transport-specific information about
283           each attached iSCSI device to sysfs, say Y.
284           Otherwise, say N.
285 
286 config SCSI_SAS_ATTRS
287         tristate "SAS Transport Attributes"
288         depends on SCSI
289         select BLK_DEV_BSG
290         help
291           If you wish to export transport-specific information about
292           each attached SAS device to sysfs, say Y.
293 
294 source "drivers/scsi/libsas/Kconfig"
295 
296 config SCSI_SRP_ATTRS
297         tristate "SRP Transport Attributes"
298         depends on SCSI
299         help
300           If you wish to export transport-specific information about
301           each attached SRP device to sysfs, say Y.
302 
303 endmenu
304 
305 menuconfig SCSI_LOWLEVEL
306         bool "SCSI low-level drivers"
307         depends on SCSI!=n
308         default y
309 
310 if SCSI_LOWLEVEL && SCSI
311 
312 config ISCSI_TCP
313         tristate "iSCSI Initiator over TCP/IP"
314         depends on SCSI && INET
315         select CRYPTO
316         select CRYPTO_MD5
317         select CRYPTO_CRC32C
318         select SCSI_ISCSI_ATTRS
319         help
320          The iSCSI Driver provides a host with the ability to access storage
321          through an IP network. The driver uses the iSCSI protocol to transport
322          SCSI requests and responses over a TCP/IP network between the host
323          (the "initiator") and "targets".  Architecturally, the iSCSI driver
324          combines with the host's TCP/IP stack, network drivers, and Network
325          Interface Card (NIC) to provide the same functions as a SCSI or a
326          Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
327 
328          To compile this driver as a module, choose M here: the
329          module will be called iscsi_tcp.
330 
331          The userspace component needed to initialize the driver, documentation,
332          and sample configuration files can be found here:
333 
334          http://open-iscsi.org
335 
336 config ISCSI_BOOT_SYSFS
337         tristate "iSCSI Boot Sysfs Interface"
338         default n
339         help
340           This option enables support for exposing iSCSI boot information
341           via sysfs to userspace. If you wish to export this information,
342           say Y. Otherwise, say N.
343 
344 source "drivers/scsi/cxgbi/Kconfig"
345 source "drivers/scsi/bnx2i/Kconfig"
346 source "drivers/scsi/bnx2fc/Kconfig"
347 source "drivers/scsi/be2iscsi/Kconfig"
348 
349 config SGIWD93_SCSI
350         tristate "SGI WD93C93 SCSI Driver"
351         depends on SGI_HAS_WD93 && SCSI
352         help
353           If you have a Western Digital WD93 SCSI controller on
354           an SGI MIPS system, say Y.  Otherwise, say N.
355 
356 config BLK_DEV_3W_XXXX_RAID
357         tristate "3ware 5/6/7/8xxx ATA-RAID support"
358         depends on PCI && SCSI
359         help
360           3ware is the only hardware ATA-Raid product in Linux to date.
361           This card is 2,4, or 8 channel master mode support only.
362           SCSI support required!!!
363 
364           <http://www.3ware.com/>
365 
366           Please read the comments at the top of
367           <file:drivers/scsi/3w-xxxx.c>.
368 
369 config SCSI_HPSA
370         tristate "HP Smart Array SCSI driver"
371         depends on PCI && SCSI
372         select CHECK_SIGNATURE
373         help
374           This driver supports HP Smart Array Controllers (circa 2009).
375           It is a SCSI alternative to the cciss driver, which is a block
376           driver.  Anyone wishing to use HP Smart Array controllers who
377           would prefer the devices be presented to linux as SCSI devices,
378           rather than as generic block devices should say Y here.
379 
380 config SCSI_3W_9XXX
381         tristate "3ware 9xxx SATA-RAID support"
382         depends on PCI && SCSI
383         help
384           This driver supports the 9000 series 3ware SATA-RAID cards.
385 
386           <http://www.amcc.com>
387 
388           Please read the comments at the top of
389           <file:drivers/scsi/3w-9xxx.c>.
390 
391 config SCSI_3W_SAS
392         tristate "3ware 97xx SAS/SATA-RAID support"
393         depends on PCI && SCSI
394         help
395           This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
396 
397           <http://www.lsi.com>
398 
399           Please read the comments at the top of
400           <file:drivers/scsi/3w-sas.c>.
401 
402 config SCSI_7000FASST
403         tristate "7000FASST SCSI support"
404         depends on ISA && SCSI && ISA_DMA_API
405         select CHECK_SIGNATURE
406         help
407           This driver supports the Western Digital 7000 SCSI host adapter
408           family.  Some information is in the source:
409           <file:drivers/scsi/wd7000.c>.
410 
411           To compile this driver as a module, choose M here: the
412           module will be called wd7000.
413 
414 config SCSI_ACARD
415         tristate "ACARD SCSI support"
416         depends on PCI && SCSI
417         help
418           This driver supports the ACARD SCSI host adapter.
419           Support Chip <ATP870 ATP876 ATP880 ATP885>
420           To compile this driver as a module, choose M here: the
421           module will be called atp870u.
422 
423 config SCSI_AHA152X
424         tristate "Adaptec AHA152X/2825 support"
425         depends on ISA && SCSI
426         select SCSI_SPI_ATTRS
427         select CHECK_SIGNATURE
428         ---help---
429           This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
430           SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
431           must be manually specified in this case.
432 
433           It is explained in section 3.3 of the SCSI-HOWTO, available from
434           <http://www.tldp.org/docs.html#howto>. You might also want to
435           read the file <file:Documentation/scsi/aha152x.txt>.
436 
437           To compile this driver as a module, choose M here: the
438           module will be called aha152x.
439 
440 config SCSI_AHA1542
441         tristate "Adaptec AHA1542 support"
442         depends on ISA && SCSI && ISA_DMA_API
443         ---help---
444           This is support for a SCSI host adapter.  It is explained in section
445           3.4 of the SCSI-HOWTO, available from
446           <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
447           purchased by Adaptec, and some former Trantor products are being
448           sold under the Adaptec name.  If it doesn't work out of the box, you
449           may have to change some settings in <file:drivers/scsi/aha1542.h>.
450 
451           To compile this driver as a module, choose M here: the
452           module will be called aha1542.
453 
454 config SCSI_AHA1740
455         tristate "Adaptec AHA1740 support"
456         depends on EISA && SCSI
457         ---help---
458           This is support for a SCSI host adapter.  It is explained in section
459           3.5 of the SCSI-HOWTO, available from
460           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
461           of the box, you may have to change some settings in
462           <file:drivers/scsi/aha1740.h>.
463 
464           To compile this driver as a module, choose M here: the
465           module will be called aha1740.
466 
467 config SCSI_AACRAID
468         tristate "Adaptec AACRAID support"
469         depends on SCSI && PCI
470         help
471           This driver supports a variety of Dell, HP, Adaptec, IBM and
472           ICP storage products. For a list of supported products, refer
473           to <file:Documentation/scsi/aacraid.txt>.
474 
475           To compile this driver as a module, choose M here: the module
476           will be called aacraid.
477 
478 
479 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
480 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
481 source "drivers/scsi/aic94xx/Kconfig"
482 source "drivers/scsi/mvsas/Kconfig"
483 
484 config SCSI_MVUMI
485         tristate "Marvell UMI driver"
486         depends on SCSI && PCI
487         help
488           Module for Marvell Universal Message Interface(UMI) driver
489 
490           To compile this driver as a module, choose M here: the
491           module will be called mvumi.
492 
493 config SCSI_DPT_I2O
494         tristate "Adaptec I2O RAID support "
495         depends on SCSI && PCI && VIRT_TO_BUS
496         help
497           This driver supports all of Adaptec's I2O based RAID controllers as 
498           well as the DPT SmartRaid V cards.  This is an Adaptec maintained
499           driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
500 
501           To compile this driver as a module, choose M here: the
502           module will be called dpt_i2o.
503 
504 config SCSI_ADVANSYS
505         tristate "AdvanSys SCSI support"
506         depends on SCSI && VIRT_TO_BUS && !ARM
507         depends on ISA || EISA || PCI
508         help
509           This is a driver for all SCSI host adapters manufactured by
510           AdvanSys. It is documented in the kernel source in
511           <file:drivers/scsi/advansys.c>.
512 
513           To compile this driver as a module, choose M here: the
514           module will be called advansys.
515 
516 config SCSI_IN2000
517         tristate "Always IN2000 SCSI support"
518         depends on ISA && SCSI
519         help
520           This is support for an ISA bus SCSI host adapter.  You'll find more
521           information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
522           out of the box, you may have to change the jumpers for IRQ or
523           address selection.
524 
525           To compile this driver as a module, choose M here: the
526           module will be called in2000.
527 
528 config SCSI_ARCMSR
529         tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
530         depends on PCI && SCSI
531         help
532           This driver supports all of ARECA's SATA/SAS RAID controller cards.
533           This is an ARECA-maintained driver by Erich Chen.
534           If you have any problems, please mail to: <erich@areca.com.tw>.
535           Areca supports Linux RAID config tools.
536           Please link <http://www.areca.com.tw>
537 
538           To compile this driver as a module, choose M here: the
539           module will be called arcmsr (modprobe arcmsr).
540 
541 source "drivers/scsi/esas2r/Kconfig"
542 source "drivers/scsi/megaraid/Kconfig.megaraid"
543 source "drivers/scsi/mpt2sas/Kconfig"
544 source "drivers/scsi/mpt3sas/Kconfig"
545 source "drivers/scsi/ufs/Kconfig"
546 
547 config SCSI_HPTIOP
548         tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
549         depends on SCSI && PCI
550         help
551           This option enables support for HighPoint RocketRAID 3xxx/4xxx
552           controllers.
553 
554           To compile this driver as a module, choose M here; the module
555           will be called hptiop. If unsure, say N.
556 
557 config SCSI_BUSLOGIC
558         tristate "BusLogic SCSI support"
559         depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
560         ---help---
561           This is support for BusLogic MultiMaster and FlashPoint SCSI Host
562           Adapters. Consult the SCSI-HOWTO, available from
563           <http://www.tldp.org/docs.html#howto>, and the files
564           <file:Documentation/scsi/BusLogic.txt> and
565           <file:Documentation/scsi/FlashPoint.txt> for more information.
566           Note that support for FlashPoint is only available for 32-bit
567           x86 configurations.
568 
569           To compile this driver as a module, choose M here: the
570           module will be called BusLogic.
571 
572 config SCSI_FLASHPOINT
573         bool "FlashPoint support"
574         depends on SCSI_BUSLOGIC && PCI
575         help
576           This option allows you to add FlashPoint support to the
577           BusLogic SCSI driver. The FlashPoint SCCB Manager code is
578           substantial, so users of MultiMaster Host Adapters may not
579           wish to include it.
580 
581 config VMWARE_PVSCSI
582         tristate "VMware PVSCSI driver support"
583         depends on PCI && SCSI && X86
584         help
585           This driver supports VMware's para virtualized SCSI HBA.
586           To compile this driver as a module, choose M here: the
587           module will be called vmw_pvscsi.
588 
589 config XEN_SCSI_FRONTEND
590         tristate "XEN SCSI frontend driver"
591         depends on SCSI && XEN
592         select XEN_XENBUS_FRONTEND
593         help
594           The XEN SCSI frontend driver allows the kernel to access SCSI Devices
595           within another guest OS (usually Dom0).
596           Only needed if the kernel is running in a XEN guest and generic
597           SCSI access to a device is needed.
598 
599 config HYPERV_STORAGE
600         tristate "Microsoft Hyper-V virtual storage driver"
601         depends on SCSI && HYPERV
602         default HYPERV
603         help
604           Select this option to enable the Hyper-V virtual storage driver.
605 
606 config LIBFC
607         tristate "LibFC module"
608         depends on SCSI_FC_ATTRS
609         select CRC32
610         ---help---
611           Fibre Channel library module
612 
613 config LIBFCOE
614         tristate "LibFCoE module"
615         depends on LIBFC
616         ---help---
617           Library for Fibre Channel over Ethernet module
618 
619 config FCOE
620         tristate "FCoE module"
621         depends on PCI
622         depends on LIBFCOE
623         ---help---
624           Fibre Channel over Ethernet module
625 
626 config FCOE_FNIC
627         tristate "Cisco FNIC Driver"
628         depends on PCI && X86
629         depends on LIBFCOE
630         help
631           This is support for the Cisco PCI-Express FCoE HBA.
632 
633           To compile this driver as a module, choose M here and read
634           <file:Documentation/scsi/scsi.txt>.
635           The module will be called fnic.
636 
637 config SCSI_DMX3191D
638         tristate "DMX3191D SCSI support"
639         depends on PCI && SCSI
640         select SCSI_SPI_ATTRS
641         help
642           This is support for Domex DMX3191D SCSI Host Adapters.
643 
644           To compile this driver as a module, choose M here: the
645           module will be called dmx3191d.
646 
647 config SCSI_DTC3280
648         tristate "DTC3180/3280 SCSI support"
649         depends on ISA && SCSI
650         select SCSI_SPI_ATTRS
651         select CHECK_SIGNATURE
652         help
653           This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
654           the SCSI-HOWTO, available from
655           <http://www.tldp.org/docs.html#howto>, and the file
656           <file:Documentation/scsi/dtc3x80.txt>.
657 
658           To compile this driver as a module, choose M here: the
659           module will be called dtc.
660 
661 config SCSI_EATA
662         tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
663         depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
664         ---help---
665           This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
666           ISA and all EISA I/O addresses are probed looking for the "EATA"
667           signature. The addresses of all the PCI SCSI controllers reported
668           by the PCI subsystem are probed as well.
669 
670           You want to read the start of <file:drivers/scsi/eata.c> and the
671           SCSI-HOWTO, available from
672           <http://www.tldp.org/docs.html#howto>.
673 
674           To compile this driver as a module, choose M here: the
675           module will be called eata.
676 
677 config SCSI_EATA_TAGGED_QUEUE
678         bool "enable tagged command queueing"
679         depends on SCSI_EATA
680         help
681           This is a feature of SCSI-2 which improves performance: the host
682           adapter can send several SCSI commands to a device's queue even if
683           previous commands haven't finished yet.
684           This is equivalent to the "eata=tc:y" boot option.
685 
686 config SCSI_EATA_LINKED_COMMANDS
687         bool "enable elevator sorting"
688         depends on SCSI_EATA
689         help
690           This option enables elevator sorting for all probed SCSI disks and
691           CD-ROMs. It definitely reduces the average seek distance when doing
692           random seeks, but this does not necessarily result in a noticeable
693           performance improvement: your mileage may vary...
694           This is equivalent to the "eata=lc:y" boot option.
695 
696 config SCSI_EATA_MAX_TAGS
697         int "maximum number of queued commands"
698         depends on SCSI_EATA
699         default "16"
700         help
701           This specifies how many SCSI commands can be maximally queued for
702           each probed SCSI device. You should reduce the default value of 16
703           only if you have disks with buggy or limited tagged command support.
704           Minimum is 2 and maximum is 62. This value is also the window size
705           used by the elevator sorting option above. The effective value used
706           by the driver for each probed SCSI device is reported at boot time.
707           This is equivalent to the "eata=mq:8" boot option.
708 
709 config SCSI_EATA_PIO
710         tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
711         depends on (ISA || EISA || PCI) && SCSI && BROKEN
712         ---help---
713           This driver supports all EATA-PIO protocol compliant SCSI Host
714           Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
715           host adapters could also use this driver but are discouraged from
716           doing so, since this driver only supports hard disks and lacks
717           numerous features.  You might want to have a look at the SCSI-HOWTO,
718           available from <http://www.tldp.org/docs.html#howto>.
719 
720           To compile this driver as a module, choose M here: the
721           module will be called eata_pio.
722 
723 config SCSI_FUTURE_DOMAIN
724         tristate "Future Domain 16xx SCSI/AHA-2920A support"
725         depends on (ISA || PCI) && SCSI
726         select CHECK_SIGNATURE
727         ---help---
728           This is support for Future Domain's 16-bit SCSI host adapters
729           (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
730           other adapters based on the Future Domain chipsets (Quantum
731           ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
732           It is explained in section 3.7 of the SCSI-HOWTO, available from
733           <http://www.tldp.org/docs.html#howto>.
734 
735           NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
736           and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
737           controller support"). This Future Domain driver works with the older
738           Adaptec AHA-2920A boards with a Future Domain chip on them.
739 
740           To compile this driver as a module, choose M here: the
741           module will be called fdomain.
742 
743 config SCSI_GDTH
744         tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
745         depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
746         ---help---
747           Formerly called GDT SCSI Disk Array Controller Support.
748 
749           This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
750           manufactured by Intel Corporation/ICP vortex GmbH. It is documented
751           in the kernel source in <file:drivers/scsi/gdth.c> and
752           <file:drivers/scsi/gdth.h>.
753 
754           To compile this driver as a module, choose M here: the
755           module will be called gdth.
756 
757 config SCSI_ISCI
758         tristate "Intel(R) C600 Series Chipset SAS Controller"
759         depends on PCI && SCSI
760         depends on X86
761         select SCSI_SAS_LIBSAS
762         ---help---
763           This driver supports the 6Gb/s SAS capabilities of the storage
764           control unit found in the Intel(R) C600 series chipset.
765 
766 config SCSI_GENERIC_NCR5380
767         tristate "Generic NCR5380/53c400 SCSI PIO support"
768         depends on ISA && SCSI
769         select SCSI_SPI_ATTRS
770         ---help---
771           This is a driver for the old NCR 53c80 series of SCSI controllers
772           on boards using PIO. Most boards such as the Trantor T130 fit this
773           category, along with a large number of ISA 8bit controllers shipped
774           for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
775           you should select the specific driver for that card rather than
776           generic 5380 support.
777 
778           It is explained in section 3.8 of the SCSI-HOWTO, available from
779           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
780           of the box, you may have to change some settings in
781           <file:drivers/scsi/g_NCR5380.h>.
782 
783           To compile this driver as a module, choose M here: the
784           module will be called g_NCR5380.
785 
786 config SCSI_GENERIC_NCR5380_MMIO
787         tristate "Generic NCR5380/53c400 SCSI MMIO support"
788         depends on ISA && SCSI
789         select SCSI_SPI_ATTRS
790         ---help---
791           This is a driver for the old NCR 53c80 series of SCSI controllers
792           on boards using memory mapped I/O. 
793           It is explained in section 3.8 of the SCSI-HOWTO, available from
794           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
795           of the box, you may have to change some settings in
796           <file:drivers/scsi/g_NCR5380.h>.
797 
798           To compile this driver as a module, choose M here: the
799           module will be called g_NCR5380_mmio.
800 
801 config SCSI_GENERIC_NCR53C400
802         bool "Enable NCR53c400 extensions"
803         depends on SCSI_GENERIC_NCR5380
804         help
805           This enables certain optimizations for the NCR53c400 SCSI cards.
806           You might as well try it out.  Note that this driver will only probe
807           for the Trantor T130B in its default configuration; you might have
808           to pass a command line option to the kernel at boot time if it does
809           not detect your card.  See the file
810           <file:Documentation/scsi/g_NCR5380.txt> for details.
811 
812 config SCSI_IPS
813         tristate "IBM ServeRAID support"
814         depends on PCI && SCSI
815         ---help---
816           This is support for the IBM ServeRAID hardware RAID controllers.
817           See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
818           and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
819           for more information.  If this driver does not work correctly
820           without modification please contact the author by email at
821           <ipslinux@adaptec.com>.
822 
823           To compile this driver as a module, choose M here: the
824           module will be called ips.
825 
826 config SCSI_IBMVSCSI
827         tristate "IBM Virtual SCSI support"
828         depends on PPC_PSERIES
829         select SCSI_SRP_ATTRS
830         help
831           This is the IBM POWER Virtual SCSI Client
832 
833           To compile this driver as a module, choose M here: the
834           module will be called ibmvscsi.
835 
836 config SCSI_IBMVFC
837         tristate "IBM Virtual FC support"
838         depends on PPC_PSERIES && SCSI
839         depends on SCSI_FC_ATTRS
840         help
841           This is the IBM POWER Virtual FC Client
842 
843           To compile this driver as a module, choose M here: the
844           module will be called ibmvfc.
845 
846 config SCSI_IBMVFC_TRACE
847         bool "enable driver internal trace"
848         depends on SCSI_IBMVFC
849         default y
850         help
851           If you say Y here, the driver will trace all commands issued
852           to the adapter. Performance impact is minimal. Trace can be
853           dumped using /sys/class/scsi_host/hostXX/trace.
854 
855 config SCSI_INITIO
856         tristate "Initio 9100U(W) support"
857         depends on PCI && SCSI
858         help
859           This is support for the Initio 91XXU(W) SCSI host adapter.  Please
860           read the SCSI-HOWTO, available from
861           <http://www.tldp.org/docs.html#howto>.
862 
863           To compile this driver as a module, choose M here: the
864           module will be called initio.
865 
866 config SCSI_INIA100
867         tristate "Initio INI-A100U2W support"
868         depends on PCI && SCSI
869         help
870           This is support for the Initio INI-A100U2W SCSI host adapter.
871           Please read the SCSI-HOWTO, available from
872           <http://www.tldp.org/docs.html#howto>.
873 
874           To compile this driver as a module, choose M here: the
875           module will be called a100u2w.
876 
877 config SCSI_PPA
878         tristate "IOMEGA parallel port (ppa - older drives)"
879         depends on SCSI && PARPORT_PC
880         ---help---
881           This driver supports older versions of IOMEGA's parallel port ZIP
882           drive (a 100 MB removable media device).
883 
884           Note that you can say N here if you have the SCSI version of the ZIP
885           drive: it will be supported automatically if you said Y to the
886           generic "SCSI disk support", above.
887 
888           If you have the ZIP Plus drive or a more recent parallel port ZIP
889           drive (if the supplied cable with the drive is labeled "AutoDetect")
890           then you should say N here and Y to "IOMEGA parallel port (imm -
891           newer drives)", below.
892 
893           For more information about this driver and how to use it you should
894           read the file <file:Documentation/scsi/ppa.txt>.  You should also read
895           the SCSI-HOWTO, which is available from
896           <http://www.tldp.org/docs.html#howto>.  If you use this driver,
897           you will still be able to use the parallel port for other tasks,
898           such as a printer; it is safe to compile both drivers into the
899           kernel.
900 
901           To compile this driver as a module, choose M here: the
902           module will be called ppa.
903 
904 config SCSI_IMM
905         tristate "IOMEGA parallel port (imm - newer drives)"
906         depends on SCSI && PARPORT_PC
907         ---help---
908           This driver supports newer versions of IOMEGA's parallel port ZIP
909           drive (a 100 MB removable media device).
910 
911           Note that you can say N here if you have the SCSI version of the ZIP
912           drive: it will be supported automatically if you said Y to the
913           generic "SCSI disk support", above.
914 
915           If you have the ZIP Plus drive or a more recent parallel port ZIP
916           drive (if the supplied cable with the drive is labeled "AutoDetect")
917           then you should say Y here; if you have an older ZIP drive, say N
918           here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
919 
920           For more information about this driver and how to use it you should
921           read the file <file:Documentation/scsi/ppa.txt>.  You should also read
922           the SCSI-HOWTO, which is available from
923           <http://www.tldp.org/docs.html#howto>.  If you use this driver,
924           you will still be able to use the parallel port for other tasks,
925           such as a printer; it is safe to compile both drivers into the
926           kernel.
927 
928           To compile this driver as a module, choose M here: the
929           module will be called imm.
930 
931 config SCSI_IZIP_EPP16
932         bool "ppa/imm option - Use slow (but safe) EPP-16"
933         depends on SCSI_PPA || SCSI_IMM
934         ---help---
935           EPP (Enhanced Parallel Port) is a standard for parallel ports which
936           allows them to act as expansion buses that can handle up to 64
937           peripheral devices.
938 
939           Some parallel port chipsets are slower than their motherboard, and
940           so we have to control the state of the chipset's FIFO queue every
941           now and then to avoid data loss. This will be done if you say Y
942           here.
943 
944           Generally, saying Y is the safe option and slows things down a bit.
945 
946 config SCSI_IZIP_SLOW_CTR
947         bool "ppa/imm option - Assume slow parport control register"
948         depends on SCSI_PPA || SCSI_IMM
949         help
950           Some parallel ports are known to have excessive delays between
951           changing the parallel port control register and good data being
952           available on the parallel port data/status register. This option
953           forces a small delay (1.0 usec to be exact) after changing the
954           control register to let things settle out. Enabling this option may
955           result in a big drop in performance but some very old parallel ports
956           (found in 386 vintage machines) will not work properly.
957 
958           Generally, saying N is fine.
959 
960 config SCSI_NCR53C406A
961         tristate "NCR53c406a SCSI support"
962         depends on ISA && SCSI
963         help
964           This is support for the NCR53c406a SCSI host adapter.  For user
965           configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
966           in the kernel source.  Also read the SCSI-HOWTO, available from
967           <http://www.tldp.org/docs.html#howto>.
968 
969           To compile this driver as a module, choose M here: the
970           module will be called NCR53c406.
971 
972 config SCSI_NCR_D700
973         tristate "NCR Dual 700 MCA SCSI support"
974         depends on MCA && SCSI
975         select SCSI_SPI_ATTRS
976         help
977           This is a driver for the MicroChannel Dual 700 card produced by
978           NCR and commonly used in 345x/35xx/4100 class machines.  It always
979           tries to negotiate sync and uses tag command queueing.
980 
981           Unless you have an NCR manufactured machine, the chances are that
982           you do not have this SCSI card, so say N.
983 
984 config SCSI_LASI700
985         tristate "HP Lasi SCSI support for 53c700/710"
986         depends on GSC && SCSI
987         select SCSI_SPI_ATTRS
988         help
989           This is a driver for the SCSI controller in the Lasi chip found in
990           many PA-RISC workstations & servers.  If you do not know whether you
991           have a Lasi chip, it is safe to say "Y" here.
992 
993 config SCSI_SNI_53C710
994         tristate "SNI RM SCSI support for 53c710"
995         depends on SNI_RM && SCSI
996         select SCSI_SPI_ATTRS
997         select 53C700_LE_ON_BE
998         help
999           This is a driver for the onboard SCSI controller found in older
1000           SNI RM workstations & servers.
1001 
1002 config 53C700_LE_ON_BE
1003         bool
1004         depends on SCSI_LASI700
1005         default y
1006 
1007 config SCSI_STEX
1008         tristate "Promise SuperTrak EX Series support"
1009         depends on PCI && SCSI
1010         ---help---
1011           This driver supports Promise SuperTrak EX series storage controllers.
1012 
1013           Promise provides Linux RAID configuration utility for these
1014           controllers. Please visit <http://www.promise.com> to download.
1015 
1016           To compile this driver as a module, choose M here: the
1017           module will be called stex.
1018 
1019 config 53C700_BE_BUS
1020         bool
1021         depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1022         default y
1023 
1024 config SCSI_SYM53C8XX_2
1025         tristate "SYM53C8XX Version 2 SCSI support"
1026         depends on PCI && SCSI
1027         select SCSI_SPI_ATTRS
1028         ---help---
1029           This driver supports the whole NCR53C8XX/SYM53C8XX family of
1030           PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
1031           Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1032           language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1033           controllers; you need to use the Fusion MPT driver for that.
1034 
1035           Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1036           information.
1037 
1038 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1039         int "DMA addressing mode"
1040         depends on SCSI_SYM53C8XX_2
1041         default "1"
1042         ---help---
1043           This option only applies to PCI-SCSI chips that are PCI DAC
1044           capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1045 
1046           When set to 0, the driver will program the chip to only perform
1047           32-bit DMA.  When set to 1, the chip will be able to perform DMA
1048           to addresses up to 1TB.  When set to 2, the driver supports the
1049           full 64-bit DMA address range, but can only address 16 segments
1050           of 4 GB each.  This limits the total addressable range to 64 GB.
1051 
1052           Most machines with less than 4GB of memory should use a setting
1053           of 0 for best performance.  If your machine has 4GB of memory
1054           or more, you should set this option to 1 (the default).
1055 
1056           The still experimental value 2 (64 bit DMA addressing with 16
1057           x 4GB segments limitation) can be used on systems that require
1058           PCI address bits past bit 39 to be set for the addressing of
1059           memory using PCI DAC cycles.
1060 
1061 config SCSI_SYM53C8XX_DEFAULT_TAGS
1062         int "Default tagged command queue depth"
1063         depends on SCSI_SYM53C8XX_2
1064         default "16"
1065         help
1066           This is the default value of the command queue depth the
1067           driver will announce to the generic SCSI layer for devices
1068           that support tagged command queueing. This value can be changed
1069           from the boot command line.  This is a soft limit that cannot
1070           exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1071 
1072 config SCSI_SYM53C8XX_MAX_TAGS
1073         int "Maximum number of queued commands"
1074         depends on SCSI_SYM53C8XX_2
1075         default "64"
1076         help
1077           This option allows you to specify the maximum number of commands
1078           that can be queued to any device, when tagged command queuing is
1079           possible. The driver supports up to 256 queued commands per device.
1080           This value is used as a compiled-in hard limit.
1081 
1082 config SCSI_SYM53C8XX_MMIO
1083         bool "Use memory mapped IO"
1084         depends on SCSI_SYM53C8XX_2
1085         default y
1086         help
1087           Memory mapped IO is faster than Port IO.  Most people should
1088           answer Y here, but some machines may have problems.  If you have
1089           to answer N here, please report the problem to the maintainer.
1090 
1091 config SCSI_IPR
1092         tristate "IBM Power Linux RAID adapter support"
1093         depends on PCI && SCSI && ATA
1094         select FW_LOADER
1095         ---help---
1096           This driver supports the IBM Power Linux family RAID adapters.
1097           This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1098           as IBM iSeries 5702, 5703, 5709, and 570A.
1099 
1100 config SCSI_IPR_TRACE
1101         bool "enable driver internal trace"
1102         depends on SCSI_IPR
1103         default y
1104         help
1105           If you say Y here, the driver will trace all commands issued
1106           to the adapter. Performance impact is minimal. Trace can be
1107           dumped using /sys/bus/class/scsi_host/hostXX/trace.
1108 
1109 config SCSI_IPR_DUMP
1110         bool "enable adapter dump support"
1111         depends on SCSI_IPR
1112         default y
1113         help
1114           If you say Y here, the driver will support adapter crash dump.
1115           If you enable this support, the iprdump daemon can be used
1116           to capture adapter failure analysis information.
1117 
1118 config SCSI_ZALON
1119         tristate "Zalon SCSI support"
1120         depends on GSC && SCSI
1121         select SCSI_SPI_ATTRS
1122         help
1123           The Zalon is a GSC/HSC bus interface chip that sits between the
1124           PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1125           C110, J200, J210 and some D, K & R-class machines.  It's also
1126           used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1127           Say Y here if you have one of these machines or cards.
1128 
1129 config SCSI_NCR_Q720
1130         tristate "NCR Quad 720 MCA SCSI support"
1131         depends on MCA && SCSI
1132         select SCSI_SPI_ATTRS
1133         help
1134           This is a driver for the MicroChannel Quad 720 card produced by
1135           NCR and commonly used in 345x/35xx/4100 class machines.  It always
1136           tries to negotiate sync and uses tag command queueing.
1137 
1138           Unless you have an NCR manufactured machine, the chances are that
1139           you do not have this SCSI card, so say N.
1140 
1141 config SCSI_NCR53C8XX_DEFAULT_TAGS
1142         int "default tagged command queue depth"
1143         depends on SCSI_ZALON || SCSI_NCR_Q720
1144         default "8"
1145         ---help---
1146           "Tagged command queuing" is a feature of SCSI-2 which improves
1147           performance: the host adapter can send several SCSI commands to a
1148           device's queue even if previous commands haven't finished yet.
1149           Because the device is intelligent, it can optimize its operations
1150           (like head positioning) based on its own request queue. Some SCSI
1151           devices don't implement this properly; if you want to disable this
1152           feature, enter 0 or 1 here (it doesn't matter which).
1153 
1154           The default value is 8 and should be supported by most hard disks.
1155           This value can be overridden from the boot command line using the
1156           'tags' option as follows (example):
1157           'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1158           4, set queue depth to 16 for target 2 and target 3 on controller 0
1159           and set queue depth to 10 for target 0 / lun 2 on controller 1.
1160 
1161           The normal answer therefore is to go with the default 8 and to use
1162           a boot command line option for devices that need to use a different
1163           command queue depth.
1164 
1165           There is no safe option other than using good SCSI devices.
1166 
1167 config SCSI_NCR53C8XX_MAX_TAGS
1168         int "maximum number of queued commands"
1169         depends on SCSI_ZALON || SCSI_NCR_Q720
1170         default "32"
1171         ---help---
1172           This option allows you to specify the maximum number of commands
1173           that can be queued to any device, when tagged command queuing is
1174           possible. The default value is 32. Minimum is 2, maximum is 64.
1175           Modern hard disks are able to support 64 tags and even more, but
1176           do not seem to be faster when more than 32 tags are being used.
1177 
1178           So, the normal answer here is to go with the default value 32 unless
1179           you are using very large hard disks with large cache (>= 1 MB) that
1180           are able to take advantage of more than 32 tagged commands.
1181 
1182           There is no safe option and the default answer is recommended.
1183 
1184 config SCSI_NCR53C8XX_SYNC
1185         int "synchronous transfers frequency in MHz"
1186         depends on SCSI_ZALON || SCSI_NCR_Q720
1187         default "20"
1188         ---help---
1189           The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1190           rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
1191           are respectively the maximum data transfer rates in mega-transfers
1192           per second for each class.  For example, a FAST-20 Wide 16 device is
1193           able to transfer data at 20 million 16 bit packets per second for a
1194           total rate of 40 MB/s.
1195 
1196           You may specify 0 if you want to only use asynchronous data
1197           transfers. This is the safest and slowest option. Otherwise, specify
1198           a value between 5 and 80, depending on the capability of your SCSI
1199           controller.  The higher the number, the faster the data transfer.
1200           Note that 80 should normally be ok since the driver decreases the
1201           value automatically according to the controller's capabilities.
1202 
1203           Your answer to this question is ignored for controllers with NVRAM,
1204           since the driver will get this information from the user set-up.  It
1205           also can be overridden using a boot setup option, as follows
1206           (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1207           for FAST-20 synchronous data transfer (20 mega-transfers per
1208           second).
1209 
1210           The normal answer therefore is not to go with the default but to
1211           select the maximum value 80 allowing the driver to use the maximum
1212           value supported by each controller. If this causes problems with
1213           your SCSI devices, you should come back and decrease the value.
1214 
1215           There is no safe option other than using good cabling, right
1216           terminations and SCSI conformant devices.
1217 
1218 config SCSI_NCR53C8XX_NO_DISCONNECT
1219         bool "not allow targets to disconnect"
1220         depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1221         help
1222           This option is only provided for safety if you suspect some SCSI
1223           device of yours to not support properly the target-disconnect
1224           feature. In that case, you would say Y here. In general however, to
1225           not allow targets to disconnect is not reasonable if there is more
1226           than 1 device on a SCSI bus. The normal answer therefore is N.
1227 
1228 config SCSI_PAS16
1229         tristate "PAS16 SCSI support"
1230         depends on ISA && SCSI
1231         select SCSI_SPI_ATTRS
1232         ---help---
1233           This is support for a SCSI host adapter.  It is explained in section
1234           3.10 of the SCSI-HOWTO, available from
1235           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1236           of the box, you may have to change some settings in
1237           <file:drivers/scsi/pas16.h>.
1238 
1239           To compile this driver as a module, choose M here: the
1240           module will be called pas16.
1241 
1242 config SCSI_QLOGIC_FAS
1243         tristate "Qlogic FAS SCSI support"
1244         depends on ISA && SCSI
1245         ---help---
1246           This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1247           FastSCSI! cards as well as any other card based on the FASXX chip
1248           (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1249 
1250           This driver does NOT support the PCI versions of these cards. The
1251           PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1252           SCSI support"), below.
1253 
1254           Information about this driver is contained in
1255           <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
1256           SCSI-HOWTO, available from
1257           <http://www.tldp.org/docs.html#howto>.
1258 
1259           To compile this driver as a module, choose M here: the
1260           module will be called qlogicfas.
1261 
1262 config SCSI_QLOGIC_1280
1263         tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1264         depends on PCI && SCSI
1265         help
1266           Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1267 
1268           To compile this driver as a module, choose M here: the
1269           module will be called qla1280.
1270 
1271 config SCSI_QLOGICPTI
1272         tristate "PTI Qlogic, ISP Driver"
1273         depends on SBUS && SCSI
1274         help
1275           This driver supports SBUS SCSI controllers from PTI or QLogic. These
1276           controllers are known under Solaris as qpti and in the openprom as
1277           PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1278           driven by a different driver.
1279 
1280           To compile this driver as a module, choose M here: the
1281           module will be called qlogicpti.
1282 
1283 source "drivers/scsi/qla2xxx/Kconfig"
1284 source "drivers/scsi/qla4xxx/Kconfig"
1285 
1286 config SCSI_LPFC
1287         tristate "Emulex LightPulse Fibre Channel Support"
1288         depends on PCI && SCSI
1289         depends on SCSI_FC_ATTRS
1290         select CRC_T10DIF
1291         help
1292           This lpfc driver supports the Emulex LightPulse
1293           Family of Fibre Channel PCI host adapters.
1294 
1295 config SCSI_LPFC_DEBUG_FS
1296         bool "Emulex LightPulse Fibre Channel debugfs Support"
1297         depends on SCSI_LPFC && DEBUG_FS
1298         help
1299           This makes debugging information from the lpfc driver
1300           available via the debugfs filesystem.
1301 
1302 config SCSI_SIM710
1303         tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1304         depends on (EISA || MCA) && SCSI
1305         select SCSI_SPI_ATTRS
1306         ---help---
1307           This driver is for NCR53c710 based SCSI host adapters.
1308 
1309           It currently supports Compaq EISA cards and NCR MCA cards
1310 
1311 config SCSI_SYM53C416
1312         tristate "Symbios 53c416 SCSI support"
1313         depends on ISA && SCSI
1314         ---help---
1315           This is support for the sym53c416 SCSI host adapter, the SCSI
1316           adapter that comes with some HP scanners. This driver requires that
1317           the sym53c416 is configured first using some sort of PnP
1318           configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1319           are using isapnp then you need to compile this driver as a module
1320           and then load it using insmod after isapnp has run. The parameters
1321           of the configured card(s) should be passed to the driver. The format
1322           is:
1323 
1324           insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1325 
1326           To compile this driver as a module, choose M here: the
1327           module will be called sym53c416.
1328 
1329 config SCSI_DC395x
1330         tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1331         depends on PCI && SCSI
1332         ---help---
1333           This driver supports PCI SCSI host adapters based on the ASIC
1334           TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1335 
1336           This driver works, but is still in experimental status. So better
1337           have a bootable disk and a backup in case of emergency.
1338 
1339           Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1340 
1341           To compile this driver as a module, choose M here: the
1342           module will be called dc395x.
1343 
1344 config SCSI_DC390T
1345         tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1346         depends on PCI && SCSI
1347         ---help---
1348           This driver supports PCI SCSI host adapters based on the Am53C974A
1349           chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1350           PCscsi/PCnet (Am53/79C974) solutions.
1351 
1352           Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1353 
1354           Note that this driver does NOT support Tekram DC390W/U/F, which are
1355           based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1356 
1357           To compile this driver as a module, choose M here: the
1358           module will be called tmscsim.
1359 
1360 config SCSI_T128
1361         tristate "Trantor T128/T128F/T228 SCSI support"
1362         depends on ISA && SCSI
1363         select SCSI_SPI_ATTRS
1364         select CHECK_SIGNATURE
1365         ---help---
1366           This is support for a SCSI host adapter. It is explained in section
1367           3.11 of the SCSI-HOWTO, available from
1368           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1369           of the box, you may have to change some settings in
1370           <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
1371           Adaptec, and some former Trantor products are being sold under the
1372           Adaptec name.
1373 
1374           To compile this driver as a module, choose M here: the
1375           module will be called t128.
1376 
1377 config SCSI_U14_34F
1378         tristate "UltraStor 14F/34F support"
1379         depends on ISA && SCSI && ISA_DMA_API
1380         ---help---
1381           This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1382           The source at <file:drivers/scsi/u14-34f.c> contains some
1383           information about this hardware.  If the driver doesn't work out of
1384           the box, you may have to change some settings in
1385           <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
1386           <http://www.tldp.org/docs.html#howto>.  Note that there is also
1387           another driver for the same hardware: "UltraStor SCSI support",
1388           below.  You should say Y to both only if you want 24F support as
1389           well.
1390 
1391           To compile this driver as a module, choose M here: the
1392           module will be called u14-34f.
1393 
1394 config SCSI_U14_34F_TAGGED_QUEUE
1395         bool "enable tagged command queueing"
1396         depends on SCSI_U14_34F
1397         help
1398           This is a feature of SCSI-2 which improves performance: the host
1399           adapter can send several SCSI commands to a device's queue even if
1400           previous commands haven't finished yet.
1401           This is equivalent to the "u14-34f=tc:y" boot option.
1402 
1403 config SCSI_U14_34F_LINKED_COMMANDS
1404         bool "enable elevator sorting"
1405         depends on SCSI_U14_34F
1406         help
1407           This option enables elevator sorting for all probed SCSI disks and
1408           CD-ROMs. It definitely reduces the average seek distance when doing
1409           random seeks, but this does not necessarily result in a noticeable
1410           performance improvement: your mileage may vary...
1411           This is equivalent to the "u14-34f=lc:y" boot option.
1412 
1413 config SCSI_U14_34F_MAX_TAGS
1414         int "maximum number of queued commands"
1415         depends on SCSI_U14_34F
1416         default "8"
1417         help
1418           This specifies how many SCSI commands can be maximally queued for
1419           each probed SCSI device. You should reduce the default value of 8
1420           only if you have disks with buggy or limited tagged command support.
1421           Minimum is 2 and maximum is 14. This value is also the window size
1422           used by the elevator sorting option above. The effective value used
1423           by the driver for each probed SCSI device is reported at boot time.
1424           This is equivalent to the "u14-34f=mq:8" boot option.
1425 
1426 config SCSI_ULTRASTOR
1427         tristate "UltraStor SCSI support"
1428         depends on X86 && ISA && SCSI
1429         ---help---
1430           This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1431           adapter family.  This driver is explained in section 3.12 of the
1432           SCSI-HOWTO, available from
1433           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1434           of the box, you may have to change some settings in
1435           <file:drivers/scsi/ultrastor.h>.
1436 
1437           Note that there is also another driver for the same hardware:
1438           "UltraStor 14F/34F support", above.
1439 
1440           To compile this driver as a module, choose M here: the
1441           module will be called ultrastor.
1442 
1443 config SCSI_NSP32
1444         tristate "Workbit NinjaSCSI-32Bi/UDE support"
1445         depends on PCI && SCSI && !64BIT
1446         help
1447           This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1448           SCSI host adapter. Please read the SCSI-HOWTO, available from
1449           <http://www.tldp.org/docs.html#howto>.
1450 
1451           To compile this driver as a module, choose M here: the
1452           module will be called nsp32.
1453 
1454 config SCSI_DEBUG
1455         tristate "SCSI debugging host simulator"
1456         depends on SCSI
1457         select CRC_T10DIF
1458         help
1459           This is a host adapter simulator that can simulate multiple hosts
1460           each with multiple dummy SCSI devices (disks). It defaults to one
1461           host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1462           RAM as storage (i.e. it is a ramdisk). To save space when multiple
1463           dummy disks are simulated, they share the same kernel RAM for 
1464           their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
1465           information. This driver is primarily of use to those testing the
1466           SCSI and block subsystems. If unsure, say N.
1467 
1468 config SCSI_MESH
1469         tristate "MESH (Power Mac internal SCSI) support"
1470         depends on PPC32 && PPC_PMAC && SCSI
1471         help
1472           Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1473           SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1474           other Power Macintoshes do). Say Y to include support for this SCSI
1475           adaptor.
1476 
1477           To compile this driver as a module, choose M here: the
1478           module will be called mesh.
1479 
1480 config SCSI_MESH_SYNC_RATE
1481         int "maximum synchronous transfer rate (MB/s) (0 = async)"
1482         depends on SCSI_MESH
1483         default "5"
1484         help
1485           On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1486           drives a bus which is entirely internal to the machine (such as the
1487           7500, 7600, 8500, etc.), the MESH is capable of synchronous
1488           operation at up to 10 MB/s. On machines where the SCSI bus
1489           controlled by the MESH can have external devices connected, it is
1490           usually rated at 5 MB/s. 5 is a safe value here unless you know the
1491           MESH SCSI bus is internal only; in that case you can say 10. Say 0
1492           to disable synchronous operation.
1493 
1494 config SCSI_MESH_RESET_DELAY_MS
1495         int "initial bus reset delay (ms) (0 = no reset)"
1496         depends on SCSI_MESH
1497         default "4000"
1498 
1499 config SCSI_MAC53C94
1500         tristate "53C94 (Power Mac external SCSI) support"
1501         depends on PPC32 && PPC_PMAC && SCSI
1502         help
1503           On Power Macintoshes (and clones) with two SCSI buses, the external
1504           SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1505           machines which only have one SCSI bus, such as the 7200, also use
1506           the 53C94. Say Y to include support for the 53C94.
1507 
1508           To compile this driver as a module, choose M here: the
1509           module will be called mac53c94.
1510 
1511 source "drivers/scsi/arm/Kconfig"
1512 
1513 config JAZZ_ESP
1514         bool "MIPS JAZZ FAS216 SCSI support"
1515         depends on MACH_JAZZ && SCSI
1516         select SCSI_SPI_ATTRS
1517         help
1518           This is the driver for the onboard SCSI host adapter of MIPS Magnum
1519           4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1520           systems.
1521 
1522 config A3000_SCSI
1523         tristate "A3000 WD33C93A support"
1524         depends on AMIGA && SCSI
1525         help
1526           If you have an Amiga 3000 and have SCSI devices connected to the
1527           built-in SCSI controller, say Y. Otherwise, say N.
1528 
1529           To compile this driver as a module, choose M here: the
1530           module will be called a3000.
1531 
1532 config A2091_SCSI
1533         tristate "A2091/A590 WD33C93A support"
1534         depends on ZORRO && SCSI
1535         help
1536           If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1537           say N.
1538 
1539           To compile this driver as a module, choose M here: the
1540           module will be called a2091.
1541 
1542 config GVP11_SCSI
1543         tristate "GVP Series II WD33C93A support"
1544         depends on ZORRO && SCSI
1545         ---help---
1546           If you have a Great Valley Products Series II SCSI controller,
1547           answer Y. Also say Y if you have a later model of GVP SCSI
1548           controller (such as the GVP A4008 or a Combo board). Otherwise,
1549           answer N. This driver does NOT work for the T-Rex series of
1550           accelerators from TekMagic and GVP-M.
1551 
1552           To compile this driver as a module, choose M here: the
1553           module will be called gvp11.
1554 
1555 config SCSI_A4000T
1556         tristate "A4000T NCR53c710 SCSI support"
1557         depends on AMIGA && SCSI
1558         select SCSI_SPI_ATTRS
1559         help
1560           If you have an Amiga 4000T and have SCSI devices connected to the
1561           built-in SCSI controller, say Y. Otherwise, say N.
1562 
1563           To compile this driver as a module, choose M here: the
1564           module will be called a4000t.
1565 
1566 config SCSI_ZORRO7XX
1567         tristate "Zorro NCR53c710 SCSI support"
1568         depends on ZORRO && SCSI
1569         select SCSI_SPI_ATTRS
1570         help
1571           Support for various NCR53c710-based SCSI controllers on Zorro
1572           expansion boards for the Amiga.
1573           This includes:
1574             - the Amiga 4091 Zorro III SCSI-2 controller,
1575             - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1576               (info at
1577               <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1578             - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1579               accelerator card for the Amiga 1200,
1580             - the SCSI controller on the GVP Turbo 040/060 accelerator.
1581 
1582 config ATARI_SCSI
1583         tristate "Atari native SCSI support"
1584         depends on ATARI && SCSI
1585         select SCSI_SPI_ATTRS
1586         select NVRAM
1587         ---help---
1588           If you have an Atari with built-in NCR5380 SCSI controller (TT,
1589           Falcon, ...) say Y to get it supported. Of course also, if you have
1590           a compatible SCSI controller (e.g. for Medusa).
1591 
1592           To compile this driver as a module, choose M here: the
1593           module will be called atari_scsi.
1594 
1595           This driver supports both styles of NCR integration into the
1596           system: the TT style (separate DMA), and the Falcon style (via
1597           ST-DMA, replacing ACSI).  It does NOT support other schemes, like
1598           in the Hades (without DMA).
1599 
1600 config ATARI_SCSI_TOSHIBA_DELAY
1601         bool "Long delays for Toshiba CD-ROMs"
1602         depends on ATARI_SCSI
1603         help
1604           This option increases the delay after a SCSI arbitration to
1605           accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1606           use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1607           would impact performance a bit, so say N.
1608 
1609 config ATARI_SCSI_RESET_BOOT
1610         bool "Reset SCSI-devices at boottime"
1611         depends on ATARI_SCSI
1612         help
1613           Reset the devices on your Atari whenever it boots.  This makes the
1614           boot process fractionally longer but may assist recovery from errors
1615           that leave the devices with SCSI operations partway completed.
1616 
1617 config MAC_SCSI
1618         bool "Macintosh NCR5380 SCSI"
1619         depends on MAC && SCSI=y
1620         select SCSI_SPI_ATTRS
1621         help
1622           This is the NCR 5380 SCSI controller included on most of the 68030
1623           based Macintoshes.  If you have one of these say Y and read the
1624           SCSI-HOWTO, available from
1625           <http://www.tldp.org/docs.html#howto>.
1626 
1627 config SCSI_MAC_ESP
1628         tristate "Macintosh NCR53c9[46] SCSI"
1629         depends on MAC && SCSI
1630         select SCSI_SPI_ATTRS
1631         help
1632           This is the NCR 53c9x SCSI controller found on most of the 68040
1633           based Macintoshes.
1634 
1635           To compile this driver as a module, choose M here: the module
1636           will be called mac_esp.
1637 
1638 config MVME147_SCSI
1639         bool "WD33C93 SCSI driver for MVME147"
1640         depends on MVME147 && SCSI=y
1641         select SCSI_SPI_ATTRS
1642         help
1643           Support for the on-board SCSI controller on the Motorola MVME147
1644           single-board computer.
1645 
1646 config MVME16x_SCSI
1647         tristate "NCR53C710 SCSI driver for MVME16x"
1648         depends on MVME16x && SCSI
1649         select SCSI_SPI_ATTRS
1650         help
1651           The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1652           SCSI controller chip.  Almost everyone using one of these boards
1653           will want to say Y to this question.
1654 
1655 config BVME6000_SCSI
1656         tristate "NCR53C710 SCSI driver for BVME6000"
1657         depends on BVME6000 && SCSI
1658         select SCSI_SPI_ATTRS
1659         help
1660           The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1661           SCSI controller chip.  Almost everyone using one of these boards
1662           will want to say Y to this question.
1663 
1664 config SUN3_SCSI
1665         tristate "Sun3 NCR5380 SCSI"
1666         depends on SUN3 && SCSI
1667         select SCSI_SPI_ATTRS
1668         help
1669           This option will enable support for the OBIO (onboard io) NCR5380
1670           SCSI controller found in the Sun 3/50 and 3/60, as well as for
1671           "Sun3" type VME scsi controllers also based on the NCR5380.
1672           General Linux information on the Sun 3 series (now discontinued)
1673           is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1674 
1675 config SUN3X_ESP
1676         bool "Sun3x ESP SCSI"
1677         depends on SUN3X && SCSI=y
1678         select SCSI_SPI_ATTRS
1679         help
1680           The ESP was an on-board SCSI controller used on Sun 3/80
1681           machines.  Say Y here to compile in support for it.
1682 
1683 config SCSI_SUNESP
1684         tristate "Sparc ESP Scsi Driver"
1685         depends on SBUS && SCSI
1686         select SCSI_SPI_ATTRS
1687         help
1688           This is the driver for the Sun ESP SCSI host adapter. The ESP
1689           chipset is present in most SPARC SBUS-based computers and
1690           supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1691           esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1692 
1693           To compile this driver as a module, choose M here: the
1694           module will be called sun_esp.
1695 
1696 config ZFCP
1697         tristate "FCP host bus adapter driver for IBM eServer zSeries"
1698         depends on S390 && QDIO && SCSI
1699         depends on SCSI_FC_ATTRS
1700         help
1701           If you want to access SCSI devices attached to your IBM eServer
1702           zSeries by means of Fibre Channel interfaces say Y.
1703           For details please refer to the documentation provided by IBM at
1704           <http://oss.software.ibm.com/developerworks/opensource/linux390>
1705 
1706           This driver is also available as a module. This module will be
1707           called zfcp. If you want to compile it as a module, say M here
1708           and read <file:Documentation/kbuild/modules.txt>.
1709 
1710 config SCSI_PMCRAID
1711         tristate "PMC SIERRA Linux MaxRAID adapter support"
1712         depends on PCI && SCSI && NET
1713         ---help---
1714           This driver supports the PMC SIERRA MaxRAID adapters.
1715 
1716 config SCSI_PM8001
1717         tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1718         depends on PCI && SCSI
1719         select SCSI_SAS_LIBSAS
1720         help
1721           This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1722           based host adapters.
1723 
1724 config SCSI_BFA_FC
1725         tristate "Brocade BFA Fibre Channel Support"
1726         depends on PCI && SCSI
1727         depends on SCSI_FC_ATTRS
1728         help
1729           This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1730 
1731           To compile this driver as a module, choose M here. The module will
1732           be called bfa.
1733 
1734 config SCSI_VIRTIO
1735         tristate "virtio-scsi support"
1736         depends on VIRTIO
1737         select BLK_DEV_INTEGRITY
1738         help
1739           This is the virtual HBA driver for virtio.  If the kernel will
1740           be used in a virtual machine, say Y or M.
1741 
1742 source "drivers/scsi/csiostor/Kconfig"
1743 
1744 endif # SCSI_LOWLEVEL
1745 
1746 source "drivers/scsi/pcmcia/Kconfig"
1747 
1748 source "drivers/scsi/device_handler/Kconfig"
1749 
1750 source "drivers/scsi/osd/Kconfig"
1751 
1752 endmenu

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us