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
22 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
23 any other SCSI device under Linux, say Y and make sure that you know
24 the name of your SCSI host adapter (the card inside your computer
25 that "speaks" the SCSI protocol, also called SCSI controller),
26 because you will be asked for it.
28 You also need to say Y here if you have a device which speaks
29 the SCSI protocol. Examples of this include the parallel port
30 version of the IOMEGA ZIP drive, USB storage devices, Fibre
31 Channel, and FireWire storage.
33 To compile this driver as a module, choose M here and read
34 <file:Documentation/scsi/scsi.txt>.
35 The module will be called scsi_mod.
37 However, do not compile this as a module if your root file system
38 (the one containing the directory /) is located on a SCSI device.
49 config SCSI_MQ_DEFAULT
50 bool "SCSI: use blk-mq I/O path by default"
53 This option enables the new blk-mq based I/O path for SCSI
54 devices by default. With the option the scsi_mod.use_blk_mq
55 module/boot option defaults to Y, without it to N, but it can
56 still be overridden either way.
61 bool "legacy /proc/scsi/ support"
62 depends on SCSI && PROC_FS
65 This option enables support for the various files in
66 /proc/scsi. In Linux 2.6 this has been superseded by
67 files in sysfs but many legacy applications rely on this.
71 comment "SCSI support type (disk, tape, CD-ROM)"
75 tristate "SCSI disk support"
78 If you want to use SCSI hard disks, Fibre Channel disks,
79 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
80 USB storage or the SCSI or parallel port version of
81 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
82 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
86 To compile this driver as a module, choose M here and read
87 <file:Documentation/scsi/scsi.txt>.
88 The module will be called sd_mod.
90 Do not compile this driver as a module if your root file system
91 (the one containing the directory /) is located on a SCSI disk.
92 In this case, do not compile the driver for your SCSI host adapter
93 (below) as a module either.
96 tristate "SCSI tape support"
99 If you want to use a SCSI tape drive under Linux, say Y and read the
100 SCSI-HOWTO, available from
101 <http://www.tldp.org/docs.html#howto>, and
102 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
105 To compile this driver as a module, choose M here and read
106 <file:Documentation/scsi/scsi.txt>. The module will be called st.
109 tristate "SCSI OnStream SC-x0 tape support"
112 The OnStream SC-x0 SCSI tape drives cannot be driven by the
113 standard st driver, but instead need this special osst driver and
114 use the /dev/osstX char device nodes (major 206). Via usb-storage,
115 you may be able to drive the USB-x0 and DI-x0 drives as well.
116 Note that there is also a second generation of OnStream
117 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
118 tapes (QIC-157) and can be driven by the standard driver st.
119 For more information, you may have a look at the SCSI-HOWTO
120 <http://www.tldp.org/docs.html#howto> and
121 <file:Documentation/scsi/osst.txt> in the kernel source.
122 More info on the OnStream driver may be found on
123 <http://sourceforge.net/projects/osst/>
124 Please also have a look at the standard st docu, as most of it
125 applies to osst as well.
127 To compile this driver as a module, choose M here and read
128 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
131 tristate "SCSI CDROM support"
134 If you want to use a CD or DVD drive attached to your computer
135 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
136 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
138 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
140 To compile this driver as a module, choose M here and read
141 <file:Documentation/scsi/scsi.txt>.
142 The module will be called sr_mod.
144 config BLK_DEV_SR_VENDOR
145 bool "Enable vendor-specific extensions (for SCSI CDROM)"
146 depends on BLK_DEV_SR
148 This enables the usage of vendor specific SCSI commands. This is
149 required to support multisession CDs with old NEC/TOSHIBA cdrom
150 drives (and HP Writers). If you have such a drive and get the first
151 session only, try saying Y here; everybody else says N.
154 tristate "SCSI generic support"
157 If you want to use SCSI scanners, synthesizers or CD-writers or just
158 about anything having "SCSI" in its name other than hard disks,
159 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
160 directly, so you need some additional software which knows how to
161 talk to these devices using the SCSI protocol:
163 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
164 writer software look at Cdrtools
165 (<http://cdrecord.berlios.de/private/cdrecord.html>)
166 and for burning a "disk at once": CDRDAO
167 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
168 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
169 For other devices, it's possible that you'll have to write the
170 driver software yourself. Please read the file
171 <file:Documentation/scsi/scsi-generic.txt> for more information.
173 To compile this driver as a module, choose M here and read
174 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
179 tristate "SCSI media changer support"
182 This is a driver for SCSI media changers. Most common devices are
183 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
184 don't need this for those tiny 6-slot cdrom changers. Media
185 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
186 If you have such hardware and want to use it with linux, say Y
187 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
189 If you want to compile this as a module ( = code which can be
190 inserted in and removed from the running kernel whenever you want),
191 say M here and read <file:Documentation/kbuild/modules.txt> and
192 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
195 config SCSI_ENCLOSURE
196 tristate "SCSI Enclosure Support"
197 depends on SCSI && ENCLOSURE_SERVICES
198 depends on m || SCSI_SAS_ATTRS != m
200 Enclosures are devices sitting on or in SCSI backplanes that
201 manage devices. If you have a disk cage, the chances are that
202 it has an enclosure device. Selecting this option will just allow
203 certain enclosure conditions to be reported and is not required.
205 config SCSI_CONSTANTS
206 bool "Verbose SCSI error reporting (kernel size += 36K)"
209 The error messages regarding your SCSI hardware will be easier to
210 understand if you say Y here; it will enlarge your kernel by about
211 36 KB. If in doubt, say Y.
214 bool "SCSI logging facility"
217 This turns on a logging facility that can be used to debug a number
218 of SCSI related problems.
220 If you say Y here, no logging output will appear by default, but you
221 can enable logging by saying Y to "/proc file system support" and
222 "Sysctl support" below and executing the command
224 echo <bitmask> > /proc/sys/dev/scsi/logging_level
226 where <bitmask> is a four byte value representing the logging type
227 and logging level for each type of logging selected.
229 There are a number of logging types and you can find them in the
230 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
231 are also described in that file and they determine the verbosity of
232 the logging for each logging type.
234 If you say N here, it may be harder to track down some types of SCSI
235 problems. If you say Y here your kernel will be somewhat larger, but
236 there should be no noticeable performance impact as long as you have
239 config SCSI_SCAN_ASYNC
240 bool "Asynchronous SCSI scanning"
243 The SCSI subsystem can probe for devices while the rest of the
244 system continues booting, and even probe devices on different
245 busses in parallel, leading to a significant speed-up.
247 You can override this choice by specifying "scsi_mod.scan=sync"
248 or async on the kernel's command line.
250 Note that this setting also affects whether resuming from
251 system suspend will be performed asynchronously.
253 menu "SCSI Transports"
256 config SCSI_SPI_ATTRS
257 tristate "Parallel SCSI (SPI) Transport Attributes"
260 If you wish to export transport-specific information about
261 each attached SCSI device to sysfs, say Y. Otherwise, say N.
264 tristate "FiberChannel Transport Attributes"
265 depends on SCSI && NET
268 If you wish to export transport-specific information about
269 each attached FiberChannel device to sysfs, say Y.
272 config SCSI_ISCSI_ATTRS
273 tristate "iSCSI Transport Attributes"
274 depends on SCSI && NET
275 select BLK_DEV_BSGLIB
277 If you wish to export transport-specific information about
278 each attached iSCSI device to sysfs, say Y.
281 config SCSI_SAS_ATTRS
282 tristate "SAS Transport Attributes"
286 If you wish to export transport-specific information about
287 each attached SAS device to sysfs, say Y.
289 source "drivers/scsi/libsas/Kconfig"
291 config SCSI_SRP_ATTRS
292 tristate "SRP Transport Attributes"
295 If you wish to export transport-specific information about
296 each attached SRP device to sysfs, say Y.
300 menuconfig SCSI_LOWLEVEL
301 bool "SCSI low-level drivers"
305 if SCSI_LOWLEVEL && SCSI
308 tristate "iSCSI Initiator over TCP/IP"
309 depends on SCSI && INET
313 select SCSI_ISCSI_ATTRS
315 The iSCSI Driver provides a host with the ability to access storage
316 through an IP network. The driver uses the iSCSI protocol to transport
317 SCSI requests and responses over a TCP/IP network between the host
318 (the "initiator") and "targets". Architecturally, the iSCSI driver
319 combines with the host's TCP/IP stack, network drivers, and Network
320 Interface Card (NIC) to provide the same functions as a SCSI or a
321 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
323 To compile this driver as a module, choose M here: the
324 module will be called iscsi_tcp.
326 The userspace component needed to initialize the driver, documentation,
327 and sample configuration files can be found here:
329 http://open-iscsi.org
331 config ISCSI_BOOT_SYSFS
332 tristate "iSCSI Boot Sysfs Interface"
335 This option enables support for exposing iSCSI boot information
336 via sysfs to userspace. If you wish to export this information,
337 say Y. Otherwise, say N.
339 source "drivers/scsi/cxgbi/Kconfig"
340 source "drivers/scsi/bnx2i/Kconfig"
341 source "drivers/scsi/bnx2fc/Kconfig"
342 source "drivers/scsi/be2iscsi/Kconfig"
343 source "drivers/scsi/cxlflash/Kconfig"
346 tristate "SGI WD93C93 SCSI Driver"
347 depends on SGI_HAS_WD93 && SCSI
349 If you have a Western Digital WD93 SCSI controller on
350 an SGI MIPS system, say Y. Otherwise, say N.
352 config BLK_DEV_3W_XXXX_RAID
353 tristate "3ware 5/6/7/8xxx ATA-RAID support"
354 depends on PCI && SCSI
356 3ware is the only hardware ATA-Raid product in Linux to date.
357 This card is 2,4, or 8 channel master mode support only.
358 SCSI support required!!!
360 <http://www.3ware.com/>
362 Please read the comments at the top of
363 <file:drivers/scsi/3w-xxxx.c>.
366 tristate "HP Smart Array SCSI driver"
367 depends on PCI && SCSI
368 select CHECK_SIGNATURE
369 select SCSI_SAS_ATTRS
371 This driver supports HP Smart Array Controllers (circa 2009).
372 It is a SCSI alternative to the cciss driver, which is a block
373 driver. Anyone wishing to use HP Smart Array controllers who
374 would prefer the devices be presented to linux as SCSI devices,
375 rather than as generic block devices should say Y here.
378 tristate "3ware 9xxx SATA-RAID support"
379 depends on PCI && SCSI
381 This driver supports the 9000 series 3ware SATA-RAID cards.
383 <http://www.amcc.com>
385 Please read the comments at the top of
386 <file:drivers/scsi/3w-9xxx.c>.
389 tristate "3ware 97xx SAS/SATA-RAID support"
390 depends on PCI && SCSI
392 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
396 Please read the comments at the top of
397 <file:drivers/scsi/3w-sas.c>.
400 tristate "ACARD SCSI support"
401 depends on PCI && SCSI
403 This driver supports the ACARD SCSI host adapter.
404 Support Chip <ATP870 ATP876 ATP880 ATP885>
405 To compile this driver as a module, choose M here: the
406 module will be called atp870u.
409 tristate "Adaptec AHA152X/2825 support"
410 depends on ISA && SCSI
411 select SCSI_SPI_ATTRS
412 select CHECK_SIGNATURE
414 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
415 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
416 must be manually specified in this case.
418 It is explained in section 3.3 of the SCSI-HOWTO, available from
419 <http://www.tldp.org/docs.html#howto>. You might also want to
420 read the file <file:Documentation/scsi/aha152x.txt>.
422 To compile this driver as a module, choose M here: the
423 module will be called aha152x.
426 tristate "Adaptec AHA1542 support"
427 depends on ISA && SCSI && ISA_DMA_API
429 This is support for a SCSI host adapter. It is explained in section
430 3.4 of the SCSI-HOWTO, available from
431 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
432 purchased by Adaptec, and some former Trantor products are being
433 sold under the Adaptec name. If it doesn't work out of the box, you
434 may have to change some settings in <file:drivers/scsi/aha1542.h>.
436 To compile this driver as a module, choose M here: the
437 module will be called aha1542.
440 tristate "Adaptec AHA1740 support"
441 depends on EISA && SCSI
443 This is support for a SCSI host adapter. It is explained in section
444 3.5 of the SCSI-HOWTO, available from
445 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
446 of the box, you may have to change some settings in
447 <file:drivers/scsi/aha1740.h>.
449 To compile this driver as a module, choose M here: the
450 module will be called aha1740.
453 tristate "Adaptec AACRAID support"
454 depends on SCSI && PCI
456 This driver supports a variety of Dell, HP, Adaptec, IBM and
457 ICP storage products. For a list of supported products, refer
458 to <file:Documentation/scsi/aacraid.txt>.
460 To compile this driver as a module, choose M here: the module
461 will be called aacraid.
464 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
465 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
466 source "drivers/scsi/aic94xx/Kconfig"
467 source "drivers/scsi/hisi_sas/Kconfig"
468 source "drivers/scsi/mvsas/Kconfig"
471 tristate "Marvell UMI driver"
472 depends on SCSI && PCI
474 Module for Marvell Universal Message Interface(UMI) driver
476 To compile this driver as a module, choose M here: the
477 module will be called mvumi.
480 tristate "Adaptec I2O RAID support "
481 depends on SCSI && PCI && VIRT_TO_BUS
483 This driver supports all of Adaptec's I2O based RAID controllers as
484 well as the DPT SmartRaid V cards. This is an Adaptec maintained
485 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
487 To compile this driver as a module, choose M here: the
488 module will be called dpt_i2o.
491 tristate "AdvanSys SCSI support"
493 depends on ISA || EISA || PCI
494 depends on ISA_DMA_API || !ISA
496 This is a driver for all SCSI host adapters manufactured by
497 AdvanSys. It is documented in the kernel source in
498 <file:drivers/scsi/advansys.c>.
500 To compile this driver as a module, choose M here: the
501 module will be called advansys.
504 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
505 depends on PCI && SCSI
507 This driver supports all of ARECA's SATA/SAS RAID controller cards.
508 This is an ARECA-maintained driver by Erich Chen.
509 If you have any problems, please mail to: <erich@areca.com.tw>.
510 Areca supports Linux RAID config tools.
511 Please link <http://www.areca.com.tw>
513 To compile this driver as a module, choose M here: the
514 module will be called arcmsr (modprobe arcmsr).
516 source "drivers/scsi/esas2r/Kconfig"
517 source "drivers/scsi/megaraid/Kconfig.megaraid"
518 source "drivers/scsi/mpt3sas/Kconfig"
519 source "drivers/scsi/smartpqi/Kconfig"
520 source "drivers/scsi/ufs/Kconfig"
523 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
524 depends on SCSI && PCI
526 This option enables support for HighPoint RocketRAID 3xxx/4xxx
529 To compile this driver as a module, choose M here; the module
530 will be called hptiop. If unsure, say N.
533 tristate "BusLogic SCSI support"
534 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
536 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
537 Adapters. Consult the SCSI-HOWTO, available from
538 <http://www.tldp.org/docs.html#howto>, and the files
539 <file:Documentation/scsi/BusLogic.txt> and
540 <file:Documentation/scsi/FlashPoint.txt> for more information.
541 Note that support for FlashPoint is only available for 32-bit
544 To compile this driver as a module, choose M here: the
545 module will be called BusLogic.
547 config SCSI_FLASHPOINT
548 bool "FlashPoint support"
549 depends on SCSI_BUSLOGIC && PCI
551 This option allows you to add FlashPoint support to the
552 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
553 substantial, so users of MultiMaster Host Adapters may not
557 tristate "VMware PVSCSI driver support"
558 depends on PCI && SCSI && X86
560 This driver supports VMware's para virtualized SCSI HBA.
561 To compile this driver as a module, choose M here: the
562 module will be called vmw_pvscsi.
564 config XEN_SCSI_FRONTEND
565 tristate "XEN SCSI frontend driver"
566 depends on SCSI && XEN
567 select XEN_XENBUS_FRONTEND
569 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
570 within another guest OS (usually Dom0).
571 Only needed if the kernel is running in a XEN guest and generic
572 SCSI access to a device is needed.
574 config HYPERV_STORAGE
575 tristate "Microsoft Hyper-V virtual storage driver"
576 depends on SCSI && HYPERV
577 depends on m || SCSI_FC_ATTRS != m
580 Select this option to enable the Hyper-V virtual storage driver.
583 tristate "LibFC module"
584 depends on SCSI_FC_ATTRS
587 Fibre Channel library module
590 tristate "LibFCoE module"
593 Library for Fibre Channel over Ethernet module
596 tristate "FCoE module"
600 Fibre Channel over Ethernet module
603 tristate "Cisco FNIC Driver"
604 depends on PCI && X86
607 This is support for the Cisco PCI-Express FCoE HBA.
609 To compile this driver as a module, choose M here and read
610 <file:Documentation/scsi/scsi.txt>.
611 The module will be called fnic.
614 tristate "Cisco SNIC Driver"
615 depends on PCI && SCSI
617 This is support for the Cisco PCI-Express SCSI HBA.
619 To compile this driver as a module, choose M here and read
620 <file:Documentation/scsi/scsi.txt>.
621 The module will be called snic.
623 config SCSI_SNIC_DEBUG_FS
624 bool "Cisco SNIC Driver Debugfs Support"
625 depends on SCSI_SNIC && DEBUG_FS
627 This enables to list debugging information from SNIC Driver
628 available via debugfs file system
631 tristate "DMX3191D SCSI support"
632 depends on PCI && SCSI
633 select SCSI_SPI_ATTRS
635 This is support for Domex DMX3191D SCSI Host Adapters.
637 To compile this driver as a module, choose M here: the
638 module will be called dmx3191d.
641 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
642 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
644 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
645 ISA and all EISA I/O addresses are probed looking for the "EATA"
646 signature. The addresses of all the PCI SCSI controllers reported
647 by the PCI subsystem are probed as well.
649 You want to read the start of <file:drivers/scsi/eata.c> and the
650 SCSI-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>.
653 To compile this driver as a module, choose M here: the
654 module will be called eata.
656 config SCSI_EATA_TAGGED_QUEUE
657 bool "enable tagged command queueing"
660 This is a feature of SCSI-2 which improves performance: the host
661 adapter can send several SCSI commands to a device's queue even if
662 previous commands haven't finished yet.
663 This is equivalent to the "eata=tc:y" boot option.
665 config SCSI_EATA_LINKED_COMMANDS
666 bool "enable elevator sorting"
669 This option enables elevator sorting for all probed SCSI disks and
670 CD-ROMs. It definitely reduces the average seek distance when doing
671 random seeks, but this does not necessarily result in a noticeable
672 performance improvement: your mileage may vary...
673 This is equivalent to the "eata=lc:y" boot option.
675 config SCSI_EATA_MAX_TAGS
676 int "maximum number of queued commands"
680 This specifies how many SCSI commands can be maximally queued for
681 each probed SCSI device. You should reduce the default value of 16
682 only if you have disks with buggy or limited tagged command support.
683 Minimum is 2 and maximum is 62. This value is also the window size
684 used by the elevator sorting option above. The effective value used
685 by the driver for each probed SCSI device is reported at boot time.
686 This is equivalent to the "eata=mq:8" boot option.
689 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
690 depends on (ISA || EISA || PCI) && SCSI && BROKEN
692 This driver supports all EATA-PIO protocol compliant SCSI Host
693 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
694 host adapters could also use this driver but are discouraged from
695 doing so, since this driver only supports hard disks and lacks
696 numerous features. You might want to have a look at the SCSI-HOWTO,
697 available from <http://www.tldp.org/docs.html#howto>.
699 To compile this driver as a module, choose M here: the
700 module will be called eata_pio.
702 config SCSI_FUTURE_DOMAIN
703 tristate "Future Domain 16xx SCSI/AHA-2920A support"
704 depends on (ISA || PCI) && SCSI
705 select CHECK_SIGNATURE
707 This is support for Future Domain's 16-bit SCSI host adapters
708 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
709 other adapters based on the Future Domain chipsets (Quantum
710 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
711 It is explained in section 3.7 of the SCSI-HOWTO, available from
712 <http://www.tldp.org/docs.html#howto>.
714 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
715 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
716 controller support"). This Future Domain driver works with the older
717 Adaptec AHA-2920A boards with a Future Domain chip on them.
719 To compile this driver as a module, choose M here: the
720 module will be called fdomain.
723 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
724 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
726 Formerly called GDT SCSI Disk Array Controller Support.
728 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
729 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
730 in the kernel source in <file:drivers/scsi/gdth.c> and
731 <file:drivers/scsi/gdth.h>.
733 To compile this driver as a module, choose M here: the
734 module will be called gdth.
737 tristate "Intel(R) C600 Series Chipset SAS Controller"
738 depends on PCI && SCSI
740 select SCSI_SAS_LIBSAS
742 This driver supports the 6Gb/s SAS capabilities of the storage
743 control unit found in the Intel(R) C600 series chipset.
745 config SCSI_GENERIC_NCR5380
746 tristate "Generic NCR5380/53c400 SCSI ISA card support"
747 depends on ISA && SCSI && HAS_IOPORT_MAP
748 select SCSI_SPI_ATTRS
750 This is a driver for old ISA card SCSI controllers based on a
751 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
752 Most boards such as the Trantor T130 fit this category, as do
753 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
755 To compile this driver as a module, choose M here: the
756 module will be called g_NCR5380.
759 tristate "IBM ServeRAID support"
760 depends on PCI && SCSI
762 This is support for the IBM ServeRAID hardware RAID controllers.
763 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
764 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
765 for more information. If this driver does not work correctly
766 without modification please contact the author by email at
767 <ipslinux@adaptec.com>.
769 To compile this driver as a module, choose M here: the
770 module will be called ips.
773 tristate "IBM Virtual SCSI support"
774 depends on PPC_PSERIES
775 select SCSI_SRP_ATTRS
777 This is the IBM POWER Virtual SCSI Client
779 To compile this driver as a module, choose M here: the
780 module will be called ibmvscsi.
782 config SCSI_IBMVSCSIS
783 tristate "IBM Virtual SCSI Server support"
784 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
786 This is the IBM POWER Virtual SCSI Target Server
787 This driver uses the SRP protocol for communication betwen servers
788 guest and/or the host that run on the same server.
789 More information on VSCSI protocol can be found at www.power.org
791 The userspace configuration needed to initialize the driver can be
794 https://github.com/powervm/ibmvscsis/wiki/Configuration
796 To compile this driver as a module, choose M here: the
797 module will be called ibmvscsis.
800 tristate "IBM Virtual FC support"
801 depends on PPC_PSERIES && SCSI
802 depends on SCSI_FC_ATTRS
804 This is the IBM POWER Virtual FC Client
806 To compile this driver as a module, choose M here: the
807 module will be called ibmvfc.
809 config SCSI_IBMVFC_TRACE
810 bool "enable driver internal trace"
811 depends on SCSI_IBMVFC
814 If you say Y here, the driver will trace all commands issued
815 to the adapter. Performance impact is minimal. Trace can be
816 dumped using /sys/class/scsi_host/hostXX/trace.
819 tristate "Initio 9100U(W) support"
820 depends on PCI && SCSI
822 This is support for the Initio 91XXU(W) SCSI host adapter. Please
823 read the SCSI-HOWTO, available from
824 <http://www.tldp.org/docs.html#howto>.
826 To compile this driver as a module, choose M here: the
827 module will be called initio.
830 tristate "Initio INI-A100U2W support"
831 depends on PCI && SCSI
833 This is support for the Initio INI-A100U2W SCSI host adapter.
834 Please read the SCSI-HOWTO, available from
835 <http://www.tldp.org/docs.html#howto>.
837 To compile this driver as a module, choose M here: the
838 module will be called a100u2w.
841 tristate "IOMEGA parallel port (ppa - older drives)"
842 depends on SCSI && PARPORT_PC
844 This driver supports older versions of IOMEGA's parallel port ZIP
845 drive (a 100 MB removable media device).
847 Note that you can say N here if you have the SCSI version of the ZIP
848 drive: it will be supported automatically if you said Y to the
849 generic "SCSI disk support", above.
851 If you have the ZIP Plus drive or a more recent parallel port ZIP
852 drive (if the supplied cable with the drive is labeled "AutoDetect")
853 then you should say N here and Y to "IOMEGA parallel port (imm -
854 newer drives)", below.
856 For more information about this driver and how to use it you should
857 read the file <file:Documentation/scsi/ppa.txt>. You should also read
858 the SCSI-HOWTO, which is available from
859 <http://www.tldp.org/docs.html#howto>. If you use this driver,
860 you will still be able to use the parallel port for other tasks,
861 such as a printer; it is safe to compile both drivers into the
864 To compile this driver as a module, choose M here: the
865 module will be called ppa.
868 tristate "IOMEGA parallel port (imm - newer drives)"
869 depends on SCSI && PARPORT_PC
871 This driver supports newer versions of IOMEGA's parallel port ZIP
872 drive (a 100 MB removable media device).
874 Note that you can say N here if you have the SCSI version of the ZIP
875 drive: it will be supported automatically if you said Y to the
876 generic "SCSI disk support", above.
878 If you have the ZIP Plus drive or a more recent parallel port ZIP
879 drive (if the supplied cable with the drive is labeled "AutoDetect")
880 then you should say Y here; if you have an older ZIP drive, say N
881 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
883 For more information about this driver and how to use it you should
884 read the file <file:Documentation/scsi/ppa.txt>. You should also read
885 the SCSI-HOWTO, which is available from
886 <http://www.tldp.org/docs.html#howto>. If you use this driver,
887 you will still be able to use the parallel port for other tasks,
888 such as a printer; it is safe to compile both drivers into the
891 To compile this driver as a module, choose M here: the
892 module will be called imm.
894 config SCSI_IZIP_EPP16
895 bool "ppa/imm option - Use slow (but safe) EPP-16"
896 depends on SCSI_PPA || SCSI_IMM
898 EPP (Enhanced Parallel Port) is a standard for parallel ports which
899 allows them to act as expansion buses that can handle up to 64
902 Some parallel port chipsets are slower than their motherboard, and
903 so we have to control the state of the chipset's FIFO queue every
904 now and then to avoid data loss. This will be done if you say Y
907 Generally, saying Y is the safe option and slows things down a bit.
909 config SCSI_IZIP_SLOW_CTR
910 bool "ppa/imm option - Assume slow parport control register"
911 depends on SCSI_PPA || SCSI_IMM
913 Some parallel ports are known to have excessive delays between
914 changing the parallel port control register and good data being
915 available on the parallel port data/status register. This option
916 forces a small delay (1.0 usec to be exact) after changing the
917 control register to let things settle out. Enabling this option may
918 result in a big drop in performance but some very old parallel ports
919 (found in 386 vintage machines) will not work properly.
921 Generally, saying N is fine.
923 config SCSI_NCR53C406A
924 tristate "NCR53c406a SCSI support"
925 depends on ISA && SCSI
927 This is support for the NCR53c406a SCSI host adapter. For user
928 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
929 in the kernel source. Also read the SCSI-HOWTO, available from
930 <http://www.tldp.org/docs.html#howto>.
932 To compile this driver as a module, choose M here: the
933 module will be called NCR53c406.
936 tristate "NCR Dual 700 MCA SCSI support"
937 depends on MCA && SCSI
938 select SCSI_SPI_ATTRS
940 This is a driver for the MicroChannel Dual 700 card produced by
941 NCR and commonly used in 345x/35xx/4100 class machines. It always
942 tries to negotiate sync and uses tag command queueing.
944 Unless you have an NCR manufactured machine, the chances are that
945 you do not have this SCSI card, so say N.
948 tristate "HP Lasi SCSI support for 53c700/710"
949 depends on GSC && SCSI
950 select SCSI_SPI_ATTRS
952 This is a driver for the SCSI controller in the Lasi chip found in
953 many PA-RISC workstations & servers. If you do not know whether you
954 have a Lasi chip, it is safe to say "Y" here.
956 config SCSI_SNI_53C710
957 tristate "SNI RM SCSI support for 53c710"
958 depends on SNI_RM && SCSI
959 select SCSI_SPI_ATTRS
960 select 53C700_LE_ON_BE
962 This is a driver for the onboard SCSI controller found in older
963 SNI RM workstations & servers.
965 config 53C700_LE_ON_BE
967 depends on SCSI_LASI700
971 tristate "Promise SuperTrak EX Series support"
972 depends on PCI && SCSI
974 This driver supports Promise SuperTrak EX series storage controllers.
976 Promise provides Linux RAID configuration utility for these
977 controllers. Please visit <http://www.promise.com> to download.
979 To compile this driver as a module, choose M here: the
980 module will be called stex.
984 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
987 config SCSI_SYM53C8XX_2
988 tristate "SYM53C8XX Version 2 SCSI support"
989 depends on PCI && SCSI
990 select SCSI_SPI_ATTRS
992 This driver supports the whole NCR53C8XX/SYM53C8XX family of
993 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
994 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
995 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
996 controllers; you need to use the Fusion MPT driver for that.
998 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1001 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1002 int "DMA addressing mode"
1003 depends on SCSI_SYM53C8XX_2
1006 This option only applies to PCI-SCSI chips that are PCI DAC
1007 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1009 When set to 0, the driver will program the chip to only perform
1010 32-bit DMA. When set to 1, the chip will be able to perform DMA
1011 to addresses up to 1TB. When set to 2, the driver supports the
1012 full 64-bit DMA address range, but can only address 16 segments
1013 of 4 GB each. This limits the total addressable range to 64 GB.
1015 Most machines with less than 4GB of memory should use a setting
1016 of 0 for best performance. If your machine has 4GB of memory
1017 or more, you should set this option to 1 (the default).
1019 The still experimental value 2 (64 bit DMA addressing with 16
1020 x 4GB segments limitation) can be used on systems that require
1021 PCI address bits past bit 39 to be set for the addressing of
1022 memory using PCI DAC cycles.
1024 config SCSI_SYM53C8XX_DEFAULT_TAGS
1025 int "Default tagged command queue depth"
1026 depends on SCSI_SYM53C8XX_2
1029 This is the default value of the command queue depth the
1030 driver will announce to the generic SCSI layer for devices
1031 that support tagged command queueing. This value can be changed
1032 from the boot command line. This is a soft limit that cannot
1033 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1035 config SCSI_SYM53C8XX_MAX_TAGS
1036 int "Maximum number of queued commands"
1037 depends on SCSI_SYM53C8XX_2
1040 This option allows you to specify the maximum number of commands
1041 that can be queued to any device, when tagged command queuing is
1042 possible. The driver supports up to 256 queued commands per device.
1043 This value is used as a compiled-in hard limit.
1045 config SCSI_SYM53C8XX_MMIO
1046 bool "Use memory mapped IO"
1047 depends on SCSI_SYM53C8XX_2
1050 Memory mapped IO is faster than Port IO. Most people should
1051 answer Y here, but some machines may have problems. If you have
1052 to answer N here, please report the problem to the maintainer.
1055 tristate "IBM Power Linux RAID adapter support"
1056 depends on PCI && SCSI && ATA
1060 This driver supports the IBM Power Linux family RAID adapters.
1061 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1062 as IBM iSeries 5702, 5703, 5709, and 570A.
1064 config SCSI_IPR_TRACE
1065 bool "enable driver internal trace"
1069 If you say Y here, the driver will trace all commands issued
1070 to the adapter. Performance impact is minimal. Trace can be
1071 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1073 config SCSI_IPR_DUMP
1074 bool "enable adapter dump support"
1078 If you say Y here, the driver will support adapter crash dump.
1079 If you enable this support, the iprdump daemon can be used
1080 to capture adapter failure analysis information.
1083 tristate "Zalon SCSI support"
1084 depends on GSC && SCSI
1085 select SCSI_SPI_ATTRS
1087 The Zalon is a GSC/HSC bus interface chip that sits between the
1088 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1089 C110, J200, J210 and some D, K & R-class machines. It's also
1090 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1091 Say Y here if you have one of these machines or cards.
1093 config SCSI_NCR_Q720
1094 tristate "NCR Quad 720 MCA SCSI support"
1095 depends on MCA && SCSI
1096 select SCSI_SPI_ATTRS
1098 This is a driver for the MicroChannel Quad 720 card produced by
1099 NCR and commonly used in 345x/35xx/4100 class machines. It always
1100 tries to negotiate sync and uses tag command queueing.
1102 Unless you have an NCR manufactured machine, the chances are that
1103 you do not have this SCSI card, so say N.
1105 config SCSI_NCR53C8XX_DEFAULT_TAGS
1106 int "default tagged command queue depth"
1107 depends on SCSI_ZALON || SCSI_NCR_Q720
1110 "Tagged command queuing" is a feature of SCSI-2 which improves
1111 performance: the host adapter can send several SCSI commands to a
1112 device's queue even if previous commands haven't finished yet.
1113 Because the device is intelligent, it can optimize its operations
1114 (like head positioning) based on its own request queue. Some SCSI
1115 devices don't implement this properly; if you want to disable this
1116 feature, enter 0 or 1 here (it doesn't matter which).
1118 The default value is 8 and should be supported by most hard disks.
1119 This value can be overridden from the boot command line using the
1120 'tags' option as follows (example):
1121 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1122 4, set queue depth to 16 for target 2 and target 3 on controller 0
1123 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1125 The normal answer therefore is to go with the default 8 and to use
1126 a boot command line option for devices that need to use a different
1127 command queue depth.
1129 There is no safe option other than using good SCSI devices.
1131 config SCSI_NCR53C8XX_MAX_TAGS
1132 int "maximum number of queued commands"
1133 depends on SCSI_ZALON || SCSI_NCR_Q720
1136 This option allows you to specify the maximum number of commands
1137 that can be queued to any device, when tagged command queuing is
1138 possible. The default value is 32. Minimum is 2, maximum is 64.
1139 Modern hard disks are able to support 64 tags and even more, but
1140 do not seem to be faster when more than 32 tags are being used.
1142 So, the normal answer here is to go with the default value 32 unless
1143 you are using very large hard disks with large cache (>= 1 MB) that
1144 are able to take advantage of more than 32 tagged commands.
1146 There is no safe option and the default answer is recommended.
1148 config SCSI_NCR53C8XX_SYNC
1149 int "synchronous transfers frequency in MHz"
1150 depends on SCSI_ZALON || SCSI_NCR_Q720
1153 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1154 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1155 are respectively the maximum data transfer rates in mega-transfers
1156 per second for each class. For example, a FAST-20 Wide 16 device is
1157 able to transfer data at 20 million 16 bit packets per second for a
1158 total rate of 40 MB/s.
1160 You may specify 0 if you want to only use asynchronous data
1161 transfers. This is the safest and slowest option. Otherwise, specify
1162 a value between 5 and 80, depending on the capability of your SCSI
1163 controller. The higher the number, the faster the data transfer.
1164 Note that 80 should normally be ok since the driver decreases the
1165 value automatically according to the controller's capabilities.
1167 Your answer to this question is ignored for controllers with NVRAM,
1168 since the driver will get this information from the user set-up. It
1169 also can be overridden using a boot setup option, as follows
1170 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1171 for FAST-20 synchronous data transfer (20 mega-transfers per
1174 The normal answer therefore is not to go with the default but to
1175 select the maximum value 80 allowing the driver to use the maximum
1176 value supported by each controller. If this causes problems with
1177 your SCSI devices, you should come back and decrease the value.
1179 There is no safe option other than using good cabling, right
1180 terminations and SCSI conformant devices.
1182 config SCSI_NCR53C8XX_NO_DISCONNECT
1183 bool "not allow targets to disconnect"
1184 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1186 This option is only provided for safety if you suspect some SCSI
1187 device of yours to not support properly the target-disconnect
1188 feature. In that case, you would say Y here. In general however, to
1189 not allow targets to disconnect is not reasonable if there is more
1190 than 1 device on a SCSI bus. The normal answer therefore is N.
1192 config SCSI_QLOGIC_FAS
1193 tristate "Qlogic FAS SCSI support"
1194 depends on ISA && SCSI
1196 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1197 FastSCSI! cards as well as any other card based on the FASXX chip
1198 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1200 This driver does NOT support the PCI versions of these cards. The
1201 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1202 SCSI support"), below.
1204 Information about this driver is contained in
1205 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1206 SCSI-HOWTO, available from
1207 <http://www.tldp.org/docs.html#howto>.
1209 To compile this driver as a module, choose M here: the
1210 module will be called qlogicfas.
1212 config SCSI_QLOGIC_1280
1213 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1214 depends on PCI && SCSI
1216 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1218 To compile this driver as a module, choose M here: the
1219 module will be called qla1280.
1221 config SCSI_QLOGICPTI
1222 tristate "PTI Qlogic, ISP Driver"
1223 depends on SBUS && SCSI
1225 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1226 controllers are known under Solaris as qpti and in the openprom as
1227 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1228 driven by a different driver.
1230 To compile this driver as a module, choose M here: the
1231 module will be called qlogicpti.
1233 source "drivers/scsi/qla2xxx/Kconfig"
1234 source "drivers/scsi/qla4xxx/Kconfig"
1237 tristate "Emulex LightPulse Fibre Channel Support"
1238 depends on PCI && SCSI
1239 depends on SCSI_FC_ATTRS
1242 This lpfc driver supports the Emulex LightPulse
1243 Family of Fibre Channel PCI host adapters.
1245 config SCSI_LPFC_DEBUG_FS
1246 bool "Emulex LightPulse Fibre Channel debugfs Support"
1247 depends on SCSI_LPFC && DEBUG_FS
1249 This makes debugging information from the lpfc driver
1250 available via the debugfs filesystem.
1253 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1254 depends on (EISA || MCA) && SCSI
1255 select SCSI_SPI_ATTRS
1257 This driver is for NCR53c710 based SCSI host adapters.
1259 It currently supports Compaq EISA cards and NCR MCA cards
1261 config SCSI_SYM53C416
1262 tristate "Symbios 53c416 SCSI support"
1263 depends on ISA && SCSI
1265 This is support for the sym53c416 SCSI host adapter, the SCSI
1266 adapter that comes with some HP scanners. This driver requires that
1267 the sym53c416 is configured first using some sort of PnP
1268 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1269 are using isapnp then you need to compile this driver as a module
1270 and then load it using insmod after isapnp has run. The parameters
1271 of the configured card(s) should be passed to the driver. The format
1274 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1276 To compile this driver as a module, choose M here: the
1277 module will be called sym53c416.
1280 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1281 depends on PCI && SCSI
1283 This driver supports PCI SCSI host adapters based on the ASIC
1284 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1286 This driver works, but is still in experimental status. So better
1287 have a bootable disk and a backup in case of emergency.
1289 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1291 To compile this driver as a module, choose M here: the
1292 module will be called dc395x.
1294 config SCSI_AM53C974
1295 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1296 depends on PCI && SCSI
1297 select SCSI_SPI_ATTRS
1299 This driver supports PCI SCSI host adapters based on the Am53C974A
1300 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1301 PCscsi/PCnet (Am53/79C974) solutions.
1302 This is a new implementation base on the generic esp_scsi driver.
1304 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1306 Note that this driver does NOT support Tekram DC390W/U/F, which are
1307 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1309 To compile this driver as a module, choose M here: the
1310 module will be called am53c974.
1313 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1314 depends on PCI && SCSI && !64BIT
1316 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1317 SCSI host adapter. Please read the SCSI-HOWTO, available from
1318 <http://www.tldp.org/docs.html#howto>.
1320 To compile this driver as a module, choose M here: the
1321 module will be called nsp32.
1324 tristate "Western Digital WD7193/7197/7296 support"
1325 depends on PCI && SCSI
1328 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1329 SCSI controllers (based on WD33C296A chip).
1332 tristate "SCSI debugging host and device simulator"
1336 This pseudo driver simulates one or more hosts (SCSI initiators),
1337 each with one or more targets, each with one or more logical units.
1338 Defaults to one of each, creating a small RAM disk device. Many
1339 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1340 directory can be tweaked at run time.
1341 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1342 Mainly used for testing and best as a module. If unsure, say N.
1345 tristate "MESH (Power Mac internal SCSI) support"
1346 depends on PPC32 && PPC_PMAC && SCSI
1348 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1349 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1350 other Power Macintoshes do). Say Y to include support for this SCSI
1353 To compile this driver as a module, choose M here: the
1354 module will be called mesh.
1356 config SCSI_MESH_SYNC_RATE
1357 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1358 depends on SCSI_MESH
1361 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1362 drives a bus which is entirely internal to the machine (such as the
1363 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1364 operation at up to 10 MB/s. On machines where the SCSI bus
1365 controlled by the MESH can have external devices connected, it is
1366 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1367 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1368 to disable synchronous operation.
1370 config SCSI_MESH_RESET_DELAY_MS
1371 int "initial bus reset delay (ms) (0 = no reset)"
1372 depends on SCSI_MESH
1375 config SCSI_MAC53C94
1376 tristate "53C94 (Power Mac external SCSI) support"
1377 depends on PPC32 && PPC_PMAC && SCSI
1379 On Power Macintoshes (and clones) with two SCSI buses, the external
1380 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1381 machines which only have one SCSI bus, such as the 7200, also use
1382 the 53C94. Say Y to include support for the 53C94.
1384 To compile this driver as a module, choose M here: the
1385 module will be called mac53c94.
1387 source "drivers/scsi/arm/Kconfig"
1390 bool "MIPS JAZZ FAS216 SCSI support"
1391 depends on MACH_JAZZ && SCSI
1392 select SCSI_SPI_ATTRS
1394 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1395 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1399 tristate "A3000 WD33C93A support"
1400 depends on AMIGA && SCSI
1402 If you have an Amiga 3000 and have SCSI devices connected to the
1403 built-in SCSI controller, say Y. Otherwise, say N.
1405 To compile this driver as a module, choose M here: the
1406 module will be called a3000.
1409 tristate "A2091/A590 WD33C93A support"
1410 depends on ZORRO && SCSI
1412 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1415 To compile this driver as a module, choose M here: the
1416 module will be called a2091.
1419 tristate "GVP Series II WD33C93A support"
1420 depends on ZORRO && SCSI
1422 If you have a Great Valley Products Series II SCSI controller,
1423 answer Y. Also say Y if you have a later model of GVP SCSI
1424 controller (such as the GVP A4008 or a Combo board). Otherwise,
1425 answer N. This driver does NOT work for the T-Rex series of
1426 accelerators from TekMagic and GVP-M.
1428 To compile this driver as a module, choose M here: the
1429 module will be called gvp11.
1432 tristate "A4000T NCR53c710 SCSI support"
1433 depends on AMIGA && SCSI
1434 select SCSI_SPI_ATTRS
1436 If you have an Amiga 4000T and have SCSI devices connected to the
1437 built-in SCSI controller, say Y. Otherwise, say N.
1439 To compile this driver as a module, choose M here: the
1440 module will be called a4000t.
1442 config SCSI_ZORRO7XX
1443 tristate "Zorro NCR53c710 SCSI support"
1444 depends on ZORRO && SCSI
1445 select SCSI_SPI_ATTRS
1447 Support for various NCR53c710-based SCSI controllers on Zorro
1448 expansion boards for the Amiga.
1450 - the Amiga 4091 Zorro III SCSI-2 controller,
1451 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1453 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1454 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1455 accelerator card for the Amiga 1200,
1456 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1459 tristate "Atari native SCSI support"
1460 depends on ATARI && SCSI
1461 select SCSI_SPI_ATTRS
1464 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1465 Falcon, ...) say Y to get it supported. Of course also, if you have
1466 a compatible SCSI controller (e.g. for Medusa).
1468 To compile this driver as a module, choose M here: the
1469 module will be called atari_scsi.
1471 This driver supports both styles of NCR integration into the
1472 system: the TT style (separate DMA), and the Falcon style (via
1473 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1474 in the Hades (without DMA).
1477 tristate "Macintosh NCR5380 SCSI"
1478 depends on MAC && SCSI=y
1479 select SCSI_SPI_ATTRS
1481 This is the NCR 5380 SCSI controller included on most of the 68030
1482 based Macintoshes. If you have one of these say Y and read the
1483 SCSI-HOWTO, available from
1484 <http://www.tldp.org/docs.html#howto>.
1487 tristate "Macintosh NCR53c9[46] SCSI"
1488 depends on MAC && SCSI
1489 select SCSI_SPI_ATTRS
1491 This is the NCR 53c9x SCSI controller found on most of the 68040
1494 To compile this driver as a module, choose M here: the module
1495 will be called mac_esp.
1498 bool "WD33C93 SCSI driver for MVME147"
1499 depends on MVME147 && SCSI=y
1500 select SCSI_SPI_ATTRS
1502 Support for the on-board SCSI controller on the Motorola MVME147
1503 single-board computer.
1506 tristate "NCR53C710 SCSI driver for MVME16x"
1507 depends on MVME16x && SCSI
1508 select SCSI_SPI_ATTRS
1510 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1511 SCSI controller chip. Almost everyone using one of these boards
1512 will want to say Y to this question.
1514 config BVME6000_SCSI
1515 tristate "NCR53C710 SCSI driver for BVME6000"
1516 depends on BVME6000 && SCSI
1517 select SCSI_SPI_ATTRS
1519 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1520 SCSI controller chip. Almost everyone using one of these boards
1521 will want to say Y to this question.
1524 tristate "Sun3 NCR5380 SCSI"
1525 depends on SUN3 && SCSI
1526 select SCSI_SPI_ATTRS
1528 This option will enable support for the OBIO (onboard io) NCR5380
1529 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1530 "Sun3" type VME scsi controllers also based on the NCR5380.
1531 General Linux information on the Sun 3 series (now discontinued)
1532 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1535 bool "Sun3x ESP SCSI"
1536 depends on SUN3X && SCSI=y
1537 select SCSI_SPI_ATTRS
1539 The ESP was an on-board SCSI controller used on Sun 3/80
1540 machines. Say Y here to compile in support for it.
1543 tristate "Sparc ESP Scsi Driver"
1544 depends on SBUS && SCSI
1545 select SCSI_SPI_ATTRS
1547 This is the driver for the Sun ESP SCSI host adapter. The ESP
1548 chipset is present in most SPARC SBUS-based computers and
1549 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1550 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1552 To compile this driver as a module, choose M here: the
1553 module will be called sun_esp.
1556 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1557 depends on S390 && QDIO && SCSI
1558 depends on SCSI_FC_ATTRS
1560 If you want to access SCSI devices attached to your IBM eServer
1561 zSeries by means of Fibre Channel interfaces say Y.
1562 For details please refer to the documentation provided by IBM at
1563 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1565 This driver is also available as a module. This module will be
1566 called zfcp. If you want to compile it as a module, say M here
1567 and read <file:Documentation/kbuild/modules.txt>.
1570 tristate "PMC SIERRA Linux MaxRAID adapter support"
1571 depends on PCI && SCSI && NET
1573 This driver supports the PMC SIERRA MaxRAID adapters.
1576 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1577 depends on PCI && SCSI
1578 select SCSI_SAS_LIBSAS
1580 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1581 based host adapters.
1584 tristate "Brocade BFA Fibre Channel Support"
1585 depends on PCI && SCSI
1586 depends on SCSI_FC_ATTRS
1588 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1590 To compile this driver as a module, choose M here. The module will
1594 tristate "virtio-scsi support"
1597 This is the virtual HBA driver for virtio. If the kernel will
1598 be used in a virtual machine, say Y or M.
1600 source "drivers/scsi/csiostor/Kconfig"
1602 endif # SCSI_LOWLEVEL
1604 source "drivers/scsi/pcmcia/Kconfig"
1606 source "drivers/scsi/device_handler/Kconfig"
1608 source "drivers/scsi/osd/Kconfig"