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.
44 tristate "SCSI target support"
45 depends on SCSI && EXPERIMENTAL
47 If you want to use SCSI target mode drivers enable this option.
48 If you choose M, the module will be called scsi_tgt.
56 bool "legacy /proc/scsi/ support"
57 depends on SCSI && PROC_FS
60 This option enables support for the various files in
61 /proc/scsi. In Linux 2.6 this has been superseded by
62 files in sysfs but many legacy applications rely on this.
66 comment "SCSI support type (disk, tape, CD-ROM)"
70 tristate "SCSI disk support"
72 select CRC_T10DIF if BLK_DEV_INTEGRITY
74 If you want to use SCSI hard disks, Fibre Channel disks,
75 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
76 USB storage or the SCSI or parallel port version of
77 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
78 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
79 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
82 To compile this driver as a module, choose M here and read
83 <file:Documentation/scsi/scsi.txt>.
84 The module will be called sd_mod.
86 Do not compile this driver as a module if your root file system
87 (the one containing the directory /) is located on a SCSI disk.
88 In this case, do not compile the driver for your SCSI host adapter
89 (below) as a module either.
92 tristate "SCSI tape support"
95 If you want to use a SCSI tape drive under Linux, say Y and read the
96 SCSI-HOWTO, available from
97 <http://www.tldp.org/docs.html#howto>, and
98 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
101 To compile this driver as a module, choose M here and read
102 <file:Documentation/scsi/scsi.txt>. The module will be called st.
105 tristate "SCSI OnStream SC-x0 tape support"
108 The OnStream SC-x0 SCSI tape drives cannot be driven by the
109 standard st driver, but instead need this special osst driver and
110 use the /dev/osstX char device nodes (major 206). Via usb-storage,
111 you may be able to drive the USB-x0 and DI-x0 drives as well.
112 Note that there is also a second generation of OnStream
113 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
114 tapes (QIC-157) and can be driven by the standard driver st.
115 For more information, you may have a look at the SCSI-HOWTO
116 <http://www.tldp.org/docs.html#howto> and
117 <file:Documentation/scsi/osst.txt> in the kernel source.
118 More info on the OnStream driver may be found on
119 <http://sourceforge.net/projects/osst/>
120 Please also have a look at the standard st docu, as most of it
121 applies to osst as well.
123 To compile this driver as a module, choose M here and read
124 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
127 tristate "SCSI CDROM support"
130 If you want to use a CD or DVD drive attached to your computer
131 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
132 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
134 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
136 To compile this driver as a module, choose M here and read
137 <file:Documentation/scsi/scsi.txt>.
138 The module will be called sr_mod.
140 config BLK_DEV_SR_VENDOR
141 bool "Enable vendor-specific extensions (for SCSI CDROM)"
142 depends on BLK_DEV_SR
144 This enables the usage of vendor specific SCSI commands. This is
145 required to support multisession CDs with old NEC/TOSHIBA cdrom
146 drives (and HP Writers). If you have such a drive and get the first
147 session only, try saying Y here; everybody else says N.
150 tristate "SCSI generic support"
153 If you want to use SCSI scanners, synthesizers or CD-writers or just
154 about anything having "SCSI" in its name other than hard disks,
155 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
156 directly, so you need some additional software which knows how to
157 talk to these devices using the SCSI protocol:
159 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
160 writer software look at Cdrtools
161 (<http://cdrecord.berlios.de/private/cdrecord.html>)
162 and for burning a "disk at once": CDRDAO
163 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
164 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
165 For other devices, it's possible that you'll have to write the
166 driver software yourself. Please read the file
167 <file:Documentation/scsi/scsi-generic.txt> for more information.
169 To compile this driver as a module, choose M here and read
170 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
175 tristate "SCSI media changer support"
178 This is a driver for SCSI media changers. Most common devices are
179 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
180 don't need this for those tiny 6-slot cdrom changers. Media
181 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
182 If you have such hardware and want to use it with linux, say Y
183 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
185 If you want to compile this as a module ( = code which can be
186 inserted in and removed from the running kernel whenever you want),
187 say M here and read <file:Documentation/kbuild/modules.txt> and
188 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
191 config SCSI_ENCLOSURE
192 tristate "SCSI Enclosure Support"
193 depends on SCSI && ENCLOSURE_SERVICES
195 Enclosures are devices sitting on or in SCSI backplanes that
196 manage devices. If you have a disk cage, the chances are that
197 it has an enclosure device. Selecting this option will just allow
198 certain enclosure conditions to be reported and is not required.
200 config SCSI_MULTI_LUN
201 bool "Probe all LUNs on each SCSI device"
204 Some devices support more than one LUN (Logical Unit Number) in order
205 to allow access to several media, e.g. CD jukebox, USB card reader,
206 mobile phone in mass storage mode. This option forces the kernel to
207 probe for all LUNs by default. This setting can be overriden by
208 max_luns boot/module parameter. Note that this option does not affect
209 devices conforming to SCSI-3 or higher as they can explicitely report
210 their number of LUNs. It is safe to say Y here unless you have one of
211 those rare devices which reacts in an unexpected way when probed for
214 config SCSI_CONSTANTS
215 bool "Verbose SCSI error reporting (kernel size +=12K)"
218 The error messages regarding your SCSI hardware will be easier to
219 understand if you say Y here; it will enlarge your kernel by about
220 12 KB. If in doubt, say Y.
223 bool "SCSI logging facility"
226 This turns on a logging facility that can be used to debug a number
227 of SCSI related problems.
229 If you say Y here, no logging output will appear by default, but you
230 can enable logging by saying Y to "/proc file system support" and
231 "Sysctl support" below and executing the command
233 echo <bitmask> > /proc/sys/dev/scsi/logging_level
235 where <bitmask> is a four byte value representing the logging type
236 and logging level for each type of logging selected.
238 There are a number of logging types and you can find them in the
239 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
240 are also described in that file and they determine the verbosity of
241 the logging for each logging type.
243 If you say N here, it may be harder to track down some types of SCSI
244 problems. If you say Y here your kernel will be somewhat larger, but
245 there should be no noticeable performance impact as long as you have
248 config SCSI_SCAN_ASYNC
249 bool "Asynchronous SCSI scanning"
252 The SCSI subsystem can probe for devices while the rest of the
253 system continues booting, and even probe devices on different
254 busses in parallel, leading to a significant speed-up.
256 If you have built SCSI as modules, enabling this option can
257 be a problem as the devices may not have been found by the
258 time your system expects them to have been. You can load the
259 scsi_wait_scan module to ensure that all scans have completed.
260 If you build your SCSI drivers into the kernel, then everything
261 will work fine if you say Y here.
263 You can override this choice by specifying "scsi_mod.scan=sync"
264 or async on the kernel's command line.
266 config SCSI_WAIT_SCAN
267 tristate # No prompt here, this is an invisible symbol.
271 # scsi_wait_scan is a loadable module which waits until all the async scans are
272 # complete. The idea is to use it in initrd/ initramfs scripts. You modprobe
273 # it after all the modprobes of the root SCSI drivers and it will wait until
274 # they have all finished scanning their buses before allowing the boot to
275 # proceed. (This method is not applicable if targets boot independently in
276 # parallel with the initiator, or with transports with non-deterministic target
277 # discovery schemes, or if a transport driver does not support scsi_wait_scan.)
279 # This symbol is not exposed as a prompt because little is to be gained by
280 # disabling it, whereas people who accidentally switch it off may wonder why
281 # their mkinitrd gets into trouble.
283 menu "SCSI Transports"
286 config SCSI_SPI_ATTRS
287 tristate "Parallel SCSI (SPI) Transport Attributes"
290 If you wish to export transport-specific information about
291 each attached SCSI device to sysfs, say Y. Otherwise, say N.
294 tristate "FiberChannel Transport Attributes"
298 If you wish to export transport-specific information about
299 each attached FiberChannel device to sysfs, say Y.
302 config SCSI_FC_TGT_ATTRS
303 bool "SCSI target support for FiberChannel Transport Attributes"
304 depends on SCSI_FC_ATTRS
305 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
307 If you want to use SCSI target mode drivers enable this option.
309 config SCSI_ISCSI_ATTRS
310 tristate "iSCSI Transport Attributes"
311 depends on SCSI && NET
312 select BLK_DEV_BSGLIB
314 If you wish to export transport-specific information about
315 each attached iSCSI device to sysfs, say Y.
318 config SCSI_SAS_ATTRS
319 tristate "SAS Transport Attributes"
323 If you wish to export transport-specific information about
324 each attached SAS device to sysfs, say Y.
326 source "drivers/scsi/libsas/Kconfig"
328 config SCSI_SRP_ATTRS
329 tristate "SRP Transport Attributes"
332 If you wish to export transport-specific information about
333 each attached SRP device to sysfs, say Y.
335 config SCSI_SRP_TGT_ATTRS
336 bool "SCSI target support for SRP Transport Attributes"
337 depends on SCSI_SRP_ATTRS
338 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
340 If you want to use SCSI target mode drivers enable this option.
344 menuconfig SCSI_LOWLEVEL
345 bool "SCSI low-level drivers"
349 if SCSI_LOWLEVEL && SCSI
352 tristate "iSCSI Initiator over TCP/IP"
353 depends on SCSI && INET
357 select SCSI_ISCSI_ATTRS
359 The iSCSI Driver provides a host with the ability to access storage
360 through an IP network. The driver uses the iSCSI protocol to transport
361 SCSI requests and responses over a TCP/IP network between the host
362 (the "initiator") and "targets". Architecturally, the iSCSI driver
363 combines with the host's TCP/IP stack, network drivers, and Network
364 Interface Card (NIC) to provide the same functions as a SCSI or a
365 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
367 To compile this driver as a module, choose M here: the
368 module will be called iscsi_tcp.
370 The userspace component needed to initialize the driver, documentation,
371 and sample configuration files can be found here:
373 http://open-iscsi.org
375 config ISCSI_BOOT_SYSFS
376 tristate "iSCSI Boot Sysfs Interface"
379 This option enables support for exposing iSCSI boot information
380 via sysfs to userspace. If you wish to export this information,
381 say Y. Otherwise, say N.
383 source "drivers/scsi/cxgbi/Kconfig"
384 source "drivers/scsi/bnx2i/Kconfig"
385 source "drivers/scsi/bnx2fc/Kconfig"
386 source "drivers/scsi/be2iscsi/Kconfig"
389 tristate "SGI WD93C93 SCSI Driver"
390 depends on SGI_HAS_WD93 && SCSI
392 If you have a Western Digital WD93 SCSI controller on
393 an SGI MIPS system, say Y. Otherwise, say N.
395 config BLK_DEV_3W_XXXX_RAID
396 tristate "3ware 5/6/7/8xxx ATA-RAID support"
397 depends on PCI && SCSI
399 3ware is the only hardware ATA-Raid product in Linux to date.
400 This card is 2,4, or 8 channel master mode support only.
401 SCSI support required!!!
403 <http://www.3ware.com/>
405 Please read the comments at the top of
406 <file:drivers/scsi/3w-xxxx.c>.
409 tristate "HP Smart Array SCSI driver"
410 depends on PCI && SCSI
412 This driver supports HP Smart Array Controllers (circa 2009).
413 It is a SCSI alternative to the cciss driver, which is a block
414 driver. Anyone wishing to use HP Smart Array controllers who
415 would prefer the devices be presented to linux as SCSI devices,
416 rather than as generic block devices should say Y here.
419 tristate "3ware 9xxx SATA-RAID support"
420 depends on PCI && SCSI
422 This driver supports the 9000 series 3ware SATA-RAID cards.
424 <http://www.amcc.com>
426 Please read the comments at the top of
427 <file:drivers/scsi/3w-9xxx.c>.
430 tristate "3ware 97xx SAS/SATA-RAID support"
431 depends on PCI && SCSI
433 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
437 Please read the comments at the top of
438 <file:drivers/scsi/3w-sas.c>.
440 config SCSI_7000FASST
441 tristate "7000FASST SCSI support"
442 depends on ISA && SCSI && ISA_DMA_API
443 select CHECK_SIGNATURE
445 This driver supports the Western Digital 7000 SCSI host adapter
446 family. Some information is in the source:
447 <file:drivers/scsi/wd7000.c>.
449 To compile this driver as a module, choose M here: the
450 module will be called wd7000.
453 tristate "ACARD SCSI support"
454 depends on PCI && SCSI
456 This driver supports the ACARD SCSI host adapter.
457 Support Chip <ATP870 ATP876 ATP880 ATP885>
458 To compile this driver as a module, choose M here: the
459 module will be called atp870u.
462 tristate "Adaptec AHA152X/2825 support"
463 depends on ISA && SCSI && !64BIT
464 select SCSI_SPI_ATTRS
465 select CHECK_SIGNATURE
467 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
468 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
469 must be manually specified in this case.
471 It is explained in section 3.3 of the SCSI-HOWTO, available from
472 <http://www.tldp.org/docs.html#howto>. You might also want to
473 read the file <file:Documentation/scsi/aha152x.txt>.
475 To compile this driver as a module, choose M here: the
476 module will be called aha152x.
479 tristate "Adaptec AHA1542 support"
480 depends on ISA && SCSI && ISA_DMA_API
482 This is support for a SCSI host adapter. It is explained in section
483 3.4 of the SCSI-HOWTO, available from
484 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
485 purchased by Adaptec, and some former Trantor products are being
486 sold under the Adaptec name. If it doesn't work out of the box, you
487 may have to change some settings in <file:drivers/scsi/aha1542.h>.
489 To compile this driver as a module, choose M here: the
490 module will be called aha1542.
493 tristate "Adaptec AHA1740 support"
494 depends on EISA && SCSI
496 This is support for a SCSI host adapter. It is explained in section
497 3.5 of the SCSI-HOWTO, available from
498 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
499 of the box, you may have to change some settings in
500 <file:drivers/scsi/aha1740.h>.
502 To compile this driver as a module, choose M here: the
503 module will be called aha1740.
506 tristate "Adaptec AACRAID support"
507 depends on SCSI && PCI
509 This driver supports a variety of Dell, HP, Adaptec, IBM and
510 ICP storage products. For a list of supported products, refer
511 to <file:Documentation/scsi/aacraid.txt>.
513 To compile this driver as a module, choose M here: the module
514 will be called aacraid.
517 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
519 config SCSI_AIC7XXX_OLD
520 tristate "Adaptec AIC7xxx support (old driver)"
521 depends on (ISA || EISA || PCI ) && SCSI
523 WARNING This driver is an older aic7xxx driver and is no longer
524 under active development. Adaptec, Inc. is writing a new driver to
525 take the place of this one, and it is recommended that whenever
526 possible, people should use the new Adaptec written driver instead
527 of this one. This driver will eventually be phased out entirely.
529 This is support for the various aic7xxx based Adaptec SCSI
530 controllers. These include the 274x EISA cards; 284x VLB cards;
531 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
532 motherboard based SCSI controllers from Adaptec. It does not support
533 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
534 support them. It does not support the 2920 cards from Adaptec that
535 use the Future Domain SCSI controller chip. For those cards, you
536 need the "Future Domain 16xx SCSI support" driver.
538 In general, if the controller is based on an Adaptec SCSI controller
539 chip from the aic777x series or the aic78xx series, this driver
540 should work. The only exception is the 7810 which is specifically
541 not supported (that's the RAID controller chip on the AAA-13x
544 Note that the AHA2920 SCSI host adapter is *not* supported by this
545 driver; choose "Future Domain 16xx SCSI support" instead if you have
548 Information on the configuration options for this controller can be
549 found by checking the help file for each of the available
550 configuration options. You should read
551 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
552 contacting the maintainer with any questions. The SCSI-HOWTO,
553 available from <http://www.tldp.org/docs.html#howto>, can also
556 To compile this driver as a module, choose M here: the
557 module will be called aic7xxx_old.
559 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
560 source "drivers/scsi/aic94xx/Kconfig"
561 source "drivers/scsi/mvsas/Kconfig"
564 tristate "Marvell UMI driver"
565 depends on SCSI && PCI
567 Module for Marvell Universal Message Interface(UMI) driver
569 To compile this driver as a module, choose M here: the
570 module will be called mvumi.
573 tristate "Adaptec I2O RAID support "
574 depends on SCSI && PCI && VIRT_TO_BUS
576 This driver supports all of Adaptec's I2O based RAID controllers as
577 well as the DPT SmartRaid V cards. This is an Adaptec maintained
578 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
580 To compile this driver as a module, choose M here: the
581 module will be called dpt_i2o.
584 tristate "AdvanSys SCSI support"
585 depends on SCSI && VIRT_TO_BUS
586 depends on ISA || EISA || PCI
588 This is a driver for all SCSI host adapters manufactured by
589 AdvanSys. It is documented in the kernel source in
590 <file:drivers/scsi/advansys.c>.
592 To compile this driver as a module, choose M here: the
593 module will be called advansys.
596 tristate "Always IN2000 SCSI support"
597 depends on ISA && SCSI
599 This is support for an ISA bus SCSI host adapter. You'll find more
600 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
601 out of the box, you may have to change the jumpers for IRQ or
604 To compile this driver as a module, choose M here: the
605 module will be called in2000.
608 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
609 depends on PCI && SCSI
611 This driver supports all of ARECA's SATA/SAS RAID controller cards.
612 This is an ARECA-maintained driver by Erich Chen.
613 If you have any problems, please mail to: <erich@areca.com.tw>.
614 Areca supports Linux RAID config tools.
615 Please link <http://www.areca.com.tw>
617 To compile this driver as a module, choose M here: the
618 module will be called arcmsr (modprobe arcmsr).
620 source "drivers/scsi/megaraid/Kconfig.megaraid"
621 source "drivers/scsi/mpt2sas/Kconfig"
622 source "drivers/scsi/ufs/Kconfig"
625 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
626 depends on SCSI && PCI
628 This option enables support for HighPoint RocketRAID 3xxx/4xxx
631 To compile this driver as a module, choose M here; the module
632 will be called hptiop. If unsure, say N.
635 tristate "BusLogic SCSI support"
636 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
638 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
639 Adapters. Consult the SCSI-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>, and the files
641 <file:Documentation/scsi/BusLogic.txt> and
642 <file:Documentation/scsi/FlashPoint.txt> for more information.
643 Note that support for FlashPoint is only available for 32-bit
646 To compile this driver as a module, choose M here: the
647 module will be called BusLogic.
649 config SCSI_FLASHPOINT
650 bool "FlashPoint support"
651 depends on SCSI_BUSLOGIC && PCI && X86_32
653 This option allows you to add FlashPoint support to the
654 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
655 substantial, so users of MultiMaster Host Adapters may not
659 tristate "VMware PVSCSI driver support"
660 depends on PCI && SCSI && X86
662 This driver supports VMware's para virtualized SCSI HBA.
663 To compile this driver as a module, choose M here: the
664 module will be called vmw_pvscsi.
667 tristate "LibFC module"
671 Fibre Channel library module
674 tristate "LibFCoE module"
677 Library for Fibre Channel over Ethernet module
680 tristate "FCoE module"
684 Fibre Channel over Ethernet module
687 tristate "Cisco FNIC Driver"
688 depends on PCI && X86
691 This is support for the Cisco PCI-Express FCoE HBA.
693 To compile this driver as a module, choose M here and read
694 <file:Documentation/scsi/scsi.txt>.
695 The module will be called fnic.
698 tristate "DMX3191D SCSI support"
699 depends on PCI && SCSI
700 select SCSI_SPI_ATTRS
702 This is support for Domex DMX3191D SCSI Host Adapters.
704 To compile this driver as a module, choose M here: the
705 module will be called dmx3191d.
708 tristate "DTC3180/3280 SCSI support"
709 depends on ISA && SCSI
710 select SCSI_SPI_ATTRS
711 select CHECK_SIGNATURE
713 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
714 the SCSI-HOWTO, available from
715 <http://www.tldp.org/docs.html#howto>, and the file
716 <file:Documentation/scsi/dtc3x80.txt>.
718 To compile this driver as a module, choose M here: the
719 module will be called dtc.
722 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
723 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
725 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
726 ISA and all EISA I/O addresses are probed looking for the "EATA"
727 signature. The addresses of all the PCI SCSI controllers reported
728 by the PCI subsystem are probed as well.
730 You want to read the start of <file:drivers/scsi/eata.c> and the
731 SCSI-HOWTO, available from
732 <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.
737 config SCSI_EATA_TAGGED_QUEUE
738 bool "enable tagged command queueing"
741 This is a feature of SCSI-2 which improves performance: the host
742 adapter can send several SCSI commands to a device's queue even if
743 previous commands haven't finished yet.
744 This is equivalent to the "eata=tc:y" boot option.
746 config SCSI_EATA_LINKED_COMMANDS
747 bool "enable elevator sorting"
750 This option enables elevator sorting for all probed SCSI disks and
751 CD-ROMs. It definitely reduces the average seek distance when doing
752 random seeks, but this does not necessarily result in a noticeable
753 performance improvement: your mileage may vary...
754 This is equivalent to the "eata=lc:y" boot option.
756 config SCSI_EATA_MAX_TAGS
757 int "maximum number of queued commands"
761 This specifies how many SCSI commands can be maximally queued for
762 each probed SCSI device. You should reduce the default value of 16
763 only if you have disks with buggy or limited tagged command support.
764 Minimum is 2 and maximum is 62. This value is also the window size
765 used by the elevator sorting option above. The effective value used
766 by the driver for each probed SCSI device is reported at boot time.
767 This is equivalent to the "eata=mq:8" boot option.
770 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
771 depends on (ISA || EISA || PCI) && SCSI && BROKEN
773 This driver supports all EATA-PIO protocol compliant SCSI Host
774 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
775 host adapters could also use this driver but are discouraged from
776 doing so, since this driver only supports hard disks and lacks
777 numerous features. You might want to have a look at the SCSI-HOWTO,
778 available from <http://www.tldp.org/docs.html#howto>.
780 To compile this driver as a module, choose M here: the
781 module will be called eata_pio.
783 config SCSI_FUTURE_DOMAIN
784 tristate "Future Domain 16xx SCSI/AHA-2920A support"
785 depends on (ISA || PCI) && SCSI
786 select CHECK_SIGNATURE
788 This is support for Future Domain's 16-bit SCSI host adapters
789 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
790 other adapters based on the Future Domain chipsets (Quantum
791 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
792 It is explained in section 3.7 of the SCSI-HOWTO, available from
793 <http://www.tldp.org/docs.html#howto>.
795 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
796 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
797 controller support"). This Future Domain driver works with the older
798 Adaptec AHA-2920A boards with a Future Domain chip on them.
800 To compile this driver as a module, choose M here: the
801 module will be called fdomain.
804 tristate "Future Domain MCS-600/700 SCSI support"
805 depends on MCA_LEGACY && SCSI
807 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
808 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
809 is identical to the MCS 700 and hence also supported by this driver.
810 This driver also supports the Reply SB16/SCSI card (the SCSI part).
811 It supports multiple adapters in the same system.
813 To compile this driver as a module, choose M here: the
814 module will be called fd_mcs.
817 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
818 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
820 Formerly called GDT SCSI Disk Array Controller Support.
822 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
823 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
824 in the kernel source in <file:drivers/scsi/gdth.c> and
825 <file:drivers/scsi/gdth.h>.
827 To compile this driver as a module, choose M here: the
828 module will be called gdth.
831 tristate "Intel(R) C600 Series Chipset SAS Controller"
832 depends on PCI && SCSI
834 select SCSI_SAS_LIBSAS
836 This driver supports the 6Gb/s SAS capabilities of the storage
837 control unit found in the Intel(R) C600 series chipset.
839 config SCSI_GENERIC_NCR5380
840 tristate "Generic NCR5380/53c400 SCSI PIO support"
841 depends on ISA && SCSI
842 select SCSI_SPI_ATTRS
844 This is a driver for the old NCR 53c80 series of SCSI controllers
845 on boards using PIO. Most boards such as the Trantor T130 fit this
846 category, along with a large number of ISA 8bit controllers shipped
847 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
848 you should select the specific driver for that card rather than
849 generic 5380 support.
851 It is explained in section 3.8 of the SCSI-HOWTO, available from
852 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
853 of the box, you may have to change some settings in
854 <file:drivers/scsi/g_NCR5380.h>.
856 To compile this driver as a module, choose M here: the
857 module will be called g_NCR5380.
859 config SCSI_GENERIC_NCR5380_MMIO
860 tristate "Generic NCR5380/53c400 SCSI MMIO support"
861 depends on ISA && SCSI
862 select SCSI_SPI_ATTRS
864 This is a driver for the old NCR 53c80 series of SCSI controllers
865 on boards using memory mapped I/O.
866 It is explained in section 3.8 of the SCSI-HOWTO, available from
867 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
868 of the box, you may have to change some settings in
869 <file:drivers/scsi/g_NCR5380.h>.
871 To compile this driver as a module, choose M here: the
872 module will be called g_NCR5380_mmio.
874 config SCSI_GENERIC_NCR53C400
875 bool "Enable NCR53c400 extensions"
876 depends on SCSI_GENERIC_NCR5380
878 This enables certain optimizations for the NCR53c400 SCSI cards.
879 You might as well try it out. Note that this driver will only probe
880 for the Trantor T130B in its default configuration; you might have
881 to pass a command line option to the kernel at boot time if it does
882 not detect your card. See the file
883 <file:Documentation/scsi/g_NCR5380.txt> for details.
886 tristate "IBMMCA SCSI support"
887 depends on MCA && SCSI
889 This is support for the IBM SCSI adapter found in many of the PS/2
890 series computers. These machines have an MCA bus, so you need to
891 answer Y to "MCA support" as well and read
892 <file:Documentation/mca.txt>.
894 If the adapter isn't found during boot (a common problem for models
895 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
896 option, where <pun> is the id of the SCSI subsystem (usually 7, but
897 if that doesn't work check your reference diskette). Owners of
898 model 95 with a LED-matrix-display can in addition activate some
899 activity info like under OS/2, but more informative, by setting
900 'ibmmcascsi=display' as an additional kernel parameter. Try "man
901 bootparam" or see the documentation of your boot loader about how to
902 pass options to the kernel.
904 To compile this driver as a module, choose M here: the
905 module will be called ibmmca.
907 config IBMMCA_SCSI_ORDER_STANDARD
908 bool "Standard SCSI-order"
909 depends on SCSI_IBMMCA
911 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
912 are assigned to the drive letters, starting with the lowest SCSI-id
913 (physical number -- pun) to be drive C:, as seen from DOS and
914 similar operating systems. When looking into papers describing the
915 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
916 The SCSI-standard follows a hardware-hierarchy which says that id 7
917 has the highest priority and id 0 the lowest. Therefore, the host
918 adapters are still today everywhere placed as SCSI-id 7 by default.
919 In the SCSI-standard, the drive letters express the priority of the
920 disk. C: should be the hard disk, or a partition on it, with the
921 highest priority. This must therefore be the disk with the highest
922 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
923 original definition of the SCSI-standard as also industrial- and
924 process-control-machines, like VME-CPUs running under realtime-OSes
925 (e.g. LynxOS, OS9) do.
927 If you like to run Linux on your MCA-machine with the same
928 assignment of hard disks as seen from e.g. DOS or OS/2 on your
929 machine, which is in addition conformant to the SCSI-standard, you
930 must say Y here. This is also necessary for MCA-Linux users who want
931 to keep downward compatibility to older releases of the
932 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
935 If you like to have the lowest SCSI-id assigned as drive C:, as
936 modern SCSI-BIOSes do, which does not conform to the standard, but
937 is widespread and common in the PC-world of today, you must say N
938 here. If unsure, say Y.
940 config IBMMCA_SCSI_DEV_RESET
941 bool "Reset SCSI-devices at boottime"
942 depends on SCSI_IBMMCA
944 By default, SCSI-devices are reset when the machine is powered on.
945 However, some devices exist, like special-control-devices,
946 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
947 not reset when switched on. If you say Y here, each device connected
948 to your SCSI-bus will be issued a reset-command after it has been
949 probed, while the kernel is booting. This may cause problems with
950 more modern devices, like hard disks, which do not appreciate these
951 reset commands, and can cause your system to hang. So say Y only if
952 you know that one of your older devices needs it; N is the safe
956 tristate "IBM ServeRAID support"
957 depends on PCI && SCSI
959 This is support for the IBM ServeRAID hardware RAID controllers.
960 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
961 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
962 for more information. If this driver does not work correctly
963 without modification please contact the author by email at
964 <ipslinux@adaptec.com>.
966 To compile this driver as a module, choose M here: the
967 module will be called ips.
970 tristate "IBM Virtual SCSI support"
971 depends on PPC_PSERIES || PPC_ISERIES
972 select SCSI_SRP_ATTRS
973 select VIOPATH if PPC_ISERIES
975 This is the IBM POWER Virtual SCSI Client
977 To compile this driver as a module, choose M here: the
978 module will be called ibmvscsic.
980 config SCSI_IBMVSCSIS
981 tristate "IBM Virtual SCSI Server support"
982 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
984 This is the SRP target driver for IBM pSeries virtual environments.
986 The userspace component needed to initialize the driver and
987 documentation can be found:
989 http://stgt.berlios.de/
991 To compile this driver as a module, choose M here: the
992 module will be called ibmvstgt.
995 tristate "IBM Virtual FC support"
996 depends on PPC_PSERIES && SCSI
999 This is the IBM POWER Virtual FC Client
1001 To compile this driver as a module, choose M here: the
1002 module will be called ibmvfc.
1004 config SCSI_IBMVFC_TRACE
1005 bool "enable driver internal trace"
1006 depends on SCSI_IBMVFC
1009 If you say Y here, the driver will trace all commands issued
1010 to the adapter. Performance impact is minimal. Trace can be
1011 dumped using /sys/class/scsi_host/hostXX/trace.
1014 tristate "Initio 9100U(W) support"
1015 depends on PCI && SCSI
1017 This is support for the Initio 91XXU(W) SCSI host adapter. Please
1018 read the SCSI-HOWTO, available from
1019 <http://www.tldp.org/docs.html#howto>.
1021 To compile this driver as a module, choose M here: the
1022 module will be called initio.
1025 tristate "Initio INI-A100U2W support"
1026 depends on PCI && SCSI
1028 This is support for the Initio INI-A100U2W SCSI host adapter.
1029 Please read the SCSI-HOWTO, available from
1030 <http://www.tldp.org/docs.html#howto>.
1032 To compile this driver as a module, choose M here: the
1033 module will be called a100u2w.
1036 tristate "IOMEGA parallel port (ppa - older drives)"
1037 depends on SCSI && PARPORT_PC
1039 This driver supports older versions of IOMEGA's parallel port ZIP
1040 drive (a 100 MB removable media device).
1042 Note that you can say N here if you have the SCSI version of the ZIP
1043 drive: it will be supported automatically if you said Y to the
1044 generic "SCSI disk support", above.
1046 If you have the ZIP Plus drive or a more recent parallel port ZIP
1047 drive (if the supplied cable with the drive is labeled "AutoDetect")
1048 then you should say N here and Y to "IOMEGA parallel port (imm -
1049 newer drives)", below.
1051 For more information about this driver and how to use it you should
1052 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1053 the SCSI-HOWTO, which is available from
1054 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1055 you will still be able to use the parallel port for other tasks,
1056 such as a printer; it is safe to compile both drivers into the
1059 To compile this driver as a module, choose M here: the
1060 module will be called ppa.
1063 tristate "IOMEGA parallel port (imm - newer drives)"
1064 depends on SCSI && PARPORT_PC
1066 This driver supports newer versions of IOMEGA's parallel port ZIP
1067 drive (a 100 MB removable media device).
1069 Note that you can say N here if you have the SCSI version of the ZIP
1070 drive: it will be supported automatically if you said Y to the
1071 generic "SCSI disk support", above.
1073 If you have the ZIP Plus drive or a more recent parallel port ZIP
1074 drive (if the supplied cable with the drive is labeled "AutoDetect")
1075 then you should say Y here; if you have an older ZIP drive, say N
1076 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
1078 For more information about this driver and how to use it you should
1079 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1080 the SCSI-HOWTO, which is available from
1081 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1082 you will still be able to use the parallel port for other tasks,
1083 such as a printer; it is safe to compile both drivers into the
1086 To compile this driver as a module, choose M here: the
1087 module will be called imm.
1089 config SCSI_IZIP_EPP16
1090 bool "ppa/imm option - Use slow (but safe) EPP-16"
1091 depends on SCSI_PPA || SCSI_IMM
1093 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1094 allows them to act as expansion buses that can handle up to 64
1097 Some parallel port chipsets are slower than their motherboard, and
1098 so we have to control the state of the chipset's FIFO queue every
1099 now and then to avoid data loss. This will be done if you say Y
1102 Generally, saying Y is the safe option and slows things down a bit.
1104 config SCSI_IZIP_SLOW_CTR
1105 bool "ppa/imm option - Assume slow parport control register"
1106 depends on SCSI_PPA || SCSI_IMM
1108 Some parallel ports are known to have excessive delays between
1109 changing the parallel port control register and good data being
1110 available on the parallel port data/status register. This option
1111 forces a small delay (1.0 usec to be exact) after changing the
1112 control register to let things settle out. Enabling this option may
1113 result in a big drop in performance but some very old parallel ports
1114 (found in 386 vintage machines) will not work properly.
1116 Generally, saying N is fine.
1118 config SCSI_NCR53C406A
1119 tristate "NCR53c406a SCSI support"
1120 depends on ISA && SCSI
1122 This is support for the NCR53c406a SCSI host adapter. For user
1123 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1124 in the kernel source. Also read the SCSI-HOWTO, available from
1125 <http://www.tldp.org/docs.html#howto>.
1127 To compile this driver as a module, choose M here: the
1128 module will be called NCR53c406.
1130 config SCSI_NCR_D700
1131 tristate "NCR Dual 700 MCA SCSI support"
1132 depends on MCA && SCSI
1133 select SCSI_SPI_ATTRS
1135 This is a driver for the MicroChannel Dual 700 card produced by
1136 NCR and commonly used in 345x/35xx/4100 class machines. It always
1137 tries to negotiate sync and uses tag command queueing.
1139 Unless you have an NCR manufactured machine, the chances are that
1140 you do not have this SCSI card, so say N.
1143 tristate "HP Lasi SCSI support for 53c700/710"
1144 depends on GSC && SCSI
1145 select SCSI_SPI_ATTRS
1147 This is a driver for the SCSI controller in the Lasi chip found in
1148 many PA-RISC workstations & servers. If you do not know whether you
1149 have a Lasi chip, it is safe to say "Y" here.
1151 config SCSI_SNI_53C710
1152 tristate "SNI RM SCSI support for 53c710"
1153 depends on SNI_RM && SCSI
1154 select SCSI_SPI_ATTRS
1155 select 53C700_LE_ON_BE
1157 This is a driver for the onboard SCSI controller found in older
1158 SNI RM workstations & servers.
1160 config 53C700_LE_ON_BE
1162 depends on SCSI_LASI700
1166 tristate "Promise SuperTrak EX Series support"
1167 depends on PCI && SCSI
1169 This driver supports Promise SuperTrak EX series storage controllers.
1171 Promise provides Linux RAID configuration utility for these
1172 controllers. Please visit <http://www.promise.com> to download.
1174 To compile this driver as a module, choose M here: the
1175 module will be called stex.
1177 config 53C700_BE_BUS
1179 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1182 config SCSI_SYM53C8XX_2
1183 tristate "SYM53C8XX Version 2 SCSI support"
1184 depends on PCI && SCSI
1185 select SCSI_SPI_ATTRS
1187 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1188 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1189 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1190 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1191 controllers; you need to use the Fusion MPT driver for that.
1193 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1196 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1197 int "DMA addressing mode"
1198 depends on SCSI_SYM53C8XX_2
1201 This option only applies to PCI-SCSI chips that are PCI DAC
1202 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1204 When set to 0, the driver will program the chip to only perform
1205 32-bit DMA. When set to 1, the chip will be able to perform DMA
1206 to addresses up to 1TB. When set to 2, the driver supports the
1207 full 64-bit DMA address range, but can only address 16 segments
1208 of 4 GB each. This limits the total addressable range to 64 GB.
1210 Most machines with less than 4GB of memory should use a setting
1211 of 0 for best performance. If your machine has 4GB of memory
1212 or more, you should set this option to 1 (the default).
1214 The still experimental value 2 (64 bit DMA addressing with 16
1215 x 4GB segments limitation) can be used on systems that require
1216 PCI address bits past bit 39 to be set for the addressing of
1217 memory using PCI DAC cycles.
1219 config SCSI_SYM53C8XX_DEFAULT_TAGS
1220 int "Default tagged command queue depth"
1221 depends on SCSI_SYM53C8XX_2
1224 This is the default value of the command queue depth the
1225 driver will announce to the generic SCSI layer for devices
1226 that support tagged command queueing. This value can be changed
1227 from the boot command line. This is a soft limit that cannot
1228 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1230 config SCSI_SYM53C8XX_MAX_TAGS
1231 int "Maximum number of queued commands"
1232 depends on SCSI_SYM53C8XX_2
1235 This option allows you to specify the maximum number of commands
1236 that can be queued to any device, when tagged command queuing is
1237 possible. The driver supports up to 256 queued commands per device.
1238 This value is used as a compiled-in hard limit.
1240 config SCSI_SYM53C8XX_MMIO
1241 bool "Use memory mapped IO"
1242 depends on SCSI_SYM53C8XX_2
1245 Memory mapped IO is faster than Port IO. Most people should
1246 answer Y here, but some machines may have problems. If you have
1247 to answer N here, please report the problem to the maintainer.
1250 tristate "IBM Power Linux RAID adapter support"
1251 depends on PCI && SCSI && ATA
1254 This driver supports the IBM Power Linux family RAID adapters.
1255 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1256 as IBM iSeries 5702, 5703, 5709, and 570A.
1258 config SCSI_IPR_TRACE
1259 bool "enable driver internal trace"
1263 If you say Y here, the driver will trace all commands issued
1264 to the adapter. Performance impact is minimal. Trace can be
1265 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1267 config SCSI_IPR_DUMP
1268 bool "enable adapter dump support"
1272 If you say Y here, the driver will support adapter crash dump.
1273 If you enable this support, the iprdump daemon can be used
1274 to capture adapter failure analysis information.
1277 tristate "Zalon SCSI support"
1278 depends on GSC && SCSI
1279 select SCSI_SPI_ATTRS
1281 The Zalon is a GSC/HSC bus interface chip that sits between the
1282 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1283 C110, J200, J210 and some D, K & R-class machines. It's also
1284 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1285 Say Y here if you have one of these machines or cards.
1287 config SCSI_NCR_Q720
1288 tristate "NCR Quad 720 MCA SCSI support"
1289 depends on MCA && SCSI
1290 select SCSI_SPI_ATTRS
1292 This is a driver for the MicroChannel Quad 720 card produced by
1293 NCR and commonly used in 345x/35xx/4100 class machines. It always
1294 tries to negotiate sync and uses tag command queueing.
1296 Unless you have an NCR manufactured machine, the chances are that
1297 you do not have this SCSI card, so say N.
1299 config SCSI_NCR53C8XX_DEFAULT_TAGS
1300 int "default tagged command queue depth"
1301 depends on SCSI_ZALON || SCSI_NCR_Q720
1304 "Tagged command queuing" is a feature of SCSI-2 which improves
1305 performance: the host adapter can send several SCSI commands to a
1306 device's queue even if previous commands haven't finished yet.
1307 Because the device is intelligent, it can optimize its operations
1308 (like head positioning) based on its own request queue. Some SCSI
1309 devices don't implement this properly; if you want to disable this
1310 feature, enter 0 or 1 here (it doesn't matter which).
1312 The default value is 8 and should be supported by most hard disks.
1313 This value can be overridden from the boot command line using the
1314 'tags' option as follows (example):
1315 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1316 4, set queue depth to 16 for target 2 and target 3 on controller 0
1317 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1319 The normal answer therefore is to go with the default 8 and to use
1320 a boot command line option for devices that need to use a different
1321 command queue depth.
1323 There is no safe option other than using good SCSI devices.
1325 config SCSI_NCR53C8XX_MAX_TAGS
1326 int "maximum number of queued commands"
1327 depends on SCSI_ZALON || SCSI_NCR_Q720
1330 This option allows you to specify the maximum number of commands
1331 that can be queued to any device, when tagged command queuing is
1332 possible. The default value is 32. Minimum is 2, maximum is 64.
1333 Modern hard disks are able to support 64 tags and even more, but
1334 do not seem to be faster when more than 32 tags are being used.
1336 So, the normal answer here is to go with the default value 32 unless
1337 you are using very large hard disks with large cache (>= 1 MB) that
1338 are able to take advantage of more than 32 tagged commands.
1340 There is no safe option and the default answer is recommended.
1342 config SCSI_NCR53C8XX_SYNC
1343 int "synchronous transfers frequency in MHz"
1344 depends on SCSI_ZALON || SCSI_NCR_Q720
1347 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1348 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1349 are respectively the maximum data transfer rates in mega-transfers
1350 per second for each class. For example, a FAST-20 Wide 16 device is
1351 able to transfer data at 20 million 16 bit packets per second for a
1352 total rate of 40 MB/s.
1354 You may specify 0 if you want to only use asynchronous data
1355 transfers. This is the safest and slowest option. Otherwise, specify
1356 a value between 5 and 80, depending on the capability of your SCSI
1357 controller. The higher the number, the faster the data transfer.
1358 Note that 80 should normally be ok since the driver decreases the
1359 value automatically according to the controller's capabilities.
1361 Your answer to this question is ignored for controllers with NVRAM,
1362 since the driver will get this information from the user set-up. It
1363 also can be overridden using a boot setup option, as follows
1364 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1365 for FAST-20 synchronous data transfer (20 mega-transfers per
1368 The normal answer therefore is not to go with the default but to
1369 select the maximum value 80 allowing the driver to use the maximum
1370 value supported by each controller. If this causes problems with
1371 your SCSI devices, you should come back and decrease the value.
1373 There is no safe option other than using good cabling, right
1374 terminations and SCSI conformant devices.
1376 config SCSI_NCR53C8XX_NO_DISCONNECT
1377 bool "not allow targets to disconnect"
1378 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1380 This option is only provided for safety if you suspect some SCSI
1381 device of yours to not support properly the target-disconnect
1382 feature. In that case, you would say Y here. In general however, to
1383 not allow targets to disconnect is not reasonable if there is more
1384 than 1 device on a SCSI bus. The normal answer therefore is N.
1387 tristate "PAS16 SCSI support"
1388 depends on ISA && SCSI
1389 select SCSI_SPI_ATTRS
1391 This is support for a SCSI host adapter. It is explained in section
1392 3.10 of the SCSI-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1394 of the box, you may have to change some settings in
1395 <file:drivers/scsi/pas16.h>.
1397 To compile this driver as a module, choose M here: the
1398 module will be called pas16.
1400 config SCSI_QLOGIC_FAS
1401 tristate "Qlogic FAS SCSI support"
1402 depends on ISA && SCSI
1404 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1405 FastSCSI! cards as well as any other card based on the FASXX chip
1406 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1408 This driver does NOT support the PCI versions of these cards. The
1409 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1410 SCSI support"), below.
1412 Information about this driver is contained in
1413 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1414 SCSI-HOWTO, available from
1415 <http://www.tldp.org/docs.html#howto>.
1417 To compile this driver as a module, choose M here: the
1418 module will be called qlogicfas.
1420 config SCSI_QLOGIC_1280
1421 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1422 depends on PCI && SCSI
1424 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1426 To compile this driver as a module, choose M here: the
1427 module will be called qla1280.
1429 config SCSI_QLOGICPTI
1430 tristate "PTI Qlogic, ISP Driver"
1431 depends on SBUS && SCSI
1433 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1434 controllers are known under Solaris as qpti and in the openprom as
1435 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1436 driven by a different driver.
1438 To compile this driver as a module, choose M here: the
1439 module will be called qlogicpti.
1441 source "drivers/scsi/qla2xxx/Kconfig"
1442 source "drivers/scsi/qla4xxx/Kconfig"
1445 tristate "Emulex LightPulse Fibre Channel Support"
1446 depends on PCI && SCSI
1447 select SCSI_FC_ATTRS
1449 This lpfc driver supports the Emulex LightPulse
1450 Family of Fibre Channel PCI host adapters.
1452 config SCSI_LPFC_DEBUG_FS
1453 bool "Emulex LightPulse Fibre Channel debugfs Support"
1454 depends on SCSI_LPFC && DEBUG_FS
1456 This makes debugging information from the lpfc driver
1457 available via the debugfs filesystem.
1460 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1461 depends on (EISA || MCA) && SCSI
1462 select SCSI_SPI_ATTRS
1464 This driver is for NCR53c710 based SCSI host adapters.
1466 It currently supports Compaq EISA cards and NCR MCA cards
1468 config SCSI_SYM53C416
1469 tristate "Symbios 53c416 SCSI support"
1470 depends on ISA && SCSI
1472 This is support for the sym53c416 SCSI host adapter, the SCSI
1473 adapter that comes with some HP scanners. This driver requires that
1474 the sym53c416 is configured first using some sort of PnP
1475 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1476 are using isapnp then you need to compile this driver as a module
1477 and then load it using insmod after isapnp has run. The parameters
1478 of the configured card(s) should be passed to the driver. The format
1481 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1483 To compile this driver as a module, choose M here: the
1484 module will be called sym53c416.
1487 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1488 depends on PCI && SCSI && EXPERIMENTAL
1490 This driver supports PCI SCSI host adapters based on the ASIC
1491 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1493 This driver works, but is still in experimental status. So better
1494 have a bootable disk and a backup in case of emergency.
1496 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1498 To compile this driver as a module, choose M here: the
1499 module will be called dc395x.
1502 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1503 depends on PCI && SCSI
1505 This driver supports PCI SCSI host adapters based on the Am53C974A
1506 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1507 PCscsi/PCnet (Am53/79C974) solutions.
1509 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1511 Note that this driver does NOT support Tekram DC390W/U/F, which are
1512 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1514 To compile this driver as a module, choose M here: the
1515 module will be called tmscsim.
1518 tristate "Trantor T128/T128F/T228 SCSI support"
1519 depends on ISA && SCSI
1520 select SCSI_SPI_ATTRS
1521 select CHECK_SIGNATURE
1523 This is support for a SCSI host adapter. It is explained in section
1524 3.11 of the SCSI-HOWTO, available from
1525 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1526 of the box, you may have to change some settings in
1527 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1528 Adaptec, and some former Trantor products are being sold under the
1531 To compile this driver as a module, choose M here: the
1532 module will be called t128.
1535 tristate "UltraStor 14F/34F support"
1536 depends on ISA && SCSI && ISA_DMA_API
1538 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1539 The source at <file:drivers/scsi/u14-34f.c> contains some
1540 information about this hardware. If the driver doesn't work out of
1541 the box, you may have to change some settings in
1542 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1543 <http://www.tldp.org/docs.html#howto>. Note that there is also
1544 another driver for the same hardware: "UltraStor SCSI support",
1545 below. You should say Y to both only if you want 24F support as
1548 To compile this driver as a module, choose M here: the
1549 module will be called u14-34f.
1551 config SCSI_U14_34F_TAGGED_QUEUE
1552 bool "enable tagged command queueing"
1553 depends on SCSI_U14_34F
1555 This is a feature of SCSI-2 which improves performance: the host
1556 adapter can send several SCSI commands to a device's queue even if
1557 previous commands haven't finished yet.
1558 This is equivalent to the "u14-34f=tc:y" boot option.
1560 config SCSI_U14_34F_LINKED_COMMANDS
1561 bool "enable elevator sorting"
1562 depends on SCSI_U14_34F
1564 This option enables elevator sorting for all probed SCSI disks and
1565 CD-ROMs. It definitely reduces the average seek distance when doing
1566 random seeks, but this does not necessarily result in a noticeable
1567 performance improvement: your mileage may vary...
1568 This is equivalent to the "u14-34f=lc:y" boot option.
1570 config SCSI_U14_34F_MAX_TAGS
1571 int "maximum number of queued commands"
1572 depends on SCSI_U14_34F
1575 This specifies how many SCSI commands can be maximally queued for
1576 each probed SCSI device. You should reduce the default value of 8
1577 only if you have disks with buggy or limited tagged command support.
1578 Minimum is 2 and maximum is 14. This value is also the window size
1579 used by the elevator sorting option above. The effective value used
1580 by the driver for each probed SCSI device is reported at boot time.
1581 This is equivalent to the "u14-34f=mq:8" boot option.
1583 config SCSI_ULTRASTOR
1584 tristate "UltraStor SCSI support"
1585 depends on X86 && ISA && SCSI
1587 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1588 adapter family. This driver is explained in section 3.12 of the
1589 SCSI-HOWTO, available from
1590 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1591 of the box, you may have to change some settings in
1592 <file:drivers/scsi/ultrastor.h>.
1594 Note that there is also another driver for the same hardware:
1595 "UltraStor 14F/34F support", above.
1597 To compile this driver as a module, choose M here: the
1598 module will be called ultrastor.
1601 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1602 depends on PCI && SCSI && !64BIT
1604 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1605 SCSI host adapter. Please read the SCSI-HOWTO, available from
1606 <http://www.tldp.org/docs.html#howto>.
1608 To compile this driver as a module, choose M here: the
1609 module will be called nsp32.
1612 tristate "SCSI debugging host simulator"
1616 This is a host adapter simulator that can simulate multiple hosts
1617 each with multiple dummy SCSI devices (disks). It defaults to one
1618 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1619 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1620 dummy disks are simulated, they share the same kernel RAM for
1621 their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
1622 information. This driver is primarily of use to those testing the
1623 SCSI and block subsystems. If unsure, say N.
1626 tristate "MESH (Power Mac internal SCSI) support"
1627 depends on PPC32 && PPC_PMAC && SCSI
1629 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1630 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1631 other Power Macintoshes do). Say Y to include support for this SCSI
1634 To compile this driver as a module, choose M here: the
1635 module will be called mesh.
1637 config SCSI_MESH_SYNC_RATE
1638 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1639 depends on SCSI_MESH
1642 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1643 drives a bus which is entirely internal to the machine (such as the
1644 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1645 operation at up to 10 MB/s. On machines where the SCSI bus
1646 controlled by the MESH can have external devices connected, it is
1647 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1648 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1649 to disable synchronous operation.
1651 config SCSI_MESH_RESET_DELAY_MS
1652 int "initial bus reset delay (ms) (0 = no reset)"
1653 depends on SCSI_MESH
1656 config SCSI_MAC53C94
1657 tristate "53C94 (Power Mac external SCSI) support"
1658 depends on PPC32 && PPC_PMAC && SCSI
1660 On Power Macintoshes (and clones) with two SCSI buses, the external
1661 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1662 machines which only have one SCSI bus, such as the 7200, also use
1663 the 53C94. Say Y to include support for the 53C94.
1665 To compile this driver as a module, choose M here: the
1666 module will be called mac53c94.
1668 source "drivers/scsi/arm/Kconfig"
1671 bool "MIPS JAZZ FAS216 SCSI support"
1672 depends on MACH_JAZZ && SCSI
1673 select SCSI_SPI_ATTRS
1675 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1676 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1680 tristate "A3000 WD33C93A support"
1681 depends on AMIGA && SCSI
1683 If you have an Amiga 3000 and have SCSI devices connected to the
1684 built-in SCSI controller, say Y. Otherwise, say N.
1686 To compile this driver as a module, choose M here: the
1687 module will be called a3000.
1690 tristate "A2091/A590 WD33C93A support"
1691 depends on ZORRO && SCSI
1693 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1696 To compile this driver as a module, choose M here: the
1697 module will be called a2091.
1700 tristate "GVP Series II WD33C93A support"
1701 depends on ZORRO && SCSI
1703 If you have a Great Valley Products Series II SCSI controller,
1704 answer Y. Also say Y if you have a later model of GVP SCSI
1705 controller (such as the GVP A4008 or a Combo board). Otherwise,
1706 answer N. This driver does NOT work for the T-Rex series of
1707 accelerators from TekMagic and GVP-M.
1709 To compile this driver as a module, choose M here: the
1710 module will be called gvp11.
1713 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1714 depends on AMIGA && SCSI && EXPERIMENTAL
1715 select SCSI_SPI_ATTRS
1717 If you have an Amiga 4000T and have SCSI devices connected to the
1718 built-in SCSI controller, say Y. Otherwise, say N.
1720 To compile this driver as a module, choose M here: the
1721 module will be called a4000t.
1723 config SCSI_ZORRO7XX
1724 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1725 depends on ZORRO && SCSI && EXPERIMENTAL
1726 select SCSI_SPI_ATTRS
1728 Support for various NCR53c710-based SCSI controllers on Zorro
1729 expansion boards for the Amiga.
1731 - the Amiga 4091 Zorro III SCSI-2 controller,
1732 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1734 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1735 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1736 accelerator card for the Amiga 1200,
1737 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1740 tristate "Atari native SCSI support"
1741 depends on ATARI && SCSI
1742 select SCSI_SPI_ATTRS
1745 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1746 Falcon, ...) say Y to get it supported. Of course also, if you have
1747 a compatible SCSI controller (e.g. for Medusa).
1749 To compile this driver as a module, choose M here: the
1750 module will be called atari_scsi.
1752 This driver supports both styles of NCR integration into the
1753 system: the TT style (separate DMA), and the Falcon style (via
1754 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1755 in the Hades (without DMA).
1757 config ATARI_SCSI_TOSHIBA_DELAY
1758 bool "Long delays for Toshiba CD-ROMs"
1759 depends on ATARI_SCSI
1761 This option increases the delay after a SCSI arbitration to
1762 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1763 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1764 would impact performance a bit, so say N.
1766 config ATARI_SCSI_RESET_BOOT
1767 bool "Reset SCSI-devices at boottime"
1768 depends on ATARI_SCSI
1770 Reset the devices on your Atari whenever it boots. This makes the
1771 boot process fractionally longer but may assist recovery from errors
1772 that leave the devices with SCSI operations partway completed.
1775 bool "Macintosh NCR5380 SCSI"
1776 depends on MAC && SCSI=y
1777 select SCSI_SPI_ATTRS
1779 This is the NCR 5380 SCSI controller included on most of the 68030
1780 based Macintoshes. If you have one of these say Y and read the
1781 SCSI-HOWTO, available from
1782 <http://www.tldp.org/docs.html#howto>.
1785 tristate "Macintosh NCR53c9[46] SCSI"
1786 depends on MAC && SCSI
1787 select SCSI_SPI_ATTRS
1789 This is the NCR 53c9x SCSI controller found on most of the 68040
1792 To compile this driver as a module, choose M here: the module
1793 will be called mac_esp.
1796 bool "WD33C93 SCSI driver for MVME147"
1797 depends on MVME147 && SCSI=y
1798 select SCSI_SPI_ATTRS
1800 Support for the on-board SCSI controller on the Motorola MVME147
1801 single-board computer.
1804 tristate "NCR53C710 SCSI driver for MVME16x"
1805 depends on MVME16x && SCSI
1806 select SCSI_SPI_ATTRS
1808 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1809 SCSI controller chip. Almost everyone using one of these boards
1810 will want to say Y to this question.
1812 config BVME6000_SCSI
1813 tristate "NCR53C710 SCSI driver for BVME6000"
1814 depends on BVME6000 && SCSI
1815 select SCSI_SPI_ATTRS
1817 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1818 SCSI controller chip. Almost everyone using one of these boards
1819 will want to say Y to this question.
1822 tristate "Sun3 NCR5380 SCSI"
1823 depends on SUN3 && SCSI
1824 select SCSI_SPI_ATTRS
1826 This option will enable support for the OBIO (onboard io) NCR5380
1827 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1828 "Sun3" type VME scsi controllers also based on the NCR5380.
1829 General Linux information on the Sun 3 series (now discontinued)
1830 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1833 bool "Sun3x ESP SCSI"
1834 depends on SUN3X && SCSI=y
1835 select SCSI_SPI_ATTRS
1837 The ESP was an on-board SCSI controller used on Sun 3/80
1838 machines. Say Y here to compile in support for it.
1841 tristate "Sparc ESP Scsi Driver"
1842 depends on SBUS && SCSI
1843 select SCSI_SPI_ATTRS
1845 This is the driver for the Sun ESP SCSI host adapter. The ESP
1846 chipset is present in most SPARC SBUS-based computers and
1847 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1848 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1850 To compile this driver as a module, choose M here: the
1851 module will be called sun_esp.
1854 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1855 depends on S390 && QDIO && SCSI
1856 select SCSI_FC_ATTRS
1858 If you want to access SCSI devices attached to your IBM eServer
1859 zSeries by means of Fibre Channel interfaces say Y.
1860 For details please refer to the documentation provided by IBM at
1861 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1863 This driver is also available as a module. This module will be
1864 called zfcp. If you want to compile it as a module, say M here
1865 and read <file:Documentation/kbuild/modules.txt>.
1868 tristate "PMC SIERRA Linux MaxRAID adapter support"
1869 depends on PCI && SCSI && NET
1871 This driver supports the PMC SIERRA MaxRAID adapters.
1874 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1875 depends on PCI && SCSI
1876 select SCSI_SAS_LIBSAS
1878 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1879 based host adapters.
1882 tristate "SCSI RDMA Protocol helper library"
1883 depends on SCSI && PCI
1886 If you wish to use SRP target drivers, say Y.
1888 To compile this driver as a module, choose M here: the
1889 module will be called libsrp.
1892 tristate "Brocade BFA Fibre Channel Support"
1893 depends on PCI && SCSI
1894 select SCSI_FC_ATTRS
1896 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1898 To compile this driver as a module, choose M here. The module will
1902 tristate "virtio-scsi support (EXPERIMENTAL)"
1903 depends on EXPERIMENTAL && VIRTIO
1905 This is the virtual HBA driver for virtio. If the kernel will
1906 be used in a virtual machine, say Y or M.
1909 endif # SCSI_LOWLEVEL
1911 source "drivers/scsi/pcmcia/Kconfig"
1913 source "drivers/scsi/device_handler/Kconfig"
1915 source "drivers/scsi/osd/Kconfig"