1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "SCSI device support"
6 default y if SCSI=n || SCSI=y
10 tristate "RAID Transport Class"
18 tristate "SCSI device support"
20 select SCSI_DMA if HAS_DMA
22 select BLK_SCSI_REQUEST
24 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
25 any other SCSI device under Linux, say Y and make sure that you know
26 the name of your SCSI host adapter (the card inside your computer
27 that "speaks" the SCSI protocol, also called SCSI controller),
28 because you will be asked for it.
30 You also need to say Y here if you have a device which speaks
31 the SCSI protocol. Examples of this include the parallel port
32 version of the IOMEGA ZIP drive, USB storage devices, Fibre
33 Channel, and FireWire storage.
35 To compile this driver as a module, choose M here and read
36 <file:Documentation/scsi/scsi.txt>.
37 The module will be called scsi_mod.
39 However, do not compile this as a module if your root file system
40 (the one containing the directory /) is located on a SCSI device.
55 bool "legacy /proc/scsi/ support"
56 depends on SCSI && PROC_FS
59 This option enables support for the various files in
60 /proc/scsi. In Linux 2.6 this has been superseded by
61 files in sysfs but many legacy applications rely on this.
65 comment "SCSI support type (disk, tape, CD-ROM)"
69 tristate "SCSI disk support"
72 If you want to use SCSI hard disks, Fibre Channel disks,
73 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
74 USB storage or the SCSI or parallel port version of
75 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
76 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
77 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
80 To compile this driver as a module, choose M here and read
81 <file:Documentation/scsi/scsi.txt>.
82 The module will be called sd_mod.
84 Do not compile this driver as a module if your root file system
85 (the one containing the directory /) is located on a SCSI disk.
86 In this case, do not compile the driver for your SCSI host adapter
87 (below) as a module either.
90 tristate "SCSI tape support"
93 If you want to use a SCSI tape drive under Linux, say Y and read the
94 SCSI-HOWTO, available from
95 <http://www.tldp.org/docs.html#howto>, and
96 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
99 To compile this driver as a module, choose M here and read
100 <file:Documentation/scsi/scsi.txt>. The module will be called st.
103 tristate "SCSI CDROM support"
104 depends on SCSI && BLK_DEV
107 If you want to use a CD or DVD drive attached to your computer
108 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
109 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
111 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
113 To compile this driver as a module, choose M here and read
114 <file:Documentation/scsi/scsi.txt>.
115 The module will be called sr_mod.
118 tristate "SCSI generic support"
121 If you want to use SCSI scanners, synthesizers or CD-writers or just
122 about anything having "SCSI" in its name other than hard disks,
123 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
124 directly, so you need some additional software which knows how to
125 talk to these devices using the SCSI protocol:
127 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
128 writer software look at Cdrtools
129 (<http://cdrecord.berlios.de/private/cdrecord.html>)
130 and for burning a "disk at once": CDRDAO
131 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
132 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
133 For other devices, it's possible that you'll have to write the
134 driver software yourself. Please read the file
135 <file:Documentation/scsi/scsi-generic.txt> for more information.
137 To compile this driver as a module, choose M here and read
138 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
143 tristate "SCSI media changer support"
146 This is a driver for SCSI media changers. Most common devices are
147 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
148 don't need this for those tiny 6-slot cdrom changers. Media
149 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
150 If you have such hardware and want to use it with linux, say Y
151 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
153 If you want to compile this as a module ( = code which can be
154 inserted in and removed from the running kernel whenever you want),
155 say M here and read <file:Documentation/kbuild/modules.rst> and
156 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
159 config SCSI_ENCLOSURE
160 tristate "SCSI Enclosure Support"
161 depends on SCSI && ENCLOSURE_SERVICES
162 depends on m || SCSI_SAS_ATTRS != m
164 Enclosures are devices sitting on or in SCSI backplanes that
165 manage devices. If you have a disk cage, the chances are that
166 it has an enclosure device. Selecting this option will just allow
167 certain enclosure conditions to be reported and is not required.
169 config SCSI_CONSTANTS
170 bool "Verbose SCSI error reporting (kernel size += 36K)"
173 The error messages regarding your SCSI hardware will be easier to
174 understand if you say Y here; it will enlarge your kernel by about
175 36 KB. If in doubt, say Y.
178 bool "SCSI logging facility"
181 This turns on a logging facility that can be used to debug a number
182 of SCSI related problems.
184 If you say Y here, no logging output will appear by default, but you
185 can enable logging by saying Y to "/proc file system support" and
186 "Sysctl support" below and executing the command
188 echo <bitmask> > /proc/sys/dev/scsi/logging_level
190 where <bitmask> is a four byte value representing the logging type
191 and logging level for each type of logging selected.
193 There are a number of logging types and you can find them in the
194 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
195 are also described in that file and they determine the verbosity of
196 the logging for each logging type.
198 If you say N here, it may be harder to track down some types of SCSI
199 problems. If you say Y here your kernel will be somewhat larger, but
200 there should be no noticeable performance impact as long as you have
203 config SCSI_SCAN_ASYNC
204 bool "Asynchronous SCSI scanning"
207 The SCSI subsystem can probe for devices while the rest of the
208 system continues booting, and even probe devices on different
209 busses in parallel, leading to a significant speed-up.
211 You can override this choice by specifying "scsi_mod.scan=sync"
212 or async on the kernel's command line.
214 Note that this setting also affects whether resuming from
215 system suspend will be performed asynchronously.
217 menu "SCSI Transports"
220 config SCSI_SPI_ATTRS
221 tristate "Parallel SCSI (SPI) Transport Attributes"
224 If you wish to export transport-specific information about
225 each attached SCSI device to sysfs, say Y. Otherwise, say N.
228 tristate "FiberChannel Transport Attributes"
229 depends on SCSI && NET
230 select BLK_DEV_BSGLIB
233 If you wish to export transport-specific information about
234 each attached FiberChannel device to sysfs, say Y.
237 config SCSI_ISCSI_ATTRS
238 tristate "iSCSI Transport Attributes"
239 depends on SCSI && NET
240 select BLK_DEV_BSGLIB
242 If you wish to export transport-specific information about
243 each attached iSCSI device to sysfs, say Y.
246 config SCSI_SAS_ATTRS
247 tristate "SAS Transport Attributes"
249 select BLK_DEV_BSGLIB
251 If you wish to export transport-specific information about
252 each attached SAS device to sysfs, say Y.
254 source "drivers/scsi/libsas/Kconfig"
256 config SCSI_SRP_ATTRS
257 tristate "SRP Transport Attributes"
260 If you wish to export transport-specific information about
261 each attached SRP device to sysfs, say Y.
265 menuconfig SCSI_LOWLEVEL
266 bool "SCSI low-level drivers"
270 if SCSI_LOWLEVEL && SCSI
273 tristate "iSCSI Initiator over TCP/IP"
274 depends on SCSI && INET
278 select SCSI_ISCSI_ATTRS
280 The iSCSI Driver provides a host with the ability to access storage
281 through an IP network. The driver uses the iSCSI protocol to transport
282 SCSI requests and responses over a TCP/IP network between the host
283 (the "initiator") and "targets". Architecturally, the iSCSI driver
284 combines with the host's TCP/IP stack, network drivers, and Network
285 Interface Card (NIC) to provide the same functions as a SCSI or a
286 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
288 To compile this driver as a module, choose M here: the
289 module will be called iscsi_tcp.
291 The userspace component needed to initialize the driver, documentation,
292 and sample configuration files can be found here:
294 http://open-iscsi.org
296 config ISCSI_BOOT_SYSFS
297 tristate "iSCSI Boot Sysfs Interface"
300 This option enables support for exposing iSCSI boot information
301 via sysfs to userspace. If you wish to export this information,
302 say Y. Otherwise, say N.
304 source "drivers/scsi/cxgbi/Kconfig"
305 source "drivers/scsi/bnx2i/Kconfig"
306 source "drivers/scsi/bnx2fc/Kconfig"
307 source "drivers/scsi/be2iscsi/Kconfig"
308 source "drivers/scsi/cxlflash/Kconfig"
311 tristate "SGI WD93C93 SCSI Driver"
312 depends on SGI_HAS_WD93 && SCSI
314 If you have a Western Digital WD93 SCSI controller on
315 an SGI MIPS system, say Y. Otherwise, say N.
317 config BLK_DEV_3W_XXXX_RAID
318 tristate "3ware 5/6/7/8xxx ATA-RAID support"
319 depends on PCI && SCSI
321 3ware is the only hardware ATA-Raid product in Linux to date.
322 This card is 2,4, or 8 channel master mode support only.
323 SCSI support required!!!
325 <http://www.3ware.com/>
327 Please read the comments at the top of
328 <file:drivers/scsi/3w-xxxx.c>.
331 tristate "HP Smart Array SCSI driver"
332 depends on PCI && SCSI
333 select CHECK_SIGNATURE
334 select SCSI_SAS_ATTRS
336 This driver supports HP Smart Array Controllers (circa 2009).
337 It is a SCSI alternative to the cciss driver, which is a block
338 driver. Anyone wishing to use HP Smart Array controllers who
339 would prefer the devices be presented to linux as SCSI devices,
340 rather than as generic block devices should say Y here.
343 tristate "3ware 9xxx SATA-RAID support"
344 depends on PCI && SCSI
346 This driver supports the 9000 series 3ware SATA-RAID cards.
348 <http://www.amcc.com>
350 Please read the comments at the top of
351 <file:drivers/scsi/3w-9xxx.c>.
354 tristate "3ware 97xx SAS/SATA-RAID support"
355 depends on PCI && SCSI
357 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
361 Please read the comments at the top of
362 <file:drivers/scsi/3w-sas.c>.
365 tristate "ACARD SCSI support"
366 depends on PCI && SCSI
368 This driver supports the ACARD SCSI host adapter.
369 Support Chip <ATP870 ATP876 ATP880 ATP885>
370 To compile this driver as a module, choose M here: the
371 module will be called atp870u.
374 tristate "Adaptec AHA152X/2825 support"
375 depends on ISA && SCSI
376 select SCSI_SPI_ATTRS
377 select CHECK_SIGNATURE
379 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
380 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
381 must be manually specified in this case.
383 It is explained in section 3.3 of the SCSI-HOWTO, available from
384 <http://www.tldp.org/docs.html#howto>. You might also want to
385 read the file <file:Documentation/scsi/aha152x.txt>.
387 To compile this driver as a module, choose M here: the
388 module will be called aha152x.
391 tristate "Adaptec AHA1542 support"
392 depends on ISA && SCSI && ISA_DMA_API
394 This is support for a SCSI host adapter. It is explained in section
395 3.4 of the SCSI-HOWTO, available from
396 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
397 purchased by Adaptec, and some former Trantor products are being
398 sold under the Adaptec name. If it doesn't work out of the box, you
399 may have to change some settings in <file:drivers/scsi/aha1542.h>.
401 To compile this driver as a module, choose M here: the
402 module will be called aha1542.
405 tristate "Adaptec AHA1740 support"
406 depends on EISA && SCSI
408 This is support for a SCSI host adapter. It is explained in section
409 3.5 of the SCSI-HOWTO, available from
410 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
411 of the box, you may have to change some settings in
412 <file:drivers/scsi/aha1740.h>.
414 To compile this driver as a module, choose M here: the
415 module will be called aha1740.
418 tristate "Adaptec AACRAID support"
419 depends on SCSI && PCI
421 This driver supports a variety of Dell, HP, Adaptec, IBM and
422 ICP storage products. For a list of supported products, refer
423 to <file:Documentation/scsi/aacraid.txt>.
425 To compile this driver as a module, choose M here: the module
426 will be called aacraid.
429 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
430 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
431 source "drivers/scsi/aic94xx/Kconfig"
432 source "drivers/scsi/hisi_sas/Kconfig"
433 source "drivers/scsi/mvsas/Kconfig"
436 tristate "Marvell UMI driver"
437 depends on SCSI && PCI
439 Module for Marvell Universal Message Interface(UMI) driver
441 To compile this driver as a module, choose M here: the
442 module will be called mvumi.
445 tristate "Adaptec I2O RAID support "
446 depends on SCSI && PCI && VIRT_TO_BUS
448 This driver supports all of Adaptec's I2O based RAID controllers as
449 well as the DPT SmartRaid V cards. This is an Adaptec maintained
450 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
452 To compile this driver as a module, choose M here: the
453 module will be called dpt_i2o.
456 tristate "AdvanSys SCSI support"
458 depends on ISA || EISA || PCI
459 depends on ISA_DMA_API || !ISA
461 This is a driver for all SCSI host adapters manufactured by
462 AdvanSys. It is documented in the kernel source in
463 <file:drivers/scsi/advansys.c>.
465 To compile this driver as a module, choose M here: the
466 module will be called advansys.
469 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
470 depends on PCI && SCSI
472 This driver supports all of ARECA's SATA/SAS RAID controller cards.
473 This is an ARECA-maintained driver by Erich Chen.
474 If you have any problems, please mail to: <erich@areca.com.tw>.
475 Areca supports Linux RAID config tools.
476 Please link <http://www.areca.com.tw>
478 To compile this driver as a module, choose M here: the
479 module will be called arcmsr (modprobe arcmsr).
481 source "drivers/scsi/esas2r/Kconfig"
482 source "drivers/scsi/megaraid/Kconfig.megaraid"
483 source "drivers/scsi/mpt3sas/Kconfig"
484 source "drivers/scsi/smartpqi/Kconfig"
485 source "drivers/scsi/ufs/Kconfig"
488 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
489 depends on SCSI && PCI
491 This option enables support for HighPoint RocketRAID 3xxx/4xxx
494 To compile this driver as a module, choose M here; the module
495 will be called hptiop. If unsure, say N.
498 tristate "BusLogic SCSI support"
499 depends on (PCI || ISA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
501 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
502 Adapters. Consult the SCSI-HOWTO, available from
503 <http://www.tldp.org/docs.html#howto>, and the files
504 <file:Documentation/scsi/BusLogic.txt> and
505 <file:Documentation/scsi/FlashPoint.txt> for more information.
506 Note that support for FlashPoint is only available for 32-bit
509 To compile this driver as a module, choose M here: the
510 module will be called BusLogic.
512 config SCSI_FLASHPOINT
513 bool "FlashPoint support"
514 depends on SCSI_BUSLOGIC && PCI
516 This option allows you to add FlashPoint support to the
517 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
518 substantial, so users of MultiMaster Host Adapters may not
522 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
526 This driver adds support for the Mylex DAC960, AcceleRAID, and
527 eXtremeRAID PCI RAID controllers. This driver supports the
528 older, block based interface.
529 This driver is a reimplementation of the original DAC960
530 driver. If you have used the DAC960 driver you should enable
533 To compile this driver as a module, choose M here: the
534 module will be called myrb.
537 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
539 depends on !CPU_BIG_ENDIAN || COMPILE_TEST
542 This driver adds support for the Mylex DAC960, AcceleRAID, and
543 eXtremeRAID PCI RAID controllers. This driver supports the
544 newer, SCSI-based interface only.
545 This driver is a reimplementation of the original DAC960
546 driver. If you have used the DAC960 driver you should enable
549 To compile this driver as a module, choose M here: the
550 module will be called myrs.
553 tristate "VMware PVSCSI driver support"
554 depends on PCI && SCSI && X86
556 This driver supports VMware's para virtualized SCSI HBA.
557 To compile this driver as a module, choose M here: the
558 module will be called vmw_pvscsi.
560 config XEN_SCSI_FRONTEND
561 tristate "XEN SCSI frontend driver"
562 depends on SCSI && XEN
563 select XEN_XENBUS_FRONTEND
565 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
566 within another guest OS (usually Dom0).
567 Only needed if the kernel is running in a XEN guest and generic
568 SCSI access to a device is needed.
570 config HYPERV_STORAGE
571 tristate "Microsoft Hyper-V virtual storage driver"
572 depends on SCSI && HYPERV
573 depends on m || SCSI_FC_ATTRS != m
576 Select this option to enable the Hyper-V virtual storage driver.
579 tristate "LibFC module"
580 depends on SCSI_FC_ATTRS
583 Fibre Channel library module
586 tristate "LibFCoE module"
589 Library for Fibre Channel over Ethernet module
592 tristate "FCoE module"
596 Fibre Channel over Ethernet module
599 tristate "Cisco FNIC Driver"
600 depends on PCI && X86
603 This is support for the Cisco PCI-Express FCoE HBA.
605 To compile this driver as a module, choose M here and read
606 <file:Documentation/scsi/scsi.txt>.
607 The module will be called fnic.
610 tristate "Cisco SNIC Driver"
611 depends on PCI && SCSI
613 This is support for the Cisco PCI-Express SCSI HBA.
615 To compile this driver as a module, choose M here and read
616 <file:Documentation/scsi/scsi.txt>.
617 The module will be called snic.
619 config SCSI_SNIC_DEBUG_FS
620 bool "Cisco SNIC Driver Debugfs Support"
621 depends on SCSI_SNIC && DEBUG_FS
623 This enables to list debugging information from SNIC Driver
624 available via debugfs file system
627 tristate "DMX3191D SCSI support"
628 depends on PCI && SCSI
629 select SCSI_SPI_ATTRS
631 This is support for Domex DMX3191D SCSI Host Adapters.
633 To compile this driver as a module, choose M here: the
634 module will be called dmx3191d.
640 config SCSI_FDOMAIN_PCI
641 tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
642 depends on PCI && SCSI
645 This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
646 and other adapters with PCI bus based on the Future Domain chipsets
649 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
650 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
651 controller support"). This Future Domain driver works with the older
652 Adaptec AHA-2920A boards with a Future Domain chip on them.
654 To compile this driver as a module, choose M here: the
655 module will be called fdomain_pci.
657 config SCSI_FDOMAIN_ISA
658 tristate "Future Domain 16xx ISA SCSI support"
659 depends on ISA && SCSI
660 select CHECK_SIGNATURE
663 This is support for Future Domain's 16-bit SCSI host adapters
664 (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
665 with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
666 ISA-250MG; and at least one IBM board).
668 To compile this driver as a module, choose M here: the
669 module will be called fdomain_isa.
672 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
673 depends on PCI && SCSI
675 Formerly called GDT SCSI Disk Array Controller Support.
677 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
678 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
679 in the kernel source in <file:drivers/scsi/gdth.c> and
680 <file:drivers/scsi/gdth.h>.
682 To compile this driver as a module, choose M here: the
683 module will be called gdth.
686 tristate "Intel(R) C600 Series Chipset SAS Controller"
687 depends on PCI && SCSI
689 select SCSI_SAS_LIBSAS
691 This driver supports the 6Gb/s SAS capabilities of the storage
692 control unit found in the Intel(R) C600 series chipset.
694 config SCSI_GENERIC_NCR5380
695 tristate "Generic NCR5380/53c400 SCSI ISA card support"
696 depends on ISA && SCSI && HAS_IOPORT_MAP
697 select SCSI_SPI_ATTRS
699 This is a driver for old ISA card SCSI controllers based on a
700 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
701 Most boards such as the Trantor T130 fit this category, as do
702 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
704 To compile this driver as a module, choose M here: the
705 module will be called g_NCR5380.
708 tristate "IBM ServeRAID support"
709 depends on PCI && SCSI
711 This is support for the IBM ServeRAID hardware RAID controllers.
712 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
713 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
714 for more information. If this driver does not work correctly
715 without modification please contact the author by email at
716 <ipslinux@adaptec.com>.
718 To compile this driver as a module, choose M here: the
719 module will be called ips.
722 tristate "IBM Virtual SCSI support"
723 depends on PPC_PSERIES
724 select SCSI_SRP_ATTRS
726 This is the IBM POWER Virtual SCSI Client
728 To compile this driver as a module, choose M here: the
729 module will be called ibmvscsi.
731 config SCSI_IBMVSCSIS
732 tristate "IBM Virtual SCSI Server support"
733 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
735 This is the IBM POWER Virtual SCSI Target Server
736 This driver uses the SRP protocol for communication between servers
737 guest and/or the host that run on the same server.
738 More information on VSCSI protocol can be found at www.power.org
740 The userspace configuration needed to initialize the driver can be
743 https://github.com/powervm/ibmvscsis/wiki/Configuration
745 To compile this driver as a module, choose M here: the
746 module will be called ibmvscsis.
749 tristate "IBM Virtual FC support"
750 depends on PPC_PSERIES && SCSI
751 depends on SCSI_FC_ATTRS
753 This is the IBM POWER Virtual FC Client
755 To compile this driver as a module, choose M here: the
756 module will be called ibmvfc.
758 config SCSI_IBMVFC_TRACE
759 bool "enable driver internal trace"
760 depends on SCSI_IBMVFC
763 If you say Y here, the driver will trace all commands issued
764 to the adapter. Performance impact is minimal. Trace can be
765 dumped using /sys/class/scsi_host/hostXX/trace.
768 tristate "Initio 9100U(W) support"
769 depends on PCI && SCSI
771 This is support for the Initio 91XXU(W) SCSI host adapter. Please
772 read the SCSI-HOWTO, available from
773 <http://www.tldp.org/docs.html#howto>.
775 To compile this driver as a module, choose M here: the
776 module will be called initio.
779 tristate "Initio INI-A100U2W support"
780 depends on PCI && SCSI
782 This is support for the Initio INI-A100U2W SCSI host adapter.
783 Please read the SCSI-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>.
786 To compile this driver as a module, choose M here: the
787 module will be called a100u2w.
790 tristate "IOMEGA parallel port (ppa - older drives)"
791 depends on SCSI && PARPORT_PC
793 This driver supports older versions of IOMEGA's parallel port ZIP
794 drive (a 100 MB removable media device).
796 Note that you can say N here if you have the SCSI version of the ZIP
797 drive: it will be supported automatically if you said Y to the
798 generic "SCSI disk support", above.
800 If you have the ZIP Plus drive or a more recent parallel port ZIP
801 drive (if the supplied cable with the drive is labeled "AutoDetect")
802 then you should say N here and Y to "IOMEGA parallel port (imm -
803 newer drives)", below.
805 For more information about this driver and how to use it you should
806 read the file <file:Documentation/scsi/ppa.txt>. You should also read
807 the SCSI-HOWTO, which is available from
808 <http://www.tldp.org/docs.html#howto>. If you use this driver,
809 you will still be able to use the parallel port for other tasks,
810 such as a printer; it is safe to compile both drivers into the
813 To compile this driver as a module, choose M here: the
814 module will be called ppa.
817 tristate "IOMEGA parallel port (imm - newer drives)"
818 depends on SCSI && PARPORT_PC
820 This driver supports newer versions of IOMEGA's parallel port ZIP
821 drive (a 100 MB removable media device).
823 Note that you can say N here if you have the SCSI version of the ZIP
824 drive: it will be supported automatically if you said Y to the
825 generic "SCSI disk support", above.
827 If you have the ZIP Plus drive or a more recent parallel port ZIP
828 drive (if the supplied cable with the drive is labeled "AutoDetect")
829 then you should say Y here; if you have an older ZIP drive, say N
830 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
832 For more information about this driver and how to use it you should
833 read the file <file:Documentation/scsi/ppa.txt>. You should also read
834 the SCSI-HOWTO, which is available from
835 <http://www.tldp.org/docs.html#howto>. If you use this driver,
836 you will still be able to use the parallel port for other tasks,
837 such as a printer; it is safe to compile both drivers into the
840 To compile this driver as a module, choose M here: the
841 module will be called imm.
843 config SCSI_IZIP_EPP16
844 bool "ppa/imm option - Use slow (but safe) EPP-16"
845 depends on SCSI_PPA || SCSI_IMM
847 EPP (Enhanced Parallel Port) is a standard for parallel ports which
848 allows them to act as expansion buses that can handle up to 64
851 Some parallel port chipsets are slower than their motherboard, and
852 so we have to control the state of the chipset's FIFO queue every
853 now and then to avoid data loss. This will be done if you say Y
856 Generally, saying Y is the safe option and slows things down a bit.
858 config SCSI_IZIP_SLOW_CTR
859 bool "ppa/imm option - Assume slow parport control register"
860 depends on SCSI_PPA || SCSI_IMM
862 Some parallel ports are known to have excessive delays between
863 changing the parallel port control register and good data being
864 available on the parallel port data/status register. This option
865 forces a small delay (1.0 usec to be exact) after changing the
866 control register to let things settle out. Enabling this option may
867 result in a big drop in performance but some very old parallel ports
868 (found in 386 vintage machines) will not work properly.
870 Generally, saying N is fine.
873 tristate "HP Lasi SCSI support for 53c700/710"
874 depends on GSC && SCSI
875 select SCSI_SPI_ATTRS
877 This is a driver for the SCSI controller in the Lasi chip found in
878 many PA-RISC workstations & servers. If you do not know whether you
879 have a Lasi chip, it is safe to say "Y" here.
881 config SCSI_SNI_53C710
882 tristate "SNI RM SCSI support for 53c710"
883 depends on SNI_RM && SCSI
884 select SCSI_SPI_ATTRS
885 select 53C700_LE_ON_BE
887 This is a driver for the onboard SCSI controller found in older
888 SNI RM workstations & servers.
890 config 53C700_LE_ON_BE
892 depends on SCSI_LASI700 || SCSI_SNI_53C710
896 tristate "Promise SuperTrak EX Series support"
897 depends on PCI && SCSI
899 This driver supports Promise SuperTrak EX series storage controllers.
901 Promise provides Linux RAID configuration utility for these
902 controllers. Please visit <http://www.promise.com> to download.
904 To compile this driver as a module, choose M here: the
905 module will be called stex.
909 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
912 config SCSI_SYM53C8XX_2
913 tristate "SYM53C8XX Version 2 SCSI support"
914 depends on PCI && SCSI
915 select SCSI_SPI_ATTRS
917 This driver supports the whole NCR53C8XX/SYM53C8XX family of
918 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
919 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
920 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
921 controllers; you need to use the Fusion MPT driver for that.
923 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
926 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
927 int "DMA addressing mode"
928 depends on SCSI_SYM53C8XX_2
931 This option only applies to PCI-SCSI chips that are PCI DAC
932 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
934 When set to 0, the driver will program the chip to only perform
935 32-bit DMA. When set to 1, the chip will be able to perform DMA
936 to addresses up to 1TB. When set to 2, the driver supports the
937 full 64-bit DMA address range, but can only address 16 segments
938 of 4 GB each. This limits the total addressable range to 64 GB.
940 Most machines with less than 4GB of memory should use a setting
941 of 0 for best performance. If your machine has 4GB of memory
942 or more, you should set this option to 1 (the default).
944 The still experimental value 2 (64 bit DMA addressing with 16
945 x 4GB segments limitation) can be used on systems that require
946 PCI address bits past bit 39 to be set for the addressing of
947 memory using PCI DAC cycles.
949 config SCSI_SYM53C8XX_DEFAULT_TAGS
950 int "Default tagged command queue depth"
951 depends on SCSI_SYM53C8XX_2
954 This is the default value of the command queue depth the
955 driver will announce to the generic SCSI layer for devices
956 that support tagged command queueing. This value can be changed
957 from the boot command line. This is a soft limit that cannot
958 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
960 config SCSI_SYM53C8XX_MAX_TAGS
961 int "Maximum number of queued commands"
962 depends on SCSI_SYM53C8XX_2
965 This option allows you to specify the maximum number of commands
966 that can be queued to any device, when tagged command queuing is
967 possible. The driver supports up to 256 queued commands per device.
968 This value is used as a compiled-in hard limit.
970 config SCSI_SYM53C8XX_MMIO
971 bool "Use memory mapped IO"
972 depends on SCSI_SYM53C8XX_2
975 Memory mapped IO is faster than Port IO. Most people should
976 answer Y here, but some machines may have problems. If you have
977 to answer N here, please report the problem to the maintainer.
980 tristate "IBM Power Linux RAID adapter support"
981 depends on PCI && SCSI && ATA
986 This driver supports the IBM Power Linux family RAID adapters.
987 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
988 as IBM iSeries 5702, 5703, 5709, and 570A.
990 config SCSI_IPR_TRACE
991 bool "enable driver internal trace"
995 If you say Y here, the driver will trace all commands issued
996 to the adapter. Performance impact is minimal. Trace can be
997 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1000 bool "enable adapter dump support"
1004 If you say Y here, the driver will support adapter crash dump.
1005 If you enable this support, the iprdump daemon can be used
1006 to capture adapter failure analysis information.
1009 tristate "Zalon SCSI support"
1010 depends on GSC && SCSI
1011 select SCSI_SPI_ATTRS
1013 The Zalon is a GSC/HSC bus interface chip that sits between the
1014 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1015 C110, J200, J210 and some D, K & R-class machines. It's also
1016 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1017 Say Y here if you have one of these machines or cards.
1019 config SCSI_NCR53C8XX_DEFAULT_TAGS
1020 int "default tagged command queue depth"
1021 depends on SCSI_ZALON
1024 "Tagged command queuing" is a feature of SCSI-2 which improves
1025 performance: the host adapter can send several SCSI commands to a
1026 device's queue even if previous commands haven't finished yet.
1027 Because the device is intelligent, it can optimize its operations
1028 (like head positioning) based on its own request queue. Some SCSI
1029 devices don't implement this properly; if you want to disable this
1030 feature, enter 0 or 1 here (it doesn't matter which).
1032 The default value is 8 and should be supported by most hard disks.
1033 This value can be overridden from the boot command line using the
1034 'tags' option as follows (example):
1035 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1036 4, set queue depth to 16 for target 2 and target 3 on controller 0
1037 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1039 The normal answer therefore is to go with the default 8 and to use
1040 a boot command line option for devices that need to use a different
1041 command queue depth.
1043 There is no safe option other than using good SCSI devices.
1045 config SCSI_NCR53C8XX_MAX_TAGS
1046 int "maximum number of queued commands"
1047 depends on SCSI_ZALON
1050 This option allows you to specify the maximum number of commands
1051 that can be queued to any device, when tagged command queuing is
1052 possible. The default value is 32. Minimum is 2, maximum is 64.
1053 Modern hard disks are able to support 64 tags and even more, but
1054 do not seem to be faster when more than 32 tags are being used.
1056 So, the normal answer here is to go with the default value 32 unless
1057 you are using very large hard disks with large cache (>= 1 MB) that
1058 are able to take advantage of more than 32 tagged commands.
1060 There is no safe option and the default answer is recommended.
1062 config SCSI_NCR53C8XX_SYNC
1063 int "synchronous transfers frequency in MHz"
1064 depends on SCSI_ZALON
1067 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1068 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1069 are respectively the maximum data transfer rates in mega-transfers
1070 per second for each class. For example, a FAST-20 Wide 16 device is
1071 able to transfer data at 20 million 16 bit packets per second for a
1072 total rate of 40 MB/s.
1074 You may specify 0 if you want to only use asynchronous data
1075 transfers. This is the safest and slowest option. Otherwise, specify
1076 a value between 5 and 80, depending on the capability of your SCSI
1077 controller. The higher the number, the faster the data transfer.
1078 Note that 80 should normally be ok since the driver decreases the
1079 value automatically according to the controller's capabilities.
1081 Your answer to this question is ignored for controllers with NVRAM,
1082 since the driver will get this information from the user set-up. It
1083 also can be overridden using a boot setup option, as follows
1084 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1085 for FAST-20 synchronous data transfer (20 mega-transfers per
1088 The normal answer therefore is not to go with the default but to
1089 select the maximum value 80 allowing the driver to use the maximum
1090 value supported by each controller. If this causes problems with
1091 your SCSI devices, you should come back and decrease the value.
1093 There is no safe option other than using good cabling, right
1094 terminations and SCSI conformant devices.
1096 config SCSI_NCR53C8XX_NO_DISCONNECT
1097 bool "not allow targets to disconnect"
1098 depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1100 This option is only provided for safety if you suspect some SCSI
1101 device of yours to not support properly the target-disconnect
1102 feature. In that case, you would say Y here. In general however, to
1103 not allow targets to disconnect is not reasonable if there is more
1104 than 1 device on a SCSI bus. The normal answer therefore is N.
1106 config SCSI_QLOGIC_FAS
1107 tristate "Qlogic FAS SCSI support"
1108 depends on ISA && SCSI
1110 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1111 FastSCSI! cards as well as any other card based on the FASXX chip
1112 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1114 This driver does NOT support the PCI versions of these cards. The
1115 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1116 SCSI support"), below.
1118 Information about this driver is contained in
1119 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1120 SCSI-HOWTO, available from
1121 <http://www.tldp.org/docs.html#howto>.
1123 To compile this driver as a module, choose M here: the
1124 module will be called qlogicfas.
1126 config SCSI_QLOGIC_1280
1127 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1128 depends on PCI && SCSI
1130 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1132 To compile this driver as a module, choose M here: the
1133 module will be called qla1280.
1135 config SCSI_QLOGICPTI
1136 tristate "PTI Qlogic, ISP Driver"
1137 depends on SBUS && SCSI
1139 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1140 controllers are known under Solaris as qpti and in the openprom as
1141 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1142 driven by a different driver.
1144 To compile this driver as a module, choose M here: the
1145 module will be called qlogicpti.
1147 source "drivers/scsi/qla2xxx/Kconfig"
1148 source "drivers/scsi/qla4xxx/Kconfig"
1149 source "drivers/scsi/qedi/Kconfig"
1150 source "drivers/scsi/qedf/Kconfig"
1153 tristate "Emulex LightPulse Fibre Channel Support"
1154 depends on PCI && SCSI
1155 depends on SCSI_FC_ATTRS
1156 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1157 depends on NVME_FC || NVME_FC=n
1160 This lpfc driver supports the Emulex LightPulse
1161 Family of Fibre Channel PCI host adapters.
1163 config SCSI_LPFC_DEBUG_FS
1164 bool "Emulex LightPulse Fibre Channel debugfs Support"
1165 depends on SCSI_LPFC && DEBUG_FS
1167 This makes debugging information from the lpfc driver
1168 available via the debugfs filesystem.
1171 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1172 depends on EISA && SCSI
1173 select SCSI_SPI_ATTRS
1175 This driver is for NCR53c710 based SCSI host adapters.
1177 It currently supports Compaq EISA cards.
1180 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1181 depends on PCI && SCSI
1183 This driver supports PCI SCSI host adapters based on the ASIC
1184 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1186 This driver works, but is still in experimental status. So better
1187 have a bootable disk and a backup in case of emergency.
1189 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1191 To compile this driver as a module, choose M here: the
1192 module will be called dc395x.
1194 config SCSI_AM53C974
1195 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1196 depends on PCI && SCSI
1197 select SCSI_SPI_ATTRS
1199 This driver supports PCI SCSI host adapters based on the Am53C974A
1200 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1201 PCscsi/PCnet (Am53/79C974) solutions.
1202 This is a new implementation base on the generic esp_scsi driver.
1204 Note that this driver does NOT support Tekram DC390W/U/F, which are
1205 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1207 To compile this driver as a module, choose M here: the
1208 module will be called am53c974.
1211 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1212 depends on PCI && SCSI && !64BIT
1214 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1215 SCSI host adapter. Please read the SCSI-HOWTO, available from
1216 <http://www.tldp.org/docs.html#howto>.
1218 To compile this driver as a module, choose M here: the
1219 module will be called nsp32.
1222 tristate "Western Digital WD7193/7197/7296 support"
1223 depends on PCI && SCSI
1226 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1227 SCSI controllers (based on WD33C296A chip).
1230 tristate "SCSI debugging host and device simulator"
1234 This pseudo driver simulates one or more hosts (SCSI initiators),
1235 each with one or more targets, each with one or more logical units.
1236 Defaults to one of each, creating a small RAM disk device. Many
1237 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1238 directory can be tweaked at run time.
1239 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1240 Mainly used for testing and best as a module. If unsure, say N.
1243 tristate "MESH (Power Mac internal SCSI) support"
1244 depends on PPC32 && PPC_PMAC && SCSI
1246 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1247 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1248 other Power Macintoshes do). Say Y to include support for this SCSI
1251 To compile this driver as a module, choose M here: the
1252 module will be called mesh.
1254 config SCSI_MESH_SYNC_RATE
1255 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1256 depends on SCSI_MESH
1259 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1260 drives a bus which is entirely internal to the machine (such as the
1261 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1262 operation at up to 10 MB/s. On machines where the SCSI bus
1263 controlled by the MESH can have external devices connected, it is
1264 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1265 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1266 to disable synchronous operation.
1268 config SCSI_MESH_RESET_DELAY_MS
1269 int "initial bus reset delay (ms) (0 = no reset)"
1270 depends on SCSI_MESH
1273 config SCSI_MAC53C94
1274 tristate "53C94 (Power Mac external SCSI) support"
1275 depends on PPC32 && PPC_PMAC && SCSI
1277 On Power Macintoshes (and clones) with two SCSI buses, the external
1278 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1279 machines which only have one SCSI bus, such as the 7200, also use
1280 the 53C94. Say Y to include support for the 53C94.
1282 To compile this driver as a module, choose M here: the
1283 module will be called mac53c94.
1285 source "drivers/scsi/arm/Kconfig"
1288 bool "MIPS JAZZ FAS216 SCSI support"
1289 depends on MACH_JAZZ && SCSI
1290 select SCSI_SPI_ATTRS
1292 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1293 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1297 tristate "A3000 WD33C93A support"
1298 depends on AMIGA && SCSI
1300 If you have an Amiga 3000 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 a3000.
1307 tristate "A2091/A590 WD33C93A support"
1308 depends on ZORRO && SCSI
1310 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1313 To compile this driver as a module, choose M here: the
1314 module will be called a2091.
1317 tristate "GVP Series II WD33C93A support"
1318 depends on ZORRO && SCSI
1320 If you have a Great Valley Products Series II SCSI controller,
1321 answer Y. Also say Y if you have a later model of GVP SCSI
1322 controller (such as the GVP A4008 or a Combo board). Otherwise,
1323 answer N. This driver does NOT work for the T-Rex series of
1324 accelerators from TekMagic and GVP-M.
1326 To compile this driver as a module, choose M here: the
1327 module will be called gvp11.
1330 tristate "A4000T NCR53c710 SCSI support"
1331 depends on AMIGA && SCSI
1332 select SCSI_SPI_ATTRS
1334 If you have an Amiga 4000T and have SCSI devices connected to the
1335 built-in SCSI controller, say Y. Otherwise, say N.
1337 To compile this driver as a module, choose M here: the
1338 module will be called a4000t.
1340 config SCSI_ZORRO7XX
1341 tristate "Zorro NCR53c710 SCSI support"
1342 depends on ZORRO && SCSI
1343 select SCSI_SPI_ATTRS
1345 Support for various NCR53c710-based SCSI controllers on Zorro
1346 expansion boards for the Amiga.
1348 - the Amiga 4091 Zorro III SCSI-2 controller,
1349 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1351 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1352 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1353 accelerator card for the Amiga 1200,
1354 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1356 config SCSI_ZORRO_ESP
1357 tristate "Zorro ESP SCSI support"
1358 depends on ZORRO && SCSI
1359 select SCSI_SPI_ATTRS
1362 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1363 expansion boards for the Amiga.
1365 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1366 - the Phase5 Blizzard 2060 SCSI controller,
1367 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1369 - the Fastlane Zorro III SCSI controller.
1372 tristate "Atari native SCSI support"
1373 depends on ATARI && SCSI
1374 select SCSI_SPI_ATTRS
1376 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1377 Falcon, ...) say Y to get it supported. Of course also, if you have
1378 a compatible SCSI controller (e.g. for Medusa).
1380 To compile this driver as a module, choose M here: the module will
1381 be called atari_scsi. If you also enable NVRAM support, the SCSI
1382 host's ID is taken from the setting in TT RTC NVRAM.
1384 This driver supports both styles of NCR integration into the
1385 system: the TT style (separate DMA), and the Falcon style (via
1386 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1387 in the Hades (without DMA).
1390 tristate "Macintosh NCR5380 SCSI"
1391 depends on MAC && SCSI
1392 select SCSI_SPI_ATTRS
1394 This is the NCR 5380 SCSI controller included on most of the 68030
1395 based Macintoshes. If you have one of these say Y and read the
1396 SCSI-HOWTO, available from
1397 <http://www.tldp.org/docs.html#howto>.
1400 tristate "Macintosh NCR53c9[46] SCSI"
1401 depends on MAC && SCSI
1402 select SCSI_SPI_ATTRS
1405 This is the NCR 53c9x SCSI controller found on most of the 68040
1408 To compile this driver as a module, choose M here: the module
1409 will be called mac_esp.
1412 bool "WD33C93 SCSI driver for MVME147"
1413 depends on MVME147 && SCSI=y
1414 select SCSI_SPI_ATTRS
1416 Support for the on-board SCSI controller on the Motorola MVME147
1417 single-board computer.
1420 tristate "NCR53C710 SCSI driver for MVME16x"
1421 depends on MVME16x && SCSI
1422 select SCSI_SPI_ATTRS
1424 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1425 SCSI controller chip. Almost everyone using one of these boards
1426 will want to say Y to this question.
1428 config BVME6000_SCSI
1429 tristate "NCR53C710 SCSI driver for BVME6000"
1430 depends on BVME6000 && SCSI
1431 select SCSI_SPI_ATTRS
1433 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1434 SCSI controller chip. Almost everyone using one of these boards
1435 will want to say Y to this question.
1438 tristate "Sun3 NCR5380 SCSI"
1439 depends on SUN3 && SCSI
1440 select SCSI_SPI_ATTRS
1442 This option will enable support for the OBIO (onboard io) NCR5380
1443 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1444 "Sun3" type VME scsi controllers also based on the NCR5380.
1445 General Linux information on the Sun 3 series (now discontinued)
1446 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1449 bool "Sun3x ESP SCSI"
1450 depends on SUN3X && SCSI=y
1451 select SCSI_SPI_ATTRS
1453 The ESP was an on-board SCSI controller used on Sun 3/80
1454 machines. Say Y here to compile in support for it.
1457 tristate "Sparc ESP Scsi Driver"
1458 depends on SBUS && SCSI
1459 select SCSI_SPI_ATTRS
1461 This is the driver for the Sun ESP SCSI host adapter. The ESP
1462 chipset is present in most SPARC SBUS-based computers and
1463 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1464 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1466 To compile this driver as a module, choose M here: the
1467 module will be called sun_esp.
1470 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1471 depends on S390 && QDIO && SCSI
1472 depends on SCSI_FC_ATTRS
1474 If you want to access SCSI devices attached to your IBM eServer
1475 zSeries by means of Fibre Channel interfaces say Y.
1476 For details please refer to the documentation provided by IBM at
1477 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1479 This driver is also available as a module. This module will be
1480 called zfcp. If you want to compile it as a module, say M here
1481 and read <file:Documentation/kbuild/modules.rst>.
1484 tristate "PMC SIERRA Linux MaxRAID adapter support"
1485 depends on PCI && SCSI && NET
1488 This driver supports the PMC SIERRA MaxRAID adapters.
1491 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1492 depends on PCI && SCSI
1493 select SCSI_SAS_LIBSAS
1495 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1496 based host adapters.
1499 tristate "Brocade BFA Fibre Channel Support"
1500 depends on PCI && SCSI
1501 depends on SCSI_FC_ATTRS
1503 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1505 To compile this driver as a module, choose M here. The module will
1509 tristate "virtio-scsi support"
1512 This is the virtual HBA driver for virtio. If the kernel will
1513 be used in a virtual machine, say Y or M.
1515 source "drivers/scsi/csiostor/Kconfig"
1517 source "drivers/scsi/pcmcia/Kconfig"
1519 endif # SCSI_LOWLEVEL
1521 source "drivers/scsi/device_handler/Kconfig"