1 menu "SCSI device support"
4 tristate "RAID Transport Class"
10 tristate "SCSI device support"
12 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
13 any other SCSI device under Linux, say Y and make sure that you know
14 the name of your SCSI host adapter (the card inside your computer
15 that "speaks" the SCSI protocol, also called SCSI controller),
16 because you will be asked for it.
18 You also need to say Y here if you have a device which speaks
19 the SCSI protocol. Examples of this include the parallel port
20 version of the IOMEGA ZIP drive, USB storage devices, Fibre
21 Channel, FireWire storage and the IDE-SCSI emulation driver.
23 To compile this driver as a module, choose M here and read
24 <file:Documentation/scsi/scsi.txt>.
25 The module will be called scsi_mod.
27 However, do not compile this as a module if your root file system
28 (the one containing the directory /) is located on a SCSI device.
31 bool "legacy /proc/scsi/ support"
32 depends on SCSI && PROC_FS
35 This option enables support for the various files in
36 /proc/scsi. In Linux 2.6 this has been superceeded by
37 files in sysfs but many legacy applications rely on this.
41 comment "SCSI support type (disk, tape, CD-ROM)"
45 tristate "SCSI disk support"
48 If you want to use SCSI hard disks, Fibre Channel disks,
49 USB storage or the SCSI or parallel port version of
50 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
51 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
52 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
55 To compile this driver as a module, choose M here and read
56 <file:Documentation/scsi/scsi.txt>.
57 The module will be called sd_mod.
59 Do not compile this driver as a module if your root file system
60 (the one containing the directory /) is located on a SCSI disk.
61 In this case, do not compile the driver for your SCSI host adapter
62 (below) as a module either.
65 tristate "SCSI tape support"
68 If you want to use a SCSI tape drive under Linux, say Y and read the
69 SCSI-HOWTO, available from
70 <http://www.tldp.org/docs.html#howto>, and
71 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
74 To compile this driver as a module, choose M here and read
75 <file:Documentation/scsi/scsi.txt>. The module will be called st.
78 tristate "SCSI OnStream SC-x0 tape support"
81 The OnStream SC-x0 SCSI tape drives can not be driven by the
82 standard st driver, but instead need this special osst driver and
83 use the /dev/osstX char device nodes (major 206). Via usb-storage
84 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
85 as well. Note that there is also a second generation of OnStream
86 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
87 tapes (QIC-157) and can be driven by the standard driver st.
88 For more information, you may have a look at the SCSI-HOWTO
89 <http://www.tldp.org/docs.html#howto> and
90 <file:Documentation/scsi/osst.txt> in the kernel source.
91 More info on the OnStream driver may be found on
92 <http://linux1.onstream.nl/test/>
93 Please also have a look at the standard st docu, as most of it
94 applies to osst as well.
96 To compile this driver as a module, choose M here and read
97 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
100 tristate "SCSI CDROM support"
103 If you want to use a SCSI or FireWire CD-ROM under Linux,
104 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
105 <http://www.tldp.org/docs.html#howto>. Also make sure to say
106 Y or M to "ISO 9660 CD-ROM file system support" later.
108 To compile this driver as a module, choose M here and read
109 <file:Documentation/scsi/scsi.txt>.
110 The module will be called sr_mod.
112 config BLK_DEV_SR_VENDOR
113 bool "Enable vendor-specific extensions (for SCSI CDROM)"
114 depends on BLK_DEV_SR
116 This enables the usage of vendor specific SCSI commands. This is
117 required to support multisession CDs with old NEC/TOSHIBA cdrom
118 drives (and HP Writers). If you have such a drive and get the first
119 session only, try saying Y here; everybody else says N.
122 tristate "SCSI generic support"
125 If you want to use SCSI scanners, synthesizers or CD-writers or just
126 about anything having "SCSI" in its name other than hard disks,
127 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
128 directly, so you need some additional software which knows how to
129 talk to these devices using the SCSI protocol:
131 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
132 writer software look at Cdrtools
133 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
134 and for burning a "disk at once": CDRDAO
135 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
136 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
137 For other devices, it's possible that you'll have to write the
138 driver software yourself. Please read the file
139 <file:Documentation/scsi/scsi-generic.txt> for more information.
141 To compile this driver as a module, choose M here and read
142 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
147 tristate "SCSI media changer support"
150 This is a driver for SCSI media changers. Most common devices are
151 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
152 don't need this for those tiny 6-slot cdrom changers. Media
153 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
154 If you have such hardware and want to use it with linux, say Y
155 here. Check <file:Documentation/scsi-changer.txt> for details.
157 If you want to compile this as a module ( = code which can be
158 inserted in and removed from the running kernel whenever you want),
159 say M here and read <file:Documentation/modules.txt> and
160 <file:Documentation/scsi.txt>. The module will be called ch.o.
164 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
167 config SCSI_MULTI_LUN
168 bool "Probe all LUNs on each SCSI device"
171 If you have a SCSI device that supports more than one LUN (Logical
172 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
173 can say Y here to force the SCSI driver to probe for multiple LUNs.
174 A SCSI device with multiple LUNs acts logically like multiple SCSI
175 devices. The vast majority of SCSI devices have only one LUN, and
176 so most people can say N here. The max_luns boot/module parameter
177 allows to override this setting.
179 config SCSI_CONSTANTS
180 bool "Verbose SCSI error reporting (kernel size +=12K)"
183 The error messages regarding your SCSI hardware will be easier to
184 understand if you say Y here; it will enlarge your kernel by about
185 12 KB. If in doubt, say Y.
188 bool "SCSI logging facility"
191 This turns on a logging facility that can be used to debug a number
192 of SCSI related problems.
194 If you say Y here, no logging output will appear by default, but you
195 can enable logging by saying Y to "/proc file system support" and
196 "Sysctl support" below and executing the command
198 echo "scsi log token [level]" > /proc/scsi/scsi
200 at boot time after the /proc file system has been mounted.
202 There are a number of things that can be used for 'token' (you can
203 find them in the source: <file:drivers/scsi/scsi.c>), and this
204 allows you to select the types of information you want, and the
205 level allows you to select the level of verbosity.
207 If you say N here, it may be harder to track down some types of SCSI
208 problems. If you say Y here your kernel will be somewhat larger, but
209 there should be no noticeable performance impact as long as you have
212 menu "SCSI Transports"
215 config SCSI_SPI_ATTRS
216 tristate "Parallel SCSI (SPI) Transport Attributes"
219 If you wish to export transport-specific information about
220 each attached SCSI device to sysfs, say Y. Otherwise, say N.
223 tristate "FiberChannel Transport Attributes"
226 If you wish to export transport-specific information about
227 each attached FiberChannel device to sysfs, say Y.
230 config SCSI_ISCSI_ATTRS
231 tristate "iSCSI Transport Attributes"
232 depends on SCSI && NET
234 If you wish to export transport-specific information about
235 each attached iSCSI device to sysfs, say Y.
238 config SCSI_SAS_ATTRS
239 tristate "SAS Transport Attributes"
242 If you wish to export transport-specific information about
243 each attached SAS device to sysfs, say Y.
245 source "drivers/scsi/libsas/Kconfig"
249 menu "SCSI low-level drivers"
253 tristate "iSCSI Initiator over TCP/IP"
254 depends on SCSI && INET
258 select SCSI_ISCSI_ATTRS
260 The iSCSI Driver provides a host with the ability to access storage
261 through an IP network. The driver uses the iSCSI protocol to transport
262 SCSI requests and responses over a TCP/IP network between the host
263 (the "initiator") and "targets". Architecturally, the iSCSI driver
264 combines with the host's TCP/IP stack, network drivers, and Network
265 Interface Card (NIC) to provide the same functions as a SCSI or a
266 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
268 To compile this driver as a module, choose M here: the
269 module will be called iscsi_tcp.
271 The userspace component needed to initialize the driver, documentation,
272 and sample configuration files can be found here:
274 http://linux-iscsi.sf.net
277 tristate "SGI WD93C93 SCSI Driver"
278 depends on SGI_IP22 && SCSI
280 If you have a Western Digital WD93 SCSI controller on
281 an SGI MIPS system, say Y. Otherwise, say N.
284 tristate "DEC NCR53C94 Scsi Driver"
285 depends on MACH_DECSTATION && SCSI && TC
287 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
288 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
291 tristate "DEC SII Scsi Driver"
292 depends on MACH_DECSTATION && SCSI && 32BIT
294 config BLK_DEV_3W_XXXX_RAID
295 tristate "3ware 5/6/7/8xxx ATA-RAID support"
296 depends on PCI && SCSI
298 3ware is the only hardware ATA-Raid product in Linux to date.
299 This card is 2,4, or 8 channel master mode support only.
300 SCSI support required!!!
302 <http://www.3ware.com/>
304 Please read the comments at the top of
305 <file:drivers/scsi/3w-xxxx.c>.
308 tristate "3ware 9xxx SATA-RAID support"
309 depends on PCI && SCSI
311 This driver supports the 9000 series 3ware SATA-RAID cards.
313 <http://www.amcc.com>
315 Please read the comments at the top of
316 <file:drivers/scsi/3w-9xxx.c>.
318 config SCSI_7000FASST
319 tristate "7000FASST SCSI support"
320 depends on ISA && SCSI && ISA_DMA_API
322 This driver supports the Western Digital 7000 SCSI host adapter
323 family. Some information is in the source:
324 <file:drivers/scsi/wd7000.c>.
326 To compile this driver as a module, choose M here: the
327 module will be called wd7000.
330 tristate "ACARD SCSI support"
331 depends on PCI && SCSI
333 This driver supports the ACARD SCSI host adapter.
334 Support Chip <ATP870 ATP876 ATP880 ATP885>
335 To compile this driver as a module, choose M here: the
336 module will be called atp870u.
339 tristate "Adaptec AHA152X/2825 support"
340 depends on ISA && SCSI && !64BIT
341 select SCSI_SPI_ATTRS
343 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
344 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
345 must be manually specified in this case.
347 It is explained in section 3.3 of the SCSI-HOWTO, available from
348 <http://www.tldp.org/docs.html#howto>. You might also want to
349 read the file <file:Documentation/scsi/aha152x.txt>.
351 To compile this driver as a module, choose M here: the
352 module will be called aha152x.
355 tristate "Adaptec AHA1542 support"
356 depends on ISA && SCSI && ISA_DMA_API
358 This is support for a SCSI host adapter. It is explained in section
359 3.4 of the SCSI-HOWTO, available from
360 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
361 purchased by Adaptec, and some former Trantor products are being
362 sold under the Adaptec name. If it doesn't work out of the box, you
363 may have to change some settings in <file:drivers/scsi/aha1542.h>.
365 To compile this driver as a module, choose M here: the
366 module will be called aha1542.
369 tristate "Adaptec AHA1740 support"
370 depends on EISA && SCSI
372 This is support for a SCSI host adapter. It is explained in section
373 3.5 of the SCSI-HOWTO, available from
374 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
375 of the box, you may have to change some settings in
376 <file:drivers/scsi/aha1740.h>.
378 To compile this driver as a module, choose M here: the
379 module will be called aha1740.
382 tristate "Adaptec AACRAID support"
383 depends on SCSI && PCI
385 This driver supports a variety of Dell, HP, Adaptec, IBM and
386 ICP storage products. For a list of supported products, refer
387 to <file:Documentation/scsi/aacraid.txt>.
389 To compile this driver as a module, choose M here: the module
390 will be called aacraid.
393 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
395 config SCSI_AIC7XXX_OLD
396 tristate "Adaptec AIC7xxx support (old driver)"
397 depends on (ISA || EISA || PCI ) && SCSI
399 WARNING This driver is an older aic7xxx driver and is no longer
400 under active development. Adaptec, Inc. is writing a new driver to
401 take the place of this one, and it is recommended that whenever
402 possible, people should use the new Adaptec written driver instead
403 of this one. This driver will eventually be phased out entirely.
405 This is support for the various aic7xxx based Adaptec SCSI
406 controllers. These include the 274x EISA cards; 284x VLB cards;
407 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
408 motherboard based SCSI controllers from Adaptec. It does not support
409 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
410 support them. It does not support the 2920 cards from Adaptec that
411 use the Future Domain SCSI controller chip. For those cards, you
412 need the "Future Domain 16xx SCSI support" driver.
414 In general, if the controller is based on an Adaptec SCSI controller
415 chip from the aic777x series or the aic78xx series, this driver
416 should work. The only exception is the 7810 which is specifically
417 not supported (that's the RAID controller chip on the AAA-13x
420 Note that the AHA2920 SCSI host adapter is *not* supported by this
421 driver; choose "Future Domain 16xx SCSI support" instead if you have
424 Information on the configuration options for this controller can be
425 found by checking the help file for each of the available
426 configuration options. You should read
427 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
428 contacting the maintainer with any questions. The SCSI-HOWTO,
429 available from <http://www.tldp.org/docs.html#howto>, can also
432 To compile this driver as a module, choose M here: the
433 module will be called aic7xxx_old.
435 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
436 source "drivers/scsi/aic94xx/Kconfig"
438 # All the I2O code and drivers do not seem to be 64bit safe.
440 tristate "Adaptec I2O RAID support "
441 depends on !64BIT && SCSI && PCI
443 This driver supports all of Adaptec's I2O based RAID controllers as
444 well as the DPT SmartRaid V cards. This is an Adaptec maintained
445 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
447 To compile this driver as a module, choose M here: the
448 module will be called dpt_i2o.
451 tristate "AdvanSys SCSI support"
453 depends on ISA || EISA || PCI
454 depends on BROKEN || X86_32
456 This is a driver for all SCSI host adapters manufactured by
457 AdvanSys. It is documented in the kernel source in
458 <file:drivers/scsi/advansys.c>.
460 To compile this driver as a module, choose M here: the
461 module will be called advansys.
464 tristate "Always IN2000 SCSI support"
465 depends on ISA && SCSI
467 This is support for an ISA bus SCSI host adapter. You'll find more
468 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
469 out of the box, you may have to change the jumpers for IRQ or
472 To compile this driver as a module, choose M here: the
473 module will be called in2000.
476 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
477 depends on PCI && SCSI
479 This driver supports all of ARECA's SATA RAID controller cards.
480 This is an ARECA-maintained driver by Erich Chen.
481 If you have any problems, please mail to: < erich@areca.com.tw >
482 Areca supports Linux RAID config tools.
484 < http://www.areca.com.tw >
486 To compile this driver as a module, choose M here: the
487 module will be called arcmsr (modprobe arcmsr).
489 source "drivers/scsi/megaraid/Kconfig.megaraid"
492 tristate "Serial ATA (SATA) support"
495 This driver family supports Serial ATA host controllers
500 config SCSI_SATA_AHCI
501 tristate "AHCI SATA support"
502 depends on SCSI_SATA && PCI
504 This option enables support for AHCI Serial ATA.
509 tristate "ServerWorks Frodo / Apple K2 SATA support"
510 depends on SCSI_SATA && PCI
512 This option enables support for Broadcom/Serverworks/Apple K2
518 tristate "Intel PIIX/ICH SATA support"
519 depends on SCSI_SATA && PCI
521 This option enables support for ICH5/6/7/8 Serial ATA.
522 If PATA support was enabled previously, this enables
523 support for select Intel PIIX/ICH PATA host controllers.
528 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
529 depends on SCSI_SATA && PCI && EXPERIMENTAL
531 This option enables support for the Marvell Serial ATA family.
532 Currently supports 88SX[56]0[48][01] chips.
537 tristate "NVIDIA SATA support"
538 depends on SCSI_SATA && PCI && EXPERIMENTAL
540 This option enables support for NVIDIA Serial ATA.
545 tristate "Pacific Digital ADMA support"
546 depends on SCSI_SATA && PCI
548 This option enables support for Pacific Digital ADMA controllers
553 tristate "HighPoint RocketRAID 3xxx Controller support"
554 depends on SCSI && PCI
556 This option enables support for HighPoint RocketRAID 3xxx
559 To compile this driver as a module, choose M here; the module
560 will be called hptiop. If unsure, say N.
562 config SCSI_SATA_QSTOR
563 tristate "Pacific Digital SATA QStor support"
564 depends on SCSI_SATA && PCI
566 This option enables support for Pacific Digital Serial ATA QStor.
570 config SCSI_SATA_PROMISE
571 tristate "Promise SATA TX2/TX4 support"
572 depends on SCSI_SATA && PCI
574 This option enables support for Promise Serial ATA TX2/TX4.
579 tristate "Promise SATA SX4 support"
580 depends on SCSI_SATA && PCI && EXPERIMENTAL
582 This option enables support for Promise Serial ATA SX4.
587 tristate "Silicon Image SATA support"
588 depends on SCSI_SATA && PCI && EXPERIMENTAL
590 This option enables support for Silicon Image Serial ATA.
594 config SCSI_SATA_SIL24
595 tristate "Silicon Image 3124/3132 SATA support"
596 depends on SCSI_SATA && PCI && EXPERIMENTAL
598 This option enables support for Silicon Image 3124/3132 Serial ATA.
603 tristate "SiS 964/180 SATA support"
604 depends on SCSI_SATA && PCI && EXPERIMENTAL
606 This option enables support for SiS Serial ATA 964/180.
611 tristate "ULi Electronics SATA support"
612 depends on SCSI_SATA && PCI && EXPERIMENTAL
614 This option enables support for ULi Electronics SATA.
619 tristate "VIA SATA support"
620 depends on SCSI_SATA && PCI
622 This option enables support for VIA Serial ATA.
626 config SCSI_SATA_VITESSE
627 tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
628 depends on SCSI_SATA && PCI
630 This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
634 config SCSI_SATA_INTEL_COMBINED
636 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
640 tristate "BusLogic SCSI support"
641 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
643 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
644 Adapters. Consult the SCSI-HOWTO, available from
645 <http://www.tldp.org/docs.html#howto>, and the files
646 <file:Documentation/scsi/BusLogic.txt> and
647 <file:Documentation/scsi/FlashPoint.txt> for more information.
649 To compile this driver as a module, choose M here: the
650 module will be called BusLogic.
652 config SCSI_OMIT_FLASHPOINT
653 bool "Omit FlashPoint support"
654 depends on SCSI_BUSLOGIC
656 This option allows you to omit the FlashPoint support from the
657 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
658 substantial, so users of MultiMaster Host Adapters may wish to omit
662 tristate "DMX3191D SCSI support"
663 depends on PCI && SCSI
664 select SCSI_SPI_ATTRS
666 This is support for Domex DMX3191D SCSI Host Adapters.
668 To compile this driver as a module, choose M here: the
669 module will be called dmx3191d.
672 tristate "DTC3180/3280 SCSI support"
673 depends on ISA && SCSI
674 select SCSI_SPI_ATTRS
676 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
677 the SCSI-HOWTO, available from
678 <http://www.tldp.org/docs.html#howto>, and the file
679 <file:Documentation/scsi/dtc3x80.txt>.
681 To compile this driver as a module, choose M here: the
682 module will be called dtc.
685 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
686 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
688 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
689 ISA and all EISA I/O addresses are probed looking for the "EATA"
690 signature. The addresses of all the PCI SCSI controllers reported
691 by the PCI subsystem are probed as well.
693 You want to read the start of <file:drivers/scsi/eata.c> and the
694 SCSI-HOWTO, available from
695 <http://www.tldp.org/docs.html#howto>.
697 To compile this driver as a module, choose M here: the
698 module will be called eata.
700 config SCSI_EATA_TAGGED_QUEUE
701 bool "enable tagged command queueing"
704 This is a feature of SCSI-2 which improves performance: the host
705 adapter can send several SCSI commands to a device's queue even if
706 previous commands haven't finished yet.
707 This is equivalent to the "eata=tc:y" boot option.
709 config SCSI_EATA_LINKED_COMMANDS
710 bool "enable elevator sorting"
713 This option enables elevator sorting for all probed SCSI disks and
714 CD-ROMs. It definitely reduces the average seek distance when doing
715 random seeks, but this does not necessarily result in a noticeable
716 performance improvement: your mileage may vary...
717 This is equivalent to the "eata=lc:y" boot option.
719 config SCSI_EATA_MAX_TAGS
720 int "maximum number of queued commands"
724 This specifies how many SCSI commands can be maximally queued for
725 each probed SCSI device. You should reduce the default value of 16
726 only if you have disks with buggy or limited tagged command support.
727 Minimum is 2 and maximum is 62. This value is also the window size
728 used by the elevator sorting option above. The effective value used
729 by the driver for each probed SCSI device is reported at boot time.
730 This is equivalent to the "eata=mq:8" boot option.
733 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
734 depends on (ISA || EISA || PCI) && SCSI && BROKEN
736 This driver supports all EATA-PIO protocol compliant SCSI Host
737 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
738 host adapters could also use this driver but are discouraged from
739 doing so, since this driver only supports hard disks and lacks
740 numerous features. You might want to have a look at the SCSI-HOWTO,
741 available from <http://www.tldp.org/docs.html#howto>.
743 To compile this driver as a module, choose M here: the
744 module will be called eata_pio.
746 config SCSI_FUTURE_DOMAIN
747 tristate "Future Domain 16xx SCSI/AHA-2920A support"
748 depends on (ISA || PCI) && SCSI
750 This is support for Future Domain's 16-bit SCSI host adapters
751 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
752 other adapters based on the Future Domain chipsets (Quantum
753 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
754 It is explained in section 3.7 of the SCSI-HOWTO, available from
755 <http://www.tldp.org/docs.html#howto>.
757 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
758 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
759 controller support"). This Future Domain driver works with the older
760 Adaptec AHA-2920A boards with a Future Domain chip on them.
762 To compile this driver as a module, choose M here: the
763 module will be called fdomain.
766 tristate "Future Domain MCS-600/700 SCSI support"
767 depends on MCA_LEGACY && SCSI
769 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
770 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
771 is identical to the MCS 700 and hence also supported by this driver.
772 This driver also supports the Reply SB16/SCSI card (the SCSI part).
773 It supports multiple adapters in the same system.
775 To compile this driver as a module, choose M here: the
776 module will be called fd_mcs.
779 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
780 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
782 Formerly called GDT SCSI Disk Array Controller Support.
784 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
785 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
786 in the kernel source in <file:drivers/scsi/gdth.c> and
787 <file:drivers/scsi/gdth.h.>
789 To compile this driver as a module, choose M here: the
790 module will be called gdth.
792 config SCSI_GENERIC_NCR5380
793 tristate "Generic NCR5380/53c400 SCSI PIO support"
794 depends on ISA && SCSI
795 select SCSI_SPI_ATTRS
797 This is a driver for the old NCR 53c80 series of SCSI controllers
798 on boards using PIO. Most boards such as the Trantor T130 fit this
799 category, along with a large number of ISA 8bit controllers shipped
800 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
801 you should select the specific driver for that card rather than
802 generic 5380 support.
804 It is explained in section 3.8 of the SCSI-HOWTO, available from
805 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
806 of the box, you may have to change some settings in
807 <file:drivers/scsi/g_NCR5380.h>.
809 To compile this driver as a module, choose M here: the
810 module will be called g_NCR5380.
812 config SCSI_GENERIC_NCR5380_MMIO
813 tristate "Generic NCR5380/53c400 SCSI MMIO support"
814 depends on ISA && SCSI
815 select SCSI_SPI_ATTRS
817 This is a driver for the old NCR 53c80 series of SCSI controllers
818 on boards using memory mapped I/O.
819 It is explained in section 3.8 of the SCSI-HOWTO, available from
820 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
821 of the box, you may have to change some settings in
822 <file:drivers/scsi/g_NCR5380.h>.
824 To compile this driver as a module, choose M here: the
825 module will be called g_NCR5380_mmio.
827 config SCSI_GENERIC_NCR53C400
828 bool "Enable NCR53c400 extensions"
829 depends on SCSI_GENERIC_NCR5380
831 This enables certain optimizations for the NCR53c400 SCSI cards.
832 You might as well try it out. Note that this driver will only probe
833 for the Trantor T130B in its default configuration; you might have
834 to pass a command line option to the kernel at boot time if it does
835 not detect your card. See the file
836 <file:Documentation/scsi/g_NCR5380.txt> for details.
839 tristate "IBMMCA SCSI support"
840 depends on MCA_LEGACY && SCSI
842 This is support for the IBM SCSI adapter found in many of the PS/2
843 series computers. These machines have an MCA bus, so you need to
844 answer Y to "MCA support" as well and read
845 <file:Documentation/mca.txt>.
847 If the adapter isn't found during boot (a common problem for models
848 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
849 option, where <pun> is the id of the SCSI subsystem (usually 7, but
850 if that doesn't work check your reference diskette). Owners of
851 model 95 with a LED-matrix-display can in addition activate some
852 activity info like under OS/2, but more informative, by setting
853 'ibmmcascsi=display' as an additional kernel parameter. Try "man
854 bootparam" or see the documentation of your boot loader about how to
855 pass options to the kernel.
857 To compile this driver as a module, choose M here: the
858 module will be called ibmmca.
860 config IBMMCA_SCSI_ORDER_STANDARD
861 bool "Standard SCSI-order"
862 depends on SCSI_IBMMCA
864 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
865 are assigned to the drive letters, starting with the lowest SCSI-id
866 (physical number -- pun) to be drive C:, as seen from DOS and
867 similar operating systems. When looking into papers describing the
868 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
869 The SCSI-standard follows a hardware-hierarchy which says that id 7
870 has the highest priority and id 0 the lowest. Therefore, the host
871 adapters are still today everywhere placed as SCSI-id 7 by default.
872 In the SCSI-standard, the drive letters express the priority of the
873 disk. C: should be the hard disk, or a partition on it, with the
874 highest priority. This must therefore be the disk with the highest
875 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
876 original definition of the SCSI-standard as also industrial- and
877 process-control-machines, like VME-CPUs running under realtime-OSes
878 (e.g. LynxOS, OS9) do.
880 If you like to run Linux on your MCA-machine with the same
881 assignment of hard disks as seen from e.g. DOS or OS/2 on your
882 machine, which is in addition conformant to the SCSI-standard, you
883 must say Y here. This is also necessary for MCA-Linux users who want
884 to keep downward compatibility to older releases of the
885 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
888 If you like to have the lowest SCSI-id assigned as drive C:, as
889 modern SCSI-BIOSes do, which does not conform to the standard, but
890 is widespread and common in the PC-world of today, you must say N
891 here. If unsure, say Y.
893 config IBMMCA_SCSI_DEV_RESET
894 bool "Reset SCSI-devices at boottime"
895 depends on SCSI_IBMMCA
897 By default, SCSI-devices are reset when the machine is powered on.
898 However, some devices exist, like special-control-devices,
899 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
900 not reset when switched on. If you say Y here, each device connected
901 to your SCSI-bus will be issued a reset-command after it has been
902 probed, while the kernel is booting. This may cause problems with
903 more modern devices, like hard disks, which do not appreciate these
904 reset commands, and can cause your system to hang. So say Y only if
905 you know that one of your older devices needs it; N is the safe
909 tristate "IBM ServeRAID support"
910 depends on PCI && SCSI
912 This is support for the IBM ServeRAID hardware RAID controllers.
913 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
914 for more information. If this driver does not work correctly
915 without modification please contact the author by email at
916 <ipslinux@adaptec.com>.
918 To compile this driver as a module, choose M here: the
919 module will be called ips.
922 tristate "IBM Virtual SCSI support"
923 depends on PPC_PSERIES || PPC_ISERIES
925 This is the IBM POWER Virtual SCSI Client
927 To compile this driver as a module, choose M here: the
928 module will be called ibmvscsic.
931 tristate "Initio 9100U(W) support"
932 depends on PCI && SCSI
934 This is support for the Initio 91XXU(W) SCSI host adapter. Please
935 read the SCSI-HOWTO, available from
936 <http://www.tldp.org/docs.html#howto>.
938 To compile this driver as a module, choose M here: the
939 module will be called initio.
942 tristate "Initio INI-A100U2W support"
943 depends on PCI && SCSI
945 This is support for the Initio INI-A100U2W SCSI host adapter.
946 Please read the SCSI-HOWTO, available from
947 <http://www.tldp.org/docs.html#howto>.
949 To compile this driver as a module, choose M here: the
950 module will be called a100u2w.
953 tristate "IOMEGA parallel port (ppa - older drives)"
954 depends on SCSI && PARPORT_PC
956 This driver supports older versions of IOMEGA's parallel port ZIP
957 drive (a 100 MB removable media device).
959 Note that you can say N here if you have the SCSI version of the ZIP
960 drive: it will be supported automatically if you said Y to the
961 generic "SCSI disk support", above.
963 If you have the ZIP Plus drive or a more recent parallel port ZIP
964 drive (if the supplied cable with the drive is labeled "AutoDetect")
965 then you should say N here and Y to "IOMEGA parallel port (imm -
966 newer drives)", below.
968 For more information about this driver and how to use it you should
969 read the file <file:Documentation/scsi/ppa.txt>. You should also read
970 the SCSI-HOWTO, which is available from
971 <http://www.tldp.org/docs.html#howto>. If you use this driver,
972 you will still be able to use the parallel port for other tasks,
973 such as a printer; it is safe to compile both drivers into the
976 To compile this driver as a module, choose M here: the
977 module will be called ppa.
980 tristate "IOMEGA parallel port (imm - newer drives)"
981 depends on SCSI && PARPORT_PC
983 This driver supports newer versions of IOMEGA's parallel port ZIP
984 drive (a 100 MB removable media device).
986 Note that you can say N here if you have the SCSI version of the ZIP
987 drive: it will be supported automatically if you said Y to the
988 generic "SCSI disk support", above.
990 If you have the ZIP Plus drive or a more recent parallel port ZIP
991 drive (if the supplied cable with the drive is labeled "AutoDetect")
992 then you should say Y here; if you have an older ZIP drive, say N
993 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
995 For more information about this driver and how to use it you should
996 read the file <file:Documentation/scsi/ppa.txt>. You should also read
997 the SCSI-HOWTO, which is available from
998 <http://www.tldp.org/docs.html#howto>. If you use this driver,
999 you will still be able to use the parallel port for other tasks,
1000 such as a printer; it is safe to compile both drivers into the
1003 To compile this driver as a module, choose M here: the
1004 module will be called imm.
1006 config SCSI_IZIP_EPP16
1007 bool "ppa/imm option - Use slow (but safe) EPP-16"
1008 depends on SCSI_PPA || SCSI_IMM
1010 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1011 allows them to act as expansion buses that can handle up to 64
1014 Some parallel port chipsets are slower than their motherboard, and
1015 so we have to control the state of the chipset's FIFO queue every
1016 now and then to avoid data loss. This will be done if you say Y
1019 Generally, saying Y is the safe option and slows things down a bit.
1021 config SCSI_IZIP_SLOW_CTR
1022 bool "ppa/imm option - Assume slow parport control register"
1023 depends on SCSI_PPA || SCSI_IMM
1025 Some parallel ports are known to have excessive delays between
1026 changing the parallel port control register and good data being
1027 available on the parallel port data/status register. This option
1028 forces a small delay (1.0 usec to be exact) after changing the
1029 control register to let things settle out. Enabling this option may
1030 result in a big drop in performance but some very old parallel ports
1031 (found in 386 vintage machines) will not work properly.
1033 Generally, saying N is fine.
1035 config SCSI_NCR53C406A
1036 tristate "NCR53c406a SCSI support"
1037 depends on ISA && SCSI
1039 This is support for the NCR53c406a SCSI host adapter. For user
1040 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1041 in the kernel source. Also read the SCSI-HOWTO, available from
1042 <http://www.tldp.org/docs.html#howto>.
1044 To compile this driver as a module, choose M here: the
1045 module will be called NCR53c406.
1047 config SCSI_NCR_D700
1048 tristate "NCR Dual 700 MCA SCSI support"
1049 depends on MCA && SCSI
1050 select SCSI_SPI_ATTRS
1052 This is a driver for the MicroChannel Dual 700 card produced by
1053 NCR and commonly used in 345x/35xx/4100 class machines. It always
1054 tries to negotiate sync and uses tag command queueing.
1056 Unless you have an NCR manufactured machine, the chances are that
1057 you do not have this SCSI card, so say N.
1060 tristate "HP Lasi SCSI support for 53c700/710"
1061 depends on GSC && SCSI
1062 select SCSI_SPI_ATTRS
1064 This is a driver for the SCSI controller in the Lasi chip found in
1065 many PA-RISC workstations & servers. If you do not know whether you
1066 have a Lasi chip, it is safe to say "Y" here.
1068 config 53C700_LE_ON_BE
1070 depends on SCSI_LASI700
1073 config SCSI_SYM53C8XX_2
1074 tristate "SYM53C8XX Version 2 SCSI support"
1075 depends on PCI && SCSI
1076 select SCSI_SPI_ATTRS
1078 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1079 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1080 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1081 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1082 controllers; you need to use the Fusion MPT driver for that.
1084 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1087 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1088 int "DMA addressing mode"
1089 depends on SCSI_SYM53C8XX_2
1092 This option only applies to PCI-SCSI chips that are PCI DAC
1093 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1095 When set to 0, the driver will program the chip to only perform
1096 32-bit DMA. When set to 1, the chip will be able to perform DMA
1097 to addresses up to 1TB. When set to 2, the driver supports the
1098 full 64-bit DMA address range, but can only address 16 segments
1099 of 4 GB each. This limits the total addressable range to 64 GB.
1101 Most machines with less than 4GB of memory should use a setting
1102 of 0 for best performance. If your machine has 4GB of memory
1103 or more, you should set this option to 1 (the default).
1105 The still experimental value 2 (64 bit DMA addressing with 16
1106 x 4GB segments limitation) can be used on systems that require
1107 PCI address bits past bit 39 to be set for the addressing of
1108 memory using PCI DAC cycles.
1110 config SCSI_SYM53C8XX_DEFAULT_TAGS
1111 int "Default tagged command queue depth"
1112 depends on SCSI_SYM53C8XX_2
1115 This is the default value of the command queue depth the
1116 driver will announce to the generic SCSI layer for devices
1117 that support tagged command queueing. This value can be changed
1118 from the boot command line. This is a soft limit that cannot
1119 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1121 config SCSI_SYM53C8XX_MAX_TAGS
1122 int "Maximum number of queued commands"
1123 depends on SCSI_SYM53C8XX_2
1126 This option allows you to specify the maximum number of commands
1127 that can be queued to any device, when tagged command queuing is
1128 possible. The driver supports up to 256 queued commands per device.
1129 This value is used as a compiled-in hard limit.
1131 config SCSI_SYM53C8XX_MMIO
1132 bool "Use memory mapped IO"
1133 depends on SCSI_SYM53C8XX_2
1136 Memory mapped IO is faster than Port IO. Most people should
1137 answer Y here, but some machines may have problems. If you have
1138 to answer N here, please report the problem to the maintainer.
1141 tristate "IBM Power Linux RAID adapter support"
1142 depends on PCI && SCSI
1145 This driver supports the IBM Power Linux family RAID adapters.
1146 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1147 as IBM iSeries 5702, 5703, 5709, and 570A.
1149 config SCSI_IPR_TRACE
1150 bool "enable driver internal trace"
1153 If you say Y here, the driver will trace all commands issued
1154 to the adapter. Performance impact is minimal. Trace can be
1155 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1157 config SCSI_IPR_DUMP
1158 bool "enable adapter dump support"
1161 If you say Y here, the driver will support adapter crash dump.
1162 If you enable this support, the iprdump daemon can be used
1163 to capture adapter failure analysis information.
1166 tristate "Zalon SCSI support"
1167 depends on GSC && SCSI
1168 select SCSI_SPI_ATTRS
1170 The Zalon is a GSC/HSC bus interface chip that sits between the
1171 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1172 C110, J200, J210 and some D, K & R-class machines. It's also
1173 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1174 Say Y here if you have one of these machines or cards.
1176 config SCSI_NCR_Q720
1177 tristate "NCR Quad 720 MCA SCSI support"
1178 depends on MCA && SCSI
1179 select SCSI_SPI_ATTRS
1181 This is a driver for the MicroChannel Quad 720 card produced by
1182 NCR and commonly used in 345x/35xx/4100 class machines. It always
1183 tries to negotiate sync and uses tag command queueing.
1185 Unless you have an NCR manufactured machine, the chances are that
1186 you do not have this SCSI card, so say N.
1188 config SCSI_NCR53C8XX_DEFAULT_TAGS
1189 int "default tagged command queue depth"
1190 depends on SCSI_ZALON || SCSI_NCR_Q720
1193 "Tagged command queuing" is a feature of SCSI-2 which improves
1194 performance: the host adapter can send several SCSI commands to a
1195 device's queue even if previous commands haven't finished yet.
1196 Because the device is intelligent, it can optimize its operations
1197 (like head positioning) based on its own request queue. Some SCSI
1198 devices don't implement this properly; if you want to disable this
1199 feature, enter 0 or 1 here (it doesn't matter which).
1201 The default value is 8 and should be supported by most hard disks.
1202 This value can be overridden from the boot command line using the
1203 'tags' option as follows (example):
1204 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1205 4, set queue depth to 16 for target 2 and target 3 on controller 0
1206 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1208 The normal answer therefore is to go with the default 8 and to use
1209 a boot command line option for devices that need to use a different
1210 command queue depth.
1212 There is no safe option other than using good SCSI devices.
1214 config SCSI_NCR53C8XX_MAX_TAGS
1215 int "maximum number of queued commands"
1216 depends on SCSI_ZALON || SCSI_NCR_Q720
1219 This option allows you to specify the maximum number of commands
1220 that can be queued to any device, when tagged command queuing is
1221 possible. The default value is 32. Minimum is 2, maximum is 64.
1222 Modern hard disks are able to support 64 tags and even more, but
1223 do not seem to be faster when more than 32 tags are being used.
1225 So, the normal answer here is to go with the default value 32 unless
1226 you are using very large hard disks with large cache (>= 1 MB) that
1227 are able to take advantage of more than 32 tagged commands.
1229 There is no safe option and the default answer is recommended.
1231 config SCSI_NCR53C8XX_SYNC
1232 int "synchronous transfers frequency in MHz"
1233 depends on SCSI_ZALON || SCSI_NCR_Q720
1236 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1237 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1238 are respectively the maximum data transfer rates in mega-transfers
1239 per second for each class. For example, a FAST-20 Wide 16 device is
1240 able to transfer data at 20 million 16 bit packets per second for a
1241 total rate of 40 MB/s.
1243 You may specify 0 if you want to only use asynchronous data
1244 transfers. This is the safest and slowest option. Otherwise, specify
1245 a value between 5 and 80, depending on the capability of your SCSI
1246 controller. The higher the number, the faster the data transfer.
1247 Note that 80 should normally be ok since the driver decreases the
1248 value automatically according to the controller's capabilities.
1250 Your answer to this question is ignored for controllers with NVRAM,
1251 since the driver will get this information from the user set-up. It
1252 also can be overridden using a boot setup option, as follows
1253 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1254 for FAST-20 synchronous data transfer (20 mega-transfers per
1257 The normal answer therefore is not to go with the default but to
1258 select the maximum value 80 allowing the driver to use the maximum
1259 value supported by each controller. If this causes problems with
1260 your SCSI devices, you should come back and decrease the value.
1262 There is no safe option other than using good cabling, right
1263 terminations and SCSI conformant devices.
1265 config SCSI_NCR53C8XX_PROFILE
1266 bool "enable profiling"
1267 depends on SCSI_ZALON || SCSI_NCR_Q720
1269 This option allows you to enable profiling information gathering.
1270 These statistics are not very accurate due to the low frequency
1271 of the kernel clock (100 Hz on i386) and have performance impact
1272 on systems that use very fast devices.
1274 The normal answer therefore is N.
1276 config SCSI_NCR53C8XX_NO_DISCONNECT
1277 bool "not allow targets to disconnect"
1278 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1280 This option is only provided for safety if you suspect some SCSI
1281 device of yours to not support properly the target-disconnect
1282 feature. In that case, you would say Y here. In general however, to
1283 not allow targets to disconnect is not reasonable if there is more
1284 than 1 device on a SCSI bus. The normal answer therefore is N.
1286 config SCSI_MCA_53C9X
1287 tristate "NCR MCA 53C9x SCSI support"
1288 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1290 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1291 controller based on the NCR 53C94. This driver will allow use of
1292 the controller on the 3550, and very possibly others.
1294 To compile this driver as a module, choose M here: the
1295 module will be called mca_53c9x.
1298 tristate "PAS16 SCSI support"
1299 depends on ISA && SCSI
1300 select SCSI_SPI_ATTRS
1302 This is support for a SCSI host adapter. It is explained in section
1303 3.10 of the SCSI-HOWTO, available from
1304 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1305 of the box, you may have to change some settings in
1306 <file:drivers/scsi/pas16.h>.
1308 To compile this driver as a module, choose M here: the
1309 module will be called pas16.
1312 tristate "PSI240i support"
1313 depends on ISA && SCSI
1315 This is support for the PSI240i EIDE interface card which acts as a
1316 SCSI host adapter. Please read the SCSI-HOWTO, available from
1317 <http://www.tldp.org/docs.html#howto>.
1319 To compile this driver as a module, choose M here: the
1320 module will be called psi240i.
1322 config SCSI_QLOGIC_FAS
1323 tristate "Qlogic FAS SCSI support"
1324 depends on ISA && SCSI
1326 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1327 FastSCSI! cards as well as any other card based on the FASXX chip
1328 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1330 This driver does NOT support the PCI versions of these cards. The
1331 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1332 SCSI support"), below.
1334 Information about this driver is contained in
1335 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1336 SCSI-HOWTO, available from
1337 <http://www.tldp.org/docs.html#howto>.
1339 To compile this driver as a module, choose M here: the
1340 module will be called qlogicfas.
1342 config SCSI_QLOGIC_FC_FIRMWARE
1343 bool "Include loadable firmware in driver"
1344 depends on SCSI_QLOGIC_FC
1346 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1347 expanded LUN addressing and FcTape (FCP-2) support, in the
1348 qlogicfc driver. This is required on some platforms.
1350 config SCSI_QLOGIC_1280
1351 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1352 depends on PCI && SCSI
1354 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1356 To compile this driver as a module, choose M here: the
1357 module will be called qla1280.
1359 config SCSI_QLOGICPTI
1360 tristate "PTI Qlogic, ISP Driver"
1361 depends on SBUS && SCSI
1363 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1364 controllers are known under Solaris as qpti and in the openprom as
1365 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1366 driven by a different driver.
1368 To compile this driver as a module, choose M here: the
1369 module will be called qlogicpti.
1371 source "drivers/scsi/qla2xxx/Kconfig"
1374 tristate "Emulex LightPulse Fibre Channel Support"
1375 depends on PCI && SCSI
1376 select SCSI_FC_ATTRS
1378 This lpfc driver supports the Emulex LightPulse
1379 Family of Fibre Channel PCI host adapters.
1382 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1383 depends on X86 && ISA && SCSI && BROKEN
1385 These are 8-bit SCSI controllers; the ST-01 is also supported by
1386 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1387 available from <http://www.tldp.org/docs.html#howto>. If it
1388 doesn't work out of the box, you may have to change some settings in
1389 <file:drivers/scsi/seagate.h>.
1391 To compile this driver as a module, choose M here: the
1392 module will be called seagate.
1394 # definitely looks not 64bit safe:
1396 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1397 depends on (EISA || MCA) && SCSI
1398 select SCSI_SPI_ATTRS
1400 This driver for NCR53c710 based SCSI host adapters.
1402 It currently supports Compaq EISA cards and NCR MCA cards
1404 config 53C700_IO_MAPPED
1406 depends on SCSI_SIM710
1409 config SCSI_SYM53C416
1410 tristate "Symbios 53c416 SCSI support"
1411 depends on ISA && SCSI
1413 This is support for the sym53c416 SCSI host adapter, the SCSI
1414 adapter that comes with some HP scanners. This driver requires that
1415 the sym53c416 is configured first using some sort of PnP
1416 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1417 are using isapnp then you need to compile this driver as a module
1418 and then load it using insmod after isapnp has run. The parameters
1419 of the configured card(s) should be passed to the driver. The format
1422 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1424 To compile this driver as a module, choose M here: the
1425 module will be called sym53c416.
1428 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1429 depends on PCI && SCSI && EXPERIMENTAL
1431 This driver supports PCI SCSI host adapters based on the ASIC
1432 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1434 This driver works, but is still in experimental status. So better
1435 have a bootable disk and a backup in case of emergency.
1437 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1439 To compile this driver as a module, choose M here: the
1440 module will be called dc395x.
1443 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1444 depends on PCI && SCSI
1446 This driver supports PCI SCSI host adapters based on the Am53C974A
1447 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1448 PCscsi/PCnet (Am53/79C974) solutions.
1450 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1452 Note that this driver does NOT support Tekram DC390W/U/F, which are
1453 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1455 To compile this driver as a module, choose M here: the
1456 module will be called tmscsim.
1459 tristate "Trantor T128/T128F/T228 SCSI support"
1460 depends on ISA && SCSI
1461 select SCSI_SPI_ATTRS
1463 This is support for a SCSI host adapter. It is explained in section
1464 3.11 of the SCSI-HOWTO, available from
1465 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1466 of the box, you may have to change some settings in
1467 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1468 Adaptec, and some former Trantor products are being sold under the
1471 To compile this driver as a module, choose M here: the
1472 module will be called t128.
1475 tristate "UltraStor 14F/34F support"
1476 depends on ISA && SCSI && ISA_DMA_API
1478 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1479 The source at <file:drivers/scsi/u14-34f.c> contains some
1480 information about this hardware. If the driver doesn't work out of
1481 the box, you may have to change some settings in
1482 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1483 <http://www.tldp.org/docs.html#howto>. Note that there is also
1484 another driver for the same hardware: "UltraStor SCSI support",
1485 below. You should say Y to both only if you want 24F support as
1488 To compile this driver as a module, choose M here: the
1489 module will be called u14-34f.
1491 config SCSI_U14_34F_TAGGED_QUEUE
1492 bool "enable tagged command queueing"
1493 depends on SCSI_U14_34F
1495 This is a feature of SCSI-2 which improves performance: the host
1496 adapter can send several SCSI commands to a device's queue even if
1497 previous commands haven't finished yet.
1498 This is equivalent to the "u14-34f=tc:y" boot option.
1500 config SCSI_U14_34F_LINKED_COMMANDS
1501 bool "enable elevator sorting"
1502 depends on SCSI_U14_34F
1504 This option enables elevator sorting for all probed SCSI disks and
1505 CD-ROMs. It definitely reduces the average seek distance when doing
1506 random seeks, but this does not necessarily result in a noticeable
1507 performance improvement: your mileage may vary...
1508 This is equivalent to the "u14-34f=lc:y" boot option.
1510 config SCSI_U14_34F_MAX_TAGS
1511 int "maximum number of queued commands"
1512 depends on SCSI_U14_34F
1515 This specifies how many SCSI commands can be maximally queued for
1516 each probed SCSI device. You should reduce the default value of 8
1517 only if you have disks with buggy or limited tagged command support.
1518 Minimum is 2 and maximum is 14. This value is also the window size
1519 used by the elevator sorting option above. The effective value used
1520 by the driver for each probed SCSI device is reported at boot time.
1521 This is equivalent to the "u14-34f=mq:8" boot option.
1523 config SCSI_ULTRASTOR
1524 tristate "UltraStor SCSI support"
1525 depends on X86 && ISA && SCSI
1527 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1528 adapter family. This driver is explained in section 3.12 of the
1529 SCSI-HOWTO, available from
1530 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1531 of the box, you may have to change some settings in
1532 <file:drivers/scsi/ultrastor.h>.
1534 Note that there is also another driver for the same hardware:
1535 "UltraStor 14F/34F support", above.
1537 To compile this driver as a module, choose M here: the
1538 module will be called ultrastor.
1541 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1542 depends on PCI && SCSI && !64BIT
1544 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1545 SCSI host adapter. Please read the SCSI-HOWTO, available from
1546 <http://www.tldp.org/docs.html#howto>.
1548 To compile this driver as a module, choose M here: the
1549 module will be called nsp32.
1552 tristate "SCSI debugging host simulator"
1555 This is a host adapter simulator that can simulate multiple hosts
1556 each with multiple dummy SCSI devices (disks). It defaults to one
1557 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1558 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1559 dummy disks are simulated, they share the same kernel RAM for
1560 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1561 information. This driver is primarily of use to those testing the
1562 SCSI and block subsystems. If unsure, say N.
1565 tristate "MESH (Power Mac internal SCSI) support"
1566 depends on PPC32 && PPC_PMAC && SCSI
1568 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1569 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1570 other Power Macintoshes do). Say Y to include support for this SCSI
1573 To compile this driver as a module, choose M here: the
1574 module will be called mesh.
1576 config SCSI_MESH_SYNC_RATE
1577 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1578 depends on SCSI_MESH
1581 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1582 drives a bus which is entirely internal to the machine (such as the
1583 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1584 operation at up to 10 MB/s. On machines where the SCSI bus
1585 controlled by the MESH can have external devices connected, it is
1586 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1587 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1588 to disable synchronous operation.
1590 config SCSI_MESH_RESET_DELAY_MS
1591 int "initial bus reset delay (ms) (0 = no reset)"
1592 depends on SCSI_MESH
1595 config SCSI_MAC53C94
1596 tristate "53C94 (Power Mac external SCSI) support"
1597 depends on PPC32 && PPC_PMAC && SCSI
1599 On Power Macintoshes (and clones) with two SCSI buses, the external
1600 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1601 machines which only have one SCSI bus, such as the 7200, also use
1602 the 53C94. Say Y to include support for the 53C94.
1604 To compile this driver as a module, choose M here: the
1605 module will be called mac53c94.
1607 source "drivers/scsi/arm/Kconfig"
1610 bool "MIPS JAZZ FAS216 SCSI support"
1611 depends on MACH_JAZZ && SCSI
1613 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1614 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1618 tristate "A3000 WD33C93A support"
1619 depends on AMIGA && SCSI
1621 If you have an Amiga 3000 and have SCSI devices connected to the
1622 built-in SCSI controller, say Y. Otherwise, say N.
1624 To compile this driver as a module, choose M here: the
1625 module will be called wd33c93.
1628 tristate "A2091/A590 WD33C93A support"
1629 depends on ZORRO && SCSI
1631 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1634 To compile this driver as a module, choose M here: the
1635 module will be called wd33c93.
1638 tristate "GVP Series II WD33C93A support"
1639 depends on ZORRO && SCSI
1641 If you have a Great Valley Products Series II SCSI controller,
1642 answer Y. Also say Y if you have a later model of GVP SCSI
1643 controller (such as the GVP A4008 or a Combo board). Otherwise,
1644 answer N. This driver does NOT work for the T-Rex series of
1645 accelerators from TekMagic and GVP-M.
1647 To compile this driver as a module, choose M here: the
1648 module will be called gvp11.
1650 config CYBERSTORM_SCSI
1651 tristate "CyberStorm SCSI support"
1652 depends on ZORRO && SCSI
1654 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1655 accelerator board and the optional Cyberstorm SCSI controller,
1656 answer Y. Otherwise, say N.
1658 config CYBERSTORMII_SCSI
1659 tristate "CyberStorm Mk II SCSI support"
1660 depends on ZORRO && SCSI
1662 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1663 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1667 tristate "Blizzard 2060 SCSI support"
1668 depends on ZORRO && SCSI
1670 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1671 and want to use the onboard SCSI controller, say Y. Otherwise,
1675 tristate "Blizzard 1230IV/1260 SCSI support"
1676 depends on ZORRO && SCSI
1678 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1679 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1682 config FASTLANE_SCSI
1683 tristate "Fastlane SCSI support"
1684 depends on ZORRO && SCSI
1686 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1687 one in the near future, say Y to this question. Otherwise, say N.
1689 config SCSI_AMIGA7XX
1690 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1691 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1693 Support for various NCR53c710-based SCSI controllers on the Amiga.
1695 - the builtin SCSI controller on the Amiga 4000T,
1696 - the Amiga 4091 Zorro III SCSI-2 controller,
1697 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1699 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1700 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1701 accelerator card for the Amiga 1200,
1702 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1703 Note that all of the above SCSI controllers, except for the builtin
1704 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1705 bus, so you also have to enable Zorro bus support if you want to use
1709 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1710 depends on ZORRO && SCSI && EXPERIMENTAL
1712 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1713 Y to this question. If you're in doubt about whether you have one,
1715 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1718 tristate "Atari native SCSI support"
1719 depends on ATARI && SCSI && BROKEN
1720 select SCSI_SPI_ATTRS
1722 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1723 Falcon, ...) say Y to get it supported. Of course also, if you have
1724 a compatible SCSI controller (e.g. for Medusa).
1726 To compile this driver as a module, choose M here: the
1727 module will be called atari_scsi.
1729 This driver supports both styles of NCR integration into the
1730 system: the TT style (separate DMA), and the Falcon style (via
1731 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1732 in the Hades (without DMA).
1734 config ATARI_SCSI_TOSHIBA_DELAY
1735 bool "Long delays for Toshiba CD-ROMs"
1736 depends on ATARI_SCSI
1738 This option increases the delay after a SCSI arbitration to
1739 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1740 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1741 would impact performance a bit, so say N.
1743 config ATARI_SCSI_RESET_BOOT
1744 bool "Reset SCSI-devices at boottime"
1745 depends on ATARI_SCSI
1747 Reset the devices on your Atari whenever it boots. This makes the
1748 boot process fractionally longer but may assist recovery from errors
1749 that leave the devices with SCSI operations partway completed.
1752 bool "Hades SCSI DMA emulator"
1753 depends on ATARI_SCSI && HADES
1755 This option enables code which emulates the TT SCSI DMA chip on the
1756 Hades. This increases the SCSI transfer rates at least ten times
1757 compared to PIO transfers.
1760 bool "Macintosh NCR5380 SCSI"
1761 depends on MAC && SCSI=y
1762 select SCSI_SPI_ATTRS
1764 This is the NCR 5380 SCSI controller included on most of the 68030
1765 based Macintoshes. If you have one of these say Y and read the
1766 SCSI-HOWTO, available from
1767 <http://www.tldp.org/docs.html#howto>.
1770 tristate "Macintosh NCR53c9[46] SCSI"
1771 depends on MAC && SCSI
1773 This is the NCR 53c9x SCSI controller found on most of the 68040
1774 based Macintoshes. If you have one of these say Y and read the
1775 SCSI-HOWTO, available from
1776 <http://www.tldp.org/docs.html#howto>.
1778 To compile this driver as a module, choose M here: the
1779 module will be called mac_esp.
1782 bool "WD33C93 SCSI driver for MVME147"
1783 depends on MVME147 && SCSI=y
1784 select SCSI_SPI_ATTRS
1786 Support for the on-board SCSI controller on the Motorola MVME147
1787 single-board computer.
1790 bool "NCR53C710 SCSI driver for MVME16x"
1791 depends on MVME16x && SCSI && BROKEN
1792 select SCSI_SPI_ATTRS
1794 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1795 SCSI controller chip. Almost everyone using one of these boards
1796 will want to say Y to this question.
1798 config BVME6000_SCSI
1799 bool "NCR53C710 SCSI driver for BVME6000"
1800 depends on BVME6000 && SCSI && BROKEN
1801 select SCSI_SPI_ATTRS
1803 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1804 SCSI controller chip. Almost everyone using one of these boards
1805 will want to say Y to this question.
1807 config SCSI_NCR53C7xx_FAST
1808 bool "allow FAST-SCSI [10MHz]"
1809 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1811 This will enable 10MHz FAST-SCSI transfers with your host
1812 adapter. Some systems have problems with that speed, so it's safest
1816 tristate "Sun3 NCR5380 SCSI"
1817 depends on SUN3 && SCSI && BROKEN
1818 select SCSI_SPI_ATTRS
1820 This option will enable support for the OBIO (onboard io) NCR5380
1821 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1822 "Sun3" type VME scsi controllers also based on the NCR5380.
1823 General Linux information on the Sun 3 series (now discontinued)
1824 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1827 bool "Sun3x ESP SCSI"
1828 depends on SUN3X && SCSI=y
1830 The ESP was an on-board SCSI controller used on Sun 3/80
1831 machines. Say Y here to compile in support for it.
1834 tristate "Sparc ESP Scsi Driver"
1835 depends on SBUS && SCSI
1837 This is the driver for the Sun ESP SCSI host adapter. The ESP
1838 chipset is present in most SPARC SBUS-based computers.
1840 To compile this driver as a module, choose M here: the
1841 module will be called esp.
1843 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1846 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1847 depends on S390 && QDIO && SCSI
1848 select SCSI_FC_ATTRS
1850 If you want to access SCSI devices attached to your IBM eServer
1851 zSeries by means of Fibre Channel interfaces say Y.
1852 For details please refer to the documentation provided by IBM at
1853 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1855 This driver is also available as a module. This module will be
1856 called zfcp. If you want to compile it as a module, say M here
1857 and read <file:Documentation/modules.txt>.
1861 source "drivers/scsi/pcmcia/Kconfig"