1 menu "SCSI device support"
4 tristate "RAID Transport Class"
11 tristate "SCSI device support"
13 select SCSI_DMA if HAS_DMA
15 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
16 any other SCSI device under Linux, say Y and make sure that you know
17 the name of your SCSI host adapter (the card inside your computer
18 that "speaks" the SCSI protocol, also called SCSI controller),
19 because you will be asked for it.
21 You also need to say Y here if you have a device which speaks
22 the SCSI protocol. Examples of this include the parallel port
23 version of the IOMEGA ZIP drive, USB storage devices, Fibre
24 Channel, and FireWire storage.
26 To compile this driver as a module, choose M here and read
27 <file:Documentation/scsi/scsi.txt>.
28 The module will be called scsi_mod.
30 However, do not compile this as a module if your root file system
31 (the one containing the directory /) is located on a SCSI device.
38 tristate "SCSI target support"
39 depends on SCSI && EXPERIMENTAL
41 If you want to use SCSI target mode drivers enable this option.
42 If you choose M, the module will be called scsi_tgt.
50 bool "legacy /proc/scsi/ support"
51 depends on SCSI && PROC_FS
54 This option enables support for the various files in
55 /proc/scsi. In Linux 2.6 this has been superseded by
56 files in sysfs but many legacy applications rely on this.
60 comment "SCSI support type (disk, tape, CD-ROM)"
64 tristate "SCSI disk support"
66 select CRC_T10DIF if BLK_DEV_INTEGRITY
68 If you want to use SCSI hard disks, Fibre Channel disks,
69 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
70 USB storage or the SCSI or parallel port version of
71 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
72 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
73 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
76 To compile this driver as a module, choose M here and read
77 <file:Documentation/scsi/scsi.txt>.
78 The module will be called sd_mod.
80 Do not compile this driver as a module if your root file system
81 (the one containing the directory /) is located on a SCSI disk.
82 In this case, do not compile the driver for your SCSI host adapter
83 (below) as a module either.
86 tristate "SCSI tape support"
89 If you want to use a SCSI tape drive under Linux, say Y and read the
90 SCSI-HOWTO, available from
91 <http://www.tldp.org/docs.html#howto>, and
92 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
95 To compile this driver as a module, choose M here and read
96 <file:Documentation/scsi/scsi.txt>. The module will be called st.
99 tristate "SCSI OnStream SC-x0 tape support"
102 The OnStream SC-x0 SCSI tape drives cannot be driven by the
103 standard st driver, but instead need this special osst driver and
104 use the /dev/osstX char device nodes (major 206). Via usb-storage,
105 you may be able to drive the USB-x0 and DI-x0 drives as well.
106 Note that there is also a second generation of OnStream
107 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
108 tapes (QIC-157) and can be driven by the standard driver st.
109 For more information, you may have a look at the SCSI-HOWTO
110 <http://www.tldp.org/docs.html#howto> and
111 <file:Documentation/scsi/osst.txt> in the kernel source.
112 More info on the OnStream driver may be found on
113 <http://linux1.onstream.nl/test/>
114 Please also have a look at the standard st docu, as most of it
115 applies to osst as well.
117 To compile this driver as a module, choose M here and read
118 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
121 tristate "SCSI CDROM support"
124 If you want to use a SCSI or FireWire CD-ROM under Linux,
125 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
126 <http://www.tldp.org/docs.html#howto>. Also make sure to say
127 Y or M to "ISO 9660 CD-ROM file system support" later.
129 To compile this driver as a module, choose M here and read
130 <file:Documentation/scsi/scsi.txt>.
131 The module will be called sr_mod.
133 config BLK_DEV_SR_VENDOR
134 bool "Enable vendor-specific extensions (for SCSI CDROM)"
135 depends on BLK_DEV_SR
137 This enables the usage of vendor specific SCSI commands. This is
138 required to support multisession CDs with old NEC/TOSHIBA cdrom
139 drives (and HP Writers). If you have such a drive and get the first
140 session only, try saying Y here; everybody else says N.
143 tristate "SCSI generic support"
146 If you want to use SCSI scanners, synthesizers or CD-writers or just
147 about anything having "SCSI" in its name other than hard disks,
148 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
149 directly, so you need some additional software which knows how to
150 talk to these devices using the SCSI protocol:
152 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
153 writer software look at Cdrtools
154 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
155 and for burning a "disk at once": CDRDAO
156 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
157 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
158 For other devices, it's possible that you'll have to write the
159 driver software yourself. Please read the file
160 <file:Documentation/scsi/scsi-generic.txt> for more information.
162 To compile this driver as a module, choose M here and read
163 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
168 tristate "SCSI media changer support"
171 This is a driver for SCSI media changers. Most common devices are
172 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
173 don't need this for those tiny 6-slot cdrom changers. Media
174 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
175 If you have such hardware and want to use it with linux, say Y
176 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
178 If you want to compile this as a module ( = code which can be
179 inserted in and removed from the running kernel whenever you want),
180 say M here and read <file:Documentation/kbuild/modules.txt> and
181 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
184 config SCSI_ENCLOSURE
185 tristate "SCSI Enclosure Support"
186 depends on SCSI && ENCLOSURE_SERVICES
188 Enclosures are devices sitting on or in SCSI backplanes that
189 manage devices. If you have a disk cage, the chances are that
190 it has an enclosure device. Selecting this option will just allow
191 certain enclosure conditions to be reported and is not required.
193 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
196 config SCSI_MULTI_LUN
197 bool "Probe all LUNs on each SCSI device"
200 If you have a SCSI device that supports more than one LUN (Logical
201 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
202 can say Y here to force the SCSI driver to probe for multiple LUNs.
203 A SCSI device with multiple LUNs acts logically like multiple SCSI
204 devices. The vast majority of SCSI devices have only one LUN, and
205 so most people can say N here. The max_luns boot/module parameter
206 allows to override this setting.
208 config SCSI_CONSTANTS
209 bool "Verbose SCSI error reporting (kernel size +=12K)"
212 The error messages regarding your SCSI hardware will be easier to
213 understand if you say Y here; it will enlarge your kernel by about
214 12 KB. If in doubt, say Y.
217 bool "SCSI logging facility"
220 This turns on a logging facility that can be used to debug a number
221 of SCSI related problems.
223 If you say Y here, no logging output will appear by default, but you
224 can enable logging by saying Y to "/proc file system support" and
225 "Sysctl support" below and executing the command
227 echo <bitmask> > /proc/sys/dev/scsi/logging_level
229 where <bitmask> is a four byte value representing the logging type
230 and logging level for each type of logging selected.
232 There are a number of logging types and you can find them in the
233 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
234 are also described in that file and they determine the verbosity of
235 the logging for each logging type.
237 If you say N here, it may be harder to track down some types of SCSI
238 problems. If you say Y here your kernel will be somewhat larger, but
239 there should be no noticeable performance impact as long as you have
242 config SCSI_SCAN_ASYNC
243 bool "Asynchronous SCSI scanning"
246 The SCSI subsystem can probe for devices while the rest of the
247 system continues booting, and even probe devices on different
248 busses in parallel, leading to a significant speed-up.
250 If you have built SCSI as modules, enabling this option can
251 be a problem as the devices may not have been found by the
252 time your system expects them to have been. You can load the
253 scsi_wait_scan module to ensure that all scans have completed.
254 If you build your SCSI drivers into the kernel, then everything
255 will work fine if you say Y here.
257 You can override this choice by specifying "scsi_mod.scan=sync"
258 or async on the kernel's command line.
260 config SCSI_WAIT_SCAN
266 menu "SCSI Transports"
269 config SCSI_SPI_ATTRS
270 tristate "Parallel SCSI (SPI) Transport Attributes"
273 If you wish to export transport-specific information about
274 each attached SCSI device to sysfs, say Y. Otherwise, say N.
277 tristate "FiberChannel Transport Attributes"
281 If you wish to export transport-specific information about
282 each attached FiberChannel device to sysfs, say Y.
285 config SCSI_FC_TGT_ATTRS
286 bool "SCSI target support for FiberChannel Transport Attributes"
287 depends on SCSI_FC_ATTRS
288 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
290 If you want to use SCSI target mode drivers enable this option.
292 config SCSI_ISCSI_ATTRS
293 tristate "iSCSI Transport Attributes"
294 depends on SCSI && NET
296 If you wish to export transport-specific information about
297 each attached iSCSI device to sysfs, say Y.
300 config SCSI_SAS_ATTRS
301 tristate "SAS Transport Attributes"
302 depends on SCSI && BLK_DEV_BSG
304 If you wish to export transport-specific information about
305 each attached SAS device to sysfs, say Y.
307 source "drivers/scsi/libsas/Kconfig"
309 config SCSI_SRP_ATTRS
310 tristate "SRP Transport Attributes"
313 If you wish to export transport-specific information about
314 each attached SRP device to sysfs, say Y.
316 config SCSI_SRP_TGT_ATTRS
317 bool "SCSI target support for SRP Transport Attributes"
318 depends on SCSI_SRP_ATTRS
319 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
321 If you want to use SCSI target mode drivers enable this option.
325 menuconfig SCSI_LOWLEVEL
326 bool "SCSI low-level drivers"
330 if SCSI_LOWLEVEL && SCSI
333 tristate "iSCSI Initiator over TCP/IP"
334 depends on SCSI && INET
338 select SCSI_ISCSI_ATTRS
340 The iSCSI Driver provides a host with the ability to access storage
341 through an IP network. The driver uses the iSCSI protocol to transport
342 SCSI requests and responses over a TCP/IP network between the host
343 (the "initiator") and "targets". Architecturally, the iSCSI driver
344 combines with the host's TCP/IP stack, network drivers, and Network
345 Interface Card (NIC) to provide the same functions as a SCSI or a
346 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
348 To compile this driver as a module, choose M here: the
349 module will be called iscsi_tcp.
351 The userspace component needed to initialize the driver, documentation,
352 and sample configuration files can be found here:
354 http://open-iscsi.org
356 source "drivers/scsi/cxgb3i/Kconfig"
359 tristate "SGI WD93C93 SCSI Driver"
360 depends on SGI_HAS_WD93 && SCSI
362 If you have a Western Digital WD93 SCSI controller on
363 an SGI MIPS system, say Y. Otherwise, say N.
365 config BLK_DEV_3W_XXXX_RAID
366 tristate "3ware 5/6/7/8xxx ATA-RAID support"
367 depends on PCI && SCSI
369 3ware is the only hardware ATA-Raid product in Linux to date.
370 This card is 2,4, or 8 channel master mode support only.
371 SCSI support required!!!
373 <http://www.3ware.com/>
375 Please read the comments at the top of
376 <file:drivers/scsi/3w-xxxx.c>.
379 tristate "3ware 9xxx SATA-RAID support"
380 depends on PCI && SCSI
382 This driver supports the 9000 series 3ware SATA-RAID cards.
384 <http://www.amcc.com>
386 Please read the comments at the top of
387 <file:drivers/scsi/3w-9xxx.c>.
389 config SCSI_7000FASST
390 tristate "7000FASST SCSI support"
391 depends on ISA && SCSI && ISA_DMA_API
392 select CHECK_SIGNATURE
394 This driver supports the Western Digital 7000 SCSI host adapter
395 family. Some information is in the source:
396 <file:drivers/scsi/wd7000.c>.
398 To compile this driver as a module, choose M here: the
399 module will be called wd7000.
402 tristate "ACARD SCSI support"
403 depends on PCI && SCSI
405 This driver supports the ACARD SCSI host adapter.
406 Support Chip <ATP870 ATP876 ATP880 ATP885>
407 To compile this driver as a module, choose M here: the
408 module will be called atp870u.
411 tristate "Adaptec AHA152X/2825 support"
412 depends on ISA && SCSI && !64BIT
413 select SCSI_SPI_ATTRS
414 select CHECK_SIGNATURE
416 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
417 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
418 must be manually specified in this case.
420 It is explained in section 3.3 of the SCSI-HOWTO, available from
421 <http://www.tldp.org/docs.html#howto>. You might also want to
422 read the file <file:Documentation/scsi/aha152x.txt>.
424 To compile this driver as a module, choose M here: the
425 module will be called aha152x.
428 tristate "Adaptec AHA1542 support"
429 depends on ISA && SCSI && ISA_DMA_API
431 This is support for a SCSI host adapter. It is explained in section
432 3.4 of the SCSI-HOWTO, available from
433 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
434 purchased by Adaptec, and some former Trantor products are being
435 sold under the Adaptec name. If it doesn't work out of the box, you
436 may have to change some settings in <file:drivers/scsi/aha1542.h>.
438 To compile this driver as a module, choose M here: the
439 module will be called aha1542.
442 tristate "Adaptec AHA1740 support"
443 depends on EISA && SCSI
445 This is support for a SCSI host adapter. It is explained in section
446 3.5 of the SCSI-HOWTO, available from
447 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
448 of the box, you may have to change some settings in
449 <file:drivers/scsi/aha1740.h>.
451 To compile this driver as a module, choose M here: the
452 module will be called aha1740.
455 tristate "Adaptec AACRAID support"
456 depends on SCSI && PCI
458 This driver supports a variety of Dell, HP, Adaptec, IBM and
459 ICP storage products. For a list of supported products, refer
460 to <file:Documentation/scsi/aacraid.txt>.
462 To compile this driver as a module, choose M here: the module
463 will be called aacraid.
466 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
468 config SCSI_AIC7XXX_OLD
469 tristate "Adaptec AIC7xxx support (old driver)"
470 depends on (ISA || EISA || PCI ) && SCSI
472 WARNING This driver is an older aic7xxx driver and is no longer
473 under active development. Adaptec, Inc. is writing a new driver to
474 take the place of this one, and it is recommended that whenever
475 possible, people should use the new Adaptec written driver instead
476 of this one. This driver will eventually be phased out entirely.
478 This is support for the various aic7xxx based Adaptec SCSI
479 controllers. These include the 274x EISA cards; 284x VLB cards;
480 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
481 motherboard based SCSI controllers from Adaptec. It does not support
482 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
483 support them. It does not support the 2920 cards from Adaptec that
484 use the Future Domain SCSI controller chip. For those cards, you
485 need the "Future Domain 16xx SCSI support" driver.
487 In general, if the controller is based on an Adaptec SCSI controller
488 chip from the aic777x series or the aic78xx series, this driver
489 should work. The only exception is the 7810 which is specifically
490 not supported (that's the RAID controller chip on the AAA-13x
493 Note that the AHA2920 SCSI host adapter is *not* supported by this
494 driver; choose "Future Domain 16xx SCSI support" instead if you have
497 Information on the configuration options for this controller can be
498 found by checking the help file for each of the available
499 configuration options. You should read
500 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
501 contacting the maintainer with any questions. The SCSI-HOWTO,
502 available from <http://www.tldp.org/docs.html#howto>, can also
505 To compile this driver as a module, choose M here: the
506 module will be called aic7xxx_old.
508 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
509 source "drivers/scsi/aic94xx/Kconfig"
512 tristate "Adaptec I2O RAID support "
513 depends on SCSI && PCI && VIRT_TO_BUS
515 This driver supports all of Adaptec's I2O based RAID controllers as
516 well as the DPT SmartRaid V cards. This is an Adaptec maintained
517 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
519 To compile this driver as a module, choose M here: the
520 module will be called dpt_i2o.
523 tristate "AdvanSys SCSI support"
524 depends on SCSI && VIRT_TO_BUS
525 depends on ISA || EISA || PCI
527 This is a driver for all SCSI host adapters manufactured by
528 AdvanSys. It is documented in the kernel source in
529 <file:drivers/scsi/advansys.c>.
531 To compile this driver as a module, choose M here: the
532 module will be called advansys.
535 tristate "Always IN2000 SCSI support"
536 depends on ISA && SCSI
538 This is support for an ISA bus SCSI host adapter. You'll find more
539 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
540 out of the box, you may have to change the jumpers for IRQ or
543 To compile this driver as a module, choose M here: the
544 module will be called in2000.
547 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
548 depends on PCI && SCSI
550 This driver supports all of ARECA's SATA/SAS RAID controller cards.
551 This is an ARECA-maintained driver by Erich Chen.
552 If you have any problems, please mail to: <erich@areca.com.tw>.
553 Areca supports Linux RAID config tools.
554 Please link <http://www.areca.com.tw>
556 To compile this driver as a module, choose M here: the
557 module will be called arcmsr (modprobe arcmsr).
559 config SCSI_ARCMSR_AER
560 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
561 depends on SCSI_ARCMSR && PCIEAER
564 The advanced error reporting(AER) capability is "NOT" provided by
565 ARC1200/1201/1202 SATA RAID controllers cards.
566 If your card is one of ARC1200/1201/1202, please use the default setting, n.
567 If your card is other models, you could pick it
568 on condition that the kernel version is greater than 2.6.19.
569 This function is maintained driver by Nick Cheng. If you have any
570 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
571 To enable this function, choose Y here.
573 source "drivers/scsi/megaraid/Kconfig.megaraid"
576 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
577 depends on SCSI && PCI
579 This option enables support for HighPoint RocketRAID 3xxx/4xxx
582 To compile this driver as a module, choose M here; the module
583 will be called hptiop. If unsure, say N.
586 tristate "BusLogic SCSI support"
587 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
589 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
590 Adapters. Consult the SCSI-HOWTO, available from
591 <http://www.tldp.org/docs.html#howto>, and the files
592 <file:Documentation/scsi/BusLogic.txt> and
593 <file:Documentation/scsi/FlashPoint.txt> for more information.
594 Note that support for FlashPoint is only available for 32-bit
597 To compile this driver as a module, choose M here: the
598 module will be called BusLogic.
600 config SCSI_FLASHPOINT
601 bool "FlashPoint support"
602 depends on SCSI_BUSLOGIC && PCI && X86_32
604 This option allows you to add FlashPoint support to the
605 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
606 substantial, so users of MultiMaster Host Adapters may not
610 tristate "LibFC module"
614 Fibre Channel library module
617 tristate "FCoE module"
621 Fibre Channel over Ethernet module
624 tristate "DMX3191D SCSI support"
625 depends on PCI && SCSI
626 select SCSI_SPI_ATTRS
628 This is support for Domex DMX3191D SCSI Host Adapters.
630 To compile this driver as a module, choose M here: the
631 module will be called dmx3191d.
634 tristate "DTC3180/3280 SCSI support"
635 depends on ISA && SCSI
636 select SCSI_SPI_ATTRS
637 select CHECK_SIGNATURE
639 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
640 the SCSI-HOWTO, available from
641 <http://www.tldp.org/docs.html#howto>, and the file
642 <file:Documentation/scsi/dtc3x80.txt>.
644 To compile this driver as a module, choose M here: the
645 module will be called dtc.
648 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
649 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
651 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
652 ISA and all EISA I/O addresses are probed looking for the "EATA"
653 signature. The addresses of all the PCI SCSI controllers reported
654 by the PCI subsystem are probed as well.
656 You want to read the start of <file:drivers/scsi/eata.c> and the
657 SCSI-HOWTO, available from
658 <http://www.tldp.org/docs.html#howto>.
660 To compile this driver as a module, choose M here: the
661 module will be called eata.
663 config SCSI_EATA_TAGGED_QUEUE
664 bool "enable tagged command queueing"
667 This is a feature of SCSI-2 which improves performance: the host
668 adapter can send several SCSI commands to a device's queue even if
669 previous commands haven't finished yet.
670 This is equivalent to the "eata=tc:y" boot option.
672 config SCSI_EATA_LINKED_COMMANDS
673 bool "enable elevator sorting"
676 This option enables elevator sorting for all probed SCSI disks and
677 CD-ROMs. It definitely reduces the average seek distance when doing
678 random seeks, but this does not necessarily result in a noticeable
679 performance improvement: your mileage may vary...
680 This is equivalent to the "eata=lc:y" boot option.
682 config SCSI_EATA_MAX_TAGS
683 int "maximum number of queued commands"
687 This specifies how many SCSI commands can be maximally queued for
688 each probed SCSI device. You should reduce the default value of 16
689 only if you have disks with buggy or limited tagged command support.
690 Minimum is 2 and maximum is 62. This value is also the window size
691 used by the elevator sorting option above. The effective value used
692 by the driver for each probed SCSI device is reported at boot time.
693 This is equivalent to the "eata=mq:8" boot option.
696 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
697 depends on (ISA || EISA || PCI) && SCSI && BROKEN
699 This driver supports all EATA-PIO protocol compliant SCSI Host
700 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
701 host adapters could also use this driver but are discouraged from
702 doing so, since this driver only supports hard disks and lacks
703 numerous features. You might want to have a look at the SCSI-HOWTO,
704 available from <http://www.tldp.org/docs.html#howto>.
706 To compile this driver as a module, choose M here: the
707 module will be called eata_pio.
709 config SCSI_FUTURE_DOMAIN
710 tristate "Future Domain 16xx SCSI/AHA-2920A support"
711 depends on (ISA || PCI) && SCSI
712 select CHECK_SIGNATURE
714 This is support for Future Domain's 16-bit SCSI host adapters
715 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
716 other adapters based on the Future Domain chipsets (Quantum
717 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
718 It is explained in section 3.7 of the SCSI-HOWTO, available from
719 <http://www.tldp.org/docs.html#howto>.
721 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
722 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
723 controller support"). This Future Domain driver works with the older
724 Adaptec AHA-2920A boards with a Future Domain chip on them.
726 To compile this driver as a module, choose M here: the
727 module will be called fdomain.
730 tristate "Future Domain MCS-600/700 SCSI support"
731 depends on MCA_LEGACY && SCSI
733 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
734 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
735 is identical to the MCS 700 and hence also supported by this driver.
736 This driver also supports the Reply SB16/SCSI card (the SCSI part).
737 It supports multiple adapters in the same system.
739 To compile this driver as a module, choose M here: the
740 module will be called fd_mcs.
743 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
744 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
746 Formerly called GDT SCSI Disk Array Controller Support.
748 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
749 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
750 in the kernel source in <file:drivers/scsi/gdth.c> and
751 <file:drivers/scsi/gdth.h>.
753 To compile this driver as a module, choose M here: the
754 module will be called gdth.
756 config SCSI_GENERIC_NCR5380
757 tristate "Generic NCR5380/53c400 SCSI PIO support"
758 depends on ISA && SCSI
759 select SCSI_SPI_ATTRS
761 This is a driver for the old NCR 53c80 series of SCSI controllers
762 on boards using PIO. Most boards such as the Trantor T130 fit this
763 category, along with a large number of ISA 8bit controllers shipped
764 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
765 you should select the specific driver for that card rather than
766 generic 5380 support.
768 It is explained in section 3.8 of the SCSI-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
770 of the box, you may have to change some settings in
771 <file:drivers/scsi/g_NCR5380.h>.
773 To compile this driver as a module, choose M here: the
774 module will be called g_NCR5380.
776 config SCSI_GENERIC_NCR5380_MMIO
777 tristate "Generic NCR5380/53c400 SCSI MMIO support"
778 depends on ISA && SCSI
779 select SCSI_SPI_ATTRS
781 This is a driver for the old NCR 53c80 series of SCSI controllers
782 on boards using memory mapped I/O.
783 It is explained in section 3.8 of the SCSI-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
785 of the box, you may have to change some settings in
786 <file:drivers/scsi/g_NCR5380.h>.
788 To compile this driver as a module, choose M here: the
789 module will be called g_NCR5380_mmio.
791 config SCSI_GENERIC_NCR53C400
792 bool "Enable NCR53c400 extensions"
793 depends on SCSI_GENERIC_NCR5380
795 This enables certain optimizations for the NCR53c400 SCSI cards.
796 You might as well try it out. Note that this driver will only probe
797 for the Trantor T130B in its default configuration; you might have
798 to pass a command line option to the kernel at boot time if it does
799 not detect your card. See the file
800 <file:Documentation/scsi/g_NCR5380.txt> for details.
803 tristate "IBMMCA SCSI support"
804 depends on MCA && SCSI
806 This is support for the IBM SCSI adapter found in many of the PS/2
807 series computers. These machines have an MCA bus, so you need to
808 answer Y to "MCA support" as well and read
809 <file:Documentation/mca.txt>.
811 If the adapter isn't found during boot (a common problem for models
812 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
813 option, where <pun> is the id of the SCSI subsystem (usually 7, but
814 if that doesn't work check your reference diskette). Owners of
815 model 95 with a LED-matrix-display can in addition activate some
816 activity info like under OS/2, but more informative, by setting
817 'ibmmcascsi=display' as an additional kernel parameter. Try "man
818 bootparam" or see the documentation of your boot loader about how to
819 pass options to the kernel.
821 To compile this driver as a module, choose M here: the
822 module will be called ibmmca.
824 config IBMMCA_SCSI_ORDER_STANDARD
825 bool "Standard SCSI-order"
826 depends on SCSI_IBMMCA
828 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
829 are assigned to the drive letters, starting with the lowest SCSI-id
830 (physical number -- pun) to be drive C:, as seen from DOS and
831 similar operating systems. When looking into papers describing the
832 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
833 The SCSI-standard follows a hardware-hierarchy which says that id 7
834 has the highest priority and id 0 the lowest. Therefore, the host
835 adapters are still today everywhere placed as SCSI-id 7 by default.
836 In the SCSI-standard, the drive letters express the priority of the
837 disk. C: should be the hard disk, or a partition on it, with the
838 highest priority. This must therefore be the disk with the highest
839 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
840 original definition of the SCSI-standard as also industrial- and
841 process-control-machines, like VME-CPUs running under realtime-OSes
842 (e.g. LynxOS, OS9) do.
844 If you like to run Linux on your MCA-machine with the same
845 assignment of hard disks as seen from e.g. DOS or OS/2 on your
846 machine, which is in addition conformant to the SCSI-standard, you
847 must say Y here. This is also necessary for MCA-Linux users who want
848 to keep downward compatibility to older releases of the
849 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
852 If you like to have the lowest SCSI-id assigned as drive C:, as
853 modern SCSI-BIOSes do, which does not conform to the standard, but
854 is widespread and common in the PC-world of today, you must say N
855 here. If unsure, say Y.
857 config IBMMCA_SCSI_DEV_RESET
858 bool "Reset SCSI-devices at boottime"
859 depends on SCSI_IBMMCA
861 By default, SCSI-devices are reset when the machine is powered on.
862 However, some devices exist, like special-control-devices,
863 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
864 not reset when switched on. If you say Y here, each device connected
865 to your SCSI-bus will be issued a reset-command after it has been
866 probed, while the kernel is booting. This may cause problems with
867 more modern devices, like hard disks, which do not appreciate these
868 reset commands, and can cause your system to hang. So say Y only if
869 you know that one of your older devices needs it; N is the safe
873 tristate "IBM ServeRAID support"
874 depends on PCI && SCSI
876 This is support for the IBM ServeRAID hardware RAID controllers.
877 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
878 for more information. If this driver does not work correctly
879 without modification please contact the author by email at
880 <ipslinux@adaptec.com>.
882 To compile this driver as a module, choose M here: the
883 module will be called ips.
886 tristate "IBM Virtual SCSI support"
887 depends on PPC_PSERIES || PPC_ISERIES
888 select SCSI_SRP_ATTRS
889 select VIOPATH if PPC_ISERIES
891 This is the IBM POWER Virtual SCSI Client
893 To compile this driver as a module, choose M here: the
894 module will be called ibmvscsic.
896 config SCSI_IBMVSCSIS
897 tristate "IBM Virtual SCSI Server support"
898 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
900 This is the SRP target driver for IBM pSeries virtual environments.
902 The userspace component needed to initialize the driver and
903 documentation can be found:
905 http://stgt.berlios.de/
907 To compile this driver as a module, choose M here: the
908 module will be called ibmvstgt.
911 tristate "IBM Virtual FC support"
912 depends on PPC_PSERIES && SCSI
915 This is the IBM POWER Virtual FC Client
917 To compile this driver as a module, choose M here: the
918 module will be called ibmvfc.
920 config SCSI_IBMVFC_TRACE
921 bool "enable driver internal trace"
922 depends on SCSI_IBMVFC
925 If you say Y here, the driver will trace all commands issued
926 to the adapter. Performance impact is minimal. Trace can be
927 dumped using /sys/class/scsi_host/hostXX/trace.
930 tristate "Initio 9100U(W) support"
931 depends on PCI && SCSI
933 This is support for the Initio 91XXU(W) SCSI host adapter. Please
934 read the SCSI-HOWTO, available from
935 <http://www.tldp.org/docs.html#howto>.
937 To compile this driver as a module, choose M here: the
938 module will be called initio.
941 tristate "Initio INI-A100U2W support"
942 depends on PCI && SCSI
944 This is support for the Initio INI-A100U2W SCSI host adapter.
945 Please read the SCSI-HOWTO, available from
946 <http://www.tldp.org/docs.html#howto>.
948 To compile this driver as a module, choose M here: the
949 module will be called a100u2w.
952 tristate "IOMEGA parallel port (ppa - older drives)"
953 depends on SCSI && PARPORT_PC
955 This driver supports older versions of IOMEGA's parallel port ZIP
956 drive (a 100 MB removable media device).
958 Note that you can say N here if you have the SCSI version of the ZIP
959 drive: it will be supported automatically if you said Y to the
960 generic "SCSI disk support", above.
962 If you have the ZIP Plus drive or a more recent parallel port ZIP
963 drive (if the supplied cable with the drive is labeled "AutoDetect")
964 then you should say N here and Y to "IOMEGA parallel port (imm -
965 newer drives)", below.
967 For more information about this driver and how to use it you should
968 read the file <file:Documentation/scsi/ppa.txt>. You should also read
969 the SCSI-HOWTO, which is available from
970 <http://www.tldp.org/docs.html#howto>. If you use this driver,
971 you will still be able to use the parallel port for other tasks,
972 such as a printer; it is safe to compile both drivers into the
975 To compile this driver as a module, choose M here: the
976 module will be called ppa.
979 tristate "IOMEGA parallel port (imm - newer drives)"
980 depends on SCSI && PARPORT_PC
982 This driver supports newer versions of IOMEGA's parallel port ZIP
983 drive (a 100 MB removable media device).
985 Note that you can say N here if you have the SCSI version of the ZIP
986 drive: it will be supported automatically if you said Y to the
987 generic "SCSI disk support", above.
989 If you have the ZIP Plus drive or a more recent parallel port ZIP
990 drive (if the supplied cable with the drive is labeled "AutoDetect")
991 then you should say Y here; if you have an older ZIP drive, say N
992 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
994 For more information about this driver and how to use it you should
995 read the file <file:Documentation/scsi/ppa.txt>. You should also read
996 the SCSI-HOWTO, which is available from
997 <http://www.tldp.org/docs.html#howto>. If you use this driver,
998 you will still be able to use the parallel port for other tasks,
999 such as a printer; it is safe to compile both drivers into the
1002 To compile this driver as a module, choose M here: the
1003 module will be called imm.
1005 config SCSI_IZIP_EPP16
1006 bool "ppa/imm option - Use slow (but safe) EPP-16"
1007 depends on SCSI_PPA || SCSI_IMM
1009 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1010 allows them to act as expansion buses that can handle up to 64
1013 Some parallel port chipsets are slower than their motherboard, and
1014 so we have to control the state of the chipset's FIFO queue every
1015 now and then to avoid data loss. This will be done if you say Y
1018 Generally, saying Y is the safe option and slows things down a bit.
1020 config SCSI_IZIP_SLOW_CTR
1021 bool "ppa/imm option - Assume slow parport control register"
1022 depends on SCSI_PPA || SCSI_IMM
1024 Some parallel ports are known to have excessive delays between
1025 changing the parallel port control register and good data being
1026 available on the parallel port data/status register. This option
1027 forces a small delay (1.0 usec to be exact) after changing the
1028 control register to let things settle out. Enabling this option may
1029 result in a big drop in performance but some very old parallel ports
1030 (found in 386 vintage machines) will not work properly.
1032 Generally, saying N is fine.
1035 tristate "Marvell 88SE6440 SAS/SATA support"
1036 depends on PCI && SCSI
1037 select SCSI_SAS_LIBSAS
1039 This driver supports Marvell SAS/SATA PCI devices.
1041 To compiler this driver as a module, choose M here: the module
1042 will be called mvsas.
1044 config SCSI_NCR53C406A
1045 tristate "NCR53c406a SCSI support"
1046 depends on ISA && SCSI
1048 This is support for the NCR53c406a SCSI host adapter. For user
1049 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1050 in the kernel source. Also read the SCSI-HOWTO, available from
1051 <http://www.tldp.org/docs.html#howto>.
1053 To compile this driver as a module, choose M here: the
1054 module will be called NCR53c406.
1056 config SCSI_NCR_D700
1057 tristate "NCR Dual 700 MCA SCSI support"
1058 depends on MCA && SCSI
1059 select SCSI_SPI_ATTRS
1061 This is a driver for the MicroChannel Dual 700 card produced by
1062 NCR and commonly used in 345x/35xx/4100 class machines. It always
1063 tries to negotiate sync and uses tag command queueing.
1065 Unless you have an NCR manufactured machine, the chances are that
1066 you do not have this SCSI card, so say N.
1069 tristate "HP Lasi SCSI support for 53c700/710"
1070 depends on GSC && SCSI
1071 select SCSI_SPI_ATTRS
1073 This is a driver for the SCSI controller in the Lasi chip found in
1074 many PA-RISC workstations & servers. If you do not know whether you
1075 have a Lasi chip, it is safe to say "Y" here.
1077 config SCSI_SNI_53C710
1078 tristate "SNI RM SCSI support for 53c710"
1079 depends on SNI_RM && SCSI
1080 select SCSI_SPI_ATTRS
1081 select 53C700_LE_ON_BE
1083 This is a driver for the onboard SCSI controller found in older
1084 SNI RM workstations & servers.
1086 config 53C700_LE_ON_BE
1088 depends on SCSI_LASI700
1092 tristate "Promise SuperTrak EX Series support"
1093 depends on PCI && SCSI
1095 This driver supports Promise SuperTrak EX series storage controllers.
1097 Promise provides Linux RAID configuration utility for these
1098 controllers. Please visit <http://www.promise.com> to download.
1100 To compile this driver as a module, choose M here: the
1101 module will be called stex.
1103 config 53C700_BE_BUS
1105 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1108 config SCSI_SYM53C8XX_2
1109 tristate "SYM53C8XX Version 2 SCSI support"
1110 depends on PCI && SCSI
1111 select SCSI_SPI_ATTRS
1113 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1114 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1115 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1116 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1117 controllers; you need to use the Fusion MPT driver for that.
1119 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1122 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1123 int "DMA addressing mode"
1124 depends on SCSI_SYM53C8XX_2
1127 This option only applies to PCI-SCSI chips that are PCI DAC
1128 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1130 When set to 0, the driver will program the chip to only perform
1131 32-bit DMA. When set to 1, the chip will be able to perform DMA
1132 to addresses up to 1TB. When set to 2, the driver supports the
1133 full 64-bit DMA address range, but can only address 16 segments
1134 of 4 GB each. This limits the total addressable range to 64 GB.
1136 Most machines with less than 4GB of memory should use a setting
1137 of 0 for best performance. If your machine has 4GB of memory
1138 or more, you should set this option to 1 (the default).
1140 The still experimental value 2 (64 bit DMA addressing with 16
1141 x 4GB segments limitation) can be used on systems that require
1142 PCI address bits past bit 39 to be set for the addressing of
1143 memory using PCI DAC cycles.
1145 config SCSI_SYM53C8XX_DEFAULT_TAGS
1146 int "Default tagged command queue depth"
1147 depends on SCSI_SYM53C8XX_2
1150 This is the default value of the command queue depth the
1151 driver will announce to the generic SCSI layer for devices
1152 that support tagged command queueing. This value can be changed
1153 from the boot command line. This is a soft limit that cannot
1154 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1156 config SCSI_SYM53C8XX_MAX_TAGS
1157 int "Maximum number of queued commands"
1158 depends on SCSI_SYM53C8XX_2
1161 This option allows you to specify the maximum number of commands
1162 that can be queued to any device, when tagged command queuing is
1163 possible. The driver supports up to 256 queued commands per device.
1164 This value is used as a compiled-in hard limit.
1166 config SCSI_SYM53C8XX_MMIO
1167 bool "Use memory mapped IO"
1168 depends on SCSI_SYM53C8XX_2
1171 Memory mapped IO is faster than Port IO. Most people should
1172 answer Y here, but some machines may have problems. If you have
1173 to answer N here, please report the problem to the maintainer.
1176 tristate "IBM Power Linux RAID adapter support"
1177 depends on PCI && SCSI && ATA
1180 This driver supports the IBM Power Linux family RAID adapters.
1181 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1182 as IBM iSeries 5702, 5703, 5709, and 570A.
1184 config SCSI_IPR_TRACE
1185 bool "enable driver internal trace"
1189 If you say Y here, the driver will trace all commands issued
1190 to the adapter. Performance impact is minimal. Trace can be
1191 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1193 config SCSI_IPR_DUMP
1194 bool "enable adapter dump support"
1198 If you say Y here, the driver will support adapter crash dump.
1199 If you enable this support, the iprdump daemon can be used
1200 to capture adapter failure analysis information.
1203 tristate "Zalon SCSI support"
1204 depends on GSC && SCSI
1205 select SCSI_SPI_ATTRS
1207 The Zalon is a GSC/HSC bus interface chip that sits between the
1208 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1209 C110, J200, J210 and some D, K & R-class machines. It's also
1210 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1211 Say Y here if you have one of these machines or cards.
1213 config SCSI_NCR_Q720
1214 tristate "NCR Quad 720 MCA SCSI support"
1215 depends on MCA && SCSI
1216 select SCSI_SPI_ATTRS
1218 This is a driver for the MicroChannel Quad 720 card produced by
1219 NCR and commonly used in 345x/35xx/4100 class machines. It always
1220 tries to negotiate sync and uses tag command queueing.
1222 Unless you have an NCR manufactured machine, the chances are that
1223 you do not have this SCSI card, so say N.
1225 config SCSI_NCR53C8XX_DEFAULT_TAGS
1226 int "default tagged command queue depth"
1227 depends on SCSI_ZALON || SCSI_NCR_Q720
1230 "Tagged command queuing" is a feature of SCSI-2 which improves
1231 performance: the host adapter can send several SCSI commands to a
1232 device's queue even if previous commands haven't finished yet.
1233 Because the device is intelligent, it can optimize its operations
1234 (like head positioning) based on its own request queue. Some SCSI
1235 devices don't implement this properly; if you want to disable this
1236 feature, enter 0 or 1 here (it doesn't matter which).
1238 The default value is 8 and should be supported by most hard disks.
1239 This value can be overridden from the boot command line using the
1240 'tags' option as follows (example):
1241 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1242 4, set queue depth to 16 for target 2 and target 3 on controller 0
1243 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1245 The normal answer therefore is to go with the default 8 and to use
1246 a boot command line option for devices that need to use a different
1247 command queue depth.
1249 There is no safe option other than using good SCSI devices.
1251 config SCSI_NCR53C8XX_MAX_TAGS
1252 int "maximum number of queued commands"
1253 depends on SCSI_ZALON || SCSI_NCR_Q720
1256 This option allows you to specify the maximum number of commands
1257 that can be queued to any device, when tagged command queuing is
1258 possible. The default value is 32. Minimum is 2, maximum is 64.
1259 Modern hard disks are able to support 64 tags and even more, but
1260 do not seem to be faster when more than 32 tags are being used.
1262 So, the normal answer here is to go with the default value 32 unless
1263 you are using very large hard disks with large cache (>= 1 MB) that
1264 are able to take advantage of more than 32 tagged commands.
1266 There is no safe option and the default answer is recommended.
1268 config SCSI_NCR53C8XX_SYNC
1269 int "synchronous transfers frequency in MHz"
1270 depends on SCSI_ZALON || SCSI_NCR_Q720
1273 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1274 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1275 are respectively the maximum data transfer rates in mega-transfers
1276 per second for each class. For example, a FAST-20 Wide 16 device is
1277 able to transfer data at 20 million 16 bit packets per second for a
1278 total rate of 40 MB/s.
1280 You may specify 0 if you want to only use asynchronous data
1281 transfers. This is the safest and slowest option. Otherwise, specify
1282 a value between 5 and 80, depending on the capability of your SCSI
1283 controller. The higher the number, the faster the data transfer.
1284 Note that 80 should normally be ok since the driver decreases the
1285 value automatically according to the controller's capabilities.
1287 Your answer to this question is ignored for controllers with NVRAM,
1288 since the driver will get this information from the user set-up. It
1289 also can be overridden using a boot setup option, as follows
1290 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1291 for FAST-20 synchronous data transfer (20 mega-transfers per
1294 The normal answer therefore is not to go with the default but to
1295 select the maximum value 80 allowing the driver to use the maximum
1296 value supported by each controller. If this causes problems with
1297 your SCSI devices, you should come back and decrease the value.
1299 There is no safe option other than using good cabling, right
1300 terminations and SCSI conformant devices.
1302 config SCSI_NCR53C8XX_NO_DISCONNECT
1303 bool "not allow targets to disconnect"
1304 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1306 This option is only provided for safety if you suspect some SCSI
1307 device of yours to not support properly the target-disconnect
1308 feature. In that case, you would say Y here. In general however, to
1309 not allow targets to disconnect is not reasonable if there is more
1310 than 1 device on a SCSI bus. The normal answer therefore is N.
1313 tristate "PAS16 SCSI support"
1314 depends on ISA && SCSI
1315 select SCSI_SPI_ATTRS
1317 This is support for a SCSI host adapter. It is explained in section
1318 3.10 of the SCSI-HOWTO, available from
1319 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1320 of the box, you may have to change some settings in
1321 <file:drivers/scsi/pas16.h>.
1323 To compile this driver as a module, choose M here: the
1324 module will be called pas16.
1326 config SCSI_QLOGIC_FAS
1327 tristate "Qlogic FAS SCSI support"
1328 depends on ISA && SCSI
1330 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1331 FastSCSI! cards as well as any other card based on the FASXX chip
1332 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1334 This driver does NOT support the PCI versions of these cards. The
1335 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1336 SCSI support"), below.
1338 Information about this driver is contained in
1339 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1340 SCSI-HOWTO, available from
1341 <http://www.tldp.org/docs.html#howto>.
1343 To compile this driver as a module, choose M here: the
1344 module will be called qlogicfas.
1346 config SCSI_QLOGIC_1280
1347 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1348 depends on PCI && SCSI
1350 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1352 To compile this driver as a module, choose M here: the
1353 module will be called qla1280.
1355 config SCSI_QLOGICPTI
1356 tristate "PTI Qlogic, ISP Driver"
1357 depends on SBUS && SCSI
1359 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1360 controllers are known under Solaris as qpti and in the openprom as
1361 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1362 driven by a different driver.
1364 To compile this driver as a module, choose M here: the
1365 module will be called qlogicpti.
1367 source "drivers/scsi/qla2xxx/Kconfig"
1368 source "drivers/scsi/qla4xxx/Kconfig"
1371 tristate "Emulex LightPulse Fibre Channel Support"
1372 depends on PCI && SCSI
1373 select SCSI_FC_ATTRS
1375 This lpfc driver supports the Emulex LightPulse
1376 Family of Fibre Channel PCI host adapters.
1378 config SCSI_LPFC_DEBUG_FS
1379 bool "Emulex LightPulse Fibre Channel debugfs Support"
1380 depends on SCSI_LPFC && DEBUG_FS
1382 This makes debugging infomation from the lpfc driver
1383 available via the debugfs filesystem.
1386 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1387 depends on (EISA || MCA) && SCSI
1388 select SCSI_SPI_ATTRS
1390 This driver for NCR53c710 based SCSI host adapters.
1392 It currently supports Compaq EISA cards and NCR MCA cards
1394 config SCSI_SYM53C416
1395 tristate "Symbios 53c416 SCSI support"
1396 depends on ISA && SCSI
1398 This is support for the sym53c416 SCSI host adapter, the SCSI
1399 adapter that comes with some HP scanners. This driver requires that
1400 the sym53c416 is configured first using some sort of PnP
1401 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1402 are using isapnp then you need to compile this driver as a module
1403 and then load it using insmod after isapnp has run. The parameters
1404 of the configured card(s) should be passed to the driver. The format
1407 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1409 To compile this driver as a module, choose M here: the
1410 module will be called sym53c416.
1413 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1414 depends on PCI && SCSI && EXPERIMENTAL
1416 This driver supports PCI SCSI host adapters based on the ASIC
1417 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1419 This driver works, but is still in experimental status. So better
1420 have a bootable disk and a backup in case of emergency.
1422 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1424 To compile this driver as a module, choose M here: the
1425 module will be called dc395x.
1428 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1429 depends on PCI && SCSI
1431 This driver supports PCI SCSI host adapters based on the Am53C974A
1432 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1433 PCscsi/PCnet (Am53/79C974) solutions.
1435 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1437 Note that this driver does NOT support Tekram DC390W/U/F, which are
1438 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1440 To compile this driver as a module, choose M here: the
1441 module will be called tmscsim.
1444 tristate "Trantor T128/T128F/T228 SCSI support"
1445 depends on ISA && SCSI
1446 select SCSI_SPI_ATTRS
1447 select CHECK_SIGNATURE
1449 This is support for a SCSI host adapter. It is explained in section
1450 3.11 of the SCSI-HOWTO, available from
1451 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1452 of the box, you may have to change some settings in
1453 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1454 Adaptec, and some former Trantor products are being sold under the
1457 To compile this driver as a module, choose M here: the
1458 module will be called t128.
1461 tristate "UltraStor 14F/34F support"
1462 depends on ISA && SCSI && ISA_DMA_API
1464 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1465 The source at <file:drivers/scsi/u14-34f.c> contains some
1466 information about this hardware. If the driver doesn't work out of
1467 the box, you may have to change some settings in
1468 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1469 <http://www.tldp.org/docs.html#howto>. Note that there is also
1470 another driver for the same hardware: "UltraStor SCSI support",
1471 below. You should say Y to both only if you want 24F support as
1474 To compile this driver as a module, choose M here: the
1475 module will be called u14-34f.
1477 config SCSI_U14_34F_TAGGED_QUEUE
1478 bool "enable tagged command queueing"
1479 depends on SCSI_U14_34F
1481 This is a feature of SCSI-2 which improves performance: the host
1482 adapter can send several SCSI commands to a device's queue even if
1483 previous commands haven't finished yet.
1484 This is equivalent to the "u14-34f=tc:y" boot option.
1486 config SCSI_U14_34F_LINKED_COMMANDS
1487 bool "enable elevator sorting"
1488 depends on SCSI_U14_34F
1490 This option enables elevator sorting for all probed SCSI disks and
1491 CD-ROMs. It definitely reduces the average seek distance when doing
1492 random seeks, but this does not necessarily result in a noticeable
1493 performance improvement: your mileage may vary...
1494 This is equivalent to the "u14-34f=lc:y" boot option.
1496 config SCSI_U14_34F_MAX_TAGS
1497 int "maximum number of queued commands"
1498 depends on SCSI_U14_34F
1501 This specifies how many SCSI commands can be maximally queued for
1502 each probed SCSI device. You should reduce the default value of 8
1503 only if you have disks with buggy or limited tagged command support.
1504 Minimum is 2 and maximum is 14. This value is also the window size
1505 used by the elevator sorting option above. The effective value used
1506 by the driver for each probed SCSI device is reported at boot time.
1507 This is equivalent to the "u14-34f=mq:8" boot option.
1509 config SCSI_ULTRASTOR
1510 tristate "UltraStor SCSI support"
1511 depends on X86 && ISA && SCSI
1513 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1514 adapter family. This driver is explained in section 3.12 of the
1515 SCSI-HOWTO, available from
1516 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1517 of the box, you may have to change some settings in
1518 <file:drivers/scsi/ultrastor.h>.
1520 Note that there is also another driver for the same hardware:
1521 "UltraStor 14F/34F support", above.
1523 To compile this driver as a module, choose M here: the
1524 module will be called ultrastor.
1527 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1528 depends on PCI && SCSI && !64BIT
1530 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1531 SCSI host adapter. Please read the SCSI-HOWTO, available from
1532 <http://www.tldp.org/docs.html#howto>.
1534 To compile this driver as a module, choose M here: the
1535 module will be called nsp32.
1538 tristate "SCSI debugging host simulator"
1542 This is a host adapter simulator that can simulate multiple hosts
1543 each with multiple dummy SCSI devices (disks). It defaults to one
1544 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1545 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1546 dummy disks are simulated, they share the same kernel RAM for
1547 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1548 information. This driver is primarily of use to those testing the
1549 SCSI and block subsystems. If unsure, say N.
1552 tristate "MESH (Power Mac internal SCSI) support"
1553 depends on PPC32 && PPC_PMAC && SCSI
1555 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1556 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1557 other Power Macintoshes do). Say Y to include support for this SCSI
1560 To compile this driver as a module, choose M here: the
1561 module will be called mesh.
1563 config SCSI_MESH_SYNC_RATE
1564 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1565 depends on SCSI_MESH
1568 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1569 drives a bus which is entirely internal to the machine (such as the
1570 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1571 operation at up to 10 MB/s. On machines where the SCSI bus
1572 controlled by the MESH can have external devices connected, it is
1573 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1574 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1575 to disable synchronous operation.
1577 config SCSI_MESH_RESET_DELAY_MS
1578 int "initial bus reset delay (ms) (0 = no reset)"
1579 depends on SCSI_MESH
1582 config SCSI_MAC53C94
1583 tristate "53C94 (Power Mac external SCSI) support"
1584 depends on PPC32 && PPC_PMAC && SCSI
1586 On Power Macintoshes (and clones) with two SCSI buses, the external
1587 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1588 machines which only have one SCSI bus, such as the 7200, also use
1589 the 53C94. Say Y to include support for the 53C94.
1591 To compile this driver as a module, choose M here: the
1592 module will be called mac53c94.
1594 source "drivers/scsi/arm/Kconfig"
1597 bool "MIPS JAZZ FAS216 SCSI support"
1598 depends on MACH_JAZZ && SCSI
1599 select SCSI_SPI_ATTRS
1601 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1602 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1606 tristate "A3000 WD33C93A support"
1607 depends on AMIGA && SCSI
1609 If you have an Amiga 3000 and have SCSI devices connected to the
1610 built-in SCSI controller, say Y. Otherwise, say N.
1612 To compile this driver as a module, choose M here: the
1613 module will be called a3000.
1616 tristate "A2091/A590 WD33C93A support"
1617 depends on ZORRO && SCSI
1619 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1622 To compile this driver as a module, choose M here: the
1623 module will be called a2091.
1626 tristate "GVP Series II WD33C93A support"
1627 depends on ZORRO && SCSI
1629 If you have a Great Valley Products Series II SCSI controller,
1630 answer Y. Also say Y if you have a later model of GVP SCSI
1631 controller (such as the GVP A4008 or a Combo board). Otherwise,
1632 answer N. This driver does NOT work for the T-Rex series of
1633 accelerators from TekMagic and GVP-M.
1635 To compile this driver as a module, choose M here: the
1636 module will be called gvp11.
1639 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1640 depends on AMIGA && SCSI && EXPERIMENTAL
1641 select SCSI_SPI_ATTRS
1643 If you have an Amiga 4000T and have SCSI devices connected to the
1644 built-in SCSI controller, say Y. Otherwise, say N.
1646 To compile this driver as a module, choose M here: the
1647 module will be called a4000t.
1649 config SCSI_ZORRO7XX
1650 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1651 depends on ZORRO && SCSI && EXPERIMENTAL
1652 select SCSI_SPI_ATTRS
1654 Support for various NCR53c710-based SCSI controllers on Zorro
1655 expansion boards for the Amiga.
1657 - the Amiga 4091 Zorro III SCSI-2 controller,
1658 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1660 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1661 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1662 accelerator card for the Amiga 1200,
1663 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1666 tristate "Atari native SCSI support"
1667 depends on ATARI && SCSI
1668 select SCSI_SPI_ATTRS
1671 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1672 Falcon, ...) say Y to get it supported. Of course also, if you have
1673 a compatible SCSI controller (e.g. for Medusa).
1675 To compile this driver as a module, choose M here: the
1676 module will be called atari_scsi.
1678 This driver supports both styles of NCR integration into the
1679 system: the TT style (separate DMA), and the Falcon style (via
1680 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1681 in the Hades (without DMA).
1683 config ATARI_SCSI_TOSHIBA_DELAY
1684 bool "Long delays for Toshiba CD-ROMs"
1685 depends on ATARI_SCSI
1687 This option increases the delay after a SCSI arbitration to
1688 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1689 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1690 would impact performance a bit, so say N.
1692 config ATARI_SCSI_RESET_BOOT
1693 bool "Reset SCSI-devices at boottime"
1694 depends on ATARI_SCSI
1696 Reset the devices on your Atari whenever it boots. This makes the
1697 boot process fractionally longer but may assist recovery from errors
1698 that leave the devices with SCSI operations partway completed.
1701 bool "Macintosh NCR5380 SCSI"
1702 depends on MAC && SCSI=y
1703 select SCSI_SPI_ATTRS
1705 This is the NCR 5380 SCSI controller included on most of the 68030
1706 based Macintoshes. If you have one of these say Y and read the
1707 SCSI-HOWTO, available from
1708 <http://www.tldp.org/docs.html#howto>.
1711 tristate "Macintosh NCR53c9[46] SCSI"
1712 depends on MAC && SCSI
1713 select SCSI_SPI_ATTRS
1715 This is the NCR 53c9x SCSI controller found on most of the 68040
1718 To compile this driver as a module, choose M here: the module
1719 will be called mac_esp.
1722 bool "WD33C93 SCSI driver for MVME147"
1723 depends on MVME147 && SCSI=y
1724 select SCSI_SPI_ATTRS
1726 Support for the on-board SCSI controller on the Motorola MVME147
1727 single-board computer.
1730 tristate "NCR53C710 SCSI driver for MVME16x"
1731 depends on MVME16x && SCSI
1732 select SCSI_SPI_ATTRS
1734 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1735 SCSI controller chip. Almost everyone using one of these boards
1736 will want to say Y to this question.
1738 config BVME6000_SCSI
1739 tristate "NCR53C710 SCSI driver for BVME6000"
1740 depends on BVME6000 && SCSI
1741 select SCSI_SPI_ATTRS
1743 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1744 SCSI controller chip. Almost everyone using one of these boards
1745 will want to say Y to this question.
1748 tristate "Sun3 NCR5380 SCSI"
1749 depends on SUN3 && SCSI
1750 select SCSI_SPI_ATTRS
1752 This option will enable support for the OBIO (onboard io) NCR5380
1753 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1754 "Sun3" type VME scsi controllers also based on the NCR5380.
1755 General Linux information on the Sun 3 series (now discontinued)
1756 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1759 bool "Sun3x ESP SCSI"
1760 depends on SUN3X && SCSI=y
1761 select SCSI_SPI_ATTRS
1763 The ESP was an on-board SCSI controller used on Sun 3/80
1764 machines. Say Y here to compile in support for it.
1767 tristate "Sparc ESP Scsi Driver"
1768 depends on SBUS && SCSI
1769 select SCSI_SPI_ATTRS
1771 This is the driver for the Sun ESP SCSI host adapter. The ESP
1772 chipset is present in most SPARC SBUS-based computers and
1773 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1774 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1776 To compile this driver as a module, choose M here: the
1777 module will be called sun_esp.
1780 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1781 depends on S390 && QDIO && SCSI
1782 select SCSI_FC_ATTRS
1784 If you want to access SCSI devices attached to your IBM eServer
1785 zSeries by means of Fibre Channel interfaces say Y.
1786 For details please refer to the documentation provided by IBM at
1787 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1789 This driver is also available as a module. This module will be
1790 called zfcp. If you want to compile it as a module, say M here
1791 and read <file:Documentation/kbuild/modules.txt>.
1794 tristate "SCSI RDMA Protocol helper library"
1795 depends on SCSI && PCI
1798 If you wish to use SRP target drivers, say Y.
1800 To compile this driver as a module, choose M here: the
1801 module will be called libsrp.
1803 endif # SCSI_LOWLEVEL
1805 source "drivers/scsi/pcmcia/Kconfig"
1807 source "drivers/scsi/device_handler/Kconfig"
1809 source "drivers/scsi/osd/Kconfig"