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 config SCSI_LIB_KUNIT_TEST
71 tristate "KUnit tests for SCSI Mid Layer's scsi_lib" if !KUNIT_ALL_TESTS
73 default KUNIT_ALL_TESTS
75 Run SCSI Mid Layer's KUnit tests for scsi_lib.
79 comment "SCSI support type (disk, tape, CD-ROM)"
83 tristate "SCSI disk support"
85 select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY
87 If you want to use SCSI hard disks, Fibre Channel disks,
88 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
89 USB storage or the SCSI or parallel port version of
90 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
91 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
92 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
95 To compile this driver as a module, choose M here and read
96 <file:Documentation/scsi/scsi.rst>.
97 The module will be called sd_mod.
99 Do not compile this driver as a module if your root file system
100 (the one containing the directory /) is located on a SCSI disk.
101 In this case, do not compile the driver for your SCSI host adapter
102 (below) as a module either.
105 tristate "SCSI tape support"
108 If you want to use a SCSI tape drive under Linux, say Y and read the
109 SCSI-HOWTO, available from
110 <http://www.tldp.org/docs.html#howto>, and
111 <file:Documentation/scsi/st.rst> in the kernel source. This is NOT
114 To compile this driver as a module, choose M here and read
115 <file:Documentation/scsi/scsi.rst>. The module will be called st.
118 tristate "SCSI CDROM support"
119 depends on SCSI && BLK_DEV
122 If you want to use a CD or DVD drive attached to your computer
123 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
124 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
126 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
128 To compile this driver as a module, choose M here and read
129 <file:Documentation/scsi/scsi.rst>.
130 The module will be called sr_mod.
133 tristate "SCSI generic support"
136 If you want to use SCSI scanners, synthesizers or CD-writers or just
137 about anything having "SCSI" in its name other than hard disks,
138 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
139 directly, so you need some additional software which knows how to
140 talk to these devices using the SCSI protocol:
142 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
143 writer software look at Cdrtools
144 (<http://cdrtools.sourceforge.net/>)
145 and for burning a "disk at once": CDRDAO
146 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
147 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
148 For other devices, it's possible that you'll have to write the
149 driver software yourself. Please read the file
150 <file:Documentation/scsi/scsi-generic.rst> for more information.
152 To compile this driver as a module, choose M here and read
153 <file:Documentation/scsi/scsi.rst>. The module will be called sg.
158 bool "/dev/bsg support (SG v4)"
162 Saying Y here will enable generic SG (SCSI generic) v4 support
165 This option is required by UDEV to access device serial numbers, etc.
170 tristate "SCSI media changer support"
173 This is a driver for SCSI media changers. Most common devices are
174 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
175 don't need this for those tiny 6-slot cdrom changers. Media
176 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
177 If you have such hardware and want to use it with linux, say Y
178 here. Check <file:Documentation/scsi/scsi-changer.rst> for details.
180 If you want to compile this as a module ( = code which can be
181 inserted in and removed from the running kernel whenever you want),
182 say M here and read <file:Documentation/kbuild/modules.rst> and
183 <file:Documentation/scsi/scsi.rst>. The module will be called ch.o.
186 config SCSI_ENCLOSURE
187 tristate "SCSI Enclosure Support"
188 depends on SCSI && ENCLOSURE_SERVICES
189 depends on m || SCSI_SAS_ATTRS != m
191 Enclosures are devices sitting on or in SCSI backplanes that
192 manage devices. If you have a disk cage, the chances are that
193 it has an enclosure device. Selecting this option will just allow
194 certain enclosure conditions to be reported and is not required.
196 config SCSI_CONSTANTS
197 bool "Verbose SCSI error reporting (kernel size += 36K)"
200 The error messages regarding your SCSI hardware will be easier to
201 understand if you say Y here; it will enlarge your kernel by about
202 36 KB. If in doubt, say Y.
205 bool "SCSI logging facility"
208 This turns on a logging facility that can be used to debug a number
209 of SCSI related problems.
211 If you say Y here, no logging output will appear by default, but you
212 can enable logging by saying Y to "/proc file system support" and
213 "Sysctl support" below and executing the command
215 echo <bitmask> > /proc/sys/dev/scsi/logging_level
217 where <bitmask> is a four byte value representing the logging type
218 and logging level for each type of logging selected.
220 There are a number of logging types and you can find them in the
221 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
222 are also described in that file and they determine the verbosity of
223 the logging for each logging type.
225 If you say N here, it may be harder to track down some types of SCSI
226 problems. If you say Y here your kernel will be somewhat larger, but
227 there should be no noticeable performance impact as long as you have
230 config SCSI_SCAN_ASYNC
231 bool "Asynchronous SCSI scanning"
234 The SCSI subsystem can probe for devices while the rest of the
235 system continues booting, and even probe devices on different
236 busses in parallel, leading to a significant speed-up.
238 You can override this choice by specifying "scsi_mod.scan=sync"
239 or async on the kernel's command line.
241 Note that this setting also affects whether resuming from
242 system suspend will be performed asynchronously.
244 config SCSI_PROTO_TEST
245 tristate "scsi_proto.h unit tests" if !KUNIT_ALL_TESTS
246 depends on SCSI && KUNIT
247 default KUNIT_ALL_TESTS
249 menu "SCSI Transports"
252 config SCSI_SPI_ATTRS
253 tristate "Parallel SCSI (SPI) Transport Attributes"
256 If you wish to export transport-specific information about
257 each attached SCSI device to sysfs, say Y. Otherwise, say N.
260 tristate "FiberChannel Transport Attributes"
261 depends on SCSI && NET
262 select BLK_DEV_BSGLIB
265 If you wish to export transport-specific information about
266 each attached FiberChannel device to sysfs, say Y.
269 config SCSI_ISCSI_ATTRS
270 tristate "iSCSI Transport Attributes"
271 depends on SCSI && NET
272 select BLK_DEV_BSGLIB
274 If you wish to export transport-specific information about
275 each attached iSCSI device to sysfs, say Y.
278 config SCSI_SAS_ATTRS
279 tristate "SAS Transport Attributes"
281 select BLK_DEV_BSGLIB
283 If you wish to export transport-specific information about
284 each attached SAS device to sysfs, say Y.
286 source "drivers/scsi/libsas/Kconfig"
288 config SCSI_SRP_ATTRS
289 tristate "SRP Transport Attributes"
292 If you wish to export transport-specific information about
293 each attached SRP device to sysfs, say Y.
297 menuconfig SCSI_LOWLEVEL
298 bool "SCSI low-level drivers"
302 if SCSI_LOWLEVEL && SCSI
305 tristate "iSCSI Initiator over TCP/IP"
306 depends on SCSI && INET
310 select SCSI_ISCSI_ATTRS
312 The iSCSI Driver provides a host with the ability to access storage
313 through an IP network. The driver uses the iSCSI protocol to transport
314 SCSI requests and responses over a TCP/IP network between the host
315 (the "initiator") and "targets". Architecturally, the iSCSI driver
316 combines with the host's TCP/IP stack, network drivers, and Network
317 Interface Card (NIC) to provide the same functions as a SCSI or a
318 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
320 To compile this driver as a module, choose M here: the
321 module will be called iscsi_tcp.
323 The userspace component needed to initialize the driver, documentation,
324 and sample configuration files can be found here:
326 http://open-iscsi.org
328 config ISCSI_BOOT_SYSFS
329 tristate "iSCSI Boot Sysfs Interface"
332 This option enables support for exposing iSCSI boot information
333 via sysfs to userspace. If you wish to export this information,
334 say Y. Otherwise, say N.
336 source "drivers/scsi/cxgbi/Kconfig"
337 source "drivers/scsi/bnx2i/Kconfig"
338 source "drivers/scsi/bnx2fc/Kconfig"
339 source "drivers/scsi/be2iscsi/Kconfig"
340 source "drivers/scsi/cxlflash/Kconfig"
343 tristate "SGI WD93C93 SCSI Driver"
344 depends on SGI_HAS_WD93 && SCSI
346 If you have a Western Digital WD93 SCSI controller on
347 an SGI MIPS system, say Y. Otherwise, say N.
349 config BLK_DEV_3W_XXXX_RAID
350 tristate "3ware 5/6/7/8xxx ATA-RAID support"
351 depends on PCI && HAS_IOPORT && SCSI
353 3ware is the only hardware ATA-Raid product in Linux to date.
354 This card is 2,4, or 8 channel master mode support only.
355 SCSI support required!!!
357 <http://www.3ware.com/>
359 Please read the comments at the top of
360 <file:drivers/scsi/3w-xxxx.c>.
363 tristate "HP Smart Array SCSI driver"
364 depends on PCI && SCSI
365 select CHECK_SIGNATURE
366 select SCSI_SAS_ATTRS
368 This driver supports HP Smart Array Controllers (circa 2009).
369 It is a SCSI alternative to the cciss driver, which is a block
370 driver. Anyone wishing to use HP Smart Array controllers who
371 would prefer the devices be presented to linux as SCSI devices,
372 rather than as generic block devices should say Y here.
375 tristate "3ware 9xxx SATA-RAID support"
376 depends on PCI && SCSI
378 This driver supports the 9000 series 3ware SATA-RAID cards.
380 <http://www.amcc.com>
382 Please read the comments at the top of
383 <file:drivers/scsi/3w-9xxx.c>.
386 tristate "3ware 97xx SAS/SATA-RAID support"
387 depends on PCI && SCSI
389 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
393 Please read the comments at the top of
394 <file:drivers/scsi/3w-sas.c>.
397 tristate "ACARD SCSI support"
398 depends on PCI && HAS_IOPORT && SCSI
400 This driver supports the ACARD SCSI host adapter.
401 Support Chip <ATP870 ATP876 ATP880 ATP885>
402 To compile this driver as a module, choose M here: the
403 module will be called atp870u.
406 tristate "Adaptec AHA152X/2825 support"
407 depends on ISA && SCSI
408 select SCSI_SPI_ATTRS
409 select CHECK_SIGNATURE
411 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
412 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
413 must be manually specified in this case.
415 It is explained in section 3.3 of the SCSI-HOWTO, available from
416 <http://www.tldp.org/docs.html#howto>. You might also want to
417 read the file <file:Documentation/scsi/aha152x.rst>.
419 To compile this driver as a module, choose M here: the
420 module will be called aha152x.
423 tristate "Adaptec AHA1542 support"
424 depends on ISA && SCSI && ISA_DMA_API
426 This is support for a SCSI host adapter. It is explained in section
427 3.4 of the SCSI-HOWTO, available from
428 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
429 purchased by Adaptec, and some former Trantor products are being
430 sold under the Adaptec name. If it doesn't work out of the box, you
431 may have to change some settings in <file:drivers/scsi/aha1542.h>.
433 To compile this driver as a module, choose M here: the
434 module will be called aha1542.
437 tristate "Adaptec AHA1740 support"
438 depends on EISA && SCSI
440 This is support for a SCSI host adapter. It is explained in section
441 3.5 of the SCSI-HOWTO, available from
442 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
443 of the box, you may have to change some settings in
444 <file:drivers/scsi/aha1740.h>.
446 To compile this driver as a module, choose M here: the
447 module will be called aha1740.
450 tristate "Adaptec AACRAID support"
451 depends on SCSI && PCI
453 This driver supports a variety of Dell, HP, Adaptec, IBM and
454 ICP storage products. For a list of supported products, refer
455 to <file:Documentation/scsi/aacraid.rst>.
457 To compile this driver as a module, choose M here: the module
458 will be called aacraid.
461 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
462 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
463 source "drivers/scsi/aic94xx/Kconfig"
464 source "drivers/scsi/hisi_sas/Kconfig"
465 source "drivers/scsi/mvsas/Kconfig"
468 tristate "Marvell UMI driver"
469 depends on SCSI && PCI
471 Module for Marvell Universal Message Interface(UMI) driver
473 To compile this driver as a module, choose M here: the
474 module will be called mvumi.
477 tristate "AdvanSys SCSI support"
479 depends on (ISA || EISA || PCI) && HAS_IOPORT
480 depends on ISA_DMA_API || !ISA
482 This is a driver for all SCSI host adapters manufactured by
483 AdvanSys. It is documented in the kernel source in
484 <file:drivers/scsi/advansys.c>.
486 To compile this driver as a module, choose M here: the
487 module will be called advansys.
490 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
491 depends on PCI && SCSI
493 This driver supports all of ARECA's SATA/SAS RAID controller cards.
494 This is an ARECA-maintained driver by Erich Chen.
495 If you have any problems, please mail to: <erich@areca.com.tw>.
496 Areca supports Linux RAID config tools.
497 Please link <http://www.areca.com.tw>
499 To compile this driver as a module, choose M here: the
500 module will be called arcmsr (modprobe arcmsr).
502 source "drivers/scsi/esas2r/Kconfig"
503 source "drivers/scsi/megaraid/Kconfig.megaraid"
504 source "drivers/scsi/mpt3sas/Kconfig"
505 source "drivers/scsi/mpi3mr/Kconfig"
506 source "drivers/scsi/smartpqi/Kconfig"
509 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
510 depends on SCSI && PCI
512 This option enables support for HighPoint RocketRAID 3xxx/4xxx
515 To compile this driver as a module, choose M here; the module
516 will be called hptiop. If unsure, say N.
519 tristate "BusLogic SCSI support"
520 depends on SCSI && PCI && HAS_IOPORT
522 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
523 Adapters. Consult the SCSI-HOWTO, available from
524 <http://www.tldp.org/docs.html#howto>, and the files
525 <file:Documentation/scsi/BusLogic.rst> and
526 <file:Documentation/scsi/FlashPoint.rst> for more information.
527 Note that support for FlashPoint is only available for 32-bit
530 To compile this driver as a module, choose M here: the
531 module will be called BusLogic.
533 config SCSI_FLASHPOINT
534 bool "FlashPoint support"
535 depends on SCSI_BUSLOGIC && PCI && HAS_IOPORT
537 This option allows you to add FlashPoint support to the
538 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
539 substantial, so users of MultiMaster Host Adapters may not
543 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
547 This driver adds support for the Mylex DAC960, AcceleRAID, and
548 eXtremeRAID PCI RAID controllers. This driver supports the
549 older, block based interface.
550 This driver is a reimplementation of the original DAC960
551 driver. If you have used the DAC960 driver you should enable
554 To compile this driver as a module, choose M here: the
555 module will be called myrb.
558 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
560 depends on !CPU_BIG_ENDIAN || COMPILE_TEST
563 This driver adds support for the Mylex DAC960, AcceleRAID, and
564 eXtremeRAID PCI RAID controllers. This driver supports the
565 newer, SCSI-based interface only.
566 This driver is a reimplementation of the original DAC960
567 driver. If you have used the DAC960 driver you should enable
570 To compile this driver as a module, choose M here: the
571 module will be called myrs.
574 tristate "VMware PVSCSI driver support"
575 depends on PCI && SCSI && X86
577 This driver supports VMware's para virtualized SCSI HBA.
578 To compile this driver as a module, choose M here: the
579 module will be called vmw_pvscsi.
581 config XEN_SCSI_FRONTEND
582 tristate "XEN SCSI frontend driver"
583 depends on SCSI && XEN
584 select XEN_XENBUS_FRONTEND
586 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
587 within another guest OS (usually Dom0).
588 Only needed if the kernel is running in a XEN guest and generic
589 SCSI access to a device is needed.
591 config HYPERV_STORAGE
592 tristate "Microsoft Hyper-V virtual storage driver"
593 depends on SCSI && HYPERV
594 depends on m || SCSI_FC_ATTRS != m
597 Select this option to enable the Hyper-V virtual storage driver.
600 tristate "LibFC module"
601 depends on SCSI_FC_ATTRS
604 Fibre Channel library module
607 tristate "LibFCoE module"
610 Library for Fibre Channel over Ethernet module
613 tristate "FCoE module"
617 Fibre Channel over Ethernet module
620 tristate "Cisco FNIC Driver"
621 depends on PCI && X86
624 This is support for the Cisco PCI-Express FCoE HBA.
626 To compile this driver as a module, choose M here and read
627 <file:Documentation/scsi/scsi.rst>.
628 The module will be called fnic.
631 tristate "Cisco SNIC Driver"
632 depends on PCI && SCSI
634 This is support for the Cisco PCI-Express SCSI HBA.
636 To compile this driver as a module, choose M here and read
637 <file:Documentation/scsi/scsi.rst>.
638 The module will be called snic.
640 config SCSI_SNIC_DEBUG_FS
641 bool "Cisco SNIC Driver Debugfs Support"
642 depends on SCSI_SNIC && DEBUG_FS
644 This enables to list debugging information from SNIC Driver
645 available via debugfs file system
648 tristate "DMX3191D SCSI support"
649 depends on PCI && HAS_IOPORT && SCSI
650 select SCSI_SPI_ATTRS
652 This is support for Domex DMX3191D SCSI Host Adapters.
654 To compile this driver as a module, choose M here: the
655 module will be called dmx3191d.
661 config SCSI_FDOMAIN_PCI
662 tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
663 depends on PCI && HAS_IOPORT && SCSI
666 This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
667 and other adapters with PCI bus based on the Future Domain chipsets
670 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
671 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
672 controller support"). This Future Domain driver works with the older
673 Adaptec AHA-2920A boards with a Future Domain chip on them.
675 To compile this driver as a module, choose M here: the
676 module will be called fdomain_pci.
678 config SCSI_FDOMAIN_ISA
679 tristate "Future Domain 16xx ISA SCSI support"
680 depends on ISA && SCSI
681 select CHECK_SIGNATURE
684 This is support for Future Domain's 16-bit SCSI host adapters
685 (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
686 with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
687 ISA-250MG; and at least one IBM board).
689 To compile this driver as a module, choose M here: the
690 module will be called fdomain_isa.
693 tristate "Intel(R) C600 Series Chipset SAS Controller"
694 depends on PCI && SCSI
696 select SCSI_SAS_LIBSAS
698 This driver supports the 6Gb/s SAS capabilities of the storage
699 control unit found in the Intel(R) C600 series chipset.
701 config SCSI_GENERIC_NCR5380
702 tristate "Generic NCR5380/53c400 SCSI ISA card support"
703 depends on ISA && SCSI && HAS_IOPORT_MAP
704 select SCSI_SPI_ATTRS
706 This is a driver for old ISA card SCSI controllers based on a
707 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
708 Most boards such as the Trantor T130 fit this category, as do
709 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
711 To compile this driver as a module, choose M here: the
712 module will be called g_NCR5380.
715 tristate "IBM ServeRAID support"
716 depends on PCI && HAS_IOPORT && SCSI
718 This is support for the IBM ServeRAID hardware RAID controllers.
719 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
720 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
721 for more information. If this driver does not work correctly
722 without modification please contact the author by email at
723 <ipslinux@adaptec.com>.
725 To compile this driver as a module, choose M here: the
726 module will be called ips.
729 tristate "IBM Virtual SCSI support"
730 depends on PPC_PSERIES
731 select SCSI_SRP_ATTRS
733 This is the IBM POWER Virtual SCSI Client
735 To compile this driver as a module, choose M here: the
736 module will be called ibmvscsi.
738 config SCSI_IBMVSCSIS
739 tristate "IBM Virtual SCSI Server support"
740 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
742 This is the IBM POWER Virtual SCSI Target Server
743 This driver uses the SRP protocol for communication between servers
744 guest and/or the host that run on the same server.
745 More information on VSCSI protocol can be found at www.power.org
747 The userspace configuration needed to initialize the driver can be
750 https://github.com/powervm/ibmvscsis/wiki/Configuration
752 To compile this driver as a module, choose M here: the
753 module will be called ibmvscsis.
756 tristate "IBM Virtual FC support"
757 depends on PPC_PSERIES && SCSI
758 depends on SCSI_FC_ATTRS
760 This is the IBM POWER Virtual FC Client
762 To compile this driver as a module, choose M here: the
763 module will be called ibmvfc.
765 config SCSI_IBMVFC_TRACE
766 bool "enable driver internal trace"
767 depends on SCSI_IBMVFC
770 If you say Y here, the driver will trace all commands issued
771 to the adapter. Performance impact is minimal. Trace can be
772 dumped using /sys/class/scsi_host/hostXX/trace.
775 tristate "Initio 9100U(W) support"
776 depends on PCI && HAS_IOPORT && SCSI
778 This is support for the Initio 91XXU(W) SCSI host adapter. Please
779 read the SCSI-HOWTO, available from
780 <http://www.tldp.org/docs.html#howto>.
782 To compile this driver as a module, choose M here: the
783 module will be called initio.
786 tristate "Initio INI-A100U2W support"
787 depends on PCI && HAS_IOPORT && SCSI
789 This is support for the Initio INI-A100U2W SCSI host adapter.
790 Please read the SCSI-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>.
793 To compile this driver as a module, choose M here: the
794 module will be called a100u2w.
797 tristate "IOMEGA parallel port (ppa - older drives)"
798 depends on SCSI && PARPORT_PC
799 depends on HAS_IOPORT
801 This driver supports older versions of IOMEGA's parallel port ZIP
802 drive (a 100 MB removable media device).
804 Note that you can say N here if you have the SCSI version of the ZIP
805 drive: it will be supported automatically if you said Y to the
806 generic "SCSI disk support", above.
808 If you have the ZIP Plus drive or a more recent parallel port ZIP
809 drive (if the supplied cable with the drive is labeled "AutoDetect")
810 then you should say N here and Y to "IOMEGA parallel port (imm -
811 newer drives)", below.
813 For more information about this driver and how to use it you should
814 read the file <file:Documentation/scsi/ppa.rst>. You should also read
815 the SCSI-HOWTO, which is available from
816 <http://www.tldp.org/docs.html#howto>. If you use this driver,
817 you will still be able to use the parallel port for other tasks,
818 such as a printer; it is safe to compile both drivers into the
821 To compile this driver as a module, choose M here: the
822 module will be called ppa.
825 tristate "IOMEGA parallel port (imm - newer drives)"
826 depends on SCSI && PARPORT_PC
828 This driver supports newer versions of IOMEGA's parallel port ZIP
829 drive (a 100 MB removable media device).
831 Note that you can say N here if you have the SCSI version of the ZIP
832 drive: it will be supported automatically if you said Y to the
833 generic "SCSI disk support", above.
835 If you have the ZIP Plus drive or a more recent parallel port ZIP
836 drive (if the supplied cable with the drive is labeled "AutoDetect")
837 then you should say Y here; if you have an older ZIP drive, say N
838 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
840 For more information about this driver and how to use it you should
841 read the file <file:Documentation/scsi/ppa.rst>. You should also read
842 the SCSI-HOWTO, which is available from
843 <http://www.tldp.org/docs.html#howto>. If you use this driver,
844 you will still be able to use the parallel port for other tasks,
845 such as a printer; it is safe to compile both drivers into the
848 To compile this driver as a module, choose M here: the
849 module will be called imm.
851 config SCSI_IZIP_SLOW_CTR
852 bool "ppa/imm option - Assume slow parport control register"
853 depends on SCSI_PPA || SCSI_IMM
855 Some parallel ports are known to have excessive delays between
856 changing the parallel port control register and good data being
857 available on the parallel port data/status register. This option
858 forces a small delay (1.0 usec to be exact) after changing the
859 control register to let things settle out. Enabling this option may
860 result in a big drop in performance but some very old parallel ports
861 (found in 386 vintage machines) will not work properly.
863 Generally, saying N is fine.
866 tristate "HP Lasi SCSI support for 53c700/710"
867 depends on GSC && SCSI
868 select SCSI_SPI_ATTRS
870 This is a driver for the SCSI controller in the Lasi chip found in
871 many PA-RISC workstations & servers. If you do not know whether you
872 have a Lasi chip, it is safe to say "Y" here.
874 config SCSI_SNI_53C710
875 tristate "SNI RM SCSI support for 53c710"
876 depends on SNI_RM && SCSI
877 select SCSI_SPI_ATTRS
878 select 53C700_LE_ON_BE
880 This is a driver for the onboard SCSI controller found in older
881 SNI RM workstations & servers.
883 config 53C700_LE_ON_BE
885 depends on SCSI_LASI700 || SCSI_SNI_53C710
889 tristate "Promise SuperTrak EX Series support"
890 depends on PCI && SCSI
892 This driver supports Promise SuperTrak EX series storage controllers.
894 Promise provides Linux RAID configuration utility for these
895 controllers. Please visit <http://www.promise.com> to download.
897 To compile this driver as a module, choose M here: the
898 module will be called stex.
902 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
905 config SCSI_SYM53C8XX_2
906 tristate "SYM53C8XX Version 2 SCSI support"
907 depends on PCI && SCSI
908 select SCSI_SPI_ATTRS
910 This driver supports the whole NCR53C8XX/SYM53C8XX family of
911 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
912 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
913 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
914 controllers; you need to use the Fusion MPT driver for that.
916 Please read <file:Documentation/scsi/sym53c8xx_2.rst> for more
919 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
920 int "DMA addressing mode"
921 depends on SCSI_SYM53C8XX_2
924 This option only applies to PCI-SCSI chips that are PCI DAC
925 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
927 When set to 0, the driver will program the chip to only perform
928 32-bit DMA. When set to 1, the chip will be able to perform DMA
929 to addresses up to 1TB. When set to 2, the driver supports the
930 full 64-bit DMA address range, but can only address 16 segments
931 of 4 GB each. This limits the total addressable range to 64 GB.
933 Most machines with less than 4GB of memory should use a setting
934 of 0 for best performance. If your machine has 4GB of memory
935 or more, you should set this option to 1 (the default).
937 The still experimental value 2 (64 bit DMA addressing with 16
938 x 4GB segments limitation) can be used on systems that require
939 PCI address bits past bit 39 to be set for the addressing of
940 memory using PCI DAC cycles.
942 config SCSI_SYM53C8XX_DEFAULT_TAGS
943 int "Default tagged command queue depth"
944 depends on SCSI_SYM53C8XX_2
947 This is the default value of the command queue depth the
948 driver will announce to the generic SCSI layer for devices
949 that support tagged command queueing. This value can be changed
950 from the boot command line. This is a soft limit that cannot
951 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
953 config SCSI_SYM53C8XX_MAX_TAGS
954 int "Maximum number of queued commands"
955 depends on SCSI_SYM53C8XX_2
958 This option allows you to specify the maximum number of commands
959 that can be queued to any device, when tagged command queuing is
960 possible. The driver supports up to 256 queued commands per device.
961 This value is used as a compiled-in hard limit.
963 config SCSI_SYM53C8XX_MMIO
964 bool "Use memory mapped IO"
965 depends on SCSI_SYM53C8XX_2
968 Memory mapped IO is faster than Port IO. Most people should
969 answer Y here, but some machines may have problems. If you have
970 to answer N here, please report the problem to the maintainer.
973 tristate "IBM Power Linux RAID adapter support"
974 depends on PCI && SCSI
979 This driver supports the IBM Power Linux family RAID adapters.
980 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
981 as IBM iSeries 5702, 5703, 5709, and 570A.
983 config SCSI_IPR_TRACE
984 bool "enable driver internal trace"
988 If you say Y here, the driver will trace all commands issued
989 to the adapter. Performance impact is minimal. Trace can be
990 dumped using /sys/bus/class/scsi_host/hostXX/trace.
993 bool "enable adapter dump support"
997 If you say Y here, the driver will support adapter crash dump.
998 If you enable this support, the iprdump daemon can be used
999 to capture adapter failure analysis information.
1002 tristate "Zalon SCSI support"
1003 depends on GSC && SCSI
1004 select SCSI_SPI_ATTRS
1006 The Zalon is a GSC/HSC bus interface chip that sits between the
1007 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1008 C110, J200, J210 and some D, K & R-class machines. It's also
1009 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1010 Say Y here if you have one of these machines or cards.
1012 config SCSI_NCR53C8XX_DEFAULT_TAGS
1013 int "default tagged command queue depth"
1014 depends on SCSI_ZALON
1017 "Tagged command queuing" is a feature of SCSI-2 which improves
1018 performance: the host adapter can send several SCSI commands to a
1019 device's queue even if previous commands haven't finished yet.
1020 Because the device is intelligent, it can optimize its operations
1021 (like head positioning) based on its own request queue. Some SCSI
1022 devices don't implement this properly; if you want to disable this
1023 feature, enter 0 or 1 here (it doesn't matter which).
1025 The default value is 8 and should be supported by most hard disks.
1026 This value can be overridden from the boot command line using the
1027 'tags' option as follows (example):
1028 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1029 4, set queue depth to 16 for target 2 and target 3 on controller 0
1030 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1032 The normal answer therefore is to go with the default 8 and to use
1033 a boot command line option for devices that need to use a different
1034 command queue depth.
1036 There is no safe option other than using good SCSI devices.
1038 config SCSI_NCR53C8XX_MAX_TAGS
1039 int "maximum number of queued commands"
1040 depends on SCSI_ZALON
1043 This option allows you to specify the maximum number of commands
1044 that can be queued to any device, when tagged command queuing is
1045 possible. The default value is 32. Minimum is 2, maximum is 64.
1046 Modern hard disks are able to support 64 tags and even more, but
1047 do not seem to be faster when more than 32 tags are being used.
1049 So, the normal answer here is to go with the default value 32 unless
1050 you are using very large hard disks with large cache (>= 1 MB) that
1051 are able to take advantage of more than 32 tagged commands.
1053 There is no safe option and the default answer is recommended.
1055 config SCSI_NCR53C8XX_SYNC
1056 int "synchronous transfers frequency in MHz"
1057 depends on SCSI_ZALON
1060 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1061 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1062 are respectively the maximum data transfer rates in mega-transfers
1063 per second for each class. For example, a FAST-20 Wide 16 device is
1064 able to transfer data at 20 million 16 bit packets per second for a
1065 total rate of 40 MB/s.
1067 You may specify 0 if you want to only use asynchronous data
1068 transfers. This is the safest and slowest option. Otherwise, specify
1069 a value between 5 and 80, depending on the capability of your SCSI
1070 controller. The higher the number, the faster the data transfer.
1071 Note that 80 should normally be ok since the driver decreases the
1072 value automatically according to the controller's capabilities.
1074 Your answer to this question is ignored for controllers with NVRAM,
1075 since the driver will get this information from the user set-up. It
1076 also can be overridden using a boot setup option, as follows
1077 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1078 for FAST-20 synchronous data transfer (20 mega-transfers per
1081 The normal answer therefore is not to go with the default but to
1082 select the maximum value 80 allowing the driver to use the maximum
1083 value supported by each controller. If this causes problems with
1084 your SCSI devices, you should come back and decrease the value.
1086 There is no safe option other than using good cabling, right
1087 terminations and SCSI conformant devices.
1089 config SCSI_NCR53C8XX_NO_DISCONNECT
1090 bool "not allow targets to disconnect"
1091 depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1093 This option is only provided for safety if you suspect some SCSI
1094 device of yours to not support properly the target-disconnect
1095 feature. In that case, you would say Y here. In general however, to
1096 not allow targets to disconnect is not reasonable if there is more
1097 than 1 device on a SCSI bus. The normal answer therefore is N.
1099 config SCSI_QLOGIC_FAS
1100 tristate "Qlogic FAS SCSI support"
1101 depends on ISA && SCSI
1103 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1104 FastSCSI! cards as well as any other card based on the FASXX chip
1105 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1107 This driver does NOT support the PCI versions of these cards. The
1108 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1109 SCSI support"), below.
1111 Information about this driver is contained in
1112 <file:Documentation/scsi/qlogicfas.rst>. You should also read the
1113 SCSI-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>.
1116 To compile this driver as a module, choose M here: the
1117 module will be called qlogicfas.
1119 config SCSI_QLOGIC_1280
1120 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1121 depends on PCI && SCSI
1123 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1125 To compile this driver as a module, choose M here: the
1126 module will be called qla1280.
1128 config SCSI_QLOGICPTI
1129 tristate "PTI Qlogic, ISP Driver"
1130 depends on SBUS && SCSI
1132 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1133 controllers are known under Solaris as qpti and in the openprom as
1134 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1135 driven by a different driver.
1137 To compile this driver as a module, choose M here: the
1138 module will be called qlogicpti.
1140 source "drivers/scsi/qla2xxx/Kconfig"
1141 source "drivers/scsi/qla4xxx/Kconfig"
1142 source "drivers/scsi/qedi/Kconfig"
1143 source "drivers/scsi/qedf/Kconfig"
1146 tristate "Emulex LightPulse Fibre Channel Support"
1147 depends on PCI && SCSI
1149 depends on SCSI_FC_ATTRS
1150 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1151 depends on NVME_FC || NVME_FC=n
1155 This lpfc driver supports the Emulex LightPulse
1156 Family of Fibre Channel PCI host adapters.
1158 config SCSI_LPFC_DEBUG_FS
1159 bool "Emulex LightPulse Fibre Channel debugfs Support"
1160 depends on SCSI_LPFC && DEBUG_FS
1162 This makes debugging information from the lpfc driver
1163 available via the debugfs filesystem.
1165 source "drivers/scsi/elx/Kconfig"
1168 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1169 depends on EISA && SCSI
1170 select SCSI_SPI_ATTRS
1172 This driver is for NCR53c710 based SCSI host adapters.
1174 It currently supports Compaq EISA cards.
1177 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1178 depends on PCI && HAS_IOPORT && SCSI
1179 select SCSI_SPI_ATTRS
1181 This driver supports PCI SCSI host adapters based on the ASIC
1182 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1184 This driver works, but is still in experimental status. So better
1185 have a bootable disk and a backup in case of emergency.
1187 Documentation can be found in <file:Documentation/scsi/dc395x.rst>.
1189 To compile this driver as a module, choose M here: the
1190 module will be called dc395x.
1192 config SCSI_AM53C974
1193 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1194 depends on PCI && SCSI
1195 select SCSI_SPI_ATTRS
1197 This driver supports PCI SCSI host adapters based on the Am53C974A
1198 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1199 PCscsi/PCnet (Am53/79C974) solutions.
1200 This is a new implementation base on the generic esp_scsi driver.
1202 Note that this driver does NOT support Tekram DC390W/U/F, which are
1203 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1205 To compile this driver as a module, choose M here: the
1206 module will be called am53c974.
1209 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1210 depends on PCI && SCSI && !64BIT && HAS_IOPORT
1212 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1213 SCSI host adapter. Please read the SCSI-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>.
1216 To compile this driver as a module, choose M here: the
1217 module will be called nsp32.
1220 tristate "Western Digital WD7193/7197/7296 support"
1221 depends on PCI && SCSI
1224 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1225 SCSI controllers (based on WD33C296A chip).
1228 tristate "SCSI debugging host and device simulator"
1232 This pseudo driver simulates one or more hosts (SCSI initiators),
1233 each with one or more targets, each with one or more logical units.
1234 Defaults to one of each, creating a small RAM disk device. Many
1235 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1236 directory can be tweaked at run time.
1237 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1238 Mainly used for testing and best as a module. If unsure, say N.
1241 tristate "MESH (Power Mac internal SCSI) support"
1242 depends on PPC32 && PPC_PMAC && SCSI
1244 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1245 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1246 other Power Macintoshes do). Say Y to include support for this SCSI
1249 To compile this driver as a module, choose M here: the
1250 module will be called mesh.
1252 config SCSI_MESH_SYNC_RATE
1253 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1254 depends on SCSI_MESH
1257 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1258 drives a bus which is entirely internal to the machine (such as the
1259 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1260 operation at up to 10 MB/s. On machines where the SCSI bus
1261 controlled by the MESH can have external devices connected, it is
1262 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1263 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1264 to disable synchronous operation.
1266 config SCSI_MESH_RESET_DELAY_MS
1267 int "initial bus reset delay (ms) (0 = no reset)"
1268 depends on SCSI_MESH
1271 config SCSI_MAC53C94
1272 tristate "53C94 (Power Mac external SCSI) support"
1273 depends on PPC32 && PPC_PMAC && SCSI
1275 On Power Macintoshes (and clones) with two SCSI buses, the external
1276 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1277 machines which only have one SCSI bus, such as the 7200, also use
1278 the 53C94. Say Y to include support for the 53C94.
1280 To compile this driver as a module, choose M here: the
1281 module will be called mac53c94.
1283 source "drivers/scsi/arm/Kconfig"
1286 bool "MIPS JAZZ FAS216 SCSI support"
1287 depends on MACH_JAZZ && SCSI=y
1288 select SCSI_SPI_ATTRS
1290 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1291 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1295 tristate "A3000 WD33C93A support"
1296 depends on AMIGA && SCSI
1298 If you have an Amiga 3000 and have SCSI devices connected to the
1299 built-in SCSI controller, say Y. Otherwise, say N.
1301 To compile this driver as a module, choose M here: the
1302 module will be called a3000.
1305 tristate "A2091/A590 WD33C93A support"
1306 depends on ZORRO && SCSI
1308 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1311 To compile this driver as a module, choose M here: the
1312 module will be called a2091.
1315 tristate "GVP Series II WD33C93A support"
1316 depends on ZORRO && SCSI
1318 If you have a Great Valley Products Series II SCSI controller,
1319 answer Y. Also say Y if you have a later model of GVP SCSI
1320 controller (such as the GVP A4008 or a Combo board). Otherwise,
1321 answer N. This driver does NOT work for the T-Rex series of
1322 accelerators from TekMagic and GVP-M.
1324 To compile this driver as a module, choose M here: the
1325 module will be called gvp11.
1328 tristate "A4000T NCR53c710 SCSI support"
1329 depends on AMIGA && SCSI
1330 select SCSI_SPI_ATTRS
1332 If you have an Amiga 4000T and have SCSI devices connected to the
1333 built-in SCSI controller, say Y. Otherwise, say N.
1335 To compile this driver as a module, choose M here: the
1336 module will be called a4000t.
1338 config SCSI_ZORRO7XX
1339 tristate "Zorro NCR53c710 SCSI support"
1340 depends on ZORRO && SCSI
1341 select SCSI_SPI_ATTRS
1343 Support for various NCR53c710-based SCSI controllers on Zorro
1344 expansion boards for the Amiga.
1346 - the Amiga 4091 Zorro III SCSI-2 controller,
1347 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1349 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1350 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1351 accelerator card for the Amiga 1200,
1352 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1354 config SCSI_ZORRO_ESP
1355 tristate "Zorro ESP SCSI support"
1356 depends on ZORRO && SCSI
1357 select SCSI_SPI_ATTRS
1360 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1361 expansion boards for the Amiga.
1363 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1364 - the Phase5 Blizzard 2060 SCSI controller,
1365 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1367 - the Fastlane Zorro III SCSI controller.
1370 tristate "Atari native SCSI support"
1371 depends on ATARI && SCSI
1372 select SCSI_SPI_ATTRS
1374 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1375 Falcon, ...) say Y to get it supported. Of course also, if you have
1376 a compatible SCSI controller (e.g. for Medusa).
1378 To compile this driver as a module, choose M here: the module will
1379 be called atari_scsi. If you also enable NVRAM support, the SCSI
1380 host's ID is taken from the setting in TT RTC NVRAM.
1382 This driver supports both styles of NCR integration into the
1383 system: the TT style (separate DMA), and the Falcon style (via
1384 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1385 in the Hades (without DMA).
1388 tristate "Macintosh NCR5380 SCSI"
1389 depends on MAC && SCSI
1390 select SCSI_SPI_ATTRS
1392 This is the NCR 5380 SCSI controller included on most of the 68030
1393 based Macintoshes. If you have one of these say Y and read the
1394 SCSI-HOWTO, available from
1395 <http://www.tldp.org/docs.html#howto>.
1398 tristate "Macintosh NCR53c9[46] SCSI"
1399 depends on MAC && SCSI
1400 select SCSI_SPI_ATTRS
1403 This is the NCR 53c9x SCSI controller found on most of the 68040
1406 To compile this driver as a module, choose M here: the module
1407 will be called mac_esp.
1410 bool "WD33C93 SCSI driver for MVME147"
1411 depends on MVME147 && SCSI=y
1412 select SCSI_SPI_ATTRS
1414 Support for the on-board SCSI controller on the Motorola MVME147
1415 single-board computer.
1418 tristate "NCR53C710 SCSI driver for MVME16x"
1419 depends on MVME16x && SCSI
1420 select SCSI_SPI_ATTRS
1422 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1423 SCSI controller chip. Almost everyone using one of these boards
1424 will want to say Y to this question.
1426 config BVME6000_SCSI
1427 tristate "NCR53C710 SCSI driver for BVME6000"
1428 depends on BVME6000 && SCSI
1429 select SCSI_SPI_ATTRS
1431 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1432 SCSI controller chip. Almost everyone using one of these boards
1433 will want to say Y to this question.
1436 tristate "Sun3 NCR5380 SCSI"
1437 depends on SUN3 && SCSI
1438 select SCSI_SPI_ATTRS
1440 This option will enable support for the OBIO (onboard io) NCR5380
1441 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1442 "Sun3" type VME scsi controllers also based on the NCR5380.
1443 General Linux information on the Sun 3 series (now discontinued)
1444 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1447 bool "Sun3x ESP SCSI"
1448 depends on SUN3X && SCSI=y
1449 select SCSI_SPI_ATTRS
1451 The ESP was an on-board SCSI controller used on Sun 3/80
1452 machines. Say Y here to compile in support for it.
1455 tristate "Sparc ESP Scsi Driver"
1456 depends on SBUS && SCSI
1457 select SCSI_SPI_ATTRS
1459 This is the driver for the Sun ESP SCSI host adapter. The ESP
1460 chipset is present in most SPARC SBUS-based computers and
1461 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1462 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1464 To compile this driver as a module, choose M here: the
1465 module will be called sun_esp.
1468 tristate "FCP host bus adapter driver for IBM mainframes"
1469 depends on S390 && QDIO && SCSI
1470 depends on SCSI_FC_ATTRS
1472 If you want to access SCSI devices attached to your IBM mainframe by
1473 means of Fibre Channel Protocol host bus adapters say Y.
1475 Supported HBAs include different models of the FICON Express and FCP
1478 For a more complete list, and for more details about setup and
1479 operation refer to the IBM publication "Device Drivers, Features, and
1480 Commands", SC33-8411.
1482 This driver is also available as a module. This module will be
1483 called zfcp. If you want to compile it as a module, say M here
1484 and read <file:Documentation/kbuild/modules.rst>.
1487 tristate "PMC SIERRA Linux MaxRAID adapter support"
1488 depends on PCI && SCSI && NET
1491 This driver supports the PMC SIERRA MaxRAID adapters.
1494 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1495 depends on PCI && SCSI
1496 select SCSI_SAS_LIBSAS
1498 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1499 based host adapters.
1502 tristate "Brocade BFA Fibre Channel Support"
1503 depends on PCI && SCSI
1504 depends on SCSI_FC_ATTRS
1506 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1508 To compile this driver as a module, choose M here. The module will
1512 tristate "virtio-scsi support"
1515 This is the virtual HBA driver for virtio. If the kernel will
1516 be used in a virtual machine, say Y or M.
1518 source "drivers/scsi/csiostor/Kconfig"
1520 source "drivers/scsi/pcmcia/Kconfig"
1522 endif # SCSI_LOWLEVEL
1524 source "drivers/scsi/device_handler/Kconfig"