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 "Always IN2000 SCSI support"
505 depends on ISA && SCSI
507 This is support for an ISA bus SCSI host adapter. You'll find more
508 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
509 out of the box, you may have to change the jumpers for IRQ or
512 To compile this driver as a module, choose M here: the
513 module will be called in2000.
516 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
517 depends on PCI && SCSI
519 This driver supports all of ARECA's SATA/SAS RAID controller cards.
520 This is an ARECA-maintained driver by Erich Chen.
521 If you have any problems, please mail to: <erich@areca.com.tw>.
522 Areca supports Linux RAID config tools.
523 Please link <http://www.areca.com.tw>
525 To compile this driver as a module, choose M here: the
526 module will be called arcmsr (modprobe arcmsr).
528 source "drivers/scsi/esas2r/Kconfig"
529 source "drivers/scsi/megaraid/Kconfig.megaraid"
530 source "drivers/scsi/mpt3sas/Kconfig"
531 source "drivers/scsi/smartpqi/Kconfig"
532 source "drivers/scsi/ufs/Kconfig"
535 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
536 depends on SCSI && PCI
538 This option enables support for HighPoint RocketRAID 3xxx/4xxx
541 To compile this driver as a module, choose M here; the module
542 will be called hptiop. If unsure, say N.
545 tristate "BusLogic SCSI support"
546 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
548 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
549 Adapters. Consult the SCSI-HOWTO, available from
550 <http://www.tldp.org/docs.html#howto>, and the files
551 <file:Documentation/scsi/BusLogic.txt> and
552 <file:Documentation/scsi/FlashPoint.txt> for more information.
553 Note that support for FlashPoint is only available for 32-bit
556 To compile this driver as a module, choose M here: the
557 module will be called BusLogic.
559 config SCSI_FLASHPOINT
560 bool "FlashPoint support"
561 depends on SCSI_BUSLOGIC && PCI
563 This option allows you to add FlashPoint support to the
564 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
565 substantial, so users of MultiMaster Host Adapters may not
569 tristate "VMware PVSCSI driver support"
570 depends on PCI && SCSI && X86
572 This driver supports VMware's para virtualized SCSI HBA.
573 To compile this driver as a module, choose M here: the
574 module will be called vmw_pvscsi.
576 config XEN_SCSI_FRONTEND
577 tristate "XEN SCSI frontend driver"
578 depends on SCSI && XEN
579 select XEN_XENBUS_FRONTEND
581 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
582 within another guest OS (usually Dom0).
583 Only needed if the kernel is running in a XEN guest and generic
584 SCSI access to a device is needed.
586 config HYPERV_STORAGE
587 tristate "Microsoft Hyper-V virtual storage driver"
588 depends on SCSI && HYPERV
589 depends on m || SCSI_FC_ATTRS != m
592 Select this option to enable the Hyper-V virtual storage driver.
595 tristate "LibFC module"
596 depends on SCSI_FC_ATTRS
599 Fibre Channel library module
602 tristate "LibFCoE module"
605 Library for Fibre Channel over Ethernet module
608 tristate "FCoE module"
612 Fibre Channel over Ethernet module
615 tristate "Cisco FNIC Driver"
616 depends on PCI && X86
619 This is support for the Cisco PCI-Express FCoE HBA.
621 To compile this driver as a module, choose M here and read
622 <file:Documentation/scsi/scsi.txt>.
623 The module will be called fnic.
626 tristate "Cisco SNIC Driver"
627 depends on PCI && SCSI
629 This is support for the Cisco PCI-Express SCSI HBA.
631 To compile this driver as a module, choose M here and read
632 <file:Documentation/scsi/scsi.txt>.
633 The module will be called snic.
635 config SCSI_SNIC_DEBUG_FS
636 bool "Cisco SNIC Driver Debugfs Support"
637 depends on SCSI_SNIC && DEBUG_FS
639 This enables to list debugging information from SNIC Driver
640 available via debugfs file system
643 tristate "DMX3191D SCSI support"
644 depends on PCI && SCSI
645 select SCSI_SPI_ATTRS
647 This is support for Domex DMX3191D SCSI Host Adapters.
649 To compile this driver as a module, choose M here: the
650 module will be called dmx3191d.
653 tristate "DTC3180/3280 SCSI support"
654 depends on ISA && SCSI
655 select SCSI_SPI_ATTRS
656 select CHECK_SIGNATURE
658 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
659 the SCSI-HOWTO, available from
660 <http://www.tldp.org/docs.html#howto>, and the file
661 <file:Documentation/scsi/dtc3x80.txt>.
663 To compile this driver as a module, choose M here: the
664 module will be called dtc.
667 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
668 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
670 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
671 ISA and all EISA I/O addresses are probed looking for the "EATA"
672 signature. The addresses of all the PCI SCSI controllers reported
673 by the PCI subsystem are probed as well.
675 You want to read the start of <file:drivers/scsi/eata.c> and the
676 SCSI-HOWTO, available from
677 <http://www.tldp.org/docs.html#howto>.
679 To compile this driver as a module, choose M here: the
680 module will be called eata.
682 config SCSI_EATA_TAGGED_QUEUE
683 bool "enable tagged command queueing"
686 This is a feature of SCSI-2 which improves performance: the host
687 adapter can send several SCSI commands to a device's queue even if
688 previous commands haven't finished yet.
689 This is equivalent to the "eata=tc:y" boot option.
691 config SCSI_EATA_LINKED_COMMANDS
692 bool "enable elevator sorting"
695 This option enables elevator sorting for all probed SCSI disks and
696 CD-ROMs. It definitely reduces the average seek distance when doing
697 random seeks, but this does not necessarily result in a noticeable
698 performance improvement: your mileage may vary...
699 This is equivalent to the "eata=lc:y" boot option.
701 config SCSI_EATA_MAX_TAGS
702 int "maximum number of queued commands"
706 This specifies how many SCSI commands can be maximally queued for
707 each probed SCSI device. You should reduce the default value of 16
708 only if you have disks with buggy or limited tagged command support.
709 Minimum is 2 and maximum is 62. This value is also the window size
710 used by the elevator sorting option above. The effective value used
711 by the driver for each probed SCSI device is reported at boot time.
712 This is equivalent to the "eata=mq:8" boot option.
715 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
716 depends on (ISA || EISA || PCI) && SCSI && BROKEN
718 This driver supports all EATA-PIO protocol compliant SCSI Host
719 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
720 host adapters could also use this driver but are discouraged from
721 doing so, since this driver only supports hard disks and lacks
722 numerous features. You might want to have a look at the SCSI-HOWTO,
723 available from <http://www.tldp.org/docs.html#howto>.
725 To compile this driver as a module, choose M here: the
726 module will be called eata_pio.
728 config SCSI_FUTURE_DOMAIN
729 tristate "Future Domain 16xx SCSI/AHA-2920A support"
730 depends on (ISA || PCI) && SCSI
731 select CHECK_SIGNATURE
733 This is support for Future Domain's 16-bit SCSI host adapters
734 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
735 other adapters based on the Future Domain chipsets (Quantum
736 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
737 It is explained in section 3.7 of the SCSI-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>.
740 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
741 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
742 controller support"). This Future Domain driver works with the older
743 Adaptec AHA-2920A boards with a Future Domain chip on them.
745 To compile this driver as a module, choose M here: the
746 module will be called fdomain.
749 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
750 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
752 Formerly called GDT SCSI Disk Array Controller Support.
754 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
755 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
756 in the kernel source in <file:drivers/scsi/gdth.c> and
757 <file:drivers/scsi/gdth.h>.
759 To compile this driver as a module, choose M here: the
760 module will be called gdth.
763 tristate "Intel(R) C600 Series Chipset SAS Controller"
764 depends on PCI && SCSI
766 select SCSI_SAS_LIBSAS
768 This driver supports the 6Gb/s SAS capabilities of the storage
769 control unit found in the Intel(R) C600 series chipset.
771 config SCSI_GENERIC_NCR5380
772 tristate "Generic NCR5380/53c400 SCSI PIO support"
773 depends on ISA && SCSI
774 select SCSI_SPI_ATTRS
776 This is a driver for the old NCR 53c80 series of SCSI controllers
777 on boards using PIO. Most boards such as the Trantor T130 fit this
778 category, along with a large number of ISA 8bit controllers shipped
779 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
780 you should select the specific driver for that card rather than
781 generic 5380 support.
783 It is explained in section 3.8 of the SCSI-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
785 of the box, you may have to change some settings in
786 <file:drivers/scsi/g_NCR5380.h>.
788 To compile this driver as a module, choose M here: the
789 module will be called g_NCR5380.
791 config SCSI_GENERIC_NCR5380_MMIO
792 tristate "Generic NCR5380/53c400 SCSI MMIO support"
793 depends on ISA && SCSI
794 select SCSI_SPI_ATTRS
796 This is a driver for the old NCR 53c80 series of SCSI controllers
797 on boards using memory mapped I/O.
798 It is explained in section 3.8 of the SCSI-HOWTO, available from
799 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
800 of the box, you may have to change some settings in
801 <file:drivers/scsi/g_NCR5380.h>.
803 To compile this driver as a module, choose M here: the
804 module will be called g_NCR5380_mmio.
807 tristate "IBM ServeRAID support"
808 depends on PCI && SCSI
810 This is support for the IBM ServeRAID hardware RAID controllers.
811 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
812 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
813 for more information. If this driver does not work correctly
814 without modification please contact the author by email at
815 <ipslinux@adaptec.com>.
817 To compile this driver as a module, choose M here: the
818 module will be called ips.
821 tristate "IBM Virtual SCSI support"
822 depends on PPC_PSERIES
823 select SCSI_SRP_ATTRS
825 This is the IBM POWER Virtual SCSI Client
827 To compile this driver as a module, choose M here: the
828 module will be called ibmvscsi.
830 config SCSI_IBMVSCSIS
831 tristate "IBM Virtual SCSI Server support"
832 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
834 This is the IBM POWER Virtual SCSI Target Server
835 This driver uses the SRP protocol for communication betwen servers
836 guest and/or the host that run on the same server.
837 More information on VSCSI protocol can be found at www.power.org
839 The userspace configuration needed to initialize the driver can be
842 https://github.com/powervm/ibmvscsis/wiki/Configuration
844 To compile this driver as a module, choose M here: the
845 module will be called ibmvscsis.
848 tristate "IBM Virtual FC support"
849 depends on PPC_PSERIES && SCSI
850 depends on SCSI_FC_ATTRS
852 This is the IBM POWER Virtual FC Client
854 To compile this driver as a module, choose M here: the
855 module will be called ibmvfc.
857 config SCSI_IBMVFC_TRACE
858 bool "enable driver internal trace"
859 depends on SCSI_IBMVFC
862 If you say Y here, the driver will trace all commands issued
863 to the adapter. Performance impact is minimal. Trace can be
864 dumped using /sys/class/scsi_host/hostXX/trace.
867 tristate "Initio 9100U(W) support"
868 depends on PCI && SCSI
870 This is support for the Initio 91XXU(W) SCSI host adapter. Please
871 read the SCSI-HOWTO, available from
872 <http://www.tldp.org/docs.html#howto>.
874 To compile this driver as a module, choose M here: the
875 module will be called initio.
878 tristate "Initio INI-A100U2W support"
879 depends on PCI && SCSI
881 This is support for the Initio INI-A100U2W SCSI host adapter.
882 Please read the SCSI-HOWTO, available from
883 <http://www.tldp.org/docs.html#howto>.
885 To compile this driver as a module, choose M here: the
886 module will be called a100u2w.
889 tristate "IOMEGA parallel port (ppa - older drives)"
890 depends on SCSI && PARPORT_PC
892 This driver supports older versions of IOMEGA's parallel port ZIP
893 drive (a 100 MB removable media device).
895 Note that you can say N here if you have the SCSI version of the ZIP
896 drive: it will be supported automatically if you said Y to the
897 generic "SCSI disk support", above.
899 If you have the ZIP Plus drive or a more recent parallel port ZIP
900 drive (if the supplied cable with the drive is labeled "AutoDetect")
901 then you should say N here and Y to "IOMEGA parallel port (imm -
902 newer drives)", below.
904 For more information about this driver and how to use it you should
905 read the file <file:Documentation/scsi/ppa.txt>. You should also read
906 the SCSI-HOWTO, which is available from
907 <http://www.tldp.org/docs.html#howto>. If you use this driver,
908 you will still be able to use the parallel port for other tasks,
909 such as a printer; it is safe to compile both drivers into the
912 To compile this driver as a module, choose M here: the
913 module will be called ppa.
916 tristate "IOMEGA parallel port (imm - newer drives)"
917 depends on SCSI && PARPORT_PC
919 This driver supports newer versions of IOMEGA's parallel port ZIP
920 drive (a 100 MB removable media device).
922 Note that you can say N here if you have the SCSI version of the ZIP
923 drive: it will be supported automatically if you said Y to the
924 generic "SCSI disk support", above.
926 If you have the ZIP Plus drive or a more recent parallel port ZIP
927 drive (if the supplied cable with the drive is labeled "AutoDetect")
928 then you should say Y here; if you have an older ZIP drive, say N
929 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
931 For more information about this driver and how to use it you should
932 read the file <file:Documentation/scsi/ppa.txt>. You should also read
933 the SCSI-HOWTO, which is available from
934 <http://www.tldp.org/docs.html#howto>. If you use this driver,
935 you will still be able to use the parallel port for other tasks,
936 such as a printer; it is safe to compile both drivers into the
939 To compile this driver as a module, choose M here: the
940 module will be called imm.
942 config SCSI_IZIP_EPP16
943 bool "ppa/imm option - Use slow (but safe) EPP-16"
944 depends on SCSI_PPA || SCSI_IMM
946 EPP (Enhanced Parallel Port) is a standard for parallel ports which
947 allows them to act as expansion buses that can handle up to 64
950 Some parallel port chipsets are slower than their motherboard, and
951 so we have to control the state of the chipset's FIFO queue every
952 now and then to avoid data loss. This will be done if you say Y
955 Generally, saying Y is the safe option and slows things down a bit.
957 config SCSI_IZIP_SLOW_CTR
958 bool "ppa/imm option - Assume slow parport control register"
959 depends on SCSI_PPA || SCSI_IMM
961 Some parallel ports are known to have excessive delays between
962 changing the parallel port control register and good data being
963 available on the parallel port data/status register. This option
964 forces a small delay (1.0 usec to be exact) after changing the
965 control register to let things settle out. Enabling this option may
966 result in a big drop in performance but some very old parallel ports
967 (found in 386 vintage machines) will not work properly.
969 Generally, saying N is fine.
971 config SCSI_NCR53C406A
972 tristate "NCR53c406a SCSI support"
973 depends on ISA && SCSI
975 This is support for the NCR53c406a SCSI host adapter. For user
976 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
977 in the kernel source. Also read the SCSI-HOWTO, available from
978 <http://www.tldp.org/docs.html#howto>.
980 To compile this driver as a module, choose M here: the
981 module will be called NCR53c406.
984 tristate "NCR Dual 700 MCA SCSI support"
985 depends on MCA && SCSI
986 select SCSI_SPI_ATTRS
988 This is a driver for the MicroChannel Dual 700 card produced by
989 NCR and commonly used in 345x/35xx/4100 class machines. It always
990 tries to negotiate sync and uses tag command queueing.
992 Unless you have an NCR manufactured machine, the chances are that
993 you do not have this SCSI card, so say N.
996 tristate "HP Lasi SCSI support for 53c700/710"
997 depends on GSC && SCSI
998 select SCSI_SPI_ATTRS
1000 This is a driver for the SCSI controller in the Lasi chip found in
1001 many PA-RISC workstations & servers. If you do not know whether you
1002 have a Lasi chip, it is safe to say "Y" here.
1004 config SCSI_SNI_53C710
1005 tristate "SNI RM SCSI support for 53c710"
1006 depends on SNI_RM && SCSI
1007 select SCSI_SPI_ATTRS
1008 select 53C700_LE_ON_BE
1010 This is a driver for the onboard SCSI controller found in older
1011 SNI RM workstations & servers.
1013 config 53C700_LE_ON_BE
1015 depends on SCSI_LASI700
1019 tristate "Promise SuperTrak EX Series support"
1020 depends on PCI && SCSI
1022 This driver supports Promise SuperTrak EX series storage controllers.
1024 Promise provides Linux RAID configuration utility for these
1025 controllers. Please visit <http://www.promise.com> to download.
1027 To compile this driver as a module, choose M here: the
1028 module will be called stex.
1030 config 53C700_BE_BUS
1032 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1035 config SCSI_SYM53C8XX_2
1036 tristate "SYM53C8XX Version 2 SCSI support"
1037 depends on PCI && SCSI
1038 select SCSI_SPI_ATTRS
1040 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1041 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1042 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1043 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1044 controllers; you need to use the Fusion MPT driver for that.
1046 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1049 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1050 int "DMA addressing mode"
1051 depends on SCSI_SYM53C8XX_2
1054 This option only applies to PCI-SCSI chips that are PCI DAC
1055 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1057 When set to 0, the driver will program the chip to only perform
1058 32-bit DMA. When set to 1, the chip will be able to perform DMA
1059 to addresses up to 1TB. When set to 2, the driver supports the
1060 full 64-bit DMA address range, but can only address 16 segments
1061 of 4 GB each. This limits the total addressable range to 64 GB.
1063 Most machines with less than 4GB of memory should use a setting
1064 of 0 for best performance. If your machine has 4GB of memory
1065 or more, you should set this option to 1 (the default).
1067 The still experimental value 2 (64 bit DMA addressing with 16
1068 x 4GB segments limitation) can be used on systems that require
1069 PCI address bits past bit 39 to be set for the addressing of
1070 memory using PCI DAC cycles.
1072 config SCSI_SYM53C8XX_DEFAULT_TAGS
1073 int "Default tagged command queue depth"
1074 depends on SCSI_SYM53C8XX_2
1077 This is the default value of the command queue depth the
1078 driver will announce to the generic SCSI layer for devices
1079 that support tagged command queueing. This value can be changed
1080 from the boot command line. This is a soft limit that cannot
1081 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1083 config SCSI_SYM53C8XX_MAX_TAGS
1084 int "Maximum number of queued commands"
1085 depends on SCSI_SYM53C8XX_2
1088 This option allows you to specify the maximum number of commands
1089 that can be queued to any device, when tagged command queuing is
1090 possible. The driver supports up to 256 queued commands per device.
1091 This value is used as a compiled-in hard limit.
1093 config SCSI_SYM53C8XX_MMIO
1094 bool "Use memory mapped IO"
1095 depends on SCSI_SYM53C8XX_2
1098 Memory mapped IO is faster than Port IO. Most people should
1099 answer Y here, but some machines may have problems. If you have
1100 to answer N here, please report the problem to the maintainer.
1103 tristate "IBM Power Linux RAID adapter support"
1104 depends on PCI && SCSI && ATA
1108 This driver supports the IBM Power Linux family RAID adapters.
1109 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1110 as IBM iSeries 5702, 5703, 5709, and 570A.
1112 config SCSI_IPR_TRACE
1113 bool "enable driver internal trace"
1117 If you say Y here, the driver will trace all commands issued
1118 to the adapter. Performance impact is minimal. Trace can be
1119 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1121 config SCSI_IPR_DUMP
1122 bool "enable adapter dump support"
1126 If you say Y here, the driver will support adapter crash dump.
1127 If you enable this support, the iprdump daemon can be used
1128 to capture adapter failure analysis information.
1131 tristate "Zalon SCSI support"
1132 depends on GSC && SCSI
1133 select SCSI_SPI_ATTRS
1135 The Zalon is a GSC/HSC bus interface chip that sits between the
1136 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1137 C110, J200, J210 and some D, K & R-class machines. It's also
1138 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1139 Say Y here if you have one of these machines or cards.
1141 config SCSI_NCR_Q720
1142 tristate "NCR Quad 720 MCA SCSI support"
1143 depends on MCA && SCSI
1144 select SCSI_SPI_ATTRS
1146 This is a driver for the MicroChannel Quad 720 card produced by
1147 NCR and commonly used in 345x/35xx/4100 class machines. It always
1148 tries to negotiate sync and uses tag command queueing.
1150 Unless you have an NCR manufactured machine, the chances are that
1151 you do not have this SCSI card, so say N.
1153 config SCSI_NCR53C8XX_DEFAULT_TAGS
1154 int "default tagged command queue depth"
1155 depends on SCSI_ZALON || SCSI_NCR_Q720
1158 "Tagged command queuing" is a feature of SCSI-2 which improves
1159 performance: the host adapter can send several SCSI commands to a
1160 device's queue even if previous commands haven't finished yet.
1161 Because the device is intelligent, it can optimize its operations
1162 (like head positioning) based on its own request queue. Some SCSI
1163 devices don't implement this properly; if you want to disable this
1164 feature, enter 0 or 1 here (it doesn't matter which).
1166 The default value is 8 and should be supported by most hard disks.
1167 This value can be overridden from the boot command line using the
1168 'tags' option as follows (example):
1169 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1170 4, set queue depth to 16 for target 2 and target 3 on controller 0
1171 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1173 The normal answer therefore is to go with the default 8 and to use
1174 a boot command line option for devices that need to use a different
1175 command queue depth.
1177 There is no safe option other than using good SCSI devices.
1179 config SCSI_NCR53C8XX_MAX_TAGS
1180 int "maximum number of queued commands"
1181 depends on SCSI_ZALON || SCSI_NCR_Q720
1184 This option allows you to specify the maximum number of commands
1185 that can be queued to any device, when tagged command queuing is
1186 possible. The default value is 32. Minimum is 2, maximum is 64.
1187 Modern hard disks are able to support 64 tags and even more, but
1188 do not seem to be faster when more than 32 tags are being used.
1190 So, the normal answer here is to go with the default value 32 unless
1191 you are using very large hard disks with large cache (>= 1 MB) that
1192 are able to take advantage of more than 32 tagged commands.
1194 There is no safe option and the default answer is recommended.
1196 config SCSI_NCR53C8XX_SYNC
1197 int "synchronous transfers frequency in MHz"
1198 depends on SCSI_ZALON || SCSI_NCR_Q720
1201 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1202 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1203 are respectively the maximum data transfer rates in mega-transfers
1204 per second for each class. For example, a FAST-20 Wide 16 device is
1205 able to transfer data at 20 million 16 bit packets per second for a
1206 total rate of 40 MB/s.
1208 You may specify 0 if you want to only use asynchronous data
1209 transfers. This is the safest and slowest option. Otherwise, specify
1210 a value between 5 and 80, depending on the capability of your SCSI
1211 controller. The higher the number, the faster the data transfer.
1212 Note that 80 should normally be ok since the driver decreases the
1213 value automatically according to the controller's capabilities.
1215 Your answer to this question is ignored for controllers with NVRAM,
1216 since the driver will get this information from the user set-up. It
1217 also can be overridden using a boot setup option, as follows
1218 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1219 for FAST-20 synchronous data transfer (20 mega-transfers per
1222 The normal answer therefore is not to go with the default but to
1223 select the maximum value 80 allowing the driver to use the maximum
1224 value supported by each controller. If this causes problems with
1225 your SCSI devices, you should come back and decrease the value.
1227 There is no safe option other than using good cabling, right
1228 terminations and SCSI conformant devices.
1230 config SCSI_NCR53C8XX_NO_DISCONNECT
1231 bool "not allow targets to disconnect"
1232 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1234 This option is only provided for safety if you suspect some SCSI
1235 device of yours to not support properly the target-disconnect
1236 feature. In that case, you would say Y here. In general however, to
1237 not allow targets to disconnect is not reasonable if there is more
1238 than 1 device on a SCSI bus. The normal answer therefore is N.
1241 tristate "PAS16 SCSI support"
1242 depends on ISA && SCSI
1243 select SCSI_SPI_ATTRS
1245 This is support for a SCSI host adapter. It is explained in section
1246 3.10 of the SCSI-HOWTO, available from
1247 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1248 of the box, you may have to change some settings in
1249 <file:drivers/scsi/pas16.h>.
1251 To compile this driver as a module, choose M here: the
1252 module will be called pas16.
1254 config SCSI_QLOGIC_FAS
1255 tristate "Qlogic FAS SCSI support"
1256 depends on ISA && SCSI
1258 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1259 FastSCSI! cards as well as any other card based on the FASXX chip
1260 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1262 This driver does NOT support the PCI versions of these cards. The
1263 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1264 SCSI support"), below.
1266 Information about this driver is contained in
1267 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1268 SCSI-HOWTO, available from
1269 <http://www.tldp.org/docs.html#howto>.
1271 To compile this driver as a module, choose M here: the
1272 module will be called qlogicfas.
1274 config SCSI_QLOGIC_1280
1275 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1276 depends on PCI && SCSI
1278 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1280 To compile this driver as a module, choose M here: the
1281 module will be called qla1280.
1283 config SCSI_QLOGICPTI
1284 tristate "PTI Qlogic, ISP Driver"
1285 depends on SBUS && SCSI
1287 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1288 controllers are known under Solaris as qpti and in the openprom as
1289 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1290 driven by a different driver.
1292 To compile this driver as a module, choose M here: the
1293 module will be called qlogicpti.
1295 source "drivers/scsi/qla2xxx/Kconfig"
1296 source "drivers/scsi/qla4xxx/Kconfig"
1299 tristate "Emulex LightPulse Fibre Channel Support"
1300 depends on PCI && SCSI
1301 depends on SCSI_FC_ATTRS
1304 This lpfc driver supports the Emulex LightPulse
1305 Family of Fibre Channel PCI host adapters.
1307 config SCSI_LPFC_DEBUG_FS
1308 bool "Emulex LightPulse Fibre Channel debugfs Support"
1309 depends on SCSI_LPFC && DEBUG_FS
1311 This makes debugging information from the lpfc driver
1312 available via the debugfs filesystem.
1315 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1316 depends on (EISA || MCA) && SCSI
1317 select SCSI_SPI_ATTRS
1319 This driver is for NCR53c710 based SCSI host adapters.
1321 It currently supports Compaq EISA cards and NCR MCA cards
1323 config SCSI_SYM53C416
1324 tristate "Symbios 53c416 SCSI support"
1325 depends on ISA && SCSI
1327 This is support for the sym53c416 SCSI host adapter, the SCSI
1328 adapter that comes with some HP scanners. This driver requires that
1329 the sym53c416 is configured first using some sort of PnP
1330 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1331 are using isapnp then you need to compile this driver as a module
1332 and then load it using insmod after isapnp has run. The parameters
1333 of the configured card(s) should be passed to the driver. The format
1336 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1338 To compile this driver as a module, choose M here: the
1339 module will be called sym53c416.
1342 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1343 depends on PCI && SCSI
1345 This driver supports PCI SCSI host adapters based on the ASIC
1346 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1348 This driver works, but is still in experimental status. So better
1349 have a bootable disk and a backup in case of emergency.
1351 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1353 To compile this driver as a module, choose M here: the
1354 module will be called dc395x.
1356 config SCSI_AM53C974
1357 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1358 depends on PCI && SCSI
1359 select SCSI_SPI_ATTRS
1361 This driver supports PCI SCSI host adapters based on the Am53C974A
1362 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1363 PCscsi/PCnet (Am53/79C974) solutions.
1364 This is a new implementation base on the generic esp_scsi driver.
1366 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1368 Note that this driver does NOT support Tekram DC390W/U/F, which are
1369 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1371 To compile this driver as a module, choose M here: the
1372 module will be called am53c974.
1375 tristate "Trantor T128/T128F/T228 SCSI support"
1376 depends on ISA && SCSI
1377 select SCSI_SPI_ATTRS
1378 select CHECK_SIGNATURE
1380 This is support for a SCSI host adapter. It is explained in section
1381 3.11 of the SCSI-HOWTO, available from
1382 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1383 of the box, you may have to change some settings in
1384 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1385 Adaptec, and some former Trantor products are being sold under the
1388 To compile this driver as a module, choose M here: the
1389 module will be called t128.
1392 tristate "UltraStor 14F/34F support"
1393 depends on ISA && SCSI && ISA_DMA_API
1395 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1396 The source at <file:drivers/scsi/u14-34f.c> contains some
1397 information about this hardware. If the driver doesn't work out of
1398 the box, you may have to change some settings in
1399 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1400 <http://www.tldp.org/docs.html#howto>. Note that there is also
1401 another driver for the same hardware: "UltraStor SCSI support",
1402 below. You should say Y to both only if you want 24F support as
1405 To compile this driver as a module, choose M here: the
1406 module will be called u14-34f.
1408 config SCSI_U14_34F_TAGGED_QUEUE
1409 bool "enable tagged command queueing"
1410 depends on SCSI_U14_34F
1412 This is a feature of SCSI-2 which improves performance: the host
1413 adapter can send several SCSI commands to a device's queue even if
1414 previous commands haven't finished yet.
1415 This is equivalent to the "u14-34f=tc:y" boot option.
1417 config SCSI_U14_34F_LINKED_COMMANDS
1418 bool "enable elevator sorting"
1419 depends on SCSI_U14_34F
1421 This option enables elevator sorting for all probed SCSI disks and
1422 CD-ROMs. It definitely reduces the average seek distance when doing
1423 random seeks, but this does not necessarily result in a noticeable
1424 performance improvement: your mileage may vary...
1425 This is equivalent to the "u14-34f=lc:y" boot option.
1427 config SCSI_U14_34F_MAX_TAGS
1428 int "maximum number of queued commands"
1429 depends on SCSI_U14_34F
1432 This specifies how many SCSI commands can be maximally queued for
1433 each probed SCSI device. You should reduce the default value of 8
1434 only if you have disks with buggy or limited tagged command support.
1435 Minimum is 2 and maximum is 14. This value is also the window size
1436 used by the elevator sorting option above. The effective value used
1437 by the driver for each probed SCSI device is reported at boot time.
1438 This is equivalent to the "u14-34f=mq:8" boot option.
1440 config SCSI_ULTRASTOR
1441 tristate "UltraStor SCSI support"
1442 depends on X86 && ISA && SCSI && ISA_DMA_API
1444 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1445 adapter family. This driver is explained in section 3.12 of the
1446 SCSI-HOWTO, available from
1447 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1448 of the box, you may have to change some settings in
1449 <file:drivers/scsi/ultrastor.h>.
1451 Note that there is also another driver for the same hardware:
1452 "UltraStor 14F/34F support", above.
1454 To compile this driver as a module, choose M here: the
1455 module will be called ultrastor.
1458 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1459 depends on PCI && SCSI && !64BIT
1461 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1462 SCSI host adapter. Please read the SCSI-HOWTO, available from
1463 <http://www.tldp.org/docs.html#howto>.
1465 To compile this driver as a module, choose M here: the
1466 module will be called nsp32.
1469 tristate "Western Digital WD7193/7197/7296 support"
1470 depends on PCI && SCSI
1473 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1474 SCSI controllers (based on WD33C296A chip).
1477 tristate "SCSI debugging host and device simulator"
1481 This pseudo driver simulates one or more hosts (SCSI initiators),
1482 each with one or more targets, each with one or more logical units.
1483 Defaults to one of each, creating a small RAM disk device. Many
1484 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1485 directory can be tweaked at run time.
1486 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1487 Mainly used for testing and best as a module. If unsure, say N.
1490 tristate "MESH (Power Mac internal SCSI) support"
1491 depends on PPC32 && PPC_PMAC && SCSI
1493 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1494 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1495 other Power Macintoshes do). Say Y to include support for this SCSI
1498 To compile this driver as a module, choose M here: the
1499 module will be called mesh.
1501 config SCSI_MESH_SYNC_RATE
1502 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1503 depends on SCSI_MESH
1506 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1507 drives a bus which is entirely internal to the machine (such as the
1508 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1509 operation at up to 10 MB/s. On machines where the SCSI bus
1510 controlled by the MESH can have external devices connected, it is
1511 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1512 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1513 to disable synchronous operation.
1515 config SCSI_MESH_RESET_DELAY_MS
1516 int "initial bus reset delay (ms) (0 = no reset)"
1517 depends on SCSI_MESH
1520 config SCSI_MAC53C94
1521 tristate "53C94 (Power Mac external SCSI) support"
1522 depends on PPC32 && PPC_PMAC && SCSI
1524 On Power Macintoshes (and clones) with two SCSI buses, the external
1525 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1526 machines which only have one SCSI bus, such as the 7200, also use
1527 the 53C94. Say Y to include support for the 53C94.
1529 To compile this driver as a module, choose M here: the
1530 module will be called mac53c94.
1532 source "drivers/scsi/arm/Kconfig"
1535 bool "MIPS JAZZ FAS216 SCSI support"
1536 depends on MACH_JAZZ && SCSI
1537 select SCSI_SPI_ATTRS
1539 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1540 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1544 tristate "A3000 WD33C93A support"
1545 depends on AMIGA && SCSI
1547 If you have an Amiga 3000 and have SCSI devices connected to the
1548 built-in SCSI controller, say Y. Otherwise, say N.
1550 To compile this driver as a module, choose M here: the
1551 module will be called a3000.
1554 tristate "A2091/A590 WD33C93A support"
1555 depends on ZORRO && SCSI
1557 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1560 To compile this driver as a module, choose M here: the
1561 module will be called a2091.
1564 tristate "GVP Series II WD33C93A support"
1565 depends on ZORRO && SCSI
1567 If you have a Great Valley Products Series II SCSI controller,
1568 answer Y. Also say Y if you have a later model of GVP SCSI
1569 controller (such as the GVP A4008 or a Combo board). Otherwise,
1570 answer N. This driver does NOT work for the T-Rex series of
1571 accelerators from TekMagic and GVP-M.
1573 To compile this driver as a module, choose M here: the
1574 module will be called gvp11.
1577 tristate "A4000T NCR53c710 SCSI support"
1578 depends on AMIGA && SCSI
1579 select SCSI_SPI_ATTRS
1581 If you have an Amiga 4000T and have SCSI devices connected to the
1582 built-in SCSI controller, say Y. Otherwise, say N.
1584 To compile this driver as a module, choose M here: the
1585 module will be called a4000t.
1587 config SCSI_ZORRO7XX
1588 tristate "Zorro NCR53c710 SCSI support"
1589 depends on ZORRO && SCSI
1590 select SCSI_SPI_ATTRS
1592 Support for various NCR53c710-based SCSI controllers on Zorro
1593 expansion boards for the Amiga.
1595 - the Amiga 4091 Zorro III SCSI-2 controller,
1596 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1598 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1599 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1600 accelerator card for the Amiga 1200,
1601 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1604 tristate "Atari native SCSI support"
1605 depends on ATARI && SCSI
1606 select SCSI_SPI_ATTRS
1609 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1610 Falcon, ...) say Y to get it supported. Of course also, if you have
1611 a compatible SCSI controller (e.g. for Medusa).
1613 To compile this driver as a module, choose M here: the
1614 module will be called atari_scsi.
1616 This driver supports both styles of NCR integration into the
1617 system: the TT style (separate DMA), and the Falcon style (via
1618 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1619 in the Hades (without DMA).
1622 tristate "Macintosh NCR5380 SCSI"
1623 depends on MAC && SCSI=y
1624 select SCSI_SPI_ATTRS
1626 This is the NCR 5380 SCSI controller included on most of the 68030
1627 based Macintoshes. If you have one of these say Y and read the
1628 SCSI-HOWTO, available from
1629 <http://www.tldp.org/docs.html#howto>.
1632 tristate "Macintosh NCR53c9[46] SCSI"
1633 depends on MAC && SCSI
1634 select SCSI_SPI_ATTRS
1636 This is the NCR 53c9x SCSI controller found on most of the 68040
1639 To compile this driver as a module, choose M here: the module
1640 will be called mac_esp.
1643 bool "WD33C93 SCSI driver for MVME147"
1644 depends on MVME147 && SCSI=y
1645 select SCSI_SPI_ATTRS
1647 Support for the on-board SCSI controller on the Motorola MVME147
1648 single-board computer.
1651 tristate "NCR53C710 SCSI driver for MVME16x"
1652 depends on MVME16x && SCSI
1653 select SCSI_SPI_ATTRS
1655 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1656 SCSI controller chip. Almost everyone using one of these boards
1657 will want to say Y to this question.
1659 config BVME6000_SCSI
1660 tristate "NCR53C710 SCSI driver for BVME6000"
1661 depends on BVME6000 && SCSI
1662 select SCSI_SPI_ATTRS
1664 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1665 SCSI controller chip. Almost everyone using one of these boards
1666 will want to say Y to this question.
1669 tristate "Sun3 NCR5380 SCSI"
1670 depends on SUN3 && SCSI
1671 select SCSI_SPI_ATTRS
1673 This option will enable support for the OBIO (onboard io) NCR5380
1674 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1675 "Sun3" type VME scsi controllers also based on the NCR5380.
1676 General Linux information on the Sun 3 series (now discontinued)
1677 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1680 bool "Sun3x ESP SCSI"
1681 depends on SUN3X && SCSI=y
1682 select SCSI_SPI_ATTRS
1684 The ESP was an on-board SCSI controller used on Sun 3/80
1685 machines. Say Y here to compile in support for it.
1688 tristate "Sparc ESP Scsi Driver"
1689 depends on SBUS && SCSI
1690 select SCSI_SPI_ATTRS
1692 This is the driver for the Sun ESP SCSI host adapter. The ESP
1693 chipset is present in most SPARC SBUS-based computers and
1694 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1695 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1697 To compile this driver as a module, choose M here: the
1698 module will be called sun_esp.
1701 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1702 depends on S390 && QDIO && SCSI
1703 depends on SCSI_FC_ATTRS
1705 If you want to access SCSI devices attached to your IBM eServer
1706 zSeries by means of Fibre Channel interfaces say Y.
1707 For details please refer to the documentation provided by IBM at
1708 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1710 This driver is also available as a module. This module will be
1711 called zfcp. If you want to compile it as a module, say M here
1712 and read <file:Documentation/kbuild/modules.txt>.
1715 tristate "PMC SIERRA Linux MaxRAID adapter support"
1716 depends on PCI && SCSI && NET
1718 This driver supports the PMC SIERRA MaxRAID adapters.
1721 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1722 depends on PCI && SCSI
1723 select SCSI_SAS_LIBSAS
1725 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1726 based host adapters.
1729 tristate "Brocade BFA Fibre Channel Support"
1730 depends on PCI && SCSI
1731 depends on SCSI_FC_ATTRS
1733 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1735 To compile this driver as a module, choose M here. The module will
1739 tristate "virtio-scsi support"
1742 This is the virtual HBA driver for virtio. If the kernel will
1743 be used in a virtual machine, say Y or M.
1745 source "drivers/scsi/csiostor/Kconfig"
1747 endif # SCSI_LOWLEVEL
1749 source "drivers/scsi/pcmcia/Kconfig"
1751 source "drivers/scsi/device_handler/Kconfig"
1753 source "drivers/scsi/osd/Kconfig"