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 "DTC3180/3280 SCSI support"
642 depends on ISA && SCSI
643 select SCSI_SPI_ATTRS
644 select CHECK_SIGNATURE
646 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
647 the SCSI-HOWTO, available from
648 <http://www.tldp.org/docs.html#howto>, and the file
649 <file:Documentation/scsi/dtc3x80.txt>.
651 To compile this driver as a module, choose M here: the
652 module will be called dtc.
655 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
656 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
658 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
659 ISA and all EISA I/O addresses are probed looking for the "EATA"
660 signature. The addresses of all the PCI SCSI controllers reported
661 by the PCI subsystem are probed as well.
663 You want to read the start of <file:drivers/scsi/eata.c> and the
664 SCSI-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>.
667 To compile this driver as a module, choose M here: the
668 module will be called eata.
670 config SCSI_EATA_TAGGED_QUEUE
671 bool "enable tagged command queueing"
674 This is a feature of SCSI-2 which improves performance: the host
675 adapter can send several SCSI commands to a device's queue even if
676 previous commands haven't finished yet.
677 This is equivalent to the "eata=tc:y" boot option.
679 config SCSI_EATA_LINKED_COMMANDS
680 bool "enable elevator sorting"
683 This option enables elevator sorting for all probed SCSI disks and
684 CD-ROMs. It definitely reduces the average seek distance when doing
685 random seeks, but this does not necessarily result in a noticeable
686 performance improvement: your mileage may vary...
687 This is equivalent to the "eata=lc:y" boot option.
689 config SCSI_EATA_MAX_TAGS
690 int "maximum number of queued commands"
694 This specifies how many SCSI commands can be maximally queued for
695 each probed SCSI device. You should reduce the default value of 16
696 only if you have disks with buggy or limited tagged command support.
697 Minimum is 2 and maximum is 62. This value is also the window size
698 used by the elevator sorting option above. The effective value used
699 by the driver for each probed SCSI device is reported at boot time.
700 This is equivalent to the "eata=mq:8" boot option.
703 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
704 depends on (ISA || EISA || PCI) && SCSI && BROKEN
706 This driver supports all EATA-PIO protocol compliant SCSI Host
707 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
708 host adapters could also use this driver but are discouraged from
709 doing so, since this driver only supports hard disks and lacks
710 numerous features. You might want to have a look at the SCSI-HOWTO,
711 available from <http://www.tldp.org/docs.html#howto>.
713 To compile this driver as a module, choose M here: the
714 module will be called eata_pio.
716 config SCSI_FUTURE_DOMAIN
717 tristate "Future Domain 16xx SCSI/AHA-2920A support"
718 depends on (ISA || PCI) && SCSI
719 select CHECK_SIGNATURE
721 This is support for Future Domain's 16-bit SCSI host adapters
722 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
723 other adapters based on the Future Domain chipsets (Quantum
724 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
725 It is explained in section 3.7 of the SCSI-HOWTO, available from
726 <http://www.tldp.org/docs.html#howto>.
728 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
729 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
730 controller support"). This Future Domain driver works with the older
731 Adaptec AHA-2920A boards with a Future Domain chip on them.
733 To compile this driver as a module, choose M here: the
734 module will be called fdomain.
737 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
738 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
740 Formerly called GDT SCSI Disk Array Controller Support.
742 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
743 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
744 in the kernel source in <file:drivers/scsi/gdth.c> and
745 <file:drivers/scsi/gdth.h>.
747 To compile this driver as a module, choose M here: the
748 module will be called gdth.
751 tristate "Intel(R) C600 Series Chipset SAS Controller"
752 depends on PCI && SCSI
754 select SCSI_SAS_LIBSAS
756 This driver supports the 6Gb/s SAS capabilities of the storage
757 control unit found in the Intel(R) C600 series chipset.
759 config SCSI_GENERIC_NCR5380
760 tristate "Generic NCR5380/53c400 SCSI PIO support"
761 depends on ISA && SCSI
762 select SCSI_SPI_ATTRS
764 This is a driver for the old NCR 53c80 series of SCSI controllers
765 on boards using PIO. Most boards such as the Trantor T130 fit this
766 category, along with a large number of ISA 8bit controllers shipped
767 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
768 you should select the specific driver for that card rather than
769 generic 5380 support.
771 It is explained in section 3.8 of the SCSI-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
773 of the box, you may have to change some settings in
774 <file:drivers/scsi/g_NCR5380.h>.
776 To compile this driver as a module, choose M here: the
777 module will be called g_NCR5380.
779 config SCSI_GENERIC_NCR5380_MMIO
780 tristate "Generic NCR5380/53c400 SCSI MMIO support"
781 depends on ISA && SCSI
782 select SCSI_SPI_ATTRS
784 This is a driver for the old NCR 53c80 series of SCSI controllers
785 on boards using memory mapped I/O.
786 It is explained in section 3.8 of the SCSI-HOWTO, available from
787 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
788 of the box, you may have to change some settings in
789 <file:drivers/scsi/g_NCR5380.h>.
791 To compile this driver as a module, choose M here: the
792 module will be called g_NCR5380_mmio.
795 tristate "IBM ServeRAID support"
796 depends on PCI && SCSI
798 This is support for the IBM ServeRAID hardware RAID controllers.
799 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
800 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
801 for more information. If this driver does not work correctly
802 without modification please contact the author by email at
803 <ipslinux@adaptec.com>.
805 To compile this driver as a module, choose M here: the
806 module will be called ips.
809 tristate "IBM Virtual SCSI support"
810 depends on PPC_PSERIES
811 select SCSI_SRP_ATTRS
813 This is the IBM POWER Virtual SCSI Client
815 To compile this driver as a module, choose M here: the
816 module will be called ibmvscsi.
818 config SCSI_IBMVSCSIS
819 tristate "IBM Virtual SCSI Server support"
820 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
822 This is the IBM POWER Virtual SCSI Target Server
823 This driver uses the SRP protocol for communication betwen servers
824 guest and/or the host that run on the same server.
825 More information on VSCSI protocol can be found at www.power.org
827 The userspace configuration needed to initialize the driver can be
830 https://github.com/powervm/ibmvscsis/wiki/Configuration
832 To compile this driver as a module, choose M here: the
833 module will be called ibmvscsis.
836 tristate "IBM Virtual FC support"
837 depends on PPC_PSERIES && SCSI
838 depends on SCSI_FC_ATTRS
840 This is the IBM POWER Virtual FC Client
842 To compile this driver as a module, choose M here: the
843 module will be called ibmvfc.
845 config SCSI_IBMVFC_TRACE
846 bool "enable driver internal trace"
847 depends on SCSI_IBMVFC
850 If you say Y here, the driver will trace all commands issued
851 to the adapter. Performance impact is minimal. Trace can be
852 dumped using /sys/class/scsi_host/hostXX/trace.
855 tristate "Initio 9100U(W) support"
856 depends on PCI && SCSI
858 This is support for the Initio 91XXU(W) SCSI host adapter. Please
859 read the SCSI-HOWTO, available from
860 <http://www.tldp.org/docs.html#howto>.
862 To compile this driver as a module, choose M here: the
863 module will be called initio.
866 tristate "Initio INI-A100U2W support"
867 depends on PCI && SCSI
869 This is support for the Initio INI-A100U2W SCSI host adapter.
870 Please 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 a100u2w.
877 tristate "IOMEGA parallel port (ppa - older drives)"
878 depends on SCSI && PARPORT_PC
880 This driver supports older versions of IOMEGA's parallel port ZIP
881 drive (a 100 MB removable media device).
883 Note that you can say N here if you have the SCSI version of the ZIP
884 drive: it will be supported automatically if you said Y to the
885 generic "SCSI disk support", above.
887 If you have the ZIP Plus drive or a more recent parallel port ZIP
888 drive (if the supplied cable with the drive is labeled "AutoDetect")
889 then you should say N here and Y to "IOMEGA parallel port (imm -
890 newer drives)", below.
892 For more information about this driver and how to use it you should
893 read the file <file:Documentation/scsi/ppa.txt>. You should also read
894 the SCSI-HOWTO, which is available from
895 <http://www.tldp.org/docs.html#howto>. If you use this driver,
896 you will still be able to use the parallel port for other tasks,
897 such as a printer; it is safe to compile both drivers into the
900 To compile this driver as a module, choose M here: the
901 module will be called ppa.
904 tristate "IOMEGA parallel port (imm - newer drives)"
905 depends on SCSI && PARPORT_PC
907 This driver supports newer versions of IOMEGA's parallel port ZIP
908 drive (a 100 MB removable media device).
910 Note that you can say N here if you have the SCSI version of the ZIP
911 drive: it will be supported automatically if you said Y to the
912 generic "SCSI disk support", above.
914 If you have the ZIP Plus drive or a more recent parallel port ZIP
915 drive (if the supplied cable with the drive is labeled "AutoDetect")
916 then you should say Y here; if you have an older ZIP drive, say N
917 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
919 For more information about this driver and how to use it you should
920 read the file <file:Documentation/scsi/ppa.txt>. You should also read
921 the SCSI-HOWTO, which is available from
922 <http://www.tldp.org/docs.html#howto>. If you use this driver,
923 you will still be able to use the parallel port for other tasks,
924 such as a printer; it is safe to compile both drivers into the
927 To compile this driver as a module, choose M here: the
928 module will be called imm.
930 config SCSI_IZIP_EPP16
931 bool "ppa/imm option - Use slow (but safe) EPP-16"
932 depends on SCSI_PPA || SCSI_IMM
934 EPP (Enhanced Parallel Port) is a standard for parallel ports which
935 allows them to act as expansion buses that can handle up to 64
938 Some parallel port chipsets are slower than their motherboard, and
939 so we have to control the state of the chipset's FIFO queue every
940 now and then to avoid data loss. This will be done if you say Y
943 Generally, saying Y is the safe option and slows things down a bit.
945 config SCSI_IZIP_SLOW_CTR
946 bool "ppa/imm option - Assume slow parport control register"
947 depends on SCSI_PPA || SCSI_IMM
949 Some parallel ports are known to have excessive delays between
950 changing the parallel port control register and good data being
951 available on the parallel port data/status register. This option
952 forces a small delay (1.0 usec to be exact) after changing the
953 control register to let things settle out. Enabling this option may
954 result in a big drop in performance but some very old parallel ports
955 (found in 386 vintage machines) will not work properly.
957 Generally, saying N is fine.
959 config SCSI_NCR53C406A
960 tristate "NCR53c406a SCSI support"
961 depends on ISA && SCSI
963 This is support for the NCR53c406a SCSI host adapter. For user
964 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
965 in the kernel source. Also read the SCSI-HOWTO, available from
966 <http://www.tldp.org/docs.html#howto>.
968 To compile this driver as a module, choose M here: the
969 module will be called NCR53c406.
972 tristate "NCR Dual 700 MCA SCSI support"
973 depends on MCA && SCSI
974 select SCSI_SPI_ATTRS
976 This is a driver for the MicroChannel Dual 700 card produced by
977 NCR and commonly used in 345x/35xx/4100 class machines. It always
978 tries to negotiate sync and uses tag command queueing.
980 Unless you have an NCR manufactured machine, the chances are that
981 you do not have this SCSI card, so say N.
984 tristate "HP Lasi SCSI support for 53c700/710"
985 depends on GSC && SCSI
986 select SCSI_SPI_ATTRS
988 This is a driver for the SCSI controller in the Lasi chip found in
989 many PA-RISC workstations & servers. If you do not know whether you
990 have a Lasi chip, it is safe to say "Y" here.
992 config SCSI_SNI_53C710
993 tristate "SNI RM SCSI support for 53c710"
994 depends on SNI_RM && SCSI
995 select SCSI_SPI_ATTRS
996 select 53C700_LE_ON_BE
998 This is a driver for the onboard SCSI controller found in older
999 SNI RM workstations & servers.
1001 config 53C700_LE_ON_BE
1003 depends on SCSI_LASI700
1007 tristate "Promise SuperTrak EX Series support"
1008 depends on PCI && SCSI
1010 This driver supports Promise SuperTrak EX series storage controllers.
1012 Promise provides Linux RAID configuration utility for these
1013 controllers. Please visit <http://www.promise.com> to download.
1015 To compile this driver as a module, choose M here: the
1016 module will be called stex.
1018 config 53C700_BE_BUS
1020 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1023 config SCSI_SYM53C8XX_2
1024 tristate "SYM53C8XX Version 2 SCSI support"
1025 depends on PCI && SCSI
1026 select SCSI_SPI_ATTRS
1028 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1029 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1030 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1031 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1032 controllers; you need to use the Fusion MPT driver for that.
1034 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1037 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1038 int "DMA addressing mode"
1039 depends on SCSI_SYM53C8XX_2
1042 This option only applies to PCI-SCSI chips that are PCI DAC
1043 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1045 When set to 0, the driver will program the chip to only perform
1046 32-bit DMA. When set to 1, the chip will be able to perform DMA
1047 to addresses up to 1TB. When set to 2, the driver supports the
1048 full 64-bit DMA address range, but can only address 16 segments
1049 of 4 GB each. This limits the total addressable range to 64 GB.
1051 Most machines with less than 4GB of memory should use a setting
1052 of 0 for best performance. If your machine has 4GB of memory
1053 or more, you should set this option to 1 (the default).
1055 The still experimental value 2 (64 bit DMA addressing with 16
1056 x 4GB segments limitation) can be used on systems that require
1057 PCI address bits past bit 39 to be set for the addressing of
1058 memory using PCI DAC cycles.
1060 config SCSI_SYM53C8XX_DEFAULT_TAGS
1061 int "Default tagged command queue depth"
1062 depends on SCSI_SYM53C8XX_2
1065 This is the default value of the command queue depth the
1066 driver will announce to the generic SCSI layer for devices
1067 that support tagged command queueing. This value can be changed
1068 from the boot command line. This is a soft limit that cannot
1069 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1071 config SCSI_SYM53C8XX_MAX_TAGS
1072 int "Maximum number of queued commands"
1073 depends on SCSI_SYM53C8XX_2
1076 This option allows you to specify the maximum number of commands
1077 that can be queued to any device, when tagged command queuing is
1078 possible. The driver supports up to 256 queued commands per device.
1079 This value is used as a compiled-in hard limit.
1081 config SCSI_SYM53C8XX_MMIO
1082 bool "Use memory mapped IO"
1083 depends on SCSI_SYM53C8XX_2
1086 Memory mapped IO is faster than Port IO. Most people should
1087 answer Y here, but some machines may have problems. If you have
1088 to answer N here, please report the problem to the maintainer.
1091 tristate "IBM Power Linux RAID adapter support"
1092 depends on PCI && SCSI && ATA
1096 This driver supports the IBM Power Linux family RAID adapters.
1097 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1098 as IBM iSeries 5702, 5703, 5709, and 570A.
1100 config SCSI_IPR_TRACE
1101 bool "enable driver internal trace"
1105 If you say Y here, the driver will trace all commands issued
1106 to the adapter. Performance impact is minimal. Trace can be
1107 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1109 config SCSI_IPR_DUMP
1110 bool "enable adapter dump support"
1114 If you say Y here, the driver will support adapter crash dump.
1115 If you enable this support, the iprdump daemon can be used
1116 to capture adapter failure analysis information.
1119 tristate "Zalon SCSI support"
1120 depends on GSC && SCSI
1121 select SCSI_SPI_ATTRS
1123 The Zalon is a GSC/HSC bus interface chip that sits between the
1124 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1125 C110, J200, J210 and some D, K & R-class machines. It's also
1126 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1127 Say Y here if you have one of these machines or cards.
1129 config SCSI_NCR_Q720
1130 tristate "NCR Quad 720 MCA SCSI support"
1131 depends on MCA && SCSI
1132 select SCSI_SPI_ATTRS
1134 This is a driver for the MicroChannel Quad 720 card produced by
1135 NCR and commonly used in 345x/35xx/4100 class machines. It always
1136 tries to negotiate sync and uses tag command queueing.
1138 Unless you have an NCR manufactured machine, the chances are that
1139 you do not have this SCSI card, so say N.
1141 config SCSI_NCR53C8XX_DEFAULT_TAGS
1142 int "default tagged command queue depth"
1143 depends on SCSI_ZALON || SCSI_NCR_Q720
1146 "Tagged command queuing" is a feature of SCSI-2 which improves
1147 performance: the host adapter can send several SCSI commands to a
1148 device's queue even if previous commands haven't finished yet.
1149 Because the device is intelligent, it can optimize its operations
1150 (like head positioning) based on its own request queue. Some SCSI
1151 devices don't implement this properly; if you want to disable this
1152 feature, enter 0 or 1 here (it doesn't matter which).
1154 The default value is 8 and should be supported by most hard disks.
1155 This value can be overridden from the boot command line using the
1156 'tags' option as follows (example):
1157 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1158 4, set queue depth to 16 for target 2 and target 3 on controller 0
1159 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1161 The normal answer therefore is to go with the default 8 and to use
1162 a boot command line option for devices that need to use a different
1163 command queue depth.
1165 There is no safe option other than using good SCSI devices.
1167 config SCSI_NCR53C8XX_MAX_TAGS
1168 int "maximum number of queued commands"
1169 depends on SCSI_ZALON || SCSI_NCR_Q720
1172 This option allows you to specify the maximum number of commands
1173 that can be queued to any device, when tagged command queuing is
1174 possible. The default value is 32. Minimum is 2, maximum is 64.
1175 Modern hard disks are able to support 64 tags and even more, but
1176 do not seem to be faster when more than 32 tags are being used.
1178 So, the normal answer here is to go with the default value 32 unless
1179 you are using very large hard disks with large cache (>= 1 MB) that
1180 are able to take advantage of more than 32 tagged commands.
1182 There is no safe option and the default answer is recommended.
1184 config SCSI_NCR53C8XX_SYNC
1185 int "synchronous transfers frequency in MHz"
1186 depends on SCSI_ZALON || SCSI_NCR_Q720
1189 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1190 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1191 are respectively the maximum data transfer rates in mega-transfers
1192 per second for each class. For example, a FAST-20 Wide 16 device is
1193 able to transfer data at 20 million 16 bit packets per second for a
1194 total rate of 40 MB/s.
1196 You may specify 0 if you want to only use asynchronous data
1197 transfers. This is the safest and slowest option. Otherwise, specify
1198 a value between 5 and 80, depending on the capability of your SCSI
1199 controller. The higher the number, the faster the data transfer.
1200 Note that 80 should normally be ok since the driver decreases the
1201 value automatically according to the controller's capabilities.
1203 Your answer to this question is ignored for controllers with NVRAM,
1204 since the driver will get this information from the user set-up. It
1205 also can be overridden using a boot setup option, as follows
1206 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1207 for FAST-20 synchronous data transfer (20 mega-transfers per
1210 The normal answer therefore is not to go with the default but to
1211 select the maximum value 80 allowing the driver to use the maximum
1212 value supported by each controller. If this causes problems with
1213 your SCSI devices, you should come back and decrease the value.
1215 There is no safe option other than using good cabling, right
1216 terminations and SCSI conformant devices.
1218 config SCSI_NCR53C8XX_NO_DISCONNECT
1219 bool "not allow targets to disconnect"
1220 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1222 This option is only provided for safety if you suspect some SCSI
1223 device of yours to not support properly the target-disconnect
1224 feature. In that case, you would say Y here. In general however, to
1225 not allow targets to disconnect is not reasonable if there is more
1226 than 1 device on a SCSI bus. The normal answer therefore is N.
1229 tristate "PAS16 SCSI support"
1230 depends on ISA && SCSI
1231 select SCSI_SPI_ATTRS
1233 This is support for a SCSI host adapter. It is explained in section
1234 3.10 of the SCSI-HOWTO, available from
1235 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1236 of the box, you may have to change some settings in
1237 <file:drivers/scsi/pas16.h>.
1239 To compile this driver as a module, choose M here: the
1240 module will be called pas16.
1242 config SCSI_QLOGIC_FAS
1243 tristate "Qlogic FAS SCSI support"
1244 depends on ISA && SCSI
1246 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1247 FastSCSI! cards as well as any other card based on the FASXX chip
1248 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1250 This driver does NOT support the PCI versions of these cards. The
1251 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1252 SCSI support"), below.
1254 Information about this driver is contained in
1255 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1256 SCSI-HOWTO, available from
1257 <http://www.tldp.org/docs.html#howto>.
1259 To compile this driver as a module, choose M here: the
1260 module will be called qlogicfas.
1262 config SCSI_QLOGIC_1280
1263 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1264 depends on PCI && SCSI
1266 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1268 To compile this driver as a module, choose M here: the
1269 module will be called qla1280.
1271 config SCSI_QLOGICPTI
1272 tristate "PTI Qlogic, ISP Driver"
1273 depends on SBUS && SCSI
1275 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1276 controllers are known under Solaris as qpti and in the openprom as
1277 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1278 driven by a different driver.
1280 To compile this driver as a module, choose M here: the
1281 module will be called qlogicpti.
1283 source "drivers/scsi/qla2xxx/Kconfig"
1284 source "drivers/scsi/qla4xxx/Kconfig"
1287 tristate "Emulex LightPulse Fibre Channel Support"
1288 depends on PCI && SCSI
1289 depends on SCSI_FC_ATTRS
1292 This lpfc driver supports the Emulex LightPulse
1293 Family of Fibre Channel PCI host adapters.
1295 config SCSI_LPFC_DEBUG_FS
1296 bool "Emulex LightPulse Fibre Channel debugfs Support"
1297 depends on SCSI_LPFC && DEBUG_FS
1299 This makes debugging information from the lpfc driver
1300 available via the debugfs filesystem.
1303 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1304 depends on (EISA || MCA) && SCSI
1305 select SCSI_SPI_ATTRS
1307 This driver is for NCR53c710 based SCSI host adapters.
1309 It currently supports Compaq EISA cards and NCR MCA cards
1311 config SCSI_SYM53C416
1312 tristate "Symbios 53c416 SCSI support"
1313 depends on ISA && SCSI
1315 This is support for the sym53c416 SCSI host adapter, the SCSI
1316 adapter that comes with some HP scanners. This driver requires that
1317 the sym53c416 is configured first using some sort of PnP
1318 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1319 are using isapnp then you need to compile this driver as a module
1320 and then load it using insmod after isapnp has run. The parameters
1321 of the configured card(s) should be passed to the driver. The format
1324 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1326 To compile this driver as a module, choose M here: the
1327 module will be called sym53c416.
1330 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1331 depends on PCI && SCSI
1333 This driver supports PCI SCSI host adapters based on the ASIC
1334 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1336 This driver works, but is still in experimental status. So better
1337 have a bootable disk and a backup in case of emergency.
1339 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1341 To compile this driver as a module, choose M here: the
1342 module will be called dc395x.
1344 config SCSI_AM53C974
1345 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1346 depends on PCI && SCSI
1347 select SCSI_SPI_ATTRS
1349 This driver supports PCI SCSI host adapters based on the Am53C974A
1350 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1351 PCscsi/PCnet (Am53/79C974) solutions.
1352 This is a new implementation base on the generic esp_scsi driver.
1354 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1356 Note that this driver does NOT support Tekram DC390W/U/F, which are
1357 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1359 To compile this driver as a module, choose M here: the
1360 module will be called am53c974.
1363 tristate "Trantor T128/T128F/T228 SCSI support"
1364 depends on ISA && SCSI
1365 select SCSI_SPI_ATTRS
1366 select CHECK_SIGNATURE
1368 This is support for a SCSI host adapter. It is explained in section
1369 3.11 of the SCSI-HOWTO, available from
1370 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1371 of the box, you may have to change some settings in
1372 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1373 Adaptec, and some former Trantor products are being sold under the
1376 To compile this driver as a module, choose M here: the
1377 module will be called t128.
1380 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1381 depends on PCI && SCSI && !64BIT
1383 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1384 SCSI host adapter. Please read the SCSI-HOWTO, available from
1385 <http://www.tldp.org/docs.html#howto>.
1387 To compile this driver as a module, choose M here: the
1388 module will be called nsp32.
1391 tristate "Western Digital WD7193/7197/7296 support"
1392 depends on PCI && SCSI
1395 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1396 SCSI controllers (based on WD33C296A chip).
1399 tristate "SCSI debugging host and device simulator"
1403 This pseudo driver simulates one or more hosts (SCSI initiators),
1404 each with one or more targets, each with one or more logical units.
1405 Defaults to one of each, creating a small RAM disk device. Many
1406 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1407 directory can be tweaked at run time.
1408 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1409 Mainly used for testing and best as a module. If unsure, say N.
1412 tristate "MESH (Power Mac internal SCSI) support"
1413 depends on PPC32 && PPC_PMAC && SCSI
1415 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1416 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1417 other Power Macintoshes do). Say Y to include support for this SCSI
1420 To compile this driver as a module, choose M here: the
1421 module will be called mesh.
1423 config SCSI_MESH_SYNC_RATE
1424 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1425 depends on SCSI_MESH
1428 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1429 drives a bus which is entirely internal to the machine (such as the
1430 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1431 operation at up to 10 MB/s. On machines where the SCSI bus
1432 controlled by the MESH can have external devices connected, it is
1433 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1434 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1435 to disable synchronous operation.
1437 config SCSI_MESH_RESET_DELAY_MS
1438 int "initial bus reset delay (ms) (0 = no reset)"
1439 depends on SCSI_MESH
1442 config SCSI_MAC53C94
1443 tristate "53C94 (Power Mac external SCSI) support"
1444 depends on PPC32 && PPC_PMAC && SCSI
1446 On Power Macintoshes (and clones) with two SCSI buses, the external
1447 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1448 machines which only have one SCSI bus, such as the 7200, also use
1449 the 53C94. Say Y to include support for the 53C94.
1451 To compile this driver as a module, choose M here: the
1452 module will be called mac53c94.
1454 source "drivers/scsi/arm/Kconfig"
1457 bool "MIPS JAZZ FAS216 SCSI support"
1458 depends on MACH_JAZZ && SCSI
1459 select SCSI_SPI_ATTRS
1461 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1462 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1466 tristate "A3000 WD33C93A support"
1467 depends on AMIGA && SCSI
1469 If you have an Amiga 3000 and have SCSI devices connected to the
1470 built-in SCSI controller, say Y. Otherwise, say N.
1472 To compile this driver as a module, choose M here: the
1473 module will be called a3000.
1476 tristate "A2091/A590 WD33C93A support"
1477 depends on ZORRO && SCSI
1479 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1482 To compile this driver as a module, choose M here: the
1483 module will be called a2091.
1486 tristate "GVP Series II WD33C93A support"
1487 depends on ZORRO && SCSI
1489 If you have a Great Valley Products Series II SCSI controller,
1490 answer Y. Also say Y if you have a later model of GVP SCSI
1491 controller (such as the GVP A4008 or a Combo board). Otherwise,
1492 answer N. This driver does NOT work for the T-Rex series of
1493 accelerators from TekMagic and GVP-M.
1495 To compile this driver as a module, choose M here: the
1496 module will be called gvp11.
1499 tristate "A4000T NCR53c710 SCSI support"
1500 depends on AMIGA && SCSI
1501 select SCSI_SPI_ATTRS
1503 If you have an Amiga 4000T and have SCSI devices connected to the
1504 built-in SCSI controller, say Y. Otherwise, say N.
1506 To compile this driver as a module, choose M here: the
1507 module will be called a4000t.
1509 config SCSI_ZORRO7XX
1510 tristate "Zorro NCR53c710 SCSI support"
1511 depends on ZORRO && SCSI
1512 select SCSI_SPI_ATTRS
1514 Support for various NCR53c710-based SCSI controllers on Zorro
1515 expansion boards for the Amiga.
1517 - the Amiga 4091 Zorro III SCSI-2 controller,
1518 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1520 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1521 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1522 accelerator card for the Amiga 1200,
1523 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1526 tristate "Atari native SCSI support"
1527 depends on ATARI && SCSI
1528 select SCSI_SPI_ATTRS
1531 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1532 Falcon, ...) say Y to get it supported. Of course also, if you have
1533 a compatible SCSI controller (e.g. for Medusa).
1535 To compile this driver as a module, choose M here: the
1536 module will be called atari_scsi.
1538 This driver supports both styles of NCR integration into the
1539 system: the TT style (separate DMA), and the Falcon style (via
1540 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1541 in the Hades (without DMA).
1544 tristate "Macintosh NCR5380 SCSI"
1545 depends on MAC && SCSI=y
1546 select SCSI_SPI_ATTRS
1548 This is the NCR 5380 SCSI controller included on most of the 68030
1549 based Macintoshes. If you have one of these say Y and read the
1550 SCSI-HOWTO, available from
1551 <http://www.tldp.org/docs.html#howto>.
1554 tristate "Macintosh NCR53c9[46] SCSI"
1555 depends on MAC && SCSI
1556 select SCSI_SPI_ATTRS
1558 This is the NCR 53c9x SCSI controller found on most of the 68040
1561 To compile this driver as a module, choose M here: the module
1562 will be called mac_esp.
1565 bool "WD33C93 SCSI driver for MVME147"
1566 depends on MVME147 && SCSI=y
1567 select SCSI_SPI_ATTRS
1569 Support for the on-board SCSI controller on the Motorola MVME147
1570 single-board computer.
1573 tristate "NCR53C710 SCSI driver for MVME16x"
1574 depends on MVME16x && SCSI
1575 select SCSI_SPI_ATTRS
1577 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1578 SCSI controller chip. Almost everyone using one of these boards
1579 will want to say Y to this question.
1581 config BVME6000_SCSI
1582 tristate "NCR53C710 SCSI driver for BVME6000"
1583 depends on BVME6000 && SCSI
1584 select SCSI_SPI_ATTRS
1586 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1587 SCSI controller chip. Almost everyone using one of these boards
1588 will want to say Y to this question.
1591 tristate "Sun3 NCR5380 SCSI"
1592 depends on SUN3 && SCSI
1593 select SCSI_SPI_ATTRS
1595 This option will enable support for the OBIO (onboard io) NCR5380
1596 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1597 "Sun3" type VME scsi controllers also based on the NCR5380.
1598 General Linux information on the Sun 3 series (now discontinued)
1599 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1602 bool "Sun3x ESP SCSI"
1603 depends on SUN3X && SCSI=y
1604 select SCSI_SPI_ATTRS
1606 The ESP was an on-board SCSI controller used on Sun 3/80
1607 machines. Say Y here to compile in support for it.
1610 tristate "Sparc ESP Scsi Driver"
1611 depends on SBUS && SCSI
1612 select SCSI_SPI_ATTRS
1614 This is the driver for the Sun ESP SCSI host adapter. The ESP
1615 chipset is present in most SPARC SBUS-based computers and
1616 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1617 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1619 To compile this driver as a module, choose M here: the
1620 module will be called sun_esp.
1623 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1624 depends on S390 && QDIO && SCSI
1625 depends on SCSI_FC_ATTRS
1627 If you want to access SCSI devices attached to your IBM eServer
1628 zSeries by means of Fibre Channel interfaces say Y.
1629 For details please refer to the documentation provided by IBM at
1630 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1632 This driver is also available as a module. This module will be
1633 called zfcp. If you want to compile it as a module, say M here
1634 and read <file:Documentation/kbuild/modules.txt>.
1637 tristate "PMC SIERRA Linux MaxRAID adapter support"
1638 depends on PCI && SCSI && NET
1640 This driver supports the PMC SIERRA MaxRAID adapters.
1643 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1644 depends on PCI && SCSI
1645 select SCSI_SAS_LIBSAS
1647 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1648 based host adapters.
1651 tristate "Brocade BFA Fibre Channel Support"
1652 depends on PCI && SCSI
1653 depends on SCSI_FC_ATTRS
1655 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1657 To compile this driver as a module, choose M here. The module will
1661 tristate "virtio-scsi support"
1664 This is the virtual HBA driver for virtio. If the kernel will
1665 be used in a virtual machine, say Y or M.
1667 source "drivers/scsi/csiostor/Kconfig"
1669 endif # SCSI_LOWLEVEL
1671 source "drivers/scsi/pcmcia/Kconfig"
1673 source "drivers/scsi/device_handler/Kconfig"
1675 source "drivers/scsi/osd/Kconfig"