1 menu "SCSI device support"
5 default y if SCSI=n || SCSI=y
9 tristate "RAID Transport Class"
17 tristate "SCSI device support"
19 select SCSI_DMA if HAS_DMA
21 select BLK_SCSI_REQUEST
23 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
24 any other SCSI device under Linux, say Y and make sure that you know
25 the name of your SCSI host adapter (the card inside your computer
26 that "speaks" the SCSI protocol, also called SCSI controller),
27 because you will be asked for it.
29 You also need to say Y here if you have a device which speaks
30 the SCSI protocol. Examples of this include the parallel port
31 version of the IOMEGA ZIP drive, USB storage devices, Fibre
32 Channel, and FireWire storage.
34 To compile this driver as a module, choose M here and read
35 <file:Documentation/scsi/scsi.txt>.
36 The module will be called scsi_mod.
38 However, do not compile this as a module if your root file system
39 (the one containing the directory /) is located on a SCSI device.
50 config SCSI_MQ_DEFAULT
51 bool "SCSI: use blk-mq I/O path by default"
55 This option enables the blk-mq based I/O path for SCSI devices by
56 default. With this option the scsi_mod.use_blk_mq module/boot
57 option defaults to Y, without it to N, but it can still be
58 overridden either way.
63 bool "legacy /proc/scsi/ support"
64 depends on SCSI && PROC_FS
67 This option enables support for the various files in
68 /proc/scsi. In Linux 2.6 this has been superseded by
69 files in sysfs but many legacy applications rely on this.
73 comment "SCSI support type (disk, tape, CD-ROM)"
77 tristate "SCSI disk support"
80 If you want to use SCSI hard disks, Fibre Channel disks,
81 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
82 USB storage or the SCSI or parallel port version of
83 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
84 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
85 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
88 To compile this driver as a module, choose M here and read
89 <file:Documentation/scsi/scsi.txt>.
90 The module will be called sd_mod.
92 Do not compile this driver as a module if your root file system
93 (the one containing the directory /) is located on a SCSI disk.
94 In this case, do not compile the driver for your SCSI host adapter
95 (below) as a module either.
98 tristate "SCSI tape support"
101 If you want to use a SCSI tape drive under Linux, say Y and read the
102 SCSI-HOWTO, available from
103 <http://www.tldp.org/docs.html#howto>, and
104 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
107 To compile this driver as a module, choose M here and read
108 <file:Documentation/scsi/scsi.txt>. The module will be called st.
111 tristate "SCSI OnStream SC-x0 tape support"
114 The OnStream SC-x0 SCSI tape drives cannot be driven by the
115 standard st driver, but instead need this special osst driver and
116 use the /dev/osstX char device nodes (major 206). Via usb-storage,
117 you may be able to drive the USB-x0 and DI-x0 drives as well.
118 Note that there is also a second generation of OnStream
119 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
120 tapes (QIC-157) and can be driven by the standard driver st.
121 For more information, you may have a look at the SCSI-HOWTO
122 <http://www.tldp.org/docs.html#howto> and
123 <file:Documentation/scsi/osst.txt> in the kernel source.
124 More info on the OnStream driver may be found on
125 <http://sourceforge.net/projects/osst/>
126 Please also have a look at the standard st docu, as most of it
127 applies to osst as well.
129 To compile this driver as a module, choose M here and read
130 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
133 tristate "SCSI CDROM support"
134 depends on SCSI && BLK_DEV
137 If you want to use a CD or DVD drive attached to your computer
138 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
139 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
141 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
143 To compile this driver as a module, choose M here and read
144 <file:Documentation/scsi/scsi.txt>.
145 The module will be called sr_mod.
148 tristate "SCSI generic support"
151 If you want to use SCSI scanners, synthesizers or CD-writers or just
152 about anything having "SCSI" in its name other than hard disks,
153 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
154 directly, so you need some additional software which knows how to
155 talk to these devices using the SCSI protocol:
157 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
158 writer software look at Cdrtools
159 (<http://cdrecord.berlios.de/private/cdrecord.html>)
160 and for burning a "disk at once": CDRDAO
161 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
162 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
163 For other devices, it's possible that you'll have to write the
164 driver software yourself. Please read the file
165 <file:Documentation/scsi/scsi-generic.txt> for more information.
167 To compile this driver as a module, choose M here and read
168 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
173 tristate "SCSI media changer support"
176 This is a driver for SCSI media changers. Most common devices are
177 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
178 don't need this for those tiny 6-slot cdrom changers. Media
179 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
180 If you have such hardware and want to use it with linux, say Y
181 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
183 If you want to compile this as a module ( = code which can be
184 inserted in and removed from the running kernel whenever you want),
185 say M here and read <file:Documentation/kbuild/modules.txt> and
186 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
189 config SCSI_ENCLOSURE
190 tristate "SCSI Enclosure Support"
191 depends on SCSI && ENCLOSURE_SERVICES
192 depends on m || SCSI_SAS_ATTRS != m
194 Enclosures are devices sitting on or in SCSI backplanes that
195 manage devices. If you have a disk cage, the chances are that
196 it has an enclosure device. Selecting this option will just allow
197 certain enclosure conditions to be reported and is not required.
199 config SCSI_CONSTANTS
200 bool "Verbose SCSI error reporting (kernel size += 36K)"
203 The error messages regarding your SCSI hardware will be easier to
204 understand if you say Y here; it will enlarge your kernel by about
205 36 KB. If in doubt, say Y.
208 bool "SCSI logging facility"
211 This turns on a logging facility that can be used to debug a number
212 of SCSI related problems.
214 If you say Y here, no logging output will appear by default, but you
215 can enable logging by saying Y to "/proc file system support" and
216 "Sysctl support" below and executing the command
218 echo <bitmask> > /proc/sys/dev/scsi/logging_level
220 where <bitmask> is a four byte value representing the logging type
221 and logging level for each type of logging selected.
223 There are a number of logging types and you can find them in the
224 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
225 are also described in that file and they determine the verbosity of
226 the logging for each logging type.
228 If you say N here, it may be harder to track down some types of SCSI
229 problems. If you say Y here your kernel will be somewhat larger, but
230 there should be no noticeable performance impact as long as you have
233 config SCSI_SCAN_ASYNC
234 bool "Asynchronous SCSI scanning"
237 The SCSI subsystem can probe for devices while the rest of the
238 system continues booting, and even probe devices on different
239 busses in parallel, leading to a significant speed-up.
241 You can override this choice by specifying "scsi_mod.scan=sync"
242 or async on the kernel's command line.
244 Note that this setting also affects whether resuming from
245 system suspend will be performed asynchronously.
247 menu "SCSI Transports"
250 config SCSI_SPI_ATTRS
251 tristate "Parallel SCSI (SPI) Transport Attributes"
254 If you wish to export transport-specific information about
255 each attached SCSI device to sysfs, say Y. Otherwise, say N.
258 tristate "FiberChannel Transport Attributes"
259 depends on SCSI && NET
260 select BLK_DEV_BSGLIB
263 If you wish to export transport-specific information about
264 each attached FiberChannel device to sysfs, say Y.
267 config SCSI_ISCSI_ATTRS
268 tristate "iSCSI Transport Attributes"
269 depends on SCSI && NET
270 select BLK_DEV_BSGLIB
272 If you wish to export transport-specific information about
273 each attached iSCSI device to sysfs, say Y.
276 config SCSI_SAS_ATTRS
277 tristate "SAS Transport Attributes"
279 select BLK_DEV_BSGLIB
281 If you wish to export transport-specific information about
282 each attached SAS device to sysfs, say Y.
284 source "drivers/scsi/libsas/Kconfig"
286 config SCSI_SRP_ATTRS
287 tristate "SRP Transport Attributes"
290 If you wish to export transport-specific information about
291 each attached SRP device to sysfs, say Y.
295 menuconfig SCSI_LOWLEVEL
296 bool "SCSI low-level drivers"
300 if SCSI_LOWLEVEL && SCSI
303 tristate "iSCSI Initiator over TCP/IP"
304 depends on SCSI && INET
308 select SCSI_ISCSI_ATTRS
310 The iSCSI Driver provides a host with the ability to access storage
311 through an IP network. The driver uses the iSCSI protocol to transport
312 SCSI requests and responses over a TCP/IP network between the host
313 (the "initiator") and "targets". Architecturally, the iSCSI driver
314 combines with the host's TCP/IP stack, network drivers, and Network
315 Interface Card (NIC) to provide the same functions as a SCSI or a
316 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
318 To compile this driver as a module, choose M here: the
319 module will be called iscsi_tcp.
321 The userspace component needed to initialize the driver, documentation,
322 and sample configuration files can be found here:
324 http://open-iscsi.org
326 config ISCSI_BOOT_SYSFS
327 tristate "iSCSI Boot Sysfs Interface"
330 This option enables support for exposing iSCSI boot information
331 via sysfs to userspace. If you wish to export this information,
332 say Y. Otherwise, say N.
334 source "drivers/scsi/cxgbi/Kconfig"
335 source "drivers/scsi/bnx2i/Kconfig"
336 source "drivers/scsi/bnx2fc/Kconfig"
337 source "drivers/scsi/be2iscsi/Kconfig"
338 source "drivers/scsi/cxlflash/Kconfig"
341 tristate "SGI WD93C93 SCSI Driver"
342 depends on SGI_HAS_WD93 && SCSI
344 If you have a Western Digital WD93 SCSI controller on
345 an SGI MIPS system, say Y. Otherwise, say N.
347 config BLK_DEV_3W_XXXX_RAID
348 tristate "3ware 5/6/7/8xxx ATA-RAID support"
349 depends on PCI && SCSI
351 3ware is the only hardware ATA-Raid product in Linux to date.
352 This card is 2,4, or 8 channel master mode support only.
353 SCSI support required!!!
355 <http://www.3ware.com/>
357 Please read the comments at the top of
358 <file:drivers/scsi/3w-xxxx.c>.
361 tristate "HP Smart Array SCSI driver"
362 depends on PCI && SCSI
363 select CHECK_SIGNATURE
364 select SCSI_SAS_ATTRS
366 This driver supports HP Smart Array Controllers (circa 2009).
367 It is a SCSI alternative to the cciss driver, which is a block
368 driver. Anyone wishing to use HP Smart Array controllers who
369 would prefer the devices be presented to linux as SCSI devices,
370 rather than as generic block devices should say Y here.
373 tristate "3ware 9xxx SATA-RAID support"
374 depends on PCI && SCSI
376 This driver supports the 9000 series 3ware SATA-RAID cards.
378 <http://www.amcc.com>
380 Please read the comments at the top of
381 <file:drivers/scsi/3w-9xxx.c>.
384 tristate "3ware 97xx SAS/SATA-RAID support"
385 depends on PCI && SCSI
387 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
391 Please read the comments at the top of
392 <file:drivers/scsi/3w-sas.c>.
395 tristate "ACARD SCSI support"
396 depends on PCI && SCSI
398 This driver supports the ACARD SCSI host adapter.
399 Support Chip <ATP870 ATP876 ATP880 ATP885>
400 To compile this driver as a module, choose M here: the
401 module will be called atp870u.
404 tristate "Adaptec AHA152X/2825 support"
405 depends on ISA && SCSI
406 select SCSI_SPI_ATTRS
407 select CHECK_SIGNATURE
409 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
410 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
411 must be manually specified in this case.
413 It is explained in section 3.3 of the SCSI-HOWTO, available from
414 <http://www.tldp.org/docs.html#howto>. You might also want to
415 read the file <file:Documentation/scsi/aha152x.txt>.
417 To compile this driver as a module, choose M here: the
418 module will be called aha152x.
421 tristate "Adaptec AHA1542 support"
422 depends on ISA && SCSI && ISA_DMA_API
424 This is support for a SCSI host adapter. It is explained in section
425 3.4 of the SCSI-HOWTO, available from
426 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
427 purchased by Adaptec, and some former Trantor products are being
428 sold under the Adaptec name. If it doesn't work out of the box, you
429 may have to change some settings in <file:drivers/scsi/aha1542.h>.
431 To compile this driver as a module, choose M here: the
432 module will be called aha1542.
435 tristate "Adaptec AHA1740 support"
436 depends on EISA && SCSI
438 This is support for a SCSI host adapter. It is explained in section
439 3.5 of the SCSI-HOWTO, available from
440 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
441 of the box, you may have to change some settings in
442 <file:drivers/scsi/aha1740.h>.
444 To compile this driver as a module, choose M here: the
445 module will be called aha1740.
448 tristate "Adaptec AACRAID support"
449 depends on SCSI && PCI
451 This driver supports a variety of Dell, HP, Adaptec, IBM and
452 ICP storage products. For a list of supported products, refer
453 to <file:Documentation/scsi/aacraid.txt>.
455 To compile this driver as a module, choose M here: the module
456 will be called aacraid.
459 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
460 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
461 source "drivers/scsi/aic94xx/Kconfig"
462 source "drivers/scsi/hisi_sas/Kconfig"
463 source "drivers/scsi/mvsas/Kconfig"
466 tristate "Marvell UMI driver"
467 depends on SCSI && PCI
469 Module for Marvell Universal Message Interface(UMI) driver
471 To compile this driver as a module, choose M here: the
472 module will be called mvumi.
475 tristate "Adaptec I2O RAID support "
476 depends on SCSI && PCI
478 This driver supports all of Adaptec's I2O based RAID controllers as
479 well as the DPT SmartRaid V cards. This is an Adaptec maintained
480 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
482 To compile this driver as a module, choose M here: the
483 module will be called dpt_i2o.
486 tristate "AdvanSys SCSI support"
488 depends on ISA || EISA || PCI
489 depends on ISA_DMA_API || !ISA
491 This is a driver for all SCSI host adapters manufactured by
492 AdvanSys. It is documented in the kernel source in
493 <file:drivers/scsi/advansys.c>.
495 To compile this driver as a module, choose M here: the
496 module will be called advansys.
499 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
500 depends on PCI && SCSI
502 This driver supports all of ARECA's SATA/SAS RAID controller cards.
503 This is an ARECA-maintained driver by Erich Chen.
504 If you have any problems, please mail to: <erich@areca.com.tw>.
505 Areca supports Linux RAID config tools.
506 Please link <http://www.areca.com.tw>
508 To compile this driver as a module, choose M here: the
509 module will be called arcmsr (modprobe arcmsr).
511 source "drivers/scsi/esas2r/Kconfig"
512 source "drivers/scsi/megaraid/Kconfig.megaraid"
513 source "drivers/scsi/mpt3sas/Kconfig"
514 source "drivers/scsi/smartpqi/Kconfig"
515 source "drivers/scsi/ufs/Kconfig"
518 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
519 depends on SCSI && PCI
521 This option enables support for HighPoint RocketRAID 3xxx/4xxx
524 To compile this driver as a module, choose M here; the module
525 will be called hptiop. If unsure, say N.
528 tristate "BusLogic SCSI support"
529 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
531 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
532 Adapters. Consult the SCSI-HOWTO, available from
533 <http://www.tldp.org/docs.html#howto>, and the files
534 <file:Documentation/scsi/BusLogic.txt> and
535 <file:Documentation/scsi/FlashPoint.txt> for more information.
536 Note that support for FlashPoint is only available for 32-bit
539 To compile this driver as a module, choose M here: the
540 module will be called BusLogic.
542 config SCSI_FLASHPOINT
543 bool "FlashPoint support"
544 depends on SCSI_BUSLOGIC && PCI
546 This option allows you to add FlashPoint support to the
547 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
548 substantial, so users of MultiMaster Host Adapters may not
552 tristate "VMware PVSCSI driver support"
553 depends on PCI && SCSI && X86
555 This driver supports VMware's para virtualized SCSI HBA.
556 To compile this driver as a module, choose M here: the
557 module will be called vmw_pvscsi.
559 config XEN_SCSI_FRONTEND
560 tristate "XEN SCSI frontend driver"
561 depends on SCSI && XEN
562 select XEN_XENBUS_FRONTEND
564 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
565 within another guest OS (usually Dom0).
566 Only needed if the kernel is running in a XEN guest and generic
567 SCSI access to a device is needed.
569 config HYPERV_STORAGE
570 tristate "Microsoft Hyper-V virtual storage driver"
571 depends on SCSI && HYPERV
572 depends on m || SCSI_FC_ATTRS != m
575 Select this option to enable the Hyper-V virtual storage driver.
578 tristate "LibFC module"
579 depends on SCSI_FC_ATTRS
582 Fibre Channel library module
585 tristate "LibFCoE module"
588 Library for Fibre Channel over Ethernet module
591 tristate "FCoE module"
595 Fibre Channel over Ethernet module
598 tristate "Cisco FNIC Driver"
599 depends on PCI && X86
602 This is support for the Cisco PCI-Express FCoE HBA.
604 To compile this driver as a module, choose M here and read
605 <file:Documentation/scsi/scsi.txt>.
606 The module will be called fnic.
609 tristate "Cisco SNIC Driver"
610 depends on PCI && SCSI
612 This is support for the Cisco PCI-Express SCSI HBA.
614 To compile this driver as a module, choose M here and read
615 <file:Documentation/scsi/scsi.txt>.
616 The module will be called snic.
618 config SCSI_SNIC_DEBUG_FS
619 bool "Cisco SNIC Driver Debugfs Support"
620 depends on SCSI_SNIC && DEBUG_FS
622 This enables to list debugging information from SNIC Driver
623 available via debugfs file system
626 tristate "DMX3191D SCSI support"
627 depends on PCI && SCSI
628 select SCSI_SPI_ATTRS
630 This is support for Domex DMX3191D SCSI Host Adapters.
632 To compile this driver as a module, choose M here: the
633 module will be called dmx3191d.
636 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
637 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
639 Formerly called GDT SCSI Disk Array Controller Support.
641 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
642 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
643 in the kernel source in <file:drivers/scsi/gdth.c> and
644 <file:drivers/scsi/gdth.h>.
646 To compile this driver as a module, choose M here: the
647 module will be called gdth.
650 tristate "Intel(R) C600 Series Chipset SAS Controller"
651 depends on PCI && SCSI
653 select SCSI_SAS_LIBSAS
655 This driver supports the 6Gb/s SAS capabilities of the storage
656 control unit found in the Intel(R) C600 series chipset.
658 config SCSI_GENERIC_NCR5380
659 tristate "Generic NCR5380/53c400 SCSI ISA card support"
660 depends on ISA && SCSI && HAS_IOPORT_MAP
661 select SCSI_SPI_ATTRS
663 This is a driver for old ISA card SCSI controllers based on a
664 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
665 Most boards such as the Trantor T130 fit this category, as do
666 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
668 To compile this driver as a module, choose M here: the
669 module will be called g_NCR5380.
672 tristate "IBM ServeRAID support"
673 depends on PCI && SCSI
675 This is support for the IBM ServeRAID hardware RAID controllers.
676 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
677 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
678 for more information. If this driver does not work correctly
679 without modification please contact the author by email at
680 <ipslinux@adaptec.com>.
682 To compile this driver as a module, choose M here: the
683 module will be called ips.
686 tristate "IBM Virtual SCSI support"
687 depends on PPC_PSERIES
688 select SCSI_SRP_ATTRS
690 This is the IBM POWER Virtual SCSI Client
692 To compile this driver as a module, choose M here: the
693 module will be called ibmvscsi.
695 config SCSI_IBMVSCSIS
696 tristate "IBM Virtual SCSI Server support"
697 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
699 This is the IBM POWER Virtual SCSI Target Server
700 This driver uses the SRP protocol for communication between servers
701 guest and/or the host that run on the same server.
702 More information on VSCSI protocol can be found at www.power.org
704 The userspace configuration needed to initialize the driver can be
707 https://github.com/powervm/ibmvscsis/wiki/Configuration
709 To compile this driver as a module, choose M here: the
710 module will be called ibmvscsis.
713 tristate "IBM Virtual FC support"
714 depends on PPC_PSERIES && SCSI
715 depends on SCSI_FC_ATTRS
717 This is the IBM POWER Virtual FC Client
719 To compile this driver as a module, choose M here: the
720 module will be called ibmvfc.
722 config SCSI_IBMVFC_TRACE
723 bool "enable driver internal trace"
724 depends on SCSI_IBMVFC
727 If you say Y here, the driver will trace all commands issued
728 to the adapter. Performance impact is minimal. Trace can be
729 dumped using /sys/class/scsi_host/hostXX/trace.
732 tristate "Initio 9100U(W) support"
733 depends on PCI && SCSI
735 This is support for the Initio 91XXU(W) SCSI host adapter. Please
736 read the SCSI-HOWTO, available from
737 <http://www.tldp.org/docs.html#howto>.
739 To compile this driver as a module, choose M here: the
740 module will be called initio.
743 tristate "Initio INI-A100U2W support"
744 depends on PCI && SCSI
746 This is support for the Initio INI-A100U2W SCSI host adapter.
747 Please read the SCSI-HOWTO, available from
748 <http://www.tldp.org/docs.html#howto>.
750 To compile this driver as a module, choose M here: the
751 module will be called a100u2w.
754 tristate "IOMEGA parallel port (ppa - older drives)"
755 depends on SCSI && PARPORT_PC
757 This driver supports older versions of IOMEGA's parallel port ZIP
758 drive (a 100 MB removable media device).
760 Note that you can say N here if you have the SCSI version of the ZIP
761 drive: it will be supported automatically if you said Y to the
762 generic "SCSI disk support", above.
764 If you have the ZIP Plus drive or a more recent parallel port ZIP
765 drive (if the supplied cable with the drive is labeled "AutoDetect")
766 then you should say N here and Y to "IOMEGA parallel port (imm -
767 newer drives)", below.
769 For more information about this driver and how to use it you should
770 read the file <file:Documentation/scsi/ppa.txt>. You should also read
771 the SCSI-HOWTO, which is available from
772 <http://www.tldp.org/docs.html#howto>. If you use this driver,
773 you will still be able to use the parallel port for other tasks,
774 such as a printer; it is safe to compile both drivers into the
777 To compile this driver as a module, choose M here: the
778 module will be called ppa.
781 tristate "IOMEGA parallel port (imm - newer drives)"
782 depends on SCSI && PARPORT_PC
784 This driver supports newer versions of IOMEGA's parallel port ZIP
785 drive (a 100 MB removable media device).
787 Note that you can say N here if you have the SCSI version of the ZIP
788 drive: it will be supported automatically if you said Y to the
789 generic "SCSI disk support", above.
791 If you have the ZIP Plus drive or a more recent parallel port ZIP
792 drive (if the supplied cable with the drive is labeled "AutoDetect")
793 then you should say Y here; if you have an older ZIP drive, say N
794 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
796 For more information about this driver and how to use it you should
797 read the file <file:Documentation/scsi/ppa.txt>. You should also read
798 the SCSI-HOWTO, which is available from
799 <http://www.tldp.org/docs.html#howto>. If you use this driver,
800 you will still be able to use the parallel port for other tasks,
801 such as a printer; it is safe to compile both drivers into the
804 To compile this driver as a module, choose M here: the
805 module will be called imm.
807 config SCSI_IZIP_EPP16
808 bool "ppa/imm option - Use slow (but safe) EPP-16"
809 depends on SCSI_PPA || SCSI_IMM
811 EPP (Enhanced Parallel Port) is a standard for parallel ports which
812 allows them to act as expansion buses that can handle up to 64
815 Some parallel port chipsets are slower than their motherboard, and
816 so we have to control the state of the chipset's FIFO queue every
817 now and then to avoid data loss. This will be done if you say Y
820 Generally, saying Y is the safe option and slows things down a bit.
822 config SCSI_IZIP_SLOW_CTR
823 bool "ppa/imm option - Assume slow parport control register"
824 depends on SCSI_PPA || SCSI_IMM
826 Some parallel ports are known to have excessive delays between
827 changing the parallel port control register and good data being
828 available on the parallel port data/status register. This option
829 forces a small delay (1.0 usec to be exact) after changing the
830 control register to let things settle out. Enabling this option may
831 result in a big drop in performance but some very old parallel ports
832 (found in 386 vintage machines) will not work properly.
834 Generally, saying N is fine.
837 tristate "HP Lasi SCSI support for 53c700/710"
838 depends on GSC && SCSI
839 select SCSI_SPI_ATTRS
841 This is a driver for the SCSI controller in the Lasi chip found in
842 many PA-RISC workstations & servers. If you do not know whether you
843 have a Lasi chip, it is safe to say "Y" here.
845 config SCSI_SNI_53C710
846 tristate "SNI RM SCSI support for 53c710"
847 depends on SNI_RM && SCSI
848 select SCSI_SPI_ATTRS
849 select 53C700_LE_ON_BE
851 This is a driver for the onboard SCSI controller found in older
852 SNI RM workstations & servers.
854 config 53C700_LE_ON_BE
856 depends on SCSI_LASI700 || SCSI_SNI_53C710
860 tristate "Promise SuperTrak EX Series support"
861 depends on PCI && SCSI
863 This driver supports Promise SuperTrak EX series storage controllers.
865 Promise provides Linux RAID configuration utility for these
866 controllers. Please visit <http://www.promise.com> to download.
868 To compile this driver as a module, choose M here: the
869 module will be called stex.
873 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
876 config SCSI_SYM53C8XX_2
877 tristate "SYM53C8XX Version 2 SCSI support"
878 depends on PCI && SCSI
879 select SCSI_SPI_ATTRS
881 This driver supports the whole NCR53C8XX/SYM53C8XX family of
882 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
883 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
884 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
885 controllers; you need to use the Fusion MPT driver for that.
887 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
890 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
891 int "DMA addressing mode"
892 depends on SCSI_SYM53C8XX_2
895 This option only applies to PCI-SCSI chips that are PCI DAC
896 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
898 When set to 0, the driver will program the chip to only perform
899 32-bit DMA. When set to 1, the chip will be able to perform DMA
900 to addresses up to 1TB. When set to 2, the driver supports the
901 full 64-bit DMA address range, but can only address 16 segments
902 of 4 GB each. This limits the total addressable range to 64 GB.
904 Most machines with less than 4GB of memory should use a setting
905 of 0 for best performance. If your machine has 4GB of memory
906 or more, you should set this option to 1 (the default).
908 The still experimental value 2 (64 bit DMA addressing with 16
909 x 4GB segments limitation) can be used on systems that require
910 PCI address bits past bit 39 to be set for the addressing of
911 memory using PCI DAC cycles.
913 config SCSI_SYM53C8XX_DEFAULT_TAGS
914 int "Default tagged command queue depth"
915 depends on SCSI_SYM53C8XX_2
918 This is the default value of the command queue depth the
919 driver will announce to the generic SCSI layer for devices
920 that support tagged command queueing. This value can be changed
921 from the boot command line. This is a soft limit that cannot
922 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
924 config SCSI_SYM53C8XX_MAX_TAGS
925 int "Maximum number of queued commands"
926 depends on SCSI_SYM53C8XX_2
929 This option allows you to specify the maximum number of commands
930 that can be queued to any device, when tagged command queuing is
931 possible. The driver supports up to 256 queued commands per device.
932 This value is used as a compiled-in hard limit.
934 config SCSI_SYM53C8XX_MMIO
935 bool "Use memory mapped IO"
936 depends on SCSI_SYM53C8XX_2
939 Memory mapped IO is faster than Port IO. Most people should
940 answer Y here, but some machines may have problems. If you have
941 to answer N here, please report the problem to the maintainer.
944 tristate "IBM Power Linux RAID adapter support"
945 depends on PCI && SCSI && ATA
950 This driver supports the IBM Power Linux family RAID adapters.
951 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
952 as IBM iSeries 5702, 5703, 5709, and 570A.
954 config SCSI_IPR_TRACE
955 bool "enable driver internal trace"
959 If you say Y here, the driver will trace all commands issued
960 to the adapter. Performance impact is minimal. Trace can be
961 dumped using /sys/bus/class/scsi_host/hostXX/trace.
964 bool "enable adapter dump support"
968 If you say Y here, the driver will support adapter crash dump.
969 If you enable this support, the iprdump daemon can be used
970 to capture adapter failure analysis information.
973 tristate "Zalon SCSI support"
974 depends on GSC && SCSI
975 select SCSI_SPI_ATTRS
977 The Zalon is a GSC/HSC bus interface chip that sits between the
978 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
979 C110, J200, J210 and some D, K & R-class machines. It's also
980 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
981 Say Y here if you have one of these machines or cards.
983 config SCSI_NCR53C8XX_DEFAULT_TAGS
984 int "default tagged command queue depth"
985 depends on SCSI_ZALON
988 "Tagged command queuing" is a feature of SCSI-2 which improves
989 performance: the host adapter can send several SCSI commands to a
990 device's queue even if previous commands haven't finished yet.
991 Because the device is intelligent, it can optimize its operations
992 (like head positioning) based on its own request queue. Some SCSI
993 devices don't implement this properly; if you want to disable this
994 feature, enter 0 or 1 here (it doesn't matter which).
996 The default value is 8 and should be supported by most hard disks.
997 This value can be overridden from the boot command line using the
998 'tags' option as follows (example):
999 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1000 4, set queue depth to 16 for target 2 and target 3 on controller 0
1001 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1003 The normal answer therefore is to go with the default 8 and to use
1004 a boot command line option for devices that need to use a different
1005 command queue depth.
1007 There is no safe option other than using good SCSI devices.
1009 config SCSI_NCR53C8XX_MAX_TAGS
1010 int "maximum number of queued commands"
1011 depends on SCSI_ZALON
1014 This option allows you to specify the maximum number of commands
1015 that can be queued to any device, when tagged command queuing is
1016 possible. The default value is 32. Minimum is 2, maximum is 64.
1017 Modern hard disks are able to support 64 tags and even more, but
1018 do not seem to be faster when more than 32 tags are being used.
1020 So, the normal answer here is to go with the default value 32 unless
1021 you are using very large hard disks with large cache (>= 1 MB) that
1022 are able to take advantage of more than 32 tagged commands.
1024 There is no safe option and the default answer is recommended.
1026 config SCSI_NCR53C8XX_SYNC
1027 int "synchronous transfers frequency in MHz"
1028 depends on SCSI_ZALON
1031 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1032 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1033 are respectively the maximum data transfer rates in mega-transfers
1034 per second for each class. For example, a FAST-20 Wide 16 device is
1035 able to transfer data at 20 million 16 bit packets per second for a
1036 total rate of 40 MB/s.
1038 You may specify 0 if you want to only use asynchronous data
1039 transfers. This is the safest and slowest option. Otherwise, specify
1040 a value between 5 and 80, depending on the capability of your SCSI
1041 controller. The higher the number, the faster the data transfer.
1042 Note that 80 should normally be ok since the driver decreases the
1043 value automatically according to the controller's capabilities.
1045 Your answer to this question is ignored for controllers with NVRAM,
1046 since the driver will get this information from the user set-up. It
1047 also can be overridden using a boot setup option, as follows
1048 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1049 for FAST-20 synchronous data transfer (20 mega-transfers per
1052 The normal answer therefore is not to go with the default but to
1053 select the maximum value 80 allowing the driver to use the maximum
1054 value supported by each controller. If this causes problems with
1055 your SCSI devices, you should come back and decrease the value.
1057 There is no safe option other than using good cabling, right
1058 terminations and SCSI conformant devices.
1060 config SCSI_NCR53C8XX_NO_DISCONNECT
1061 bool "not allow targets to disconnect"
1062 depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1064 This option is only provided for safety if you suspect some SCSI
1065 device of yours to not support properly the target-disconnect
1066 feature. In that case, you would say Y here. In general however, to
1067 not allow targets to disconnect is not reasonable if there is more
1068 than 1 device on a SCSI bus. The normal answer therefore is N.
1070 config SCSI_QLOGIC_FAS
1071 tristate "Qlogic FAS SCSI support"
1072 depends on ISA && SCSI
1074 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1075 FastSCSI! cards as well as any other card based on the FASXX chip
1076 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1078 This driver does NOT support the PCI versions of these cards. The
1079 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1080 SCSI support"), below.
1082 Information about this driver is contained in
1083 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1084 SCSI-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1087 To compile this driver as a module, choose M here: the
1088 module will be called qlogicfas.
1090 config SCSI_QLOGIC_1280
1091 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1092 depends on PCI && SCSI
1094 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1096 To compile this driver as a module, choose M here: the
1097 module will be called qla1280.
1099 config SCSI_QLOGICPTI
1100 tristate "PTI Qlogic, ISP Driver"
1101 depends on SBUS && SCSI
1103 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1104 controllers are known under Solaris as qpti and in the openprom as
1105 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1106 driven by a different driver.
1108 To compile this driver as a module, choose M here: the
1109 module will be called qlogicpti.
1111 source "drivers/scsi/qla2xxx/Kconfig"
1112 source "drivers/scsi/qla4xxx/Kconfig"
1113 source "drivers/scsi/qedi/Kconfig"
1114 source "drivers/scsi/qedf/Kconfig"
1117 tristate "Emulex LightPulse Fibre Channel Support"
1118 depends on PCI && SCSI
1119 depends on SCSI_FC_ATTRS
1120 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1121 depends on NVME_FC || NVME_FC=n
1124 This lpfc driver supports the Emulex LightPulse
1125 Family of Fibre Channel PCI host adapters.
1127 config SCSI_LPFC_DEBUG_FS
1128 bool "Emulex LightPulse Fibre Channel debugfs Support"
1129 depends on SCSI_LPFC && DEBUG_FS
1131 This makes debugging information from the lpfc driver
1132 available via the debugfs filesystem.
1135 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1136 depends on (EISA || MCA) && SCSI
1137 select SCSI_SPI_ATTRS
1139 This driver is for NCR53c710 based SCSI host adapters.
1141 It currently supports Compaq EISA cards and NCR MCA cards
1144 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1145 depends on PCI && SCSI
1147 This driver supports PCI SCSI host adapters based on the ASIC
1148 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1150 This driver works, but is still in experimental status. So better
1151 have a bootable disk and a backup in case of emergency.
1153 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1155 To compile this driver as a module, choose M here: the
1156 module will be called dc395x.
1158 config SCSI_AM53C974
1159 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1160 depends on PCI && SCSI
1161 select SCSI_SPI_ATTRS
1163 This driver supports PCI SCSI host adapters based on the Am53C974A
1164 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1165 PCscsi/PCnet (Am53/79C974) solutions.
1166 This is a new implementation base on the generic esp_scsi driver.
1168 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1170 Note that this driver does NOT support Tekram DC390W/U/F, which are
1171 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1173 To compile this driver as a module, choose M here: the
1174 module will be called am53c974.
1177 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1178 depends on PCI && SCSI && !64BIT
1180 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1181 SCSI host adapter. Please read the SCSI-HOWTO, available from
1182 <http://www.tldp.org/docs.html#howto>.
1184 To compile this driver as a module, choose M here: the
1185 module will be called nsp32.
1188 tristate "Western Digital WD7193/7197/7296 support"
1189 depends on PCI && SCSI
1192 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1193 SCSI controllers (based on WD33C296A chip).
1196 tristate "SCSI debugging host and device simulator"
1200 This pseudo driver simulates one or more hosts (SCSI initiators),
1201 each with one or more targets, each with one or more logical units.
1202 Defaults to one of each, creating a small RAM disk device. Many
1203 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1204 directory can be tweaked at run time.
1205 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1206 Mainly used for testing and best as a module. If unsure, say N.
1209 tristate "MESH (Power Mac internal SCSI) support"
1210 depends on PPC32 && PPC_PMAC && SCSI
1212 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1213 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1214 other Power Macintoshes do). Say Y to include support for this SCSI
1217 To compile this driver as a module, choose M here: the
1218 module will be called mesh.
1220 config SCSI_MESH_SYNC_RATE
1221 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1222 depends on SCSI_MESH
1225 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1226 drives a bus which is entirely internal to the machine (such as the
1227 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1228 operation at up to 10 MB/s. On machines where the SCSI bus
1229 controlled by the MESH can have external devices connected, it is
1230 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1231 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1232 to disable synchronous operation.
1234 config SCSI_MESH_RESET_DELAY_MS
1235 int "initial bus reset delay (ms) (0 = no reset)"
1236 depends on SCSI_MESH
1239 config SCSI_MAC53C94
1240 tristate "53C94 (Power Mac external SCSI) support"
1241 depends on PPC32 && PPC_PMAC && SCSI
1243 On Power Macintoshes (and clones) with two SCSI buses, the external
1244 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1245 machines which only have one SCSI bus, such as the 7200, also use
1246 the 53C94. Say Y to include support for the 53C94.
1248 To compile this driver as a module, choose M here: the
1249 module will be called mac53c94.
1251 source "drivers/scsi/arm/Kconfig"
1254 bool "MIPS JAZZ FAS216 SCSI support"
1255 depends on MACH_JAZZ && SCSI
1256 select SCSI_SPI_ATTRS
1258 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1259 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1263 tristate "A3000 WD33C93A support"
1264 depends on AMIGA && SCSI
1266 If you have an Amiga 3000 and have SCSI devices connected to the
1267 built-in SCSI controller, say Y. Otherwise, say N.
1269 To compile this driver as a module, choose M here: the
1270 module will be called a3000.
1273 tristate "A2091/A590 WD33C93A support"
1274 depends on ZORRO && SCSI
1276 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1279 To compile this driver as a module, choose M here: the
1280 module will be called a2091.
1283 tristate "GVP Series II WD33C93A support"
1284 depends on ZORRO && SCSI
1286 If you have a Great Valley Products Series II SCSI controller,
1287 answer Y. Also say Y if you have a later model of GVP SCSI
1288 controller (such as the GVP A4008 or a Combo board). Otherwise,
1289 answer N. This driver does NOT work for the T-Rex series of
1290 accelerators from TekMagic and GVP-M.
1292 To compile this driver as a module, choose M here: the
1293 module will be called gvp11.
1296 tristate "A4000T NCR53c710 SCSI support"
1297 depends on AMIGA && SCSI
1298 select SCSI_SPI_ATTRS
1300 If you have an Amiga 4000T and have SCSI devices connected to the
1301 built-in SCSI controller, say Y. Otherwise, say N.
1303 To compile this driver as a module, choose M here: the
1304 module will be called a4000t.
1306 config SCSI_ZORRO7XX
1307 tristate "Zorro NCR53c710 SCSI support"
1308 depends on ZORRO && SCSI
1309 select SCSI_SPI_ATTRS
1311 Support for various NCR53c710-based SCSI controllers on Zorro
1312 expansion boards for the Amiga.
1314 - the Amiga 4091 Zorro III SCSI-2 controller,
1315 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1317 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1318 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1319 accelerator card for the Amiga 1200,
1320 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1322 config SCSI_ZORRO_ESP
1323 tristate "Zorro ESP SCSI support"
1324 depends on ZORRO && SCSI
1325 select SCSI_SPI_ATTRS
1327 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1328 expansion boards for the Amiga.
1330 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1331 - the Phase5 Blizzard 2060 SCSI controller,
1332 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1334 - the Fastlane Zorro III SCSI controller.
1337 tristate "Atari native SCSI support"
1338 depends on ATARI && SCSI
1339 select SCSI_SPI_ATTRS
1342 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1343 Falcon, ...) say Y to get it supported. Of course also, if you have
1344 a compatible SCSI controller (e.g. for Medusa).
1346 To compile this driver as a module, choose M here: the
1347 module will be called atari_scsi.
1349 This driver supports both styles of NCR integration into the
1350 system: the TT style (separate DMA), and the Falcon style (via
1351 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1352 in the Hades (without DMA).
1355 tristate "Macintosh NCR5380 SCSI"
1356 depends on MAC && SCSI
1357 select SCSI_SPI_ATTRS
1359 This is the NCR 5380 SCSI controller included on most of the 68030
1360 based Macintoshes. If you have one of these say Y and read the
1361 SCSI-HOWTO, available from
1362 <http://www.tldp.org/docs.html#howto>.
1365 tristate "Macintosh NCR53c9[46] SCSI"
1366 depends on MAC && SCSI
1367 select SCSI_SPI_ATTRS
1369 This is the NCR 53c9x SCSI controller found on most of the 68040
1372 To compile this driver as a module, choose M here: the module
1373 will be called mac_esp.
1376 bool "WD33C93 SCSI driver for MVME147"
1377 depends on MVME147 && SCSI=y
1378 select SCSI_SPI_ATTRS
1380 Support for the on-board SCSI controller on the Motorola MVME147
1381 single-board computer.
1384 tristate "NCR53C710 SCSI driver for MVME16x"
1385 depends on MVME16x && SCSI
1386 select SCSI_SPI_ATTRS
1388 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1389 SCSI controller chip. Almost everyone using one of these boards
1390 will want to say Y to this question.
1392 config BVME6000_SCSI
1393 tristate "NCR53C710 SCSI driver for BVME6000"
1394 depends on BVME6000 && SCSI
1395 select SCSI_SPI_ATTRS
1397 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1398 SCSI controller chip. Almost everyone using one of these boards
1399 will want to say Y to this question.
1402 tristate "Sun3 NCR5380 SCSI"
1403 depends on SUN3 && SCSI
1404 select SCSI_SPI_ATTRS
1406 This option will enable support for the OBIO (onboard io) NCR5380
1407 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1408 "Sun3" type VME scsi controllers also based on the NCR5380.
1409 General Linux information on the Sun 3 series (now discontinued)
1410 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1413 bool "Sun3x ESP SCSI"
1414 depends on SUN3X && SCSI=y
1415 select SCSI_SPI_ATTRS
1417 The ESP was an on-board SCSI controller used on Sun 3/80
1418 machines. Say Y here to compile in support for it.
1421 tristate "Sparc ESP Scsi Driver"
1422 depends on SBUS && SCSI
1423 select SCSI_SPI_ATTRS
1425 This is the driver for the Sun ESP SCSI host adapter. The ESP
1426 chipset is present in most SPARC SBUS-based computers and
1427 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1428 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1430 To compile this driver as a module, choose M here: the
1431 module will be called sun_esp.
1434 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1435 depends on S390 && QDIO && SCSI
1436 depends on SCSI_FC_ATTRS
1438 If you want to access SCSI devices attached to your IBM eServer
1439 zSeries by means of Fibre Channel interfaces say Y.
1440 For details please refer to the documentation provided by IBM at
1441 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1443 This driver is also available as a module. This module will be
1444 called zfcp. If you want to compile it as a module, say M here
1445 and read <file:Documentation/kbuild/modules.txt>.
1448 tristate "PMC SIERRA Linux MaxRAID adapter support"
1449 depends on PCI && SCSI && NET
1452 This driver supports the PMC SIERRA MaxRAID adapters.
1455 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1456 depends on PCI && SCSI
1457 select SCSI_SAS_LIBSAS
1459 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1460 based host adapters.
1463 tristate "Brocade BFA Fibre Channel Support"
1464 depends on PCI && SCSI
1465 depends on SCSI_FC_ATTRS
1467 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1469 To compile this driver as a module, choose M here. The module will
1473 tristate "virtio-scsi support"
1476 This is the virtual HBA driver for virtio. If the kernel will
1477 be used in a virtual machine, say Y or M.
1479 source "drivers/scsi/csiostor/Kconfig"
1481 endif # SCSI_LOWLEVEL
1483 source "drivers/scsi/pcmcia/Kconfig"
1485 source "drivers/scsi/device_handler/Kconfig"
1487 source "drivers/scsi/osd/Kconfig"