1 menu "SCSI device support"
5 default y if SCSI=n || SCSI=y
9 tristate "RAID Transport Class"
17 tristate "SCSI device support"
19 select SCSI_DMA if HAS_DMA
21 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
22 any other SCSI device under Linux, say Y and make sure that you know
23 the name of your SCSI host adapter (the card inside your computer
24 that "speaks" the SCSI protocol, also called SCSI controller),
25 because you will be asked for it.
27 You also need to say Y here if you have a device which speaks
28 the SCSI protocol. Examples of this include the parallel port
29 version of the IOMEGA ZIP drive, USB storage devices, Fibre
30 Channel, and FireWire storage.
32 To compile this driver as a module, choose M here and read
33 <file:Documentation/scsi/scsi.txt>.
34 The module will be called scsi_mod.
36 However, do not compile this as a module if your root file system
37 (the one containing the directory /) is located on a SCSI device.
48 config SCSI_MQ_DEFAULT
49 bool "SCSI: use blk-mq I/O path by default"
52 This option enables the new blk-mq based I/O path for SCSI
53 devices by default. With the option the scsi_mod.use_blk_mq
54 module/boot option defaults to Y, without it to N, but it can
55 still be overridden either way.
60 bool "legacy /proc/scsi/ support"
61 depends on SCSI && PROC_FS
64 This option enables support for the various files in
65 /proc/scsi. In Linux 2.6 this has been superseded by
66 files in sysfs but many legacy applications rely on this.
70 comment "SCSI support type (disk, tape, CD-ROM)"
74 tristate "SCSI disk support"
77 If you want to use SCSI hard disks, Fibre Channel disks,
78 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
79 USB storage or the SCSI or parallel port version of
80 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
81 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
82 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
85 To compile this driver as a module, choose M here and read
86 <file:Documentation/scsi/scsi.txt>.
87 The module will be called sd_mod.
89 Do not compile this driver as a module if your root file system
90 (the one containing the directory /) is located on a SCSI disk.
91 In this case, do not compile the driver for your SCSI host adapter
92 (below) as a module either.
95 tristate "SCSI tape support"
98 If you want to use a SCSI tape drive under Linux, say Y and read the
99 SCSI-HOWTO, available from
100 <http://www.tldp.org/docs.html#howto>, and
101 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
104 To compile this driver as a module, choose M here and read
105 <file:Documentation/scsi/scsi.txt>. The module will be called st.
108 tristate "SCSI OnStream SC-x0 tape support"
111 The OnStream SC-x0 SCSI tape drives cannot be driven by the
112 standard st driver, but instead need this special osst driver and
113 use the /dev/osstX char device nodes (major 206). Via usb-storage,
114 you may be able to drive the USB-x0 and DI-x0 drives as well.
115 Note that there is also a second generation of OnStream
116 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
117 tapes (QIC-157) and can be driven by the standard driver st.
118 For more information, you may have a look at the SCSI-HOWTO
119 <http://www.tldp.org/docs.html#howto> and
120 <file:Documentation/scsi/osst.txt> in the kernel source.
121 More info on the OnStream driver may be found on
122 <http://sourceforge.net/projects/osst/>
123 Please also have a look at the standard st docu, as most of it
124 applies to osst as well.
126 To compile this driver as a module, choose M here and read
127 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
130 tristate "SCSI CDROM support"
133 If you want to use a CD or DVD drive attached to your computer
134 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
135 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
137 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
139 To compile this driver as a module, choose M here and read
140 <file:Documentation/scsi/scsi.txt>.
141 The module will be called sr_mod.
143 config BLK_DEV_SR_VENDOR
144 bool "Enable vendor-specific extensions (for SCSI CDROM)"
145 depends on BLK_DEV_SR
147 This enables the usage of vendor specific SCSI commands. This is
148 required to support multisession CDs with old NEC/TOSHIBA cdrom
149 drives (and HP Writers). If you have such a drive and get the first
150 session only, try saying Y here; everybody else says N.
153 tristate "SCSI generic support"
156 If you want to use SCSI scanners, synthesizers or CD-writers or just
157 about anything having "SCSI" in its name other than hard disks,
158 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
159 directly, so you need some additional software which knows how to
160 talk to these devices using the SCSI protocol:
162 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
163 writer software look at Cdrtools
164 (<http://cdrecord.berlios.de/private/cdrecord.html>)
165 and for burning a "disk at once": CDRDAO
166 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
167 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
168 For other devices, it's possible that you'll have to write the
169 driver software yourself. Please read the file
170 <file:Documentation/scsi/scsi-generic.txt> for more information.
172 To compile this driver as a module, choose M here and read
173 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
178 tristate "SCSI media changer support"
181 This is a driver for SCSI media changers. Most common devices are
182 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
183 don't need this for those tiny 6-slot cdrom changers. Media
184 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
185 If you have such hardware and want to use it with linux, say Y
186 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
188 If you want to compile this as a module ( = code which can be
189 inserted in and removed from the running kernel whenever you want),
190 say M here and read <file:Documentation/kbuild/modules.txt> and
191 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
194 config SCSI_ENCLOSURE
195 tristate "SCSI Enclosure Support"
196 depends on SCSI && ENCLOSURE_SERVICES
197 depends on m || SCSI_SAS_ATTRS != m
199 Enclosures are devices sitting on or in SCSI backplanes that
200 manage devices. If you have a disk cage, the chances are that
201 it has an enclosure device. Selecting this option will just allow
202 certain enclosure conditions to be reported and is not required.
204 config SCSI_CONSTANTS
205 bool "Verbose SCSI error reporting (kernel size +=75K)"
208 The error messages regarding your SCSI hardware will be easier to
209 understand if you say Y here; it will enlarge your kernel by about
210 75 KB. If in doubt, say Y.
213 bool "SCSI logging facility"
216 This turns on a logging facility that can be used to debug a number
217 of SCSI related problems.
219 If you say Y here, no logging output will appear by default, but you
220 can enable logging by saying Y to "/proc file system support" and
221 "Sysctl support" below and executing the command
223 echo <bitmask> > /proc/sys/dev/scsi/logging_level
225 where <bitmask> is a four byte value representing the logging type
226 and logging level for each type of logging selected.
228 There are a number of logging types and you can find them in the
229 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
230 are also described in that file and they determine the verbosity of
231 the logging for each logging type.
233 If you say N here, it may be harder to track down some types of SCSI
234 problems. If you say Y here your kernel will be somewhat larger, but
235 there should be no noticeable performance impact as long as you have
238 config SCSI_SCAN_ASYNC
239 bool "Asynchronous SCSI scanning"
242 The SCSI subsystem can probe for devices while the rest of the
243 system continues booting, and even probe devices on different
244 busses in parallel, leading to a significant speed-up.
246 You can override this choice by specifying "scsi_mod.scan=sync"
247 or async on the kernel's command line.
249 Note that this setting also affects whether resuming from
250 system suspend will be performed asynchronously.
252 menu "SCSI Transports"
255 config SCSI_SPI_ATTRS
256 tristate "Parallel SCSI (SPI) Transport Attributes"
259 If you wish to export transport-specific information about
260 each attached SCSI device to sysfs, say Y. Otherwise, say N.
263 tristate "FiberChannel Transport Attributes"
264 depends on SCSI && NET
267 If you wish to export transport-specific information about
268 each attached FiberChannel device to sysfs, say Y.
271 config SCSI_ISCSI_ATTRS
272 tristate "iSCSI Transport Attributes"
273 depends on SCSI && NET
274 select BLK_DEV_BSGLIB
276 If you wish to export transport-specific information about
277 each attached iSCSI device to sysfs, say Y.
280 config SCSI_SAS_ATTRS
281 tristate "SAS Transport Attributes"
285 If you wish to export transport-specific information about
286 each attached SAS device to sysfs, say Y.
288 source "drivers/scsi/libsas/Kconfig"
290 config SCSI_SRP_ATTRS
291 tristate "SRP Transport Attributes"
294 If you wish to export transport-specific information about
295 each attached SRP device to sysfs, say Y.
299 menuconfig SCSI_LOWLEVEL
300 bool "SCSI low-level drivers"
304 if SCSI_LOWLEVEL && SCSI
307 tristate "iSCSI Initiator over TCP/IP"
308 depends on SCSI && INET
312 select SCSI_ISCSI_ATTRS
314 The iSCSI Driver provides a host with the ability to access storage
315 through an IP network. The driver uses the iSCSI protocol to transport
316 SCSI requests and responses over a TCP/IP network between the host
317 (the "initiator") and "targets". Architecturally, the iSCSI driver
318 combines with the host's TCP/IP stack, network drivers, and Network
319 Interface Card (NIC) to provide the same functions as a SCSI or a
320 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
322 To compile this driver as a module, choose M here: the
323 module will be called iscsi_tcp.
325 The userspace component needed to initialize the driver, documentation,
326 and sample configuration files can be found here:
328 http://open-iscsi.org
330 config ISCSI_BOOT_SYSFS
331 tristate "iSCSI Boot Sysfs Interface"
334 This option enables support for exposing iSCSI boot information
335 via sysfs to userspace. If you wish to export this information,
336 say Y. Otherwise, say N.
338 source "drivers/scsi/cxgbi/Kconfig"
339 source "drivers/scsi/bnx2i/Kconfig"
340 source "drivers/scsi/bnx2fc/Kconfig"
341 source "drivers/scsi/be2iscsi/Kconfig"
342 source "drivers/scsi/cxlflash/Kconfig"
345 tristate "SGI WD93C93 SCSI Driver"
346 depends on SGI_HAS_WD93 && SCSI
348 If you have a Western Digital WD93 SCSI controller on
349 an SGI MIPS system, say Y. Otherwise, say N.
351 config BLK_DEV_3W_XXXX_RAID
352 tristate "3ware 5/6/7/8xxx ATA-RAID support"
353 depends on PCI && SCSI
355 3ware is the only hardware ATA-Raid product in Linux to date.
356 This card is 2,4, or 8 channel master mode support only.
357 SCSI support required!!!
359 <http://www.3ware.com/>
361 Please read the comments at the top of
362 <file:drivers/scsi/3w-xxxx.c>.
365 tristate "HP Smart Array SCSI driver"
366 depends on PCI && SCSI
367 select CHECK_SIGNATURE
368 select SCSI_SAS_ATTRS
370 This driver supports HP Smart Array Controllers (circa 2009).
371 It is a SCSI alternative to the cciss driver, which is a block
372 driver. Anyone wishing to use HP Smart Array controllers who
373 would prefer the devices be presented to linux as SCSI devices,
374 rather than as generic block devices should say Y here.
377 tristate "3ware 9xxx SATA-RAID support"
378 depends on PCI && SCSI
380 This driver supports the 9000 series 3ware SATA-RAID cards.
382 <http://www.amcc.com>
384 Please read the comments at the top of
385 <file:drivers/scsi/3w-9xxx.c>.
388 tristate "3ware 97xx SAS/SATA-RAID support"
389 depends on PCI && SCSI
391 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
395 Please read the comments at the top of
396 <file:drivers/scsi/3w-sas.c>.
398 config SCSI_7000FASST
399 tristate "7000FASST SCSI support"
400 depends on ISA && SCSI && ISA_DMA_API
401 select CHECK_SIGNATURE
403 This driver supports the Western Digital 7000 SCSI host adapter
404 family. Some information is in the source:
405 <file:drivers/scsi/wd7000.c>.
407 To compile this driver as a module, choose M here: the
408 module will be called wd7000.
411 tristate "ACARD SCSI support"
412 depends on PCI && SCSI
414 This driver supports the ACARD SCSI host adapter.
415 Support Chip <ATP870 ATP876 ATP880 ATP885>
416 To compile this driver as a module, choose M here: the
417 module will be called atp870u.
420 tristate "Adaptec AHA152X/2825 support"
421 depends on ISA && SCSI
422 select SCSI_SPI_ATTRS
423 select CHECK_SIGNATURE
425 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
426 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
427 must be manually specified in this case.
429 It is explained in section 3.3 of the SCSI-HOWTO, available from
430 <http://www.tldp.org/docs.html#howto>. You might also want to
431 read the file <file:Documentation/scsi/aha152x.txt>.
433 To compile this driver as a module, choose M here: the
434 module will be called aha152x.
437 tristate "Adaptec AHA1542 support"
438 depends on ISA && SCSI && ISA_DMA_API
440 This is support for a SCSI host adapter. It is explained in section
441 3.4 of the SCSI-HOWTO, available from
442 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
443 purchased by Adaptec, and some former Trantor products are being
444 sold under the Adaptec name. If it doesn't work out of the box, you
445 may have to change some settings in <file:drivers/scsi/aha1542.h>.
447 To compile this driver as a module, choose M here: the
448 module will be called aha1542.
451 tristate "Adaptec AHA1740 support"
452 depends on EISA && SCSI
454 This is support for a SCSI host adapter. It is explained in section
455 3.5 of the SCSI-HOWTO, available from
456 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
457 of the box, you may have to change some settings in
458 <file:drivers/scsi/aha1740.h>.
460 To compile this driver as a module, choose M here: the
461 module will be called aha1740.
464 tristate "Adaptec AACRAID support"
465 depends on SCSI && PCI
467 This driver supports a variety of Dell, HP, Adaptec, IBM and
468 ICP storage products. For a list of supported products, refer
469 to <file:Documentation/scsi/aacraid.txt>.
471 To compile this driver as a module, choose M here: the module
472 will be called aacraid.
475 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
476 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
477 source "drivers/scsi/aic94xx/Kconfig"
478 source "drivers/scsi/hisi_sas/Kconfig"
479 source "drivers/scsi/mvsas/Kconfig"
482 tristate "Marvell UMI driver"
483 depends on SCSI && PCI
485 Module for Marvell Universal Message Interface(UMI) driver
487 To compile this driver as a module, choose M here: the
488 module will be called mvumi.
491 tristate "Adaptec I2O RAID support "
492 depends on SCSI && PCI && VIRT_TO_BUS
494 This driver supports all of Adaptec's I2O based RAID controllers as
495 well as the DPT SmartRaid V cards. This is an Adaptec maintained
496 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
498 To compile this driver as a module, choose M here: the
499 module will be called dpt_i2o.
502 tristate "AdvanSys SCSI support"
504 depends on ISA || EISA || PCI
505 depends on ISA_DMA_API || !ISA
507 This is a driver for all SCSI host adapters manufactured by
508 AdvanSys. It is documented in the kernel source in
509 <file:drivers/scsi/advansys.c>.
511 To compile this driver as a module, choose M here: the
512 module will be called advansys.
515 tristate "Always IN2000 SCSI support"
516 depends on ISA && SCSI
518 This is support for an ISA bus SCSI host adapter. You'll find more
519 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
520 out of the box, you may have to change the jumpers for IRQ or
523 To compile this driver as a module, choose M here: the
524 module will be called in2000.
527 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
528 depends on PCI && SCSI
530 This driver supports all of ARECA's SATA/SAS RAID controller cards.
531 This is an ARECA-maintained driver by Erich Chen.
532 If you have any problems, please mail to: <erich@areca.com.tw>.
533 Areca supports Linux RAID config tools.
534 Please link <http://www.areca.com.tw>
536 To compile this driver as a module, choose M here: the
537 module will be called arcmsr (modprobe arcmsr).
539 source "drivers/scsi/esas2r/Kconfig"
540 source "drivers/scsi/megaraid/Kconfig.megaraid"
541 source "drivers/scsi/mpt3sas/Kconfig"
542 source "drivers/scsi/ufs/Kconfig"
545 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
546 depends on SCSI && PCI
548 This option enables support for HighPoint RocketRAID 3xxx/4xxx
551 To compile this driver as a module, choose M here; the module
552 will be called hptiop. If unsure, say N.
555 tristate "BusLogic SCSI support"
556 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
558 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
559 Adapters. Consult the SCSI-HOWTO, available from
560 <http://www.tldp.org/docs.html#howto>, and the files
561 <file:Documentation/scsi/BusLogic.txt> and
562 <file:Documentation/scsi/FlashPoint.txt> for more information.
563 Note that support for FlashPoint is only available for 32-bit
566 To compile this driver as a module, choose M here: the
567 module will be called BusLogic.
569 config SCSI_FLASHPOINT
570 bool "FlashPoint support"
571 depends on SCSI_BUSLOGIC && PCI
573 This option allows you to add FlashPoint support to the
574 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
575 substantial, so users of MultiMaster Host Adapters may not
579 tristate "VMware PVSCSI driver support"
580 depends on PCI && SCSI && X86
582 This driver supports VMware's para virtualized SCSI HBA.
583 To compile this driver as a module, choose M here: the
584 module will be called vmw_pvscsi.
586 config XEN_SCSI_FRONTEND
587 tristate "XEN SCSI frontend driver"
588 depends on SCSI && XEN
589 select XEN_XENBUS_FRONTEND
591 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
592 within another guest OS (usually Dom0).
593 Only needed if the kernel is running in a XEN guest and generic
594 SCSI access to a device is needed.
596 config HYPERV_STORAGE
597 tristate "Microsoft Hyper-V virtual storage driver"
598 depends on SCSI && HYPERV
601 Select this option to enable the Hyper-V virtual storage driver.
604 tristate "LibFC module"
605 depends on SCSI_FC_ATTRS
608 Fibre Channel library module
611 tristate "LibFCoE module"
614 Library for Fibre Channel over Ethernet module
617 tristate "FCoE module"
621 Fibre Channel over Ethernet module
624 tristate "Cisco FNIC Driver"
625 depends on PCI && X86
628 This is support for the Cisco PCI-Express FCoE HBA.
630 To compile this driver as a module, choose M here and read
631 <file:Documentation/scsi/scsi.txt>.
632 The module will be called fnic.
635 tristate "Cisco SNIC Driver"
636 depends on PCI && SCSI
638 This is support for the Cisco PCI-Express SCSI HBA.
640 To compile this driver as a module, choose M here and read
641 <file:Documentation/scsi/scsi.txt>.
642 The module will be called snic.
644 config SCSI_SNIC_DEBUG_FS
645 bool "Cisco SNIC Driver Debugfs Support"
646 depends on SCSI_SNIC && DEBUG_FS
648 This enables to list debugging information from SNIC Driver
649 available via debugfs file system
652 tristate "DMX3191D SCSI support"
653 depends on PCI && SCSI
654 select SCSI_SPI_ATTRS
656 This is support for Domex DMX3191D SCSI Host Adapters.
658 To compile this driver as a module, choose M here: the
659 module will be called dmx3191d.
662 tristate "DTC3180/3280 SCSI support"
663 depends on ISA && SCSI
664 select SCSI_SPI_ATTRS
665 select CHECK_SIGNATURE
667 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
668 the SCSI-HOWTO, available from
669 <http://www.tldp.org/docs.html#howto>, and the file
670 <file:Documentation/scsi/dtc3x80.txt>.
672 To compile this driver as a module, choose M here: the
673 module will be called dtc.
676 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
677 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
679 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
680 ISA and all EISA I/O addresses are probed looking for the "EATA"
681 signature. The addresses of all the PCI SCSI controllers reported
682 by the PCI subsystem are probed as well.
684 You want to read the start of <file:drivers/scsi/eata.c> and the
685 SCSI-HOWTO, available from
686 <http://www.tldp.org/docs.html#howto>.
688 To compile this driver as a module, choose M here: the
689 module will be called eata.
691 config SCSI_EATA_TAGGED_QUEUE
692 bool "enable tagged command queueing"
695 This is a feature of SCSI-2 which improves performance: the host
696 adapter can send several SCSI commands to a device's queue even if
697 previous commands haven't finished yet.
698 This is equivalent to the "eata=tc:y" boot option.
700 config SCSI_EATA_LINKED_COMMANDS
701 bool "enable elevator sorting"
704 This option enables elevator sorting for all probed SCSI disks and
705 CD-ROMs. It definitely reduces the average seek distance when doing
706 random seeks, but this does not necessarily result in a noticeable
707 performance improvement: your mileage may vary...
708 This is equivalent to the "eata=lc:y" boot option.
710 config SCSI_EATA_MAX_TAGS
711 int "maximum number of queued commands"
715 This specifies how many SCSI commands can be maximally queued for
716 each probed SCSI device. You should reduce the default value of 16
717 only if you have disks with buggy or limited tagged command support.
718 Minimum is 2 and maximum is 62. This value is also the window size
719 used by the elevator sorting option above. The effective value used
720 by the driver for each probed SCSI device is reported at boot time.
721 This is equivalent to the "eata=mq:8" boot option.
724 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
725 depends on (ISA || EISA || PCI) && SCSI && BROKEN
727 This driver supports all EATA-PIO protocol compliant SCSI Host
728 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
729 host adapters could also use this driver but are discouraged from
730 doing so, since this driver only supports hard disks and lacks
731 numerous features. You might want to have a look at the SCSI-HOWTO,
732 available from <http://www.tldp.org/docs.html#howto>.
734 To compile this driver as a module, choose M here: the
735 module will be called eata_pio.
737 config SCSI_FUTURE_DOMAIN
738 tristate "Future Domain 16xx SCSI/AHA-2920A support"
739 depends on (ISA || PCI) && SCSI
740 select CHECK_SIGNATURE
742 This is support for Future Domain's 16-bit SCSI host adapters
743 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
744 other adapters based on the Future Domain chipsets (Quantum
745 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
746 It is explained in section 3.7 of the SCSI-HOWTO, available from
747 <http://www.tldp.org/docs.html#howto>.
749 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
750 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
751 controller support"). This Future Domain driver works with the older
752 Adaptec AHA-2920A boards with a Future Domain chip on them.
754 To compile this driver as a module, choose M here: the
755 module will be called fdomain.
758 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
759 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
761 Formerly called GDT SCSI Disk Array Controller Support.
763 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
764 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
765 in the kernel source in <file:drivers/scsi/gdth.c> and
766 <file:drivers/scsi/gdth.h>.
768 To compile this driver as a module, choose M here: the
769 module will be called gdth.
772 tristate "Intel(R) C600 Series Chipset SAS Controller"
773 depends on PCI && SCSI
775 select SCSI_SAS_LIBSAS
777 This driver supports the 6Gb/s SAS capabilities of the storage
778 control unit found in the Intel(R) C600 series chipset.
780 config SCSI_GENERIC_NCR5380
781 tristate "Generic NCR5380/53c400 SCSI PIO support"
782 depends on ISA && SCSI
783 select SCSI_SPI_ATTRS
785 This is a driver for the old NCR 53c80 series of SCSI controllers
786 on boards using PIO. Most boards such as the Trantor T130 fit this
787 category, along with a large number of ISA 8bit controllers shipped
788 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
789 you should select the specific driver for that card rather than
790 generic 5380 support.
792 It is explained in section 3.8 of the SCSI-HOWTO, available from
793 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
794 of the box, you may have to change some settings in
795 <file:drivers/scsi/g_NCR5380.h>.
797 To compile this driver as a module, choose M here: the
798 module will be called g_NCR5380.
800 config SCSI_GENERIC_NCR5380_MMIO
801 tristate "Generic NCR5380/53c400 SCSI MMIO support"
802 depends on ISA && SCSI
803 select SCSI_SPI_ATTRS
805 This is a driver for the old NCR 53c80 series of SCSI controllers
806 on boards using memory mapped I/O.
807 It is explained in section 3.8 of the SCSI-HOWTO, available from
808 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
809 of the box, you may have to change some settings in
810 <file:drivers/scsi/g_NCR5380.h>.
812 To compile this driver as a module, choose M here: the
813 module will be called g_NCR5380_mmio.
815 config SCSI_GENERIC_NCR53C400
816 bool "Enable NCR53c400 extensions"
817 depends on SCSI_GENERIC_NCR5380
819 This enables certain optimizations for the NCR53c400 SCSI cards.
820 You might as well try it out. Note that this driver will only probe
821 for the Trantor T130B in its default configuration; you might have
822 to pass a command line option to the kernel at boot time if it does
823 not detect your card. See the file
824 <file:Documentation/scsi/g_NCR5380.txt> for details.
827 tristate "IBM ServeRAID support"
828 depends on PCI && SCSI
830 This is support for the IBM ServeRAID hardware RAID controllers.
831 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
832 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
833 for more information. If this driver does not work correctly
834 without modification please contact the author by email at
835 <ipslinux@adaptec.com>.
837 To compile this driver as a module, choose M here: the
838 module will be called ips.
841 tristate "IBM Virtual SCSI support"
842 depends on PPC_PSERIES
843 select SCSI_SRP_ATTRS
845 This is the IBM POWER Virtual SCSI Client
847 To compile this driver as a module, choose M here: the
848 module will be called ibmvscsi.
851 tristate "IBM Virtual FC support"
852 depends on PPC_PSERIES && SCSI
853 depends on SCSI_FC_ATTRS
855 This is the IBM POWER Virtual FC Client
857 To compile this driver as a module, choose M here: the
858 module will be called ibmvfc.
860 config SCSI_IBMVFC_TRACE
861 bool "enable driver internal trace"
862 depends on SCSI_IBMVFC
865 If you say Y here, the driver will trace all commands issued
866 to the adapter. Performance impact is minimal. Trace can be
867 dumped using /sys/class/scsi_host/hostXX/trace.
870 tristate "Initio 9100U(W) support"
871 depends on PCI && SCSI
873 This is support for the Initio 91XXU(W) SCSI host adapter. Please
874 read the SCSI-HOWTO, available from
875 <http://www.tldp.org/docs.html#howto>.
877 To compile this driver as a module, choose M here: the
878 module will be called initio.
881 tristate "Initio INI-A100U2W support"
882 depends on PCI && SCSI
884 This is support for the Initio INI-A100U2W SCSI host adapter.
885 Please read the SCSI-HOWTO, available from
886 <http://www.tldp.org/docs.html#howto>.
888 To compile this driver as a module, choose M here: the
889 module will be called a100u2w.
892 tristate "IOMEGA parallel port (ppa - older drives)"
893 depends on SCSI && PARPORT_PC
895 This driver supports older versions of IOMEGA's parallel port ZIP
896 drive (a 100 MB removable media device).
898 Note that you can say N here if you have the SCSI version of the ZIP
899 drive: it will be supported automatically if you said Y to the
900 generic "SCSI disk support", above.
902 If you have the ZIP Plus drive or a more recent parallel port ZIP
903 drive (if the supplied cable with the drive is labeled "AutoDetect")
904 then you should say N here and Y to "IOMEGA parallel port (imm -
905 newer drives)", below.
907 For more information about this driver and how to use it you should
908 read the file <file:Documentation/scsi/ppa.txt>. You should also read
909 the SCSI-HOWTO, which is available from
910 <http://www.tldp.org/docs.html#howto>. If you use this driver,
911 you will still be able to use the parallel port for other tasks,
912 such as a printer; it is safe to compile both drivers into the
915 To compile this driver as a module, choose M here: the
916 module will be called ppa.
919 tristate "IOMEGA parallel port (imm - newer drives)"
920 depends on SCSI && PARPORT_PC
922 This driver supports newer versions of IOMEGA's parallel port ZIP
923 drive (a 100 MB removable media device).
925 Note that you can say N here if you have the SCSI version of the ZIP
926 drive: it will be supported automatically if you said Y to the
927 generic "SCSI disk support", above.
929 If you have the ZIP Plus drive or a more recent parallel port ZIP
930 drive (if the supplied cable with the drive is labeled "AutoDetect")
931 then you should say Y here; if you have an older ZIP drive, say N
932 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
934 For more information about this driver and how to use it you should
935 read the file <file:Documentation/scsi/ppa.txt>. You should also read
936 the SCSI-HOWTO, which is available from
937 <http://www.tldp.org/docs.html#howto>. If you use this driver,
938 you will still be able to use the parallel port for other tasks,
939 such as a printer; it is safe to compile both drivers into the
942 To compile this driver as a module, choose M here: the
943 module will be called imm.
945 config SCSI_IZIP_EPP16
946 bool "ppa/imm option - Use slow (but safe) EPP-16"
947 depends on SCSI_PPA || SCSI_IMM
949 EPP (Enhanced Parallel Port) is a standard for parallel ports which
950 allows them to act as expansion buses that can handle up to 64
953 Some parallel port chipsets are slower than their motherboard, and
954 so we have to control the state of the chipset's FIFO queue every
955 now and then to avoid data loss. This will be done if you say Y
958 Generally, saying Y is the safe option and slows things down a bit.
960 config SCSI_IZIP_SLOW_CTR
961 bool "ppa/imm option - Assume slow parport control register"
962 depends on SCSI_PPA || SCSI_IMM
964 Some parallel ports are known to have excessive delays between
965 changing the parallel port control register and good data being
966 available on the parallel port data/status register. This option
967 forces a small delay (1.0 usec to be exact) after changing the
968 control register to let things settle out. Enabling this option may
969 result in a big drop in performance but some very old parallel ports
970 (found in 386 vintage machines) will not work properly.
972 Generally, saying N is fine.
974 config SCSI_NCR53C406A
975 tristate "NCR53c406a SCSI support"
976 depends on ISA && SCSI
978 This is support for the NCR53c406a SCSI host adapter. For user
979 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
980 in the kernel source. Also read the SCSI-HOWTO, available from
981 <http://www.tldp.org/docs.html#howto>.
983 To compile this driver as a module, choose M here: the
984 module will be called NCR53c406.
987 tristate "NCR Dual 700 MCA SCSI support"
988 depends on MCA && SCSI
989 select SCSI_SPI_ATTRS
991 This is a driver for the MicroChannel Dual 700 card produced by
992 NCR and commonly used in 345x/35xx/4100 class machines. It always
993 tries to negotiate sync and uses tag command queueing.
995 Unless you have an NCR manufactured machine, the chances are that
996 you do not have this SCSI card, so say N.
999 tristate "HP Lasi SCSI support for 53c700/710"
1000 depends on GSC && SCSI
1001 select SCSI_SPI_ATTRS
1003 This is a driver for the SCSI controller in the Lasi chip found in
1004 many PA-RISC workstations & servers. If you do not know whether you
1005 have a Lasi chip, it is safe to say "Y" here.
1007 config SCSI_SNI_53C710
1008 tristate "SNI RM SCSI support for 53c710"
1009 depends on SNI_RM && SCSI
1010 select SCSI_SPI_ATTRS
1011 select 53C700_LE_ON_BE
1013 This is a driver for the onboard SCSI controller found in older
1014 SNI RM workstations & servers.
1016 config 53C700_LE_ON_BE
1018 depends on SCSI_LASI700
1022 tristate "Promise SuperTrak EX Series support"
1023 depends on PCI && SCSI
1025 This driver supports Promise SuperTrak EX series storage controllers.
1027 Promise provides Linux RAID configuration utility for these
1028 controllers. Please visit <http://www.promise.com> to download.
1030 To compile this driver as a module, choose M here: the
1031 module will be called stex.
1033 config 53C700_BE_BUS
1035 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1038 config SCSI_SYM53C8XX_2
1039 tristate "SYM53C8XX Version 2 SCSI support"
1040 depends on PCI && SCSI
1041 select SCSI_SPI_ATTRS
1043 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1044 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1045 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1046 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1047 controllers; you need to use the Fusion MPT driver for that.
1049 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1052 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1053 int "DMA addressing mode"
1054 depends on SCSI_SYM53C8XX_2
1057 This option only applies to PCI-SCSI chips that are PCI DAC
1058 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1060 When set to 0, the driver will program the chip to only perform
1061 32-bit DMA. When set to 1, the chip will be able to perform DMA
1062 to addresses up to 1TB. When set to 2, the driver supports the
1063 full 64-bit DMA address range, but can only address 16 segments
1064 of 4 GB each. This limits the total addressable range to 64 GB.
1066 Most machines with less than 4GB of memory should use a setting
1067 of 0 for best performance. If your machine has 4GB of memory
1068 or more, you should set this option to 1 (the default).
1070 The still experimental value 2 (64 bit DMA addressing with 16
1071 x 4GB segments limitation) can be used on systems that require
1072 PCI address bits past bit 39 to be set for the addressing of
1073 memory using PCI DAC cycles.
1075 config SCSI_SYM53C8XX_DEFAULT_TAGS
1076 int "Default tagged command queue depth"
1077 depends on SCSI_SYM53C8XX_2
1080 This is the default value of the command queue depth the
1081 driver will announce to the generic SCSI layer for devices
1082 that support tagged command queueing. This value can be changed
1083 from the boot command line. This is a soft limit that cannot
1084 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1086 config SCSI_SYM53C8XX_MAX_TAGS
1087 int "Maximum number of queued commands"
1088 depends on SCSI_SYM53C8XX_2
1091 This option allows you to specify the maximum number of commands
1092 that can be queued to any device, when tagged command queuing is
1093 possible. The driver supports up to 256 queued commands per device.
1094 This value is used as a compiled-in hard limit.
1096 config SCSI_SYM53C8XX_MMIO
1097 bool "Use memory mapped IO"
1098 depends on SCSI_SYM53C8XX_2
1101 Memory mapped IO is faster than Port IO. Most people should
1102 answer Y here, but some machines may have problems. If you have
1103 to answer N here, please report the problem to the maintainer.
1106 tristate "IBM Power Linux RAID adapter support"
1107 depends on PCI && SCSI && ATA
1111 This driver supports the IBM Power Linux family RAID adapters.
1112 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1113 as IBM iSeries 5702, 5703, 5709, and 570A.
1115 config SCSI_IPR_TRACE
1116 bool "enable driver internal trace"
1120 If you say Y here, the driver will trace all commands issued
1121 to the adapter. Performance impact is minimal. Trace can be
1122 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1124 config SCSI_IPR_DUMP
1125 bool "enable adapter dump support"
1129 If you say Y here, the driver will support adapter crash dump.
1130 If you enable this support, the iprdump daemon can be used
1131 to capture adapter failure analysis information.
1134 tristate "Zalon SCSI support"
1135 depends on GSC && SCSI
1136 select SCSI_SPI_ATTRS
1138 The Zalon is a GSC/HSC bus interface chip that sits between the
1139 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1140 C110, J200, J210 and some D, K & R-class machines. It's also
1141 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1142 Say Y here if you have one of these machines or cards.
1144 config SCSI_NCR_Q720
1145 tristate "NCR Quad 720 MCA SCSI support"
1146 depends on MCA && SCSI
1147 select SCSI_SPI_ATTRS
1149 This is a driver for the MicroChannel Quad 720 card produced by
1150 NCR and commonly used in 345x/35xx/4100 class machines. It always
1151 tries to negotiate sync and uses tag command queueing.
1153 Unless you have an NCR manufactured machine, the chances are that
1154 you do not have this SCSI card, so say N.
1156 config SCSI_NCR53C8XX_DEFAULT_TAGS
1157 int "default tagged command queue depth"
1158 depends on SCSI_ZALON || SCSI_NCR_Q720
1161 "Tagged command queuing" is a feature of SCSI-2 which improves
1162 performance: the host adapter can send several SCSI commands to a
1163 device's queue even if previous commands haven't finished yet.
1164 Because the device is intelligent, it can optimize its operations
1165 (like head positioning) based on its own request queue. Some SCSI
1166 devices don't implement this properly; if you want to disable this
1167 feature, enter 0 or 1 here (it doesn't matter which).
1169 The default value is 8 and should be supported by most hard disks.
1170 This value can be overridden from the boot command line using the
1171 'tags' option as follows (example):
1172 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1173 4, set queue depth to 16 for target 2 and target 3 on controller 0
1174 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1176 The normal answer therefore is to go with the default 8 and to use
1177 a boot command line option for devices that need to use a different
1178 command queue depth.
1180 There is no safe option other than using good SCSI devices.
1182 config SCSI_NCR53C8XX_MAX_TAGS
1183 int "maximum number of queued commands"
1184 depends on SCSI_ZALON || SCSI_NCR_Q720
1187 This option allows you to specify the maximum number of commands
1188 that can be queued to any device, when tagged command queuing is
1189 possible. The default value is 32. Minimum is 2, maximum is 64.
1190 Modern hard disks are able to support 64 tags and even more, but
1191 do not seem to be faster when more than 32 tags are being used.
1193 So, the normal answer here is to go with the default value 32 unless
1194 you are using very large hard disks with large cache (>= 1 MB) that
1195 are able to take advantage of more than 32 tagged commands.
1197 There is no safe option and the default answer is recommended.
1199 config SCSI_NCR53C8XX_SYNC
1200 int "synchronous transfers frequency in MHz"
1201 depends on SCSI_ZALON || SCSI_NCR_Q720
1204 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1205 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1206 are respectively the maximum data transfer rates in mega-transfers
1207 per second for each class. For example, a FAST-20 Wide 16 device is
1208 able to transfer data at 20 million 16 bit packets per second for a
1209 total rate of 40 MB/s.
1211 You may specify 0 if you want to only use asynchronous data
1212 transfers. This is the safest and slowest option. Otherwise, specify
1213 a value between 5 and 80, depending on the capability of your SCSI
1214 controller. The higher the number, the faster the data transfer.
1215 Note that 80 should normally be ok since the driver decreases the
1216 value automatically according to the controller's capabilities.
1218 Your answer to this question is ignored for controllers with NVRAM,
1219 since the driver will get this information from the user set-up. It
1220 also can be overridden using a boot setup option, as follows
1221 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1222 for FAST-20 synchronous data transfer (20 mega-transfers per
1225 The normal answer therefore is not to go with the default but to
1226 select the maximum value 80 allowing the driver to use the maximum
1227 value supported by each controller. If this causes problems with
1228 your SCSI devices, you should come back and decrease the value.
1230 There is no safe option other than using good cabling, right
1231 terminations and SCSI conformant devices.
1233 config SCSI_NCR53C8XX_NO_DISCONNECT
1234 bool "not allow targets to disconnect"
1235 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1237 This option is only provided for safety if you suspect some SCSI
1238 device of yours to not support properly the target-disconnect
1239 feature. In that case, you would say Y here. In general however, to
1240 not allow targets to disconnect is not reasonable if there is more
1241 than 1 device on a SCSI bus. The normal answer therefore is N.
1244 tristate "PAS16 SCSI support"
1245 depends on ISA && SCSI
1246 select SCSI_SPI_ATTRS
1248 This is support for a SCSI host adapter. It is explained in section
1249 3.10 of the SCSI-HOWTO, available from
1250 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1251 of the box, you may have to change some settings in
1252 <file:drivers/scsi/pas16.h>.
1254 To compile this driver as a module, choose M here: the
1255 module will be called pas16.
1257 config SCSI_QLOGIC_FAS
1258 tristate "Qlogic FAS SCSI support"
1259 depends on ISA && SCSI
1261 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1262 FastSCSI! cards as well as any other card based on the FASXX chip
1263 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1265 This driver does NOT support the PCI versions of these cards. The
1266 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1267 SCSI support"), below.
1269 Information about this driver is contained in
1270 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1271 SCSI-HOWTO, available from
1272 <http://www.tldp.org/docs.html#howto>.
1274 To compile this driver as a module, choose M here: the
1275 module will be called qlogicfas.
1277 config SCSI_QLOGIC_1280
1278 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1279 depends on PCI && SCSI
1281 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1283 To compile this driver as a module, choose M here: the
1284 module will be called qla1280.
1286 config SCSI_QLOGICPTI
1287 tristate "PTI Qlogic, ISP Driver"
1288 depends on SBUS && SCSI
1290 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1291 controllers are known under Solaris as qpti and in the openprom as
1292 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1293 driven by a different driver.
1295 To compile this driver as a module, choose M here: the
1296 module will be called qlogicpti.
1298 source "drivers/scsi/qla2xxx/Kconfig"
1299 source "drivers/scsi/qla4xxx/Kconfig"
1302 tristate "Emulex LightPulse Fibre Channel Support"
1303 depends on PCI && SCSI
1304 depends on SCSI_FC_ATTRS
1307 This lpfc driver supports the Emulex LightPulse
1308 Family of Fibre Channel PCI host adapters.
1310 config SCSI_LPFC_DEBUG_FS
1311 bool "Emulex LightPulse Fibre Channel debugfs Support"
1312 depends on SCSI_LPFC && DEBUG_FS
1314 This makes debugging information from the lpfc driver
1315 available via the debugfs filesystem.
1318 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1319 depends on (EISA || MCA) && SCSI
1320 select SCSI_SPI_ATTRS
1322 This driver is for NCR53c710 based SCSI host adapters.
1324 It currently supports Compaq EISA cards and NCR MCA cards
1326 config SCSI_SYM53C416
1327 tristate "Symbios 53c416 SCSI support"
1328 depends on ISA && SCSI
1330 This is support for the sym53c416 SCSI host adapter, the SCSI
1331 adapter that comes with some HP scanners. This driver requires that
1332 the sym53c416 is configured first using some sort of PnP
1333 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1334 are using isapnp then you need to compile this driver as a module
1335 and then load it using insmod after isapnp has run. The parameters
1336 of the configured card(s) should be passed to the driver. The format
1339 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1341 To compile this driver as a module, choose M here: the
1342 module will be called sym53c416.
1345 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1346 depends on PCI && SCSI
1348 This driver supports PCI SCSI host adapters based on the ASIC
1349 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1351 This driver works, but is still in experimental status. So better
1352 have a bootable disk and a backup in case of emergency.
1354 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1356 To compile this driver as a module, choose M here: the
1357 module will be called dc395x.
1359 config SCSI_AM53C974
1360 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1361 depends on PCI && SCSI
1362 select SCSI_SPI_ATTRS
1364 This driver supports PCI SCSI host adapters based on the Am53C974A
1365 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1366 PCscsi/PCnet (Am53/79C974) solutions.
1367 This is a new implementation base on the generic esp_scsi driver.
1369 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1371 Note that this driver does NOT support Tekram DC390W/U/F, which are
1372 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1374 To compile this driver as a module, choose M here: the
1375 module will be called am53c974.
1378 tristate "Trantor T128/T128F/T228 SCSI support"
1379 depends on ISA && SCSI
1380 select SCSI_SPI_ATTRS
1381 select CHECK_SIGNATURE
1383 This is support for a SCSI host adapter. It is explained in section
1384 3.11 of the SCSI-HOWTO, available from
1385 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1386 of the box, you may have to change some settings in
1387 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1388 Adaptec, and some former Trantor products are being sold under the
1391 To compile this driver as a module, choose M here: the
1392 module will be called t128.
1395 tristate "UltraStor 14F/34F support"
1396 depends on ISA && SCSI && ISA_DMA_API
1398 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1399 The source at <file:drivers/scsi/u14-34f.c> contains some
1400 information about this hardware. If the driver doesn't work out of
1401 the box, you may have to change some settings in
1402 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1403 <http://www.tldp.org/docs.html#howto>. Note that there is also
1404 another driver for the same hardware: "UltraStor SCSI support",
1405 below. You should say Y to both only if you want 24F support as
1408 To compile this driver as a module, choose M here: the
1409 module will be called u14-34f.
1411 config SCSI_U14_34F_TAGGED_QUEUE
1412 bool "enable tagged command queueing"
1413 depends on SCSI_U14_34F
1415 This is a feature of SCSI-2 which improves performance: the host
1416 adapter can send several SCSI commands to a device's queue even if
1417 previous commands haven't finished yet.
1418 This is equivalent to the "u14-34f=tc:y" boot option.
1420 config SCSI_U14_34F_LINKED_COMMANDS
1421 bool "enable elevator sorting"
1422 depends on SCSI_U14_34F
1424 This option enables elevator sorting for all probed SCSI disks and
1425 CD-ROMs. It definitely reduces the average seek distance when doing
1426 random seeks, but this does not necessarily result in a noticeable
1427 performance improvement: your mileage may vary...
1428 This is equivalent to the "u14-34f=lc:y" boot option.
1430 config SCSI_U14_34F_MAX_TAGS
1431 int "maximum number of queued commands"
1432 depends on SCSI_U14_34F
1435 This specifies how many SCSI commands can be maximally queued for
1436 each probed SCSI device. You should reduce the default value of 8
1437 only if you have disks with buggy or limited tagged command support.
1438 Minimum is 2 and maximum is 14. This value is also the window size
1439 used by the elevator sorting option above. The effective value used
1440 by the driver for each probed SCSI device is reported at boot time.
1441 This is equivalent to the "u14-34f=mq:8" boot option.
1443 config SCSI_ULTRASTOR
1444 tristate "UltraStor SCSI support"
1445 depends on X86 && ISA && SCSI
1447 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1448 adapter family. This driver is explained in section 3.12 of the
1449 SCSI-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1451 of the box, you may have to change some settings in
1452 <file:drivers/scsi/ultrastor.h>.
1454 Note that there is also another driver for the same hardware:
1455 "UltraStor 14F/34F support", above.
1457 To compile this driver as a module, choose M here: the
1458 module will be called ultrastor.
1461 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1462 depends on PCI && SCSI && !64BIT
1464 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1465 SCSI host adapter. Please read the SCSI-HOWTO, available from
1466 <http://www.tldp.org/docs.html#howto>.
1468 To compile this driver as a module, choose M here: the
1469 module will be called nsp32.
1472 tristate "Western Digital WD7193/7197/7296 support"
1473 depends on PCI && SCSI
1476 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1477 SCSI controllers (based on WD33C296A chip).
1480 tristate "SCSI debugging host and device simulator"
1484 This pseudo driver simulates one or more hosts (SCSI initiators),
1485 each with one or more targets, each with one or more logical units.
1486 Defaults to one of each, creating a small RAM disk device. Many
1487 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1488 directory can be tweaked at run time.
1489 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1490 Mainly used for testing and best as a module. If unsure, say N.
1493 tristate "MESH (Power Mac internal SCSI) support"
1494 depends on PPC32 && PPC_PMAC && SCSI
1496 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1497 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1498 other Power Macintoshes do). Say Y to include support for this SCSI
1501 To compile this driver as a module, choose M here: the
1502 module will be called mesh.
1504 config SCSI_MESH_SYNC_RATE
1505 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1506 depends on SCSI_MESH
1509 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1510 drives a bus which is entirely internal to the machine (such as the
1511 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1512 operation at up to 10 MB/s. On machines where the SCSI bus
1513 controlled by the MESH can have external devices connected, it is
1514 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1515 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1516 to disable synchronous operation.
1518 config SCSI_MESH_RESET_DELAY_MS
1519 int "initial bus reset delay (ms) (0 = no reset)"
1520 depends on SCSI_MESH
1523 config SCSI_MAC53C94
1524 tristate "53C94 (Power Mac external SCSI) support"
1525 depends on PPC32 && PPC_PMAC && SCSI
1527 On Power Macintoshes (and clones) with two SCSI buses, the external
1528 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1529 machines which only have one SCSI bus, such as the 7200, also use
1530 the 53C94. Say Y to include support for the 53C94.
1532 To compile this driver as a module, choose M here: the
1533 module will be called mac53c94.
1535 source "drivers/scsi/arm/Kconfig"
1538 bool "MIPS JAZZ FAS216 SCSI support"
1539 depends on MACH_JAZZ && SCSI
1540 select SCSI_SPI_ATTRS
1542 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1543 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1547 tristate "A3000 WD33C93A support"
1548 depends on AMIGA && SCSI
1550 If you have an Amiga 3000 and have SCSI devices connected to the
1551 built-in SCSI controller, say Y. Otherwise, say N.
1553 To compile this driver as a module, choose M here: the
1554 module will be called a3000.
1557 tristate "A2091/A590 WD33C93A support"
1558 depends on ZORRO && SCSI
1560 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1563 To compile this driver as a module, choose M here: the
1564 module will be called a2091.
1567 tristate "GVP Series II WD33C93A support"
1568 depends on ZORRO && SCSI
1570 If you have a Great Valley Products Series II SCSI controller,
1571 answer Y. Also say Y if you have a later model of GVP SCSI
1572 controller (such as the GVP A4008 or a Combo board). Otherwise,
1573 answer N. This driver does NOT work for the T-Rex series of
1574 accelerators from TekMagic and GVP-M.
1576 To compile this driver as a module, choose M here: the
1577 module will be called gvp11.
1580 tristate "A4000T NCR53c710 SCSI support"
1581 depends on AMIGA && SCSI
1582 select SCSI_SPI_ATTRS
1584 If you have an Amiga 4000T and have SCSI devices connected to the
1585 built-in SCSI controller, say Y. Otherwise, say N.
1587 To compile this driver as a module, choose M here: the
1588 module will be called a4000t.
1590 config SCSI_ZORRO7XX
1591 tristate "Zorro NCR53c710 SCSI support"
1592 depends on ZORRO && SCSI
1593 select SCSI_SPI_ATTRS
1595 Support for various NCR53c710-based SCSI controllers on Zorro
1596 expansion boards for the Amiga.
1598 - the Amiga 4091 Zorro III SCSI-2 controller,
1599 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1601 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1602 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1603 accelerator card for the Amiga 1200,
1604 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1607 tristate "Atari native SCSI support"
1608 depends on ATARI && SCSI
1609 select SCSI_SPI_ATTRS
1612 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1613 Falcon, ...) say Y to get it supported. Of course also, if you have
1614 a compatible SCSI controller (e.g. for Medusa).
1616 To compile this driver as a module, choose M here: the
1617 module will be called atari_scsi.
1619 This driver supports both styles of NCR integration into the
1620 system: the TT style (separate DMA), and the Falcon style (via
1621 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1622 in the Hades (without DMA).
1625 tristate "Macintosh NCR5380 SCSI"
1626 depends on MAC && SCSI=y
1627 select SCSI_SPI_ATTRS
1629 This is the NCR 5380 SCSI controller included on most of the 68030
1630 based Macintoshes. If you have one of these say Y and read the
1631 SCSI-HOWTO, available from
1632 <http://www.tldp.org/docs.html#howto>.
1635 tristate "Macintosh NCR53c9[46] SCSI"
1636 depends on MAC && SCSI
1637 select SCSI_SPI_ATTRS
1639 This is the NCR 53c9x SCSI controller found on most of the 68040
1642 To compile this driver as a module, choose M here: the module
1643 will be called mac_esp.
1646 bool "WD33C93 SCSI driver for MVME147"
1647 depends on MVME147 && SCSI=y
1648 select SCSI_SPI_ATTRS
1650 Support for the on-board SCSI controller on the Motorola MVME147
1651 single-board computer.
1654 tristate "NCR53C710 SCSI driver for MVME16x"
1655 depends on MVME16x && SCSI
1656 select SCSI_SPI_ATTRS
1658 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1659 SCSI controller chip. Almost everyone using one of these boards
1660 will want to say Y to this question.
1662 config BVME6000_SCSI
1663 tristate "NCR53C710 SCSI driver for BVME6000"
1664 depends on BVME6000 && SCSI
1665 select SCSI_SPI_ATTRS
1667 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1668 SCSI controller chip. Almost everyone using one of these boards
1669 will want to say Y to this question.
1672 tristate "Sun3 NCR5380 SCSI"
1673 depends on SUN3 && SCSI
1674 select SCSI_SPI_ATTRS
1676 This option will enable support for the OBIO (onboard io) NCR5380
1677 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1678 "Sun3" type VME scsi controllers also based on the NCR5380.
1679 General Linux information on the Sun 3 series (now discontinued)
1680 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1683 bool "Sun3x ESP SCSI"
1684 depends on SUN3X && SCSI=y
1685 select SCSI_SPI_ATTRS
1687 The ESP was an on-board SCSI controller used on Sun 3/80
1688 machines. Say Y here to compile in support for it.
1691 tristate "Sparc ESP Scsi Driver"
1692 depends on SBUS && SCSI
1693 select SCSI_SPI_ATTRS
1695 This is the driver for the Sun ESP SCSI host adapter. The ESP
1696 chipset is present in most SPARC SBUS-based computers and
1697 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1698 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1700 To compile this driver as a module, choose M here: the
1701 module will be called sun_esp.
1704 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1705 depends on S390 && QDIO && SCSI
1706 depends on SCSI_FC_ATTRS
1708 If you want to access SCSI devices attached to your IBM eServer
1709 zSeries by means of Fibre Channel interfaces say Y.
1710 For details please refer to the documentation provided by IBM at
1711 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1713 This driver is also available as a module. This module will be
1714 called zfcp. If you want to compile it as a module, say M here
1715 and read <file:Documentation/kbuild/modules.txt>.
1718 tristate "PMC SIERRA Linux MaxRAID adapter support"
1719 depends on PCI && SCSI && NET
1721 This driver supports the PMC SIERRA MaxRAID adapters.
1724 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1725 depends on PCI && SCSI
1726 select SCSI_SAS_LIBSAS
1728 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1729 based host adapters.
1732 tristate "Brocade BFA Fibre Channel Support"
1733 depends on PCI && SCSI
1734 depends on SCSI_FC_ATTRS
1736 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1738 To compile this driver as a module, choose M here. The module will
1742 tristate "virtio-scsi support"
1745 This is the virtual HBA driver for virtio. If the kernel will
1746 be used in a virtual machine, say Y or M.
1748 source "drivers/scsi/csiostor/Kconfig"
1750 endif # SCSI_LOWLEVEL
1752 source "drivers/scsi/pcmcia/Kconfig"
1754 source "drivers/scsi/device_handler/Kconfig"
1756 source "drivers/scsi/osd/Kconfig"