Version:  2.0.40 2.2.26 2.4.37 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4

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

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