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 Transport Attributes"
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.
247 menu "SCSI low-level drivers"
251 tristate "iSCSI Initiator over TCP/IP"
252 depends on SCSI && INET
256 select SCSI_ISCSI_ATTRS
258 The iSCSI Driver provides a host with the ability to access storage
259 through an IP network. The driver uses the iSCSI protocol to transport
260 SCSI requests and responses over a TCP/IP network between the host
261 (the "initiator") and "targets". Architecturally, the iSCSI driver
262 combines with the host's TCP/IP stack, network drivers, and Network
263 Interface Card (NIC) to provide the same functions as a SCSI or a
264 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
266 To compile this driver as a module, choose M here: the
267 module will be called iscsi_tcp.
269 The userspace component needed to initialize the driver, documentation,
270 and sample configuration files can be found here:
272 http://linux-iscsi.sf.net
275 tristate "SGI WD93C93 SCSI Driver"
276 depends on SGI_IP22 && SCSI
278 If you have a Western Digital WD93 SCSI controller on
279 an SGI MIPS system, say Y. Otherwise, say N.
282 tristate "DEC NCR53C94 Scsi Driver"
283 depends on MACH_DECSTATION && SCSI && TC
285 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
286 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
289 tristate "DEC SII Scsi Driver"
290 depends on MACH_DECSTATION && SCSI && 32BIT
292 config BLK_DEV_3W_XXXX_RAID
293 tristate "3ware 5/6/7/8xxx ATA-RAID support"
294 depends on PCI && SCSI
296 3ware is the only hardware ATA-Raid product in Linux to date.
297 This card is 2,4, or 8 channel master mode support only.
298 SCSI support required!!!
300 <http://www.3ware.com/>
302 Please read the comments at the top of
303 <file:drivers/scsi/3w-xxxx.c>.
306 tristate "3ware 9xxx SATA-RAID support"
307 depends on PCI && SCSI
309 This driver supports the 9000 series 3ware SATA-RAID cards.
311 <http://www.amcc.com>
313 Please read the comments at the top of
314 <file:drivers/scsi/3w-9xxx.c>.
316 config SCSI_7000FASST
317 tristate "7000FASST SCSI support"
318 depends on ISA && SCSI && ISA_DMA_API
320 This driver supports the Western Digital 7000 SCSI host adapter
321 family. Some information is in the source:
322 <file:drivers/scsi/wd7000.c>.
324 To compile this driver as a module, choose M here: the
325 module will be called wd7000.
328 tristate "ACARD SCSI support"
329 depends on PCI && SCSI
331 This driver supports the ACARD SCSI host adapter.
332 Support Chip <ATP870 ATP876 ATP880 ATP885>
333 To compile this driver as a module, choose M here: the
334 module will be called atp870u.
337 tristate "Adaptec AHA152X/2825 support"
338 depends on ISA && SCSI && !64BIT
340 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
341 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
342 must be manually specified in this case.
344 It is explained in section 3.3 of the SCSI-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>. You might also want to
346 read the file <file:Documentation/scsi/aha152x.txt>.
348 To compile this driver as a module, choose M here: the
349 module will be called aha152x.
352 tristate "Adaptec AHA1542 support"
353 depends on ISA && SCSI && ISA_DMA_API
355 This is support for a SCSI host adapter. It is explained in section
356 3.4 of the SCSI-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
358 purchased by Adaptec, and some former Trantor products are being
359 sold under the Adaptec name. If it doesn't work out of the box, you
360 may have to change some settings in <file:drivers/scsi/aha1542.h>.
362 To compile this driver as a module, choose M here: the
363 module will be called aha1542.
366 tristate "Adaptec AHA1740 support"
367 depends on EISA && SCSI
369 This is support for a SCSI host adapter. It is explained in section
370 3.5 of the SCSI-HOWTO, available from
371 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
372 of the box, you may have to change some settings in
373 <file:drivers/scsi/aha1740.h>.
375 To compile this driver as a module, choose M here: the
376 module will be called aha1740.
379 tristate "Adaptec AACRAID support"
380 depends on SCSI && PCI
382 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
384 config SCSI_AIC7XXX_OLD
385 tristate "Adaptec AIC7xxx support (old driver)"
386 depends on (ISA || EISA || PCI ) && SCSI
388 WARNING This driver is an older aic7xxx driver and is no longer
389 under active development. Adaptec, Inc. is writing a new driver to
390 take the place of this one, and it is recommended that whenever
391 possible, people should use the new Adaptec written driver instead
392 of this one. This driver will eventually be phased out entirely.
394 This is support for the various aic7xxx based Adaptec SCSI
395 controllers. These include the 274x EISA cards; 284x VLB cards;
396 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
397 motherboard based SCSI controllers from Adaptec. It does not support
398 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
399 support them. It does not support the 2920 cards from Adaptec that
400 use the Future Domain SCSI controller chip. For those cards, you
401 need the "Future Domain 16xx SCSI support" driver.
403 In general, if the controller is based on an Adaptec SCSI controller
404 chip from the aic777x series or the aic78xx series, this driver
405 should work. The only exception is the 7810 which is specifically
406 not supported (that's the RAID controller chip on the AAA-13x
409 Note that the AHA2920 SCSI host adapter is *not* supported by this
410 driver; choose "Future Domain 16xx SCSI support" instead if you have
413 Information on the configuration options for this controller can be
414 found by checking the help file for each of the available
415 configuration options. You should read
416 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
417 contacting the maintainer with any questions. The SCSI-HOWTO,
418 available from <http://www.tldp.org/docs.html#howto>, can also
421 To compile this driver as a module, choose M here: the
422 module will be called aic7xxx_old.
424 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
426 # All the I2O code and drivers do not seem to be 64bit safe.
428 tristate "Adaptec I2O RAID support "
429 depends on !64BIT && SCSI && PCI
431 This driver supports all of Adaptec's I2O based RAID controllers as
432 well as the DPT SmartRaid V cards. This is an Adaptec maintained
433 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
435 To compile this driver as a module, choose M here: the
436 module will be called dpt_i2o.
439 tristate "AdvanSys SCSI support"
440 depends on (ISA || EISA || PCI) && SCSI && BROKEN
442 This is a driver for all SCSI host adapters manufactured by
443 AdvanSys. It is documented in the kernel source in
444 <file:drivers/scsi/advansys.c>.
446 To compile this driver as a module, choose M here: the
447 module will be called advansys.
450 tristate "Always IN2000 SCSI support"
451 depends on ISA && SCSI
453 This is support for an ISA bus SCSI host adapter. You'll find more
454 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
455 out of the box, you may have to change the jumpers for IRQ or
458 To compile this driver as a module, choose M here: the
459 module will be called in2000.
461 source "drivers/scsi/megaraid/Kconfig.megaraid"
464 tristate "Serial ATA (SATA) support"
467 This driver family supports Serial ATA host controllers
472 config SCSI_SATA_AHCI
473 tristate "AHCI SATA support"
474 depends on SCSI_SATA && PCI
476 This option enables support for AHCI Serial ATA.
481 tristate "ServerWorks Frodo / Apple K2 SATA support"
482 depends on SCSI_SATA && PCI
484 This option enables support for Broadcom/Serverworks/Apple K2
490 tristate "Intel PIIX/ICH SATA support"
491 depends on SCSI_SATA && PCI
493 This option enables support for ICH5 Serial ATA.
494 If PATA support was enabled previously, this enables
495 support for select Intel PIIX/ICH PATA host controllers.
500 tristate "Marvell SATA support"
501 depends on SCSI_SATA && PCI && EXPERIMENTAL
503 This option enables support for the Marvell Serial ATA family.
504 Currently supports 88SX[56]0[48][01] chips.
509 tristate "NVIDIA SATA support"
510 depends on SCSI_SATA && PCI && EXPERIMENTAL
512 This option enables support for NVIDIA Serial ATA.
517 tristate "Pacific Digital ADMA support"
518 depends on SCSI_SATA && PCI
520 This option enables support for Pacific Digital ADMA controllers
524 config SCSI_SATA_QSTOR
525 tristate "Pacific Digital SATA QStor support"
526 depends on SCSI_SATA && PCI
528 This option enables support for Pacific Digital Serial ATA QStor.
532 config SCSI_SATA_PROMISE
533 tristate "Promise SATA TX2/TX4 support"
534 depends on SCSI_SATA && PCI
536 This option enables support for Promise Serial ATA TX2/TX4.
541 tristate "Promise SATA SX4 support"
542 depends on SCSI_SATA && PCI && EXPERIMENTAL
544 This option enables support for Promise Serial ATA SX4.
549 tristate "Silicon Image SATA support"
550 depends on SCSI_SATA && PCI && EXPERIMENTAL
552 This option enables support for Silicon Image Serial ATA.
556 config SCSI_SATA_SIL24
557 tristate "Silicon Image 3124/3132 SATA support"
558 depends on SCSI_SATA && PCI && EXPERIMENTAL
560 This option enables support for Silicon Image 3124/3132 Serial ATA.
565 tristate "SiS 964/180 SATA support"
566 depends on SCSI_SATA && PCI && EXPERIMENTAL
568 This option enables support for SiS Serial ATA 964/180.
573 tristate "ULi Electronics SATA support"
574 depends on SCSI_SATA && PCI && EXPERIMENTAL
576 This option enables support for ULi Electronics SATA.
581 tristate "VIA SATA support"
582 depends on SCSI_SATA && PCI
584 This option enables support for VIA Serial ATA.
588 config SCSI_SATA_VITESSE
589 tristate "VITESSE VSC-7174 SATA support"
590 depends on SCSI_SATA && PCI
592 This option enables support for Vitesse VSC7174 Serial ATA.
596 config SCSI_SATA_INTEL_COMBINED
598 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
602 tristate "BusLogic SCSI support"
603 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
605 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
606 Adapters. Consult the SCSI-HOWTO, available from
607 <http://www.tldp.org/docs.html#howto>, and the files
608 <file:Documentation/scsi/BusLogic.txt> and
609 <file:Documentation/scsi/FlashPoint.txt> for more information.
611 To compile this driver as a module, choose M here: the
612 module will be called BusLogic.
614 config SCSI_OMIT_FLASHPOINT
615 bool "Omit FlashPoint support"
616 depends on SCSI_BUSLOGIC
618 This option allows you to omit the FlashPoint support from the
619 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
620 substantial, so users of MultiMaster Host Adapters may wish to omit
624 # This is marked broken because it uses over 4kB of stack in
626 # 2076 CpqTsProcessIMQEntry
630 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
631 depends on PCI && SCSI && BROKEN
633 Say Y here to compile in support for the Compaq StorageWorks Fibre
634 Channel 64-bit/66Mhz Host Bus Adapter.
637 tristate "DMX3191D SCSI support"
638 depends on PCI && SCSI
640 This is support for Domex DMX3191D SCSI Host Adapters.
642 To compile this driver as a module, choose M here: the
643 module will be called dmx3191d.
646 tristate "DTC3180/3280 SCSI support"
647 depends on ISA && SCSI
649 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
650 the SCSI-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>, and the file
652 <file:Documentation/scsi/dtc3x80.txt>.
654 To compile this driver as a module, choose M here: the
655 module will be called dtc.
658 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
659 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
661 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
662 ISA and all EISA I/O addresses are probed looking for the "EATA"
663 signature. The addresses of all the PCI SCSI controllers reported
664 by the PCI subsystem are probed as well.
666 You want to read the start of <file:drivers/scsi/eata.c> and the
667 SCSI-HOWTO, available from
668 <http://www.tldp.org/docs.html#howto>.
670 To compile this driver as a module, choose M here: the
671 module will be called eata.
673 config SCSI_EATA_TAGGED_QUEUE
674 bool "enable tagged command queueing"
677 This is a feature of SCSI-2 which improves performance: the host
678 adapter can send several SCSI commands to a device's queue even if
679 previous commands haven't finished yet.
680 This is equivalent to the "eata=tc:y" boot option.
682 config SCSI_EATA_LINKED_COMMANDS
683 bool "enable elevator sorting"
686 This option enables elevator sorting for all probed SCSI disks and
687 CD-ROMs. It definitely reduces the average seek distance when doing
688 random seeks, but this does not necessarily result in a noticeable
689 performance improvement: your mileage may vary...
690 This is equivalent to the "eata=lc:y" boot option.
692 config SCSI_EATA_MAX_TAGS
693 int "maximum number of queued commands"
697 This specifies how many SCSI commands can be maximally queued for
698 each probed SCSI device. You should reduce the default value of 16
699 only if you have disks with buggy or limited tagged command support.
700 Minimum is 2 and maximum is 62. This value is also the window size
701 used by the elevator sorting option above. The effective value used
702 by the driver for each probed SCSI device is reported at boot time.
703 This is equivalent to the "eata=mq:8" boot option.
706 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
707 depends on (ISA || EISA || PCI) && SCSI && BROKEN
709 This driver supports all EATA-PIO protocol compliant SCSI Host
710 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
711 host adapters could also use this driver but are discouraged from
712 doing so, since this driver only supports hard disks and lacks
713 numerous features. You might want to have a look at the SCSI-HOWTO,
714 available from <http://www.tldp.org/docs.html#howto>.
716 To compile this driver as a module, choose M here: the
717 module will be called eata_pio.
719 config SCSI_FUTURE_DOMAIN
720 tristate "Future Domain 16xx SCSI/AHA-2920A support"
721 depends on (ISA || PCI) && SCSI
723 This is support for Future Domain's 16-bit SCSI host adapters
724 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
725 other adapters based on the Future Domain chipsets (Quantum
726 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
727 It is explained in section 3.7 of the SCSI-HOWTO, available from
728 <http://www.tldp.org/docs.html#howto>.
730 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
731 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
732 controller support"). This Future Domain driver works with the older
733 Adaptec AHA-2920A boards with a Future Domain chip on them.
735 To compile this driver as a module, choose M here: the
736 module will be called fdomain.
739 tristate "Future Domain MCS-600/700 SCSI support"
740 depends on MCA_LEGACY && SCSI
742 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
743 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
744 is identical to the MCS 700 and hence also supported by this driver.
745 This driver also supports the Reply SB16/SCSI card (the SCSI part).
746 It supports multiple adapters in the same system.
748 To compile this driver as a module, choose M here: the
749 module will be called fd_mcs.
752 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
753 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
755 Formerly called GDT SCSI Disk Array Controller Support.
757 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
758 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
759 in the kernel source in <file:drivers/scsi/gdth.c> and
760 <file:drivers/scsi/gdth.h.>
762 To compile this driver as a module, choose M here: the
763 module will be called gdth.
765 config SCSI_GENERIC_NCR5380
766 tristate "Generic NCR5380/53c400 SCSI PIO support"
767 depends on ISA && SCSI
769 This is a driver for the old NCR 53c80 series of SCSI controllers
770 on boards using PIO. Most boards such as the Trantor T130 fit this
771 category, along with a large number of ISA 8bit controllers shipped
772 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
773 you should select the specific driver for that card rather than
774 generic 5380 support.
776 It is explained in section 3.8 of the SCSI-HOWTO, available from
777 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
778 of the box, you may have to change some settings in
779 <file:drivers/scsi/g_NCR5380.h>.
781 To compile this driver as a module, choose M here: the
782 module will be called g_NCR5380.
784 config SCSI_GENERIC_NCR5380_MMIO
785 tristate "Generic NCR5380/53c400 SCSI MMIO support"
786 depends on ISA && SCSI
788 This is a driver for the old NCR 53c80 series of SCSI controllers
789 on boards using memory mapped I/O.
790 It is explained in section 3.8 of the SCSI-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
792 of the box, you may have to change some settings in
793 <file:drivers/scsi/g_NCR5380.h>.
795 To compile this driver as a module, choose M here: the
796 module will be called g_NCR5380_mmio.
798 config SCSI_GENERIC_NCR53C400
799 bool "Enable NCR53c400 extensions"
800 depends on SCSI_GENERIC_NCR5380
802 This enables certain optimizations for the NCR53c400 SCSI cards.
803 You might as well try it out. Note that this driver will only probe
804 for the Trantor T130B in its default configuration; you might have
805 to pass a command line option to the kernel at boot time if it does
806 not detect your card. See the file
807 <file:Documentation/scsi/g_NCR5380.txt> for details.
810 tristate "IBMMCA SCSI support"
811 depends on MCA_LEGACY && SCSI
813 This is support for the IBM SCSI adapter found in many of the PS/2
814 series computers. These machines have an MCA bus, so you need to
815 answer Y to "MCA support" as well and read
816 <file:Documentation/mca.txt>.
818 If the adapter isn't found during boot (a common problem for models
819 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
820 option, where <pun> is the id of the SCSI subsystem (usually 7, but
821 if that doesn't work check your reference diskette). Owners of
822 model 95 with a LED-matrix-display can in addition activate some
823 activity info like under OS/2, but more informative, by setting
824 'ibmmcascsi=display' as an additional kernel parameter. Try "man
825 bootparam" or see the documentation of your boot loader about how to
826 pass options to the kernel.
828 To compile this driver as a module, choose M here: the
829 module will be called ibmmca.
831 config IBMMCA_SCSI_ORDER_STANDARD
832 bool "Standard SCSI-order"
833 depends on SCSI_IBMMCA
835 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
836 are assigned to the drive letters, starting with the lowest SCSI-id
837 (physical number -- pun) to be drive C:, as seen from DOS and
838 similar operating systems. When looking into papers describing the
839 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
840 The SCSI-standard follows a hardware-hierarchy which says that id 7
841 has the highest priority and id 0 the lowest. Therefore, the host
842 adapters are still today everywhere placed as SCSI-id 7 by default.
843 In the SCSI-standard, the drive letters express the priority of the
844 disk. C: should be the hard disk, or a partition on it, with the
845 highest priority. This must therefore be the disk with the highest
846 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
847 original definition of the SCSI-standard as also industrial- and
848 process-control-machines, like VME-CPUs running under realtime-OSes
849 (e.g. LynxOS, OS9) do.
851 If you like to run Linux on your MCA-machine with the same
852 assignment of hard disks as seen from e.g. DOS or OS/2 on your
853 machine, which is in addition conformant to the SCSI-standard, you
854 must say Y here. This is also necessary for MCA-Linux users who want
855 to keep downward compatibility to older releases of the
856 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
859 If you like to have the lowest SCSI-id assigned as drive C:, as
860 modern SCSI-BIOSes do, which does not conform to the standard, but
861 is widespread and common in the PC-world of today, you must say N
862 here. If unsure, say Y.
864 config IBMMCA_SCSI_DEV_RESET
865 bool "Reset SCSI-devices at boottime"
866 depends on SCSI_IBMMCA
868 By default, SCSI-devices are reset when the machine is powered on.
869 However, some devices exist, like special-control-devices,
870 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
871 not reset when switched on. If you say Y here, each device connected
872 to your SCSI-bus will be issued a reset-command after it has been
873 probed, while the kernel is booting. This may cause problems with
874 more modern devices, like hard disks, which do not appreciate these
875 reset commands, and can cause your system to hang. So say Y only if
876 you know that one of your older devices needs it; N is the safe
880 tristate "IBM ServeRAID support"
881 depends on PCI && SCSI
883 This is support for the IBM ServeRAID hardware RAID controllers.
884 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
885 for more information. If this driver does not work correctly
886 without modification please contact the author by email at
887 <ipslinux@adaptec.com>.
889 To compile this driver as a module, choose M here: the
890 module will be called ips.
893 tristate "IBM Virtual SCSI support"
894 depends on PPC_PSERIES || PPC_ISERIES
896 This is the IBM POWER Virtual SCSI Client
898 To compile this driver as a module, choose M here: the
899 module will be called ibmvscsic.
902 tristate "Initio 9100U(W) support"
903 depends on PCI && SCSI
905 This is support for the Initio 91XXU(W) SCSI host adapter. Please
906 read the SCSI-HOWTO, available from
907 <http://www.tldp.org/docs.html#howto>.
909 To compile this driver as a module, choose M here: the
910 module will be called initio.
913 tristate "Initio INI-A100U2W support"
914 depends on PCI && SCSI
916 This is support for the Initio INI-A100U2W SCSI host adapter.
917 Please read the SCSI-HOWTO, available from
918 <http://www.tldp.org/docs.html#howto>.
920 To compile this driver as a module, choose M here: the
921 module will be called a100u2w.
924 tristate "IOMEGA parallel port (ppa - older drives)"
925 depends on SCSI && PARPORT
927 This driver supports older versions of IOMEGA's parallel port ZIP
928 drive (a 100 MB removable media device).
930 Note that you can say N here if you have the SCSI version of the ZIP
931 drive: it will be supported automatically if you said Y to the
932 generic "SCSI disk support", above.
934 If you have the ZIP Plus drive or a more recent parallel port ZIP
935 drive (if the supplied cable with the drive is labeled "AutoDetect")
936 then you should say N here and Y to "IOMEGA parallel port (imm -
937 newer drives)", below.
939 For more information about this driver and how to use it you should
940 read the file <file:Documentation/scsi/ppa.txt>. You should also read
941 the SCSI-HOWTO, which is available from
942 <http://www.tldp.org/docs.html#howto>. If you use this driver,
943 you will still be able to use the parallel port for other tasks,
944 such as a printer; it is safe to compile both drivers into the
947 To compile this driver as a module, choose M here: the
948 module will be called ppa.
951 tristate "IOMEGA parallel port (imm - newer drives)"
952 depends on SCSI && PARPORT
954 This driver supports newer versions of IOMEGA's parallel port ZIP
955 drive (a 100 MB removable media device).
957 Note that you can say N here if you have the SCSI version of the ZIP
958 drive: it will be supported automatically if you said Y to the
959 generic "SCSI disk support", above.
961 If you have the ZIP Plus drive or a more recent parallel port ZIP
962 drive (if the supplied cable with the drive is labeled "AutoDetect")
963 then you should say Y here; if you have an older ZIP drive, say N
964 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
966 For more information about this driver and how to use it you should
967 read the file <file:Documentation/scsi/ppa.txt>. You should also read
968 the SCSI-HOWTO, which is available from
969 <http://www.tldp.org/docs.html#howto>. If you use this driver,
970 you will still be able to use the parallel port for other tasks,
971 such as a printer; it is safe to compile both drivers into the
974 To compile this driver as a module, choose M here: the
975 module will be called imm.
977 config SCSI_IZIP_EPP16
978 bool "ppa/imm option - Use slow (but safe) EPP-16"
979 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
981 EPP (Enhanced Parallel Port) is a standard for parallel ports which
982 allows them to act as expansion buses that can handle up to 64
985 Some parallel port chipsets are slower than their motherboard, and
986 so we have to control the state of the chipset's FIFO queue every
987 now and then to avoid data loss. This will be done if you say Y
990 Generally, saying Y is the safe option and slows things down a bit.
992 config SCSI_IZIP_SLOW_CTR
993 bool "ppa/imm option - Assume slow parport control register"
994 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
996 Some parallel ports are known to have excessive delays between
997 changing the parallel port control register and good data being
998 available on the parallel port data/status register. This option
999 forces a small delay (1.0 usec to be exact) after changing the
1000 control register to let things settle out. Enabling this option may
1001 result in a big drop in performance but some very old parallel ports
1002 (found in 386 vintage machines) will not work properly.
1004 Generally, saying N is fine.
1006 config SCSI_NCR53C406A
1007 tristate "NCR53c406a SCSI support"
1008 depends on ISA && SCSI
1010 This is support for the NCR53c406a SCSI host adapter. For user
1011 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1012 in the kernel source. Also read the SCSI-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
1015 To compile this driver as a module, choose M here: the
1016 module will be called NCR53c406.
1018 config SCSI_NCR_D700
1019 tristate "NCR Dual 700 MCA SCSI support"
1020 depends on MCA && SCSI
1021 select SCSI_SPI_ATTRS
1023 This is a driver for the MicroChannel Dual 700 card produced by
1024 NCR and commonly used in 345x/35xx/4100 class machines. It always
1025 tries to negotiate sync and uses tag command queueing.
1027 Unless you have an NCR manufactured machine, the chances are that
1028 you do not have this SCSI card, so say N.
1031 tristate "HP Lasi SCSI support for 53c700/710"
1032 depends on GSC && SCSI
1033 select SCSI_SPI_ATTRS
1035 This is a driver for the SCSI controller in the Lasi chip found in
1036 many PA-RISC workstations & servers. If you do not know whether you
1037 have a Lasi chip, it is safe to say "Y" here.
1039 config 53C700_LE_ON_BE
1041 depends on SCSI_LASI700
1044 config SCSI_SYM53C8XX_2
1045 tristate "SYM53C8XX Version 2 SCSI support"
1046 depends on PCI && SCSI
1047 select SCSI_SPI_ATTRS
1049 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1050 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1051 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1052 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1053 controllers; you need to use the Fusion MPT driver for that.
1055 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1058 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1059 int "DMA addressing mode"
1060 depends on SCSI_SYM53C8XX_2
1063 This option only applies to PCI-SCSI chips that are PCI DAC
1064 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1066 When set to 0, the driver will program the chip to only perform
1067 32-bit DMA. When set to 1, the chip will be able to perform DMA
1068 to addresses up to 1TB. When set to 2, the driver supports the
1069 full 64-bit DMA address range, but can only address 16 segments
1070 of 4 GB each. This limits the total addressable range to 64 GB.
1072 Most machines with less than 4GB of memory should use a setting
1073 of 0 for best performance. If your machine has 4GB of memory
1074 or more, you should set this option to 1 (the default).
1076 The still experimental value 2 (64 bit DMA addressing with 16
1077 x 4GB segments limitation) can be used on systems that require
1078 PCI address bits past bit 39 to be set for the addressing of
1079 memory using PCI DAC cycles.
1081 config SCSI_SYM53C8XX_DEFAULT_TAGS
1082 int "default tagged command queue depth"
1083 depends on SCSI_SYM53C8XX_2
1086 This is the default value of the command queue depth the
1087 driver will announce to the generic SCSI layer for devices
1088 that support tagged command queueing. This value can be changed
1089 from the boot command line. This is a soft limit that cannot
1090 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1092 config SCSI_SYM53C8XX_MAX_TAGS
1093 int "maximum number of queued commands"
1094 depends on SCSI_SYM53C8XX_2
1097 This option allows you to specify the maximum number of commands
1098 that can be queued to any device, when tagged command queuing is
1099 possible. The driver supports up to 256 queued commands per device.
1100 This value is used as a compiled-in hard limit.
1102 config SCSI_SYM53C8XX_IOMAPPED
1104 depends on SCSI_SYM53C8XX_2
1106 If you say Y here, the driver will use port IO to access
1107 the card. This is significantly slower then using memory
1108 mapped IO. Most people should answer N.
1111 tristate "IBM Power Linux RAID adapter support"
1112 depends on PCI && SCSI
1115 This driver supports the IBM Power Linux family RAID adapters.
1116 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1117 as IBM iSeries 5702, 5703, 5709, and 570A.
1119 config SCSI_IPR_TRACE
1120 bool "enable driver internal trace"
1123 If you say Y here, the driver will trace all commands issued
1124 to the adapter. Performance impact is minimal. Trace can be
1125 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1127 config SCSI_IPR_DUMP
1128 bool "enable adapter dump support"
1131 If you say Y here, the driver will support adapter crash dump.
1132 If you enable this support, the iprdump daemon can be used
1133 to capture adapter failure analysis information.
1136 tristate "Zalon SCSI support"
1137 depends on GSC && SCSI
1138 select SCSI_SPI_ATTRS
1140 The Zalon is a GSC/HSC bus interface chip that sits between the
1141 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1142 C110, J200, J210 and some D, K & R-class machines. It's also
1143 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1144 Say Y here if you have one of these machines or cards.
1146 config SCSI_NCR_Q720
1147 tristate "NCR Quad 720 MCA SCSI support"
1148 depends on MCA && SCSI
1149 select SCSI_SPI_ATTRS
1151 This is a driver for the MicroChannel Quad 720 card produced by
1152 NCR and commonly used in 345x/35xx/4100 class machines. It always
1153 tries to negotiate sync and uses tag command queueing.
1155 Unless you have an NCR manufactured machine, the chances are that
1156 you do not have this SCSI card, so say N.
1158 config SCSI_NCR53C8XX_DEFAULT_TAGS
1159 int " default tagged command queue depth"
1160 depends on SCSI_ZALON || SCSI_NCR_Q720
1163 "Tagged command queuing" is a feature of SCSI-2 which improves
1164 performance: the host adapter can send several SCSI commands to a
1165 device's queue even if previous commands haven't finished yet.
1166 Because the device is intelligent, it can optimize its operations
1167 (like head positioning) based on its own request queue. Some SCSI
1168 devices don't implement this properly; if you want to disable this
1169 feature, enter 0 or 1 here (it doesn't matter which).
1171 The default value is 8 and should be supported by most hard disks.
1172 This value can be overridden from the boot command line using the
1173 'tags' option as follows (example):
1174 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1175 4, set queue depth to 16 for target 2 and target 3 on controller 0
1176 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1178 The normal answer therefore is to go with the default 8 and to use
1179 a boot command line option for devices that need to use a different
1180 command queue depth.
1182 There is no safe option other than using good SCSI devices.
1184 config SCSI_NCR53C8XX_MAX_TAGS
1185 int " maximum number of queued commands"
1186 depends on SCSI_ZALON || SCSI_NCR_Q720
1189 This option allows you to specify the maximum number of commands
1190 that can be queued to any device, when tagged command queuing is
1191 possible. The default value is 32. Minimum is 2, maximum is 64.
1192 Modern hard disks are able to support 64 tags and even more, but
1193 do not seem to be faster when more than 32 tags are being used.
1195 So, the normal answer here is to go with the default value 32 unless
1196 you are using very large hard disks with large cache (>= 1 MB) that
1197 are able to take advantage of more than 32 tagged commands.
1199 There is no safe option and the default answer is recommended.
1201 config SCSI_NCR53C8XX_SYNC
1202 int " synchronous transfers frequency in MHz"
1203 depends on SCSI_ZALON || SCSI_NCR_Q720
1206 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1207 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1208 are respectively the maximum data transfer rates in mega-transfers
1209 per second for each class. For example, a FAST-20 Wide 16 device is
1210 able to transfer data at 20 million 16 bit packets per second for a
1211 total rate of 40 MB/s.
1213 You may specify 0 if you want to only use asynchronous data
1214 transfers. This is the safest and slowest option. Otherwise, specify
1215 a value between 5 and 80, depending on the capability of your SCSI
1216 controller. The higher the number, the faster the data transfer.
1217 Note that 80 should normally be ok since the driver decreases the
1218 value automatically according to the controller's capabilities.
1220 Your answer to this question is ignored for controllers with NVRAM,
1221 since the driver will get this information from the user set-up. It
1222 also can be overridden using a boot setup option, as follows
1223 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1224 for FAST-20 synchronous data transfer (20 mega-transfers per
1227 The normal answer therefore is not to go with the default but to
1228 select the maximum value 80 allowing the driver to use the maximum
1229 value supported by each controller. If this causes problems with
1230 your SCSI devices, you should come back and decrease the value.
1232 There is no safe option other than using good cabling, right
1233 terminations and SCSI conformant devices.
1235 config SCSI_NCR53C8XX_PROFILE
1236 bool " enable profiling"
1237 depends on SCSI_ZALON || SCSI_NCR_Q720
1239 This option allows you to enable profiling information gathering.
1240 These statistics are not very accurate due to the low frequency
1241 of the kernel clock (100 Hz on i386) and have performance impact
1242 on systems that use very fast devices.
1244 The normal answer therefore is N.
1246 config SCSI_NCR53C8XX_NO_DISCONNECT
1247 bool " not allow targets to disconnect"
1248 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1250 This option is only provided for safety if you suspect some SCSI
1251 device of yours to not support properly the target-disconnect
1252 feature. In that case, you would say Y here. In general however, to
1253 not allow targets to disconnect is not reasonable if there is more
1254 than 1 device on a SCSI bus. The normal answer therefore is N.
1256 config SCSI_MCA_53C9X
1257 tristate "NCR MCA 53C9x SCSI support"
1258 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1260 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1261 controller based on the NCR 53C94. This driver will allow use of
1262 the controller on the 3550, and very possibly others.
1264 To compile this driver as a module, choose M here: the
1265 module will be called mca_53c9x.
1268 tristate "PAS16 SCSI support"
1269 depends on ISA && SCSI
1271 This is support for a SCSI host adapter. It is explained in section
1272 3.10 of the SCSI-HOWTO, available from
1273 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1274 of the box, you may have to change some settings in
1275 <file:drivers/scsi/pas16.h>.
1277 To compile this driver as a module, choose M here: the
1278 module will be called pas16.
1281 tristate "PSI240i support"
1282 depends on ISA && SCSI
1284 This is support for the PSI240i EIDE interface card which acts as a
1285 SCSI host adapter. Please read the SCSI-HOWTO, available from
1286 <http://www.tldp.org/docs.html#howto>.
1288 To compile this driver as a module, choose M here: the
1289 module will be called psi240i.
1291 config SCSI_QLOGIC_FAS
1292 tristate "Qlogic FAS SCSI support"
1293 depends on ISA && SCSI
1295 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1296 FastSCSI! cards as well as any other card based on the FASXX chip
1297 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1299 This driver does NOT support the PCI versions of these cards. The
1300 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1301 SCSI support"), below.
1303 Information about this driver is contained in
1304 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1305 SCSI-HOWTO, available from
1306 <http://www.tldp.org/docs.html#howto>.
1308 To compile this driver as a module, choose M here: the
1309 module will be called qlogicfas.
1311 config SCSI_QLOGIC_ISP
1312 tristate "Qlogic ISP SCSI support (old driver)"
1313 depends on PCI && SCSI && BROKEN
1315 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1316 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1317 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1319 If you say Y here, make sure to choose "BIOS" at the question "PCI
1322 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1323 should also read the SCSI-HOWTO, available from
1324 <http://www.tldp.org/docs.html#howto>.
1326 To compile this driver as a module, choose M here: the
1327 module will be called qlogicisp.
1329 These days the hardware is also supported by the more modern qla1280
1330 driver. In doubt use that one instead of qlogicisp.
1332 config SCSI_QLOGIC_FC
1333 tristate "Qlogic ISP FC SCSI support"
1334 depends on PCI && SCSI
1336 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1338 To compile this driver as a module, choose M here: the
1339 module will be called qlogicfc.
1341 config SCSI_QLOGIC_FC_FIRMWARE
1342 bool "Include loadable firmware in driver"
1343 depends on SCSI_QLOGIC_FC
1345 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1346 expanded LUN addressing and FcTape (FCP-2) support, in the
1347 qlogicfc driver. This is required on some platforms.
1349 config SCSI_QLOGIC_1280
1350 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1351 depends on PCI && SCSI
1353 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1355 To compile this driver as a module, choose M here: the
1356 module will be called qla1280.
1358 config SCSI_QLOGIC_1280_1040
1359 bool "Qlogic QLA 1020/1040 SCSI support"
1360 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1362 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1363 do not want to use the old driver. This option enables support in
1364 the qla1280 driver for those host adapters.
1366 config SCSI_QLOGICPTI
1367 tristate "PTI Qlogic, ISP Driver"
1368 depends on SBUS && SCSI
1370 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1371 controllers are known under Solaris as qpti and in the openprom as
1372 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1373 driven by a different driver.
1375 To compile this driver as a module, choose M here: the
1376 module will be called qlogicpti.
1378 source "drivers/scsi/qla2xxx/Kconfig"
1381 tristate "Emulex LightPulse Fibre Channel Support"
1382 depends on PCI && SCSI
1383 select SCSI_FC_ATTRS
1385 This lpfc driver supports the Emulex LightPulse
1386 Family of Fibre Channel PCI host adapters.
1389 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1390 depends on X86 && ISA && SCSI && BROKEN
1392 These are 8-bit SCSI controllers; the ST-01 is also supported by
1393 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1394 available from <http://www.tldp.org/docs.html#howto>. If it
1395 doesn't work out of the box, you may have to change some settings in
1396 <file:drivers/scsi/seagate.h>.
1398 To compile this driver as a module, choose M here: the
1399 module will be called seagate.
1401 # definitely looks not 64bit safe:
1403 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1404 depends on (EISA || MCA) && SCSI
1405 select SCSI_SPI_ATTRS
1407 This driver for NCR53c710 based SCSI host adapters.
1409 It currently supports Compaq EISA cards and NCR MCA cards
1411 config 53C700_IO_MAPPED
1413 depends on SCSI_SIM710
1416 config SCSI_SYM53C416
1417 tristate "Symbios 53c416 SCSI support"
1418 depends on ISA && SCSI
1420 This is support for the sym53c416 SCSI host adapter, the SCSI
1421 adapter that comes with some HP scanners. This driver requires that
1422 the sym53c416 is configured first using some sort of PnP
1423 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1424 are using isapnp then you need to compile this driver as a module
1425 and then load it using insmod after isapnp has run. The parameters
1426 of the configured card(s) should be passed to the driver. The format
1429 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1431 To compile this driver as a module, choose M here: the
1432 module will be called sym53c416.
1435 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1436 depends on PCI && SCSI && EXPERIMENTAL
1438 This driver supports PCI SCSI host adapters based on the ASIC
1439 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1441 This driver works, but is still in experimental status. So better
1442 have a bootable disk and a backup in case of emergency.
1444 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1446 To compile this driver as a module, choose M here: the
1447 module will be called dc395x.
1450 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1451 depends on PCI && SCSI
1453 This driver supports PCI SCSI host adapters based on the Am53C974A
1454 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1455 PCscsi/PCnet (Am53/79C974) solutions.
1457 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1459 Note that this driver does NOT support Tekram DC390W/U/F, which are
1460 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1462 To compile this driver as a module, choose M here: the
1463 module will be called tmscsim.
1466 tristate "Trantor T128/T128F/T228 SCSI support"
1467 depends on ISA && SCSI
1469 This is support for a SCSI host adapter. It is explained in section
1470 3.11 of the SCSI-HOWTO, available from
1471 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1472 of the box, you may have to change some settings in
1473 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1474 Adaptec, and some former Trantor products are being sold under the
1477 To compile this driver as a module, choose M here: the
1478 module will be called t128.
1481 tristate "UltraStor 14F/34F support"
1482 depends on ISA && SCSI && ISA_DMA_API
1484 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1485 The source at <file:drivers/scsi/u14-34f.c> contains some
1486 information about this hardware. If the driver doesn't work out of
1487 the box, you may have to change some settings in
1488 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1489 <http://www.tldp.org/docs.html#howto>. Note that there is also
1490 another driver for the same hardware: "UltraStor SCSI support",
1491 below. You should say Y to both only if you want 24F support as
1494 To compile this driver as a module, choose M here: the
1495 module will be called u14-34f.
1497 config SCSI_U14_34F_TAGGED_QUEUE
1498 bool "enable tagged command queueing"
1499 depends on SCSI_U14_34F
1501 This is a feature of SCSI-2 which improves performance: the host
1502 adapter can send several SCSI commands to a device's queue even if
1503 previous commands haven't finished yet.
1504 This is equivalent to the "u14-34f=tc:y" boot option.
1506 config SCSI_U14_34F_LINKED_COMMANDS
1507 bool "enable elevator sorting"
1508 depends on SCSI_U14_34F
1510 This option enables elevator sorting for all probed SCSI disks and
1511 CD-ROMs. It definitely reduces the average seek distance when doing
1512 random seeks, but this does not necessarily result in a noticeable
1513 performance improvement: your mileage may vary...
1514 This is equivalent to the "u14-34f=lc:y" boot option.
1516 config SCSI_U14_34F_MAX_TAGS
1517 int "maximum number of queued commands"
1518 depends on SCSI_U14_34F
1521 This specifies how many SCSI commands can be maximally queued for
1522 each probed SCSI device. You should reduce the default value of 8
1523 only if you have disks with buggy or limited tagged command support.
1524 Minimum is 2 and maximum is 14. This value is also the window size
1525 used by the elevator sorting option above. The effective value used
1526 by the driver for each probed SCSI device is reported at boot time.
1527 This is equivalent to the "u14-34f=mq:8" boot option.
1529 config SCSI_ULTRASTOR
1530 tristate "UltraStor SCSI support"
1531 depends on X86 && ISA && SCSI
1533 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1534 adapter family. This driver is explained in section 3.12 of the
1535 SCSI-HOWTO, available from
1536 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1537 of the box, you may have to change some settings in
1538 <file:drivers/scsi/ultrastor.h>.
1540 Note that there is also another driver for the same hardware:
1541 "UltraStor 14F/34F support", above.
1543 To compile this driver as a module, choose M here: the
1544 module will be called ultrastor.
1547 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1548 depends on PCI && SCSI && !64BIT
1550 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1551 SCSI host adapter. Please read the SCSI-HOWTO, available from
1552 <http://www.tldp.org/docs.html#howto>.
1554 To compile this driver as a module, choose M here: the
1555 module will be called nsp32.
1558 tristate "SCSI debugging host simulator"
1561 This is a host adapter simulator that can simulate multiple hosts
1562 each with multiple dummy SCSI devices (disks). It defaults to one
1563 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1564 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1565 dummy disks are simulated, they share the same kernel RAM for
1566 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1567 information. This driver is primarily of use to those testing the
1568 SCSI and block subsystems. If unsure, say N.
1571 tristate "MESH (Power Mac internal SCSI) support"
1572 depends on PPC32 && PPC_PMAC && SCSI
1574 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1575 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1576 other Power Macintoshes do). Say Y to include support for this SCSI
1579 To compile this driver as a module, choose M here: the
1580 module will be called mesh.
1582 config SCSI_MESH_SYNC_RATE
1583 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1584 depends on SCSI_MESH
1587 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1588 drives a bus which is entirely internal to the machine (such as the
1589 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1590 operation at up to 10 MB/s. On machines where the SCSI bus
1591 controlled by the MESH can have external devices connected, it is
1592 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1593 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1594 to disable synchronous operation.
1596 config SCSI_MESH_RESET_DELAY_MS
1597 int "initial bus reset delay (ms) (0 = no reset)"
1598 depends on SCSI_MESH
1601 config SCSI_MAC53C94
1602 tristate "53C94 (Power Mac external SCSI) support"
1603 depends on PPC32 && PPC_PMAC && SCSI
1605 On Power Macintoshes (and clones) with two SCSI buses, the external
1606 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1607 machines which only have one SCSI bus, such as the 7200, also use
1608 the 53C94. Say Y to include support for the 53C94.
1610 To compile this driver as a module, choose M here: the
1611 module will be called mac53c94.
1613 source "drivers/scsi/arm/Kconfig"
1616 bool "MIPS JAZZ FAS216 SCSI support"
1617 depends on MACH_JAZZ && SCSI
1619 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1620 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1624 tristate "A3000 WD33C93A support"
1625 depends on AMIGA && SCSI
1627 If you have an Amiga 3000 and have SCSI devices connected to the
1628 built-in SCSI controller, say Y. Otherwise, say N.
1630 To compile this driver as a module, choose M here: the
1631 module will be called wd33c93.
1634 tristate "A2091/A590 WD33C93A support"
1635 depends on ZORRO && SCSI
1637 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1640 To compile this driver as a module, choose M here: the
1641 module will be called wd33c93.
1644 tristate "GVP Series II WD33C93A support"
1645 depends on ZORRO && SCSI
1647 If you have a Great Valley Products Series II SCSI controller,
1648 answer Y. Also say Y if you have a later model of GVP SCSI
1649 controller (such as the GVP A4008 or a Combo board). Otherwise,
1650 answer N. This driver does NOT work for the T-Rex series of
1651 accelerators from TekMagic and GVP-M.
1653 To compile this driver as a module, choose M here: the
1654 module will be called gvp11.
1656 config CYBERSTORM_SCSI
1657 tristate "CyberStorm SCSI support"
1658 depends on ZORRO && SCSI
1660 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1661 accelerator board and the optional Cyberstorm SCSI controller,
1662 answer Y. Otherwise, say N.
1664 config CYBERSTORMII_SCSI
1665 tristate "CyberStorm Mk II SCSI support"
1666 depends on ZORRO && SCSI
1668 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1669 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1673 tristate "Blizzard 2060 SCSI support"
1674 depends on ZORRO && SCSI
1676 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1677 and want to use the onboard SCSI controller, say Y. Otherwise,
1681 tristate "Blizzard 1230IV/1260 SCSI support"
1682 depends on ZORRO && SCSI
1684 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1685 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1688 config FASTLANE_SCSI
1689 tristate "Fastlane SCSI support"
1690 depends on ZORRO && SCSI
1692 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1693 one in the near future, say Y to this question. Otherwise, say N.
1695 config SCSI_AMIGA7XX
1696 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1697 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1699 Support for various NCR53c710-based SCSI controllers on the Amiga.
1701 - the builtin SCSI controller on the Amiga 4000T,
1702 - the Amiga 4091 Zorro III SCSI-2 controller,
1703 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1705 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1706 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1707 accelerator card for the Amiga 1200,
1708 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1709 Note that all of the above SCSI controllers, except for the builtin
1710 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1711 bus, so you also have to enable Zorro bus support if you want to use
1715 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1716 depends on ZORRO && SCSI && EXPERIMENTAL
1718 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1719 Y to this question. If you're in doubt about whether you have one,
1721 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1724 tristate "Atari native SCSI support"
1725 depends on ATARI && SCSI && BROKEN
1727 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1728 Falcon, ...) say Y to get it supported. Of course also, if you have
1729 a compatible SCSI controller (e.g. for Medusa).
1731 To compile this driver as a module, choose M here: the
1732 module will be called atari_scsi.
1734 This driver supports both styles of NCR integration into the
1735 system: the TT style (separate DMA), and the Falcon style (via
1736 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1737 in the Hades (without DMA).
1739 config ATARI_SCSI_TOSHIBA_DELAY
1740 bool "Long delays for Toshiba CD-ROMs"
1741 depends on ATARI_SCSI
1743 This option increases the delay after a SCSI arbitration to
1744 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1745 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1746 would impact performance a bit, so say N.
1748 config ATARI_SCSI_RESET_BOOT
1749 bool "Reset SCSI-devices at boottime"
1750 depends on ATARI_SCSI
1752 Reset the devices on your Atari whenever it boots. This makes the
1753 boot process fractionally longer but may assist recovery from errors
1754 that leave the devices with SCSI operations partway completed.
1757 bool "Hades SCSI DMA emulator"
1758 depends on ATARI_SCSI && HADES
1760 This option enables code which emulates the TT SCSI DMA chip on the
1761 Hades. This increases the SCSI transfer rates at least ten times
1762 compared to PIO transfers.
1765 bool "Macintosh NCR5380 SCSI"
1766 depends on MAC && SCSI=y
1768 This is the NCR 5380 SCSI controller included on most of the 68030
1769 based Macintoshes. If you have one of these say Y and read the
1770 SCSI-HOWTO, available from
1771 <http://www.tldp.org/docs.html#howto>.
1774 tristate "Macintosh NCR53c9[46] SCSI"
1775 depends on MAC && SCSI
1777 This is the NCR 53c9x SCSI controller found on most of the 68040
1778 based Macintoshes. If you have one of these say Y and read the
1779 SCSI-HOWTO, available from
1780 <http://www.tldp.org/docs.html#howto>.
1782 To compile this driver as a module, choose M here: the
1783 module will be called mac_esp.
1786 bool "WD33C93 SCSI driver for MVME147"
1787 depends on MVME147 && SCSI=y
1789 Support for the on-board SCSI controller on the Motorola MVME147
1790 single-board computer.
1793 bool "NCR53C710 SCSI driver for MVME16x"
1794 depends on MVME16x && SCSI && BROKEN
1796 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1797 SCSI controller chip. Almost everyone using one of these boards
1798 will want to say Y to this question.
1800 config BVME6000_SCSI
1801 bool "NCR53C710 SCSI driver for BVME6000"
1802 depends on BVME6000 && SCSI && BROKEN
1804 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1805 SCSI controller chip. Almost everyone using one of these boards
1806 will want to say Y to this question.
1808 config SCSI_NCR53C7xx_FAST
1809 bool "allow FAST-SCSI [10MHz]"
1810 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1812 This will enable 10MHz FAST-SCSI transfers with your host
1813 adapter. Some systems have problems with that speed, so it's safest
1817 tristate "Sun3 NCR5380 SCSI"
1818 depends on SUN3 && SCSI && BROKEN
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 ARCH_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"