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

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

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