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/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/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://open-iscsi.org
347 tristate "SGI WD93C93 SCSI Driver"
348 depends on SGI_HAS_WD93 && SCSI
350 If you have a Western Digital WD93 SCSI controller on
351 an SGI MIPS system, say Y. Otherwise, say N.
353 config BLK_DEV_3W_XXXX_RAID
354 tristate "3ware 5/6/7/8xxx ATA-RAID support"
355 depends on PCI && SCSI
357 3ware is the only hardware ATA-Raid product in Linux to date.
358 This card is 2,4, or 8 channel master mode support only.
359 SCSI support required!!!
361 <http://www.3ware.com/>
363 Please read the comments at the top of
364 <file:drivers/scsi/3w-xxxx.c>.
367 tristate "3ware 9xxx SATA-RAID support"
368 depends on PCI && SCSI
370 This driver supports the 9000 series 3ware SATA-RAID cards.
372 <http://www.amcc.com>
374 Please read the comments at the top of
375 <file:drivers/scsi/3w-9xxx.c>.
377 config SCSI_7000FASST
378 tristate "7000FASST SCSI support"
379 depends on ISA && SCSI && ISA_DMA_API
380 select CHECK_SIGNATURE
382 This driver supports the Western Digital 7000 SCSI host adapter
383 family. Some information is in the source:
384 <file:drivers/scsi/wd7000.c>.
386 To compile this driver as a module, choose M here: the
387 module will be called wd7000.
390 tristate "ACARD SCSI support"
391 depends on PCI && SCSI
393 This driver supports the ACARD SCSI host adapter.
394 Support Chip <ATP870 ATP876 ATP880 ATP885>
395 To compile this driver as a module, choose M here: the
396 module will be called atp870u.
399 tristate "Adaptec AHA152X/2825 support"
400 depends on ISA && SCSI && !64BIT
401 select SCSI_SPI_ATTRS
402 select CHECK_SIGNATURE
404 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
405 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
406 must be manually specified in this case.
408 It is explained in section 3.3 of the SCSI-HOWTO, available from
409 <http://www.tldp.org/docs.html#howto>. You might also want to
410 read the file <file:Documentation/scsi/aha152x.txt>.
412 To compile this driver as a module, choose M here: the
413 module will be called aha152x.
416 tristate "Adaptec AHA1542 support"
417 depends on ISA && SCSI && ISA_DMA_API
419 This is support for a SCSI host adapter. It is explained in section
420 3.4 of the SCSI-HOWTO, available from
421 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
422 purchased by Adaptec, and some former Trantor products are being
423 sold under the Adaptec name. If it doesn't work out of the box, you
424 may have to change some settings in <file:drivers/scsi/aha1542.h>.
426 To compile this driver as a module, choose M here: the
427 module will be called aha1542.
430 tristate "Adaptec AHA1740 support"
431 depends on EISA && SCSI
433 This is support for a SCSI host adapter. It is explained in section
434 3.5 of the SCSI-HOWTO, available from
435 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
436 of the box, you may have to change some settings in
437 <file:drivers/scsi/aha1740.h>.
439 To compile this driver as a module, choose M here: the
440 module will be called aha1740.
443 tristate "Adaptec AACRAID support"
444 depends on SCSI && PCI
446 This driver supports a variety of Dell, HP, Adaptec, IBM and
447 ICP storage products. For a list of supported products, refer
448 to <file:Documentation/scsi/aacraid.txt>.
450 To compile this driver as a module, choose M here: the module
451 will be called aacraid.
454 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
456 config SCSI_AIC7XXX_OLD
457 tristate "Adaptec AIC7xxx support (old driver)"
458 depends on (ISA || EISA || PCI ) && SCSI
460 WARNING This driver is an older aic7xxx driver and is no longer
461 under active development. Adaptec, Inc. is writing a new driver to
462 take the place of this one, and it is recommended that whenever
463 possible, people should use the new Adaptec written driver instead
464 of this one. This driver will eventually be phased out entirely.
466 This is support for the various aic7xxx based Adaptec SCSI
467 controllers. These include the 274x EISA cards; 284x VLB cards;
468 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
469 motherboard based SCSI controllers from Adaptec. It does not support
470 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
471 support them. It does not support the 2920 cards from Adaptec that
472 use the Future Domain SCSI controller chip. For those cards, you
473 need the "Future Domain 16xx SCSI support" driver.
475 In general, if the controller is based on an Adaptec SCSI controller
476 chip from the aic777x series or the aic78xx series, this driver
477 should work. The only exception is the 7810 which is specifically
478 not supported (that's the RAID controller chip on the AAA-13x
481 Note that the AHA2920 SCSI host adapter is *not* supported by this
482 driver; choose "Future Domain 16xx SCSI support" instead if you have
485 Information on the configuration options for this controller can be
486 found by checking the help file for each of the available
487 configuration options. You should read
488 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
489 contacting the maintainer with any questions. The SCSI-HOWTO,
490 available from <http://www.tldp.org/docs.html#howto>, can also
493 To compile this driver as a module, choose M here: the
494 module will be called aic7xxx_old.
496 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
497 source "drivers/scsi/aic94xx/Kconfig"
499 # All the I2O code and drivers do not seem to be 64bit safe.
501 tristate "Adaptec I2O RAID support "
502 depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
504 This driver supports all of Adaptec's I2O based RAID controllers as
505 well as the DPT SmartRaid V cards. This is an Adaptec maintained
506 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
508 To compile this driver as a module, choose M here: the
509 module will be called dpt_i2o.
512 tristate "AdvanSys SCSI support"
513 depends on SCSI && VIRT_TO_BUS
514 depends on ISA || EISA || PCI
516 This is a driver for all SCSI host adapters manufactured by
517 AdvanSys. It is documented in the kernel source in
518 <file:drivers/scsi/advansys.c>.
520 To compile this driver as a module, choose M here: the
521 module will be called advansys.
524 tristate "Always IN2000 SCSI support"
525 depends on ISA && SCSI
527 This is support for an ISA bus SCSI host adapter. You'll find more
528 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
529 out of the box, you may have to change the jumpers for IRQ or
532 To compile this driver as a module, choose M here: the
533 module will be called in2000.
536 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
537 depends on PCI && SCSI
539 This driver supports all of ARECA's SATA/SAS RAID controller cards.
540 This is an ARECA-maintained driver by Erich Chen.
541 If you have any problems, please mail to: <erich@areca.com.tw>.
542 Areca supports Linux RAID config tools.
543 Please link <http://www.areca.com.tw>
545 To compile this driver as a module, choose M here: the
546 module will be called arcmsr (modprobe arcmsr).
548 config SCSI_ARCMSR_AER
549 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
550 depends on SCSI_ARCMSR && PCIEAER
553 The advanced error reporting(AER) capability is "NOT" provided by
554 ARC1200/1201/1202 SATA RAID controllers cards.
555 If your card is one of ARC1200/1201/1202, please use the default setting, n.
556 If your card is other models, you could pick it
557 on condition that the kernel version is greater than 2.6.19.
558 This function is maintained driver by Nick Cheng. If you have any
559 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
560 To enable this function, choose Y here.
562 source "drivers/scsi/megaraid/Kconfig.megaraid"
565 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
566 depends on SCSI && PCI
568 This option enables support for HighPoint RocketRAID 3xxx/4xxx
571 To compile this driver as a module, choose M here; the module
572 will be called hptiop. If unsure, say N.
575 tristate "BusLogic SCSI support"
576 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
578 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
579 Adapters. Consult the SCSI-HOWTO, available from
580 <http://www.tldp.org/docs.html#howto>, and the files
581 <file:Documentation/scsi/BusLogic.txt> and
582 <file:Documentation/scsi/FlashPoint.txt> for more information.
584 To compile this driver as a module, choose M here: the
585 module will be called BusLogic.
587 config SCSI_OMIT_FLASHPOINT
588 bool "Omit FlashPoint support"
589 depends on SCSI_BUSLOGIC
591 This option allows you to omit the FlashPoint support from the
592 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
593 substantial, so users of MultiMaster Host Adapters may wish to omit
597 tristate "DMX3191D SCSI support"
598 depends on PCI && SCSI
599 select SCSI_SPI_ATTRS
601 This is support for Domex DMX3191D SCSI Host Adapters.
603 To compile this driver as a module, choose M here: the
604 module will be called dmx3191d.
607 tristate "DTC3180/3280 SCSI support"
608 depends on ISA && SCSI
609 select SCSI_SPI_ATTRS
610 select CHECK_SIGNATURE
612 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
613 the SCSI-HOWTO, available from
614 <http://www.tldp.org/docs.html#howto>, and the file
615 <file:Documentation/scsi/dtc3x80.txt>.
617 To compile this driver as a module, choose M here: the
618 module will be called dtc.
621 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
622 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
624 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
625 ISA and all EISA I/O addresses are probed looking for the "EATA"
626 signature. The addresses of all the PCI SCSI controllers reported
627 by the PCI subsystem are probed as well.
629 You want to read the start of <file:drivers/scsi/eata.c> and the
630 SCSI-HOWTO, available from
631 <http://www.tldp.org/docs.html#howto>.
633 To compile this driver as a module, choose M here: the
634 module will be called eata.
636 config SCSI_EATA_TAGGED_QUEUE
637 bool "enable tagged command queueing"
640 This is a feature of SCSI-2 which improves performance: the host
641 adapter can send several SCSI commands to a device's queue even if
642 previous commands haven't finished yet.
643 This is equivalent to the "eata=tc:y" boot option.
645 config SCSI_EATA_LINKED_COMMANDS
646 bool "enable elevator sorting"
649 This option enables elevator sorting for all probed SCSI disks and
650 CD-ROMs. It definitely reduces the average seek distance when doing
651 random seeks, but this does not necessarily result in a noticeable
652 performance improvement: your mileage may vary...
653 This is equivalent to the "eata=lc:y" boot option.
655 config SCSI_EATA_MAX_TAGS
656 int "maximum number of queued commands"
660 This specifies how many SCSI commands can be maximally queued for
661 each probed SCSI device. You should reduce the default value of 16
662 only if you have disks with buggy or limited tagged command support.
663 Minimum is 2 and maximum is 62. This value is also the window size
664 used by the elevator sorting option above. The effective value used
665 by the driver for each probed SCSI device is reported at boot time.
666 This is equivalent to the "eata=mq:8" boot option.
669 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
670 depends on (ISA || EISA || PCI) && SCSI && BROKEN
672 This driver supports all EATA-PIO protocol compliant SCSI Host
673 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
674 host adapters could also use this driver but are discouraged from
675 doing so, since this driver only supports hard disks and lacks
676 numerous features. You might want to have a look at the SCSI-HOWTO,
677 available from <http://www.tldp.org/docs.html#howto>.
679 To compile this driver as a module, choose M here: the
680 module will be called eata_pio.
682 config SCSI_FUTURE_DOMAIN
683 tristate "Future Domain 16xx SCSI/AHA-2920A support"
684 depends on (ISA || PCI) && SCSI
685 select CHECK_SIGNATURE
687 This is support for Future Domain's 16-bit SCSI host adapters
688 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
689 other adapters based on the Future Domain chipsets (Quantum
690 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
691 It is explained in section 3.7 of the SCSI-HOWTO, available from
692 <http://www.tldp.org/docs.html#howto>.
694 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
695 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
696 controller support"). This Future Domain driver works with the older
697 Adaptec AHA-2920A boards with a Future Domain chip on them.
699 To compile this driver as a module, choose M here: the
700 module will be called fdomain.
703 tristate "Future Domain MCS-600/700 SCSI support"
704 depends on MCA_LEGACY && SCSI
706 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
707 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
708 is identical to the MCS 700 and hence also supported by this driver.
709 This driver also supports the Reply SB16/SCSI card (the SCSI part).
710 It supports multiple adapters in the same system.
712 To compile this driver as a module, choose M here: the
713 module will be called fd_mcs.
716 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
717 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API && PCI_LEGACY
719 Formerly called GDT SCSI Disk Array Controller Support.
721 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
722 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
723 in the kernel source in <file:drivers/scsi/gdth.c> and
724 <file:drivers/scsi/gdth.h>.
726 To compile this driver as a module, choose M here: the
727 module will be called gdth.
729 config SCSI_GENERIC_NCR5380
730 tristate "Generic NCR5380/53c400 SCSI PIO support"
731 depends on ISA && SCSI
732 select SCSI_SPI_ATTRS
734 This is a driver for the old NCR 53c80 series of SCSI controllers
735 on boards using PIO. Most boards such as the Trantor T130 fit this
736 category, along with a large number of ISA 8bit controllers shipped
737 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
738 you should select the specific driver for that card rather than
739 generic 5380 support.
741 It is explained in section 3.8 of the SCSI-HOWTO, available from
742 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
743 of the box, you may have to change some settings in
744 <file:drivers/scsi/g_NCR5380.h>.
746 To compile this driver as a module, choose M here: the
747 module will be called g_NCR5380.
749 config SCSI_GENERIC_NCR5380_MMIO
750 tristate "Generic NCR5380/53c400 SCSI MMIO support"
751 depends on ISA && SCSI
752 select SCSI_SPI_ATTRS
754 This is a driver for the old NCR 53c80 series of SCSI controllers
755 on boards using memory mapped I/O.
756 It is explained in section 3.8 of the SCSI-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
758 of the box, you may have to change some settings in
759 <file:drivers/scsi/g_NCR5380.h>.
761 To compile this driver as a module, choose M here: the
762 module will be called g_NCR5380_mmio.
764 config SCSI_GENERIC_NCR53C400
765 bool "Enable NCR53c400 extensions"
766 depends on SCSI_GENERIC_NCR5380
768 This enables certain optimizations for the NCR53c400 SCSI cards.
769 You might as well try it out. Note that this driver will only probe
770 for the Trantor T130B in its default configuration; you might have
771 to pass a command line option to the kernel at boot time if it does
772 not detect your card. See the file
773 <file:Documentation/scsi/g_NCR5380.txt> for details.
776 tristate "IBMMCA SCSI support"
777 depends on MCA && SCSI
779 This is support for the IBM SCSI adapter found in many of the PS/2
780 series computers. These machines have an MCA bus, so you need to
781 answer Y to "MCA support" as well and read
782 <file:Documentation/mca.txt>.
784 If the adapter isn't found during boot (a common problem for models
785 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
786 option, where <pun> is the id of the SCSI subsystem (usually 7, but
787 if that doesn't work check your reference diskette). Owners of
788 model 95 with a LED-matrix-display can in addition activate some
789 activity info like under OS/2, but more informative, by setting
790 'ibmmcascsi=display' as an additional kernel parameter. Try "man
791 bootparam" or see the documentation of your boot loader about how to
792 pass options to the kernel.
794 To compile this driver as a module, choose M here: the
795 module will be called ibmmca.
797 config IBMMCA_SCSI_ORDER_STANDARD
798 bool "Standard SCSI-order"
799 depends on SCSI_IBMMCA
801 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
802 are assigned to the drive letters, starting with the lowest SCSI-id
803 (physical number -- pun) to be drive C:, as seen from DOS and
804 similar operating systems. When looking into papers describing the
805 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
806 The SCSI-standard follows a hardware-hierarchy which says that id 7
807 has the highest priority and id 0 the lowest. Therefore, the host
808 adapters are still today everywhere placed as SCSI-id 7 by default.
809 In the SCSI-standard, the drive letters express the priority of the
810 disk. C: should be the hard disk, or a partition on it, with the
811 highest priority. This must therefore be the disk with the highest
812 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
813 original definition of the SCSI-standard as also industrial- and
814 process-control-machines, like VME-CPUs running under realtime-OSes
815 (e.g. LynxOS, OS9) do.
817 If you like to run Linux on your MCA-machine with the same
818 assignment of hard disks as seen from e.g. DOS or OS/2 on your
819 machine, which is in addition conformant to the SCSI-standard, you
820 must say Y here. This is also necessary for MCA-Linux users who want
821 to keep downward compatibility to older releases of the
822 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
825 If you like to have the lowest SCSI-id assigned as drive C:, as
826 modern SCSI-BIOSes do, which does not conform to the standard, but
827 is widespread and common in the PC-world of today, you must say N
828 here. If unsure, say Y.
830 config IBMMCA_SCSI_DEV_RESET
831 bool "Reset SCSI-devices at boottime"
832 depends on SCSI_IBMMCA
834 By default, SCSI-devices are reset when the machine is powered on.
835 However, some devices exist, like special-control-devices,
836 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
837 not reset when switched on. If you say Y here, each device connected
838 to your SCSI-bus will be issued a reset-command after it has been
839 probed, while the kernel is booting. This may cause problems with
840 more modern devices, like hard disks, which do not appreciate these
841 reset commands, and can cause your system to hang. So say Y only if
842 you know that one of your older devices needs it; N is the safe
846 tristate "IBM ServeRAID support"
847 depends on PCI && SCSI
849 This is support for the IBM ServeRAID hardware RAID controllers.
850 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
851 for more information. If this driver does not work correctly
852 without modification please contact the author by email at
853 <ipslinux@adaptec.com>.
855 To compile this driver as a module, choose M here: the
856 module will be called ips.
859 tristate "IBM Virtual SCSI support"
860 depends on PPC_PSERIES || PPC_ISERIES
861 select SCSI_SRP_ATTRS
863 This is the IBM POWER Virtual SCSI Client
865 To compile this driver as a module, choose M here: the
866 module will be called ibmvscsic.
868 config SCSI_IBMVSCSIS
869 tristate "IBM Virtual SCSI Server support"
870 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
872 This is the SRP target driver for IBM pSeries virtual environments.
874 The userspace component needed to initialize the driver and
875 documentation can be found:
877 http://stgt.berlios.de/
879 To compile this driver as a module, choose M here: the
880 module will be called ibmvstgt.
883 tristate "Initio 9100U(W) support"
884 depends on PCI && SCSI
886 This is support for the Initio 91XXU(W) SCSI host adapter. Please
887 read the SCSI-HOWTO, available from
888 <http://www.tldp.org/docs.html#howto>.
890 To compile this driver as a module, choose M here: the
891 module will be called initio.
894 tristate "Initio INI-A100U2W support"
895 depends on PCI && SCSI
897 This is support for the Initio INI-A100U2W SCSI host adapter.
898 Please read the SCSI-HOWTO, available from
899 <http://www.tldp.org/docs.html#howto>.
901 To compile this driver as a module, choose M here: the
902 module will be called a100u2w.
905 tristate "IOMEGA parallel port (ppa - older drives)"
906 depends on SCSI && PARPORT_PC
908 This driver supports older versions of IOMEGA's parallel port ZIP
909 drive (a 100 MB removable media device).
911 Note that you can say N here if you have the SCSI version of the ZIP
912 drive: it will be supported automatically if you said Y to the
913 generic "SCSI disk support", above.
915 If you have the ZIP Plus drive or a more recent parallel port ZIP
916 drive (if the supplied cable with the drive is labeled "AutoDetect")
917 then you should say N here and Y to "IOMEGA parallel port (imm -
918 newer drives)", below.
920 For more information about this driver and how to use it you should
921 read the file <file:Documentation/scsi/ppa.txt>. You should also read
922 the SCSI-HOWTO, which is available from
923 <http://www.tldp.org/docs.html#howto>. If you use this driver,
924 you will still be able to use the parallel port for other tasks,
925 such as a printer; it is safe to compile both drivers into the
928 To compile this driver as a module, choose M here: the
929 module will be called ppa.
932 tristate "IOMEGA parallel port (imm - newer drives)"
933 depends on SCSI && PARPORT_PC
935 This driver supports newer versions of IOMEGA's parallel port ZIP
936 drive (a 100 MB removable media device).
938 Note that you can say N here if you have the SCSI version of the ZIP
939 drive: it will be supported automatically if you said Y to the
940 generic "SCSI disk support", above.
942 If you have the ZIP Plus drive or a more recent parallel port ZIP
943 drive (if the supplied cable with the drive is labeled "AutoDetect")
944 then you should say Y here; if you have an older ZIP drive, say N
945 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
947 For more information about this driver and how to use it you should
948 read the file <file:Documentation/scsi/ppa.txt>. You should also read
949 the SCSI-HOWTO, which is available from
950 <http://www.tldp.org/docs.html#howto>. If you use this driver,
951 you will still be able to use the parallel port for other tasks,
952 such as a printer; it is safe to compile both drivers into the
955 To compile this driver as a module, choose M here: the
956 module will be called imm.
958 config SCSI_IZIP_EPP16
959 bool "ppa/imm option - Use slow (but safe) EPP-16"
960 depends on SCSI_PPA || SCSI_IMM
962 EPP (Enhanced Parallel Port) is a standard for parallel ports which
963 allows them to act as expansion buses that can handle up to 64
966 Some parallel port chipsets are slower than their motherboard, and
967 so we have to control the state of the chipset's FIFO queue every
968 now and then to avoid data loss. This will be done if you say Y
971 Generally, saying Y is the safe option and slows things down a bit.
973 config SCSI_IZIP_SLOW_CTR
974 bool "ppa/imm option - Assume slow parport control register"
975 depends on SCSI_PPA || SCSI_IMM
977 Some parallel ports are known to have excessive delays between
978 changing the parallel port control register and good data being
979 available on the parallel port data/status register. This option
980 forces a small delay (1.0 usec to be exact) after changing the
981 control register to let things settle out. Enabling this option may
982 result in a big drop in performance but some very old parallel ports
983 (found in 386 vintage machines) will not work properly.
985 Generally, saying N is fine.
987 config SCSI_NCR53C406A
988 tristate "NCR53c406a SCSI support"
989 depends on ISA && SCSI
991 This is support for the NCR53c406a SCSI host adapter. For user
992 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
993 in the kernel source. Also read the SCSI-HOWTO, available from
994 <http://www.tldp.org/docs.html#howto>.
996 To compile this driver as a module, choose M here: the
997 module will be called NCR53c406.
1000 tristate "NCR Dual 700 MCA SCSI support"
1001 depends on MCA && SCSI
1002 select SCSI_SPI_ATTRS
1004 This is a driver for the MicroChannel Dual 700 card produced by
1005 NCR and commonly used in 345x/35xx/4100 class machines. It always
1006 tries to negotiate sync and uses tag command queueing.
1008 Unless you have an NCR manufactured machine, the chances are that
1009 you do not have this SCSI card, so say N.
1012 tristate "HP Lasi SCSI support for 53c700/710"
1013 depends on GSC && SCSI
1014 select SCSI_SPI_ATTRS
1016 This is a driver for the SCSI controller in the Lasi chip found in
1017 many PA-RISC workstations & servers. If you do not know whether you
1018 have a Lasi chip, it is safe to say "Y" here.
1020 config SCSI_SNI_53C710
1021 tristate "SNI RM SCSI support for 53c710"
1022 depends on SNI_RM && SCSI
1023 select SCSI_SPI_ATTRS
1024 select 53C700_LE_ON_BE
1026 This is a driver for the onboard SCSI controller found in older
1027 SNI RM workstations & servers.
1029 config 53C700_LE_ON_BE
1031 depends on SCSI_LASI700
1035 tristate "Promise SuperTrak EX Series support"
1036 depends on PCI && SCSI
1038 This driver supports Promise SuperTrak EX series storage controllers.
1040 Promise provides Linux RAID configuration utility for these
1041 controllers. Please visit <http://www.promise.com> to download.
1043 To compile this driver as a module, choose M here: the
1044 module will be called stex.
1046 config 53C700_BE_BUS
1048 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1051 config SCSI_SYM53C8XX_2
1052 tristate "SYM53C8XX Version 2 SCSI support"
1053 depends on PCI && SCSI
1054 select SCSI_SPI_ATTRS
1056 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1057 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1058 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1059 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1060 controllers; you need to use the Fusion MPT driver for that.
1062 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1065 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1066 int "DMA addressing mode"
1067 depends on SCSI_SYM53C8XX_2
1070 This option only applies to PCI-SCSI chips that are PCI DAC
1071 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1073 When set to 0, the driver will program the chip to only perform
1074 32-bit DMA. When set to 1, the chip will be able to perform DMA
1075 to addresses up to 1TB. When set to 2, the driver supports the
1076 full 64-bit DMA address range, but can only address 16 segments
1077 of 4 GB each. This limits the total addressable range to 64 GB.
1079 Most machines with less than 4GB of memory should use a setting
1080 of 0 for best performance. If your machine has 4GB of memory
1081 or more, you should set this option to 1 (the default).
1083 The still experimental value 2 (64 bit DMA addressing with 16
1084 x 4GB segments limitation) can be used on systems that require
1085 PCI address bits past bit 39 to be set for the addressing of
1086 memory using PCI DAC cycles.
1088 config SCSI_SYM53C8XX_DEFAULT_TAGS
1089 int "Default tagged command queue depth"
1090 depends on SCSI_SYM53C8XX_2
1093 This is the default value of the command queue depth the
1094 driver will announce to the generic SCSI layer for devices
1095 that support tagged command queueing. This value can be changed
1096 from the boot command line. This is a soft limit that cannot
1097 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1099 config SCSI_SYM53C8XX_MAX_TAGS
1100 int "Maximum number of queued commands"
1101 depends on SCSI_SYM53C8XX_2
1104 This option allows you to specify the maximum number of commands
1105 that can be queued to any device, when tagged command queuing is
1106 possible. The driver supports up to 256 queued commands per device.
1107 This value is used as a compiled-in hard limit.
1109 config SCSI_SYM53C8XX_MMIO
1110 bool "Use memory mapped IO"
1111 depends on SCSI_SYM53C8XX_2
1114 Memory mapped IO is faster than Port IO. Most people should
1115 answer Y here, but some machines may have problems. If you have
1116 to answer N here, please report the problem to the maintainer.
1119 tristate "IBM Power Linux RAID adapter support"
1120 depends on PCI && SCSI && ATA
1123 This driver supports the IBM Power Linux family RAID adapters.
1124 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1125 as IBM iSeries 5702, 5703, 5709, and 570A.
1127 config SCSI_IPR_TRACE
1128 bool "enable driver internal trace"
1132 If you say Y here, the driver will trace all commands issued
1133 to the adapter. Performance impact is minimal. Trace can be
1134 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1136 config SCSI_IPR_DUMP
1137 bool "enable adapter dump support"
1141 If you say Y here, the driver will support adapter crash dump.
1142 If you enable this support, the iprdump daemon can be used
1143 to capture adapter failure analysis information.
1146 tristate "Zalon SCSI support"
1147 depends on GSC && SCSI
1148 select SCSI_SPI_ATTRS
1150 The Zalon is a GSC/HSC bus interface chip that sits between the
1151 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1152 C110, J200, J210 and some D, K & R-class machines. It's also
1153 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1154 Say Y here if you have one of these machines or cards.
1156 config SCSI_NCR_Q720
1157 tristate "NCR Quad 720 MCA SCSI support"
1158 depends on MCA && SCSI
1159 select SCSI_SPI_ATTRS
1161 This is a driver for the MicroChannel Quad 720 card produced by
1162 NCR and commonly used in 345x/35xx/4100 class machines. It always
1163 tries to negotiate sync and uses tag command queueing.
1165 Unless you have an NCR manufactured machine, the chances are that
1166 you do not have this SCSI card, so say N.
1168 config SCSI_NCR53C8XX_DEFAULT_TAGS
1169 int "default tagged command queue depth"
1170 depends on SCSI_ZALON || SCSI_NCR_Q720
1173 "Tagged command queuing" is a feature of SCSI-2 which improves
1174 performance: the host adapter can send several SCSI commands to a
1175 device's queue even if previous commands haven't finished yet.
1176 Because the device is intelligent, it can optimize its operations
1177 (like head positioning) based on its own request queue. Some SCSI
1178 devices don't implement this properly; if you want to disable this
1179 feature, enter 0 or 1 here (it doesn't matter which).
1181 The default value is 8 and should be supported by most hard disks.
1182 This value can be overridden from the boot command line using the
1183 'tags' option as follows (example):
1184 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1185 4, set queue depth to 16 for target 2 and target 3 on controller 0
1186 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1188 The normal answer therefore is to go with the default 8 and to use
1189 a boot command line option for devices that need to use a different
1190 command queue depth.
1192 There is no safe option other than using good SCSI devices.
1194 config SCSI_NCR53C8XX_MAX_TAGS
1195 int "maximum number of queued commands"
1196 depends on SCSI_ZALON || SCSI_NCR_Q720
1199 This option allows you to specify the maximum number of commands
1200 that can be queued to any device, when tagged command queuing is
1201 possible. The default value is 32. Minimum is 2, maximum is 64.
1202 Modern hard disks are able to support 64 tags and even more, but
1203 do not seem to be faster when more than 32 tags are being used.
1205 So, the normal answer here is to go with the default value 32 unless
1206 you are using very large hard disks with large cache (>= 1 MB) that
1207 are able to take advantage of more than 32 tagged commands.
1209 There is no safe option and the default answer is recommended.
1211 config SCSI_NCR53C8XX_SYNC
1212 int "synchronous transfers frequency in MHz"
1213 depends on SCSI_ZALON || SCSI_NCR_Q720
1216 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1217 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1218 are respectively the maximum data transfer rates in mega-transfers
1219 per second for each class. For example, a FAST-20 Wide 16 device is
1220 able to transfer data at 20 million 16 bit packets per second for a
1221 total rate of 40 MB/s.
1223 You may specify 0 if you want to only use asynchronous data
1224 transfers. This is the safest and slowest option. Otherwise, specify
1225 a value between 5 and 80, depending on the capability of your SCSI
1226 controller. The higher the number, the faster the data transfer.
1227 Note that 80 should normally be ok since the driver decreases the
1228 value automatically according to the controller's capabilities.
1230 Your answer to this question is ignored for controllers with NVRAM,
1231 since the driver will get this information from the user set-up. It
1232 also can be overridden using a boot setup option, as follows
1233 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1234 for FAST-20 synchronous data transfer (20 mega-transfers per
1237 The normal answer therefore is not to go with the default but to
1238 select the maximum value 80 allowing the driver to use the maximum
1239 value supported by each controller. If this causes problems with
1240 your SCSI devices, you should come back and decrease the value.
1242 There is no safe option other than using good cabling, right
1243 terminations and SCSI conformant devices.
1245 config SCSI_NCR53C8XX_NO_DISCONNECT
1246 bool "not allow targets to disconnect"
1247 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1249 This option is only provided for safety if you suspect some SCSI
1250 device of yours to not support properly the target-disconnect
1251 feature. In that case, you would say Y here. In general however, to
1252 not allow targets to disconnect is not reasonable if there is more
1253 than 1 device on a SCSI bus. The normal answer therefore is N.
1256 tristate "PAS16 SCSI support"
1257 depends on ISA && SCSI
1258 select SCSI_SPI_ATTRS
1260 This is support for a SCSI host adapter. It is explained in section
1261 3.10 of the SCSI-HOWTO, available from
1262 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1263 of the box, you may have to change some settings in
1264 <file:drivers/scsi/pas16.h>.
1266 To compile this driver as a module, choose M here: the
1267 module will be called pas16.
1269 config SCSI_QLOGIC_FAS
1270 tristate "Qlogic FAS SCSI support"
1271 depends on ISA && SCSI
1273 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1274 FastSCSI! cards as well as any other card based on the FASXX chip
1275 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1277 This driver does NOT support the PCI versions of these cards. The
1278 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1279 SCSI support"), below.
1281 Information about this driver is contained in
1282 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1283 SCSI-HOWTO, available from
1284 <http://www.tldp.org/docs.html#howto>.
1286 To compile this driver as a module, choose M here: the
1287 module will be called qlogicfas.
1289 config SCSI_QLOGIC_FC_FIRMWARE
1290 bool "Include loadable firmware in driver"
1291 depends on SCSI_QLOGIC_FC
1293 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1294 expanded LUN addressing and FcTape (FCP-2) support, in the
1295 qlogicfc driver. This is required on some platforms.
1297 config SCSI_QLOGIC_1280
1298 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1299 depends on PCI && SCSI
1301 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1303 To compile this driver as a module, choose M here: the
1304 module will be called qla1280.
1306 config SCSI_QLOGICPTI
1307 tristate "PTI Qlogic, ISP Driver"
1308 depends on SBUS && SCSI
1310 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1311 controllers are known under Solaris as qpti and in the openprom as
1312 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1313 driven by a different driver.
1315 To compile this driver as a module, choose M here: the
1316 module will be called qlogicpti.
1318 source "drivers/scsi/qla2xxx/Kconfig"
1319 source "drivers/scsi/qla4xxx/Kconfig"
1322 tristate "Emulex LightPulse Fibre Channel Support"
1323 depends on PCI && SCSI
1324 select SCSI_FC_ATTRS
1326 This lpfc driver supports the Emulex LightPulse
1327 Family of Fibre Channel PCI host adapters.
1330 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1331 depends on (EISA || MCA) && SCSI
1332 select SCSI_SPI_ATTRS
1334 This driver for NCR53c710 based SCSI host adapters.
1336 It currently supports Compaq EISA cards and NCR MCA cards
1338 config SCSI_SYM53C416
1339 tristate "Symbios 53c416 SCSI support"
1340 depends on ISA && SCSI
1342 This is support for the sym53c416 SCSI host adapter, the SCSI
1343 adapter that comes with some HP scanners. This driver requires that
1344 the sym53c416 is configured first using some sort of PnP
1345 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1346 are using isapnp then you need to compile this driver as a module
1347 and then load it using insmod after isapnp has run. The parameters
1348 of the configured card(s) should be passed to the driver. The format
1351 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1353 To compile this driver as a module, choose M here: the
1354 module will be called sym53c416.
1357 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1358 depends on PCI && SCSI && EXPERIMENTAL
1360 This driver supports PCI SCSI host adapters based on the ASIC
1361 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1363 This driver works, but is still in experimental status. So better
1364 have a bootable disk and a backup in case of emergency.
1366 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1368 To compile this driver as a module, choose M here: the
1369 module will be called dc395x.
1372 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1373 depends on PCI && SCSI
1375 This driver supports PCI SCSI host adapters based on the Am53C974A
1376 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1377 PCscsi/PCnet (Am53/79C974) solutions.
1379 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1381 Note that this driver does NOT support Tekram DC390W/U/F, which are
1382 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1384 To compile this driver as a module, choose M here: the
1385 module will be called tmscsim.
1388 tristate "Trantor T128/T128F/T228 SCSI support"
1389 depends on ISA && SCSI
1390 select SCSI_SPI_ATTRS
1391 select CHECK_SIGNATURE
1393 This is support for a SCSI host adapter. It is explained in section
1394 3.11 of the SCSI-HOWTO, available from
1395 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1396 of the box, you may have to change some settings in
1397 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1398 Adaptec, and some former Trantor products are being sold under the
1401 To compile this driver as a module, choose M here: the
1402 module will be called t128.
1405 tristate "UltraStor 14F/34F support"
1406 depends on ISA && SCSI && ISA_DMA_API
1408 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1409 The source at <file:drivers/scsi/u14-34f.c> contains some
1410 information about this hardware. If the driver doesn't work out of
1411 the box, you may have to change some settings in
1412 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1413 <http://www.tldp.org/docs.html#howto>. Note that there is also
1414 another driver for the same hardware: "UltraStor SCSI support",
1415 below. You should say Y to both only if you want 24F support as
1418 To compile this driver as a module, choose M here: the
1419 module will be called u14-34f.
1421 config SCSI_U14_34F_TAGGED_QUEUE
1422 bool "enable tagged command queueing"
1423 depends on SCSI_U14_34F
1425 This is a feature of SCSI-2 which improves performance: the host
1426 adapter can send several SCSI commands to a device's queue even if
1427 previous commands haven't finished yet.
1428 This is equivalent to the "u14-34f=tc:y" boot option.
1430 config SCSI_U14_34F_LINKED_COMMANDS
1431 bool "enable elevator sorting"
1432 depends on SCSI_U14_34F
1434 This option enables elevator sorting for all probed SCSI disks and
1435 CD-ROMs. It definitely reduces the average seek distance when doing
1436 random seeks, but this does not necessarily result in a noticeable
1437 performance improvement: your mileage may vary...
1438 This is equivalent to the "u14-34f=lc:y" boot option.
1440 config SCSI_U14_34F_MAX_TAGS
1441 int "maximum number of queued commands"
1442 depends on SCSI_U14_34F
1445 This specifies how many SCSI commands can be maximally queued for
1446 each probed SCSI device. You should reduce the default value of 8
1447 only if you have disks with buggy or limited tagged command support.
1448 Minimum is 2 and maximum is 14. This value is also the window size
1449 used by the elevator sorting option above. The effective value used
1450 by the driver for each probed SCSI device is reported at boot time.
1451 This is equivalent to the "u14-34f=mq:8" boot option.
1453 config SCSI_ULTRASTOR
1454 tristate "UltraStor SCSI support"
1455 depends on X86 && ISA && SCSI
1457 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1458 adapter family. This driver is explained in section 3.12 of the
1459 SCSI-HOWTO, available from
1460 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1461 of the box, you may have to change some settings in
1462 <file:drivers/scsi/ultrastor.h>.
1464 Note that there is also another driver for the same hardware:
1465 "UltraStor 14F/34F support", above.
1467 To compile this driver as a module, choose M here: the
1468 module will be called ultrastor.
1471 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1472 depends on PCI && SCSI && !64BIT
1474 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1475 SCSI host adapter. Please read the SCSI-HOWTO, available from
1476 <http://www.tldp.org/docs.html#howto>.
1478 To compile this driver as a module, choose M here: the
1479 module will be called nsp32.
1482 tristate "SCSI debugging host simulator"
1485 This is a host adapter simulator that can simulate multiple hosts
1486 each with multiple dummy SCSI devices (disks). It defaults to one
1487 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1488 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1489 dummy disks are simulated, they share the same kernel RAM for
1490 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1491 information. This driver is primarily of use to those testing the
1492 SCSI and block subsystems. If unsure, say N.
1495 tristate "MESH (Power Mac internal SCSI) support"
1496 depends on PPC32 && PPC_PMAC && SCSI
1498 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1499 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1500 other Power Macintoshes do). Say Y to include support for this SCSI
1503 To compile this driver as a module, choose M here: the
1504 module will be called mesh.
1506 config SCSI_MESH_SYNC_RATE
1507 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1508 depends on SCSI_MESH
1511 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1512 drives a bus which is entirely internal to the machine (such as the
1513 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1514 operation at up to 10 MB/s. On machines where the SCSI bus
1515 controlled by the MESH can have external devices connected, it is
1516 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1517 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1518 to disable synchronous operation.
1520 config SCSI_MESH_RESET_DELAY_MS
1521 int "initial bus reset delay (ms) (0 = no reset)"
1522 depends on SCSI_MESH
1525 config SCSI_MAC53C94
1526 tristate "53C94 (Power Mac external SCSI) support"
1527 depends on PPC32 && PPC_PMAC && SCSI
1529 On Power Macintoshes (and clones) with two SCSI buses, the external
1530 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1531 machines which only have one SCSI bus, such as the 7200, also use
1532 the 53C94. Say Y to include support for the 53C94.
1534 To compile this driver as a module, choose M here: the
1535 module will be called mac53c94.
1537 source "drivers/scsi/arm/Kconfig"
1540 bool "MIPS JAZZ FAS216 SCSI support"
1541 depends on MACH_JAZZ && SCSI
1542 select SCSI_SPI_ATTRS
1544 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1545 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1549 tristate "A3000 WD33C93A support"
1550 depends on AMIGA && SCSI
1552 If you have an Amiga 3000 and have SCSI devices connected to the
1553 built-in SCSI controller, say Y. Otherwise, say N.
1555 To compile this driver as a module, choose M here: the
1556 module will be called a3000.
1559 tristate "A2091/A590 WD33C93A support"
1560 depends on ZORRO && SCSI
1562 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1565 To compile this driver as a module, choose M here: the
1566 module will be called a2091.
1569 tristate "GVP Series II WD33C93A support"
1570 depends on ZORRO && SCSI
1572 If you have a Great Valley Products Series II SCSI controller,
1573 answer Y. Also say Y if you have a later model of GVP SCSI
1574 controller (such as the GVP A4008 or a Combo board). Otherwise,
1575 answer N. This driver does NOT work for the T-Rex series of
1576 accelerators from TekMagic and GVP-M.
1578 To compile this driver as a module, choose M here: the
1579 module will be called gvp11.
1582 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1583 depends on AMIGA && SCSI && EXPERIMENTAL
1584 select SCSI_SPI_ATTRS
1586 If you have an Amiga 4000T and have SCSI devices connected to the
1587 built-in SCSI controller, say Y. Otherwise, say N.
1589 To compile this driver as a module, choose M here: the
1590 module will be called a4000t.
1592 config SCSI_ZORRO7XX
1593 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1594 depends on ZORRO && SCSI && EXPERIMENTAL
1595 select SCSI_SPI_ATTRS
1597 Support for various NCR53c710-based SCSI controllers on Zorro
1598 expansion boards for the Amiga.
1600 - the Amiga 4091 Zorro III SCSI-2 controller,
1601 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1603 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1604 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1605 accelerator card for the Amiga 1200,
1606 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1609 tristate "Atari native SCSI support"
1610 depends on ATARI && SCSI
1611 select SCSI_SPI_ATTRS
1613 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1614 Falcon, ...) say Y to get it supported. Of course also, if you have
1615 a compatible SCSI controller (e.g. for Medusa).
1617 To compile this driver as a module, choose M here: the
1618 module will be called atari_scsi.
1620 This driver supports both styles of NCR integration into the
1621 system: the TT style (separate DMA), and the Falcon style (via
1622 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1623 in the Hades (without DMA).
1625 config ATARI_SCSI_TOSHIBA_DELAY
1626 bool "Long delays for Toshiba CD-ROMs"
1627 depends on ATARI_SCSI
1629 This option increases the delay after a SCSI arbitration to
1630 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1631 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1632 would impact performance a bit, so say N.
1634 config ATARI_SCSI_RESET_BOOT
1635 bool "Reset SCSI-devices at boottime"
1636 depends on ATARI_SCSI
1638 Reset the devices on your Atari whenever it boots. This makes the
1639 boot process fractionally longer but may assist recovery from errors
1640 that leave the devices with SCSI operations partway completed.
1643 bool "Hades SCSI DMA emulator"
1644 depends on ATARI_SCSI && HADES
1646 This option enables code which emulates the TT SCSI DMA chip on the
1647 Hades. This increases the SCSI transfer rates at least ten times
1648 compared to PIO transfers.
1651 bool "Macintosh NCR5380 SCSI"
1652 depends on MAC && SCSI=y
1653 select SCSI_SPI_ATTRS
1655 This is the NCR 5380 SCSI controller included on most of the 68030
1656 based Macintoshes. If you have one of these say Y and read the
1657 SCSI-HOWTO, available from
1658 <http://www.tldp.org/docs.html#howto>.
1661 bool "WD33C93 SCSI driver for MVME147"
1662 depends on MVME147 && SCSI=y
1663 select SCSI_SPI_ATTRS
1665 Support for the on-board SCSI controller on the Motorola MVME147
1666 single-board computer.
1669 tristate "NCR53C710 SCSI driver for MVME16x"
1670 depends on MVME16x && SCSI
1671 select SCSI_SPI_ATTRS
1673 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1674 SCSI controller chip. Almost everyone using one of these boards
1675 will want to say Y to this question.
1677 config BVME6000_SCSI
1678 tristate "NCR53C710 SCSI driver for BVME6000"
1679 depends on BVME6000 && SCSI
1680 select SCSI_SPI_ATTRS
1682 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1683 SCSI controller chip. Almost everyone using one of these boards
1684 will want to say Y to this question.
1687 tristate "Sun3 NCR5380 SCSI"
1688 depends on SUN3 && SCSI
1689 select SCSI_SPI_ATTRS
1691 This option will enable support for the OBIO (onboard io) NCR5380
1692 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1693 "Sun3" type VME scsi controllers also based on the NCR5380.
1694 General Linux information on the Sun 3 series (now discontinued)
1695 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1698 bool "Sun3x ESP SCSI"
1699 depends on SUN3X && SCSI=y
1700 select SCSI_SPI_ATTRS
1702 The ESP was an on-board SCSI controller used on Sun 3/80
1703 machines. Say Y here to compile in support for it.
1706 tristate "Sparc ESP Scsi Driver"
1707 depends on SBUS && SCSI
1708 select SCSI_SPI_ATTRS
1710 This is the driver for the Sun ESP SCSI host adapter. The ESP
1711 chipset is present in most SPARC SBUS-based computers.
1713 To compile this driver as a module, choose M here: the
1714 module will be called esp.
1717 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1718 depends on S390 && QDIO && SCSI
1719 select SCSI_FC_ATTRS
1721 If you want to access SCSI devices attached to your IBM eServer
1722 zSeries by means of Fibre Channel interfaces say Y.
1723 For details please refer to the documentation provided by IBM at
1724 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1726 This driver is also available as a module. This module will be
1727 called zfcp. If you want to compile it as a module, say M here
1728 and read <file:Documentation/kbuild/modules.txt>.
1731 tristate "SCSI RDMA Protocol helper library"
1732 depends on SCSI && PCI
1735 If you wish to use SRP target drivers, say Y.
1737 To compile this driver as a module, choose M here: the
1738 module will be called libsrp.
1740 endif # SCSI_LOWLEVEL
1742 source "drivers/scsi/pcmcia/Kconfig"