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
198 Enclosures are devices sitting on or in SCSI backplanes that
199 manage devices. If you have a disk cage, the chances are that
200 it has an enclosure device. Selecting this option will just allow
201 certain enclosure conditions to be reported and is not required.
203 config SCSI_CONSTANTS
204 bool "Verbose SCSI error reporting (kernel size +=75K)"
207 The error messages regarding your SCSI hardware will be easier to
208 understand if you say Y here; it will enlarge your kernel by about
209 75 KB. If in doubt, say Y.
212 bool "SCSI logging facility"
215 This turns on a logging facility that can be used to debug a number
216 of SCSI related problems.
218 If you say Y here, no logging output will appear by default, but you
219 can enable logging by saying Y to "/proc file system support" and
220 "Sysctl support" below and executing the command
222 echo <bitmask> > /proc/sys/dev/scsi/logging_level
224 where <bitmask> is a four byte value representing the logging type
225 and logging level for each type of logging selected.
227 There are a number of logging types and you can find them in the
228 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
229 are also described in that file and they determine the verbosity of
230 the logging for each logging type.
232 If you say N here, it may be harder to track down some types of SCSI
233 problems. If you say Y here your kernel will be somewhat larger, but
234 there should be no noticeable performance impact as long as you have
237 config SCSI_SCAN_ASYNC
238 bool "Asynchronous SCSI scanning"
241 The SCSI subsystem can probe for devices while the rest of the
242 system continues booting, and even probe devices on different
243 busses in parallel, leading to a significant speed-up.
245 If you have built SCSI as modules, enabling this option can
246 be a problem as the devices may not have been found by the
247 time your system expects them to have been. You can load the
248 scsi_wait_scan module to ensure that all scans have completed.
249 If you build your SCSI drivers into the kernel, then everything
250 will work fine if you say Y here.
252 You can override this choice by specifying "scsi_mod.scan=sync"
253 or async on the kernel's command line.
255 Note that this setting also affects whether resuming from
256 system suspend will be performed asynchronously.
258 menu "SCSI Transports"
261 config SCSI_SPI_ATTRS
262 tristate "Parallel SCSI (SPI) Transport Attributes"
265 If you wish to export transport-specific information about
266 each attached SCSI device to sysfs, say Y. Otherwise, say N.
269 tristate "FiberChannel Transport Attributes"
270 depends on SCSI && NET
273 If you wish to export transport-specific information about
274 each attached FiberChannel device to sysfs, say Y.
277 config SCSI_ISCSI_ATTRS
278 tristate "iSCSI Transport Attributes"
279 depends on SCSI && NET
280 select BLK_DEV_BSGLIB
282 If you wish to export transport-specific information about
283 each attached iSCSI device to sysfs, say Y.
286 config SCSI_SAS_ATTRS
287 tristate "SAS Transport Attributes"
291 If you wish to export transport-specific information about
292 each attached SAS device to sysfs, say Y.
294 source "drivers/scsi/libsas/Kconfig"
296 config SCSI_SRP_ATTRS
297 tristate "SRP Transport Attributes"
300 If you wish to export transport-specific information about
301 each attached SRP device to sysfs, say Y.
305 menuconfig SCSI_LOWLEVEL
306 bool "SCSI low-level drivers"
310 if SCSI_LOWLEVEL && SCSI
313 tristate "iSCSI Initiator over TCP/IP"
314 depends on SCSI && INET
318 select SCSI_ISCSI_ATTRS
320 The iSCSI Driver provides a host with the ability to access storage
321 through an IP network. The driver uses the iSCSI protocol to transport
322 SCSI requests and responses over a TCP/IP network between the host
323 (the "initiator") and "targets". Architecturally, the iSCSI driver
324 combines with the host's TCP/IP stack, network drivers, and Network
325 Interface Card (NIC) to provide the same functions as a SCSI or a
326 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
328 To compile this driver as a module, choose M here: the
329 module will be called iscsi_tcp.
331 The userspace component needed to initialize the driver, documentation,
332 and sample configuration files can be found here:
334 http://open-iscsi.org
336 config ISCSI_BOOT_SYSFS
337 tristate "iSCSI Boot Sysfs Interface"
340 This option enables support for exposing iSCSI boot information
341 via sysfs to userspace. If you wish to export this information,
342 say Y. Otherwise, say N.
344 source "drivers/scsi/cxgbi/Kconfig"
345 source "drivers/scsi/bnx2i/Kconfig"
346 source "drivers/scsi/bnx2fc/Kconfig"
347 source "drivers/scsi/be2iscsi/Kconfig"
350 tristate "SGI WD93C93 SCSI Driver"
351 depends on SGI_HAS_WD93 && SCSI
353 If you have a Western Digital WD93 SCSI controller on
354 an SGI MIPS system, say Y. Otherwise, say N.
356 config BLK_DEV_3W_XXXX_RAID
357 tristate "3ware 5/6/7/8xxx ATA-RAID support"
358 depends on PCI && SCSI
360 3ware is the only hardware ATA-Raid product in Linux to date.
361 This card is 2,4, or 8 channel master mode support only.
362 SCSI support required!!!
364 <http://www.3ware.com/>
366 Please read the comments at the top of
367 <file:drivers/scsi/3w-xxxx.c>.
370 tristate "HP Smart Array SCSI driver"
371 depends on PCI && SCSI
372 select CHECK_SIGNATURE
374 This driver supports HP Smart Array Controllers (circa 2009).
375 It is a SCSI alternative to the cciss driver, which is a block
376 driver. Anyone wishing to use HP Smart Array controllers who
377 would prefer the devices be presented to linux as SCSI devices,
378 rather than as generic block devices should say Y here.
381 tristate "3ware 9xxx SATA-RAID support"
382 depends on PCI && SCSI
384 This driver supports the 9000 series 3ware SATA-RAID cards.
386 <http://www.amcc.com>
388 Please read the comments at the top of
389 <file:drivers/scsi/3w-9xxx.c>.
392 tristate "3ware 97xx SAS/SATA-RAID support"
393 depends on PCI && SCSI
395 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
399 Please read the comments at the top of
400 <file:drivers/scsi/3w-sas.c>.
402 config SCSI_7000FASST
403 tristate "7000FASST SCSI support"
404 depends on ISA && SCSI && ISA_DMA_API
405 select CHECK_SIGNATURE
407 This driver supports the Western Digital 7000 SCSI host adapter
408 family. Some information is in the source:
409 <file:drivers/scsi/wd7000.c>.
411 To compile this driver as a module, choose M here: the
412 module will be called wd7000.
415 tristate "ACARD SCSI support"
416 depends on PCI && SCSI
418 This driver supports the ACARD SCSI host adapter.
419 Support Chip <ATP870 ATP876 ATP880 ATP885>
420 To compile this driver as a module, choose M here: the
421 module will be called atp870u.
424 tristate "Adaptec AHA152X/2825 support"
425 depends on ISA && SCSI
426 select SCSI_SPI_ATTRS
427 select CHECK_SIGNATURE
429 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
430 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
431 must be manually specified in this case.
433 It is explained in section 3.3 of the SCSI-HOWTO, available from
434 <http://www.tldp.org/docs.html#howto>. You might also want to
435 read the file <file:Documentation/scsi/aha152x.txt>.
437 To compile this driver as a module, choose M here: the
438 module will be called aha152x.
441 tristate "Adaptec AHA1542 support"
442 depends on ISA && SCSI && ISA_DMA_API
444 This is support for a SCSI host adapter. It is explained in section
445 3.4 of the SCSI-HOWTO, available from
446 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
447 purchased by Adaptec, and some former Trantor products are being
448 sold under the Adaptec name. If it doesn't work out of the box, you
449 may have to change some settings in <file:drivers/scsi/aha1542.h>.
451 To compile this driver as a module, choose M here: the
452 module will be called aha1542.
455 tristate "Adaptec AHA1740 support"
456 depends on EISA && SCSI
458 This is support for a SCSI host adapter. It is explained in section
459 3.5 of the SCSI-HOWTO, available from
460 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
461 of the box, you may have to change some settings in
462 <file:drivers/scsi/aha1740.h>.
464 To compile this driver as a module, choose M here: the
465 module will be called aha1740.
468 tristate "Adaptec AACRAID support"
469 depends on SCSI && PCI
471 This driver supports a variety of Dell, HP, Adaptec, IBM and
472 ICP storage products. For a list of supported products, refer
473 to <file:Documentation/scsi/aacraid.txt>.
475 To compile this driver as a module, choose M here: the module
476 will be called aacraid.
479 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
480 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
481 source "drivers/scsi/aic94xx/Kconfig"
482 source "drivers/scsi/mvsas/Kconfig"
485 tristate "Marvell UMI driver"
486 depends on SCSI && PCI
488 Module for Marvell Universal Message Interface(UMI) driver
490 To compile this driver as a module, choose M here: the
491 module will be called mvumi.
494 tristate "Adaptec I2O RAID support "
495 depends on SCSI && PCI && VIRT_TO_BUS
497 This driver supports all of Adaptec's I2O based RAID controllers as
498 well as the DPT SmartRaid V cards. This is an Adaptec maintained
499 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
501 To compile this driver as a module, choose M here: the
502 module will be called dpt_i2o.
505 tristate "AdvanSys SCSI support"
507 depends on ISA || EISA || PCI
509 This is a driver for all SCSI host adapters manufactured by
510 AdvanSys. It is documented in the kernel source in
511 <file:drivers/scsi/advansys.c>.
513 To compile this driver as a module, choose M here: the
514 module will be called advansys.
517 tristate "Always IN2000 SCSI support"
518 depends on ISA && SCSI
520 This is support for an ISA bus SCSI host adapter. You'll find more
521 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
522 out of the box, you may have to change the jumpers for IRQ or
525 To compile this driver as a module, choose M here: the
526 module will be called in2000.
529 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
530 depends on PCI && SCSI
532 This driver supports all of ARECA's SATA/SAS RAID controller cards.
533 This is an ARECA-maintained driver by Erich Chen.
534 If you have any problems, please mail to: <erich@areca.com.tw>.
535 Areca supports Linux RAID config tools.
536 Please link <http://www.areca.com.tw>
538 To compile this driver as a module, choose M here: the
539 module will be called arcmsr (modprobe arcmsr).
541 source "drivers/scsi/esas2r/Kconfig"
542 source "drivers/scsi/megaraid/Kconfig.megaraid"
543 source "drivers/scsi/mpt2sas/Kconfig"
544 source "drivers/scsi/mpt3sas/Kconfig"
545 source "drivers/scsi/ufs/Kconfig"
548 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
549 depends on SCSI && PCI
551 This option enables support for HighPoint RocketRAID 3xxx/4xxx
554 To compile this driver as a module, choose M here; the module
555 will be called hptiop. If unsure, say N.
558 tristate "BusLogic SCSI support"
559 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
561 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
562 Adapters. Consult the SCSI-HOWTO, available from
563 <http://www.tldp.org/docs.html#howto>, and the files
564 <file:Documentation/scsi/BusLogic.txt> and
565 <file:Documentation/scsi/FlashPoint.txt> for more information.
566 Note that support for FlashPoint is only available for 32-bit
569 To compile this driver as a module, choose M here: the
570 module will be called BusLogic.
572 config SCSI_FLASHPOINT
573 bool "FlashPoint support"
574 depends on SCSI_BUSLOGIC && PCI
576 This option allows you to add FlashPoint support to the
577 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
578 substantial, so users of MultiMaster Host Adapters may not
582 tristate "VMware PVSCSI driver support"
583 depends on PCI && SCSI && X86
585 This driver supports VMware's para virtualized SCSI HBA.
586 To compile this driver as a module, choose M here: the
587 module will be called vmw_pvscsi.
589 config XEN_SCSI_FRONTEND
590 tristate "XEN SCSI frontend driver"
591 depends on SCSI && XEN
592 select XEN_XENBUS_FRONTEND
594 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
595 within another guest OS (usually Dom0).
596 Only needed if the kernel is running in a XEN guest and generic
597 SCSI access to a device is needed.
599 config HYPERV_STORAGE
600 tristate "Microsoft Hyper-V virtual storage driver"
601 depends on SCSI && HYPERV
604 Select this option to enable the Hyper-V virtual storage driver.
607 tristate "LibFC module"
608 depends on SCSI_FC_ATTRS
611 Fibre Channel library module
614 tristate "LibFCoE module"
617 Library for Fibre Channel over Ethernet module
620 tristate "FCoE module"
624 Fibre Channel over Ethernet module
627 tristate "Cisco FNIC Driver"
628 depends on PCI && X86
631 This is support for the Cisco PCI-Express FCoE HBA.
633 To compile this driver as a module, choose M here and read
634 <file:Documentation/scsi/scsi.txt>.
635 The module will be called fnic.
638 tristate "Cisco SNIC Driver"
639 depends on PCI && SCSI
641 This is support for the Cisco PCI-Express SCSI HBA.
643 To compile this driver as a module, choose M here and read
644 <file:Documentation/scsi/scsi.txt>.
645 The module will be called snic.
647 config SCSI_SNIC_DEBUG_FS
648 bool "Cisco SNIC Driver Debugfs Support"
649 depends on SCSI_SNIC && DEBUG_FS
651 This enables to list debugging information from SNIC Driver
652 available via debugfs file system
655 tristate "DMX3191D SCSI support"
656 depends on PCI && SCSI
657 select SCSI_SPI_ATTRS
659 This is support for Domex DMX3191D SCSI Host Adapters.
661 To compile this driver as a module, choose M here: the
662 module will be called dmx3191d.
665 tristate "DTC3180/3280 SCSI support"
666 depends on ISA && SCSI
667 select SCSI_SPI_ATTRS
668 select CHECK_SIGNATURE
670 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
671 the SCSI-HOWTO, available from
672 <http://www.tldp.org/docs.html#howto>, and the file
673 <file:Documentation/scsi/dtc3x80.txt>.
675 To compile this driver as a module, choose M here: the
676 module will be called dtc.
679 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
680 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
682 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
683 ISA and all EISA I/O addresses are probed looking for the "EATA"
684 signature. The addresses of all the PCI SCSI controllers reported
685 by the PCI subsystem are probed as well.
687 You want to read the start of <file:drivers/scsi/eata.c> and the
688 SCSI-HOWTO, available from
689 <http://www.tldp.org/docs.html#howto>.
691 To compile this driver as a module, choose M here: the
692 module will be called eata.
694 config SCSI_EATA_TAGGED_QUEUE
695 bool "enable tagged command queueing"
698 This is a feature of SCSI-2 which improves performance: the host
699 adapter can send several SCSI commands to a device's queue even if
700 previous commands haven't finished yet.
701 This is equivalent to the "eata=tc:y" boot option.
703 config SCSI_EATA_LINKED_COMMANDS
704 bool "enable elevator sorting"
707 This option enables elevator sorting for all probed SCSI disks and
708 CD-ROMs. It definitely reduces the average seek distance when doing
709 random seeks, but this does not necessarily result in a noticeable
710 performance improvement: your mileage may vary...
711 This is equivalent to the "eata=lc:y" boot option.
713 config SCSI_EATA_MAX_TAGS
714 int "maximum number of queued commands"
718 This specifies how many SCSI commands can be maximally queued for
719 each probed SCSI device. You should reduce the default value of 16
720 only if you have disks with buggy or limited tagged command support.
721 Minimum is 2 and maximum is 62. This value is also the window size
722 used by the elevator sorting option above. The effective value used
723 by the driver for each probed SCSI device is reported at boot time.
724 This is equivalent to the "eata=mq:8" boot option.
727 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
728 depends on (ISA || EISA || PCI) && SCSI && BROKEN
730 This driver supports all EATA-PIO protocol compliant SCSI Host
731 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
732 host adapters could also use this driver but are discouraged from
733 doing so, since this driver only supports hard disks and lacks
734 numerous features. You might want to have a look at the SCSI-HOWTO,
735 available from <http://www.tldp.org/docs.html#howto>.
737 To compile this driver as a module, choose M here: the
738 module will be called eata_pio.
740 config SCSI_FUTURE_DOMAIN
741 tristate "Future Domain 16xx SCSI/AHA-2920A support"
742 depends on (ISA || PCI) && SCSI
743 select CHECK_SIGNATURE
745 This is support for Future Domain's 16-bit SCSI host adapters
746 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
747 other adapters based on the Future Domain chipsets (Quantum
748 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
749 It is explained in section 3.7 of the SCSI-HOWTO, available from
750 <http://www.tldp.org/docs.html#howto>.
752 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
753 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
754 controller support"). This Future Domain driver works with the older
755 Adaptec AHA-2920A boards with a Future Domain chip on them.
757 To compile this driver as a module, choose M here: the
758 module will be called fdomain.
761 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
762 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
764 Formerly called GDT SCSI Disk Array Controller Support.
766 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
767 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
768 in the kernel source in <file:drivers/scsi/gdth.c> and
769 <file:drivers/scsi/gdth.h>.
771 To compile this driver as a module, choose M here: the
772 module will be called gdth.
775 tristate "Intel(R) C600 Series Chipset SAS Controller"
776 depends on PCI && SCSI
778 select SCSI_SAS_LIBSAS
780 This driver supports the 6Gb/s SAS capabilities of the storage
781 control unit found in the Intel(R) C600 series chipset.
783 config SCSI_GENERIC_NCR5380
784 tristate "Generic NCR5380/53c400 SCSI PIO support"
785 depends on ISA && SCSI
786 select SCSI_SPI_ATTRS
788 This is a driver for the old NCR 53c80 series of SCSI controllers
789 on boards using PIO. Most boards such as the Trantor T130 fit this
790 category, along with a large number of ISA 8bit controllers shipped
791 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
792 you should select the specific driver for that card rather than
793 generic 5380 support.
795 It is explained in section 3.8 of the SCSI-HOWTO, available from
796 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
797 of the box, you may have to change some settings in
798 <file:drivers/scsi/g_NCR5380.h>.
800 To compile this driver as a module, choose M here: the
801 module will be called g_NCR5380.
803 config SCSI_GENERIC_NCR5380_MMIO
804 tristate "Generic NCR5380/53c400 SCSI MMIO support"
805 depends on ISA && SCSI
806 select SCSI_SPI_ATTRS
808 This is a driver for the old NCR 53c80 series of SCSI controllers
809 on boards using memory mapped I/O.
810 It is explained in section 3.8 of the SCSI-HOWTO, available from
811 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
812 of the box, you may have to change some settings in
813 <file:drivers/scsi/g_NCR5380.h>.
815 To compile this driver as a module, choose M here: the
816 module will be called g_NCR5380_mmio.
818 config SCSI_GENERIC_NCR53C400
819 bool "Enable NCR53c400 extensions"
820 depends on SCSI_GENERIC_NCR5380
822 This enables certain optimizations for the NCR53c400 SCSI cards.
823 You might as well try it out. Note that this driver will only probe
824 for the Trantor T130B in its default configuration; you might have
825 to pass a command line option to the kernel at boot time if it does
826 not detect your card. See the file
827 <file:Documentation/scsi/g_NCR5380.txt> for details.
830 tristate "IBM ServeRAID support"
831 depends on PCI && SCSI
833 This is support for the IBM ServeRAID hardware RAID controllers.
834 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
835 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
836 for more information. If this driver does not work correctly
837 without modification please contact the author by email at
838 <ipslinux@adaptec.com>.
840 To compile this driver as a module, choose M here: the
841 module will be called ips.
844 tristate "IBM Virtual SCSI support"
845 depends on PPC_PSERIES
846 select SCSI_SRP_ATTRS
848 This is the IBM POWER Virtual SCSI Client
850 To compile this driver as a module, choose M here: the
851 module will be called ibmvscsi.
854 tristate "IBM Virtual FC support"
855 depends on PPC_PSERIES && SCSI
856 depends on SCSI_FC_ATTRS
858 This is the IBM POWER Virtual FC Client
860 To compile this driver as a module, choose M here: the
861 module will be called ibmvfc.
863 config SCSI_IBMVFC_TRACE
864 bool "enable driver internal trace"
865 depends on SCSI_IBMVFC
868 If you say Y here, the driver will trace all commands issued
869 to the adapter. Performance impact is minimal. Trace can be
870 dumped using /sys/class/scsi_host/hostXX/trace.
873 tristate "Initio 9100U(W) support"
874 depends on PCI && SCSI
876 This is support for the Initio 91XXU(W) SCSI host adapter. Please
877 read the SCSI-HOWTO, available from
878 <http://www.tldp.org/docs.html#howto>.
880 To compile this driver as a module, choose M here: the
881 module will be called initio.
884 tristate "Initio INI-A100U2W support"
885 depends on PCI && SCSI
887 This is support for the Initio INI-A100U2W SCSI host adapter.
888 Please read the SCSI-HOWTO, available from
889 <http://www.tldp.org/docs.html#howto>.
891 To compile this driver as a module, choose M here: the
892 module will be called a100u2w.
895 tristate "IOMEGA parallel port (ppa - older drives)"
896 depends on SCSI && PARPORT_PC
898 This driver supports older versions of IOMEGA's parallel port ZIP
899 drive (a 100 MB removable media device).
901 Note that you can say N here if you have the SCSI version of the ZIP
902 drive: it will be supported automatically if you said Y to the
903 generic "SCSI disk support", above.
905 If you have the ZIP Plus drive or a more recent parallel port ZIP
906 drive (if the supplied cable with the drive is labeled "AutoDetect")
907 then you should say N here and Y to "IOMEGA parallel port (imm -
908 newer drives)", below.
910 For more information about this driver and how to use it you should
911 read the file <file:Documentation/scsi/ppa.txt>. You should also read
912 the SCSI-HOWTO, which is available from
913 <http://www.tldp.org/docs.html#howto>. If you use this driver,
914 you will still be able to use the parallel port for other tasks,
915 such as a printer; it is safe to compile both drivers into the
918 To compile this driver as a module, choose M here: the
919 module will be called ppa.
922 tristate "IOMEGA parallel port (imm - newer drives)"
923 depends on SCSI && PARPORT_PC
925 This driver supports newer versions of IOMEGA's parallel port ZIP
926 drive (a 100 MB removable media device).
928 Note that you can say N here if you have the SCSI version of the ZIP
929 drive: it will be supported automatically if you said Y to the
930 generic "SCSI disk support", above.
932 If you have the ZIP Plus drive or a more recent parallel port ZIP
933 drive (if the supplied cable with the drive is labeled "AutoDetect")
934 then you should say Y here; if you have an older ZIP drive, say N
935 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
937 For more information about this driver and how to use it you should
938 read the file <file:Documentation/scsi/ppa.txt>. You should also read
939 the SCSI-HOWTO, which is available from
940 <http://www.tldp.org/docs.html#howto>. If you use this driver,
941 you will still be able to use the parallel port for other tasks,
942 such as a printer; it is safe to compile both drivers into the
945 To compile this driver as a module, choose M here: the
946 module will be called imm.
948 config SCSI_IZIP_EPP16
949 bool "ppa/imm option - Use slow (but safe) EPP-16"
950 depends on SCSI_PPA || SCSI_IMM
952 EPP (Enhanced Parallel Port) is a standard for parallel ports which
953 allows them to act as expansion buses that can handle up to 64
956 Some parallel port chipsets are slower than their motherboard, and
957 so we have to control the state of the chipset's FIFO queue every
958 now and then to avoid data loss. This will be done if you say Y
961 Generally, saying Y is the safe option and slows things down a bit.
963 config SCSI_IZIP_SLOW_CTR
964 bool "ppa/imm option - Assume slow parport control register"
965 depends on SCSI_PPA || SCSI_IMM
967 Some parallel ports are known to have excessive delays between
968 changing the parallel port control register and good data being
969 available on the parallel port data/status register. This option
970 forces a small delay (1.0 usec to be exact) after changing the
971 control register to let things settle out. Enabling this option may
972 result in a big drop in performance but some very old parallel ports
973 (found in 386 vintage machines) will not work properly.
975 Generally, saying N is fine.
977 config SCSI_NCR53C406A
978 tristate "NCR53c406a SCSI support"
979 depends on ISA && SCSI
981 This is support for the NCR53c406a SCSI host adapter. For user
982 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
983 in the kernel source. Also read the SCSI-HOWTO, available from
984 <http://www.tldp.org/docs.html#howto>.
986 To compile this driver as a module, choose M here: the
987 module will be called NCR53c406.
990 tristate "NCR Dual 700 MCA SCSI support"
991 depends on MCA && SCSI
992 select SCSI_SPI_ATTRS
994 This is a driver for the MicroChannel Dual 700 card produced by
995 NCR and commonly used in 345x/35xx/4100 class machines. It always
996 tries to negotiate sync and uses tag command queueing.
998 Unless you have an NCR manufactured machine, the chances are that
999 you do not have this SCSI card, so say N.
1002 tristate "HP Lasi SCSI support for 53c700/710"
1003 depends on GSC && SCSI
1004 select SCSI_SPI_ATTRS
1006 This is a driver for the SCSI controller in the Lasi chip found in
1007 many PA-RISC workstations & servers. If you do not know whether you
1008 have a Lasi chip, it is safe to say "Y" here.
1010 config SCSI_SNI_53C710
1011 tristate "SNI RM SCSI support for 53c710"
1012 depends on SNI_RM && SCSI
1013 select SCSI_SPI_ATTRS
1014 select 53C700_LE_ON_BE
1016 This is a driver for the onboard SCSI controller found in older
1017 SNI RM workstations & servers.
1019 config 53C700_LE_ON_BE
1021 depends on SCSI_LASI700
1025 tristate "Promise SuperTrak EX Series support"
1026 depends on PCI && SCSI
1028 This driver supports Promise SuperTrak EX series storage controllers.
1030 Promise provides Linux RAID configuration utility for these
1031 controllers. Please visit <http://www.promise.com> to download.
1033 To compile this driver as a module, choose M here: the
1034 module will be called stex.
1036 config 53C700_BE_BUS
1038 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1041 config SCSI_SYM53C8XX_2
1042 tristate "SYM53C8XX Version 2 SCSI support"
1043 depends on PCI && SCSI
1044 select SCSI_SPI_ATTRS
1046 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1047 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1048 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1049 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1050 controllers; you need to use the Fusion MPT driver for that.
1052 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1055 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1056 int "DMA addressing mode"
1057 depends on SCSI_SYM53C8XX_2
1060 This option only applies to PCI-SCSI chips that are PCI DAC
1061 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1063 When set to 0, the driver will program the chip to only perform
1064 32-bit DMA. When set to 1, the chip will be able to perform DMA
1065 to addresses up to 1TB. When set to 2, the driver supports the
1066 full 64-bit DMA address range, but can only address 16 segments
1067 of 4 GB each. This limits the total addressable range to 64 GB.
1069 Most machines with less than 4GB of memory should use a setting
1070 of 0 for best performance. If your machine has 4GB of memory
1071 or more, you should set this option to 1 (the default).
1073 The still experimental value 2 (64 bit DMA addressing with 16
1074 x 4GB segments limitation) can be used on systems that require
1075 PCI address bits past bit 39 to be set for the addressing of
1076 memory using PCI DAC cycles.
1078 config SCSI_SYM53C8XX_DEFAULT_TAGS
1079 int "Default tagged command queue depth"
1080 depends on SCSI_SYM53C8XX_2
1083 This is the default value of the command queue depth the
1084 driver will announce to the generic SCSI layer for devices
1085 that support tagged command queueing. This value can be changed
1086 from the boot command line. This is a soft limit that cannot
1087 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1089 config SCSI_SYM53C8XX_MAX_TAGS
1090 int "Maximum number of queued commands"
1091 depends on SCSI_SYM53C8XX_2
1094 This option allows you to specify the maximum number of commands
1095 that can be queued to any device, when tagged command queuing is
1096 possible. The driver supports up to 256 queued commands per device.
1097 This value is used as a compiled-in hard limit.
1099 config SCSI_SYM53C8XX_MMIO
1100 bool "Use memory mapped IO"
1101 depends on SCSI_SYM53C8XX_2
1104 Memory mapped IO is faster than Port IO. Most people should
1105 answer Y here, but some machines may have problems. If you have
1106 to answer N here, please report the problem to the maintainer.
1109 tristate "IBM Power Linux RAID adapter support"
1110 depends on PCI && SCSI && ATA
1113 This driver supports the IBM Power Linux family RAID adapters.
1114 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1115 as IBM iSeries 5702, 5703, 5709, and 570A.
1117 config SCSI_IPR_TRACE
1118 bool "enable driver internal trace"
1122 If you say Y here, the driver will trace all commands issued
1123 to the adapter. Performance impact is minimal. Trace can be
1124 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1126 config SCSI_IPR_DUMP
1127 bool "enable adapter dump support"
1131 If you say Y here, the driver will support adapter crash dump.
1132 If you enable this support, the iprdump daemon can be used
1133 to capture adapter failure analysis information.
1136 tristate "Zalon SCSI support"
1137 depends on GSC && SCSI
1138 select SCSI_SPI_ATTRS
1140 The Zalon is a GSC/HSC bus interface chip that sits between the
1141 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1142 C110, J200, J210 and some D, K & R-class machines. It's also
1143 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1144 Say Y here if you have one of these machines or cards.
1146 config SCSI_NCR_Q720
1147 tristate "NCR Quad 720 MCA SCSI support"
1148 depends on MCA && SCSI
1149 select SCSI_SPI_ATTRS
1151 This is a driver for the MicroChannel Quad 720 card produced by
1152 NCR and commonly used in 345x/35xx/4100 class machines. It always
1153 tries to negotiate sync and uses tag command queueing.
1155 Unless you have an NCR manufactured machine, the chances are that
1156 you do not have this SCSI card, so say N.
1158 config SCSI_NCR53C8XX_DEFAULT_TAGS
1159 int "default tagged command queue depth"
1160 depends on SCSI_ZALON || SCSI_NCR_Q720
1163 "Tagged command queuing" is a feature of SCSI-2 which improves
1164 performance: the host adapter can send several SCSI commands to a
1165 device's queue even if previous commands haven't finished yet.
1166 Because the device is intelligent, it can optimize its operations
1167 (like head positioning) based on its own request queue. Some SCSI
1168 devices don't implement this properly; if you want to disable this
1169 feature, enter 0 or 1 here (it doesn't matter which).
1171 The default value is 8 and should be supported by most hard disks.
1172 This value can be overridden from the boot command line using the
1173 'tags' option as follows (example):
1174 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1175 4, set queue depth to 16 for target 2 and target 3 on controller 0
1176 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1178 The normal answer therefore is to go with the default 8 and to use
1179 a boot command line option for devices that need to use a different
1180 command queue depth.
1182 There is no safe option other than using good SCSI devices.
1184 config SCSI_NCR53C8XX_MAX_TAGS
1185 int "maximum number of queued commands"
1186 depends on SCSI_ZALON || SCSI_NCR_Q720
1189 This option allows you to specify the maximum number of commands
1190 that can be queued to any device, when tagged command queuing is
1191 possible. The default value is 32. Minimum is 2, maximum is 64.
1192 Modern hard disks are able to support 64 tags and even more, but
1193 do not seem to be faster when more than 32 tags are being used.
1195 So, the normal answer here is to go with the default value 32 unless
1196 you are using very large hard disks with large cache (>= 1 MB) that
1197 are able to take advantage of more than 32 tagged commands.
1199 There is no safe option and the default answer is recommended.
1201 config SCSI_NCR53C8XX_SYNC
1202 int "synchronous transfers frequency in MHz"
1203 depends on SCSI_ZALON || SCSI_NCR_Q720
1206 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1207 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1208 are respectively the maximum data transfer rates in mega-transfers
1209 per second for each class. For example, a FAST-20 Wide 16 device is
1210 able to transfer data at 20 million 16 bit packets per second for a
1211 total rate of 40 MB/s.
1213 You may specify 0 if you want to only use asynchronous data
1214 transfers. This is the safest and slowest option. Otherwise, specify
1215 a value between 5 and 80, depending on the capability of your SCSI
1216 controller. The higher the number, the faster the data transfer.
1217 Note that 80 should normally be ok since the driver decreases the
1218 value automatically according to the controller's capabilities.
1220 Your answer to this question is ignored for controllers with NVRAM,
1221 since the driver will get this information from the user set-up. It
1222 also can be overridden using a boot setup option, as follows
1223 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1224 for FAST-20 synchronous data transfer (20 mega-transfers per
1227 The normal answer therefore is not to go with the default but to
1228 select the maximum value 80 allowing the driver to use the maximum
1229 value supported by each controller. If this causes problems with
1230 your SCSI devices, you should come back and decrease the value.
1232 There is no safe option other than using good cabling, right
1233 terminations and SCSI conformant devices.
1235 config SCSI_NCR53C8XX_NO_DISCONNECT
1236 bool "not allow targets to disconnect"
1237 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1239 This option is only provided for safety if you suspect some SCSI
1240 device of yours to not support properly the target-disconnect
1241 feature. In that case, you would say Y here. In general however, to
1242 not allow targets to disconnect is not reasonable if there is more
1243 than 1 device on a SCSI bus. The normal answer therefore is N.
1246 tristate "PAS16 SCSI support"
1247 depends on ISA && SCSI
1248 select SCSI_SPI_ATTRS
1250 This is support for a SCSI host adapter. It is explained in section
1251 3.10 of the SCSI-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1253 of the box, you may have to change some settings in
1254 <file:drivers/scsi/pas16.h>.
1256 To compile this driver as a module, choose M here: the
1257 module will be called pas16.
1259 config SCSI_QLOGIC_FAS
1260 tristate "Qlogic FAS SCSI support"
1261 depends on ISA && SCSI
1263 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1264 FastSCSI! cards as well as any other card based on the FASXX chip
1265 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1267 This driver does NOT support the PCI versions of these cards. The
1268 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1269 SCSI support"), below.
1271 Information about this driver is contained in
1272 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1273 SCSI-HOWTO, available from
1274 <http://www.tldp.org/docs.html#howto>.
1276 To compile this driver as a module, choose M here: the
1277 module will be called qlogicfas.
1279 config SCSI_QLOGIC_1280
1280 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1281 depends on PCI && SCSI
1283 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1285 To compile this driver as a module, choose M here: the
1286 module will be called qla1280.
1288 config SCSI_QLOGICPTI
1289 tristate "PTI Qlogic, ISP Driver"
1290 depends on SBUS && SCSI
1292 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1293 controllers are known under Solaris as qpti and in the openprom as
1294 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1295 driven by a different driver.
1297 To compile this driver as a module, choose M here: the
1298 module will be called qlogicpti.
1300 source "drivers/scsi/qla2xxx/Kconfig"
1301 source "drivers/scsi/qla4xxx/Kconfig"
1304 tristate "Emulex LightPulse Fibre Channel Support"
1305 depends on PCI && SCSI
1306 depends on SCSI_FC_ATTRS
1309 This lpfc driver supports the Emulex LightPulse
1310 Family of Fibre Channel PCI host adapters.
1312 config SCSI_LPFC_DEBUG_FS
1313 bool "Emulex LightPulse Fibre Channel debugfs Support"
1314 depends on SCSI_LPFC && DEBUG_FS
1316 This makes debugging information from the lpfc driver
1317 available via the debugfs filesystem.
1320 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1321 depends on (EISA || MCA) && SCSI
1322 select SCSI_SPI_ATTRS
1324 This driver is for NCR53c710 based SCSI host adapters.
1326 It currently supports Compaq EISA cards and NCR MCA cards
1328 config SCSI_SYM53C416
1329 tristate "Symbios 53c416 SCSI support"
1330 depends on ISA && SCSI
1332 This is support for the sym53c416 SCSI host adapter, the SCSI
1333 adapter that comes with some HP scanners. This driver requires that
1334 the sym53c416 is configured first using some sort of PnP
1335 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1336 are using isapnp then you need to compile this driver as a module
1337 and then load it using insmod after isapnp has run. The parameters
1338 of the configured card(s) should be passed to the driver. The format
1341 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1343 To compile this driver as a module, choose M here: the
1344 module will be called sym53c416.
1347 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1348 depends on PCI && SCSI
1350 This driver supports PCI SCSI host adapters based on the ASIC
1351 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1353 This driver works, but is still in experimental status. So better
1354 have a bootable disk and a backup in case of emergency.
1356 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1358 To compile this driver as a module, choose M here: the
1359 module will be called dc395x.
1361 config SCSI_AM53C974
1362 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1363 depends on PCI && SCSI
1364 select SCSI_SPI_ATTRS
1366 This driver supports PCI SCSI host adapters based on the Am53C974A
1367 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1368 PCscsi/PCnet (Am53/79C974) solutions.
1369 This is a new implementation base on the generic esp_scsi driver.
1371 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1373 Note that this driver does NOT support Tekram DC390W/U/F, which are
1374 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1376 To compile this driver as a module, choose M here: the
1377 module will be called am53c974.
1380 tristate "Trantor T128/T128F/T228 SCSI support"
1381 depends on ISA && SCSI
1382 select SCSI_SPI_ATTRS
1383 select CHECK_SIGNATURE
1385 This is support for a SCSI host adapter. It is explained in section
1386 3.11 of the SCSI-HOWTO, available from
1387 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1388 of the box, you may have to change some settings in
1389 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1390 Adaptec, and some former Trantor products are being sold under the
1393 To compile this driver as a module, choose M here: the
1394 module will be called t128.
1397 tristate "UltraStor 14F/34F support"
1398 depends on ISA && SCSI && ISA_DMA_API
1400 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1401 The source at <file:drivers/scsi/u14-34f.c> contains some
1402 information about this hardware. If the driver doesn't work out of
1403 the box, you may have to change some settings in
1404 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1405 <http://www.tldp.org/docs.html#howto>. Note that there is also
1406 another driver for the same hardware: "UltraStor SCSI support",
1407 below. You should say Y to both only if you want 24F support as
1410 To compile this driver as a module, choose M here: the
1411 module will be called u14-34f.
1413 config SCSI_U14_34F_TAGGED_QUEUE
1414 bool "enable tagged command queueing"
1415 depends on SCSI_U14_34F
1417 This is a feature of SCSI-2 which improves performance: the host
1418 adapter can send several SCSI commands to a device's queue even if
1419 previous commands haven't finished yet.
1420 This is equivalent to the "u14-34f=tc:y" boot option.
1422 config SCSI_U14_34F_LINKED_COMMANDS
1423 bool "enable elevator sorting"
1424 depends on SCSI_U14_34F
1426 This option enables elevator sorting for all probed SCSI disks and
1427 CD-ROMs. It definitely reduces the average seek distance when doing
1428 random seeks, but this does not necessarily result in a noticeable
1429 performance improvement: your mileage may vary...
1430 This is equivalent to the "u14-34f=lc:y" boot option.
1432 config SCSI_U14_34F_MAX_TAGS
1433 int "maximum number of queued commands"
1434 depends on SCSI_U14_34F
1437 This specifies how many SCSI commands can be maximally queued for
1438 each probed SCSI device. You should reduce the default value of 8
1439 only if you have disks with buggy or limited tagged command support.
1440 Minimum is 2 and maximum is 14. This value is also the window size
1441 used by the elevator sorting option above. The effective value used
1442 by the driver for each probed SCSI device is reported at boot time.
1443 This is equivalent to the "u14-34f=mq:8" boot option.
1445 config SCSI_ULTRASTOR
1446 tristate "UltraStor SCSI support"
1447 depends on X86 && ISA && SCSI
1449 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1450 adapter family. This driver is explained in section 3.12 of the
1451 SCSI-HOWTO, available from
1452 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1453 of the box, you may have to change some settings in
1454 <file:drivers/scsi/ultrastor.h>.
1456 Note that there is also another driver for the same hardware:
1457 "UltraStor 14F/34F support", above.
1459 To compile this driver as a module, choose M here: the
1460 module will be called ultrastor.
1463 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1464 depends on PCI && SCSI && !64BIT
1466 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1467 SCSI host adapter. Please read the SCSI-HOWTO, available from
1468 <http://www.tldp.org/docs.html#howto>.
1470 To compile this driver as a module, choose M here: the
1471 module will be called nsp32.
1474 tristate "Western Digital WD7193/7197/7296 support"
1475 depends on PCI && SCSI
1478 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1479 SCSI controllers (based on WD33C296A chip).
1482 tristate "SCSI debugging host and device simulator"
1486 This pseudo driver simulates one or more hosts (SCSI initiators),
1487 each with one or more targets, each with one or more logical units.
1488 Defaults to one of each, creating a small RAM disk device. Many
1489 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1490 directory can be tweaked at run time.
1491 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1492 Mainly used for testing and best as a module. If unsure, say N.
1495 tristate "MESH (Power Mac internal SCSI) support"
1496 depends on PPC32 && PPC_PMAC && SCSI
1498 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1499 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1500 other Power Macintoshes do). Say Y to include support for this SCSI
1503 To compile this driver as a module, choose M here: the
1504 module will be called mesh.
1506 config SCSI_MESH_SYNC_RATE
1507 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1508 depends on SCSI_MESH
1511 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1512 drives a bus which is entirely internal to the machine (such as the
1513 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1514 operation at up to 10 MB/s. On machines where the SCSI bus
1515 controlled by the MESH can have external devices connected, it is
1516 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1517 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1518 to disable synchronous operation.
1520 config SCSI_MESH_RESET_DELAY_MS
1521 int "initial bus reset delay (ms) (0 = no reset)"
1522 depends on SCSI_MESH
1525 config SCSI_MAC53C94
1526 tristate "53C94 (Power Mac external SCSI) support"
1527 depends on PPC32 && PPC_PMAC && SCSI
1529 On Power Macintoshes (and clones) with two SCSI buses, the external
1530 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1531 machines which only have one SCSI bus, such as the 7200, also use
1532 the 53C94. Say Y to include support for the 53C94.
1534 To compile this driver as a module, choose M here: the
1535 module will be called mac53c94.
1537 source "drivers/scsi/arm/Kconfig"
1540 bool "MIPS JAZZ FAS216 SCSI support"
1541 depends on MACH_JAZZ && SCSI
1542 select SCSI_SPI_ATTRS
1544 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1545 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1549 tristate "A3000 WD33C93A support"
1550 depends on AMIGA && SCSI
1552 If you have an Amiga 3000 and have SCSI devices connected to the
1553 built-in SCSI controller, say Y. Otherwise, say N.
1555 To compile this driver as a module, choose M here: the
1556 module will be called a3000.
1559 tristate "A2091/A590 WD33C93A support"
1560 depends on ZORRO && SCSI
1562 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1565 To compile this driver as a module, choose M here: the
1566 module will be called a2091.
1569 tristate "GVP Series II WD33C93A support"
1570 depends on ZORRO && SCSI
1572 If you have a Great Valley Products Series II SCSI controller,
1573 answer Y. Also say Y if you have a later model of GVP SCSI
1574 controller (such as the GVP A4008 or a Combo board). Otherwise,
1575 answer N. This driver does NOT work for the T-Rex series of
1576 accelerators from TekMagic and GVP-M.
1578 To compile this driver as a module, choose M here: the
1579 module will be called gvp11.
1582 tristate "A4000T NCR53c710 SCSI support"
1583 depends on AMIGA && SCSI
1584 select SCSI_SPI_ATTRS
1586 If you have an Amiga 4000T and have SCSI devices connected to the
1587 built-in SCSI controller, say Y. Otherwise, say N.
1589 To compile this driver as a module, choose M here: the
1590 module will be called a4000t.
1592 config SCSI_ZORRO7XX
1593 tristate "Zorro NCR53c710 SCSI support"
1594 depends on ZORRO && SCSI
1595 select SCSI_SPI_ATTRS
1597 Support for various NCR53c710-based SCSI controllers on Zorro
1598 expansion boards for the Amiga.
1600 - the Amiga 4091 Zorro III SCSI-2 controller,
1601 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1603 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1604 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1605 accelerator card for the Amiga 1200,
1606 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1609 tristate "Atari native SCSI support"
1610 depends on ATARI && SCSI
1611 select SCSI_SPI_ATTRS
1614 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1615 Falcon, ...) say Y to get it supported. Of course also, if you have
1616 a compatible SCSI controller (e.g. for Medusa).
1618 To compile this driver as a module, choose M here: the
1619 module will be called atari_scsi.
1621 This driver supports both styles of NCR integration into the
1622 system: the TT style (separate DMA), and the Falcon style (via
1623 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1624 in the Hades (without DMA).
1626 config ATARI_SCSI_TOSHIBA_DELAY
1627 bool "Long delays for Toshiba CD-ROMs"
1628 depends on ATARI_SCSI
1630 This option increases the delay after a SCSI arbitration to
1631 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1632 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1633 would impact performance a bit, so say N.
1635 config ATARI_SCSI_RESET_BOOT
1636 bool "Reset SCSI-devices at boottime"
1637 depends on ATARI_SCSI
1639 Reset the devices on your Atari whenever it boots. This makes the
1640 boot process fractionally longer but may assist recovery from errors
1641 that leave the devices with SCSI operations partway completed.
1644 tristate "Macintosh NCR5380 SCSI"
1645 depends on MAC && SCSI=y
1646 select SCSI_SPI_ATTRS
1648 This is the NCR 5380 SCSI controller included on most of the 68030
1649 based Macintoshes. If you have one of these say Y and read the
1650 SCSI-HOWTO, available from
1651 <http://www.tldp.org/docs.html#howto>.
1654 tristate "Macintosh NCR53c9[46] SCSI"
1655 depends on MAC && SCSI
1656 select SCSI_SPI_ATTRS
1658 This is the NCR 53c9x SCSI controller found on most of the 68040
1661 To compile this driver as a module, choose M here: the module
1662 will be called mac_esp.
1665 bool "WD33C93 SCSI driver for MVME147"
1666 depends on MVME147 && SCSI=y
1667 select SCSI_SPI_ATTRS
1669 Support for the on-board SCSI controller on the Motorola MVME147
1670 single-board computer.
1673 tristate "NCR53C710 SCSI driver for MVME16x"
1674 depends on MVME16x && SCSI
1675 select SCSI_SPI_ATTRS
1677 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1678 SCSI controller chip. Almost everyone using one of these boards
1679 will want to say Y to this question.
1681 config BVME6000_SCSI
1682 tristate "NCR53C710 SCSI driver for BVME6000"
1683 depends on BVME6000 && SCSI
1684 select SCSI_SPI_ATTRS
1686 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1687 SCSI controller chip. Almost everyone using one of these boards
1688 will want to say Y to this question.
1691 tristate "Sun3 NCR5380 SCSI"
1692 depends on SUN3 && SCSI
1693 select SCSI_SPI_ATTRS
1695 This option will enable support for the OBIO (onboard io) NCR5380
1696 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1697 "Sun3" type VME scsi controllers also based on the NCR5380.
1698 General Linux information on the Sun 3 series (now discontinued)
1699 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1702 bool "Sun3x ESP SCSI"
1703 depends on SUN3X && SCSI=y
1704 select SCSI_SPI_ATTRS
1706 The ESP was an on-board SCSI controller used on Sun 3/80
1707 machines. Say Y here to compile in support for it.
1710 tristate "Sparc ESP Scsi Driver"
1711 depends on SBUS && SCSI
1712 select SCSI_SPI_ATTRS
1714 This is the driver for the Sun ESP SCSI host adapter. The ESP
1715 chipset is present in most SPARC SBUS-based computers and
1716 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1717 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1719 To compile this driver as a module, choose M here: the
1720 module will be called sun_esp.
1723 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1724 depends on S390 && QDIO && SCSI
1725 depends on SCSI_FC_ATTRS
1727 If you want to access SCSI devices attached to your IBM eServer
1728 zSeries by means of Fibre Channel interfaces say Y.
1729 For details please refer to the documentation provided by IBM at
1730 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1732 This driver is also available as a module. This module will be
1733 called zfcp. If you want to compile it as a module, say M here
1734 and read <file:Documentation/kbuild/modules.txt>.
1737 tristate "PMC SIERRA Linux MaxRAID adapter support"
1738 depends on PCI && SCSI && NET
1740 This driver supports the PMC SIERRA MaxRAID adapters.
1743 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1744 depends on PCI && SCSI
1745 select SCSI_SAS_LIBSAS
1747 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1748 based host adapters.
1751 tristate "Brocade BFA Fibre Channel Support"
1752 depends on PCI && SCSI
1753 depends on SCSI_FC_ATTRS
1755 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1757 To compile this driver as a module, choose M here. The module will
1761 tristate "virtio-scsi support"
1764 This is the virtual HBA driver for virtio. If the kernel will
1765 be used in a virtual machine, say Y or M.
1767 source "drivers/scsi/csiostor/Kconfig"
1769 endif # SCSI_LOWLEVEL
1771 source "drivers/scsi/pcmcia/Kconfig"
1773 source "drivers/scsi/device_handler/Kconfig"
1775 source "drivers/scsi/osd/Kconfig"