1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "SCSI device support"
6 default y if SCSI=n || SCSI=y
11 tristate "RAID Transport Class"
22 tristate "SCSI device support"
24 select SCSI_DMA if HAS_DMA
27 select BLK_DEV_BSG_COMMON if BLK_DEV_BSG
29 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
30 any other SCSI device under Linux, say Y and make sure that you know
31 the name of your SCSI host adapter (the card inside your computer
32 that "speaks" the SCSI protocol, also called SCSI controller),
33 because you will be asked for it.
35 You also need to say Y here if you have a device which speaks
36 the SCSI protocol. Examples of this include the parallel port
37 version of the IOMEGA ZIP drive, USB storage devices, Fibre
38 Channel, and FireWire storage.
40 To compile this driver as a module, choose M here and read
41 <file:Documentation/scsi/scsi.rst>.
42 The module will be called scsi_mod.
44 However, do not compile this as a module if your root file system
45 (the one containing the directory /) is located on a SCSI device.
60 bool "legacy /proc/scsi/ support"
61 depends on SCSI && PROC_FS
64 This option enables support for the various files in
65 /proc/scsi. In Linux 2.6 this has been superseded by
66 files in sysfs but many legacy applications rely on this.
70 comment "SCSI support type (disk, tape, CD-ROM)"
74 tristate "SCSI disk support"
76 select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY
78 If you want to use SCSI hard disks, Fibre Channel disks,
79 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
80 USB storage or the SCSI or parallel port version of
81 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
82 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
86 To compile this driver as a module, choose M here and read
87 <file:Documentation/scsi/scsi.rst>.
88 The module will be called sd_mod.
90 Do not compile this driver as a module if your root file system
91 (the one containing the directory /) is located on a SCSI disk.
92 In this case, do not compile the driver for your SCSI host adapter
93 (below) as a module either.
96 tristate "SCSI tape support"
99 If you want to use a SCSI tape drive under Linux, say Y and read the
100 SCSI-HOWTO, available from
101 <http://www.tldp.org/docs.html#howto>, and
102 <file:Documentation/scsi/st.rst> in the kernel source. This is NOT
105 To compile this driver as a module, choose M here and read
106 <file:Documentation/scsi/scsi.rst>. The module will be called st.
109 tristate "SCSI CDROM support"
110 depends on SCSI && BLK_DEV
113 If you want to use a CD or DVD drive attached to your computer
114 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
115 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
117 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
119 To compile this driver as a module, choose M here and read
120 <file:Documentation/scsi/scsi.rst>.
121 The module will be called sr_mod.
124 tristate "SCSI generic support"
127 If you want to use SCSI scanners, synthesizers or CD-writers or just
128 about anything having "SCSI" in its name other than hard disks,
129 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
130 directly, so you need some additional software which knows how to
131 talk to these devices using the SCSI protocol:
133 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
134 writer software look at Cdrtools
135 (<http://cdrtools.sourceforge.net/>)
136 and for burning a "disk at once": CDRDAO
137 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
138 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
139 For other devices, it's possible that you'll have to write the
140 driver software yourself. Please read the file
141 <file:Documentation/scsi/scsi-generic.rst> for more information.
143 To compile this driver as a module, choose M here and read
144 <file:Documentation/scsi/scsi.rst>. The module will be called sg.
149 bool "/dev/bsg support (SG v4)"
153 Saying Y here will enable generic SG (SCSI generic) v4 support
156 This option is required by UDEV to access device serial numbers, etc.
161 tristate "SCSI media changer support"
164 This is a driver for SCSI media changers. Most common devices are
165 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
166 don't need this for those tiny 6-slot cdrom changers. Media
167 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
168 If you have such hardware and want to use it with linux, say Y
169 here. Check <file:Documentation/scsi/scsi-changer.rst> for details.
171 If you want to compile this as a module ( = code which can be
172 inserted in and removed from the running kernel whenever you want),
173 say M here and read <file:Documentation/kbuild/modules.rst> and
174 <file:Documentation/scsi/scsi.rst>. The module will be called ch.o.
177 config SCSI_ENCLOSURE
178 tristate "SCSI Enclosure Support"
179 depends on SCSI && ENCLOSURE_SERVICES
180 depends on m || SCSI_SAS_ATTRS != m
182 Enclosures are devices sitting on or in SCSI backplanes that
183 manage devices. If you have a disk cage, the chances are that
184 it has an enclosure device. Selecting this option will just allow
185 certain enclosure conditions to be reported and is not required.
187 config SCSI_CONSTANTS
188 bool "Verbose SCSI error reporting (kernel size += 36K)"
191 The error messages regarding your SCSI hardware will be easier to
192 understand if you say Y here; it will enlarge your kernel by about
193 36 KB. If in doubt, say Y.
196 bool "SCSI logging facility"
199 This turns on a logging facility that can be used to debug a number
200 of SCSI related problems.
202 If you say Y here, no logging output will appear by default, but you
203 can enable logging by saying Y to "/proc file system support" and
204 "Sysctl support" below and executing the command
206 echo <bitmask> > /proc/sys/dev/scsi/logging_level
208 where <bitmask> is a four byte value representing the logging type
209 and logging level for each type of logging selected.
211 There are a number of logging types and you can find them in the
212 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
213 are also described in that file and they determine the verbosity of
214 the logging for each logging type.
216 If you say N here, it may be harder to track down some types of SCSI
217 problems. If you say Y here your kernel will be somewhat larger, but
218 there should be no noticeable performance impact as long as you have
221 config SCSI_SCAN_ASYNC
222 bool "Asynchronous SCSI scanning"
225 The SCSI subsystem can probe for devices while the rest of the
226 system continues booting, and even probe devices on different
227 busses in parallel, leading to a significant speed-up.
229 You can override this choice by specifying "scsi_mod.scan=sync"
230 or async on the kernel's command line.
232 Note that this setting also affects whether resuming from
233 system suspend will be performed asynchronously.
235 menu "SCSI Transports"
238 config SCSI_SPI_ATTRS
239 tristate "Parallel SCSI (SPI) Transport Attributes"
242 If you wish to export transport-specific information about
243 each attached SCSI device to sysfs, say Y. Otherwise, say N.
246 tristate "FiberChannel Transport Attributes"
247 depends on SCSI && NET
248 select BLK_DEV_BSGLIB
251 If you wish to export transport-specific information about
252 each attached FiberChannel device to sysfs, say Y.
255 config SCSI_ISCSI_ATTRS
256 tristate "iSCSI Transport Attributes"
257 depends on SCSI && NET
258 select BLK_DEV_BSGLIB
260 If you wish to export transport-specific information about
261 each attached iSCSI device to sysfs, say Y.
264 config SCSI_SAS_ATTRS
265 tristate "SAS Transport Attributes"
267 select BLK_DEV_BSGLIB
269 If you wish to export transport-specific information about
270 each attached SAS device to sysfs, say Y.
272 source "drivers/scsi/libsas/Kconfig"
274 config SCSI_SRP_ATTRS
275 tristate "SRP Transport Attributes"
278 If you wish to export transport-specific information about
279 each attached SRP device to sysfs, say Y.
283 menuconfig SCSI_LOWLEVEL
284 bool "SCSI low-level drivers"
288 if SCSI_LOWLEVEL && SCSI
291 tristate "iSCSI Initiator over TCP/IP"
292 depends on SCSI && INET
296 select SCSI_ISCSI_ATTRS
298 The iSCSI Driver provides a host with the ability to access storage
299 through an IP network. The driver uses the iSCSI protocol to transport
300 SCSI requests and responses over a TCP/IP network between the host
301 (the "initiator") and "targets". Architecturally, the iSCSI driver
302 combines with the host's TCP/IP stack, network drivers, and Network
303 Interface Card (NIC) to provide the same functions as a SCSI or a
304 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
306 To compile this driver as a module, choose M here: the
307 module will be called iscsi_tcp.
309 The userspace component needed to initialize the driver, documentation,
310 and sample configuration files can be found here:
312 http://open-iscsi.org
314 config ISCSI_BOOT_SYSFS
315 tristate "iSCSI Boot Sysfs Interface"
318 This option enables support for exposing iSCSI boot information
319 via sysfs to userspace. If you wish to export this information,
320 say Y. Otherwise, say N.
322 source "drivers/scsi/cxgbi/Kconfig"
323 source "drivers/scsi/bnx2i/Kconfig"
324 source "drivers/scsi/bnx2fc/Kconfig"
325 source "drivers/scsi/be2iscsi/Kconfig"
326 source "drivers/scsi/cxlflash/Kconfig"
329 tristate "SGI WD93C93 SCSI Driver"
330 depends on SGI_HAS_WD93 && SCSI
332 If you have a Western Digital WD93 SCSI controller on
333 an SGI MIPS system, say Y. Otherwise, say N.
335 config BLK_DEV_3W_XXXX_RAID
336 tristate "3ware 5/6/7/8xxx ATA-RAID support"
337 depends on PCI && HAS_IOPORT && SCSI
339 3ware is the only hardware ATA-Raid product in Linux to date.
340 This card is 2,4, or 8 channel master mode support only.
341 SCSI support required!!!
343 <http://www.3ware.com/>
345 Please read the comments at the top of
346 <file:drivers/scsi/3w-xxxx.c>.
349 tristate "HP Smart Array SCSI driver"
350 depends on PCI && SCSI
351 select CHECK_SIGNATURE
352 select SCSI_SAS_ATTRS
354 This driver supports HP Smart Array Controllers (circa 2009).
355 It is a SCSI alternative to the cciss driver, which is a block
356 driver. Anyone wishing to use HP Smart Array controllers who
357 would prefer the devices be presented to linux as SCSI devices,
358 rather than as generic block devices should say Y here.
361 tristate "3ware 9xxx SATA-RAID support"
362 depends on PCI && SCSI
364 This driver supports the 9000 series 3ware SATA-RAID cards.
366 <http://www.amcc.com>
368 Please read the comments at the top of
369 <file:drivers/scsi/3w-9xxx.c>.
372 tristate "3ware 97xx SAS/SATA-RAID support"
373 depends on PCI && SCSI
375 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
379 Please read the comments at the top of
380 <file:drivers/scsi/3w-sas.c>.
383 tristate "ACARD SCSI support"
384 depends on PCI && HAS_IOPORT && SCSI
386 This driver supports the ACARD SCSI host adapter.
387 Support Chip <ATP870 ATP876 ATP880 ATP885>
388 To compile this driver as a module, choose M here: the
389 module will be called atp870u.
392 tristate "Adaptec AHA152X/2825 support"
393 depends on ISA && SCSI
394 select SCSI_SPI_ATTRS
395 select CHECK_SIGNATURE
397 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
398 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
399 must be manually specified in this case.
401 It is explained in section 3.3 of the SCSI-HOWTO, available from
402 <http://www.tldp.org/docs.html#howto>. You might also want to
403 read the file <file:Documentation/scsi/aha152x.rst>.
405 To compile this driver as a module, choose M here: the
406 module will be called aha152x.
409 tristate "Adaptec AHA1542 support"
410 depends on ISA && SCSI && ISA_DMA_API
412 This is support for a SCSI host adapter. It is explained in section
413 3.4 of the SCSI-HOWTO, available from
414 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
415 purchased by Adaptec, and some former Trantor products are being
416 sold under the Adaptec name. If it doesn't work out of the box, you
417 may have to change some settings in <file:drivers/scsi/aha1542.h>.
419 To compile this driver as a module, choose M here: the
420 module will be called aha1542.
423 tristate "Adaptec AHA1740 support"
424 depends on EISA && SCSI
426 This is support for a SCSI host adapter. It is explained in section
427 3.5 of the SCSI-HOWTO, available from
428 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
429 of the box, you may have to change some settings in
430 <file:drivers/scsi/aha1740.h>.
432 To compile this driver as a module, choose M here: the
433 module will be called aha1740.
436 tristate "Adaptec AACRAID support"
437 depends on SCSI && PCI
439 This driver supports a variety of Dell, HP, Adaptec, IBM and
440 ICP storage products. For a list of supported products, refer
441 to <file:Documentation/scsi/aacraid.rst>.
443 To compile this driver as a module, choose M here: the module
444 will be called aacraid.
447 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
448 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
449 source "drivers/scsi/aic94xx/Kconfig"
450 source "drivers/scsi/hisi_sas/Kconfig"
451 source "drivers/scsi/mvsas/Kconfig"
454 tristate "Marvell UMI driver"
455 depends on SCSI && PCI
457 Module for Marvell Universal Message Interface(UMI) driver
459 To compile this driver as a module, choose M here: the
460 module will be called mvumi.
463 tristate "AdvanSys SCSI support"
465 depends on (ISA || EISA || PCI) && HAS_IOPORT
466 depends on ISA_DMA_API || !ISA
468 This is a driver for all SCSI host adapters manufactured by
469 AdvanSys. It is documented in the kernel source in
470 <file:drivers/scsi/advansys.c>.
472 To compile this driver as a module, choose M here: the
473 module will be called advansys.
476 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
477 depends on PCI && SCSI
479 This driver supports all of ARECA's SATA/SAS RAID controller cards.
480 This is an ARECA-maintained driver by Erich Chen.
481 If you have any problems, please mail to: <erich@areca.com.tw>.
482 Areca supports Linux RAID config tools.
483 Please link <http://www.areca.com.tw>
485 To compile this driver as a module, choose M here: the
486 module will be called arcmsr (modprobe arcmsr).
488 source "drivers/scsi/esas2r/Kconfig"
489 source "drivers/scsi/megaraid/Kconfig.megaraid"
490 source "drivers/scsi/mpt3sas/Kconfig"
491 source "drivers/scsi/mpi3mr/Kconfig"
492 source "drivers/scsi/smartpqi/Kconfig"
495 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
496 depends on SCSI && PCI
498 This option enables support for HighPoint RocketRAID 3xxx/4xxx
501 To compile this driver as a module, choose M here; the module
502 will be called hptiop. If unsure, say N.
505 tristate "BusLogic SCSI support"
506 depends on SCSI && PCI && HAS_IOPORT
508 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
509 Adapters. Consult the SCSI-HOWTO, available from
510 <http://www.tldp.org/docs.html#howto>, and the files
511 <file:Documentation/scsi/BusLogic.rst> and
512 <file:Documentation/scsi/FlashPoint.rst> for more information.
513 Note that support for FlashPoint is only available for 32-bit
516 To compile this driver as a module, choose M here: the
517 module will be called BusLogic.
519 config SCSI_FLASHPOINT
520 bool "FlashPoint support"
521 depends on SCSI_BUSLOGIC && PCI && HAS_IOPORT
523 This option allows you to add FlashPoint support to the
524 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
525 substantial, so users of MultiMaster Host Adapters may not
529 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
533 This driver adds support for the Mylex DAC960, AcceleRAID, and
534 eXtremeRAID PCI RAID controllers. This driver supports the
535 older, block based interface.
536 This driver is a reimplementation of the original DAC960
537 driver. If you have used the DAC960 driver you should enable
540 To compile this driver as a module, choose M here: the
541 module will be called myrb.
544 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
546 depends on !CPU_BIG_ENDIAN || COMPILE_TEST
549 This driver adds support for the Mylex DAC960, AcceleRAID, and
550 eXtremeRAID PCI RAID controllers. This driver supports the
551 newer, SCSI-based interface only.
552 This driver is a reimplementation of the original DAC960
553 driver. If you have used the DAC960 driver you should enable
556 To compile this driver as a module, choose M here: the
557 module will be called myrs.
560 tristate "VMware PVSCSI driver support"
561 depends on PCI && SCSI && X86
563 This driver supports VMware's para virtualized SCSI HBA.
564 To compile this driver as a module, choose M here: the
565 module will be called vmw_pvscsi.
567 config XEN_SCSI_FRONTEND
568 tristate "XEN SCSI frontend driver"
569 depends on SCSI && XEN
570 select XEN_XENBUS_FRONTEND
572 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
573 within another guest OS (usually Dom0).
574 Only needed if the kernel is running in a XEN guest and generic
575 SCSI access to a device is needed.
577 config HYPERV_STORAGE
578 tristate "Microsoft Hyper-V virtual storage driver"
579 depends on SCSI && HYPERV
580 depends on m || SCSI_FC_ATTRS != m
583 Select this option to enable the Hyper-V virtual storage driver.
586 tristate "LibFC module"
587 depends on SCSI_FC_ATTRS
590 Fibre Channel library module
593 tristate "LibFCoE module"
596 Library for Fibre Channel over Ethernet module
599 tristate "FCoE module"
603 Fibre Channel over Ethernet module
606 tristate "Cisco FNIC Driver"
607 depends on PCI && X86
610 This is support for the Cisco PCI-Express FCoE HBA.
612 To compile this driver as a module, choose M here and read
613 <file:Documentation/scsi/scsi.rst>.
614 The module will be called fnic.
617 tristate "Cisco SNIC Driver"
618 depends on PCI && SCSI
620 This is support for the Cisco PCI-Express SCSI HBA.
622 To compile this driver as a module, choose M here and read
623 <file:Documentation/scsi/scsi.rst>.
624 The module will be called snic.
626 config SCSI_SNIC_DEBUG_FS
627 bool "Cisco SNIC Driver Debugfs Support"
628 depends on SCSI_SNIC && DEBUG_FS
630 This enables to list debugging information from SNIC Driver
631 available via debugfs file system
634 tristate "DMX3191D SCSI support"
635 depends on PCI && HAS_IOPORT && SCSI
636 select SCSI_SPI_ATTRS
638 This is support for Domex DMX3191D SCSI Host Adapters.
640 To compile this driver as a module, choose M here: the
641 module will be called dmx3191d.
647 config SCSI_FDOMAIN_PCI
648 tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
649 depends on PCI && HAS_IOPORT && SCSI
652 This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
653 and other adapters with PCI bus based on the Future Domain chipsets
656 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
657 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
658 controller support"). This Future Domain driver works with the older
659 Adaptec AHA-2920A boards with a Future Domain chip on them.
661 To compile this driver as a module, choose M here: the
662 module will be called fdomain_pci.
664 config SCSI_FDOMAIN_ISA
665 tristate "Future Domain 16xx ISA SCSI support"
666 depends on ISA && SCSI
667 select CHECK_SIGNATURE
670 This is support for Future Domain's 16-bit SCSI host adapters
671 (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
672 with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
673 ISA-250MG; and at least one IBM board).
675 To compile this driver as a module, choose M here: the
676 module will be called fdomain_isa.
679 tristate "Intel(R) C600 Series Chipset SAS Controller"
680 depends on PCI && SCSI
682 select SCSI_SAS_LIBSAS
684 This driver supports the 6Gb/s SAS capabilities of the storage
685 control unit found in the Intel(R) C600 series chipset.
687 config SCSI_GENERIC_NCR5380
688 tristate "Generic NCR5380/53c400 SCSI ISA card support"
689 depends on ISA && SCSI && HAS_IOPORT_MAP
690 select SCSI_SPI_ATTRS
692 This is a driver for old ISA card SCSI controllers based on a
693 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
694 Most boards such as the Trantor T130 fit this category, as do
695 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
697 To compile this driver as a module, choose M here: the
698 module will be called g_NCR5380.
701 tristate "IBM ServeRAID support"
702 depends on PCI && HAS_IOPORT && SCSI
704 This is support for the IBM ServeRAID hardware RAID controllers.
705 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
706 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
707 for more information. If this driver does not work correctly
708 without modification please contact the author by email at
709 <ipslinux@adaptec.com>.
711 To compile this driver as a module, choose M here: the
712 module will be called ips.
715 tristate "IBM Virtual SCSI support"
716 depends on PPC_PSERIES
717 select SCSI_SRP_ATTRS
719 This is the IBM POWER Virtual SCSI Client
721 To compile this driver as a module, choose M here: the
722 module will be called ibmvscsi.
724 config SCSI_IBMVSCSIS
725 tristate "IBM Virtual SCSI Server support"
726 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
728 This is the IBM POWER Virtual SCSI Target Server
729 This driver uses the SRP protocol for communication between servers
730 guest and/or the host that run on the same server.
731 More information on VSCSI protocol can be found at www.power.org
733 The userspace configuration needed to initialize the driver can be
736 https://github.com/powervm/ibmvscsis/wiki/Configuration
738 To compile this driver as a module, choose M here: the
739 module will be called ibmvscsis.
742 tristate "IBM Virtual FC support"
743 depends on PPC_PSERIES && SCSI
744 depends on SCSI_FC_ATTRS
746 This is the IBM POWER Virtual FC Client
748 To compile this driver as a module, choose M here: the
749 module will be called ibmvfc.
751 config SCSI_IBMVFC_TRACE
752 bool "enable driver internal trace"
753 depends on SCSI_IBMVFC
756 If you say Y here, the driver will trace all commands issued
757 to the adapter. Performance impact is minimal. Trace can be
758 dumped using /sys/class/scsi_host/hostXX/trace.
761 tristate "Initio 9100U(W) support"
762 depends on PCI && HAS_IOPORT && SCSI
764 This is support for the Initio 91XXU(W) SCSI host adapter. Please
765 read the SCSI-HOWTO, available from
766 <http://www.tldp.org/docs.html#howto>.
768 To compile this driver as a module, choose M here: the
769 module will be called initio.
772 tristate "Initio INI-A100U2W support"
773 depends on PCI && HAS_IOPORT && SCSI
775 This is support for the Initio INI-A100U2W SCSI host adapter.
776 Please read the SCSI-HOWTO, available from
777 <http://www.tldp.org/docs.html#howto>.
779 To compile this driver as a module, choose M here: the
780 module will be called a100u2w.
783 tristate "IOMEGA parallel port (ppa - older drives)"
784 depends on SCSI && PARPORT_PC
785 depends on HAS_IOPORT
787 This driver supports older versions of IOMEGA's parallel port ZIP
788 drive (a 100 MB removable media device).
790 Note that you can say N here if you have the SCSI version of the ZIP
791 drive: it will be supported automatically if you said Y to the
792 generic "SCSI disk support", above.
794 If you have the ZIP Plus drive or a more recent parallel port ZIP
795 drive (if the supplied cable with the drive is labeled "AutoDetect")
796 then you should say N here and Y to "IOMEGA parallel port (imm -
797 newer drives)", below.
799 For more information about this driver and how to use it you should
800 read the file <file:Documentation/scsi/ppa.rst>. You should also read
801 the SCSI-HOWTO, which is available from
802 <http://www.tldp.org/docs.html#howto>. If you use this driver,
803 you will still be able to use the parallel port for other tasks,
804 such as a printer; it is safe to compile both drivers into the
807 To compile this driver as a module, choose M here: the
808 module will be called ppa.
811 tristate "IOMEGA parallel port (imm - newer drives)"
812 depends on SCSI && PARPORT_PC
814 This driver supports newer versions of IOMEGA's parallel port ZIP
815 drive (a 100 MB removable media device).
817 Note that you can say N here if you have the SCSI version of the ZIP
818 drive: it will be supported automatically if you said Y to the
819 generic "SCSI disk support", above.
821 If you have the ZIP Plus drive or a more recent parallel port ZIP
822 drive (if the supplied cable with the drive is labeled "AutoDetect")
823 then you should say Y here; if you have an older ZIP drive, say N
824 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
826 For more information about this driver and how to use it you should
827 read the file <file:Documentation/scsi/ppa.rst>. You should also read
828 the SCSI-HOWTO, which is available from
829 <http://www.tldp.org/docs.html#howto>. If you use this driver,
830 you will still be able to use the parallel port for other tasks,
831 such as a printer; it is safe to compile both drivers into the
834 To compile this driver as a module, choose M here: the
835 module will be called imm.
837 config SCSI_IZIP_SLOW_CTR
838 bool "ppa/imm option - Assume slow parport control register"
839 depends on SCSI_PPA || SCSI_IMM
841 Some parallel ports are known to have excessive delays between
842 changing the parallel port control register and good data being
843 available on the parallel port data/status register. This option
844 forces a small delay (1.0 usec to be exact) after changing the
845 control register to let things settle out. Enabling this option may
846 result in a big drop in performance but some very old parallel ports
847 (found in 386 vintage machines) will not work properly.
849 Generally, saying N is fine.
852 tristate "HP Lasi SCSI support for 53c700/710"
853 depends on GSC && SCSI
854 select SCSI_SPI_ATTRS
856 This is a driver for the SCSI controller in the Lasi chip found in
857 many PA-RISC workstations & servers. If you do not know whether you
858 have a Lasi chip, it is safe to say "Y" here.
860 config SCSI_SNI_53C710
861 tristate "SNI RM SCSI support for 53c710"
862 depends on SNI_RM && SCSI
863 select SCSI_SPI_ATTRS
864 select 53C700_LE_ON_BE
866 This is a driver for the onboard SCSI controller found in older
867 SNI RM workstations & servers.
869 config 53C700_LE_ON_BE
871 depends on SCSI_LASI700 || SCSI_SNI_53C710
875 tristate "Promise SuperTrak EX Series support"
876 depends on PCI && SCSI
878 This driver supports Promise SuperTrak EX series storage controllers.
880 Promise provides Linux RAID configuration utility for these
881 controllers. Please visit <http://www.promise.com> to download.
883 To compile this driver as a module, choose M here: the
884 module will be called stex.
888 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
891 config SCSI_SYM53C8XX_2
892 tristate "SYM53C8XX Version 2 SCSI support"
893 depends on PCI && SCSI
894 select SCSI_SPI_ATTRS
896 This driver supports the whole NCR53C8XX/SYM53C8XX family of
897 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
898 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
899 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
900 controllers; you need to use the Fusion MPT driver for that.
902 Please read <file:Documentation/scsi/sym53c8xx_2.rst> for more
905 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
906 int "DMA addressing mode"
907 depends on SCSI_SYM53C8XX_2
910 This option only applies to PCI-SCSI chips that are PCI DAC
911 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
913 When set to 0, the driver will program the chip to only perform
914 32-bit DMA. When set to 1, the chip will be able to perform DMA
915 to addresses up to 1TB. When set to 2, the driver supports the
916 full 64-bit DMA address range, but can only address 16 segments
917 of 4 GB each. This limits the total addressable range to 64 GB.
919 Most machines with less than 4GB of memory should use a setting
920 of 0 for best performance. If your machine has 4GB of memory
921 or more, you should set this option to 1 (the default).
923 The still experimental value 2 (64 bit DMA addressing with 16
924 x 4GB segments limitation) can be used on systems that require
925 PCI address bits past bit 39 to be set for the addressing of
926 memory using PCI DAC cycles.
928 config SCSI_SYM53C8XX_DEFAULT_TAGS
929 int "Default tagged command queue depth"
930 depends on SCSI_SYM53C8XX_2
933 This is the default value of the command queue depth the
934 driver will announce to the generic SCSI layer for devices
935 that support tagged command queueing. This value can be changed
936 from the boot command line. This is a soft limit that cannot
937 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
939 config SCSI_SYM53C8XX_MAX_TAGS
940 int "Maximum number of queued commands"
941 depends on SCSI_SYM53C8XX_2
944 This option allows you to specify the maximum number of commands
945 that can be queued to any device, when tagged command queuing is
946 possible. The driver supports up to 256 queued commands per device.
947 This value is used as a compiled-in hard limit.
949 config SCSI_SYM53C8XX_MMIO
950 bool "Use memory mapped IO"
951 depends on SCSI_SYM53C8XX_2
954 Memory mapped IO is faster than Port IO. Most people should
955 answer Y here, but some machines may have problems. If you have
956 to answer N here, please report the problem to the maintainer.
959 tristate "IBM Power Linux RAID adapter support"
960 depends on PCI && SCSI
965 This driver supports the IBM Power Linux family RAID adapters.
966 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
967 as IBM iSeries 5702, 5703, 5709, and 570A.
969 config SCSI_IPR_TRACE
970 bool "enable driver internal trace"
974 If you say Y here, the driver will trace all commands issued
975 to the adapter. Performance impact is minimal. Trace can be
976 dumped using /sys/bus/class/scsi_host/hostXX/trace.
979 bool "enable adapter dump support"
983 If you say Y here, the driver will support adapter crash dump.
984 If you enable this support, the iprdump daemon can be used
985 to capture adapter failure analysis information.
988 tristate "Zalon SCSI support"
989 depends on GSC && SCSI
990 select SCSI_SPI_ATTRS
992 The Zalon is a GSC/HSC bus interface chip that sits between the
993 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
994 C110, J200, J210 and some D, K & R-class machines. It's also
995 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
996 Say Y here if you have one of these machines or cards.
998 config SCSI_NCR53C8XX_DEFAULT_TAGS
999 int "default tagged command queue depth"
1000 depends on SCSI_ZALON
1003 "Tagged command queuing" is a feature of SCSI-2 which improves
1004 performance: the host adapter can send several SCSI commands to a
1005 device's queue even if previous commands haven't finished yet.
1006 Because the device is intelligent, it can optimize its operations
1007 (like head positioning) based on its own request queue. Some SCSI
1008 devices don't implement this properly; if you want to disable this
1009 feature, enter 0 or 1 here (it doesn't matter which).
1011 The default value is 8 and should be supported by most hard disks.
1012 This value can be overridden from the boot command line using the
1013 'tags' option as follows (example):
1014 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1015 4, set queue depth to 16 for target 2 and target 3 on controller 0
1016 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1018 The normal answer therefore is to go with the default 8 and to use
1019 a boot command line option for devices that need to use a different
1020 command queue depth.
1022 There is no safe option other than using good SCSI devices.
1024 config SCSI_NCR53C8XX_MAX_TAGS
1025 int "maximum number of queued commands"
1026 depends on SCSI_ZALON
1029 This option allows you to specify the maximum number of commands
1030 that can be queued to any device, when tagged command queuing is
1031 possible. The default value is 32. Minimum is 2, maximum is 64.
1032 Modern hard disks are able to support 64 tags and even more, but
1033 do not seem to be faster when more than 32 tags are being used.
1035 So, the normal answer here is to go with the default value 32 unless
1036 you are using very large hard disks with large cache (>= 1 MB) that
1037 are able to take advantage of more than 32 tagged commands.
1039 There is no safe option and the default answer is recommended.
1041 config SCSI_NCR53C8XX_SYNC
1042 int "synchronous transfers frequency in MHz"
1043 depends on SCSI_ZALON
1046 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1047 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1048 are respectively the maximum data transfer rates in mega-transfers
1049 per second for each class. For example, a FAST-20 Wide 16 device is
1050 able to transfer data at 20 million 16 bit packets per second for a
1051 total rate of 40 MB/s.
1053 You may specify 0 if you want to only use asynchronous data
1054 transfers. This is the safest and slowest option. Otherwise, specify
1055 a value between 5 and 80, depending on the capability of your SCSI
1056 controller. The higher the number, the faster the data transfer.
1057 Note that 80 should normally be ok since the driver decreases the
1058 value automatically according to the controller's capabilities.
1060 Your answer to this question is ignored for controllers with NVRAM,
1061 since the driver will get this information from the user set-up. It
1062 also can be overridden using a boot setup option, as follows
1063 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1064 for FAST-20 synchronous data transfer (20 mega-transfers per
1067 The normal answer therefore is not to go with the default but to
1068 select the maximum value 80 allowing the driver to use the maximum
1069 value supported by each controller. If this causes problems with
1070 your SCSI devices, you should come back and decrease the value.
1072 There is no safe option other than using good cabling, right
1073 terminations and SCSI conformant devices.
1075 config SCSI_NCR53C8XX_NO_DISCONNECT
1076 bool "not allow targets to disconnect"
1077 depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1079 This option is only provided for safety if you suspect some SCSI
1080 device of yours to not support properly the target-disconnect
1081 feature. In that case, you would say Y here. In general however, to
1082 not allow targets to disconnect is not reasonable if there is more
1083 than 1 device on a SCSI bus. The normal answer therefore is N.
1085 config SCSI_QLOGIC_FAS
1086 tristate "Qlogic FAS SCSI support"
1087 depends on ISA && SCSI
1089 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1090 FastSCSI! cards as well as any other card based on the FASXX chip
1091 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1093 This driver does NOT support the PCI versions of these cards. The
1094 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1095 SCSI support"), below.
1097 Information about this driver is contained in
1098 <file:Documentation/scsi/qlogicfas.rst>. You should also read the
1099 SCSI-HOWTO, available from
1100 <http://www.tldp.org/docs.html#howto>.
1102 To compile this driver as a module, choose M here: the
1103 module will be called qlogicfas.
1105 config SCSI_QLOGIC_1280
1106 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1107 depends on PCI && SCSI
1109 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1111 To compile this driver as a module, choose M here: the
1112 module will be called qla1280.
1114 config SCSI_QLOGICPTI
1115 tristate "PTI Qlogic, ISP Driver"
1116 depends on SBUS && SCSI
1118 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1119 controllers are known under Solaris as qpti and in the openprom as
1120 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1121 driven by a different driver.
1123 To compile this driver as a module, choose M here: the
1124 module will be called qlogicpti.
1126 source "drivers/scsi/qla2xxx/Kconfig"
1127 source "drivers/scsi/qla4xxx/Kconfig"
1128 source "drivers/scsi/qedi/Kconfig"
1129 source "drivers/scsi/qedf/Kconfig"
1132 tristate "Emulex LightPulse Fibre Channel Support"
1133 depends on PCI && SCSI
1135 depends on SCSI_FC_ATTRS
1136 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1137 depends on NVME_FC || NVME_FC=n
1141 This lpfc driver supports the Emulex LightPulse
1142 Family of Fibre Channel PCI host adapters.
1144 config SCSI_LPFC_DEBUG_FS
1145 bool "Emulex LightPulse Fibre Channel debugfs Support"
1146 depends on SCSI_LPFC && DEBUG_FS
1148 This makes debugging information from the lpfc driver
1149 available via the debugfs filesystem.
1151 source "drivers/scsi/elx/Kconfig"
1154 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1155 depends on EISA && SCSI
1156 select SCSI_SPI_ATTRS
1158 This driver is for NCR53c710 based SCSI host adapters.
1160 It currently supports Compaq EISA cards.
1163 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1164 depends on PCI && HAS_IOPORT && SCSI
1165 select SCSI_SPI_ATTRS
1167 This driver supports PCI SCSI host adapters based on the ASIC
1168 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1170 This driver works, but is still in experimental status. So better
1171 have a bootable disk and a backup in case of emergency.
1173 Documentation can be found in <file:Documentation/scsi/dc395x.rst>.
1175 To compile this driver as a module, choose M here: the
1176 module will be called dc395x.
1178 config SCSI_AM53C974
1179 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1180 depends on PCI && SCSI
1181 select SCSI_SPI_ATTRS
1183 This driver supports PCI SCSI host adapters based on the Am53C974A
1184 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1185 PCscsi/PCnet (Am53/79C974) solutions.
1186 This is a new implementation base on the generic esp_scsi driver.
1188 Note that this driver does NOT support Tekram DC390W/U/F, which are
1189 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1191 To compile this driver as a module, choose M here: the
1192 module will be called am53c974.
1195 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1196 depends on PCI && SCSI && !64BIT && HAS_IOPORT
1198 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1199 SCSI host adapter. Please read the SCSI-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here: the
1203 module will be called nsp32.
1206 tristate "Western Digital WD7193/7197/7296 support"
1207 depends on PCI && SCSI
1210 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1211 SCSI controllers (based on WD33C296A chip).
1214 tristate "SCSI debugging host and device simulator"
1218 This pseudo driver simulates one or more hosts (SCSI initiators),
1219 each with one or more targets, each with one or more logical units.
1220 Defaults to one of each, creating a small RAM disk device. Many
1221 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1222 directory can be tweaked at run time.
1223 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1224 Mainly used for testing and best as a module. If unsure, say N.
1227 tristate "MESH (Power Mac internal SCSI) support"
1228 depends on PPC32 && PPC_PMAC && SCSI
1230 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1231 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1232 other Power Macintoshes do). Say Y to include support for this SCSI
1235 To compile this driver as a module, choose M here: the
1236 module will be called mesh.
1238 config SCSI_MESH_SYNC_RATE
1239 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1240 depends on SCSI_MESH
1243 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1244 drives a bus which is entirely internal to the machine (such as the
1245 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1246 operation at up to 10 MB/s. On machines where the SCSI bus
1247 controlled by the MESH can have external devices connected, it is
1248 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1249 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1250 to disable synchronous operation.
1252 config SCSI_MESH_RESET_DELAY_MS
1253 int "initial bus reset delay (ms) (0 = no reset)"
1254 depends on SCSI_MESH
1257 config SCSI_MAC53C94
1258 tristate "53C94 (Power Mac external SCSI) support"
1259 depends on PPC32 && PPC_PMAC && SCSI
1261 On Power Macintoshes (and clones) with two SCSI buses, the external
1262 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1263 machines which only have one SCSI bus, such as the 7200, also use
1264 the 53C94. Say Y to include support for the 53C94.
1266 To compile this driver as a module, choose M here: the
1267 module will be called mac53c94.
1269 source "drivers/scsi/arm/Kconfig"
1272 bool "MIPS JAZZ FAS216 SCSI support"
1273 depends on MACH_JAZZ && SCSI=y
1274 select SCSI_SPI_ATTRS
1276 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1277 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1281 tristate "A3000 WD33C93A support"
1282 depends on AMIGA && SCSI
1284 If you have an Amiga 3000 and have SCSI devices connected to the
1285 built-in SCSI controller, say Y. Otherwise, say N.
1287 To compile this driver as a module, choose M here: the
1288 module will be called a3000.
1291 tristate "A2091/A590 WD33C93A support"
1292 depends on ZORRO && SCSI
1294 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1297 To compile this driver as a module, choose M here: the
1298 module will be called a2091.
1301 tristate "GVP Series II WD33C93A support"
1302 depends on ZORRO && SCSI
1304 If you have a Great Valley Products Series II SCSI controller,
1305 answer Y. Also say Y if you have a later model of GVP SCSI
1306 controller (such as the GVP A4008 or a Combo board). Otherwise,
1307 answer N. This driver does NOT work for the T-Rex series of
1308 accelerators from TekMagic and GVP-M.
1310 To compile this driver as a module, choose M here: the
1311 module will be called gvp11.
1314 tristate "A4000T NCR53c710 SCSI support"
1315 depends on AMIGA && SCSI
1316 select SCSI_SPI_ATTRS
1318 If you have an Amiga 4000T and have SCSI devices connected to the
1319 built-in SCSI controller, say Y. Otherwise, say N.
1321 To compile this driver as a module, choose M here: the
1322 module will be called a4000t.
1324 config SCSI_ZORRO7XX
1325 tristate "Zorro NCR53c710 SCSI support"
1326 depends on ZORRO && SCSI
1327 select SCSI_SPI_ATTRS
1329 Support for various NCR53c710-based SCSI controllers on Zorro
1330 expansion boards for the Amiga.
1332 - the Amiga 4091 Zorro III SCSI-2 controller,
1333 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1335 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1336 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1337 accelerator card for the Amiga 1200,
1338 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1340 config SCSI_ZORRO_ESP
1341 tristate "Zorro ESP SCSI support"
1342 depends on ZORRO && SCSI
1343 select SCSI_SPI_ATTRS
1346 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1347 expansion boards for the Amiga.
1349 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1350 - the Phase5 Blizzard 2060 SCSI controller,
1351 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1353 - the Fastlane Zorro III SCSI controller.
1356 tristate "Atari native SCSI support"
1357 depends on ATARI && SCSI
1358 select SCSI_SPI_ATTRS
1360 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1361 Falcon, ...) say Y to get it supported. Of course also, if you have
1362 a compatible SCSI controller (e.g. for Medusa).
1364 To compile this driver as a module, choose M here: the module will
1365 be called atari_scsi. If you also enable NVRAM support, the SCSI
1366 host's ID is taken from the setting in TT RTC NVRAM.
1368 This driver supports both styles of NCR integration into the
1369 system: the TT style (separate DMA), and the Falcon style (via
1370 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1371 in the Hades (without DMA).
1374 tristate "Macintosh NCR5380 SCSI"
1375 depends on MAC && SCSI
1376 select SCSI_SPI_ATTRS
1378 This is the NCR 5380 SCSI controller included on most of the 68030
1379 based Macintoshes. If you have one of these say Y and read the
1380 SCSI-HOWTO, available from
1381 <http://www.tldp.org/docs.html#howto>.
1384 tristate "Macintosh NCR53c9[46] SCSI"
1385 depends on MAC && SCSI
1386 select SCSI_SPI_ATTRS
1389 This is the NCR 53c9x SCSI controller found on most of the 68040
1392 To compile this driver as a module, choose M here: the module
1393 will be called mac_esp.
1396 bool "WD33C93 SCSI driver for MVME147"
1397 depends on MVME147 && SCSI=y
1398 select SCSI_SPI_ATTRS
1400 Support for the on-board SCSI controller on the Motorola MVME147
1401 single-board computer.
1404 tristate "NCR53C710 SCSI driver for MVME16x"
1405 depends on MVME16x && SCSI
1406 select SCSI_SPI_ATTRS
1408 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1409 SCSI controller chip. Almost everyone using one of these boards
1410 will want to say Y to this question.
1412 config BVME6000_SCSI
1413 tristate "NCR53C710 SCSI driver for BVME6000"
1414 depends on BVME6000 && SCSI
1415 select SCSI_SPI_ATTRS
1417 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1418 SCSI controller chip. Almost everyone using one of these boards
1419 will want to say Y to this question.
1422 tristate "Sun3 NCR5380 SCSI"
1423 depends on SUN3 && SCSI
1424 select SCSI_SPI_ATTRS
1426 This option will enable support for the OBIO (onboard io) NCR5380
1427 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1428 "Sun3" type VME scsi controllers also based on the NCR5380.
1429 General Linux information on the Sun 3 series (now discontinued)
1430 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1433 bool "Sun3x ESP SCSI"
1434 depends on SUN3X && SCSI=y
1435 select SCSI_SPI_ATTRS
1437 The ESP was an on-board SCSI controller used on Sun 3/80
1438 machines. Say Y here to compile in support for it.
1441 tristate "Sparc ESP Scsi Driver"
1442 depends on SBUS && SCSI
1443 select SCSI_SPI_ATTRS
1445 This is the driver for the Sun ESP SCSI host adapter. The ESP
1446 chipset is present in most SPARC SBUS-based computers and
1447 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1448 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1450 To compile this driver as a module, choose M here: the
1451 module will be called sun_esp.
1454 tristate "FCP host bus adapter driver for IBM mainframes"
1455 depends on S390 && QDIO && SCSI
1456 depends on SCSI_FC_ATTRS
1458 If you want to access SCSI devices attached to your IBM mainframe by
1459 means of Fibre Channel Protocol host bus adapters say Y.
1461 Supported HBAs include different models of the FICON Express and FCP
1464 For a more complete list, and for more details about setup and
1465 operation refer to the IBM publication "Device Drivers, Features, and
1466 Commands", SC33-8411.
1468 This driver is also available as a module. This module will be
1469 called zfcp. If you want to compile it as a module, say M here
1470 and read <file:Documentation/kbuild/modules.rst>.
1473 tristate "PMC SIERRA Linux MaxRAID adapter support"
1474 depends on PCI && SCSI && NET
1477 This driver supports the PMC SIERRA MaxRAID adapters.
1480 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1481 depends on PCI && SCSI
1482 select SCSI_SAS_LIBSAS
1484 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1485 based host adapters.
1488 tristate "Brocade BFA Fibre Channel Support"
1489 depends on PCI && SCSI
1490 depends on SCSI_FC_ATTRS
1492 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1494 To compile this driver as a module, choose M here. The module will
1498 tristate "virtio-scsi support"
1501 This is the virtual HBA driver for virtio. If the kernel will
1502 be used in a virtual machine, say Y or M.
1504 source "drivers/scsi/csiostor/Kconfig"
1506 source "drivers/scsi/pcmcia/Kconfig"
1508 endif # SCSI_LOWLEVEL
1510 source "drivers/scsi/device_handler/Kconfig"