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"
67 If you want to use SCSI hard disks, Fibre Channel disks,
68 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
69 USB storage or the SCSI or parallel port version of
70 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
71 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
72 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
75 To compile this driver as a module, choose M here and read
76 <file:Documentation/scsi/scsi.txt>.
77 The module will be called sd_mod.
79 Do not compile this driver as a module if your root file system
80 (the one containing the directory /) is located on a SCSI disk.
81 In this case, do not compile the driver for your SCSI host adapter
82 (below) as a module either.
85 tristate "SCSI tape support"
88 If you want to use a SCSI tape drive under Linux, say Y and read the
89 SCSI-HOWTO, available from
90 <http://www.tldp.org/docs.html#howto>, and
91 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
94 To compile this driver as a module, choose M here and read
95 <file:Documentation/scsi/scsi.txt>. The module will be called st.
98 tristate "SCSI OnStream SC-x0 tape support"
101 The OnStream SC-x0 SCSI tape drives cannot be driven by the
102 standard st driver, but instead need this special osst driver and
103 use the /dev/osstX char device nodes (major 206). Via usb-storage
104 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
105 as well. Note that there is also a second generation of OnStream
106 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
107 tapes (QIC-157) and can be driven by the standard driver st.
108 For more information, you may have a look at the SCSI-HOWTO
109 <http://www.tldp.org/docs.html#howto> and
110 <file:Documentation/scsi/osst.txt> in the kernel source.
111 More info on the OnStream driver may be found on
112 <http://linux1.onstream.nl/test/>
113 Please also have a look at the standard st docu, as most of it
114 applies to osst as well.
116 To compile this driver as a module, choose M here and read
117 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
120 tristate "SCSI CDROM support"
123 If you want to use a SCSI or FireWire CD-ROM under Linux,
124 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
125 <http://www.tldp.org/docs.html#howto>. Also make sure to say
126 Y or M to "ISO 9660 CD-ROM file system support" later.
128 To compile this driver as a module, choose M here and read
129 <file:Documentation/scsi/scsi.txt>.
130 The module will be called sr_mod.
132 config BLK_DEV_SR_VENDOR
133 bool "Enable vendor-specific extensions (for SCSI CDROM)"
134 depends on BLK_DEV_SR
136 This enables the usage of vendor specific SCSI commands. This is
137 required to support multisession CDs with old NEC/TOSHIBA cdrom
138 drives (and HP Writers). If you have such a drive and get the first
139 session only, try saying Y here; everybody else says N.
142 tristate "SCSI generic support"
145 If you want to use SCSI scanners, synthesizers or CD-writers or just
146 about anything having "SCSI" in its name other than hard disks,
147 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
148 directly, so you need some additional software which knows how to
149 talk to these devices using the SCSI protocol:
151 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
152 writer software look at Cdrtools
153 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
154 and for burning a "disk at once": CDRDAO
155 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
156 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
157 For other devices, it's possible that you'll have to write the
158 driver software yourself. Please read the file
159 <file:Documentation/scsi/scsi-generic.txt> for more information.
161 To compile this driver as a module, choose M here and read
162 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
167 tristate "SCSI media changer support"
170 This is a driver for SCSI media changers. Most common devices are
171 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
172 don't need this for those tiny 6-slot cdrom changers. Media
173 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
174 If you have such hardware and want to use it with linux, say Y
175 here. Check <file:Documentation/scsi-changer.txt> for details.
177 If you want to compile this as a module ( = code which can be
178 inserted in and removed from the running kernel whenever you want),
179 say M here and read <file:Documentation/kbuild/modules.txt> and
180 <file:Documentation/scsi.txt>. The module will be called ch.o.
184 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
187 config SCSI_MULTI_LUN
188 bool "Probe all LUNs on each SCSI device"
191 If you have a SCSI device that supports more than one LUN (Logical
192 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
193 can say Y here to force the SCSI driver to probe for multiple LUNs.
194 A SCSI device with multiple LUNs acts logically like multiple SCSI
195 devices. The vast majority of SCSI devices have only one LUN, and
196 so most people can say N here. The max_luns boot/module parameter
197 allows to override this setting.
199 config SCSI_CONSTANTS
200 bool "Verbose SCSI error reporting (kernel size +=12K)"
203 The error messages regarding your SCSI hardware will be easier to
204 understand if you say Y here; it will enlarge your kernel by about
205 12 KB. If in doubt, say Y.
208 bool "SCSI logging facility"
211 This turns on a logging facility that can be used to debug a number
212 of SCSI related problems.
214 If you say Y here, no logging output will appear by default, but you
215 can enable logging by saying Y to "/proc file system support" and
216 "Sysctl support" below and executing the command
218 echo "scsi log token [level]" > /proc/scsi/scsi
220 at boot time after the /proc file system has been mounted.
222 There are a number of things that can be used for 'token' (you can
223 find them in the source: <file:drivers/scsi/scsi.c>), and this
224 allows you to select the types of information you want, and the
225 level allows you to select the level of verbosity.
227 If you say N here, it may be harder to track down some types of SCSI
228 problems. If you say Y here your kernel will be somewhat larger, but
229 there should be no noticeable performance impact as long as you have
232 config SCSI_SCAN_ASYNC
233 bool "Asynchronous SCSI scanning"
236 The SCSI subsystem can probe for devices while the rest of the
237 system continues booting, and even probe devices on different
238 busses in parallel, leading to a significant speed-up.
240 If you have built SCSI as modules, enabling this option can
241 be a problem as the devices may not have been found by the
242 time your system expects them to have been. You can load the
243 scsi_wait_scan module to ensure that all scans have completed.
244 If you build your SCSI drivers into the kernel, then everything
245 will work fine if you say Y here.
247 You can override this choice by specifying "scsi_mod.scan=sync"
248 or async on the kernel's command line.
250 config SCSI_WAIT_SCAN
256 menu "SCSI Transports"
259 config SCSI_SPI_ATTRS
260 tristate "Parallel SCSI (SPI) Transport Attributes"
263 If you wish to export transport-specific information about
264 each attached SCSI device to sysfs, say Y. Otherwise, say N.
267 tristate "FiberChannel Transport Attributes"
271 If you wish to export transport-specific information about
272 each attached FiberChannel device to sysfs, say Y.
275 config SCSI_FC_TGT_ATTRS
276 bool "SCSI target support for FiberChannel Transport Attributes"
277 depends on SCSI_FC_ATTRS
278 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
280 If you want to use SCSI target mode drivers enable this option.
282 config SCSI_ISCSI_ATTRS
283 tristate "iSCSI Transport Attributes"
284 depends on SCSI && NET
286 If you wish to export transport-specific information about
287 each attached iSCSI device to sysfs, say Y.
290 config SCSI_SAS_ATTRS
291 tristate "SAS Transport Attributes"
292 depends on SCSI && BLK_DEV_BSG
294 If you wish to export transport-specific information about
295 each attached SAS device to sysfs, say Y.
297 source "drivers/scsi/libsas/Kconfig"
299 config SCSI_SRP_ATTRS
300 tristate "SRP Transport Attributes"
303 If you wish to export transport-specific information about
304 each attached SRP device to sysfs, say Y.
306 config SCSI_SRP_TGT_ATTRS
307 bool "SCSI target support for SRP Transport Attributes"
308 depends on SCSI_SRP_ATTRS
309 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
311 If you want to use SCSI target mode drivers enable this option.
315 menuconfig SCSI_LOWLEVEL
316 bool "SCSI low-level drivers"
323 tristate "iSCSI Initiator over TCP/IP"
324 depends on SCSI && INET
328 select SCSI_ISCSI_ATTRS
330 The iSCSI Driver provides a host with the ability to access storage
331 through an IP network. The driver uses the iSCSI protocol to transport
332 SCSI requests and responses over a TCP/IP network between the host
333 (the "initiator") and "targets". Architecturally, the iSCSI driver
334 combines with the host's TCP/IP stack, network drivers, and Network
335 Interface Card (NIC) to provide the same functions as a SCSI or a
336 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
338 To compile this driver as a module, choose M here: the
339 module will be called iscsi_tcp.
341 The userspace component needed to initialize the driver, documentation,
342 and sample configuration files can be found here:
344 http://linux-iscsi.sf.net
347 tristate "SGI WD93C93 SCSI Driver"
348 depends on SGI_IP22 && SCSI
350 If you have a Western Digital WD93 SCSI controller on
351 an SGI MIPS system, say Y. Otherwise, say N.
354 tristate "DEC NCR53C94 Scsi Driver"
355 depends on MACH_DECSTATION && SCSI && TC
357 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
358 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
361 tristate "DEC SII Scsi Driver"
362 depends on MACH_DECSTATION && SCSI && 32BIT
364 config BLK_DEV_3W_XXXX_RAID
365 tristate "3ware 5/6/7/8xxx ATA-RAID support"
366 depends on PCI && SCSI
368 3ware is the only hardware ATA-Raid product in Linux to date.
369 This card is 2,4, or 8 channel master mode support only.
370 SCSI support required!!!
372 <http://www.3ware.com/>
374 Please read the comments at the top of
375 <file:drivers/scsi/3w-xxxx.c>.
378 tristate "3ware 9xxx SATA-RAID support"
379 depends on PCI && SCSI
381 This driver supports the 9000 series 3ware SATA-RAID cards.
383 <http://www.amcc.com>
385 Please read the comments at the top of
386 <file:drivers/scsi/3w-9xxx.c>.
388 config SCSI_7000FASST
389 tristate "7000FASST SCSI support"
390 depends on ISA && SCSI && ISA_DMA_API
392 This driver supports the Western Digital 7000 SCSI host adapter
393 family. Some information is in the source:
394 <file:drivers/scsi/wd7000.c>.
396 To compile this driver as a module, choose M here: the
397 module will be called wd7000.
400 tristate "ACARD SCSI support"
401 depends on PCI && SCSI
403 This driver supports the ACARD SCSI host adapter.
404 Support Chip <ATP870 ATP876 ATP880 ATP885>
405 To compile this driver as a module, choose M here: the
406 module will be called atp870u.
409 tristate "Adaptec AHA152X/2825 support"
410 depends on ISA && SCSI && !64BIT
411 select SCSI_SPI_ATTRS
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"
508 # All the I2O code and drivers do not seem to be 64bit safe.
510 tristate "Adaptec I2O RAID support "
511 depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
513 This driver supports all of Adaptec's I2O based RAID controllers as
514 well as the DPT SmartRaid V cards. This is an Adaptec maintained
515 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
517 To compile this driver as a module, choose M here: the
518 module will be called dpt_i2o.
521 tristate "AdvanSys SCSI support"
523 depends on ISA || EISA || PCI
525 This is a driver for all SCSI host adapters manufactured by
526 AdvanSys. It is documented in the kernel source in
527 <file:drivers/scsi/advansys.c>.
529 To compile this driver as a module, choose M here: the
530 module will be called advansys.
533 tristate "Always IN2000 SCSI support"
534 depends on ISA && SCSI
536 This is support for an ISA bus SCSI host adapter. You'll find more
537 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
538 out of the box, you may have to change the jumpers for IRQ or
541 To compile this driver as a module, choose M here: the
542 module will be called in2000.
545 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
546 depends on PCI && SCSI
548 This driver supports all of ARECA's SATA/SAS RAID controller cards.
549 This is an ARECA-maintained driver by Erich Chen.
550 If you have any problems, please mail to: <erich@areca.com.tw>.
551 Areca supports Linux RAID config tools.
552 Please link <http://www.areca.com.tw>
554 To compile this driver as a module, choose M here: the
555 module will be called arcmsr (modprobe arcmsr).
557 config SCSI_ARCMSR_AER
558 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
559 depends on SCSI_ARCMSR && PCIEAER
562 The advanced error reporting(AER) capability is "NOT" provided by
563 ARC1200/1201/1202 SATA RAID controllers cards.
564 If your card is one of ARC1200/1201/1202, please use the default setting, n.
565 If your card is other models, you could pick it
566 on condition that the kernel version is greater than 2.6.19.
567 This function is maintained driver by Nick Cheng. If you have any
568 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
569 To enable this function, choose Y here.
571 source "drivers/scsi/megaraid/Kconfig.megaraid"
574 tristate "HighPoint RocketRAID 3xxx Controller support"
575 depends on SCSI && PCI
577 This option enables support for HighPoint RocketRAID 3xxx
580 To compile this driver as a module, choose M here; the module
581 will be called hptiop. If unsure, say N.
584 tristate "BusLogic SCSI support"
585 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
587 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
588 Adapters. Consult the SCSI-HOWTO, available from
589 <http://www.tldp.org/docs.html#howto>, and the files
590 <file:Documentation/scsi/BusLogic.txt> and
591 <file:Documentation/scsi/FlashPoint.txt> for more information.
593 To compile this driver as a module, choose M here: the
594 module will be called BusLogic.
596 config SCSI_OMIT_FLASHPOINT
597 bool "Omit FlashPoint support"
598 depends on SCSI_BUSLOGIC
600 This option allows you to omit the FlashPoint support from the
601 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
602 substantial, so users of MultiMaster Host Adapters may wish to omit
606 tristate "DMX3191D SCSI support"
607 depends on PCI && SCSI
608 select SCSI_SPI_ATTRS
610 This is support for Domex DMX3191D SCSI Host Adapters.
612 To compile this driver as a module, choose M here: the
613 module will be called dmx3191d.
616 tristate "DTC3180/3280 SCSI support"
617 depends on ISA && SCSI
618 select SCSI_SPI_ATTRS
620 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
621 the SCSI-HOWTO, available from
622 <http://www.tldp.org/docs.html#howto>, and the file
623 <file:Documentation/scsi/dtc3x80.txt>.
625 To compile this driver as a module, choose M here: the
626 module will be called dtc.
629 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
630 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
632 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
633 ISA and all EISA I/O addresses are probed looking for the "EATA"
634 signature. The addresses of all the PCI SCSI controllers reported
635 by the PCI subsystem are probed as well.
637 You want to read the start of <file:drivers/scsi/eata.c> and the
638 SCSI-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
641 To compile this driver as a module, choose M here: the
642 module will be called eata.
644 config SCSI_EATA_TAGGED_QUEUE
645 bool "enable tagged command queueing"
648 This is a feature of SCSI-2 which improves performance: the host
649 adapter can send several SCSI commands to a device's queue even if
650 previous commands haven't finished yet.
651 This is equivalent to the "eata=tc:y" boot option.
653 config SCSI_EATA_LINKED_COMMANDS
654 bool "enable elevator sorting"
657 This option enables elevator sorting for all probed SCSI disks and
658 CD-ROMs. It definitely reduces the average seek distance when doing
659 random seeks, but this does not necessarily result in a noticeable
660 performance improvement: your mileage may vary...
661 This is equivalent to the "eata=lc:y" boot option.
663 config SCSI_EATA_MAX_TAGS
664 int "maximum number of queued commands"
668 This specifies how many SCSI commands can be maximally queued for
669 each probed SCSI device. You should reduce the default value of 16
670 only if you have disks with buggy or limited tagged command support.
671 Minimum is 2 and maximum is 62. This value is also the window size
672 used by the elevator sorting option above. The effective value used
673 by the driver for each probed SCSI device is reported at boot time.
674 This is equivalent to the "eata=mq:8" boot option.
677 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
678 depends on (ISA || EISA || PCI) && SCSI && BROKEN
680 This driver supports all EATA-PIO protocol compliant SCSI Host
681 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
682 host adapters could also use this driver but are discouraged from
683 doing so, since this driver only supports hard disks and lacks
684 numerous features. You might want to have a look at the SCSI-HOWTO,
685 available from <http://www.tldp.org/docs.html#howto>.
687 To compile this driver as a module, choose M here: the
688 module will be called eata_pio.
690 config SCSI_FUTURE_DOMAIN
691 tristate "Future Domain 16xx SCSI/AHA-2920A support"
692 depends on (ISA || PCI) && SCSI
694 This is support for Future Domain's 16-bit SCSI host adapters
695 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
696 other adapters based on the Future Domain chipsets (Quantum
697 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
698 It is explained in section 3.7 of the SCSI-HOWTO, available from
699 <http://www.tldp.org/docs.html#howto>.
701 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
702 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
703 controller support"). This Future Domain driver works with the older
704 Adaptec AHA-2920A boards with a Future Domain chip on them.
706 To compile this driver as a module, choose M here: the
707 module will be called fdomain.
710 tristate "Future Domain MCS-600/700 SCSI support"
711 depends on MCA_LEGACY && SCSI
713 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
714 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
715 is identical to the MCS 700 and hence also supported by this driver.
716 This driver also supports the Reply SB16/SCSI card (the SCSI part).
717 It supports multiple adapters in the same system.
719 To compile this driver as a module, choose M here: the
720 module will be called fd_mcs.
723 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
724 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
726 Formerly called GDT SCSI Disk Array Controller Support.
728 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
729 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
730 in the kernel source in <file:drivers/scsi/gdth.c> and
731 <file:drivers/scsi/gdth.h.>
733 To compile this driver as a module, choose M here: the
734 module will be called gdth.
736 config SCSI_GENERIC_NCR5380
737 tristate "Generic NCR5380/53c400 SCSI PIO support"
738 depends on ISA && SCSI
739 select SCSI_SPI_ATTRS
741 This is a driver for the old NCR 53c80 series of SCSI controllers
742 on boards using PIO. Most boards such as the Trantor T130 fit this
743 category, along with a large number of ISA 8bit controllers shipped
744 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
745 you should select the specific driver for that card rather than
746 generic 5380 support.
748 It is explained in section 3.8 of the SCSI-HOWTO, available from
749 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
750 of the box, you may have to change some settings in
751 <file:drivers/scsi/g_NCR5380.h>.
753 To compile this driver as a module, choose M here: the
754 module will be called g_NCR5380.
756 config SCSI_GENERIC_NCR5380_MMIO
757 tristate "Generic NCR5380/53c400 SCSI MMIO 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 memory mapped I/O.
763 It is explained in section 3.8 of the SCSI-HOWTO, available from
764 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
765 of the box, you may have to change some settings in
766 <file:drivers/scsi/g_NCR5380.h>.
768 To compile this driver as a module, choose M here: the
769 module will be called g_NCR5380_mmio.
771 config SCSI_GENERIC_NCR53C400
772 bool "Enable NCR53c400 extensions"
773 depends on SCSI_GENERIC_NCR5380
775 This enables certain optimizations for the NCR53c400 SCSI cards.
776 You might as well try it out. Note that this driver will only probe
777 for the Trantor T130B in its default configuration; you might have
778 to pass a command line option to the kernel at boot time if it does
779 not detect your card. See the file
780 <file:Documentation/scsi/g_NCR5380.txt> for details.
783 tristate "IBMMCA SCSI support"
784 depends on MCA && SCSI
786 This is support for the IBM SCSI adapter found in many of the PS/2
787 series computers. These machines have an MCA bus, so you need to
788 answer Y to "MCA support" as well and read
789 <file:Documentation/mca.txt>.
791 If the adapter isn't found during boot (a common problem for models
792 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
793 option, where <pun> is the id of the SCSI subsystem (usually 7, but
794 if that doesn't work check your reference diskette). Owners of
795 model 95 with a LED-matrix-display can in addition activate some
796 activity info like under OS/2, but more informative, by setting
797 'ibmmcascsi=display' as an additional kernel parameter. Try "man
798 bootparam" or see the documentation of your boot loader about how to
799 pass options to the kernel.
801 To compile this driver as a module, choose M here: the
802 module will be called ibmmca.
804 config IBMMCA_SCSI_ORDER_STANDARD
805 bool "Standard SCSI-order"
806 depends on SCSI_IBMMCA
808 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
809 are assigned to the drive letters, starting with the lowest SCSI-id
810 (physical number -- pun) to be drive C:, as seen from DOS and
811 similar operating systems. When looking into papers describing the
812 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
813 The SCSI-standard follows a hardware-hierarchy which says that id 7
814 has the highest priority and id 0 the lowest. Therefore, the host
815 adapters are still today everywhere placed as SCSI-id 7 by default.
816 In the SCSI-standard, the drive letters express the priority of the
817 disk. C: should be the hard disk, or a partition on it, with the
818 highest priority. This must therefore be the disk with the highest
819 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
820 original definition of the SCSI-standard as also industrial- and
821 process-control-machines, like VME-CPUs running under realtime-OSes
822 (e.g. LynxOS, OS9) do.
824 If you like to run Linux on your MCA-machine with the same
825 assignment of hard disks as seen from e.g. DOS or OS/2 on your
826 machine, which is in addition conformant to the SCSI-standard, you
827 must say Y here. This is also necessary for MCA-Linux users who want
828 to keep downward compatibility to older releases of the
829 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
832 If you like to have the lowest SCSI-id assigned as drive C:, as
833 modern SCSI-BIOSes do, which does not conform to the standard, but
834 is widespread and common in the PC-world of today, you must say N
835 here. If unsure, say Y.
837 config IBMMCA_SCSI_DEV_RESET
838 bool "Reset SCSI-devices at boottime"
839 depends on SCSI_IBMMCA
841 By default, SCSI-devices are reset when the machine is powered on.
842 However, some devices exist, like special-control-devices,
843 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
844 not reset when switched on. If you say Y here, each device connected
845 to your SCSI-bus will be issued a reset-command after it has been
846 probed, while the kernel is booting. This may cause problems with
847 more modern devices, like hard disks, which do not appreciate these
848 reset commands, and can cause your system to hang. So say Y only if
849 you know that one of your older devices needs it; N is the safe
853 tristate "IBM ServeRAID support"
854 depends on PCI && SCSI
856 This is support for the IBM ServeRAID hardware RAID controllers.
857 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
858 for more information. If this driver does not work correctly
859 without modification please contact the author by email at
860 <ipslinux@adaptec.com>.
862 To compile this driver as a module, choose M here: the
863 module will be called ips.
866 tristate "IBM Virtual SCSI support"
867 depends on PPC_PSERIES || PPC_ISERIES
868 select SCSI_SRP_ATTRS
870 This is the IBM POWER Virtual SCSI Client
872 To compile this driver as a module, choose M here: the
873 module will be called ibmvscsic.
875 config SCSI_IBMVSCSIS
876 tristate "IBM Virtual SCSI Server support"
877 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
879 This is the SRP target driver for IBM pSeries virtual environments.
881 The userspace component needed to initialize the driver and
882 documentation can be found:
884 http://stgt.berlios.de/
886 To compile this driver as a module, choose M here: the
887 module will be called ibmvstgt.
890 tristate "Initio 9100U(W) support"
891 depends on PCI && SCSI
893 This is support for the Initio 91XXU(W) SCSI host adapter. Please
894 read the SCSI-HOWTO, available from
895 <http://www.tldp.org/docs.html#howto>.
897 To compile this driver as a module, choose M here: the
898 module will be called initio.
901 tristate "Initio INI-A100U2W support"
902 depends on PCI && SCSI
904 This is support for the Initio INI-A100U2W SCSI host adapter.
905 Please read the SCSI-HOWTO, available from
906 <http://www.tldp.org/docs.html#howto>.
908 To compile this driver as a module, choose M here: the
909 module will be called a100u2w.
912 tristate "IOMEGA parallel port (ppa - older drives)"
913 depends on SCSI && PARPORT_PC
915 This driver supports older versions of IOMEGA's parallel port ZIP
916 drive (a 100 MB removable media device).
918 Note that you can say N here if you have the SCSI version of the ZIP
919 drive: it will be supported automatically if you said Y to the
920 generic "SCSI disk support", above.
922 If you have the ZIP Plus drive or a more recent parallel port ZIP
923 drive (if the supplied cable with the drive is labeled "AutoDetect")
924 then you should say N here and Y to "IOMEGA parallel port (imm -
925 newer drives)", below.
927 For more information about this driver and how to use it you should
928 read the file <file:Documentation/scsi/ppa.txt>. You should also read
929 the SCSI-HOWTO, which is available from
930 <http://www.tldp.org/docs.html#howto>. If you use this driver,
931 you will still be able to use the parallel port for other tasks,
932 such as a printer; it is safe to compile both drivers into the
935 To compile this driver as a module, choose M here: the
936 module will be called ppa.
939 tristate "IOMEGA parallel port (imm - newer drives)"
940 depends on SCSI && PARPORT_PC
942 This driver supports newer versions of IOMEGA's parallel port ZIP
943 drive (a 100 MB removable media device).
945 Note that you can say N here if you have the SCSI version of the ZIP
946 drive: it will be supported automatically if you said Y to the
947 generic "SCSI disk support", above.
949 If you have the ZIP Plus drive or a more recent parallel port ZIP
950 drive (if the supplied cable with the drive is labeled "AutoDetect")
951 then you should say Y here; if you have an older ZIP drive, say N
952 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
954 For more information about this driver and how to use it you should
955 read the file <file:Documentation/scsi/ppa.txt>. You should also read
956 the SCSI-HOWTO, which is available from
957 <http://www.tldp.org/docs.html#howto>. If you use this driver,
958 you will still be able to use the parallel port for other tasks,
959 such as a printer; it is safe to compile both drivers into the
962 To compile this driver as a module, choose M here: the
963 module will be called imm.
965 config SCSI_IZIP_EPP16
966 bool "ppa/imm option - Use slow (but safe) EPP-16"
967 depends on SCSI_PPA || SCSI_IMM
969 EPP (Enhanced Parallel Port) is a standard for parallel ports which
970 allows them to act as expansion buses that can handle up to 64
973 Some parallel port chipsets are slower than their motherboard, and
974 so we have to control the state of the chipset's FIFO queue every
975 now and then to avoid data loss. This will be done if you say Y
978 Generally, saying Y is the safe option and slows things down a bit.
980 config SCSI_IZIP_SLOW_CTR
981 bool "ppa/imm option - Assume slow parport control register"
982 depends on SCSI_PPA || SCSI_IMM
984 Some parallel ports are known to have excessive delays between
985 changing the parallel port control register and good data being
986 available on the parallel port data/status register. This option
987 forces a small delay (1.0 usec to be exact) after changing the
988 control register to let things settle out. Enabling this option may
989 result in a big drop in performance but some very old parallel ports
990 (found in 386 vintage machines) will not work properly.
992 Generally, saying N is fine.
994 config SCSI_NCR53C406A
995 tristate "NCR53c406a SCSI support"
996 depends on ISA && SCSI
998 This is support for the NCR53c406a SCSI host adapter. For user
999 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1000 in the kernel source. Also read the SCSI-HOWTO, available from
1001 <http://www.tldp.org/docs.html#howto>.
1003 To compile this driver as a module, choose M here: the
1004 module will be called NCR53c406.
1006 config SCSI_NCR_D700
1007 tristate "NCR Dual 700 MCA SCSI support"
1008 depends on MCA && SCSI
1009 select SCSI_SPI_ATTRS
1011 This is a driver for the MicroChannel Dual 700 card produced by
1012 NCR and commonly used in 345x/35xx/4100 class machines. It always
1013 tries to negotiate sync and uses tag command queueing.
1015 Unless you have an NCR manufactured machine, the chances are that
1016 you do not have this SCSI card, so say N.
1019 tristate "HP Lasi SCSI support for 53c700/710"
1020 depends on GSC && SCSI
1021 select SCSI_SPI_ATTRS
1023 This is a driver for the SCSI controller in the Lasi chip found in
1024 many PA-RISC workstations & servers. If you do not know whether you
1025 have a Lasi chip, it is safe to say "Y" here.
1027 config SCSI_SNI_53C710
1028 tristate "SNI RM SCSI support for 53c710"
1029 depends on SNI_RM && SCSI
1030 select SCSI_SPI_ATTRS
1031 select 53C700_LE_ON_BE
1033 This is a driver for the onboard SCSI controller found in older
1034 SNI RM workstations & servers.
1036 config 53C700_LE_ON_BE
1038 depends on SCSI_LASI700
1042 tristate "Promise SuperTrak EX Series support"
1043 depends on PCI && SCSI
1045 This driver supports Promise SuperTrak EX series storage controllers.
1047 Promise provides Linux RAID configuration utility for these
1048 controllers. Please visit <http://www.promise.com> to download.
1050 To compile this driver as a module, choose M here: the
1051 module will be called stex.
1053 config 53C700_BE_BUS
1055 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1058 config SCSI_SYM53C8XX_2
1059 tristate "SYM53C8XX Version 2 SCSI support"
1060 depends on PCI && SCSI
1061 select SCSI_SPI_ATTRS
1063 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1064 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1065 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1066 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1067 controllers; you need to use the Fusion MPT driver for that.
1069 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1072 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1073 int "DMA addressing mode"
1074 depends on SCSI_SYM53C8XX_2
1077 This option only applies to PCI-SCSI chips that are PCI DAC
1078 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1080 When set to 0, the driver will program the chip to only perform
1081 32-bit DMA. When set to 1, the chip will be able to perform DMA
1082 to addresses up to 1TB. When set to 2, the driver supports the
1083 full 64-bit DMA address range, but can only address 16 segments
1084 of 4 GB each. This limits the total addressable range to 64 GB.
1086 Most machines with less than 4GB of memory should use a setting
1087 of 0 for best performance. If your machine has 4GB of memory
1088 or more, you should set this option to 1 (the default).
1090 The still experimental value 2 (64 bit DMA addressing with 16
1091 x 4GB segments limitation) can be used on systems that require
1092 PCI address bits past bit 39 to be set for the addressing of
1093 memory using PCI DAC cycles.
1095 config SCSI_SYM53C8XX_DEFAULT_TAGS
1096 int "Default tagged command queue depth"
1097 depends on SCSI_SYM53C8XX_2
1100 This is the default value of the command queue depth the
1101 driver will announce to the generic SCSI layer for devices
1102 that support tagged command queueing. This value can be changed
1103 from the boot command line. This is a soft limit that cannot
1104 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1106 config SCSI_SYM53C8XX_MAX_TAGS
1107 int "Maximum number of queued commands"
1108 depends on SCSI_SYM53C8XX_2
1111 This option allows you to specify the maximum number of commands
1112 that can be queued to any device, when tagged command queuing is
1113 possible. The driver supports up to 256 queued commands per device.
1114 This value is used as a compiled-in hard limit.
1116 config SCSI_SYM53C8XX_MMIO
1117 bool "Use memory mapped IO"
1118 depends on SCSI_SYM53C8XX_2
1121 Memory mapped IO is faster than Port IO. Most people should
1122 answer Y here, but some machines may have problems. If you have
1123 to answer N here, please report the problem to the maintainer.
1126 tristate "IBM Power Linux RAID adapter support"
1127 depends on PCI && SCSI && ATA
1130 This driver supports the IBM Power Linux family RAID adapters.
1131 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1132 as IBM iSeries 5702, 5703, 5709, and 570A.
1134 config SCSI_IPR_TRACE
1135 bool "enable driver internal trace"
1139 If you say Y here, the driver will trace all commands issued
1140 to the adapter. Performance impact is minimal. Trace can be
1141 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1143 config SCSI_IPR_DUMP
1144 bool "enable adapter dump support"
1148 If you say Y here, the driver will support adapter crash dump.
1149 If you enable this support, the iprdump daemon can be used
1150 to capture adapter failure analysis information.
1153 tristate "Zalon SCSI support"
1154 depends on GSC && SCSI
1155 select SCSI_SPI_ATTRS
1157 The Zalon is a GSC/HSC bus interface chip that sits between the
1158 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1159 C110, J200, J210 and some D, K & R-class machines. It's also
1160 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1161 Say Y here if you have one of these machines or cards.
1163 config SCSI_NCR_Q720
1164 tristate "NCR Quad 720 MCA SCSI support"
1165 depends on MCA && SCSI
1166 select SCSI_SPI_ATTRS
1168 This is a driver for the MicroChannel Quad 720 card produced by
1169 NCR and commonly used in 345x/35xx/4100 class machines. It always
1170 tries to negotiate sync and uses tag command queueing.
1172 Unless you have an NCR manufactured machine, the chances are that
1173 you do not have this SCSI card, so say N.
1175 config SCSI_NCR53C8XX_DEFAULT_TAGS
1176 int "default tagged command queue depth"
1177 depends on SCSI_ZALON || SCSI_NCR_Q720
1180 "Tagged command queuing" is a feature of SCSI-2 which improves
1181 performance: the host adapter can send several SCSI commands to a
1182 device's queue even if previous commands haven't finished yet.
1183 Because the device is intelligent, it can optimize its operations
1184 (like head positioning) based on its own request queue. Some SCSI
1185 devices don't implement this properly; if you want to disable this
1186 feature, enter 0 or 1 here (it doesn't matter which).
1188 The default value is 8 and should be supported by most hard disks.
1189 This value can be overridden from the boot command line using the
1190 'tags' option as follows (example):
1191 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1192 4, set queue depth to 16 for target 2 and target 3 on controller 0
1193 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1195 The normal answer therefore is to go with the default 8 and to use
1196 a boot command line option for devices that need to use a different
1197 command queue depth.
1199 There is no safe option other than using good SCSI devices.
1201 config SCSI_NCR53C8XX_MAX_TAGS
1202 int "maximum number of queued commands"
1203 depends on SCSI_ZALON || SCSI_NCR_Q720
1206 This option allows you to specify the maximum number of commands
1207 that can be queued to any device, when tagged command queuing is
1208 possible. The default value is 32. Minimum is 2, maximum is 64.
1209 Modern hard disks are able to support 64 tags and even more, but
1210 do not seem to be faster when more than 32 tags are being used.
1212 So, the normal answer here is to go with the default value 32 unless
1213 you are using very large hard disks with large cache (>= 1 MB) that
1214 are able to take advantage of more than 32 tagged commands.
1216 There is no safe option and the default answer is recommended.
1218 config SCSI_NCR53C8XX_SYNC
1219 int "synchronous transfers frequency in MHz"
1220 depends on SCSI_ZALON || SCSI_NCR_Q720
1223 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1224 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1225 are respectively the maximum data transfer rates in mega-transfers
1226 per second for each class. For example, a FAST-20 Wide 16 device is
1227 able to transfer data at 20 million 16 bit packets per second for a
1228 total rate of 40 MB/s.
1230 You may specify 0 if you want to only use asynchronous data
1231 transfers. This is the safest and slowest option. Otherwise, specify
1232 a value between 5 and 80, depending on the capability of your SCSI
1233 controller. The higher the number, the faster the data transfer.
1234 Note that 80 should normally be ok since the driver decreases the
1235 value automatically according to the controller's capabilities.
1237 Your answer to this question is ignored for controllers with NVRAM,
1238 since the driver will get this information from the user set-up. It
1239 also can be overridden using a boot setup option, as follows
1240 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1241 for FAST-20 synchronous data transfer (20 mega-transfers per
1244 The normal answer therefore is not to go with the default but to
1245 select the maximum value 80 allowing the driver to use the maximum
1246 value supported by each controller. If this causes problems with
1247 your SCSI devices, you should come back and decrease the value.
1249 There is no safe option other than using good cabling, right
1250 terminations and SCSI conformant devices.
1252 config SCSI_NCR53C8XX_NO_DISCONNECT
1253 bool "not allow targets to disconnect"
1254 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1256 This option is only provided for safety if you suspect some SCSI
1257 device of yours to not support properly the target-disconnect
1258 feature. In that case, you would say Y here. In general however, to
1259 not allow targets to disconnect is not reasonable if there is more
1260 than 1 device on a SCSI bus. The normal answer therefore is N.
1262 config SCSI_MCA_53C9X
1263 tristate "NCR MCA 53C9x SCSI support"
1264 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1266 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1267 controller based on the NCR 53C94. This driver will allow use of
1268 the controller on the 3550, and very possibly others.
1270 To compile this driver as a module, choose M here: the
1271 module will be called mca_53c9x.
1274 tristate "PAS16 SCSI support"
1275 depends on ISA && SCSI
1276 select SCSI_SPI_ATTRS
1278 This is support for a SCSI host adapter. It is explained in section
1279 3.10 of the SCSI-HOWTO, available from
1280 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1281 of the box, you may have to change some settings in
1282 <file:drivers/scsi/pas16.h>.
1284 To compile this driver as a module, choose M here: the
1285 module will be called pas16.
1288 tristate "PSI240i support"
1289 depends on ISA && SCSI
1291 This is support for the PSI240i EIDE interface card which acts as a
1292 SCSI host adapter. Please read the SCSI-HOWTO, available from
1293 <http://www.tldp.org/docs.html#howto>.
1295 To compile this driver as a module, choose M here: the
1296 module will be called psi240i.
1298 config SCSI_QLOGIC_FAS
1299 tristate "Qlogic FAS SCSI support"
1300 depends on ISA && SCSI
1302 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1303 FastSCSI! cards as well as any other card based on the FASXX chip
1304 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1306 This driver does NOT support the PCI versions of these cards. The
1307 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1308 SCSI support"), below.
1310 Information about this driver is contained in
1311 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1312 SCSI-HOWTO, available from
1313 <http://www.tldp.org/docs.html#howto>.
1315 To compile this driver as a module, choose M here: the
1316 module will be called qlogicfas.
1318 config SCSI_QLOGIC_FC_FIRMWARE
1319 bool "Include loadable firmware in driver"
1320 depends on SCSI_QLOGIC_FC
1322 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1323 expanded LUN addressing and FcTape (FCP-2) support, in the
1324 qlogicfc driver. This is required on some platforms.
1326 config SCSI_QLOGIC_1280
1327 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1328 depends on PCI && SCSI
1330 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1332 To compile this driver as a module, choose M here: the
1333 module will be called qla1280.
1335 config SCSI_QLOGICPTI
1336 tristate "PTI Qlogic, ISP Driver"
1337 depends on SBUS && SCSI
1339 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1340 controllers are known under Solaris as qpti and in the openprom as
1341 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1342 driven by a different driver.
1344 To compile this driver as a module, choose M here: the
1345 module will be called qlogicpti.
1347 source "drivers/scsi/qla2xxx/Kconfig"
1348 source "drivers/scsi/qla4xxx/Kconfig"
1351 tristate "Emulex LightPulse Fibre Channel Support"
1352 depends on PCI && SCSI
1353 select SCSI_FC_ATTRS
1355 This lpfc driver supports the Emulex LightPulse
1356 Family of Fibre Channel PCI host adapters.
1359 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1360 depends on X86 && ISA && SCSI
1362 These are 8-bit SCSI controllers; the ST-01 is also supported by
1363 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1364 available from <http://www.tldp.org/docs.html#howto>. If it
1365 doesn't work out of the box, you may have to change some macros at
1366 compiletime, which are described in <file:drivers/scsi/seagate.c>.
1368 To compile this driver as a module, choose M here: the
1369 module will be called seagate.
1371 # definitely looks not 64bit safe:
1373 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1374 depends on (EISA || MCA) && SCSI
1375 select SCSI_SPI_ATTRS
1377 This driver for NCR53c710 based SCSI host adapters.
1379 It currently supports Compaq EISA cards and NCR MCA cards
1381 config SCSI_SYM53C416
1382 tristate "Symbios 53c416 SCSI support"
1383 depends on ISA && SCSI
1385 This is support for the sym53c416 SCSI host adapter, the SCSI
1386 adapter that comes with some HP scanners. This driver requires that
1387 the sym53c416 is configured first using some sort of PnP
1388 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1389 are using isapnp then you need to compile this driver as a module
1390 and then load it using insmod after isapnp has run. The parameters
1391 of the configured card(s) should be passed to the driver. The format
1394 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1396 To compile this driver as a module, choose M here: the
1397 module will be called sym53c416.
1400 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1401 depends on PCI && SCSI && EXPERIMENTAL
1403 This driver supports PCI SCSI host adapters based on the ASIC
1404 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1406 This driver works, but is still in experimental status. So better
1407 have a bootable disk and a backup in case of emergency.
1409 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1411 To compile this driver as a module, choose M here: the
1412 module will be called dc395x.
1415 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1416 depends on PCI && SCSI
1418 This driver supports PCI SCSI host adapters based on the Am53C974A
1419 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1420 PCscsi/PCnet (Am53/79C974) solutions.
1422 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1424 Note that this driver does NOT support Tekram DC390W/U/F, which are
1425 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1427 To compile this driver as a module, choose M here: the
1428 module will be called tmscsim.
1431 tristate "Trantor T128/T128F/T228 SCSI support"
1432 depends on ISA && SCSI
1433 select SCSI_SPI_ATTRS
1435 This is support for a SCSI host adapter. It is explained in section
1436 3.11 of the SCSI-HOWTO, available from
1437 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1438 of the box, you may have to change some settings in
1439 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1440 Adaptec, and some former Trantor products are being sold under the
1443 To compile this driver as a module, choose M here: the
1444 module will be called t128.
1447 tristate "UltraStor 14F/34F support"
1448 depends on ISA && SCSI && ISA_DMA_API
1450 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1451 The source at <file:drivers/scsi/u14-34f.c> contains some
1452 information about this hardware. If the driver doesn't work out of
1453 the box, you may have to change some settings in
1454 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1455 <http://www.tldp.org/docs.html#howto>. Note that there is also
1456 another driver for the same hardware: "UltraStor SCSI support",
1457 below. You should say Y to both only if you want 24F support as
1460 To compile this driver as a module, choose M here: the
1461 module will be called u14-34f.
1463 config SCSI_U14_34F_TAGGED_QUEUE
1464 bool "enable tagged command queueing"
1465 depends on SCSI_U14_34F
1467 This is a feature of SCSI-2 which improves performance: the host
1468 adapter can send several SCSI commands to a device's queue even if
1469 previous commands haven't finished yet.
1470 This is equivalent to the "u14-34f=tc:y" boot option.
1472 config SCSI_U14_34F_LINKED_COMMANDS
1473 bool "enable elevator sorting"
1474 depends on SCSI_U14_34F
1476 This option enables elevator sorting for all probed SCSI disks and
1477 CD-ROMs. It definitely reduces the average seek distance when doing
1478 random seeks, but this does not necessarily result in a noticeable
1479 performance improvement: your mileage may vary...
1480 This is equivalent to the "u14-34f=lc:y" boot option.
1482 config SCSI_U14_34F_MAX_TAGS
1483 int "maximum number of queued commands"
1484 depends on SCSI_U14_34F
1487 This specifies how many SCSI commands can be maximally queued for
1488 each probed SCSI device. You should reduce the default value of 8
1489 only if you have disks with buggy or limited tagged command support.
1490 Minimum is 2 and maximum is 14. This value is also the window size
1491 used by the elevator sorting option above. The effective value used
1492 by the driver for each probed SCSI device is reported at boot time.
1493 This is equivalent to the "u14-34f=mq:8" boot option.
1495 config SCSI_ULTRASTOR
1496 tristate "UltraStor SCSI support"
1497 depends on X86 && ISA && SCSI
1499 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1500 adapter family. This driver is explained in section 3.12 of the
1501 SCSI-HOWTO, available from
1502 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1503 of the box, you may have to change some settings in
1504 <file:drivers/scsi/ultrastor.h>.
1506 Note that there is also another driver for the same hardware:
1507 "UltraStor 14F/34F support", above.
1509 To compile this driver as a module, choose M here: the
1510 module will be called ultrastor.
1513 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1514 depends on PCI && SCSI && !64BIT
1516 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1517 SCSI host adapter. Please read the SCSI-HOWTO, available from
1518 <http://www.tldp.org/docs.html#howto>.
1520 To compile this driver as a module, choose M here: the
1521 module will be called nsp32.
1524 tristate "SCSI debugging host simulator"
1527 This is a host adapter simulator that can simulate multiple hosts
1528 each with multiple dummy SCSI devices (disks). It defaults to one
1529 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1530 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1531 dummy disks are simulated, they share the same kernel RAM for
1532 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1533 information. This driver is primarily of use to those testing the
1534 SCSI and block subsystems. If unsure, say N.
1537 tristate "MESH (Power Mac internal SCSI) support"
1538 depends on PPC32 && PPC_PMAC && SCSI
1540 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1541 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1542 other Power Macintoshes do). Say Y to include support for this SCSI
1545 To compile this driver as a module, choose M here: the
1546 module will be called mesh.
1548 config SCSI_MESH_SYNC_RATE
1549 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1550 depends on SCSI_MESH
1553 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1554 drives a bus which is entirely internal to the machine (such as the
1555 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1556 operation at up to 10 MB/s. On machines where the SCSI bus
1557 controlled by the MESH can have external devices connected, it is
1558 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1559 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1560 to disable synchronous operation.
1562 config SCSI_MESH_RESET_DELAY_MS
1563 int "initial bus reset delay (ms) (0 = no reset)"
1564 depends on SCSI_MESH
1567 config SCSI_MAC53C94
1568 tristate "53C94 (Power Mac external SCSI) support"
1569 depends on PPC32 && PPC_PMAC && SCSI
1571 On Power Macintoshes (and clones) with two SCSI buses, the external
1572 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1573 machines which only have one SCSI bus, such as the 7200, also use
1574 the 53C94. Say Y to include support for the 53C94.
1576 To compile this driver as a module, choose M here: the
1577 module will be called mac53c94.
1579 source "drivers/scsi/arm/Kconfig"
1582 bool "MIPS JAZZ FAS216 SCSI support"
1583 depends on MACH_JAZZ && SCSI
1584 select SCSI_SPI_ATTRS
1586 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1587 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1591 tristate "A3000 WD33C93A support"
1592 depends on AMIGA && SCSI
1594 If you have an Amiga 3000 and have SCSI devices connected to the
1595 built-in SCSI controller, say Y. Otherwise, say N.
1597 To compile this driver as a module, choose M here: the
1598 module will be called wd33c93.
1601 tristate "A2091/A590 WD33C93A support"
1602 depends on ZORRO && SCSI
1604 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1607 To compile this driver as a module, choose M here: the
1608 module will be called wd33c93.
1611 tristate "GVP Series II WD33C93A support"
1612 depends on ZORRO && SCSI
1614 If you have a Great Valley Products Series II SCSI controller,
1615 answer Y. Also say Y if you have a later model of GVP SCSI
1616 controller (such as the GVP A4008 or a Combo board). Otherwise,
1617 answer N. This driver does NOT work for the T-Rex series of
1618 accelerators from TekMagic and GVP-M.
1620 To compile this driver as a module, choose M here: the
1621 module will be called gvp11.
1623 config CYBERSTORM_SCSI
1624 tristate "CyberStorm SCSI support"
1625 depends on ZORRO && SCSI
1627 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1628 accelerator board and the optional Cyberstorm SCSI controller,
1629 answer Y. Otherwise, say N.
1631 config CYBERSTORMII_SCSI
1632 tristate "CyberStorm Mk II SCSI support"
1633 depends on ZORRO && SCSI
1635 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1636 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1640 tristate "Blizzard 2060 SCSI support"
1641 depends on ZORRO && SCSI
1643 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1644 and want to use the onboard SCSI controller, say Y. Otherwise,
1648 tristate "Blizzard 1230IV/1260 SCSI support"
1649 depends on ZORRO && SCSI
1651 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1652 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1655 config FASTLANE_SCSI
1656 tristate "Fastlane SCSI support"
1657 depends on ZORRO && SCSI
1659 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1660 one in the near future, say Y to this question. Otherwise, say N.
1663 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1664 depends on AMIGA && SCSI && EXPERIMENTAL
1665 select SCSI_SPI_ATTRS
1667 If you have an Amiga 4000T and have SCSI devices connected to the
1668 built-in SCSI controller, say Y. Otherwise, say N.
1670 To compile this driver as a module, choose M here: the
1671 module will be called a4000t.
1673 config SCSI_ZORRO7XX
1674 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1675 depends on ZORRO && SCSI && EXPERIMENTAL
1676 select SCSI_SPI_ATTRS
1678 Support for various NCR53c710-based SCSI controllers on Zorro
1679 expansion boards for the Amiga.
1681 - the Amiga 4091 Zorro III SCSI-2 controller,
1682 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1684 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1685 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1686 accelerator card for the Amiga 1200,
1687 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1690 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1691 depends on ZORRO && SCSI && EXPERIMENTAL
1693 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1694 Y to this question. If you're in doubt about whether you have one,
1696 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1699 tristate "Atari native SCSI support"
1700 depends on ATARI && SCSI
1701 select SCSI_SPI_ATTRS
1703 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1704 Falcon, ...) say Y to get it supported. Of course also, if you have
1705 a compatible SCSI controller (e.g. for Medusa).
1707 To compile this driver as a module, choose M here: the
1708 module will be called atari_scsi.
1710 This driver supports both styles of NCR integration into the
1711 system: the TT style (separate DMA), and the Falcon style (via
1712 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1713 in the Hades (without DMA).
1715 config ATARI_SCSI_TOSHIBA_DELAY
1716 bool "Long delays for Toshiba CD-ROMs"
1717 depends on ATARI_SCSI
1719 This option increases the delay after a SCSI arbitration to
1720 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1721 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1722 would impact performance a bit, so say N.
1724 config ATARI_SCSI_RESET_BOOT
1725 bool "Reset SCSI-devices at boottime"
1726 depends on ATARI_SCSI
1728 Reset the devices on your Atari whenever it boots. This makes the
1729 boot process fractionally longer but may assist recovery from errors
1730 that leave the devices with SCSI operations partway completed.
1733 bool "Hades SCSI DMA emulator"
1734 depends on ATARI_SCSI && HADES
1736 This option enables code which emulates the TT SCSI DMA chip on the
1737 Hades. This increases the SCSI transfer rates at least ten times
1738 compared to PIO transfers.
1741 bool "Macintosh NCR5380 SCSI"
1742 depends on MAC && SCSI=y
1743 select SCSI_SPI_ATTRS
1745 This is the NCR 5380 SCSI controller included on most of the 68030
1746 based Macintoshes. If you have one of these say Y and read the
1747 SCSI-HOWTO, available from
1748 <http://www.tldp.org/docs.html#howto>.
1751 tristate "Macintosh NCR53c9[46] SCSI"
1752 depends on MAC && SCSI
1754 This is the NCR 53c9x SCSI controller found on most of the 68040
1755 based Macintoshes. If you have one of these say Y and read the
1756 SCSI-HOWTO, available from
1757 <http://www.tldp.org/docs.html#howto>.
1759 To compile this driver as a module, choose M here: the
1760 module will be called mac_esp.
1763 bool "WD33C93 SCSI driver for MVME147"
1764 depends on MVME147 && SCSI=y
1765 select SCSI_SPI_ATTRS
1767 Support for the on-board SCSI controller on the Motorola MVME147
1768 single-board computer.
1771 tristate "NCR53C710 SCSI driver for MVME16x"
1772 depends on MVME16x && SCSI
1773 select SCSI_SPI_ATTRS
1775 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1776 SCSI controller chip. Almost everyone using one of these boards
1777 will want to say Y to this question.
1779 config BVME6000_SCSI
1780 tristate "NCR53C710 SCSI driver for BVME6000"
1781 depends on BVME6000 && SCSI
1782 select SCSI_SPI_ATTRS
1784 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1785 SCSI controller chip. Almost everyone using one of these boards
1786 will want to say Y to this question.
1789 tristate "Sun3 NCR5380 SCSI"
1790 depends on SUN3 && SCSI
1791 select SCSI_SPI_ATTRS
1793 This option will enable support for the OBIO (onboard io) NCR5380
1794 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1795 "Sun3" type VME scsi controllers also based on the NCR5380.
1796 General Linux information on the Sun 3 series (now discontinued)
1797 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1800 bool "Sun3x ESP SCSI"
1801 depends on SUN3X && SCSI=y
1803 The ESP was an on-board SCSI controller used on Sun 3/80
1804 machines. Say Y here to compile in support for it.
1807 tristate "Sparc ESP Scsi Driver"
1808 depends on SBUS && SCSI
1809 select SCSI_SPI_ATTRS
1811 This is the driver for the Sun ESP SCSI host adapter. The ESP
1812 chipset is present in most SPARC SBUS-based computers.
1814 To compile this driver as a module, choose M here: the
1815 module will be called esp.
1818 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1819 depends on S390 && QDIO && SCSI
1820 select SCSI_FC_ATTRS
1822 If you want to access SCSI devices attached to your IBM eServer
1823 zSeries by means of Fibre Channel interfaces say Y.
1824 For details please refer to the documentation provided by IBM at
1825 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1827 This driver is also available as a module. This module will be
1828 called zfcp. If you want to compile it as a module, say M here
1829 and read <file:Documentation/kbuild/modules.txt>.
1832 tristate "SCSI RDMA Protocol helper library"
1833 depends on SCSI && PCI
1836 If you wish to use SRP target drivers, say Y.
1838 To compile this driver as a module, choose M here: the
1839 module will be called libsrp.
1841 endif # SCSI_LOWLEVEL
1843 source "drivers/scsi/pcmcia/Kconfig"