Version:  2.0.40 2.2.26 2.4.37 3.1 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

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

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