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://linux1.onstream.nl/test/>
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.mostang.com/sane/>). For CD
160 writer software look at Cdrtools
161 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/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
313 If you wish to export transport-specific information about
314 each attached iSCSI device to sysfs, say Y.
317 config SCSI_SAS_ATTRS
318 tristate "SAS Transport Attributes"
322 If you wish to export transport-specific information about
323 each attached SAS device to sysfs, say Y.
325 source "drivers/scsi/libsas/Kconfig"
327 config SCSI_SRP_ATTRS
328 tristate "SRP Transport Attributes"
331 If you wish to export transport-specific information about
332 each attached SRP device to sysfs, say Y.
334 config SCSI_SRP_TGT_ATTRS
335 bool "SCSI target support for SRP Transport Attributes"
336 depends on SCSI_SRP_ATTRS
337 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
339 If you want to use SCSI target mode drivers enable this option.
343 menuconfig SCSI_LOWLEVEL
344 bool "SCSI low-level drivers"
348 if SCSI_LOWLEVEL && SCSI
351 tristate "iSCSI Initiator over TCP/IP"
352 depends on SCSI && INET
356 select SCSI_ISCSI_ATTRS
358 The iSCSI Driver provides a host with the ability to access storage
359 through an IP network. The driver uses the iSCSI protocol to transport
360 SCSI requests and responses over a TCP/IP network between the host
361 (the "initiator") and "targets". Architecturally, the iSCSI driver
362 combines with the host's TCP/IP stack, network drivers, and Network
363 Interface Card (NIC) to provide the same functions as a SCSI or a
364 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
366 To compile this driver as a module, choose M here: the
367 module will be called iscsi_tcp.
369 The userspace component needed to initialize the driver, documentation,
370 and sample configuration files can be found here:
372 http://open-iscsi.org
374 config ISCSI_BOOT_SYSFS
375 tristate "iSCSI Boot Sysfs Interface"
378 This option enables support for exposing iSCSI boot information
379 via sysfs to userspace. If you wish to export this information,
380 say Y. Otherwise, say N.
382 source "drivers/scsi/cxgbi/Kconfig"
383 source "drivers/scsi/bnx2i/Kconfig"
384 source "drivers/scsi/be2iscsi/Kconfig"
387 tristate "SGI WD93C93 SCSI Driver"
388 depends on SGI_HAS_WD93 && SCSI
390 If you have a Western Digital WD93 SCSI controller on
391 an SGI MIPS system, say Y. Otherwise, say N.
393 config BLK_DEV_3W_XXXX_RAID
394 tristate "3ware 5/6/7/8xxx ATA-RAID support"
395 depends on PCI && SCSI
397 3ware is the only hardware ATA-Raid product in Linux to date.
398 This card is 2,4, or 8 channel master mode support only.
399 SCSI support required!!!
401 <http://www.3ware.com/>
403 Please read the comments at the top of
404 <file:drivers/scsi/3w-xxxx.c>.
407 tristate "HP Smart Array SCSI driver"
408 depends on PCI && SCSI
410 This driver supports HP Smart Array Controllers (circa 2009).
411 It is a SCSI alternative to the cciss driver, which is a block
412 driver. Anyone wishing to use HP Smart Array controllers who
413 would prefer the devices be presented to linux as SCSI devices,
414 rather than as generic block devices should say Y here.
417 tristate "3ware 9xxx SATA-RAID support"
418 depends on PCI && SCSI
420 This driver supports the 9000 series 3ware SATA-RAID cards.
422 <http://www.amcc.com>
424 Please read the comments at the top of
425 <file:drivers/scsi/3w-9xxx.c>.
428 tristate "3ware 97xx SAS/SATA-RAID support"
429 depends on PCI && SCSI
431 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
435 Please read the comments at the top of
436 <file:drivers/scsi/3w-sas.c>.
438 config SCSI_7000FASST
439 tristate "7000FASST SCSI support"
440 depends on ISA && SCSI && ISA_DMA_API
441 select CHECK_SIGNATURE
443 This driver supports the Western Digital 7000 SCSI host adapter
444 family. Some information is in the source:
445 <file:drivers/scsi/wd7000.c>.
447 To compile this driver as a module, choose M here: the
448 module will be called wd7000.
451 tristate "ACARD SCSI support"
452 depends on PCI && SCSI
454 This driver supports the ACARD SCSI host adapter.
455 Support Chip <ATP870 ATP876 ATP880 ATP885>
456 To compile this driver as a module, choose M here: the
457 module will be called atp870u.
460 tristate "Adaptec AHA152X/2825 support"
461 depends on ISA && SCSI && !64BIT
462 select SCSI_SPI_ATTRS
463 select CHECK_SIGNATURE
465 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
466 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
467 must be manually specified in this case.
469 It is explained in section 3.3 of the SCSI-HOWTO, available from
470 <http://www.tldp.org/docs.html#howto>. You might also want to
471 read the file <file:Documentation/scsi/aha152x.txt>.
473 To compile this driver as a module, choose M here: the
474 module will be called aha152x.
477 tristate "Adaptec AHA1542 support"
478 depends on ISA && SCSI && ISA_DMA_API
480 This is support for a SCSI host adapter. It is explained in section
481 3.4 of the SCSI-HOWTO, available from
482 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
483 purchased by Adaptec, and some former Trantor products are being
484 sold under the Adaptec name. If it doesn't work out of the box, you
485 may have to change some settings in <file:drivers/scsi/aha1542.h>.
487 To compile this driver as a module, choose M here: the
488 module will be called aha1542.
491 tristate "Adaptec AHA1740 support"
492 depends on EISA && SCSI
494 This is support for a SCSI host adapter. It is explained in section
495 3.5 of the SCSI-HOWTO, available from
496 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
497 of the box, you may have to change some settings in
498 <file:drivers/scsi/aha1740.h>.
500 To compile this driver as a module, choose M here: the
501 module will be called aha1740.
504 tristate "Adaptec AACRAID support"
505 depends on SCSI && PCI
507 This driver supports a variety of Dell, HP, Adaptec, IBM and
508 ICP storage products. For a list of supported products, refer
509 to <file:Documentation/scsi/aacraid.txt>.
511 To compile this driver as a module, choose M here: the module
512 will be called aacraid.
515 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
517 config SCSI_AIC7XXX_OLD
518 tristate "Adaptec AIC7xxx support (old driver)"
519 depends on (ISA || EISA || PCI ) && SCSI
521 WARNING This driver is an older aic7xxx driver and is no longer
522 under active development. Adaptec, Inc. is writing a new driver to
523 take the place of this one, and it is recommended that whenever
524 possible, people should use the new Adaptec written driver instead
525 of this one. This driver will eventually be phased out entirely.
527 This is support for the various aic7xxx based Adaptec SCSI
528 controllers. These include the 274x EISA cards; 284x VLB cards;
529 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
530 motherboard based SCSI controllers from Adaptec. It does not support
531 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
532 support them. It does not support the 2920 cards from Adaptec that
533 use the Future Domain SCSI controller chip. For those cards, you
534 need the "Future Domain 16xx SCSI support" driver.
536 In general, if the controller is based on an Adaptec SCSI controller
537 chip from the aic777x series or the aic78xx series, this driver
538 should work. The only exception is the 7810 which is specifically
539 not supported (that's the RAID controller chip on the AAA-13x
542 Note that the AHA2920 SCSI host adapter is *not* supported by this
543 driver; choose "Future Domain 16xx SCSI support" instead if you have
546 Information on the configuration options for this controller can be
547 found by checking the help file for each of the available
548 configuration options. You should read
549 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
550 contacting the maintainer with any questions. The SCSI-HOWTO,
551 available from <http://www.tldp.org/docs.html#howto>, can also
554 To compile this driver as a module, choose M here: the
555 module will be called aic7xxx_old.
557 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
558 source "drivers/scsi/aic94xx/Kconfig"
559 source "drivers/scsi/mvsas/Kconfig"
562 tristate "Adaptec I2O RAID support "
563 depends on SCSI && PCI && VIRT_TO_BUS
565 This driver supports all of Adaptec's I2O based RAID controllers as
566 well as the DPT SmartRaid V cards. This is an Adaptec maintained
567 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
569 To compile this driver as a module, choose M here: the
570 module will be called dpt_i2o.
573 tristate "AdvanSys SCSI support"
574 depends on SCSI && VIRT_TO_BUS
575 depends on ISA || EISA || PCI
577 This is a driver for all SCSI host adapters manufactured by
578 AdvanSys. It is documented in the kernel source in
579 <file:drivers/scsi/advansys.c>.
581 To compile this driver as a module, choose M here: the
582 module will be called advansys.
585 tristate "Always IN2000 SCSI support"
586 depends on ISA && SCSI
588 This is support for an ISA bus SCSI host adapter. You'll find more
589 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
590 out of the box, you may have to change the jumpers for IRQ or
593 To compile this driver as a module, choose M here: the
594 module will be called in2000.
597 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
598 depends on PCI && SCSI
600 This driver supports all of ARECA's SATA/SAS RAID controller cards.
601 This is an ARECA-maintained driver by Erich Chen.
602 If you have any problems, please mail to: <erich@areca.com.tw>.
603 Areca supports Linux RAID config tools.
604 Please link <http://www.areca.com.tw>
606 To compile this driver as a module, choose M here: the
607 module will be called arcmsr (modprobe arcmsr).
609 config SCSI_ARCMSR_AER
610 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
611 depends on SCSI_ARCMSR && PCIEAER
614 The advanced error reporting(AER) capability is "NOT" provided by
615 ARC1200/1201/1202 SATA RAID controllers cards.
616 If your card is one of ARC1200/1201/1202, please use the default setting, n.
617 If your card is other models, you could pick it
618 on condition that the kernel version is greater than 2.6.19.
619 This function is maintained driver by Nick Cheng. If you have any
620 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
621 To enable this function, choose Y here.
623 source "drivers/scsi/megaraid/Kconfig.megaraid"
624 source "drivers/scsi/mpt2sas/Kconfig"
627 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
628 depends on SCSI && PCI
630 This option enables support for HighPoint RocketRAID 3xxx/4xxx
633 To compile this driver as a module, choose M here; the module
634 will be called hptiop. If unsure, say N.
637 tristate "BusLogic SCSI support"
638 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
640 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
641 Adapters. Consult the SCSI-HOWTO, available from
642 <http://www.tldp.org/docs.html#howto>, and the files
643 <file:Documentation/scsi/BusLogic.txt> and
644 <file:Documentation/scsi/FlashPoint.txt> for more information.
645 Note that support for FlashPoint is only available for 32-bit
648 To compile this driver as a module, choose M here: the
649 module will be called BusLogic.
651 config SCSI_FLASHPOINT
652 bool "FlashPoint support"
653 depends on SCSI_BUSLOGIC && PCI && X86_32
655 This option allows you to add FlashPoint support to the
656 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
657 substantial, so users of MultiMaster Host Adapters may not
661 tristate "VMware PVSCSI driver support"
662 depends on PCI && SCSI && X86
664 This driver supports VMware's para virtualized SCSI HBA.
665 To compile this driver as a module, choose M here: the
666 module will be called vmw_pvscsi.
669 tristate "LibFC module"
673 Fibre Channel library module
676 tristate "LibFCoE module"
679 Library for Fibre Channel over Ethernet module
682 tristate "FCoE module"
686 Fibre Channel over Ethernet module
689 tristate "Cisco FNIC Driver"
690 depends on PCI && X86
693 This is support for the Cisco PCI-Express FCoE HBA.
695 To compile this driver as a module, choose M here and read
696 <file:Documentation/scsi/scsi.txt>.
697 The module will be called fnic.
700 tristate "DMX3191D SCSI support"
701 depends on PCI && SCSI
702 select SCSI_SPI_ATTRS
704 This is support for Domex DMX3191D SCSI Host Adapters.
706 To compile this driver as a module, choose M here: the
707 module will be called dmx3191d.
710 tristate "DTC3180/3280 SCSI support"
711 depends on ISA && SCSI
712 select SCSI_SPI_ATTRS
713 select CHECK_SIGNATURE
715 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
716 the SCSI-HOWTO, available from
717 <http://www.tldp.org/docs.html#howto>, and the file
718 <file:Documentation/scsi/dtc3x80.txt>.
720 To compile this driver as a module, choose M here: the
721 module will be called dtc.
724 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
725 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
727 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
728 ISA and all EISA I/O addresses are probed looking for the "EATA"
729 signature. The addresses of all the PCI SCSI controllers reported
730 by the PCI subsystem are probed as well.
732 You want to read the start of <file:drivers/scsi/eata.c> and the
733 SCSI-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
736 To compile this driver as a module, choose M here: the
737 module will be called eata.
739 config SCSI_EATA_TAGGED_QUEUE
740 bool "enable tagged command queueing"
743 This is a feature of SCSI-2 which improves performance: the host
744 adapter can send several SCSI commands to a device's queue even if
745 previous commands haven't finished yet.
746 This is equivalent to the "eata=tc:y" boot option.
748 config SCSI_EATA_LINKED_COMMANDS
749 bool "enable elevator sorting"
752 This option enables elevator sorting for all probed SCSI disks and
753 CD-ROMs. It definitely reduces the average seek distance when doing
754 random seeks, but this does not necessarily result in a noticeable
755 performance improvement: your mileage may vary...
756 This is equivalent to the "eata=lc:y" boot option.
758 config SCSI_EATA_MAX_TAGS
759 int "maximum number of queued commands"
763 This specifies how many SCSI commands can be maximally queued for
764 each probed SCSI device. You should reduce the default value of 16
765 only if you have disks with buggy or limited tagged command support.
766 Minimum is 2 and maximum is 62. This value is also the window size
767 used by the elevator sorting option above. The effective value used
768 by the driver for each probed SCSI device is reported at boot time.
769 This is equivalent to the "eata=mq:8" boot option.
772 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
773 depends on (ISA || EISA || PCI) && SCSI && BROKEN
775 This driver supports all EATA-PIO protocol compliant SCSI Host
776 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
777 host adapters could also use this driver but are discouraged from
778 doing so, since this driver only supports hard disks and lacks
779 numerous features. You might want to have a look at the SCSI-HOWTO,
780 available from <http://www.tldp.org/docs.html#howto>.
782 To compile this driver as a module, choose M here: the
783 module will be called eata_pio.
785 config SCSI_FUTURE_DOMAIN
786 tristate "Future Domain 16xx SCSI/AHA-2920A support"
787 depends on (ISA || PCI) && SCSI
788 select CHECK_SIGNATURE
790 This is support for Future Domain's 16-bit SCSI host adapters
791 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
792 other adapters based on the Future Domain chipsets (Quantum
793 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
794 It is explained in section 3.7 of the SCSI-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
798 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
799 controller support"). This Future Domain driver works with the older
800 Adaptec AHA-2920A boards with a Future Domain chip on them.
802 To compile this driver as a module, choose M here: the
803 module will be called fdomain.
806 tristate "Future Domain MCS-600/700 SCSI support"
807 depends on MCA_LEGACY && SCSI
809 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
810 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
811 is identical to the MCS 700 and hence also supported by this driver.
812 This driver also supports the Reply SB16/SCSI card (the SCSI part).
813 It supports multiple adapters in the same system.
815 To compile this driver as a module, choose M here: the
816 module will be called fd_mcs.
819 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
820 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
822 Formerly called GDT SCSI Disk Array Controller Support.
824 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
825 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
826 in the kernel source in <file:drivers/scsi/gdth.c> and
827 <file:drivers/scsi/gdth.h>.
829 To compile this driver as a module, choose M here: the
830 module will be called gdth.
832 config SCSI_GENERIC_NCR5380
833 tristate "Generic NCR5380/53c400 SCSI PIO support"
834 depends on ISA && SCSI
835 select SCSI_SPI_ATTRS
837 This is a driver for the old NCR 53c80 series of SCSI controllers
838 on boards using PIO. Most boards such as the Trantor T130 fit this
839 category, along with a large number of ISA 8bit controllers shipped
840 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
841 you should select the specific driver for that card rather than
842 generic 5380 support.
844 It is explained in section 3.8 of the SCSI-HOWTO, available from
845 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
846 of the box, you may have to change some settings in
847 <file:drivers/scsi/g_NCR5380.h>.
849 To compile this driver as a module, choose M here: the
850 module will be called g_NCR5380.
852 config SCSI_GENERIC_NCR5380_MMIO
853 tristate "Generic NCR5380/53c400 SCSI MMIO support"
854 depends on ISA && SCSI
855 select SCSI_SPI_ATTRS
857 This is a driver for the old NCR 53c80 series of SCSI controllers
858 on boards using memory mapped I/O.
859 It is explained in section 3.8 of the SCSI-HOWTO, available from
860 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
861 of the box, you may have to change some settings in
862 <file:drivers/scsi/g_NCR5380.h>.
864 To compile this driver as a module, choose M here: the
865 module will be called g_NCR5380_mmio.
867 config SCSI_GENERIC_NCR53C400
868 bool "Enable NCR53c400 extensions"
869 depends on SCSI_GENERIC_NCR5380
871 This enables certain optimizations for the NCR53c400 SCSI cards.
872 You might as well try it out. Note that this driver will only probe
873 for the Trantor T130B in its default configuration; you might have
874 to pass a command line option to the kernel at boot time if it does
875 not detect your card. See the file
876 <file:Documentation/scsi/g_NCR5380.txt> for details.
879 tristate "IBMMCA SCSI support"
880 depends on MCA && SCSI
882 This is support for the IBM SCSI adapter found in many of the PS/2
883 series computers. These machines have an MCA bus, so you need to
884 answer Y to "MCA support" as well and read
885 <file:Documentation/mca.txt>.
887 If the adapter isn't found during boot (a common problem for models
888 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
889 option, where <pun> is the id of the SCSI subsystem (usually 7, but
890 if that doesn't work check your reference diskette). Owners of
891 model 95 with a LED-matrix-display can in addition activate some
892 activity info like under OS/2, but more informative, by setting
893 'ibmmcascsi=display' as an additional kernel parameter. Try "man
894 bootparam" or see the documentation of your boot loader about how to
895 pass options to the kernel.
897 To compile this driver as a module, choose M here: the
898 module will be called ibmmca.
900 config IBMMCA_SCSI_ORDER_STANDARD
901 bool "Standard SCSI-order"
902 depends on SCSI_IBMMCA
904 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
905 are assigned to the drive letters, starting with the lowest SCSI-id
906 (physical number -- pun) to be drive C:, as seen from DOS and
907 similar operating systems. When looking into papers describing the
908 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
909 The SCSI-standard follows a hardware-hierarchy which says that id 7
910 has the highest priority and id 0 the lowest. Therefore, the host
911 adapters are still today everywhere placed as SCSI-id 7 by default.
912 In the SCSI-standard, the drive letters express the priority of the
913 disk. C: should be the hard disk, or a partition on it, with the
914 highest priority. This must therefore be the disk with the highest
915 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
916 original definition of the SCSI-standard as also industrial- and
917 process-control-machines, like VME-CPUs running under realtime-OSes
918 (e.g. LynxOS, OS9) do.
920 If you like to run Linux on your MCA-machine with the same
921 assignment of hard disks as seen from e.g. DOS or OS/2 on your
922 machine, which is in addition conformant to the SCSI-standard, you
923 must say Y here. This is also necessary for MCA-Linux users who want
924 to keep downward compatibility to older releases of the
925 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
928 If you like to have the lowest SCSI-id assigned as drive C:, as
929 modern SCSI-BIOSes do, which does not conform to the standard, but
930 is widespread and common in the PC-world of today, you must say N
931 here. If unsure, say Y.
933 config IBMMCA_SCSI_DEV_RESET
934 bool "Reset SCSI-devices at boottime"
935 depends on SCSI_IBMMCA
937 By default, SCSI-devices are reset when the machine is powered on.
938 However, some devices exist, like special-control-devices,
939 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
940 not reset when switched on. If you say Y here, each device connected
941 to your SCSI-bus will be issued a reset-command after it has been
942 probed, while the kernel is booting. This may cause problems with
943 more modern devices, like hard disks, which do not appreciate these
944 reset commands, and can cause your system to hang. So say Y only if
945 you know that one of your older devices needs it; N is the safe
949 tristate "IBM ServeRAID support"
950 depends on PCI && SCSI
952 This is support for the IBM ServeRAID hardware RAID controllers.
953 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
954 for more information. If this driver does not work correctly
955 without modification please contact the author by email at
956 <ipslinux@adaptec.com>.
958 To compile this driver as a module, choose M here: the
959 module will be called ips.
962 tristate "IBM Virtual SCSI support"
963 depends on PPC_PSERIES || PPC_ISERIES
964 select SCSI_SRP_ATTRS
965 select VIOPATH if PPC_ISERIES
967 This is the IBM POWER Virtual SCSI Client
969 To compile this driver as a module, choose M here: the
970 module will be called ibmvscsic.
972 config SCSI_IBMVSCSIS
973 tristate "IBM Virtual SCSI Server support"
974 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
976 This is the SRP target driver for IBM pSeries virtual environments.
978 The userspace component needed to initialize the driver and
979 documentation can be found:
981 http://stgt.berlios.de/
983 To compile this driver as a module, choose M here: the
984 module will be called ibmvstgt.
987 tristate "IBM Virtual FC support"
988 depends on PPC_PSERIES && SCSI
991 This is the IBM POWER Virtual FC Client
993 To compile this driver as a module, choose M here: the
994 module will be called ibmvfc.
996 config SCSI_IBMVFC_TRACE
997 bool "enable driver internal trace"
998 depends on SCSI_IBMVFC
1001 If you say Y here, the driver will trace all commands issued
1002 to the adapter. Performance impact is minimal. Trace can be
1003 dumped using /sys/class/scsi_host/hostXX/trace.
1006 tristate "Initio 9100U(W) support"
1007 depends on PCI && SCSI
1009 This is support for the Initio 91XXU(W) SCSI host adapter. Please
1010 read the SCSI-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1013 To compile this driver as a module, choose M here: the
1014 module will be called initio.
1017 tristate "Initio INI-A100U2W support"
1018 depends on PCI && SCSI
1020 This is support for the Initio INI-A100U2W SCSI host adapter.
1021 Please read the SCSI-HOWTO, available from
1022 <http://www.tldp.org/docs.html#howto>.
1024 To compile this driver as a module, choose M here: the
1025 module will be called a100u2w.
1028 tristate "IOMEGA parallel port (ppa - older drives)"
1029 depends on SCSI && PARPORT_PC
1031 This driver supports older versions of IOMEGA's parallel port ZIP
1032 drive (a 100 MB removable media device).
1034 Note that you can say N here if you have the SCSI version of the ZIP
1035 drive: it will be supported automatically if you said Y to the
1036 generic "SCSI disk support", above.
1038 If you have the ZIP Plus drive or a more recent parallel port ZIP
1039 drive (if the supplied cable with the drive is labeled "AutoDetect")
1040 then you should say N here and Y to "IOMEGA parallel port (imm -
1041 newer drives)", below.
1043 For more information about this driver and how to use it you should
1044 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1045 the SCSI-HOWTO, which is available from
1046 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1047 you will still be able to use the parallel port for other tasks,
1048 such as a printer; it is safe to compile both drivers into the
1051 To compile this driver as a module, choose M here: the
1052 module will be called ppa.
1055 tristate "IOMEGA parallel port (imm - newer drives)"
1056 depends on SCSI && PARPORT_PC
1058 This driver supports newer versions of IOMEGA's parallel port ZIP
1059 drive (a 100 MB removable media device).
1061 Note that you can say N here if you have the SCSI version of the ZIP
1062 drive: it will be supported automatically if you said Y to the
1063 generic "SCSI disk support", above.
1065 If you have the ZIP Plus drive or a more recent parallel port ZIP
1066 drive (if the supplied cable with the drive is labeled "AutoDetect")
1067 then you should say Y here; if you have an older ZIP drive, say N
1068 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
1070 For more information about this driver and how to use it you should
1071 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1072 the SCSI-HOWTO, which is available from
1073 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1074 you will still be able to use the parallel port for other tasks,
1075 such as a printer; it is safe to compile both drivers into the
1078 To compile this driver as a module, choose M here: the
1079 module will be called imm.
1081 config SCSI_IZIP_EPP16
1082 bool "ppa/imm option - Use slow (but safe) EPP-16"
1083 depends on SCSI_PPA || SCSI_IMM
1085 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1086 allows them to act as expansion buses that can handle up to 64
1089 Some parallel port chipsets are slower than their motherboard, and
1090 so we have to control the state of the chipset's FIFO queue every
1091 now and then to avoid data loss. This will be done if you say Y
1094 Generally, saying Y is the safe option and slows things down a bit.
1096 config SCSI_IZIP_SLOW_CTR
1097 bool "ppa/imm option - Assume slow parport control register"
1098 depends on SCSI_PPA || SCSI_IMM
1100 Some parallel ports are known to have excessive delays between
1101 changing the parallel port control register and good data being
1102 available on the parallel port data/status register. This option
1103 forces a small delay (1.0 usec to be exact) after changing the
1104 control register to let things settle out. Enabling this option may
1105 result in a big drop in performance but some very old parallel ports
1106 (found in 386 vintage machines) will not work properly.
1108 Generally, saying N is fine.
1110 config SCSI_NCR53C406A
1111 tristate "NCR53c406a SCSI support"
1112 depends on ISA && SCSI
1114 This is support for the NCR53c406a SCSI host adapter. For user
1115 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1116 in the kernel source. Also read the SCSI-HOWTO, available from
1117 <http://www.tldp.org/docs.html#howto>.
1119 To compile this driver as a module, choose M here: the
1120 module will be called NCR53c406.
1122 config SCSI_NCR_D700
1123 tristate "NCR Dual 700 MCA SCSI support"
1124 depends on MCA && SCSI
1125 select SCSI_SPI_ATTRS
1127 This is a driver for the MicroChannel Dual 700 card produced by
1128 NCR and commonly used in 345x/35xx/4100 class machines. It always
1129 tries to negotiate sync and uses tag command queueing.
1131 Unless you have an NCR manufactured machine, the chances are that
1132 you do not have this SCSI card, so say N.
1135 tristate "HP Lasi SCSI support for 53c700/710"
1136 depends on GSC && SCSI
1137 select SCSI_SPI_ATTRS
1139 This is a driver for the SCSI controller in the Lasi chip found in
1140 many PA-RISC workstations & servers. If you do not know whether you
1141 have a Lasi chip, it is safe to say "Y" here.
1143 config SCSI_SNI_53C710
1144 tristate "SNI RM SCSI support for 53c710"
1145 depends on SNI_RM && SCSI
1146 select SCSI_SPI_ATTRS
1147 select 53C700_LE_ON_BE
1149 This is a driver for the onboard SCSI controller found in older
1150 SNI RM workstations & servers.
1152 config 53C700_LE_ON_BE
1154 depends on SCSI_LASI700
1158 tristate "Promise SuperTrak EX Series support"
1159 depends on PCI && SCSI
1161 This driver supports Promise SuperTrak EX series storage controllers.
1163 Promise provides Linux RAID configuration utility for these
1164 controllers. Please visit <http://www.promise.com> to download.
1166 To compile this driver as a module, choose M here: the
1167 module will be called stex.
1169 config 53C700_BE_BUS
1171 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1174 config SCSI_SYM53C8XX_2
1175 tristate "SYM53C8XX Version 2 SCSI support"
1176 depends on PCI && SCSI
1177 select SCSI_SPI_ATTRS
1179 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1180 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1181 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1182 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1183 controllers; you need to use the Fusion MPT driver for that.
1185 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1188 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1189 int "DMA addressing mode"
1190 depends on SCSI_SYM53C8XX_2
1193 This option only applies to PCI-SCSI chips that are PCI DAC
1194 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1196 When set to 0, the driver will program the chip to only perform
1197 32-bit DMA. When set to 1, the chip will be able to perform DMA
1198 to addresses up to 1TB. When set to 2, the driver supports the
1199 full 64-bit DMA address range, but can only address 16 segments
1200 of 4 GB each. This limits the total addressable range to 64 GB.
1202 Most machines with less than 4GB of memory should use a setting
1203 of 0 for best performance. If your machine has 4GB of memory
1204 or more, you should set this option to 1 (the default).
1206 The still experimental value 2 (64 bit DMA addressing with 16
1207 x 4GB segments limitation) can be used on systems that require
1208 PCI address bits past bit 39 to be set for the addressing of
1209 memory using PCI DAC cycles.
1211 config SCSI_SYM53C8XX_DEFAULT_TAGS
1212 int "Default tagged command queue depth"
1213 depends on SCSI_SYM53C8XX_2
1216 This is the default value of the command queue depth the
1217 driver will announce to the generic SCSI layer for devices
1218 that support tagged command queueing. This value can be changed
1219 from the boot command line. This is a soft limit that cannot
1220 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1222 config SCSI_SYM53C8XX_MAX_TAGS
1223 int "Maximum number of queued commands"
1224 depends on SCSI_SYM53C8XX_2
1227 This option allows you to specify the maximum number of commands
1228 that can be queued to any device, when tagged command queuing is
1229 possible. The driver supports up to 256 queued commands per device.
1230 This value is used as a compiled-in hard limit.
1232 config SCSI_SYM53C8XX_MMIO
1233 bool "Use memory mapped IO"
1234 depends on SCSI_SYM53C8XX_2
1237 Memory mapped IO is faster than Port IO. Most people should
1238 answer Y here, but some machines may have problems. If you have
1239 to answer N here, please report the problem to the maintainer.
1242 tristate "IBM Power Linux RAID adapter support"
1243 depends on PCI && SCSI && ATA
1246 This driver supports the IBM Power Linux family RAID adapters.
1247 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1248 as IBM iSeries 5702, 5703, 5709, and 570A.
1250 config SCSI_IPR_TRACE
1251 bool "enable driver internal trace"
1255 If you say Y here, the driver will trace all commands issued
1256 to the adapter. Performance impact is minimal. Trace can be
1257 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1259 config SCSI_IPR_DUMP
1260 bool "enable adapter dump support"
1264 If you say Y here, the driver will support adapter crash dump.
1265 If you enable this support, the iprdump daemon can be used
1266 to capture adapter failure analysis information.
1269 tristate "Zalon SCSI support"
1270 depends on GSC && SCSI
1271 select SCSI_SPI_ATTRS
1273 The Zalon is a GSC/HSC bus interface chip that sits between the
1274 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1275 C110, J200, J210 and some D, K & R-class machines. It's also
1276 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1277 Say Y here if you have one of these machines or cards.
1279 config SCSI_NCR_Q720
1280 tristate "NCR Quad 720 MCA SCSI support"
1281 depends on MCA && SCSI
1282 select SCSI_SPI_ATTRS
1284 This is a driver for the MicroChannel Quad 720 card produced by
1285 NCR and commonly used in 345x/35xx/4100 class machines. It always
1286 tries to negotiate sync and uses tag command queueing.
1288 Unless you have an NCR manufactured machine, the chances are that
1289 you do not have this SCSI card, so say N.
1291 config SCSI_NCR53C8XX_DEFAULT_TAGS
1292 int "default tagged command queue depth"
1293 depends on SCSI_ZALON || SCSI_NCR_Q720
1296 "Tagged command queuing" is a feature of SCSI-2 which improves
1297 performance: the host adapter can send several SCSI commands to a
1298 device's queue even if previous commands haven't finished yet.
1299 Because the device is intelligent, it can optimize its operations
1300 (like head positioning) based on its own request queue. Some SCSI
1301 devices don't implement this properly; if you want to disable this
1302 feature, enter 0 or 1 here (it doesn't matter which).
1304 The default value is 8 and should be supported by most hard disks.
1305 This value can be overridden from the boot command line using the
1306 'tags' option as follows (example):
1307 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1308 4, set queue depth to 16 for target 2 and target 3 on controller 0
1309 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1311 The normal answer therefore is to go with the default 8 and to use
1312 a boot command line option for devices that need to use a different
1313 command queue depth.
1315 There is no safe option other than using good SCSI devices.
1317 config SCSI_NCR53C8XX_MAX_TAGS
1318 int "maximum number of queued commands"
1319 depends on SCSI_ZALON || SCSI_NCR_Q720
1322 This option allows you to specify the maximum number of commands
1323 that can be queued to any device, when tagged command queuing is
1324 possible. The default value is 32. Minimum is 2, maximum is 64.
1325 Modern hard disks are able to support 64 tags and even more, but
1326 do not seem to be faster when more than 32 tags are being used.
1328 So, the normal answer here is to go with the default value 32 unless
1329 you are using very large hard disks with large cache (>= 1 MB) that
1330 are able to take advantage of more than 32 tagged commands.
1332 There is no safe option and the default answer is recommended.
1334 config SCSI_NCR53C8XX_SYNC
1335 int "synchronous transfers frequency in MHz"
1336 depends on SCSI_ZALON || SCSI_NCR_Q720
1339 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1340 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1341 are respectively the maximum data transfer rates in mega-transfers
1342 per second for each class. For example, a FAST-20 Wide 16 device is
1343 able to transfer data at 20 million 16 bit packets per second for a
1344 total rate of 40 MB/s.
1346 You may specify 0 if you want to only use asynchronous data
1347 transfers. This is the safest and slowest option. Otherwise, specify
1348 a value between 5 and 80, depending on the capability of your SCSI
1349 controller. The higher the number, the faster the data transfer.
1350 Note that 80 should normally be ok since the driver decreases the
1351 value automatically according to the controller's capabilities.
1353 Your answer to this question is ignored for controllers with NVRAM,
1354 since the driver will get this information from the user set-up. It
1355 also can be overridden using a boot setup option, as follows
1356 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1357 for FAST-20 synchronous data transfer (20 mega-transfers per
1360 The normal answer therefore is not to go with the default but to
1361 select the maximum value 80 allowing the driver to use the maximum
1362 value supported by each controller. If this causes problems with
1363 your SCSI devices, you should come back and decrease the value.
1365 There is no safe option other than using good cabling, right
1366 terminations and SCSI conformant devices.
1368 config SCSI_NCR53C8XX_NO_DISCONNECT
1369 bool "not allow targets to disconnect"
1370 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1372 This option is only provided for safety if you suspect some SCSI
1373 device of yours to not support properly the target-disconnect
1374 feature. In that case, you would say Y here. In general however, to
1375 not allow targets to disconnect is not reasonable if there is more
1376 than 1 device on a SCSI bus. The normal answer therefore is N.
1379 tristate "PAS16 SCSI support"
1380 depends on ISA && SCSI
1381 select SCSI_SPI_ATTRS
1383 This is support for a SCSI host adapter. It is explained in section
1384 3.10 of the SCSI-HOWTO, available from
1385 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1386 of the box, you may have to change some settings in
1387 <file:drivers/scsi/pas16.h>.
1389 To compile this driver as a module, choose M here: the
1390 module will be called pas16.
1392 config SCSI_QLOGIC_FAS
1393 tristate "Qlogic FAS SCSI support"
1394 depends on ISA && SCSI
1396 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1397 FastSCSI! cards as well as any other card based on the FASXX chip
1398 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1400 This driver does NOT support the PCI versions of these cards. The
1401 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1402 SCSI support"), below.
1404 Information about this driver is contained in
1405 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1406 SCSI-HOWTO, available from
1407 <http://www.tldp.org/docs.html#howto>.
1409 To compile this driver as a module, choose M here: the
1410 module will be called qlogicfas.
1412 config SCSI_QLOGIC_1280
1413 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1414 depends on PCI && SCSI
1416 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1418 To compile this driver as a module, choose M here: the
1419 module will be called qla1280.
1421 config SCSI_QLOGICPTI
1422 tristate "PTI Qlogic, ISP Driver"
1423 depends on SBUS && SCSI
1425 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1426 controllers are known under Solaris as qpti and in the openprom as
1427 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1428 driven by a different driver.
1430 To compile this driver as a module, choose M here: the
1431 module will be called qlogicpti.
1433 source "drivers/scsi/qla2xxx/Kconfig"
1434 source "drivers/scsi/qla4xxx/Kconfig"
1437 tristate "Emulex LightPulse Fibre Channel Support"
1438 depends on PCI && SCSI
1439 select SCSI_FC_ATTRS
1441 This lpfc driver supports the Emulex LightPulse
1442 Family of Fibre Channel PCI host adapters.
1444 config SCSI_LPFC_DEBUG_FS
1445 bool "Emulex LightPulse Fibre Channel debugfs Support"
1446 depends on SCSI_LPFC && DEBUG_FS
1448 This makes debugging information from the lpfc driver
1449 available via the debugfs filesystem.
1452 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1453 depends on (EISA || MCA) && SCSI
1454 select SCSI_SPI_ATTRS
1456 This driver is for NCR53c710 based SCSI host adapters.
1458 It currently supports Compaq EISA cards and NCR MCA cards
1460 config SCSI_SYM53C416
1461 tristate "Symbios 53c416 SCSI support"
1462 depends on ISA && SCSI
1464 This is support for the sym53c416 SCSI host adapter, the SCSI
1465 adapter that comes with some HP scanners. This driver requires that
1466 the sym53c416 is configured first using some sort of PnP
1467 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1468 are using isapnp then you need to compile this driver as a module
1469 and then load it using insmod after isapnp has run. The parameters
1470 of the configured card(s) should be passed to the driver. The format
1473 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1475 To compile this driver as a module, choose M here: the
1476 module will be called sym53c416.
1479 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1480 depends on PCI && SCSI && EXPERIMENTAL
1482 This driver supports PCI SCSI host adapters based on the ASIC
1483 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1485 This driver works, but is still in experimental status. So better
1486 have a bootable disk and a backup in case of emergency.
1488 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1490 To compile this driver as a module, choose M here: the
1491 module will be called dc395x.
1494 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1495 depends on PCI && SCSI
1497 This driver supports PCI SCSI host adapters based on the Am53C974A
1498 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1499 PCscsi/PCnet (Am53/79C974) solutions.
1501 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1503 Note that this driver does NOT support Tekram DC390W/U/F, which are
1504 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1506 To compile this driver as a module, choose M here: the
1507 module will be called tmscsim.
1510 tristate "Trantor T128/T128F/T228 SCSI support"
1511 depends on ISA && SCSI
1512 select SCSI_SPI_ATTRS
1513 select CHECK_SIGNATURE
1515 This is support for a SCSI host adapter. It is explained in section
1516 3.11 of the SCSI-HOWTO, available from
1517 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1518 of the box, you may have to change some settings in
1519 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1520 Adaptec, and some former Trantor products are being sold under the
1523 To compile this driver as a module, choose M here: the
1524 module will be called t128.
1527 tristate "UltraStor 14F/34F support"
1528 depends on ISA && SCSI && ISA_DMA_API
1530 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1531 The source at <file:drivers/scsi/u14-34f.c> contains some
1532 information about this hardware. If the driver doesn't work out of
1533 the box, you may have to change some settings in
1534 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1535 <http://www.tldp.org/docs.html#howto>. Note that there is also
1536 another driver for the same hardware: "UltraStor SCSI support",
1537 below. You should say Y to both only if you want 24F support as
1540 To compile this driver as a module, choose M here: the
1541 module will be called u14-34f.
1543 config SCSI_U14_34F_TAGGED_QUEUE
1544 bool "enable tagged command queueing"
1545 depends on SCSI_U14_34F
1547 This is a feature of SCSI-2 which improves performance: the host
1548 adapter can send several SCSI commands to a device's queue even if
1549 previous commands haven't finished yet.
1550 This is equivalent to the "u14-34f=tc:y" boot option.
1552 config SCSI_U14_34F_LINKED_COMMANDS
1553 bool "enable elevator sorting"
1554 depends on SCSI_U14_34F
1556 This option enables elevator sorting for all probed SCSI disks and
1557 CD-ROMs. It definitely reduces the average seek distance when doing
1558 random seeks, but this does not necessarily result in a noticeable
1559 performance improvement: your mileage may vary...
1560 This is equivalent to the "u14-34f=lc:y" boot option.
1562 config SCSI_U14_34F_MAX_TAGS
1563 int "maximum number of queued commands"
1564 depends on SCSI_U14_34F
1567 This specifies how many SCSI commands can be maximally queued for
1568 each probed SCSI device. You should reduce the default value of 8
1569 only if you have disks with buggy or limited tagged command support.
1570 Minimum is 2 and maximum is 14. This value is also the window size
1571 used by the elevator sorting option above. The effective value used
1572 by the driver for each probed SCSI device is reported at boot time.
1573 This is equivalent to the "u14-34f=mq:8" boot option.
1575 config SCSI_ULTRASTOR
1576 tristate "UltraStor SCSI support"
1577 depends on X86 && ISA && SCSI
1579 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1580 adapter family. This driver is explained in section 3.12 of the
1581 SCSI-HOWTO, available from
1582 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1583 of the box, you may have to change some settings in
1584 <file:drivers/scsi/ultrastor.h>.
1586 Note that there is also another driver for the same hardware:
1587 "UltraStor 14F/34F support", above.
1589 To compile this driver as a module, choose M here: the
1590 module will be called ultrastor.
1593 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1594 depends on PCI && SCSI && !64BIT
1596 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1597 SCSI host adapter. Please read the SCSI-HOWTO, available from
1598 <http://www.tldp.org/docs.html#howto>.
1600 To compile this driver as a module, choose M here: the
1601 module will be called nsp32.
1604 tristate "SCSI debugging host simulator"
1608 This is a host adapter simulator that can simulate multiple hosts
1609 each with multiple dummy SCSI devices (disks). It defaults to one
1610 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1611 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1612 dummy disks are simulated, they share the same kernel RAM for
1613 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1614 information. This driver is primarily of use to those testing the
1615 SCSI and block subsystems. If unsure, say N.
1618 tristate "MESH (Power Mac internal SCSI) support"
1619 depends on PPC32 && PPC_PMAC && SCSI
1621 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1622 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1623 other Power Macintoshes do). Say Y to include support for this SCSI
1626 To compile this driver as a module, choose M here: the
1627 module will be called mesh.
1629 config SCSI_MESH_SYNC_RATE
1630 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1631 depends on SCSI_MESH
1634 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1635 drives a bus which is entirely internal to the machine (such as the
1636 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1637 operation at up to 10 MB/s. On machines where the SCSI bus
1638 controlled by the MESH can have external devices connected, it is
1639 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1640 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1641 to disable synchronous operation.
1643 config SCSI_MESH_RESET_DELAY_MS
1644 int "initial bus reset delay (ms) (0 = no reset)"
1645 depends on SCSI_MESH
1648 config SCSI_MAC53C94
1649 tristate "53C94 (Power Mac external SCSI) support"
1650 depends on PPC32 && PPC_PMAC && SCSI
1652 On Power Macintoshes (and clones) with two SCSI buses, the external
1653 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1654 machines which only have one SCSI bus, such as the 7200, also use
1655 the 53C94. Say Y to include support for the 53C94.
1657 To compile this driver as a module, choose M here: the
1658 module will be called mac53c94.
1660 source "drivers/scsi/arm/Kconfig"
1663 bool "MIPS JAZZ FAS216 SCSI support"
1664 depends on MACH_JAZZ && SCSI
1665 select SCSI_SPI_ATTRS
1667 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1668 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1672 tristate "A3000 WD33C93A support"
1673 depends on AMIGA && SCSI
1675 If you have an Amiga 3000 and have SCSI devices connected to the
1676 built-in SCSI controller, say Y. Otherwise, say N.
1678 To compile this driver as a module, choose M here: the
1679 module will be called a3000.
1682 tristate "A2091/A590 WD33C93A support"
1683 depends on ZORRO && SCSI
1685 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1688 To compile this driver as a module, choose M here: the
1689 module will be called a2091.
1692 tristate "GVP Series II WD33C93A support"
1693 depends on ZORRO && SCSI
1695 If you have a Great Valley Products Series II SCSI controller,
1696 answer Y. Also say Y if you have a later model of GVP SCSI
1697 controller (such as the GVP A4008 or a Combo board). Otherwise,
1698 answer N. This driver does NOT work for the T-Rex series of
1699 accelerators from TekMagic and GVP-M.
1701 To compile this driver as a module, choose M here: the
1702 module will be called gvp11.
1705 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1706 depends on AMIGA && SCSI && EXPERIMENTAL
1707 select SCSI_SPI_ATTRS
1709 If you have an Amiga 4000T and have SCSI devices connected to the
1710 built-in SCSI controller, say Y. Otherwise, say N.
1712 To compile this driver as a module, choose M here: the
1713 module will be called a4000t.
1715 config SCSI_ZORRO7XX
1716 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1717 depends on ZORRO && SCSI && EXPERIMENTAL
1718 select SCSI_SPI_ATTRS
1720 Support for various NCR53c710-based SCSI controllers on Zorro
1721 expansion boards for the Amiga.
1723 - the Amiga 4091 Zorro III SCSI-2 controller,
1724 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1726 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1727 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1728 accelerator card for the Amiga 1200,
1729 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1732 tristate "Atari native SCSI support"
1733 depends on ATARI && SCSI
1734 select SCSI_SPI_ATTRS
1737 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1738 Falcon, ...) say Y to get it supported. Of course also, if you have
1739 a compatible SCSI controller (e.g. for Medusa).
1741 To compile this driver as a module, choose M here: the
1742 module will be called atari_scsi.
1744 This driver supports both styles of NCR integration into the
1745 system: the TT style (separate DMA), and the Falcon style (via
1746 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1747 in the Hades (without DMA).
1749 config ATARI_SCSI_TOSHIBA_DELAY
1750 bool "Long delays for Toshiba CD-ROMs"
1751 depends on ATARI_SCSI
1753 This option increases the delay after a SCSI arbitration to
1754 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1755 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1756 would impact performance a bit, so say N.
1758 config ATARI_SCSI_RESET_BOOT
1759 bool "Reset SCSI-devices at boottime"
1760 depends on ATARI_SCSI
1762 Reset the devices on your Atari whenever it boots. This makes the
1763 boot process fractionally longer but may assist recovery from errors
1764 that leave the devices with SCSI operations partway completed.
1767 bool "Macintosh NCR5380 SCSI"
1768 depends on MAC && SCSI=y
1769 select SCSI_SPI_ATTRS
1771 This is the NCR 5380 SCSI controller included on most of the 68030
1772 based Macintoshes. If you have one of these say Y and read the
1773 SCSI-HOWTO, available from
1774 <http://www.tldp.org/docs.html#howto>.
1777 tristate "Macintosh NCR53c9[46] SCSI"
1778 depends on MAC && SCSI
1779 select SCSI_SPI_ATTRS
1781 This is the NCR 53c9x SCSI controller found on most of the 68040
1784 To compile this driver as a module, choose M here: the module
1785 will be called mac_esp.
1788 bool "WD33C93 SCSI driver for MVME147"
1789 depends on MVME147 && SCSI=y
1790 select SCSI_SPI_ATTRS
1792 Support for the on-board SCSI controller on the Motorola MVME147
1793 single-board computer.
1796 tristate "NCR53C710 SCSI driver for MVME16x"
1797 depends on MVME16x && SCSI
1798 select SCSI_SPI_ATTRS
1800 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1801 SCSI controller chip. Almost everyone using one of these boards
1802 will want to say Y to this question.
1804 config BVME6000_SCSI
1805 tristate "NCR53C710 SCSI driver for BVME6000"
1806 depends on BVME6000 && SCSI
1807 select SCSI_SPI_ATTRS
1809 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1810 SCSI controller chip. Almost everyone using one of these boards
1811 will want to say Y to this question.
1814 tristate "Sun3 NCR5380 SCSI"
1815 depends on SUN3 && SCSI
1816 select SCSI_SPI_ATTRS
1818 This option will enable support for the OBIO (onboard io) NCR5380
1819 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1820 "Sun3" type VME scsi controllers also based on the NCR5380.
1821 General Linux information on the Sun 3 series (now discontinued)
1822 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1825 bool "Sun3x ESP SCSI"
1826 depends on SUN3X && SCSI=y
1827 select SCSI_SPI_ATTRS
1829 The ESP was an on-board SCSI controller used on Sun 3/80
1830 machines. Say Y here to compile in support for it.
1833 tristate "Sparc ESP Scsi Driver"
1834 depends on SBUS && SCSI
1835 select SCSI_SPI_ATTRS
1837 This is the driver for the Sun ESP SCSI host adapter. The ESP
1838 chipset is present in most SPARC SBUS-based computers and
1839 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1840 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1842 To compile this driver as a module, choose M here: the
1843 module will be called sun_esp.
1846 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1847 depends on S390 && QDIO && SCSI
1848 select SCSI_FC_ATTRS
1850 If you want to access SCSI devices attached to your IBM eServer
1851 zSeries by means of Fibre Channel interfaces say Y.
1852 For details please refer to the documentation provided by IBM at
1853 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1855 This driver is also available as a module. This module will be
1856 called zfcp. If you want to compile it as a module, say M here
1857 and read <file:Documentation/kbuild/modules.txt>.
1860 tristate "T10 DIF/DIX support for the zfcp driver (EXPERIMENTAL)"
1861 depends on ZFCP && EXPERIMENTAL
1864 tristate "PMC SIERRA Linux MaxRAID adapter support"
1865 depends on PCI && SCSI && NET
1867 This driver supports the PMC SIERRA MaxRAID adapters.
1870 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1871 depends on PCI && SCSI
1872 select SCSI_SAS_LIBSAS
1874 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1875 based host adapters.
1878 tristate "SCSI RDMA Protocol helper library"
1879 depends on SCSI && PCI
1882 If you wish to use SRP target drivers, say Y.
1884 To compile this driver as a module, choose M here: the
1885 module will be called libsrp.
1888 tristate "Brocade BFA Fibre Channel Support"
1889 depends on PCI && SCSI
1890 select SCSI_FC_ATTRS
1892 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1894 To compile this driver as a module, choose M here. The module will
1897 endif # SCSI_LOWLEVEL
1899 source "drivers/scsi/pcmcia/Kconfig"
1901 source "drivers/scsi/device_handler/Kconfig"
1903 source "drivers/scsi/osd/Kconfig"