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, FireWire storage and the IDE-SCSI emulation driver.
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 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
106 as well. 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 "scsi log token [level]" > /proc/scsi/scsi
229 at boot time after the /proc file system has been mounted.
231 There are a number of things that can be used for 'token' (you can
232 find them in the source: <file:drivers/scsi/scsi.c>), and this
233 allows you to select the types of information you want, and the
234 level allows you to select the level of verbosity.
236 If you say N here, it may be harder to track down some types of SCSI
237 problems. If you say Y here your kernel will be somewhat larger, but
238 there should be no noticeable performance impact as long as you have
241 config SCSI_SCAN_ASYNC
242 bool "Asynchronous SCSI scanning"
245 The SCSI subsystem can probe for devices while the rest of the
246 system continues booting, and even probe devices on different
247 busses in parallel, leading to a significant speed-up.
249 If you have built SCSI as modules, enabling this option can
250 be a problem as the devices may not have been found by the
251 time your system expects them to have been. You can load the
252 scsi_wait_scan module to ensure that all scans have completed.
253 If you build your SCSI drivers into the kernel, then everything
254 will work fine if you say Y here.
256 You can override this choice by specifying "scsi_mod.scan=sync"
257 or async on the kernel's command line.
259 config SCSI_WAIT_SCAN
265 menu "SCSI Transports"
268 config SCSI_SPI_ATTRS
269 tristate "Parallel SCSI (SPI) Transport Attributes"
272 If you wish to export transport-specific information about
273 each attached SCSI device to sysfs, say Y. Otherwise, say N.
276 tristate "FiberChannel Transport Attributes"
280 If you wish to export transport-specific information about
281 each attached FiberChannel device to sysfs, say Y.
284 config SCSI_FC_TGT_ATTRS
285 bool "SCSI target support for FiberChannel Transport Attributes"
286 depends on SCSI_FC_ATTRS
287 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
289 If you want to use SCSI target mode drivers enable this option.
291 config SCSI_ISCSI_ATTRS
292 tristate "iSCSI Transport Attributes"
293 depends on SCSI && NET
295 If you wish to export transport-specific information about
296 each attached iSCSI device to sysfs, say Y.
299 config SCSI_SAS_ATTRS
300 tristate "SAS Transport Attributes"
301 depends on SCSI && BLK_DEV_BSG
303 If you wish to export transport-specific information about
304 each attached SAS device to sysfs, say Y.
306 source "drivers/scsi/libsas/Kconfig"
308 config SCSI_SRP_ATTRS
309 tristate "SRP Transport Attributes"
312 If you wish to export transport-specific information about
313 each attached SRP device to sysfs, say Y.
315 config SCSI_SRP_TGT_ATTRS
316 bool "SCSI target support for SRP Transport Attributes"
317 depends on SCSI_SRP_ATTRS
318 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
320 If you want to use SCSI target mode drivers enable this option.
324 menuconfig SCSI_LOWLEVEL
325 bool "SCSI low-level drivers"
329 if SCSI_LOWLEVEL && SCSI
332 tristate "iSCSI Initiator over TCP/IP"
333 depends on SCSI && INET
337 select SCSI_ISCSI_ATTRS
339 The iSCSI Driver provides a host with the ability to access storage
340 through an IP network. The driver uses the iSCSI protocol to transport
341 SCSI requests and responses over a TCP/IP network between the host
342 (the "initiator") and "targets". Architecturally, the iSCSI driver
343 combines with the host's TCP/IP stack, network drivers, and Network
344 Interface Card (NIC) to provide the same functions as a SCSI or a
345 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
347 To compile this driver as a module, choose M here: the
348 module will be called iscsi_tcp.
350 The userspace component needed to initialize the driver, documentation,
351 and sample configuration files can be found here:
353 http://open-iscsi.org
356 tristate "SGI WD93C93 SCSI Driver"
357 depends on SGI_HAS_WD93 && SCSI
359 If you have a Western Digital WD93 SCSI controller on
360 an SGI MIPS system, say Y. Otherwise, say N.
362 config BLK_DEV_3W_XXXX_RAID
363 tristate "3ware 5/6/7/8xxx ATA-RAID support"
364 depends on PCI && SCSI
366 3ware is the only hardware ATA-Raid product in Linux to date.
367 This card is 2,4, or 8 channel master mode support only.
368 SCSI support required!!!
370 <http://www.3ware.com/>
372 Please read the comments at the top of
373 <file:drivers/scsi/3w-xxxx.c>.
376 tristate "3ware 9xxx SATA-RAID support"
377 depends on PCI && SCSI
379 This driver supports the 9000 series 3ware SATA-RAID cards.
381 <http://www.amcc.com>
383 Please read the comments at the top of
384 <file:drivers/scsi/3w-9xxx.c>.
386 config SCSI_7000FASST
387 tristate "7000FASST SCSI support"
388 depends on ISA && SCSI && ISA_DMA_API
389 select CHECK_SIGNATURE
391 This driver supports the Western Digital 7000 SCSI host adapter
392 family. Some information is in the source:
393 <file:drivers/scsi/wd7000.c>.
395 To compile this driver as a module, choose M here: the
396 module will be called wd7000.
399 tristate "ACARD SCSI support"
400 depends on PCI && SCSI
402 This driver supports the ACARD SCSI host adapter.
403 Support Chip <ATP870 ATP876 ATP880 ATP885>
404 To compile this driver as a module, choose M here: the
405 module will be called atp870u.
408 tristate "Adaptec AHA152X/2825 support"
409 depends on ISA && SCSI && !64BIT
410 select SCSI_SPI_ATTRS
411 select CHECK_SIGNATURE
413 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
414 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
415 must be manually specified in this case.
417 It is explained in section 3.3 of the SCSI-HOWTO, available from
418 <http://www.tldp.org/docs.html#howto>. You might also want to
419 read the file <file:Documentation/scsi/aha152x.txt>.
421 To compile this driver as a module, choose M here: the
422 module will be called aha152x.
425 tristate "Adaptec AHA1542 support"
426 depends on ISA && SCSI && ISA_DMA_API
428 This is support for a SCSI host adapter. It is explained in section
429 3.4 of the SCSI-HOWTO, available from
430 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
431 purchased by Adaptec, and some former Trantor products are being
432 sold under the Adaptec name. If it doesn't work out of the box, you
433 may have to change some settings in <file:drivers/scsi/aha1542.h>.
435 To compile this driver as a module, choose M here: the
436 module will be called aha1542.
439 tristate "Adaptec AHA1740 support"
440 depends on EISA && SCSI
442 This is support for a SCSI host adapter. It is explained in section
443 3.5 of the SCSI-HOWTO, available from
444 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
445 of the box, you may have to change some settings in
446 <file:drivers/scsi/aha1740.h>.
448 To compile this driver as a module, choose M here: the
449 module will be called aha1740.
452 tristate "Adaptec AACRAID support"
453 depends on SCSI && PCI
455 This driver supports a variety of Dell, HP, Adaptec, IBM and
456 ICP storage products. For a list of supported products, refer
457 to <file:Documentation/scsi/aacraid.txt>.
459 To compile this driver as a module, choose M here: the module
460 will be called aacraid.
463 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
465 config SCSI_AIC7XXX_OLD
466 tristate "Adaptec AIC7xxx support (old driver)"
467 depends on (ISA || EISA || PCI ) && SCSI
469 WARNING This driver is an older aic7xxx driver and is no longer
470 under active development. Adaptec, Inc. is writing a new driver to
471 take the place of this one, and it is recommended that whenever
472 possible, people should use the new Adaptec written driver instead
473 of this one. This driver will eventually be phased out entirely.
475 This is support for the various aic7xxx based Adaptec SCSI
476 controllers. These include the 274x EISA cards; 284x VLB cards;
477 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
478 motherboard based SCSI controllers from Adaptec. It does not support
479 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
480 support them. It does not support the 2920 cards from Adaptec that
481 use the Future Domain SCSI controller chip. For those cards, you
482 need the "Future Domain 16xx SCSI support" driver.
484 In general, if the controller is based on an Adaptec SCSI controller
485 chip from the aic777x series or the aic78xx series, this driver
486 should work. The only exception is the 7810 which is specifically
487 not supported (that's the RAID controller chip on the AAA-13x
490 Note that the AHA2920 SCSI host adapter is *not* supported by this
491 driver; choose "Future Domain 16xx SCSI support" instead if you have
494 Information on the configuration options for this controller can be
495 found by checking the help file for each of the available
496 configuration options. You should read
497 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
498 contacting the maintainer with any questions. The SCSI-HOWTO,
499 available from <http://www.tldp.org/docs.html#howto>, can also
502 To compile this driver as a module, choose M here: the
503 module will be called aic7xxx_old.
505 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
506 source "drivers/scsi/aic94xx/Kconfig"
509 tristate "Adaptec I2O RAID support "
510 depends on SCSI && PCI && VIRT_TO_BUS
512 This driver supports all of Adaptec's I2O based RAID controllers as
513 well as the DPT SmartRaid V cards. This is an Adaptec maintained
514 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
516 To compile this driver as a module, choose M here: the
517 module will be called dpt_i2o.
520 tristate "AdvanSys SCSI support"
521 depends on SCSI && VIRT_TO_BUS
522 depends on ISA || EISA || PCI
524 This is a driver for all SCSI host adapters manufactured by
525 AdvanSys. It is documented in the kernel source in
526 <file:drivers/scsi/advansys.c>.
528 To compile this driver as a module, choose M here: the
529 module will be called advansys.
532 tristate "Always IN2000 SCSI support"
533 depends on ISA && SCSI
535 This is support for an ISA bus SCSI host adapter. You'll find more
536 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
537 out of the box, you may have to change the jumpers for IRQ or
540 To compile this driver as a module, choose M here: the
541 module will be called in2000.
544 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
545 depends on PCI && SCSI
547 This driver supports all of ARECA's SATA/SAS RAID controller cards.
548 This is an ARECA-maintained driver by Erich Chen.
549 If you have any problems, please mail to: <erich@areca.com.tw>.
550 Areca supports Linux RAID config tools.
551 Please link <http://www.areca.com.tw>
553 To compile this driver as a module, choose M here: the
554 module will be called arcmsr (modprobe arcmsr).
556 config SCSI_ARCMSR_AER
557 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
558 depends on SCSI_ARCMSR && PCIEAER
561 The advanced error reporting(AER) capability is "NOT" provided by
562 ARC1200/1201/1202 SATA RAID controllers cards.
563 If your card is one of ARC1200/1201/1202, please use the default setting, n.
564 If your card is other models, you could pick it
565 on condition that the kernel version is greater than 2.6.19.
566 This function is maintained driver by Nick Cheng. If you have any
567 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
568 To enable this function, choose Y here.
570 source "drivers/scsi/megaraid/Kconfig.megaraid"
573 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
574 depends on SCSI && PCI
576 This option enables support for HighPoint RocketRAID 3xxx/4xxx
579 To compile this driver as a module, choose M here; the module
580 will be called hptiop. If unsure, say N.
583 tristate "BusLogic SCSI support"
584 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
586 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
587 Adapters. Consult the SCSI-HOWTO, available from
588 <http://www.tldp.org/docs.html#howto>, and the files
589 <file:Documentation/scsi/BusLogic.txt> and
590 <file:Documentation/scsi/FlashPoint.txt> for more information.
591 Note that support for FlashPoint is only available for 32-bit
594 To compile this driver as a module, choose M here: the
595 module will be called BusLogic.
597 config SCSI_FLASHPOINT
598 bool "FlashPoint support"
599 depends on SCSI_BUSLOGIC && PCI && X86_32
601 This option allows you to add FlashPoint support to the
602 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
603 substantial, so users of MultiMaster Host Adapters may not
607 tristate "LibFC module"
608 depends on SCSI && SCSI_FC_ATTRS
610 Fibre Channel library module
613 tristate "DMX3191D SCSI support"
614 depends on PCI && SCSI
615 select SCSI_SPI_ATTRS
617 This is support for Domex DMX3191D SCSI Host Adapters.
619 To compile this driver as a module, choose M here: the
620 module will be called dmx3191d.
623 tristate "DTC3180/3280 SCSI support"
624 depends on ISA && SCSI
625 select SCSI_SPI_ATTRS
626 select CHECK_SIGNATURE
628 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
629 the SCSI-HOWTO, available from
630 <http://www.tldp.org/docs.html#howto>, and the file
631 <file:Documentation/scsi/dtc3x80.txt>.
633 To compile this driver as a module, choose M here: the
634 module will be called dtc.
637 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
638 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
640 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
641 ISA and all EISA I/O addresses are probed looking for the "EATA"
642 signature. The addresses of all the PCI SCSI controllers reported
643 by the PCI subsystem are probed as well.
645 You want to read the start of <file:drivers/scsi/eata.c> and the
646 SCSI-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here: the
650 module will be called eata.
652 config SCSI_EATA_TAGGED_QUEUE
653 bool "enable tagged command queueing"
656 This is a feature of SCSI-2 which improves performance: the host
657 adapter can send several SCSI commands to a device's queue even if
658 previous commands haven't finished yet.
659 This is equivalent to the "eata=tc:y" boot option.
661 config SCSI_EATA_LINKED_COMMANDS
662 bool "enable elevator sorting"
665 This option enables elevator sorting for all probed SCSI disks and
666 CD-ROMs. It definitely reduces the average seek distance when doing
667 random seeks, but this does not necessarily result in a noticeable
668 performance improvement: your mileage may vary...
669 This is equivalent to the "eata=lc:y" boot option.
671 config SCSI_EATA_MAX_TAGS
672 int "maximum number of queued commands"
676 This specifies how many SCSI commands can be maximally queued for
677 each probed SCSI device. You should reduce the default value of 16
678 only if you have disks with buggy or limited tagged command support.
679 Minimum is 2 and maximum is 62. This value is also the window size
680 used by the elevator sorting option above. The effective value used
681 by the driver for each probed SCSI device is reported at boot time.
682 This is equivalent to the "eata=mq:8" boot option.
685 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
686 depends on (ISA || EISA || PCI) && SCSI && BROKEN
688 This driver supports all EATA-PIO protocol compliant SCSI Host
689 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
690 host adapters could also use this driver but are discouraged from
691 doing so, since this driver only supports hard disks and lacks
692 numerous features. You might want to have a look at the SCSI-HOWTO,
693 available from <http://www.tldp.org/docs.html#howto>.
695 To compile this driver as a module, choose M here: the
696 module will be called eata_pio.
698 config SCSI_FUTURE_DOMAIN
699 tristate "Future Domain 16xx SCSI/AHA-2920A support"
700 depends on (ISA || PCI) && SCSI
701 select CHECK_SIGNATURE
703 This is support for Future Domain's 16-bit SCSI host adapters
704 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
705 other adapters based on the Future Domain chipsets (Quantum
706 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
707 It is explained in section 3.7 of the SCSI-HOWTO, available from
708 <http://www.tldp.org/docs.html#howto>.
710 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
711 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
712 controller support"). This Future Domain driver works with the older
713 Adaptec AHA-2920A boards with a Future Domain chip on them.
715 To compile this driver as a module, choose M here: the
716 module will be called fdomain.
719 tristate "Future Domain MCS-600/700 SCSI support"
720 depends on MCA_LEGACY && SCSI
722 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
723 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
724 is identical to the MCS 700 and hence also supported by this driver.
725 This driver also supports the Reply SB16/SCSI card (the SCSI part).
726 It supports multiple adapters in the same system.
728 To compile this driver as a module, choose M here: the
729 module will be called fd_mcs.
732 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
733 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
735 Formerly called GDT SCSI Disk Array Controller Support.
737 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
738 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
739 in the kernel source in <file:drivers/scsi/gdth.c> and
740 <file:drivers/scsi/gdth.h>.
742 To compile this driver as a module, choose M here: the
743 module will be called gdth.
745 config SCSI_GENERIC_NCR5380
746 tristate "Generic NCR5380/53c400 SCSI PIO support"
747 depends on ISA && SCSI
748 select SCSI_SPI_ATTRS
750 This is a driver for the old NCR 53c80 series of SCSI controllers
751 on boards using PIO. Most boards such as the Trantor T130 fit this
752 category, along with a large number of ISA 8bit controllers shipped
753 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
754 you should select the specific driver for that card rather than
755 generic 5380 support.
757 It is explained in section 3.8 of the SCSI-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
759 of the box, you may have to change some settings in
760 <file:drivers/scsi/g_NCR5380.h>.
762 To compile this driver as a module, choose M here: the
763 module will be called g_NCR5380.
765 config SCSI_GENERIC_NCR5380_MMIO
766 tristate "Generic NCR5380/53c400 SCSI MMIO support"
767 depends on ISA && SCSI
768 select SCSI_SPI_ATTRS
770 This is a driver for the old NCR 53c80 series of SCSI controllers
771 on boards using memory mapped I/O.
772 It is explained in section 3.8 of the SCSI-HOWTO, available from
773 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
774 of the box, you may have to change some settings in
775 <file:drivers/scsi/g_NCR5380.h>.
777 To compile this driver as a module, choose M here: the
778 module will be called g_NCR5380_mmio.
780 config SCSI_GENERIC_NCR53C400
781 bool "Enable NCR53c400 extensions"
782 depends on SCSI_GENERIC_NCR5380
784 This enables certain optimizations for the NCR53c400 SCSI cards.
785 You might as well try it out. Note that this driver will only probe
786 for the Trantor T130B in its default configuration; you might have
787 to pass a command line option to the kernel at boot time if it does
788 not detect your card. See the file
789 <file:Documentation/scsi/g_NCR5380.txt> for details.
792 tristate "IBMMCA SCSI support"
793 depends on MCA && SCSI
795 This is support for the IBM SCSI adapter found in many of the PS/2
796 series computers. These machines have an MCA bus, so you need to
797 answer Y to "MCA support" as well and read
798 <file:Documentation/mca.txt>.
800 If the adapter isn't found during boot (a common problem for models
801 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
802 option, where <pun> is the id of the SCSI subsystem (usually 7, but
803 if that doesn't work check your reference diskette). Owners of
804 model 95 with a LED-matrix-display can in addition activate some
805 activity info like under OS/2, but more informative, by setting
806 'ibmmcascsi=display' as an additional kernel parameter. Try "man
807 bootparam" or see the documentation of your boot loader about how to
808 pass options to the kernel.
810 To compile this driver as a module, choose M here: the
811 module will be called ibmmca.
813 config IBMMCA_SCSI_ORDER_STANDARD
814 bool "Standard SCSI-order"
815 depends on SCSI_IBMMCA
817 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
818 are assigned to the drive letters, starting with the lowest SCSI-id
819 (physical number -- pun) to be drive C:, as seen from DOS and
820 similar operating systems. When looking into papers describing the
821 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
822 The SCSI-standard follows a hardware-hierarchy which says that id 7
823 has the highest priority and id 0 the lowest. Therefore, the host
824 adapters are still today everywhere placed as SCSI-id 7 by default.
825 In the SCSI-standard, the drive letters express the priority of the
826 disk. C: should be the hard disk, or a partition on it, with the
827 highest priority. This must therefore be the disk with the highest
828 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
829 original definition of the SCSI-standard as also industrial- and
830 process-control-machines, like VME-CPUs running under realtime-OSes
831 (e.g. LynxOS, OS9) do.
833 If you like to run Linux on your MCA-machine with the same
834 assignment of hard disks as seen from e.g. DOS or OS/2 on your
835 machine, which is in addition conformant to the SCSI-standard, you
836 must say Y here. This is also necessary for MCA-Linux users who want
837 to keep downward compatibility to older releases of the
838 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
841 If you like to have the lowest SCSI-id assigned as drive C:, as
842 modern SCSI-BIOSes do, which does not conform to the standard, but
843 is widespread and common in the PC-world of today, you must say N
844 here. If unsure, say Y.
846 config IBMMCA_SCSI_DEV_RESET
847 bool "Reset SCSI-devices at boottime"
848 depends on SCSI_IBMMCA
850 By default, SCSI-devices are reset when the machine is powered on.
851 However, some devices exist, like special-control-devices,
852 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
853 not reset when switched on. If you say Y here, each device connected
854 to your SCSI-bus will be issued a reset-command after it has been
855 probed, while the kernel is booting. This may cause problems with
856 more modern devices, like hard disks, which do not appreciate these
857 reset commands, and can cause your system to hang. So say Y only if
858 you know that one of your older devices needs it; N is the safe
862 tristate "IBM ServeRAID support"
863 depends on PCI && SCSI
865 This is support for the IBM ServeRAID hardware RAID controllers.
866 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
867 for more information. If this driver does not work correctly
868 without modification please contact the author by email at
869 <ipslinux@adaptec.com>.
871 To compile this driver as a module, choose M here: the
872 module will be called ips.
875 tristate "IBM Virtual SCSI support"
876 depends on PPC_PSERIES || PPC_ISERIES
877 select SCSI_SRP_ATTRS
879 This is the IBM POWER Virtual SCSI Client
881 To compile this driver as a module, choose M here: the
882 module will be called ibmvscsic.
884 config SCSI_IBMVSCSIS
885 tristate "IBM Virtual SCSI Server support"
886 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
888 This is the SRP target driver for IBM pSeries virtual environments.
890 The userspace component needed to initialize the driver and
891 documentation can be found:
893 http://stgt.berlios.de/
895 To compile this driver as a module, choose M here: the
896 module will be called ibmvstgt.
899 tristate "IBM Virtual FC support"
900 depends on PPC_PSERIES && SCSI
903 This is the IBM POWER Virtual FC Client
905 To compile this driver as a module, choose M here: the
906 module will be called ibmvfc.
908 config SCSI_IBMVFC_TRACE
909 bool "enable driver internal trace"
910 depends on SCSI_IBMVFC
913 If you say Y here, the driver will trace all commands issued
914 to the adapter. Performance impact is minimal. Trace can be
915 dumped using /sys/class/scsi_host/hostXX/trace.
918 tristate "Initio 9100U(W) support"
919 depends on PCI && SCSI
921 This is support for the Initio 91XXU(W) SCSI host adapter. Please
922 read the SCSI-HOWTO, available from
923 <http://www.tldp.org/docs.html#howto>.
925 To compile this driver as a module, choose M here: the
926 module will be called initio.
929 tristate "Initio INI-A100U2W support"
930 depends on PCI && SCSI
932 This is support for the Initio INI-A100U2W SCSI host adapter.
933 Please read the SCSI-HOWTO, available from
934 <http://www.tldp.org/docs.html#howto>.
936 To compile this driver as a module, choose M here: the
937 module will be called a100u2w.
940 tristate "IOMEGA parallel port (ppa - older drives)"
941 depends on SCSI && PARPORT_PC
943 This driver supports older versions of IOMEGA's parallel port ZIP
944 drive (a 100 MB removable media device).
946 Note that you can say N here if you have the SCSI version of the ZIP
947 drive: it will be supported automatically if you said Y to the
948 generic "SCSI disk support", above.
950 If you have the ZIP Plus drive or a more recent parallel port ZIP
951 drive (if the supplied cable with the drive is labeled "AutoDetect")
952 then you should say N here and Y to "IOMEGA parallel port (imm -
953 newer drives)", below.
955 For more information about this driver and how to use it you should
956 read the file <file:Documentation/scsi/ppa.txt>. You should also read
957 the SCSI-HOWTO, which is available from
958 <http://www.tldp.org/docs.html#howto>. If you use this driver,
959 you will still be able to use the parallel port for other tasks,
960 such as a printer; it is safe to compile both drivers into the
963 To compile this driver as a module, choose M here: the
964 module will be called ppa.
967 tristate "IOMEGA parallel port (imm - newer drives)"
968 depends on SCSI && PARPORT_PC
970 This driver supports newer versions of IOMEGA's parallel port ZIP
971 drive (a 100 MB removable media device).
973 Note that you can say N here if you have the SCSI version of the ZIP
974 drive: it will be supported automatically if you said Y to the
975 generic "SCSI disk support", above.
977 If you have the ZIP Plus drive or a more recent parallel port ZIP
978 drive (if the supplied cable with the drive is labeled "AutoDetect")
979 then you should say Y here; if you have an older ZIP drive, say N
980 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
982 For more information about this driver and how to use it you should
983 read the file <file:Documentation/scsi/ppa.txt>. You should also read
984 the SCSI-HOWTO, which is available from
985 <http://www.tldp.org/docs.html#howto>. If you use this driver,
986 you will still be able to use the parallel port for other tasks,
987 such as a printer; it is safe to compile both drivers into the
990 To compile this driver as a module, choose M here: the
991 module will be called imm.
993 config SCSI_IZIP_EPP16
994 bool "ppa/imm option - Use slow (but safe) EPP-16"
995 depends on SCSI_PPA || SCSI_IMM
997 EPP (Enhanced Parallel Port) is a standard for parallel ports which
998 allows them to act as expansion buses that can handle up to 64
1001 Some parallel port chipsets are slower than their motherboard, and
1002 so we have to control the state of the chipset's FIFO queue every
1003 now and then to avoid data loss. This will be done if you say Y
1006 Generally, saying Y is the safe option and slows things down a bit.
1008 config SCSI_IZIP_SLOW_CTR
1009 bool "ppa/imm option - Assume slow parport control register"
1010 depends on SCSI_PPA || SCSI_IMM
1012 Some parallel ports are known to have excessive delays between
1013 changing the parallel port control register and good data being
1014 available on the parallel port data/status register. This option
1015 forces a small delay (1.0 usec to be exact) after changing the
1016 control register to let things settle out. Enabling this option may
1017 result in a big drop in performance but some very old parallel ports
1018 (found in 386 vintage machines) will not work properly.
1020 Generally, saying N is fine.
1023 tristate "Marvell 88SE6440 SAS/SATA support"
1024 depends on PCI && SCSI
1025 select SCSI_SAS_LIBSAS
1027 This driver supports Marvell SAS/SATA PCI devices.
1029 To compiler this driver as a module, choose M here: the module
1030 will be called mvsas.
1032 config SCSI_NCR53C406A
1033 tristate "NCR53c406a SCSI support"
1034 depends on ISA && SCSI
1036 This is support for the NCR53c406a SCSI host adapter. For user
1037 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1038 in the kernel source. Also read the SCSI-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here: the
1042 module will be called NCR53c406.
1044 config SCSI_NCR_D700
1045 tristate "NCR Dual 700 MCA SCSI support"
1046 depends on MCA && SCSI
1047 select SCSI_SPI_ATTRS
1049 This is a driver for the MicroChannel Dual 700 card produced by
1050 NCR and commonly used in 345x/35xx/4100 class machines. It always
1051 tries to negotiate sync and uses tag command queueing.
1053 Unless you have an NCR manufactured machine, the chances are that
1054 you do not have this SCSI card, so say N.
1057 tristate "HP Lasi SCSI support for 53c700/710"
1058 depends on GSC && SCSI
1059 select SCSI_SPI_ATTRS
1061 This is a driver for the SCSI controller in the Lasi chip found in
1062 many PA-RISC workstations & servers. If you do not know whether you
1063 have a Lasi chip, it is safe to say "Y" here.
1065 config SCSI_SNI_53C710
1066 tristate "SNI RM SCSI support for 53c710"
1067 depends on SNI_RM && SCSI
1068 select SCSI_SPI_ATTRS
1069 select 53C700_LE_ON_BE
1071 This is a driver for the onboard SCSI controller found in older
1072 SNI RM workstations & servers.
1074 config 53C700_LE_ON_BE
1076 depends on SCSI_LASI700
1080 tristate "Promise SuperTrak EX Series support"
1081 depends on PCI && SCSI
1083 This driver supports Promise SuperTrak EX series storage controllers.
1085 Promise provides Linux RAID configuration utility for these
1086 controllers. Please visit <http://www.promise.com> to download.
1088 To compile this driver as a module, choose M here: the
1089 module will be called stex.
1091 config 53C700_BE_BUS
1093 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1096 config SCSI_SYM53C8XX_2
1097 tristate "SYM53C8XX Version 2 SCSI support"
1098 depends on PCI && SCSI
1099 select SCSI_SPI_ATTRS
1101 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1102 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1103 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1104 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1105 controllers; you need to use the Fusion MPT driver for that.
1107 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1110 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1111 int "DMA addressing mode"
1112 depends on SCSI_SYM53C8XX_2
1115 This option only applies to PCI-SCSI chips that are PCI DAC
1116 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1118 When set to 0, the driver will program the chip to only perform
1119 32-bit DMA. When set to 1, the chip will be able to perform DMA
1120 to addresses up to 1TB. When set to 2, the driver supports the
1121 full 64-bit DMA address range, but can only address 16 segments
1122 of 4 GB each. This limits the total addressable range to 64 GB.
1124 Most machines with less than 4GB of memory should use a setting
1125 of 0 for best performance. If your machine has 4GB of memory
1126 or more, you should set this option to 1 (the default).
1128 The still experimental value 2 (64 bit DMA addressing with 16
1129 x 4GB segments limitation) can be used on systems that require
1130 PCI address bits past bit 39 to be set for the addressing of
1131 memory using PCI DAC cycles.
1133 config SCSI_SYM53C8XX_DEFAULT_TAGS
1134 int "Default tagged command queue depth"
1135 depends on SCSI_SYM53C8XX_2
1138 This is the default value of the command queue depth the
1139 driver will announce to the generic SCSI layer for devices
1140 that support tagged command queueing. This value can be changed
1141 from the boot command line. This is a soft limit that cannot
1142 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1144 config SCSI_SYM53C8XX_MAX_TAGS
1145 int "Maximum number of queued commands"
1146 depends on SCSI_SYM53C8XX_2
1149 This option allows you to specify the maximum number of commands
1150 that can be queued to any device, when tagged command queuing is
1151 possible. The driver supports up to 256 queued commands per device.
1152 This value is used as a compiled-in hard limit.
1154 config SCSI_SYM53C8XX_MMIO
1155 bool "Use memory mapped IO"
1156 depends on SCSI_SYM53C8XX_2
1159 Memory mapped IO is faster than Port IO. Most people should
1160 answer Y here, but some machines may have problems. If you have
1161 to answer N here, please report the problem to the maintainer.
1164 tristate "IBM Power Linux RAID adapter support"
1165 depends on PCI && SCSI && ATA
1168 This driver supports the IBM Power Linux family RAID adapters.
1169 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1170 as IBM iSeries 5702, 5703, 5709, and 570A.
1172 config SCSI_IPR_TRACE
1173 bool "enable driver internal trace"
1177 If you say Y here, the driver will trace all commands issued
1178 to the adapter. Performance impact is minimal. Trace can be
1179 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1181 config SCSI_IPR_DUMP
1182 bool "enable adapter dump support"
1186 If you say Y here, the driver will support adapter crash dump.
1187 If you enable this support, the iprdump daemon can be used
1188 to capture adapter failure analysis information.
1191 tristate "Zalon SCSI support"
1192 depends on GSC && SCSI
1193 select SCSI_SPI_ATTRS
1195 The Zalon is a GSC/HSC bus interface chip that sits between the
1196 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1197 C110, J200, J210 and some D, K & R-class machines. It's also
1198 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1199 Say Y here if you have one of these machines or cards.
1201 config SCSI_NCR_Q720
1202 tristate "NCR Quad 720 MCA SCSI support"
1203 depends on MCA && SCSI
1204 select SCSI_SPI_ATTRS
1206 This is a driver for the MicroChannel Quad 720 card produced by
1207 NCR and commonly used in 345x/35xx/4100 class machines. It always
1208 tries to negotiate sync and uses tag command queueing.
1210 Unless you have an NCR manufactured machine, the chances are that
1211 you do not have this SCSI card, so say N.
1213 config SCSI_NCR53C8XX_DEFAULT_TAGS
1214 int "default tagged command queue depth"
1215 depends on SCSI_ZALON || SCSI_NCR_Q720
1218 "Tagged command queuing" is a feature of SCSI-2 which improves
1219 performance: the host adapter can send several SCSI commands to a
1220 device's queue even if previous commands haven't finished yet.
1221 Because the device is intelligent, it can optimize its operations
1222 (like head positioning) based on its own request queue. Some SCSI
1223 devices don't implement this properly; if you want to disable this
1224 feature, enter 0 or 1 here (it doesn't matter which).
1226 The default value is 8 and should be supported by most hard disks.
1227 This value can be overridden from the boot command line using the
1228 'tags' option as follows (example):
1229 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1230 4, set queue depth to 16 for target 2 and target 3 on controller 0
1231 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1233 The normal answer therefore is to go with the default 8 and to use
1234 a boot command line option for devices that need to use a different
1235 command queue depth.
1237 There is no safe option other than using good SCSI devices.
1239 config SCSI_NCR53C8XX_MAX_TAGS
1240 int "maximum number of queued commands"
1241 depends on SCSI_ZALON || SCSI_NCR_Q720
1244 This option allows you to specify the maximum number of commands
1245 that can be queued to any device, when tagged command queuing is
1246 possible. The default value is 32. Minimum is 2, maximum is 64.
1247 Modern hard disks are able to support 64 tags and even more, but
1248 do not seem to be faster when more than 32 tags are being used.
1250 So, the normal answer here is to go with the default value 32 unless
1251 you are using very large hard disks with large cache (>= 1 MB) that
1252 are able to take advantage of more than 32 tagged commands.
1254 There is no safe option and the default answer is recommended.
1256 config SCSI_NCR53C8XX_SYNC
1257 int "synchronous transfers frequency in MHz"
1258 depends on SCSI_ZALON || SCSI_NCR_Q720
1261 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1262 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1263 are respectively the maximum data transfer rates in mega-transfers
1264 per second for each class. For example, a FAST-20 Wide 16 device is
1265 able to transfer data at 20 million 16 bit packets per second for a
1266 total rate of 40 MB/s.
1268 You may specify 0 if you want to only use asynchronous data
1269 transfers. This is the safest and slowest option. Otherwise, specify
1270 a value between 5 and 80, depending on the capability of your SCSI
1271 controller. The higher the number, the faster the data transfer.
1272 Note that 80 should normally be ok since the driver decreases the
1273 value automatically according to the controller's capabilities.
1275 Your answer to this question is ignored for controllers with NVRAM,
1276 since the driver will get this information from the user set-up. It
1277 also can be overridden using a boot setup option, as follows
1278 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1279 for FAST-20 synchronous data transfer (20 mega-transfers per
1282 The normal answer therefore is not to go with the default but to
1283 select the maximum value 80 allowing the driver to use the maximum
1284 value supported by each controller. If this causes problems with
1285 your SCSI devices, you should come back and decrease the value.
1287 There is no safe option other than using good cabling, right
1288 terminations and SCSI conformant devices.
1290 config SCSI_NCR53C8XX_NO_DISCONNECT
1291 bool "not allow targets to disconnect"
1292 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1294 This option is only provided for safety if you suspect some SCSI
1295 device of yours to not support properly the target-disconnect
1296 feature. In that case, you would say Y here. In general however, to
1297 not allow targets to disconnect is not reasonable if there is more
1298 than 1 device on a SCSI bus. The normal answer therefore is N.
1301 tristate "PAS16 SCSI support"
1302 depends on ISA && SCSI
1303 select SCSI_SPI_ATTRS
1305 This is support for a SCSI host adapter. It is explained in section
1306 3.10 of the SCSI-HOWTO, available from
1307 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1308 of the box, you may have to change some settings in
1309 <file:drivers/scsi/pas16.h>.
1311 To compile this driver as a module, choose M here: the
1312 module will be called pas16.
1314 config SCSI_QLOGIC_FAS
1315 tristate "Qlogic FAS SCSI support"
1316 depends on ISA && SCSI
1318 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1319 FastSCSI! cards as well as any other card based on the FASXX chip
1320 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1322 This driver does NOT support the PCI versions of these cards. The
1323 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1324 SCSI support"), below.
1326 Information about this driver is contained in
1327 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1328 SCSI-HOWTO, available from
1329 <http://www.tldp.org/docs.html#howto>.
1331 To compile this driver as a module, choose M here: the
1332 module will be called qlogicfas.
1334 config SCSI_QLOGIC_1280
1335 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1336 depends on PCI && SCSI
1338 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1340 To compile this driver as a module, choose M here: the
1341 module will be called qla1280.
1343 config SCSI_QLOGICPTI
1344 tristate "PTI Qlogic, ISP Driver"
1345 depends on SBUS && SCSI
1347 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1348 controllers are known under Solaris as qpti and in the openprom as
1349 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1350 driven by a different driver.
1352 To compile this driver as a module, choose M here: the
1353 module will be called qlogicpti.
1355 source "drivers/scsi/qla2xxx/Kconfig"
1356 source "drivers/scsi/qla4xxx/Kconfig"
1359 tristate "Emulex LightPulse Fibre Channel Support"
1360 depends on PCI && SCSI
1361 select SCSI_FC_ATTRS
1363 This lpfc driver supports the Emulex LightPulse
1364 Family of Fibre Channel PCI host adapters.
1366 config SCSI_LPFC_DEBUG_FS
1367 bool "Emulex LightPulse Fibre Channel debugfs Support"
1368 depends on SCSI_LPFC && DEBUG_FS
1370 This makes debugging infomation from the lpfc driver
1371 available via the debugfs filesystem.
1374 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1375 depends on (EISA || MCA) && SCSI
1376 select SCSI_SPI_ATTRS
1378 This driver for NCR53c710 based SCSI host adapters.
1380 It currently supports Compaq EISA cards and NCR MCA cards
1382 config SCSI_SYM53C416
1383 tristate "Symbios 53c416 SCSI support"
1384 depends on ISA && SCSI
1386 This is support for the sym53c416 SCSI host adapter, the SCSI
1387 adapter that comes with some HP scanners. This driver requires that
1388 the sym53c416 is configured first using some sort of PnP
1389 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1390 are using isapnp then you need to compile this driver as a module
1391 and then load it using insmod after isapnp has run. The parameters
1392 of the configured card(s) should be passed to the driver. The format
1395 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1397 To compile this driver as a module, choose M here: the
1398 module will be called sym53c416.
1401 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1402 depends on PCI && SCSI && EXPERIMENTAL
1404 This driver supports PCI SCSI host adapters based on the ASIC
1405 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1407 This driver works, but is still in experimental status. So better
1408 have a bootable disk and a backup in case of emergency.
1410 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1412 To compile this driver as a module, choose M here: the
1413 module will be called dc395x.
1416 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1417 depends on PCI && SCSI
1419 This driver supports PCI SCSI host adapters based on the Am53C974A
1420 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1421 PCscsi/PCnet (Am53/79C974) solutions.
1423 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1425 Note that this driver does NOT support Tekram DC390W/U/F, which are
1426 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1428 To compile this driver as a module, choose M here: the
1429 module will be called tmscsim.
1432 tristate "Trantor T128/T128F/T228 SCSI support"
1433 depends on ISA && SCSI
1434 select SCSI_SPI_ATTRS
1435 select CHECK_SIGNATURE
1437 This is support for a SCSI host adapter. It is explained in section
1438 3.11 of the SCSI-HOWTO, available from
1439 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1440 of the box, you may have to change some settings in
1441 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1442 Adaptec, and some former Trantor products are being sold under the
1445 To compile this driver as a module, choose M here: the
1446 module will be called t128.
1449 tristate "UltraStor 14F/34F support"
1450 depends on ISA && SCSI && ISA_DMA_API
1452 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1453 The source at <file:drivers/scsi/u14-34f.c> contains some
1454 information about this hardware. If the driver doesn't work out of
1455 the box, you may have to change some settings in
1456 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1457 <http://www.tldp.org/docs.html#howto>. Note that there is also
1458 another driver for the same hardware: "UltraStor SCSI support",
1459 below. You should say Y to both only if you want 24F support as
1462 To compile this driver as a module, choose M here: the
1463 module will be called u14-34f.
1465 config SCSI_U14_34F_TAGGED_QUEUE
1466 bool "enable tagged command queueing"
1467 depends on SCSI_U14_34F
1469 This is a feature of SCSI-2 which improves performance: the host
1470 adapter can send several SCSI commands to a device's queue even if
1471 previous commands haven't finished yet.
1472 This is equivalent to the "u14-34f=tc:y" boot option.
1474 config SCSI_U14_34F_LINKED_COMMANDS
1475 bool "enable elevator sorting"
1476 depends on SCSI_U14_34F
1478 This option enables elevator sorting for all probed SCSI disks and
1479 CD-ROMs. It definitely reduces the average seek distance when doing
1480 random seeks, but this does not necessarily result in a noticeable
1481 performance improvement: your mileage may vary...
1482 This is equivalent to the "u14-34f=lc:y" boot option.
1484 config SCSI_U14_34F_MAX_TAGS
1485 int "maximum number of queued commands"
1486 depends on SCSI_U14_34F
1489 This specifies how many SCSI commands can be maximally queued for
1490 each probed SCSI device. You should reduce the default value of 8
1491 only if you have disks with buggy or limited tagged command support.
1492 Minimum is 2 and maximum is 14. This value is also the window size
1493 used by the elevator sorting option above. The effective value used
1494 by the driver for each probed SCSI device is reported at boot time.
1495 This is equivalent to the "u14-34f=mq:8" boot option.
1497 config SCSI_ULTRASTOR
1498 tristate "UltraStor SCSI support"
1499 depends on X86 && ISA && SCSI
1501 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1502 adapter family. This driver is explained in section 3.12 of the
1503 SCSI-HOWTO, available from
1504 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1505 of the box, you may have to change some settings in
1506 <file:drivers/scsi/ultrastor.h>.
1508 Note that there is also another driver for the same hardware:
1509 "UltraStor 14F/34F support", above.
1511 To compile this driver as a module, choose M here: the
1512 module will be called ultrastor.
1515 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1516 depends on PCI && SCSI && !64BIT
1518 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1519 SCSI host adapter. Please read the SCSI-HOWTO, available from
1520 <http://www.tldp.org/docs.html#howto>.
1522 To compile this driver as a module, choose M here: the
1523 module will be called nsp32.
1526 tristate "SCSI debugging host simulator"
1529 This is a host adapter simulator that can simulate multiple hosts
1530 each with multiple dummy SCSI devices (disks). It defaults to one
1531 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1532 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1533 dummy disks are simulated, they share the same kernel RAM for
1534 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1535 information. This driver is primarily of use to those testing the
1536 SCSI and block subsystems. If unsure, say N.
1539 tristate "MESH (Power Mac internal SCSI) support"
1540 depends on PPC32 && PPC_PMAC && SCSI
1542 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1543 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1544 other Power Macintoshes do). Say Y to include support for this SCSI
1547 To compile this driver as a module, choose M here: the
1548 module will be called mesh.
1550 config SCSI_MESH_SYNC_RATE
1551 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1552 depends on SCSI_MESH
1555 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1556 drives a bus which is entirely internal to the machine (such as the
1557 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1558 operation at up to 10 MB/s. On machines where the SCSI bus
1559 controlled by the MESH can have external devices connected, it is
1560 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1561 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1562 to disable synchronous operation.
1564 config SCSI_MESH_RESET_DELAY_MS
1565 int "initial bus reset delay (ms) (0 = no reset)"
1566 depends on SCSI_MESH
1569 config SCSI_MAC53C94
1570 tristate "53C94 (Power Mac external SCSI) support"
1571 depends on PPC32 && PPC_PMAC && SCSI
1573 On Power Macintoshes (and clones) with two SCSI buses, the external
1574 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1575 machines which only have one SCSI bus, such as the 7200, also use
1576 the 53C94. Say Y to include support for the 53C94.
1578 To compile this driver as a module, choose M here: the
1579 module will be called mac53c94.
1581 source "drivers/scsi/arm/Kconfig"
1584 bool "MIPS JAZZ FAS216 SCSI support"
1585 depends on MACH_JAZZ && SCSI
1586 select SCSI_SPI_ATTRS
1588 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1589 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1593 tristate "A3000 WD33C93A support"
1594 depends on AMIGA && SCSI
1596 If you have an Amiga 3000 and have SCSI devices connected to the
1597 built-in SCSI controller, say Y. Otherwise, say N.
1599 To compile this driver as a module, choose M here: the
1600 module will be called a3000.
1603 tristate "A2091/A590 WD33C93A support"
1604 depends on ZORRO && SCSI
1606 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1609 To compile this driver as a module, choose M here: the
1610 module will be called a2091.
1613 tristate "GVP Series II WD33C93A support"
1614 depends on ZORRO && SCSI
1616 If you have a Great Valley Products Series II SCSI controller,
1617 answer Y. Also say Y if you have a later model of GVP SCSI
1618 controller (such as the GVP A4008 or a Combo board). Otherwise,
1619 answer N. This driver does NOT work for the T-Rex series of
1620 accelerators from TekMagic and GVP-M.
1622 To compile this driver as a module, choose M here: the
1623 module will be called gvp11.
1626 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1627 depends on AMIGA && SCSI && EXPERIMENTAL
1628 select SCSI_SPI_ATTRS
1630 If you have an Amiga 4000T and have SCSI devices connected to the
1631 built-in SCSI controller, say Y. Otherwise, say N.
1633 To compile this driver as a module, choose M here: the
1634 module will be called a4000t.
1636 config SCSI_ZORRO7XX
1637 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1638 depends on ZORRO && SCSI && EXPERIMENTAL
1639 select SCSI_SPI_ATTRS
1641 Support for various NCR53c710-based SCSI controllers on Zorro
1642 expansion boards for the Amiga.
1644 - the Amiga 4091 Zorro III SCSI-2 controller,
1645 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1647 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1648 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1649 accelerator card for the Amiga 1200,
1650 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1653 tristate "Atari native SCSI support"
1654 depends on ATARI && SCSI
1655 select SCSI_SPI_ATTRS
1658 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1659 Falcon, ...) say Y to get it supported. Of course also, if you have
1660 a compatible SCSI controller (e.g. for Medusa).
1662 To compile this driver as a module, choose M here: the
1663 module will be called atari_scsi.
1665 This driver supports both styles of NCR integration into the
1666 system: the TT style (separate DMA), and the Falcon style (via
1667 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1668 in the Hades (without DMA).
1670 config ATARI_SCSI_TOSHIBA_DELAY
1671 bool "Long delays for Toshiba CD-ROMs"
1672 depends on ATARI_SCSI
1674 This option increases the delay after a SCSI arbitration to
1675 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1676 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1677 would impact performance a bit, so say N.
1679 config ATARI_SCSI_RESET_BOOT
1680 bool "Reset SCSI-devices at boottime"
1681 depends on ATARI_SCSI
1683 Reset the devices on your Atari whenever it boots. This makes the
1684 boot process fractionally longer but may assist recovery from errors
1685 that leave the devices with SCSI operations partway completed.
1688 bool "Macintosh NCR5380 SCSI"
1689 depends on MAC && SCSI=y
1690 select SCSI_SPI_ATTRS
1692 This is the NCR 5380 SCSI controller included on most of the 68030
1693 based Macintoshes. If you have one of these say Y and read the
1694 SCSI-HOWTO, available from
1695 <http://www.tldp.org/docs.html#howto>.
1698 tristate "Macintosh NCR53c9[46] SCSI"
1699 depends on MAC && SCSI
1700 select SCSI_SPI_ATTRS
1702 This is the NCR 53c9x SCSI controller found on most of the 68040
1705 To compile this driver as a module, choose M here: the module
1706 will be called mac_esp.
1709 bool "WD33C93 SCSI driver for MVME147"
1710 depends on MVME147 && SCSI=y
1711 select SCSI_SPI_ATTRS
1713 Support for the on-board SCSI controller on the Motorola MVME147
1714 single-board computer.
1717 tristate "NCR53C710 SCSI driver for MVME16x"
1718 depends on MVME16x && SCSI
1719 select SCSI_SPI_ATTRS
1721 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1722 SCSI controller chip. Almost everyone using one of these boards
1723 will want to say Y to this question.
1725 config BVME6000_SCSI
1726 tristate "NCR53C710 SCSI driver for BVME6000"
1727 depends on BVME6000 && SCSI
1728 select SCSI_SPI_ATTRS
1730 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1731 SCSI controller chip. Almost everyone using one of these boards
1732 will want to say Y to this question.
1735 tristate "Sun3 NCR5380 SCSI"
1736 depends on SUN3 && SCSI
1737 select SCSI_SPI_ATTRS
1739 This option will enable support for the OBIO (onboard io) NCR5380
1740 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1741 "Sun3" type VME scsi controllers also based on the NCR5380.
1742 General Linux information on the Sun 3 series (now discontinued)
1743 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1746 bool "Sun3x ESP SCSI"
1747 depends on SUN3X && SCSI=y
1748 select SCSI_SPI_ATTRS
1750 The ESP was an on-board SCSI controller used on Sun 3/80
1751 machines. Say Y here to compile in support for it.
1754 tristate "Sparc ESP Scsi Driver"
1755 depends on SBUS && SCSI
1756 select SCSI_SPI_ATTRS
1758 This is the driver for the Sun ESP SCSI host adapter. The ESP
1759 chipset is present in most SPARC SBUS-based computers and
1760 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1761 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1763 To compile this driver as a module, choose M here: the
1764 module will be called sun_esp.
1767 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1768 depends on S390 && QDIO && SCSI
1769 select SCSI_FC_ATTRS
1771 If you want to access SCSI devices attached to your IBM eServer
1772 zSeries by means of Fibre Channel interfaces say Y.
1773 For details please refer to the documentation provided by IBM at
1774 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1776 This driver is also available as a module. This module will be
1777 called zfcp. If you want to compile it as a module, say M here
1778 and read <file:Documentation/kbuild/modules.txt>.
1781 tristate "SCSI RDMA Protocol helper library"
1782 depends on SCSI && PCI
1785 If you wish to use SRP target drivers, say Y.
1787 To compile this driver as a module, choose M here: the
1788 module will be called libsrp.
1790 endif # SCSI_LOWLEVEL
1792 source "drivers/scsi/pcmcia/Kconfig"
1794 source "drivers/scsi/device_handler/Kconfig"