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.
54 bool "legacy /proc/scsi/ support"
55 depends on SCSI && PROC_FS
58 This option enables support for the various files in
59 /proc/scsi. In Linux 2.6 this has been superseded by
60 files in sysfs but many legacy applications rely on this.
64 comment "SCSI support type (disk, tape, CD-ROM)"
68 tristate "SCSI disk support"
71 If you want to use SCSI hard disks, Fibre Channel disks,
72 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
73 USB storage or the SCSI or parallel port version of
74 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
75 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
76 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
79 To compile this driver as a module, choose M here and read
80 <file:Documentation/scsi/scsi.txt>.
81 The module will be called sd_mod.
83 Do not compile this driver as a module if your root file system
84 (the one containing the directory /) is located on a SCSI disk.
85 In this case, do not compile the driver for your SCSI host adapter
86 (below) as a module either.
89 tristate "SCSI tape support"
92 If you want to use a SCSI tape drive under Linux, say Y and read the
93 SCSI-HOWTO, available from
94 <http://www.tldp.org/docs.html#howto>, and
95 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
98 To compile this driver as a module, choose M here and read
99 <file:Documentation/scsi/scsi.txt>. The module will be called st.
102 tristate "SCSI CDROM support"
103 depends on SCSI && BLK_DEV
106 If you want to use a CD or DVD drive attached to your computer
107 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
108 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
110 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
112 To compile this driver as a module, choose M here and read
113 <file:Documentation/scsi/scsi.txt>.
114 The module will be called sr_mod.
116 config BLK_DEV_SR_VENDOR
117 bool "Enable vendor-specific extensions (for SCSI CDROM)"
118 depends on BLK_DEV_SR
120 This enables the usage of vendor specific SCSI commands. This is
121 required to support multisession CDs with old NEC/TOSHIBA cdrom
122 drives (and HP Writers). If you have such a drive and get the first
123 session only, try saying Y here; everybody else says N.
126 tristate "SCSI generic support"
129 If you want to use SCSI scanners, synthesizers or CD-writers or just
130 about anything having "SCSI" in its name other than hard disks,
131 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
132 directly, so you need some additional software which knows how to
133 talk to these devices using the SCSI protocol:
135 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
136 writer software look at Cdrtools
137 (<http://cdrecord.berlios.de/private/cdrecord.html>)
138 and for burning a "disk at once": CDRDAO
139 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
140 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
141 For other devices, it's possible that you'll have to write the
142 driver software yourself. Please read the file
143 <file:Documentation/scsi/scsi-generic.txt> for more information.
145 To compile this driver as a module, choose M here and read
146 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
151 tristate "SCSI media changer support"
154 This is a driver for SCSI media changers. Most common devices are
155 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
156 don't need this for those tiny 6-slot cdrom changers. Media
157 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
158 If you have such hardware and want to use it with linux, say Y
159 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
161 If you want to compile this as a module ( = code which can be
162 inserted in and removed from the running kernel whenever you want),
163 say M here and read <file:Documentation/kbuild/modules.txt> and
164 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
167 config SCSI_ENCLOSURE
168 tristate "SCSI Enclosure Support"
169 depends on SCSI && ENCLOSURE_SERVICES
170 depends on m || SCSI_SAS_ATTRS != m
172 Enclosures are devices sitting on or in SCSI backplanes that
173 manage devices. If you have a disk cage, the chances are that
174 it has an enclosure device. Selecting this option will just allow
175 certain enclosure conditions to be reported and is not required.
177 config SCSI_CONSTANTS
178 bool "Verbose SCSI error reporting (kernel size += 36K)"
181 The error messages regarding your SCSI hardware will be easier to
182 understand if you say Y here; it will enlarge your kernel by about
183 36 KB. If in doubt, say Y.
186 bool "SCSI logging facility"
189 This turns on a logging facility that can be used to debug a number
190 of SCSI related problems.
192 If you say Y here, no logging output will appear by default, but you
193 can enable logging by saying Y to "/proc file system support" and
194 "Sysctl support" below and executing the command
196 echo <bitmask> > /proc/sys/dev/scsi/logging_level
198 where <bitmask> is a four byte value representing the logging type
199 and logging level for each type of logging selected.
201 There are a number of logging types and you can find them in the
202 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
203 are also described in that file and they determine the verbosity of
204 the logging for each logging type.
206 If you say N here, it may be harder to track down some types of SCSI
207 problems. If you say Y here your kernel will be somewhat larger, but
208 there should be no noticeable performance impact as long as you have
211 config SCSI_SCAN_ASYNC
212 bool "Asynchronous SCSI scanning"
215 The SCSI subsystem can probe for devices while the rest of the
216 system continues booting, and even probe devices on different
217 busses in parallel, leading to a significant speed-up.
219 You can override this choice by specifying "scsi_mod.scan=sync"
220 or async on the kernel's command line.
222 Note that this setting also affects whether resuming from
223 system suspend will be performed asynchronously.
225 menu "SCSI Transports"
228 config SCSI_SPI_ATTRS
229 tristate "Parallel SCSI (SPI) Transport Attributes"
232 If you wish to export transport-specific information about
233 each attached SCSI device to sysfs, say Y. Otherwise, say N.
236 tristate "FiberChannel Transport Attributes"
237 depends on SCSI && NET
238 select BLK_DEV_BSGLIB
241 If you wish to export transport-specific information about
242 each attached FiberChannel device to sysfs, say Y.
245 config SCSI_ISCSI_ATTRS
246 tristate "iSCSI Transport Attributes"
247 depends on SCSI && NET
248 select BLK_DEV_BSGLIB
250 If you wish to export transport-specific information about
251 each attached iSCSI device to sysfs, say Y.
254 config SCSI_SAS_ATTRS
255 tristate "SAS Transport Attributes"
257 select BLK_DEV_BSGLIB
259 If you wish to export transport-specific information about
260 each attached SAS device to sysfs, say Y.
262 source "drivers/scsi/libsas/Kconfig"
264 config SCSI_SRP_ATTRS
265 tristate "SRP Transport Attributes"
268 If you wish to export transport-specific information about
269 each attached SRP device to sysfs, say Y.
273 menuconfig SCSI_LOWLEVEL
274 bool "SCSI low-level drivers"
278 if SCSI_LOWLEVEL && SCSI
281 tristate "iSCSI Initiator over TCP/IP"
282 depends on SCSI && INET
286 select SCSI_ISCSI_ATTRS
288 The iSCSI Driver provides a host with the ability to access storage
289 through an IP network. The driver uses the iSCSI protocol to transport
290 SCSI requests and responses over a TCP/IP network between the host
291 (the "initiator") and "targets". Architecturally, the iSCSI driver
292 combines with the host's TCP/IP stack, network drivers, and Network
293 Interface Card (NIC) to provide the same functions as a SCSI or a
294 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
296 To compile this driver as a module, choose M here: the
297 module will be called iscsi_tcp.
299 The userspace component needed to initialize the driver, documentation,
300 and sample configuration files can be found here:
302 http://open-iscsi.org
304 config ISCSI_BOOT_SYSFS
305 tristate "iSCSI Boot Sysfs Interface"
308 This option enables support for exposing iSCSI boot information
309 via sysfs to userspace. If you wish to export this information,
310 say Y. Otherwise, say N.
312 source "drivers/scsi/cxgbi/Kconfig"
313 source "drivers/scsi/bnx2i/Kconfig"
314 source "drivers/scsi/bnx2fc/Kconfig"
315 source "drivers/scsi/be2iscsi/Kconfig"
316 source "drivers/scsi/cxlflash/Kconfig"
319 tristate "SGI WD93C93 SCSI Driver"
320 depends on SGI_HAS_WD93 && SCSI
322 If you have a Western Digital WD93 SCSI controller on
323 an SGI MIPS system, say Y. Otherwise, say N.
325 config BLK_DEV_3W_XXXX_RAID
326 tristate "3ware 5/6/7/8xxx ATA-RAID support"
327 depends on PCI && SCSI
329 3ware is the only hardware ATA-Raid product in Linux to date.
330 This card is 2,4, or 8 channel master mode support only.
331 SCSI support required!!!
333 <http://www.3ware.com/>
335 Please read the comments at the top of
336 <file:drivers/scsi/3w-xxxx.c>.
339 tristate "HP Smart Array SCSI driver"
340 depends on PCI && SCSI
341 select CHECK_SIGNATURE
342 select SCSI_SAS_ATTRS
344 This driver supports HP Smart Array Controllers (circa 2009).
345 It is a SCSI alternative to the cciss driver, which is a block
346 driver. Anyone wishing to use HP Smart Array controllers who
347 would prefer the devices be presented to linux as SCSI devices,
348 rather than as generic block devices should say Y here.
351 tristate "3ware 9xxx SATA-RAID support"
352 depends on PCI && SCSI
354 This driver supports the 9000 series 3ware SATA-RAID cards.
356 <http://www.amcc.com>
358 Please read the comments at the top of
359 <file:drivers/scsi/3w-9xxx.c>.
362 tristate "3ware 97xx SAS/SATA-RAID support"
363 depends on PCI && SCSI
365 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
369 Please read the comments at the top of
370 <file:drivers/scsi/3w-sas.c>.
373 tristate "ACARD SCSI support"
374 depends on PCI && SCSI
376 This driver supports the ACARD SCSI host adapter.
377 Support Chip <ATP870 ATP876 ATP880 ATP885>
378 To compile this driver as a module, choose M here: the
379 module will be called atp870u.
382 tristate "Adaptec AHA152X/2825 support"
383 depends on ISA && SCSI
384 select SCSI_SPI_ATTRS
385 select CHECK_SIGNATURE
387 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
388 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
389 must be manually specified in this case.
391 It is explained in section 3.3 of the SCSI-HOWTO, available from
392 <http://www.tldp.org/docs.html#howto>. You might also want to
393 read the file <file:Documentation/scsi/aha152x.txt>.
395 To compile this driver as a module, choose M here: the
396 module will be called aha152x.
399 tristate "Adaptec AHA1542 support"
400 depends on ISA && SCSI && ISA_DMA_API
402 This is support for a SCSI host adapter. It is explained in section
403 3.4 of the SCSI-HOWTO, available from
404 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
405 purchased by Adaptec, and some former Trantor products are being
406 sold under the Adaptec name. If it doesn't work out of the box, you
407 may have to change some settings in <file:drivers/scsi/aha1542.h>.
409 To compile this driver as a module, choose M here: the
410 module will be called aha1542.
413 tristate "Adaptec AHA1740 support"
414 depends on EISA && SCSI
416 This is support for a SCSI host adapter. It is explained in section
417 3.5 of the SCSI-HOWTO, available from
418 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
419 of the box, you may have to change some settings in
420 <file:drivers/scsi/aha1740.h>.
422 To compile this driver as a module, choose M here: the
423 module will be called aha1740.
426 tristate "Adaptec AACRAID support"
427 depends on SCSI && PCI
429 This driver supports a variety of Dell, HP, Adaptec, IBM and
430 ICP storage products. For a list of supported products, refer
431 to <file:Documentation/scsi/aacraid.txt>.
433 To compile this driver as a module, choose M here: the module
434 will be called aacraid.
437 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
438 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
439 source "drivers/scsi/aic94xx/Kconfig"
440 source "drivers/scsi/hisi_sas/Kconfig"
441 source "drivers/scsi/mvsas/Kconfig"
444 tristate "Marvell UMI driver"
445 depends on SCSI && PCI
447 Module for Marvell Universal Message Interface(UMI) driver
449 To compile this driver as a module, choose M here: the
450 module will be called mvumi.
453 tristate "Adaptec I2O RAID support "
454 depends on SCSI && PCI && VIRT_TO_BUS
456 This driver supports all of Adaptec's I2O based RAID controllers as
457 well as the DPT SmartRaid V cards. This is an Adaptec maintained
458 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
460 To compile this driver as a module, choose M here: the
461 module will be called dpt_i2o.
464 tristate "AdvanSys SCSI support"
466 depends on ISA || EISA || PCI
467 depends on ISA_DMA_API || !ISA
469 This is a driver for all SCSI host adapters manufactured by
470 AdvanSys. It is documented in the kernel source in
471 <file:drivers/scsi/advansys.c>.
473 To compile this driver as a module, choose M here: the
474 module will be called advansys.
477 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
478 depends on PCI && SCSI
480 This driver supports all of ARECA's SATA/SAS RAID controller cards.
481 This is an ARECA-maintained driver by Erich Chen.
482 If you have any problems, please mail to: <erich@areca.com.tw>.
483 Areca supports Linux RAID config tools.
484 Please link <http://www.areca.com.tw>
486 To compile this driver as a module, choose M here: the
487 module will be called arcmsr (modprobe arcmsr).
489 source "drivers/scsi/esas2r/Kconfig"
490 source "drivers/scsi/megaraid/Kconfig.megaraid"
491 source "drivers/scsi/mpt3sas/Kconfig"
492 source "drivers/scsi/smartpqi/Kconfig"
493 source "drivers/scsi/ufs/Kconfig"
496 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
497 depends on SCSI && PCI
499 This option enables support for HighPoint RocketRAID 3xxx/4xxx
502 To compile this driver as a module, choose M here; the module
503 will be called hptiop. If unsure, say N.
506 tristate "BusLogic SCSI support"
507 depends on (PCI || ISA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
509 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
510 Adapters. Consult the SCSI-HOWTO, available from
511 <http://www.tldp.org/docs.html#howto>, and the files
512 <file:Documentation/scsi/BusLogic.txt> and
513 <file:Documentation/scsi/FlashPoint.txt> for more information.
514 Note that support for FlashPoint is only available for 32-bit
517 To compile this driver as a module, choose M here: the
518 module will be called BusLogic.
520 config SCSI_FLASHPOINT
521 bool "FlashPoint support"
522 depends on SCSI_BUSLOGIC && PCI
524 This option allows you to add FlashPoint support to the
525 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
526 substantial, so users of MultiMaster Host Adapters may not
530 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
534 This driver adds support for the Mylex DAC960, AcceleRAID, and
535 eXtremeRAID PCI RAID controllers. This driver supports the
536 older, block based interface.
537 This driver is a reimplementation of the original DAC960
538 driver. If you have used the DAC960 driver you should enable
541 To compile this driver as a module, choose M here: the
542 module will be called myrb.
545 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
547 depends on !CPU_BIG_ENDIAN || COMPILE_TEST
550 This driver adds support for the Mylex DAC960, AcceleRAID, and
551 eXtremeRAID PCI RAID controllers. This driver supports the
552 newer, SCSI-based interface only.
553 This driver is a reimplementation of the original DAC960
554 driver. If you have used the DAC960 driver you should enable
557 To compile this driver as a module, choose M here: the
558 module will be called myrs.
561 tristate "VMware PVSCSI driver support"
562 depends on PCI && SCSI && X86
564 This driver supports VMware's para virtualized SCSI HBA.
565 To compile this driver as a module, choose M here: the
566 module will be called vmw_pvscsi.
568 config XEN_SCSI_FRONTEND
569 tristate "XEN SCSI frontend driver"
570 depends on SCSI && XEN
571 select XEN_XENBUS_FRONTEND
573 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
574 within another guest OS (usually Dom0).
575 Only needed if the kernel is running in a XEN guest and generic
576 SCSI access to a device is needed.
578 config HYPERV_STORAGE
579 tristate "Microsoft Hyper-V virtual storage driver"
580 depends on SCSI && HYPERV
581 depends on m || SCSI_FC_ATTRS != m
584 Select this option to enable the Hyper-V virtual storage driver.
587 tristate "LibFC module"
588 depends on SCSI_FC_ATTRS
591 Fibre Channel library module
594 tristate "LibFCoE module"
597 Library for Fibre Channel over Ethernet module
600 tristate "FCoE module"
604 Fibre Channel over Ethernet module
607 tristate "Cisco FNIC Driver"
608 depends on PCI && X86
611 This is support for the Cisco PCI-Express FCoE HBA.
613 To compile this driver as a module, choose M here and read
614 <file:Documentation/scsi/scsi.txt>.
615 The module will be called fnic.
618 tristate "Cisco SNIC Driver"
619 depends on PCI && SCSI
621 This is support for the Cisco PCI-Express SCSI HBA.
623 To compile this driver as a module, choose M here and read
624 <file:Documentation/scsi/scsi.txt>.
625 The module will be called snic.
627 config SCSI_SNIC_DEBUG_FS
628 bool "Cisco SNIC Driver Debugfs Support"
629 depends on SCSI_SNIC && DEBUG_FS
631 This enables to list debugging information from SNIC Driver
632 available via debugfs file system
635 tristate "DMX3191D SCSI support"
636 depends on PCI && SCSI
637 select SCSI_SPI_ATTRS
639 This is support for Domex DMX3191D SCSI Host Adapters.
641 To compile this driver as a module, choose M here: the
642 module will be called dmx3191d.
648 config SCSI_FDOMAIN_PCI
649 tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
650 depends on PCI && SCSI
653 This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
654 and other adapters with PCI bus based on the Future Domain chipsets
657 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
658 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
659 controller support"). This Future Domain driver works with the older
660 Adaptec AHA-2920A boards with a Future Domain chip on them.
662 To compile this driver as a module, choose M here: the
663 module will be called fdomain_pci.
665 config SCSI_FDOMAIN_ISA
666 tristate "Future Domain 16xx ISA SCSI support"
667 depends on ISA && SCSI
668 select CHECK_SIGNATURE
671 This is support for Future Domain's 16-bit SCSI host adapters
672 (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
673 with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
674 ISA-250MG; and at least one IBM board).
676 To compile this driver as a module, choose M here: the
677 module will be called fdomain_isa.
680 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
681 depends on PCI && SCSI
683 Formerly called GDT SCSI Disk Array Controller Support.
685 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
686 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
687 in the kernel source in <file:drivers/scsi/gdth.c> and
688 <file:drivers/scsi/gdth.h>.
690 To compile this driver as a module, choose M here: the
691 module will be called gdth.
694 tristate "Intel(R) C600 Series Chipset SAS Controller"
695 depends on PCI && SCSI
697 select SCSI_SAS_LIBSAS
699 This driver supports the 6Gb/s SAS capabilities of the storage
700 control unit found in the Intel(R) C600 series chipset.
702 config SCSI_GENERIC_NCR5380
703 tristate "Generic NCR5380/53c400 SCSI ISA card support"
704 depends on ISA && SCSI && HAS_IOPORT_MAP
705 select SCSI_SPI_ATTRS
707 This is a driver for old ISA card SCSI controllers based on a
708 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
709 Most boards such as the Trantor T130 fit this category, as do
710 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
712 To compile this driver as a module, choose M here: the
713 module will be called g_NCR5380.
716 tristate "IBM ServeRAID support"
717 depends on PCI && SCSI
719 This is support for the IBM ServeRAID hardware RAID controllers.
720 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
721 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
722 for more information. If this driver does not work correctly
723 without modification please contact the author by email at
724 <ipslinux@adaptec.com>.
726 To compile this driver as a module, choose M here: the
727 module will be called ips.
730 tristate "IBM Virtual SCSI support"
731 depends on PPC_PSERIES
732 select SCSI_SRP_ATTRS
734 This is the IBM POWER Virtual SCSI Client
736 To compile this driver as a module, choose M here: the
737 module will be called ibmvscsi.
739 config SCSI_IBMVSCSIS
740 tristate "IBM Virtual SCSI Server support"
741 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
743 This is the IBM POWER Virtual SCSI Target Server
744 This driver uses the SRP protocol for communication between servers
745 guest and/or the host that run on the same server.
746 More information on VSCSI protocol can be found at www.power.org
748 The userspace configuration needed to initialize the driver can be
751 https://github.com/powervm/ibmvscsis/wiki/Configuration
753 To compile this driver as a module, choose M here: the
754 module will be called ibmvscsis.
757 tristate "IBM Virtual FC support"
758 depends on PPC_PSERIES && SCSI
759 depends on SCSI_FC_ATTRS
761 This is the IBM POWER Virtual FC Client
763 To compile this driver as a module, choose M here: the
764 module will be called ibmvfc.
766 config SCSI_IBMVFC_TRACE
767 bool "enable driver internal trace"
768 depends on SCSI_IBMVFC
771 If you say Y here, the driver will trace all commands issued
772 to the adapter. Performance impact is minimal. Trace can be
773 dumped using /sys/class/scsi_host/hostXX/trace.
776 tristate "Initio 9100U(W) support"
777 depends on PCI && SCSI
779 This is support for the Initio 91XXU(W) SCSI host adapter. Please
780 read the SCSI-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 To compile this driver as a module, choose M here: the
784 module will be called initio.
787 tristate "Initio INI-A100U2W support"
788 depends on PCI && SCSI
790 This is support for the Initio INI-A100U2W SCSI host adapter.
791 Please read the SCSI-HOWTO, available from
792 <http://www.tldp.org/docs.html#howto>.
794 To compile this driver as a module, choose M here: the
795 module will be called a100u2w.
798 tristate "IOMEGA parallel port (ppa - older drives)"
799 depends on SCSI && PARPORT_PC
801 This driver supports older versions of IOMEGA's parallel port ZIP
802 drive (a 100 MB removable media device).
804 Note that you can say N here if you have the SCSI version of the ZIP
805 drive: it will be supported automatically if you said Y to the
806 generic "SCSI disk support", above.
808 If you have the ZIP Plus drive or a more recent parallel port ZIP
809 drive (if the supplied cable with the drive is labeled "AutoDetect")
810 then you should say N here and Y to "IOMEGA parallel port (imm -
811 newer drives)", below.
813 For more information about this driver and how to use it you should
814 read the file <file:Documentation/scsi/ppa.txt>. You should also read
815 the SCSI-HOWTO, which is available from
816 <http://www.tldp.org/docs.html#howto>. If you use this driver,
817 you will still be able to use the parallel port for other tasks,
818 such as a printer; it is safe to compile both drivers into the
821 To compile this driver as a module, choose M here: the
822 module will be called ppa.
825 tristate "IOMEGA parallel port (imm - newer drives)"
826 depends on SCSI && PARPORT_PC
828 This driver supports newer versions of IOMEGA's parallel port ZIP
829 drive (a 100 MB removable media device).
831 Note that you can say N here if you have the SCSI version of the ZIP
832 drive: it will be supported automatically if you said Y to the
833 generic "SCSI disk support", above.
835 If you have the ZIP Plus drive or a more recent parallel port ZIP
836 drive (if the supplied cable with the drive is labeled "AutoDetect")
837 then you should say Y here; if you have an older ZIP drive, say N
838 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
840 For more information about this driver and how to use it you should
841 read the file <file:Documentation/scsi/ppa.txt>. You should also read
842 the SCSI-HOWTO, which is available from
843 <http://www.tldp.org/docs.html#howto>. If you use this driver,
844 you will still be able to use the parallel port for other tasks,
845 such as a printer; it is safe to compile both drivers into the
848 To compile this driver as a module, choose M here: the
849 module will be called imm.
851 config SCSI_IZIP_EPP16
852 bool "ppa/imm option - Use slow (but safe) EPP-16"
853 depends on SCSI_PPA || SCSI_IMM
855 EPP (Enhanced Parallel Port) is a standard for parallel ports which
856 allows them to act as expansion buses that can handle up to 64
859 Some parallel port chipsets are slower than their motherboard, and
860 so we have to control the state of the chipset's FIFO queue every
861 now and then to avoid data loss. This will be done if you say Y
864 Generally, saying Y is the safe option and slows things down a bit.
866 config SCSI_IZIP_SLOW_CTR
867 bool "ppa/imm option - Assume slow parport control register"
868 depends on SCSI_PPA || SCSI_IMM
870 Some parallel ports are known to have excessive delays between
871 changing the parallel port control register and good data being
872 available on the parallel port data/status register. This option
873 forces a small delay (1.0 usec to be exact) after changing the
874 control register to let things settle out. Enabling this option may
875 result in a big drop in performance but some very old parallel ports
876 (found in 386 vintage machines) will not work properly.
878 Generally, saying N is fine.
881 tristate "HP Lasi SCSI support for 53c700/710"
882 depends on GSC && SCSI
883 select SCSI_SPI_ATTRS
885 This is a driver for the SCSI controller in the Lasi chip found in
886 many PA-RISC workstations & servers. If you do not know whether you
887 have a Lasi chip, it is safe to say "Y" here.
889 config SCSI_SNI_53C710
890 tristate "SNI RM SCSI support for 53c710"
891 depends on SNI_RM && SCSI
892 select SCSI_SPI_ATTRS
893 select 53C700_LE_ON_BE
895 This is a driver for the onboard SCSI controller found in older
896 SNI RM workstations & servers.
898 config 53C700_LE_ON_BE
900 depends on SCSI_LASI700
904 tristate "Promise SuperTrak EX Series support"
905 depends on PCI && SCSI
907 This driver supports Promise SuperTrak EX series storage controllers.
909 Promise provides Linux RAID configuration utility for these
910 controllers. Please visit <http://www.promise.com> to download.
912 To compile this driver as a module, choose M here: the
913 module will be called stex.
917 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
920 config SCSI_SYM53C8XX_2
921 tristate "SYM53C8XX Version 2 SCSI support"
922 depends on PCI && SCSI
923 select SCSI_SPI_ATTRS
925 This driver supports the whole NCR53C8XX/SYM53C8XX family of
926 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
927 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
928 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
929 controllers; you need to use the Fusion MPT driver for that.
931 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
934 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
935 int "DMA addressing mode"
936 depends on SCSI_SYM53C8XX_2
939 This option only applies to PCI-SCSI chips that are PCI DAC
940 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
942 When set to 0, the driver will program the chip to only perform
943 32-bit DMA. When set to 1, the chip will be able to perform DMA
944 to addresses up to 1TB. When set to 2, the driver supports the
945 full 64-bit DMA address range, but can only address 16 segments
946 of 4 GB each. This limits the total addressable range to 64 GB.
948 Most machines with less than 4GB of memory should use a setting
949 of 0 for best performance. If your machine has 4GB of memory
950 or more, you should set this option to 1 (the default).
952 The still experimental value 2 (64 bit DMA addressing with 16
953 x 4GB segments limitation) can be used on systems that require
954 PCI address bits past bit 39 to be set for the addressing of
955 memory using PCI DAC cycles.
957 config SCSI_SYM53C8XX_DEFAULT_TAGS
958 int "Default tagged command queue depth"
959 depends on SCSI_SYM53C8XX_2
962 This is the default value of the command queue depth the
963 driver will announce to the generic SCSI layer for devices
964 that support tagged command queueing. This value can be changed
965 from the boot command line. This is a soft limit that cannot
966 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
968 config SCSI_SYM53C8XX_MAX_TAGS
969 int "Maximum number of queued commands"
970 depends on SCSI_SYM53C8XX_2
973 This option allows you to specify the maximum number of commands
974 that can be queued to any device, when tagged command queuing is
975 possible. The driver supports up to 256 queued commands per device.
976 This value is used as a compiled-in hard limit.
978 config SCSI_SYM53C8XX_MMIO
979 bool "Use memory mapped IO"
980 depends on SCSI_SYM53C8XX_2
983 Memory mapped IO is faster than Port IO. Most people should
984 answer Y here, but some machines may have problems. If you have
985 to answer N here, please report the problem to the maintainer.
988 tristate "IBM Power Linux RAID adapter support"
989 depends on PCI && SCSI && ATA
994 This driver supports the IBM Power Linux family RAID adapters.
995 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
996 as IBM iSeries 5702, 5703, 5709, and 570A.
998 config SCSI_IPR_TRACE
999 bool "enable driver internal trace"
1003 If you say Y here, the driver will trace all commands issued
1004 to the adapter. Performance impact is minimal. Trace can be
1005 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1007 config SCSI_IPR_DUMP
1008 bool "enable adapter dump support"
1012 If you say Y here, the driver will support adapter crash dump.
1013 If you enable this support, the iprdump daemon can be used
1014 to capture adapter failure analysis information.
1017 tristate "Zalon SCSI support"
1018 depends on GSC && SCSI
1019 select SCSI_SPI_ATTRS
1021 The Zalon is a GSC/HSC bus interface chip that sits between the
1022 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1023 C110, J200, J210 and some D, K & R-class machines. It's also
1024 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1025 Say Y here if you have one of these machines or cards.
1027 config SCSI_NCR53C8XX_DEFAULT_TAGS
1028 int "default tagged command queue depth"
1029 depends on SCSI_ZALON
1032 "Tagged command queuing" is a feature of SCSI-2 which improves
1033 performance: the host adapter can send several SCSI commands to a
1034 device's queue even if previous commands haven't finished yet.
1035 Because the device is intelligent, it can optimize its operations
1036 (like head positioning) based on its own request queue. Some SCSI
1037 devices don't implement this properly; if you want to disable this
1038 feature, enter 0 or 1 here (it doesn't matter which).
1040 The default value is 8 and should be supported by most hard disks.
1041 This value can be overridden from the boot command line using the
1042 'tags' option as follows (example):
1043 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1044 4, set queue depth to 16 for target 2 and target 3 on controller 0
1045 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1047 The normal answer therefore is to go with the default 8 and to use
1048 a boot command line option for devices that need to use a different
1049 command queue depth.
1051 There is no safe option other than using good SCSI devices.
1053 config SCSI_NCR53C8XX_MAX_TAGS
1054 int "maximum number of queued commands"
1055 depends on SCSI_ZALON
1058 This option allows you to specify the maximum number of commands
1059 that can be queued to any device, when tagged command queuing is
1060 possible. The default value is 32. Minimum is 2, maximum is 64.
1061 Modern hard disks are able to support 64 tags and even more, but
1062 do not seem to be faster when more than 32 tags are being used.
1064 So, the normal answer here is to go with the default value 32 unless
1065 you are using very large hard disks with large cache (>= 1 MB) that
1066 are able to take advantage of more than 32 tagged commands.
1068 There is no safe option and the default answer is recommended.
1070 config SCSI_NCR53C8XX_SYNC
1071 int "synchronous transfers frequency in MHz"
1072 depends on SCSI_ZALON
1075 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1076 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1077 are respectively the maximum data transfer rates in mega-transfers
1078 per second for each class. For example, a FAST-20 Wide 16 device is
1079 able to transfer data at 20 million 16 bit packets per second for a
1080 total rate of 40 MB/s.
1082 You may specify 0 if you want to only use asynchronous data
1083 transfers. This is the safest and slowest option. Otherwise, specify
1084 a value between 5 and 80, depending on the capability of your SCSI
1085 controller. The higher the number, the faster the data transfer.
1086 Note that 80 should normally be ok since the driver decreases the
1087 value automatically according to the controller's capabilities.
1089 Your answer to this question is ignored for controllers with NVRAM,
1090 since the driver will get this information from the user set-up. It
1091 also can be overridden using a boot setup option, as follows
1092 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1093 for FAST-20 synchronous data transfer (20 mega-transfers per
1096 The normal answer therefore is not to go with the default but to
1097 select the maximum value 80 allowing the driver to use the maximum
1098 value supported by each controller. If this causes problems with
1099 your SCSI devices, you should come back and decrease the value.
1101 There is no safe option other than using good cabling, right
1102 terminations and SCSI conformant devices.
1104 config SCSI_NCR53C8XX_NO_DISCONNECT
1105 bool "not allow targets to disconnect"
1106 depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1108 This option is only provided for safety if you suspect some SCSI
1109 device of yours to not support properly the target-disconnect
1110 feature. In that case, you would say Y here. In general however, to
1111 not allow targets to disconnect is not reasonable if there is more
1112 than 1 device on a SCSI bus. The normal answer therefore is N.
1114 config SCSI_QLOGIC_FAS
1115 tristate "Qlogic FAS SCSI support"
1116 depends on ISA && SCSI
1118 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1119 FastSCSI! cards as well as any other card based on the FASXX chip
1120 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1122 This driver does NOT support the PCI versions of these cards. The
1123 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1124 SCSI support"), below.
1126 Information about this driver is contained in
1127 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1128 SCSI-HOWTO, available from
1129 <http://www.tldp.org/docs.html#howto>.
1131 To compile this driver as a module, choose M here: the
1132 module will be called qlogicfas.
1134 config SCSI_QLOGIC_1280
1135 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1136 depends on PCI && SCSI
1138 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1140 To compile this driver as a module, choose M here: the
1141 module will be called qla1280.
1143 config SCSI_QLOGICPTI
1144 tristate "PTI Qlogic, ISP Driver"
1145 depends on SBUS && SCSI
1147 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1148 controllers are known under Solaris as qpti and in the openprom as
1149 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1150 driven by a different driver.
1152 To compile this driver as a module, choose M here: the
1153 module will be called qlogicpti.
1155 source "drivers/scsi/qla2xxx/Kconfig"
1156 source "drivers/scsi/qla4xxx/Kconfig"
1157 source "drivers/scsi/qedi/Kconfig"
1158 source "drivers/scsi/qedf/Kconfig"
1161 tristate "Emulex LightPulse Fibre Channel Support"
1162 depends on PCI && SCSI
1163 depends on SCSI_FC_ATTRS
1164 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1165 depends on NVME_FC || NVME_FC=n
1168 This lpfc driver supports the Emulex LightPulse
1169 Family of Fibre Channel PCI host adapters.
1171 config SCSI_LPFC_DEBUG_FS
1172 bool "Emulex LightPulse Fibre Channel debugfs Support"
1173 depends on SCSI_LPFC && DEBUG_FS
1175 This makes debugging information from the lpfc driver
1176 available via the debugfs filesystem.
1179 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1180 depends on EISA && SCSI
1181 select SCSI_SPI_ATTRS
1183 This driver is for NCR53c710 based SCSI host adapters.
1185 It currently supports Compaq EISA cards.
1188 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1189 depends on PCI && SCSI
1191 This driver supports PCI SCSI host adapters based on the ASIC
1192 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1194 This driver works, but is still in experimental status. So better
1195 have a bootable disk and a backup in case of emergency.
1197 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1199 To compile this driver as a module, choose M here: the
1200 module will be called dc395x.
1202 config SCSI_AM53C974
1203 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1204 depends on PCI && SCSI
1205 select SCSI_SPI_ATTRS
1207 This driver supports PCI SCSI host adapters based on the Am53C974A
1208 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1209 PCscsi/PCnet (Am53/79C974) solutions.
1210 This is a new implementation base on the generic esp_scsi driver.
1212 Note that this driver does NOT support Tekram DC390W/U/F, which are
1213 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1215 To compile this driver as a module, choose M here: the
1216 module will be called am53c974.
1219 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1220 depends on PCI && SCSI && !64BIT
1222 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1223 SCSI host adapter. Please read the SCSI-HOWTO, available from
1224 <http://www.tldp.org/docs.html#howto>.
1226 To compile this driver as a module, choose M here: the
1227 module will be called nsp32.
1230 tristate "Western Digital WD7193/7197/7296 support"
1231 depends on PCI && SCSI
1234 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1235 SCSI controllers (based on WD33C296A chip).
1238 tristate "SCSI debugging host and device simulator"
1242 This pseudo driver simulates one or more hosts (SCSI initiators),
1243 each with one or more targets, each with one or more logical units.
1244 Defaults to one of each, creating a small RAM disk device. Many
1245 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1246 directory can be tweaked at run time.
1247 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1248 Mainly used for testing and best as a module. If unsure, say N.
1251 tristate "MESH (Power Mac internal SCSI) support"
1252 depends on PPC32 && PPC_PMAC && SCSI
1254 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1255 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1256 other Power Macintoshes do). Say Y to include support for this SCSI
1259 To compile this driver as a module, choose M here: the
1260 module will be called mesh.
1262 config SCSI_MESH_SYNC_RATE
1263 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1264 depends on SCSI_MESH
1267 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1268 drives a bus which is entirely internal to the machine (such as the
1269 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1270 operation at up to 10 MB/s. On machines where the SCSI bus
1271 controlled by the MESH can have external devices connected, it is
1272 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1273 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1274 to disable synchronous operation.
1276 config SCSI_MESH_RESET_DELAY_MS
1277 int "initial bus reset delay (ms) (0 = no reset)"
1278 depends on SCSI_MESH
1281 config SCSI_MAC53C94
1282 tristate "53C94 (Power Mac external SCSI) support"
1283 depends on PPC32 && PPC_PMAC && SCSI
1285 On Power Macintoshes (and clones) with two SCSI buses, the external
1286 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1287 machines which only have one SCSI bus, such as the 7200, also use
1288 the 53C94. Say Y to include support for the 53C94.
1290 To compile this driver as a module, choose M here: the
1291 module will be called mac53c94.
1293 source "drivers/scsi/arm/Kconfig"
1296 bool "MIPS JAZZ FAS216 SCSI support"
1297 depends on MACH_JAZZ && SCSI
1298 select SCSI_SPI_ATTRS
1300 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1301 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1305 tristate "A3000 WD33C93A support"
1306 depends on AMIGA && SCSI
1308 If you have an Amiga 3000 and have SCSI devices connected to the
1309 built-in SCSI controller, say Y. Otherwise, say N.
1311 To compile this driver as a module, choose M here: the
1312 module will be called a3000.
1315 tristate "A2091/A590 WD33C93A support"
1316 depends on ZORRO && SCSI
1318 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1321 To compile this driver as a module, choose M here: the
1322 module will be called a2091.
1325 tristate "GVP Series II WD33C93A support"
1326 depends on ZORRO && SCSI
1328 If you have a Great Valley Products Series II SCSI controller,
1329 answer Y. Also say Y if you have a later model of GVP SCSI
1330 controller (such as the GVP A4008 or a Combo board). Otherwise,
1331 answer N. This driver does NOT work for the T-Rex series of
1332 accelerators from TekMagic and GVP-M.
1334 To compile this driver as a module, choose M here: the
1335 module will be called gvp11.
1338 tristate "A4000T NCR53c710 SCSI support"
1339 depends on AMIGA && SCSI
1340 select SCSI_SPI_ATTRS
1342 If you have an Amiga 4000T and have SCSI devices connected to the
1343 built-in SCSI controller, say Y. Otherwise, say N.
1345 To compile this driver as a module, choose M here: the
1346 module will be called a4000t.
1348 config SCSI_ZORRO7XX
1349 tristate "Zorro NCR53c710 SCSI support"
1350 depends on ZORRO && SCSI
1351 select SCSI_SPI_ATTRS
1353 Support for various NCR53c710-based SCSI controllers on Zorro
1354 expansion boards for the Amiga.
1356 - the Amiga 4091 Zorro III SCSI-2 controller,
1357 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1359 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1360 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1361 accelerator card for the Amiga 1200,
1362 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1364 config SCSI_ZORRO_ESP
1365 tristate "Zorro ESP SCSI support"
1366 depends on ZORRO && SCSI
1367 select SCSI_SPI_ATTRS
1370 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1371 expansion boards for the Amiga.
1373 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1374 - the Phase5 Blizzard 2060 SCSI controller,
1375 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1377 - the Fastlane Zorro III SCSI controller.
1380 tristate "Atari native SCSI support"
1381 depends on ATARI && SCSI
1382 select SCSI_SPI_ATTRS
1384 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1385 Falcon, ...) say Y to get it supported. Of course also, if you have
1386 a compatible SCSI controller (e.g. for Medusa).
1388 To compile this driver as a module, choose M here: the module will
1389 be called atari_scsi. If you also enable NVRAM support, the SCSI
1390 host's ID is taken from the setting in TT RTC NVRAM.
1392 This driver supports both styles of NCR integration into the
1393 system: the TT style (separate DMA), and the Falcon style (via
1394 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1395 in the Hades (without DMA).
1398 tristate "Macintosh NCR5380 SCSI"
1399 depends on MAC && SCSI
1400 select SCSI_SPI_ATTRS
1402 This is the NCR 5380 SCSI controller included on most of the 68030
1403 based Macintoshes. If you have one of these say Y and read the
1404 SCSI-HOWTO, available from
1405 <http://www.tldp.org/docs.html#howto>.
1408 tristate "Macintosh NCR53c9[46] SCSI"
1409 depends on MAC && SCSI
1410 select SCSI_SPI_ATTRS
1413 This is the NCR 53c9x SCSI controller found on most of the 68040
1416 To compile this driver as a module, choose M here: the module
1417 will be called mac_esp.
1420 bool "WD33C93 SCSI driver for MVME147"
1421 depends on MVME147 && SCSI=y
1422 select SCSI_SPI_ATTRS
1424 Support for the on-board SCSI controller on the Motorola MVME147
1425 single-board computer.
1428 tristate "NCR53C710 SCSI driver for MVME16x"
1429 depends on MVME16x && SCSI
1430 select SCSI_SPI_ATTRS
1432 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1433 SCSI controller chip. Almost everyone using one of these boards
1434 will want to say Y to this question.
1436 config BVME6000_SCSI
1437 tristate "NCR53C710 SCSI driver for BVME6000"
1438 depends on BVME6000 && SCSI
1439 select SCSI_SPI_ATTRS
1441 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1442 SCSI controller chip. Almost everyone using one of these boards
1443 will want to say Y to this question.
1446 tristate "Sun3 NCR5380 SCSI"
1447 depends on SUN3 && SCSI
1448 select SCSI_SPI_ATTRS
1450 This option will enable support for the OBIO (onboard io) NCR5380
1451 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1452 "Sun3" type VME scsi controllers also based on the NCR5380.
1453 General Linux information on the Sun 3 series (now discontinued)
1454 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1457 bool "Sun3x ESP SCSI"
1458 depends on SUN3X && SCSI=y
1459 select SCSI_SPI_ATTRS
1461 The ESP was an on-board SCSI controller used on Sun 3/80
1462 machines. Say Y here to compile in support for it.
1465 tristate "Sparc ESP Scsi Driver"
1466 depends on SBUS && SCSI
1467 select SCSI_SPI_ATTRS
1469 This is the driver for the Sun ESP SCSI host adapter. The ESP
1470 chipset is present in most SPARC SBUS-based computers and
1471 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1472 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1474 To compile this driver as a module, choose M here: the
1475 module will be called sun_esp.
1478 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1479 depends on S390 && QDIO && SCSI
1480 depends on SCSI_FC_ATTRS
1482 If you want to access SCSI devices attached to your IBM eServer
1483 zSeries by means of Fibre Channel interfaces say Y.
1484 For details please refer to the documentation provided by IBM at
1485 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1487 This driver is also available as a module. This module will be
1488 called zfcp. If you want to compile it as a module, say M here
1489 and read <file:Documentation/kbuild/modules.txt>.
1492 tristate "PMC SIERRA Linux MaxRAID adapter support"
1493 depends on PCI && SCSI && NET
1496 This driver supports the PMC SIERRA MaxRAID adapters.
1499 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1500 depends on PCI && SCSI
1501 select SCSI_SAS_LIBSAS
1503 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1504 based host adapters.
1507 tristate "Brocade BFA Fibre Channel Support"
1508 depends on PCI && SCSI
1509 depends on SCSI_FC_ATTRS
1511 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1513 To compile this driver as a module, choose M here. The module will
1517 tristate "virtio-scsi support"
1520 This is the virtual HBA driver for virtio. If the kernel will
1521 be used in a virtual machine, say Y or M.
1523 source "drivers/scsi/csiostor/Kconfig"
1525 endif # SCSI_LOWLEVEL
1527 source "drivers/scsi/pcmcia/Kconfig"
1529 source "drivers/scsi/device_handler/Kconfig"