1 menu "SCSI device support"
5 default y if SCSI=n || SCSI=y
9 tristate "RAID Transport Class"
17 tristate "SCSI device support"
19 select SCSI_DMA if HAS_DMA
21 select BLK_SCSI_REQUEST
23 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
24 any other SCSI device under Linux, say Y and make sure that you know
25 the name of your SCSI host adapter (the card inside your computer
26 that "speaks" the SCSI protocol, also called SCSI controller),
27 because you will be asked for it.
29 You also need to say Y here if you have a device which speaks
30 the SCSI protocol. Examples of this include the parallel port
31 version of the IOMEGA ZIP drive, USB storage devices, Fibre
32 Channel, and FireWire storage.
34 To compile this driver as a module, choose M here and read
35 <file:Documentation/scsi/scsi.txt>.
36 The module will be called scsi_mod.
38 However, do not compile this as a module if your root file system
39 (the one containing the directory /) is located on a SCSI device.
50 config SCSI_MQ_DEFAULT
51 bool "SCSI: use blk-mq I/O path by default"
54 This option enables the new blk-mq based I/O path for SCSI
55 devices by default. With the option the scsi_mod.use_blk_mq
56 module/boot option defaults to Y, without it to N, but it can
57 still be overridden either way.
62 bool "legacy /proc/scsi/ support"
63 depends on SCSI && PROC_FS
66 This option enables support for the various files in
67 /proc/scsi. In Linux 2.6 this has been superseded by
68 files in sysfs but many legacy applications rely on this.
72 comment "SCSI support type (disk, tape, CD-ROM)"
76 tristate "SCSI disk support"
79 If you want to use SCSI hard disks, Fibre Channel disks,
80 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
81 USB storage or the SCSI or parallel port version of
82 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
83 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
84 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
87 To compile this driver as a module, choose M here and read
88 <file:Documentation/scsi/scsi.txt>.
89 The module will be called sd_mod.
91 Do not compile this driver as a module if your root file system
92 (the one containing the directory /) is located on a SCSI disk.
93 In this case, do not compile the driver for your SCSI host adapter
94 (below) as a module either.
97 tristate "SCSI tape support"
100 If you want to use a SCSI tape drive under Linux, say Y and read the
101 SCSI-HOWTO, available from
102 <http://www.tldp.org/docs.html#howto>, and
103 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
106 To compile this driver as a module, choose M here and read
107 <file:Documentation/scsi/scsi.txt>. The module will be called st.
110 tristate "SCSI OnStream SC-x0 tape support"
113 The OnStream SC-x0 SCSI tape drives cannot be driven by the
114 standard st driver, but instead need this special osst driver and
115 use the /dev/osstX char device nodes (major 206). Via usb-storage,
116 you may be able to drive the USB-x0 and DI-x0 drives as well.
117 Note that there is also a second generation of OnStream
118 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
119 tapes (QIC-157) and can be driven by the standard driver st.
120 For more information, you may have a look at the SCSI-HOWTO
121 <http://www.tldp.org/docs.html#howto> and
122 <file:Documentation/scsi/osst.txt> in the kernel source.
123 More info on the OnStream driver may be found on
124 <http://sourceforge.net/projects/osst/>
125 Please also have a look at the standard st docu, as most of it
126 applies to osst as well.
128 To compile this driver as a module, choose M here and read
129 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
132 tristate "SCSI CDROM support"
133 depends on SCSI && BLK_DEV
136 If you want to use a CD or DVD drive attached to your computer
137 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
138 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
140 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
142 To compile this driver as a module, choose M here and read
143 <file:Documentation/scsi/scsi.txt>.
144 The module will be called sr_mod.
146 config BLK_DEV_SR_VENDOR
147 bool "Enable vendor-specific extensions (for SCSI CDROM)"
148 depends on BLK_DEV_SR
150 This enables the usage of vendor specific SCSI commands. This is
151 required to support multisession CDs with old NEC/TOSHIBA cdrom
152 drives (and HP Writers). If you have such a drive and get the first
153 session only, try saying Y here; everybody else says N.
156 tristate "SCSI generic support"
159 If you want to use SCSI scanners, synthesizers or CD-writers or just
160 about anything having "SCSI" in its name other than hard disks,
161 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
162 directly, so you need some additional software which knows how to
163 talk to these devices using the SCSI protocol:
165 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
166 writer software look at Cdrtools
167 (<http://cdrecord.berlios.de/private/cdrecord.html>)
168 and for burning a "disk at once": CDRDAO
169 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
170 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
171 For other devices, it's possible that you'll have to write the
172 driver software yourself. Please read the file
173 <file:Documentation/scsi/scsi-generic.txt> for more information.
175 To compile this driver as a module, choose M here and read
176 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
181 tristate "SCSI media changer support"
184 This is a driver for SCSI media changers. Most common devices are
185 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
186 don't need this for those tiny 6-slot cdrom changers. Media
187 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
188 If you have such hardware and want to use it with linux, say Y
189 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
191 If you want to compile this as a module ( = code which can be
192 inserted in and removed from the running kernel whenever you want),
193 say M here and read <file:Documentation/kbuild/modules.txt> and
194 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
197 config SCSI_ENCLOSURE
198 tristate "SCSI Enclosure Support"
199 depends on SCSI && ENCLOSURE_SERVICES
200 depends on m || SCSI_SAS_ATTRS != m
202 Enclosures are devices sitting on or in SCSI backplanes that
203 manage devices. If you have a disk cage, the chances are that
204 it has an enclosure device. Selecting this option will just allow
205 certain enclosure conditions to be reported and is not required.
207 config SCSI_CONSTANTS
208 bool "Verbose SCSI error reporting (kernel size += 36K)"
211 The error messages regarding your SCSI hardware will be easier to
212 understand if you say Y here; it will enlarge your kernel by about
213 36 KB. If in doubt, say Y.
216 bool "SCSI logging facility"
219 This turns on a logging facility that can be used to debug a number
220 of SCSI related problems.
222 If you say Y here, no logging output will appear by default, but you
223 can enable logging by saying Y to "/proc file system support" and
224 "Sysctl support" below and executing the command
226 echo <bitmask> > /proc/sys/dev/scsi/logging_level
228 where <bitmask> is a four byte value representing the logging type
229 and logging level for each type of logging selected.
231 There are a number of logging types and you can find them in the
232 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
233 are also described in that file and they determine the verbosity of
234 the logging for each logging type.
236 If you say N here, it may be harder to track down some types of SCSI
237 problems. If you say Y here your kernel will be somewhat larger, but
238 there should be no noticeable performance impact as long as you have
241 config SCSI_SCAN_ASYNC
242 bool "Asynchronous SCSI scanning"
245 The SCSI subsystem can probe for devices while the rest of the
246 system continues booting, and even probe devices on different
247 busses in parallel, leading to a significant speed-up.
249 You can override this choice by specifying "scsi_mod.scan=sync"
250 or async on the kernel's command line.
252 Note that this setting also affects whether resuming from
253 system suspend will be performed asynchronously.
255 menu "SCSI Transports"
258 config SCSI_SPI_ATTRS
259 tristate "Parallel SCSI (SPI) Transport Attributes"
262 If you wish to export transport-specific information about
263 each attached SCSI device to sysfs, say Y. Otherwise, say N.
266 tristate "FiberChannel Transport Attributes"
267 depends on SCSI && NET
268 select BLK_DEV_BSGLIB
271 If you wish to export transport-specific information about
272 each attached FiberChannel device to sysfs, say Y.
275 config SCSI_ISCSI_ATTRS
276 tristate "iSCSI Transport Attributes"
277 depends on SCSI && NET
278 select BLK_DEV_BSGLIB
280 If you wish to export transport-specific information about
281 each attached iSCSI device to sysfs, say Y.
284 config SCSI_SAS_ATTRS
285 tristate "SAS Transport Attributes"
287 select BLK_DEV_BSGLIB
289 If you wish to export transport-specific information about
290 each attached SAS device to sysfs, say Y.
292 source "drivers/scsi/libsas/Kconfig"
294 config SCSI_SRP_ATTRS
295 tristate "SRP Transport Attributes"
298 If you wish to export transport-specific information about
299 each attached SRP device to sysfs, say Y.
303 menuconfig SCSI_LOWLEVEL
304 bool "SCSI low-level drivers"
308 if SCSI_LOWLEVEL && SCSI
311 tristate "iSCSI Initiator over TCP/IP"
312 depends on SCSI && INET
316 select SCSI_ISCSI_ATTRS
318 The iSCSI Driver provides a host with the ability to access storage
319 through an IP network. The driver uses the iSCSI protocol to transport
320 SCSI requests and responses over a TCP/IP network between the host
321 (the "initiator") and "targets". Architecturally, the iSCSI driver
322 combines with the host's TCP/IP stack, network drivers, and Network
323 Interface Card (NIC) to provide the same functions as a SCSI or a
324 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
326 To compile this driver as a module, choose M here: the
327 module will be called iscsi_tcp.
329 The userspace component needed to initialize the driver, documentation,
330 and sample configuration files can be found here:
332 http://open-iscsi.org
334 config ISCSI_BOOT_SYSFS
335 tristate "iSCSI Boot Sysfs Interface"
338 This option enables support for exposing iSCSI boot information
339 via sysfs to userspace. If you wish to export this information,
340 say Y. Otherwise, say N.
342 source "drivers/scsi/cxgbi/Kconfig"
343 source "drivers/scsi/bnx2i/Kconfig"
344 source "drivers/scsi/bnx2fc/Kconfig"
345 source "drivers/scsi/be2iscsi/Kconfig"
346 source "drivers/scsi/cxlflash/Kconfig"
349 tristate "SGI WD93C93 SCSI Driver"
350 depends on SGI_HAS_WD93 && SCSI
352 If you have a Western Digital WD93 SCSI controller on
353 an SGI MIPS system, say Y. Otherwise, say N.
355 config BLK_DEV_3W_XXXX_RAID
356 tristate "3ware 5/6/7/8xxx ATA-RAID support"
357 depends on PCI && SCSI
359 3ware is the only hardware ATA-Raid product in Linux to date.
360 This card is 2,4, or 8 channel master mode support only.
361 SCSI support required!!!
363 <http://www.3ware.com/>
365 Please read the comments at the top of
366 <file:drivers/scsi/3w-xxxx.c>.
369 tristate "HP Smart Array SCSI driver"
370 depends on PCI && SCSI
371 select CHECK_SIGNATURE
372 select SCSI_SAS_ATTRS
374 This driver supports HP Smart Array Controllers (circa 2009).
375 It is a SCSI alternative to the cciss driver, which is a block
376 driver. Anyone wishing to use HP Smart Array controllers who
377 would prefer the devices be presented to linux as SCSI devices,
378 rather than as generic block devices should say Y here.
381 tristate "3ware 9xxx SATA-RAID support"
382 depends on PCI && SCSI
384 This driver supports the 9000 series 3ware SATA-RAID cards.
386 <http://www.amcc.com>
388 Please read the comments at the top of
389 <file:drivers/scsi/3w-9xxx.c>.
392 tristate "3ware 97xx SAS/SATA-RAID support"
393 depends on PCI && SCSI
395 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
399 Please read the comments at the top of
400 <file:drivers/scsi/3w-sas.c>.
403 tristate "ACARD SCSI support"
404 depends on PCI && SCSI
406 This driver supports the ACARD SCSI host adapter.
407 Support Chip <ATP870 ATP876 ATP880 ATP885>
408 To compile this driver as a module, choose M here: the
409 module will be called atp870u.
412 tristate "Adaptec AHA152X/2825 support"
413 depends on ISA && SCSI
414 select SCSI_SPI_ATTRS
415 select CHECK_SIGNATURE
417 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
418 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
419 must be manually specified in this case.
421 It is explained in section 3.3 of the SCSI-HOWTO, available from
422 <http://www.tldp.org/docs.html#howto>. You might also want to
423 read the file <file:Documentation/scsi/aha152x.txt>.
425 To compile this driver as a module, choose M here: the
426 module will be called aha152x.
429 tristate "Adaptec AHA1542 support"
430 depends on ISA && SCSI && ISA_DMA_API
432 This is support for a SCSI host adapter. It is explained in section
433 3.4 of the SCSI-HOWTO, available from
434 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
435 purchased by Adaptec, and some former Trantor products are being
436 sold under the Adaptec name. If it doesn't work out of the box, you
437 may have to change some settings in <file:drivers/scsi/aha1542.h>.
439 To compile this driver as a module, choose M here: the
440 module will be called aha1542.
443 tristate "Adaptec AHA1740 support"
444 depends on EISA && SCSI
446 This is support for a SCSI host adapter. It is explained in section
447 3.5 of the SCSI-HOWTO, available from
448 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
449 of the box, you may have to change some settings in
450 <file:drivers/scsi/aha1740.h>.
452 To compile this driver as a module, choose M here: the
453 module will be called aha1740.
456 tristate "Adaptec AACRAID support"
457 depends on SCSI && PCI
459 This driver supports a variety of Dell, HP, Adaptec, IBM and
460 ICP storage products. For a list of supported products, refer
461 to <file:Documentation/scsi/aacraid.txt>.
463 To compile this driver as a module, choose M here: the module
464 will be called aacraid.
467 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
468 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
469 source "drivers/scsi/aic94xx/Kconfig"
470 source "drivers/scsi/hisi_sas/Kconfig"
471 source "drivers/scsi/mvsas/Kconfig"
474 tristate "Marvell UMI driver"
475 depends on SCSI && PCI
477 Module for Marvell Universal Message Interface(UMI) driver
479 To compile this driver as a module, choose M here: the
480 module will be called mvumi.
483 tristate "Adaptec I2O RAID support "
484 depends on SCSI && PCI && VIRT_TO_BUS
486 This driver supports all of Adaptec's I2O based RAID controllers as
487 well as the DPT SmartRaid V cards. This is an Adaptec maintained
488 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
490 To compile this driver as a module, choose M here: the
491 module will be called dpt_i2o.
494 tristate "AdvanSys SCSI support"
496 depends on ISA || EISA || PCI
497 depends on ISA_DMA_API || !ISA
499 This is a driver for all SCSI host adapters manufactured by
500 AdvanSys. It is documented in the kernel source in
501 <file:drivers/scsi/advansys.c>.
503 To compile this driver as a module, choose M here: the
504 module will be called advansys.
507 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
508 depends on PCI && SCSI
510 This driver supports all of ARECA's SATA/SAS RAID controller cards.
511 This is an ARECA-maintained driver by Erich Chen.
512 If you have any problems, please mail to: <erich@areca.com.tw>.
513 Areca supports Linux RAID config tools.
514 Please link <http://www.areca.com.tw>
516 To compile this driver as a module, choose M here: the
517 module will be called arcmsr (modprobe arcmsr).
519 source "drivers/scsi/esas2r/Kconfig"
520 source "drivers/scsi/megaraid/Kconfig.megaraid"
521 source "drivers/scsi/mpt3sas/Kconfig"
522 source "drivers/scsi/smartpqi/Kconfig"
523 source "drivers/scsi/ufs/Kconfig"
526 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
527 depends on SCSI && PCI
529 This option enables support for HighPoint RocketRAID 3xxx/4xxx
532 To compile this driver as a module, choose M here; the module
533 will be called hptiop. If unsure, say N.
536 tristate "BusLogic SCSI support"
537 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
539 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
540 Adapters. Consult the SCSI-HOWTO, available from
541 <http://www.tldp.org/docs.html#howto>, and the files
542 <file:Documentation/scsi/BusLogic.txt> and
543 <file:Documentation/scsi/FlashPoint.txt> for more information.
544 Note that support for FlashPoint is only available for 32-bit
547 To compile this driver as a module, choose M here: the
548 module will be called BusLogic.
550 config SCSI_FLASHPOINT
551 bool "FlashPoint support"
552 depends on SCSI_BUSLOGIC && PCI
554 This option allows you to add FlashPoint support to the
555 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
556 substantial, so users of MultiMaster Host Adapters may not
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.txt>.
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.txt>.
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 && 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.
643 config SCSI_FUTURE_DOMAIN
644 tristate "Future Domain 16xx SCSI/AHA-2920A support"
645 depends on (ISA || PCI) && SCSI
646 select CHECK_SIGNATURE
648 This is support for Future Domain's 16-bit SCSI host adapters
649 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
650 other adapters based on the Future Domain chipsets (Quantum
651 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
652 It is explained in section 3.7 of the SCSI-HOWTO, available from
653 <http://www.tldp.org/docs.html#howto>.
655 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
656 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
657 controller support"). This Future Domain driver works with the older
658 Adaptec AHA-2920A boards with a Future Domain chip on them.
660 To compile this driver as a module, choose M here: the
661 module will be called fdomain.
664 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
665 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
667 Formerly called GDT SCSI Disk Array Controller Support.
669 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
670 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
671 in the kernel source in <file:drivers/scsi/gdth.c> and
672 <file:drivers/scsi/gdth.h>.
674 To compile this driver as a module, choose M here: the
675 module will be called gdth.
678 tristate "Intel(R) C600 Series Chipset SAS Controller"
679 depends on PCI && SCSI
681 select SCSI_SAS_LIBSAS
683 This driver supports the 6Gb/s SAS capabilities of the storage
684 control unit found in the Intel(R) C600 series chipset.
686 config SCSI_GENERIC_NCR5380
687 tristate "Generic NCR5380/53c400 SCSI ISA card support"
688 depends on ISA && SCSI && HAS_IOPORT_MAP
689 select SCSI_SPI_ATTRS
691 This is a driver for old ISA card SCSI controllers based on a
692 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
693 Most boards such as the Trantor T130 fit this category, as do
694 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
696 To compile this driver as a module, choose M here: the
697 module will be called g_NCR5380.
700 tristate "IBM ServeRAID support"
701 depends on PCI && SCSI
703 This is support for the IBM ServeRAID hardware RAID controllers.
704 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
705 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
706 for more information. If this driver does not work correctly
707 without modification please contact the author by email at
708 <ipslinux@adaptec.com>.
710 To compile this driver as a module, choose M here: the
711 module will be called ips.
714 tristate "IBM Virtual SCSI support"
715 depends on PPC_PSERIES
716 select SCSI_SRP_ATTRS
718 This is the IBM POWER Virtual SCSI Client
720 To compile this driver as a module, choose M here: the
721 module will be called ibmvscsi.
723 config SCSI_IBMVSCSIS
724 tristate "IBM Virtual SCSI Server support"
725 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
727 This is the IBM POWER Virtual SCSI Target Server
728 This driver uses the SRP protocol for communication between servers
729 guest and/or the host that run on the same server.
730 More information on VSCSI protocol can be found at www.power.org
732 The userspace configuration needed to initialize the driver can be
735 https://github.com/powervm/ibmvscsis/wiki/Configuration
737 To compile this driver as a module, choose M here: the
738 module will be called ibmvscsis.
741 tristate "IBM Virtual FC support"
742 depends on PPC_PSERIES && SCSI
743 depends on SCSI_FC_ATTRS
745 This is the IBM POWER Virtual FC Client
747 To compile this driver as a module, choose M here: the
748 module will be called ibmvfc.
750 config SCSI_IBMVFC_TRACE
751 bool "enable driver internal trace"
752 depends on SCSI_IBMVFC
755 If you say Y here, the driver will trace all commands issued
756 to the adapter. Performance impact is minimal. Trace can be
757 dumped using /sys/class/scsi_host/hostXX/trace.
760 tristate "Initio 9100U(W) support"
761 depends on PCI && SCSI
763 This is support for the Initio 91XXU(W) SCSI host adapter. Please
764 read the SCSI-HOWTO, available from
765 <http://www.tldp.org/docs.html#howto>.
767 To compile this driver as a module, choose M here: the
768 module will be called initio.
771 tristate "Initio INI-A100U2W support"
772 depends on PCI && SCSI
774 This is support for the Initio INI-A100U2W SCSI host adapter.
775 Please read the SCSI-HOWTO, available from
776 <http://www.tldp.org/docs.html#howto>.
778 To compile this driver as a module, choose M here: the
779 module will be called a100u2w.
782 tristate "IOMEGA parallel port (ppa - older drives)"
783 depends on SCSI && PARPORT_PC
785 This driver supports older versions of IOMEGA's parallel port ZIP
786 drive (a 100 MB removable media device).
788 Note that you can say N here if you have the SCSI version of the ZIP
789 drive: it will be supported automatically if you said Y to the
790 generic "SCSI disk support", above.
792 If you have the ZIP Plus drive or a more recent parallel port ZIP
793 drive (if the supplied cable with the drive is labeled "AutoDetect")
794 then you should say N here and Y to "IOMEGA parallel port (imm -
795 newer drives)", below.
797 For more information about this driver and how to use it you should
798 read the file <file:Documentation/scsi/ppa.txt>. You should also read
799 the SCSI-HOWTO, which is available from
800 <http://www.tldp.org/docs.html#howto>. If you use this driver,
801 you will still be able to use the parallel port for other tasks,
802 such as a printer; it is safe to compile both drivers into the
805 To compile this driver as a module, choose M here: the
806 module will be called ppa.
809 tristate "IOMEGA parallel port (imm - newer drives)"
810 depends on SCSI && PARPORT_PC
812 This driver supports newer versions of IOMEGA's parallel port ZIP
813 drive (a 100 MB removable media device).
815 Note that you can say N here if you have the SCSI version of the ZIP
816 drive: it will be supported automatically if you said Y to the
817 generic "SCSI disk support", above.
819 If you have the ZIP Plus drive or a more recent parallel port ZIP
820 drive (if the supplied cable with the drive is labeled "AutoDetect")
821 then you should say Y here; if you have an older ZIP drive, say N
822 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
824 For more information about this driver and how to use it you should
825 read the file <file:Documentation/scsi/ppa.txt>. You should also read
826 the SCSI-HOWTO, which is available from
827 <http://www.tldp.org/docs.html#howto>. If you use this driver,
828 you will still be able to use the parallel port for other tasks,
829 such as a printer; it is safe to compile both drivers into the
832 To compile this driver as a module, choose M here: the
833 module will be called imm.
835 config SCSI_IZIP_EPP16
836 bool "ppa/imm option - Use slow (but safe) EPP-16"
837 depends on SCSI_PPA || SCSI_IMM
839 EPP (Enhanced Parallel Port) is a standard for parallel ports which
840 allows them to act as expansion buses that can handle up to 64
843 Some parallel port chipsets are slower than their motherboard, and
844 so we have to control the state of the chipset's FIFO queue every
845 now and then to avoid data loss. This will be done if you say Y
848 Generally, saying Y is the safe option and slows things down a bit.
850 config SCSI_IZIP_SLOW_CTR
851 bool "ppa/imm option - Assume slow parport control register"
852 depends on SCSI_PPA || SCSI_IMM
854 Some parallel ports are known to have excessive delays between
855 changing the parallel port control register and good data being
856 available on the parallel port data/status register. This option
857 forces a small delay (1.0 usec to be exact) after changing the
858 control register to let things settle out. Enabling this option may
859 result in a big drop in performance but some very old parallel ports
860 (found in 386 vintage machines) will not work properly.
862 Generally, saying N is fine.
864 config SCSI_NCR53C406A
865 tristate "NCR53c406a SCSI support"
866 depends on ISA && SCSI
868 This is support for the NCR53c406a SCSI host adapter. For user
869 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
870 in the kernel source. Also read the SCSI-HOWTO, available from
871 <http://www.tldp.org/docs.html#howto>.
873 To compile this driver as a module, choose M here: the
874 module will be called NCR53c406.
877 tristate "NCR Dual 700 MCA SCSI support"
878 depends on MCA && SCSI
879 select SCSI_SPI_ATTRS
881 This is a driver for the MicroChannel Dual 700 card produced by
882 NCR and commonly used in 345x/35xx/4100 class machines. It always
883 tries to negotiate sync and uses tag command queueing.
885 Unless you have an NCR manufactured machine, the chances are that
886 you do not have this SCSI card, so say N.
889 tristate "HP Lasi SCSI support for 53c700/710"
890 depends on GSC && SCSI
891 select SCSI_SPI_ATTRS
893 This is a driver for the SCSI controller in the Lasi chip found in
894 many PA-RISC workstations & servers. If you do not know whether you
895 have a Lasi chip, it is safe to say "Y" here.
897 config SCSI_SNI_53C710
898 tristate "SNI RM SCSI support for 53c710"
899 depends on SNI_RM && SCSI
900 select SCSI_SPI_ATTRS
901 select 53C700_LE_ON_BE
903 This is a driver for the onboard SCSI controller found in older
904 SNI RM workstations & servers.
906 config 53C700_LE_ON_BE
908 depends on SCSI_LASI700
912 tristate "Promise SuperTrak EX Series support"
913 depends on PCI && SCSI
915 This driver supports Promise SuperTrak EX series storage controllers.
917 Promise provides Linux RAID configuration utility for these
918 controllers. Please visit <http://www.promise.com> to download.
920 To compile this driver as a module, choose M here: the
921 module will be called stex.
925 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
928 config SCSI_SYM53C8XX_2
929 tristate "SYM53C8XX Version 2 SCSI support"
930 depends on PCI && SCSI
931 select SCSI_SPI_ATTRS
933 This driver supports the whole NCR53C8XX/SYM53C8XX family of
934 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
935 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
936 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
937 controllers; you need to use the Fusion MPT driver for that.
939 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
942 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
943 int "DMA addressing mode"
944 depends on SCSI_SYM53C8XX_2
947 This option only applies to PCI-SCSI chips that are PCI DAC
948 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
950 When set to 0, the driver will program the chip to only perform
951 32-bit DMA. When set to 1, the chip will be able to perform DMA
952 to addresses up to 1TB. When set to 2, the driver supports the
953 full 64-bit DMA address range, but can only address 16 segments
954 of 4 GB each. This limits the total addressable range to 64 GB.
956 Most machines with less than 4GB of memory should use a setting
957 of 0 for best performance. If your machine has 4GB of memory
958 or more, you should set this option to 1 (the default).
960 The still experimental value 2 (64 bit DMA addressing with 16
961 x 4GB segments limitation) can be used on systems that require
962 PCI address bits past bit 39 to be set for the addressing of
963 memory using PCI DAC cycles.
965 config SCSI_SYM53C8XX_DEFAULT_TAGS
966 int "Default tagged command queue depth"
967 depends on SCSI_SYM53C8XX_2
970 This is the default value of the command queue depth the
971 driver will announce to the generic SCSI layer for devices
972 that support tagged command queueing. This value can be changed
973 from the boot command line. This is a soft limit that cannot
974 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
976 config SCSI_SYM53C8XX_MAX_TAGS
977 int "Maximum number of queued commands"
978 depends on SCSI_SYM53C8XX_2
981 This option allows you to specify the maximum number of commands
982 that can be queued to any device, when tagged command queuing is
983 possible. The driver supports up to 256 queued commands per device.
984 This value is used as a compiled-in hard limit.
986 config SCSI_SYM53C8XX_MMIO
987 bool "Use memory mapped IO"
988 depends on SCSI_SYM53C8XX_2
991 Memory mapped IO is faster than Port IO. Most people should
992 answer Y here, but some machines may have problems. If you have
993 to answer N here, please report the problem to the maintainer.
996 tristate "IBM Power Linux RAID adapter support"
997 depends on PCI && SCSI && ATA
1002 This driver supports the IBM Power Linux family RAID adapters.
1003 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1004 as IBM iSeries 5702, 5703, 5709, and 570A.
1006 config SCSI_IPR_TRACE
1007 bool "enable driver internal trace"
1011 If you say Y here, the driver will trace all commands issued
1012 to the adapter. Performance impact is minimal. Trace can be
1013 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1015 config SCSI_IPR_DUMP
1016 bool "enable adapter dump support"
1020 If you say Y here, the driver will support adapter crash dump.
1021 If you enable this support, the iprdump daemon can be used
1022 to capture adapter failure analysis information.
1025 tristate "Zalon SCSI support"
1026 depends on GSC && SCSI
1027 select SCSI_SPI_ATTRS
1029 The Zalon is a GSC/HSC bus interface chip that sits between the
1030 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1031 C110, J200, J210 and some D, K & R-class machines. It's also
1032 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1033 Say Y here if you have one of these machines or cards.
1035 config SCSI_NCR_Q720
1036 tristate "NCR Quad 720 MCA SCSI support"
1037 depends on MCA && SCSI
1038 select SCSI_SPI_ATTRS
1040 This is a driver for the MicroChannel Quad 720 card produced by
1041 NCR and commonly used in 345x/35xx/4100 class machines. It always
1042 tries to negotiate sync and uses tag command queueing.
1044 Unless you have an NCR manufactured machine, the chances are that
1045 you do not have this SCSI card, so say N.
1047 config SCSI_NCR53C8XX_DEFAULT_TAGS
1048 int "default tagged command queue depth"
1049 depends on SCSI_ZALON || SCSI_NCR_Q720
1052 "Tagged command queuing" is a feature of SCSI-2 which improves
1053 performance: the host adapter can send several SCSI commands to a
1054 device's queue even if previous commands haven't finished yet.
1055 Because the device is intelligent, it can optimize its operations
1056 (like head positioning) based on its own request queue. Some SCSI
1057 devices don't implement this properly; if you want to disable this
1058 feature, enter 0 or 1 here (it doesn't matter which).
1060 The default value is 8 and should be supported by most hard disks.
1061 This value can be overridden from the boot command line using the
1062 'tags' option as follows (example):
1063 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1064 4, set queue depth to 16 for target 2 and target 3 on controller 0
1065 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1067 The normal answer therefore is to go with the default 8 and to use
1068 a boot command line option for devices that need to use a different
1069 command queue depth.
1071 There is no safe option other than using good SCSI devices.
1073 config SCSI_NCR53C8XX_MAX_TAGS
1074 int "maximum number of queued commands"
1075 depends on SCSI_ZALON || SCSI_NCR_Q720
1078 This option allows you to specify the maximum number of commands
1079 that can be queued to any device, when tagged command queuing is
1080 possible. The default value is 32. Minimum is 2, maximum is 64.
1081 Modern hard disks are able to support 64 tags and even more, but
1082 do not seem to be faster when more than 32 tags are being used.
1084 So, the normal answer here is to go with the default value 32 unless
1085 you are using very large hard disks with large cache (>= 1 MB) that
1086 are able to take advantage of more than 32 tagged commands.
1088 There is no safe option and the default answer is recommended.
1090 config SCSI_NCR53C8XX_SYNC
1091 int "synchronous transfers frequency in MHz"
1092 depends on SCSI_ZALON || SCSI_NCR_Q720
1095 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1096 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1097 are respectively the maximum data transfer rates in mega-transfers
1098 per second for each class. For example, a FAST-20 Wide 16 device is
1099 able to transfer data at 20 million 16 bit packets per second for a
1100 total rate of 40 MB/s.
1102 You may specify 0 if you want to only use asynchronous data
1103 transfers. This is the safest and slowest option. Otherwise, specify
1104 a value between 5 and 80, depending on the capability of your SCSI
1105 controller. The higher the number, the faster the data transfer.
1106 Note that 80 should normally be ok since the driver decreases the
1107 value automatically according to the controller's capabilities.
1109 Your answer to this question is ignored for controllers with NVRAM,
1110 since the driver will get this information from the user set-up. It
1111 also can be overridden using a boot setup option, as follows
1112 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1113 for FAST-20 synchronous data transfer (20 mega-transfers per
1116 The normal answer therefore is not to go with the default but to
1117 select the maximum value 80 allowing the driver to use the maximum
1118 value supported by each controller. If this causes problems with
1119 your SCSI devices, you should come back and decrease the value.
1121 There is no safe option other than using good cabling, right
1122 terminations and SCSI conformant devices.
1124 config SCSI_NCR53C8XX_NO_DISCONNECT
1125 bool "not allow targets to disconnect"
1126 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1128 This option is only provided for safety if you suspect some SCSI
1129 device of yours to not support properly the target-disconnect
1130 feature. In that case, you would say Y here. In general however, to
1131 not allow targets to disconnect is not reasonable if there is more
1132 than 1 device on a SCSI bus. The normal answer therefore is N.
1134 config SCSI_QLOGIC_FAS
1135 tristate "Qlogic FAS SCSI support"
1136 depends on ISA && SCSI
1138 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1139 FastSCSI! cards as well as any other card based on the FASXX chip
1140 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1142 This driver does NOT support the PCI versions of these cards. The
1143 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1144 SCSI support"), below.
1146 Information about this driver is contained in
1147 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1148 SCSI-HOWTO, available from
1149 <http://www.tldp.org/docs.html#howto>.
1151 To compile this driver as a module, choose M here: the
1152 module will be called qlogicfas.
1154 config SCSI_QLOGIC_1280
1155 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1156 depends on PCI && SCSI
1158 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1160 To compile this driver as a module, choose M here: the
1161 module will be called qla1280.
1163 config SCSI_QLOGICPTI
1164 tristate "PTI Qlogic, ISP Driver"
1165 depends on SBUS && SCSI
1167 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1168 controllers are known under Solaris as qpti and in the openprom as
1169 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1170 driven by a different driver.
1172 To compile this driver as a module, choose M here: the
1173 module will be called qlogicpti.
1175 source "drivers/scsi/qla2xxx/Kconfig"
1176 source "drivers/scsi/qla4xxx/Kconfig"
1177 source "drivers/scsi/qedi/Kconfig"
1178 source "drivers/scsi/qedf/Kconfig"
1181 tristate "Emulex LightPulse Fibre Channel Support"
1182 depends on PCI && SCSI
1183 depends on SCSI_FC_ATTRS
1184 depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1185 depends on NVME_FC || NVME_FC=n
1188 This lpfc driver supports the Emulex LightPulse
1189 Family of Fibre Channel PCI host adapters.
1191 config SCSI_LPFC_DEBUG_FS
1192 bool "Emulex LightPulse Fibre Channel debugfs Support"
1193 depends on SCSI_LPFC && DEBUG_FS
1195 This makes debugging information from the lpfc driver
1196 available via the debugfs filesystem.
1199 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1200 depends on (EISA || MCA) && SCSI
1201 select SCSI_SPI_ATTRS
1203 This driver is for NCR53c710 based SCSI host adapters.
1205 It currently supports Compaq EISA cards and NCR MCA cards
1207 config SCSI_SYM53C416
1208 tristate "Symbios 53c416 SCSI support"
1209 depends on ISA && SCSI
1211 This is support for the sym53c416 SCSI host adapter, the SCSI
1212 adapter that comes with some HP scanners. This driver requires that
1213 the sym53c416 is configured first using some sort of PnP
1214 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1215 are using isapnp then you need to compile this driver as a module
1216 and then load it using insmod after isapnp has run. The parameters
1217 of the configured card(s) should be passed to the driver. The format
1220 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1222 To compile this driver as a module, choose M here: the
1223 module will be called sym53c416.
1226 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1227 depends on PCI && SCSI
1229 This driver supports PCI SCSI host adapters based on the ASIC
1230 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1232 This driver works, but is still in experimental status. So better
1233 have a bootable disk and a backup in case of emergency.
1235 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1237 To compile this driver as a module, choose M here: the
1238 module will be called dc395x.
1240 config SCSI_AM53C974
1241 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1242 depends on PCI && SCSI
1243 select SCSI_SPI_ATTRS
1245 This driver supports PCI SCSI host adapters based on the Am53C974A
1246 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1247 PCscsi/PCnet (Am53/79C974) solutions.
1248 This is a new implementation base on the generic esp_scsi driver.
1250 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1252 Note that this driver does NOT support Tekram DC390W/U/F, which are
1253 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1255 To compile this driver as a module, choose M here: the
1256 module will be called am53c974.
1259 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1260 depends on PCI && SCSI && !64BIT
1262 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1263 SCSI host adapter. Please read the SCSI-HOWTO, available from
1264 <http://www.tldp.org/docs.html#howto>.
1266 To compile this driver as a module, choose M here: the
1267 module will be called nsp32.
1270 tristate "Western Digital WD7193/7197/7296 support"
1271 depends on PCI && SCSI
1274 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1275 SCSI controllers (based on WD33C296A chip).
1278 tristate "SCSI debugging host and device simulator"
1282 This pseudo driver simulates one or more hosts (SCSI initiators),
1283 each with one or more targets, each with one or more logical units.
1284 Defaults to one of each, creating a small RAM disk device. Many
1285 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1286 directory can be tweaked at run time.
1287 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1288 Mainly used for testing and best as a module. If unsure, say N.
1291 tristate "MESH (Power Mac internal SCSI) support"
1292 depends on PPC32 && PPC_PMAC && SCSI
1294 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1295 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1296 other Power Macintoshes do). Say Y to include support for this SCSI
1299 To compile this driver as a module, choose M here: the
1300 module will be called mesh.
1302 config SCSI_MESH_SYNC_RATE
1303 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1304 depends on SCSI_MESH
1307 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1308 drives a bus which is entirely internal to the machine (such as the
1309 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1310 operation at up to 10 MB/s. On machines where the SCSI bus
1311 controlled by the MESH can have external devices connected, it is
1312 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1313 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1314 to disable synchronous operation.
1316 config SCSI_MESH_RESET_DELAY_MS
1317 int "initial bus reset delay (ms) (0 = no reset)"
1318 depends on SCSI_MESH
1321 config SCSI_MAC53C94
1322 tristate "53C94 (Power Mac external SCSI) support"
1323 depends on PPC32 && PPC_PMAC && SCSI
1325 On Power Macintoshes (and clones) with two SCSI buses, the external
1326 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1327 machines which only have one SCSI bus, such as the 7200, also use
1328 the 53C94. Say Y to include support for the 53C94.
1330 To compile this driver as a module, choose M here: the
1331 module will be called mac53c94.
1333 source "drivers/scsi/arm/Kconfig"
1336 bool "MIPS JAZZ FAS216 SCSI support"
1337 depends on MACH_JAZZ && SCSI
1338 select SCSI_SPI_ATTRS
1340 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1341 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1345 tristate "A3000 WD33C93A support"
1346 depends on AMIGA && SCSI
1348 If you have an Amiga 3000 and have SCSI devices connected to the
1349 built-in SCSI controller, say Y. Otherwise, say N.
1351 To compile this driver as a module, choose M here: the
1352 module will be called a3000.
1355 tristate "A2091/A590 WD33C93A support"
1356 depends on ZORRO && SCSI
1358 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1361 To compile this driver as a module, choose M here: the
1362 module will be called a2091.
1365 tristate "GVP Series II WD33C93A support"
1366 depends on ZORRO && SCSI
1368 If you have a Great Valley Products Series II SCSI controller,
1369 answer Y. Also say Y if you have a later model of GVP SCSI
1370 controller (such as the GVP A4008 or a Combo board). Otherwise,
1371 answer N. This driver does NOT work for the T-Rex series of
1372 accelerators from TekMagic and GVP-M.
1374 To compile this driver as a module, choose M here: the
1375 module will be called gvp11.
1378 tristate "A4000T NCR53c710 SCSI support"
1379 depends on AMIGA && SCSI
1380 select SCSI_SPI_ATTRS
1382 If you have an Amiga 4000T and have SCSI devices connected to the
1383 built-in SCSI controller, say Y. Otherwise, say N.
1385 To compile this driver as a module, choose M here: the
1386 module will be called a4000t.
1388 config SCSI_ZORRO7XX
1389 tristate "Zorro NCR53c710 SCSI support"
1390 depends on ZORRO && SCSI
1391 select SCSI_SPI_ATTRS
1393 Support for various NCR53c710-based SCSI controllers on Zorro
1394 expansion boards for the Amiga.
1396 - the Amiga 4091 Zorro III SCSI-2 controller,
1397 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1399 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1400 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1401 accelerator card for the Amiga 1200,
1402 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1405 tristate "Atari native SCSI support"
1406 depends on ATARI && SCSI
1407 select SCSI_SPI_ATTRS
1410 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1411 Falcon, ...) say Y to get it supported. Of course also, if you have
1412 a compatible SCSI controller (e.g. for Medusa).
1414 To compile this driver as a module, choose M here: the
1415 module will be called atari_scsi.
1417 This driver supports both styles of NCR integration into the
1418 system: the TT style (separate DMA), and the Falcon style (via
1419 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1420 in the Hades (without DMA).
1423 tristate "Macintosh NCR5380 SCSI"
1424 depends on MAC && SCSI
1425 select SCSI_SPI_ATTRS
1427 This is the NCR 5380 SCSI controller included on most of the 68030
1428 based Macintoshes. If you have one of these say Y and read the
1429 SCSI-HOWTO, available from
1430 <http://www.tldp.org/docs.html#howto>.
1433 tristate "Macintosh NCR53c9[46] SCSI"
1434 depends on MAC && SCSI
1435 select SCSI_SPI_ATTRS
1437 This is the NCR 53c9x SCSI controller found on most of the 68040
1440 To compile this driver as a module, choose M here: the module
1441 will be called mac_esp.
1444 bool "WD33C93 SCSI driver for MVME147"
1445 depends on MVME147 && SCSI=y
1446 select SCSI_SPI_ATTRS
1448 Support for the on-board SCSI controller on the Motorola MVME147
1449 single-board computer.
1452 tristate "NCR53C710 SCSI driver for MVME16x"
1453 depends on MVME16x && SCSI
1454 select SCSI_SPI_ATTRS
1456 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1457 SCSI controller chip. Almost everyone using one of these boards
1458 will want to say Y to this question.
1460 config BVME6000_SCSI
1461 tristate "NCR53C710 SCSI driver for BVME6000"
1462 depends on BVME6000 && SCSI
1463 select SCSI_SPI_ATTRS
1465 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1466 SCSI controller chip. Almost everyone using one of these boards
1467 will want to say Y to this question.
1470 tristate "Sun3 NCR5380 SCSI"
1471 depends on SUN3 && SCSI
1472 select SCSI_SPI_ATTRS
1474 This option will enable support for the OBIO (onboard io) NCR5380
1475 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1476 "Sun3" type VME scsi controllers also based on the NCR5380.
1477 General Linux information on the Sun 3 series (now discontinued)
1478 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1481 bool "Sun3x ESP SCSI"
1482 depends on SUN3X && SCSI=y
1483 select SCSI_SPI_ATTRS
1485 The ESP was an on-board SCSI controller used on Sun 3/80
1486 machines. Say Y here to compile in support for it.
1489 tristate "Sparc ESP Scsi Driver"
1490 depends on SBUS && SCSI
1491 select SCSI_SPI_ATTRS
1493 This is the driver for the Sun ESP SCSI host adapter. The ESP
1494 chipset is present in most SPARC SBUS-based computers and
1495 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1496 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1498 To compile this driver as a module, choose M here: the
1499 module will be called sun_esp.
1502 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1503 depends on S390 && QDIO && SCSI
1504 depends on SCSI_FC_ATTRS
1506 If you want to access SCSI devices attached to your IBM eServer
1507 zSeries by means of Fibre Channel interfaces say Y.
1508 For details please refer to the documentation provided by IBM at
1509 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1511 This driver is also available as a module. This module will be
1512 called zfcp. If you want to compile it as a module, say M here
1513 and read <file:Documentation/kbuild/modules.txt>.
1516 tristate "PMC SIERRA Linux MaxRAID adapter support"
1517 depends on PCI && SCSI && NET
1520 This driver supports the PMC SIERRA MaxRAID adapters.
1523 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1524 depends on PCI && SCSI
1525 select SCSI_SAS_LIBSAS
1527 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1528 based host adapters.
1531 tristate "Brocade BFA Fibre Channel Support"
1532 depends on PCI && SCSI
1533 depends on SCSI_FC_ATTRS
1535 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1537 To compile this driver as a module, choose M here. The module will
1541 tristate "virtio-scsi support"
1544 This is the virtual HBA driver for virtio. If the kernel will
1545 be used in a virtual machine, say Y or M.
1547 source "drivers/scsi/csiostor/Kconfig"
1549 endif # SCSI_LOWLEVEL
1551 source "drivers/scsi/pcmcia/Kconfig"
1553 source "drivers/scsi/device_handler/Kconfig"
1555 source "drivers/scsi/osd/Kconfig"