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.
36 bool "legacy /proc/scsi/ support"
37 depends on SCSI && PROC_FS
40 This option enables support for the various files in
41 /proc/scsi. In Linux 2.6 this has been superceeded by
42 files in sysfs but many legacy applications rely on this.
46 comment "SCSI support type (disk, tape, CD-ROM)"
50 tristate "SCSI disk support"
53 If you want to use SCSI hard disks, Fibre Channel disks,
54 USB storage or the SCSI or parallel port version of
55 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
56 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
57 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
60 To compile this driver as a module, choose M here and read
61 <file:Documentation/scsi/scsi.txt>.
62 The module will be called sd_mod.
64 Do not compile this driver as a module if your root file system
65 (the one containing the directory /) is located on a SCSI disk.
66 In this case, do not compile the driver for your SCSI host adapter
67 (below) as a module either.
70 tristate "SCSI tape support"
73 If you want to use a SCSI tape drive under Linux, say Y and read the
74 SCSI-HOWTO, available from
75 <http://www.tldp.org/docs.html#howto>, and
76 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
79 To compile this driver as a module, choose M here and read
80 <file:Documentation/scsi/scsi.txt>. The module will be called st.
83 tristate "SCSI OnStream SC-x0 tape support"
86 The OnStream SC-x0 SCSI tape drives can not be driven by the
87 standard st driver, but instead need this special osst driver and
88 use the /dev/osstX char device nodes (major 206). Via usb-storage
89 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
90 as well. Note that there is also a second generation of OnStream
91 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
92 tapes (QIC-157) and can be driven by the standard driver st.
93 For more information, you may have a look at the SCSI-HOWTO
94 <http://www.tldp.org/docs.html#howto> and
95 <file:Documentation/scsi/osst.txt> in the kernel source.
96 More info on the OnStream driver may be found on
97 <http://linux1.onstream.nl/test/>
98 Please also have a look at the standard st docu, as most of it
99 applies to osst as well.
101 To compile this driver as a module, choose M here and read
102 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
105 tristate "SCSI CDROM support"
108 If you want to use a SCSI or FireWire CD-ROM under Linux,
109 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
110 <http://www.tldp.org/docs.html#howto>. Also make sure to say
111 Y or M to "ISO 9660 CD-ROM file system support" later.
113 To compile this driver as a module, choose M here and read
114 <file:Documentation/scsi/scsi.txt>.
115 The module will be called sr_mod.
117 config BLK_DEV_SR_VENDOR
118 bool "Enable vendor-specific extensions (for SCSI CDROM)"
119 depends on BLK_DEV_SR
121 This enables the usage of vendor specific SCSI commands. This is
122 required to support multisession CDs with old NEC/TOSHIBA cdrom
123 drives (and HP Writers). If you have such a drive and get the first
124 session only, try saying Y here; everybody else says N.
127 tristate "SCSI generic support"
130 If you want to use SCSI scanners, synthesizers or CD-writers or just
131 about anything having "SCSI" in its name other than hard disks,
132 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
133 directly, so you need some additional software which knows how to
134 talk to these devices using the SCSI protocol:
136 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
137 writer software look at Cdrtools
138 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
139 and for burning a "disk at once": CDRDAO
140 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
141 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
142 For other devices, it's possible that you'll have to write the
143 driver software yourself. Please read the file
144 <file:Documentation/scsi/scsi-generic.txt> for more information.
146 To compile this driver as a module, choose M here and read
147 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
152 tristate "SCSI media changer support"
155 This is a driver for SCSI media changers. Most common devices are
156 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
157 don't need this for those tiny 6-slot cdrom changers. Media
158 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
159 If you have such hardware and want to use it with linux, say Y
160 here. Check <file:Documentation/scsi-changer.txt> for details.
162 If you want to compile this as a module ( = code which can be
163 inserted in and removed from the running kernel whenever you want),
164 say M here and read <file:Documentation/modules.txt> and
165 <file:Documentation/scsi.txt>. The module will be called ch.o.
169 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
172 config SCSI_MULTI_LUN
173 bool "Probe all LUNs on each SCSI device"
176 If you have a SCSI device that supports more than one LUN (Logical
177 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
178 can say Y here to force the SCSI driver to probe for multiple LUNs.
179 A SCSI device with multiple LUNs acts logically like multiple SCSI
180 devices. The vast majority of SCSI devices have only one LUN, and
181 so most people can say N here. The max_luns boot/module parameter
182 allows to override this setting.
184 config SCSI_CONSTANTS
185 bool "Verbose SCSI error reporting (kernel size +=12K)"
188 The error messages regarding your SCSI hardware will be easier to
189 understand if you say Y here; it will enlarge your kernel by about
190 12 KB. If in doubt, say Y.
193 bool "SCSI logging facility"
196 This turns on a logging facility that can be used to debug a number
197 of SCSI related problems.
199 If you say Y here, no logging output will appear by default, but you
200 can enable logging by saying Y to "/proc file system support" and
201 "Sysctl support" below and executing the command
203 echo "scsi log token [level]" > /proc/scsi/scsi
205 at boot time after the /proc file system has been mounted.
207 There are a number of things that can be used for 'token' (you can
208 find them in the source: <file:drivers/scsi/scsi.c>), and this
209 allows you to select the types of information you want, and the
210 level allows you to select the level of verbosity.
212 If you say N here, it may be harder to track down some types of SCSI
213 problems. If you say Y here your kernel will be somewhat larger, but
214 there should be no noticeable performance impact as long as you have
217 menu "SCSI Transports"
220 config SCSI_SPI_ATTRS
221 tristate "Parallel SCSI (SPI) Transport Attributes"
224 If you wish to export transport-specific information about
225 each attached SCSI device to sysfs, say Y. Otherwise, say N.
228 tristate "FiberChannel Transport Attributes"
232 If you wish to export transport-specific information about
233 each attached FiberChannel device to sysfs, say Y.
236 config SCSI_ISCSI_ATTRS
237 tristate "iSCSI Transport Attributes"
238 depends on SCSI && NET
240 If you wish to export transport-specific information about
241 each attached iSCSI device to sysfs, say Y.
244 config SCSI_SAS_ATTRS
245 tristate "SAS Transport Attributes"
248 If you wish to export transport-specific information about
249 each attached SAS device to sysfs, say Y.
251 source "drivers/scsi/libsas/Kconfig"
255 menu "SCSI low-level drivers"
259 tristate "iSCSI Initiator over TCP/IP"
260 depends on SCSI && INET
264 select SCSI_ISCSI_ATTRS
266 The iSCSI Driver provides a host with the ability to access storage
267 through an IP network. The driver uses the iSCSI protocol to transport
268 SCSI requests and responses over a TCP/IP network between the host
269 (the "initiator") and "targets". Architecturally, the iSCSI driver
270 combines with the host's TCP/IP stack, network drivers, and Network
271 Interface Card (NIC) to provide the same functions as a SCSI or a
272 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
274 To compile this driver as a module, choose M here: the
275 module will be called iscsi_tcp.
277 The userspace component needed to initialize the driver, documentation,
278 and sample configuration files can be found here:
280 http://linux-iscsi.sf.net
283 tristate "SGI WD93C93 SCSI Driver"
284 depends on SGI_IP22 && SCSI
286 If you have a Western Digital WD93 SCSI controller on
287 an SGI MIPS system, say Y. Otherwise, say N.
290 tristate "DEC NCR53C94 Scsi Driver"
291 depends on MACH_DECSTATION && SCSI && TC
293 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
294 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
297 tristate "DEC SII Scsi Driver"
298 depends on MACH_DECSTATION && SCSI && 32BIT
300 config BLK_DEV_3W_XXXX_RAID
301 tristate "3ware 5/6/7/8xxx ATA-RAID support"
302 depends on PCI && SCSI
304 3ware is the only hardware ATA-Raid product in Linux to date.
305 This card is 2,4, or 8 channel master mode support only.
306 SCSI support required!!!
308 <http://www.3ware.com/>
310 Please read the comments at the top of
311 <file:drivers/scsi/3w-xxxx.c>.
314 tristate "3ware 9xxx SATA-RAID support"
315 depends on PCI && SCSI
317 This driver supports the 9000 series 3ware SATA-RAID cards.
319 <http://www.amcc.com>
321 Please read the comments at the top of
322 <file:drivers/scsi/3w-9xxx.c>.
324 config SCSI_7000FASST
325 tristate "7000FASST SCSI support"
326 depends on ISA && SCSI && ISA_DMA_API
328 This driver supports the Western Digital 7000 SCSI host adapter
329 family. Some information is in the source:
330 <file:drivers/scsi/wd7000.c>.
332 To compile this driver as a module, choose M here: the
333 module will be called wd7000.
336 tristate "ACARD SCSI support"
337 depends on PCI && SCSI
339 This driver supports the ACARD SCSI host adapter.
340 Support Chip <ATP870 ATP876 ATP880 ATP885>
341 To compile this driver as a module, choose M here: the
342 module will be called atp870u.
345 tristate "Adaptec AHA152X/2825 support"
346 depends on ISA && SCSI && !64BIT
347 select SCSI_SPI_ATTRS
349 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
350 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
351 must be manually specified in this case.
353 It is explained in section 3.3 of the SCSI-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>. You might also want to
355 read the file <file:Documentation/scsi/aha152x.txt>.
357 To compile this driver as a module, choose M here: the
358 module will be called aha152x.
361 tristate "Adaptec AHA1542 support"
362 depends on ISA && SCSI && ISA_DMA_API
364 This is support for a SCSI host adapter. It is explained in section
365 3.4 of the SCSI-HOWTO, available from
366 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
367 purchased by Adaptec, and some former Trantor products are being
368 sold under the Adaptec name. If it doesn't work out of the box, you
369 may have to change some settings in <file:drivers/scsi/aha1542.h>.
371 To compile this driver as a module, choose M here: the
372 module will be called aha1542.
375 tristate "Adaptec AHA1740 support"
376 depends on EISA && SCSI
378 This is support for a SCSI host adapter. It is explained in section
379 3.5 of the SCSI-HOWTO, available from
380 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
381 of the box, you may have to change some settings in
382 <file:drivers/scsi/aha1740.h>.
384 To compile this driver as a module, choose M here: the
385 module will be called aha1740.
388 tristate "Adaptec AACRAID support"
389 depends on SCSI && PCI
391 This driver supports a variety of Dell, HP, Adaptec, IBM and
392 ICP storage products. For a list of supported products, refer
393 to <file:Documentation/scsi/aacraid.txt>.
395 To compile this driver as a module, choose M here: the module
396 will be called aacraid.
399 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
401 config SCSI_AIC7XXX_OLD
402 tristate "Adaptec AIC7xxx support (old driver)"
403 depends on (ISA || EISA || PCI ) && SCSI
405 WARNING This driver is an older aic7xxx driver and is no longer
406 under active development. Adaptec, Inc. is writing a new driver to
407 take the place of this one, and it is recommended that whenever
408 possible, people should use the new Adaptec written driver instead
409 of this one. This driver will eventually be phased out entirely.
411 This is support for the various aic7xxx based Adaptec SCSI
412 controllers. These include the 274x EISA cards; 284x VLB cards;
413 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
414 motherboard based SCSI controllers from Adaptec. It does not support
415 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
416 support them. It does not support the 2920 cards from Adaptec that
417 use the Future Domain SCSI controller chip. For those cards, you
418 need the "Future Domain 16xx SCSI support" driver.
420 In general, if the controller is based on an Adaptec SCSI controller
421 chip from the aic777x series or the aic78xx series, this driver
422 should work. The only exception is the 7810 which is specifically
423 not supported (that's the RAID controller chip on the AAA-13x
426 Note that the AHA2920 SCSI host adapter is *not* supported by this
427 driver; choose "Future Domain 16xx SCSI support" instead if you have
430 Information on the configuration options for this controller can be
431 found by checking the help file for each of the available
432 configuration options. You should read
433 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
434 contacting the maintainer with any questions. The SCSI-HOWTO,
435 available from <http://www.tldp.org/docs.html#howto>, can also
438 To compile this driver as a module, choose M here: the
439 module will be called aic7xxx_old.
441 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
442 source "drivers/scsi/aic94xx/Kconfig"
444 # All the I2O code and drivers do not seem to be 64bit safe.
446 tristate "Adaptec I2O RAID support "
447 depends on !64BIT && SCSI && PCI
449 This driver supports all of Adaptec's I2O based RAID controllers as
450 well as the DPT SmartRaid V cards. This is an Adaptec maintained
451 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
453 To compile this driver as a module, choose M here: the
454 module will be called dpt_i2o.
457 tristate "AdvanSys SCSI support"
459 depends on ISA || EISA || PCI
460 depends on BROKEN || X86_32
462 This is a driver for all SCSI host adapters manufactured by
463 AdvanSys. It is documented in the kernel source in
464 <file:drivers/scsi/advansys.c>.
466 To compile this driver as a module, choose M here: the
467 module will be called advansys.
470 tristate "Always IN2000 SCSI support"
471 depends on ISA && SCSI
473 This is support for an ISA bus SCSI host adapter. You'll find more
474 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
475 out of the box, you may have to change the jumpers for IRQ or
478 To compile this driver as a module, choose M here: the
479 module will be called in2000.
482 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
483 depends on PCI && SCSI
485 This driver supports all of ARECA's SATA RAID controller cards.
486 This is an ARECA-maintained driver by Erich Chen.
487 If you have any problems, please mail to: < erich@areca.com.tw >
488 Areca supports Linux RAID config tools.
490 < http://www.areca.com.tw >
492 To compile this driver as a module, choose M here: the
493 module will be called arcmsr (modprobe arcmsr).
495 source "drivers/scsi/megaraid/Kconfig.megaraid"
498 tristate "Serial ATA (SATA) support"
501 This driver family supports Serial ATA host controllers
506 config SCSI_SATA_AHCI
507 tristate "AHCI SATA support"
508 depends on SCSI_SATA && PCI
510 This option enables support for AHCI Serial ATA.
515 tristate "ServerWorks Frodo / Apple K2 SATA support"
516 depends on SCSI_SATA && PCI
518 This option enables support for Broadcom/Serverworks/Apple K2
524 tristate "Intel PIIX/ICH SATA support"
525 depends on SCSI_SATA && PCI
527 This option enables support for ICH5/6/7/8 Serial ATA.
528 If PATA support was enabled previously, this enables
529 support for select Intel PIIX/ICH PATA host controllers.
534 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
535 depends on SCSI_SATA && PCI && EXPERIMENTAL
537 This option enables support for the Marvell Serial ATA family.
538 Currently supports 88SX[56]0[48][01] chips.
543 tristate "NVIDIA SATA support"
544 depends on SCSI_SATA && PCI && EXPERIMENTAL
546 This option enables support for NVIDIA Serial ATA.
551 tristate "Pacific Digital ADMA support"
552 depends on SCSI_SATA && PCI
554 This option enables support for Pacific Digital ADMA controllers
559 tristate "HighPoint RocketRAID 3xxx Controller support"
560 depends on SCSI && PCI
562 This option enables support for HighPoint RocketRAID 3xxx
565 To compile this driver as a module, choose M here; the module
566 will be called hptiop. If unsure, say N.
568 config SCSI_SATA_QSTOR
569 tristate "Pacific Digital SATA QStor support"
570 depends on SCSI_SATA && PCI
572 This option enables support for Pacific Digital Serial ATA QStor.
576 config SCSI_SATA_PROMISE
577 tristate "Promise SATA TX2/TX4 support"
578 depends on SCSI_SATA && PCI
580 This option enables support for Promise Serial ATA TX2/TX4.
585 tristate "Promise SATA SX4 support"
586 depends on SCSI_SATA && PCI && EXPERIMENTAL
588 This option enables support for Promise Serial ATA SX4.
593 tristate "Silicon Image SATA support"
594 depends on SCSI_SATA && PCI && EXPERIMENTAL
596 This option enables support for Silicon Image Serial ATA.
600 config SCSI_SATA_SIL24
601 tristate "Silicon Image 3124/3132 SATA support"
602 depends on SCSI_SATA && PCI && EXPERIMENTAL
604 This option enables support for Silicon Image 3124/3132 Serial ATA.
609 tristate "SiS 964/180 SATA support"
610 depends on SCSI_SATA && PCI && EXPERIMENTAL
612 This option enables support for SiS Serial ATA 964/180.
617 tristate "ULi Electronics SATA support"
618 depends on SCSI_SATA && PCI && EXPERIMENTAL
620 This option enables support for ULi Electronics SATA.
625 tristate "VIA SATA support"
626 depends on SCSI_SATA && PCI
628 This option enables support for VIA Serial ATA.
632 config SCSI_SATA_VITESSE
633 tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
634 depends on SCSI_SATA && PCI
636 This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
640 config SCSI_SATA_INTEL_COMBINED
642 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
646 tristate "BusLogic SCSI support"
647 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
649 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
650 Adapters. Consult the SCSI-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>, and the files
652 <file:Documentation/scsi/BusLogic.txt> and
653 <file:Documentation/scsi/FlashPoint.txt> for more information.
655 To compile this driver as a module, choose M here: the
656 module will be called BusLogic.
658 config SCSI_OMIT_FLASHPOINT
659 bool "Omit FlashPoint support"
660 depends on SCSI_BUSLOGIC
662 This option allows you to omit the FlashPoint support from the
663 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
664 substantial, so users of MultiMaster Host Adapters may wish to omit
668 tristate "DMX3191D SCSI support"
669 depends on PCI && SCSI
670 select SCSI_SPI_ATTRS
672 This is support for Domex DMX3191D SCSI Host Adapters.
674 To compile this driver as a module, choose M here: the
675 module will be called dmx3191d.
678 tristate "DTC3180/3280 SCSI support"
679 depends on ISA && SCSI
680 select SCSI_SPI_ATTRS
682 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
683 the SCSI-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>, and the file
685 <file:Documentation/scsi/dtc3x80.txt>.
687 To compile this driver as a module, choose M here: the
688 module will be called dtc.
691 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
692 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
694 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
695 ISA and all EISA I/O addresses are probed looking for the "EATA"
696 signature. The addresses of all the PCI SCSI controllers reported
697 by the PCI subsystem are probed as well.
699 You want to read the start of <file:drivers/scsi/eata.c> and the
700 SCSI-HOWTO, available from
701 <http://www.tldp.org/docs.html#howto>.
703 To compile this driver as a module, choose M here: the
704 module will be called eata.
706 config SCSI_EATA_TAGGED_QUEUE
707 bool "enable tagged command queueing"
710 This is a feature of SCSI-2 which improves performance: the host
711 adapter can send several SCSI commands to a device's queue even if
712 previous commands haven't finished yet.
713 This is equivalent to the "eata=tc:y" boot option.
715 config SCSI_EATA_LINKED_COMMANDS
716 bool "enable elevator sorting"
719 This option enables elevator sorting for all probed SCSI disks and
720 CD-ROMs. It definitely reduces the average seek distance when doing
721 random seeks, but this does not necessarily result in a noticeable
722 performance improvement: your mileage may vary...
723 This is equivalent to the "eata=lc:y" boot option.
725 config SCSI_EATA_MAX_TAGS
726 int "maximum number of queued commands"
730 This specifies how many SCSI commands can be maximally queued for
731 each probed SCSI device. You should reduce the default value of 16
732 only if you have disks with buggy or limited tagged command support.
733 Minimum is 2 and maximum is 62. This value is also the window size
734 used by the elevator sorting option above. The effective value used
735 by the driver for each probed SCSI device is reported at boot time.
736 This is equivalent to the "eata=mq:8" boot option.
739 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
740 depends on (ISA || EISA || PCI) && SCSI && BROKEN
742 This driver supports all EATA-PIO protocol compliant SCSI Host
743 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
744 host adapters could also use this driver but are discouraged from
745 doing so, since this driver only supports hard disks and lacks
746 numerous features. You might want to have a look at the SCSI-HOWTO,
747 available from <http://www.tldp.org/docs.html#howto>.
749 To compile this driver as a module, choose M here: the
750 module will be called eata_pio.
752 config SCSI_FUTURE_DOMAIN
753 tristate "Future Domain 16xx SCSI/AHA-2920A support"
754 depends on (ISA || PCI) && SCSI
756 This is support for Future Domain's 16-bit SCSI host adapters
757 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
758 other adapters based on the Future Domain chipsets (Quantum
759 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
760 It is explained in section 3.7 of the SCSI-HOWTO, available from
761 <http://www.tldp.org/docs.html#howto>.
763 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
764 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
765 controller support"). This Future Domain driver works with the older
766 Adaptec AHA-2920A boards with a Future Domain chip on them.
768 To compile this driver as a module, choose M here: the
769 module will be called fdomain.
772 tristate "Future Domain MCS-600/700 SCSI support"
773 depends on MCA_LEGACY && SCSI
775 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
776 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
777 is identical to the MCS 700 and hence also supported by this driver.
778 This driver also supports the Reply SB16/SCSI card (the SCSI part).
779 It supports multiple adapters in the same system.
781 To compile this driver as a module, choose M here: the
782 module will be called fd_mcs.
785 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
786 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
788 Formerly called GDT SCSI Disk Array Controller Support.
790 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
791 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
792 in the kernel source in <file:drivers/scsi/gdth.c> and
793 <file:drivers/scsi/gdth.h.>
795 To compile this driver as a module, choose M here: the
796 module will be called gdth.
798 config SCSI_GENERIC_NCR5380
799 tristate "Generic NCR5380/53c400 SCSI PIO support"
800 depends on ISA && SCSI
801 select SCSI_SPI_ATTRS
803 This is a driver for the old NCR 53c80 series of SCSI controllers
804 on boards using PIO. Most boards such as the Trantor T130 fit this
805 category, along with a large number of ISA 8bit controllers shipped
806 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
807 you should select the specific driver for that card rather than
808 generic 5380 support.
810 It is explained in section 3.8 of the SCSI-HOWTO, available from
811 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
812 of the box, you may have to change some settings in
813 <file:drivers/scsi/g_NCR5380.h>.
815 To compile this driver as a module, choose M here: the
816 module will be called g_NCR5380.
818 config SCSI_GENERIC_NCR5380_MMIO
819 tristate "Generic NCR5380/53c400 SCSI MMIO support"
820 depends on ISA && SCSI
821 select SCSI_SPI_ATTRS
823 This is a driver for the old NCR 53c80 series of SCSI controllers
824 on boards using memory mapped I/O.
825 It is explained in section 3.8 of the SCSI-HOWTO, available from
826 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
827 of the box, you may have to change some settings in
828 <file:drivers/scsi/g_NCR5380.h>.
830 To compile this driver as a module, choose M here: the
831 module will be called g_NCR5380_mmio.
833 config SCSI_GENERIC_NCR53C400
834 bool "Enable NCR53c400 extensions"
835 depends on SCSI_GENERIC_NCR5380
837 This enables certain optimizations for the NCR53c400 SCSI cards.
838 You might as well try it out. Note that this driver will only probe
839 for the Trantor T130B in its default configuration; you might have
840 to pass a command line option to the kernel at boot time if it does
841 not detect your card. See the file
842 <file:Documentation/scsi/g_NCR5380.txt> for details.
845 tristate "IBMMCA SCSI support"
846 depends on MCA_LEGACY && SCSI
848 This is support for the IBM SCSI adapter found in many of the PS/2
849 series computers. These machines have an MCA bus, so you need to
850 answer Y to "MCA support" as well and read
851 <file:Documentation/mca.txt>.
853 If the adapter isn't found during boot (a common problem for models
854 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
855 option, where <pun> is the id of the SCSI subsystem (usually 7, but
856 if that doesn't work check your reference diskette). Owners of
857 model 95 with a LED-matrix-display can in addition activate some
858 activity info like under OS/2, but more informative, by setting
859 'ibmmcascsi=display' as an additional kernel parameter. Try "man
860 bootparam" or see the documentation of your boot loader about how to
861 pass options to the kernel.
863 To compile this driver as a module, choose M here: the
864 module will be called ibmmca.
866 config IBMMCA_SCSI_ORDER_STANDARD
867 bool "Standard SCSI-order"
868 depends on SCSI_IBMMCA
870 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
871 are assigned to the drive letters, starting with the lowest SCSI-id
872 (physical number -- pun) to be drive C:, as seen from DOS and
873 similar operating systems. When looking into papers describing the
874 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
875 The SCSI-standard follows a hardware-hierarchy which says that id 7
876 has the highest priority and id 0 the lowest. Therefore, the host
877 adapters are still today everywhere placed as SCSI-id 7 by default.
878 In the SCSI-standard, the drive letters express the priority of the
879 disk. C: should be the hard disk, or a partition on it, with the
880 highest priority. This must therefore be the disk with the highest
881 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
882 original definition of the SCSI-standard as also industrial- and
883 process-control-machines, like VME-CPUs running under realtime-OSes
884 (e.g. LynxOS, OS9) do.
886 If you like to run Linux on your MCA-machine with the same
887 assignment of hard disks as seen from e.g. DOS or OS/2 on your
888 machine, which is in addition conformant to the SCSI-standard, you
889 must say Y here. This is also necessary for MCA-Linux users who want
890 to keep downward compatibility to older releases of the
891 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
894 If you like to have the lowest SCSI-id assigned as drive C:, as
895 modern SCSI-BIOSes do, which does not conform to the standard, but
896 is widespread and common in the PC-world of today, you must say N
897 here. If unsure, say Y.
899 config IBMMCA_SCSI_DEV_RESET
900 bool "Reset SCSI-devices at boottime"
901 depends on SCSI_IBMMCA
903 By default, SCSI-devices are reset when the machine is powered on.
904 However, some devices exist, like special-control-devices,
905 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
906 not reset when switched on. If you say Y here, each device connected
907 to your SCSI-bus will be issued a reset-command after it has been
908 probed, while the kernel is booting. This may cause problems with
909 more modern devices, like hard disks, which do not appreciate these
910 reset commands, and can cause your system to hang. So say Y only if
911 you know that one of your older devices needs it; N is the safe
915 tristate "IBM ServeRAID support"
916 depends on PCI && SCSI
918 This is support for the IBM ServeRAID hardware RAID controllers.
919 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
920 for more information. If this driver does not work correctly
921 without modification please contact the author by email at
922 <ipslinux@adaptec.com>.
924 To compile this driver as a module, choose M here: the
925 module will be called ips.
928 tristate "IBM Virtual SCSI support"
929 depends on PPC_PSERIES || PPC_ISERIES
931 This is the IBM POWER Virtual SCSI Client
933 To compile this driver as a module, choose M here: the
934 module will be called ibmvscsic.
937 tristate "Initio 9100U(W) support"
938 depends on PCI && SCSI
940 This is support for the Initio 91XXU(W) SCSI host adapter. Please
941 read the SCSI-HOWTO, available from
942 <http://www.tldp.org/docs.html#howto>.
944 To compile this driver as a module, choose M here: the
945 module will be called initio.
948 tristate "Initio INI-A100U2W support"
949 depends on PCI && SCSI
951 This is support for the Initio INI-A100U2W SCSI host adapter.
952 Please read the SCSI-HOWTO, available from
953 <http://www.tldp.org/docs.html#howto>.
955 To compile this driver as a module, choose M here: the
956 module will be called a100u2w.
959 tristate "IOMEGA parallel port (ppa - older drives)"
960 depends on SCSI && PARPORT_PC
962 This driver supports older versions of IOMEGA's parallel port ZIP
963 drive (a 100 MB removable media device).
965 Note that you can say N here if you have the SCSI version of the ZIP
966 drive: it will be supported automatically if you said Y to the
967 generic "SCSI disk support", above.
969 If you have the ZIP Plus drive or a more recent parallel port ZIP
970 drive (if the supplied cable with the drive is labeled "AutoDetect")
971 then you should say N here and Y to "IOMEGA parallel port (imm -
972 newer drives)", below.
974 For more information about this driver and how to use it you should
975 read the file <file:Documentation/scsi/ppa.txt>. You should also read
976 the SCSI-HOWTO, which is available from
977 <http://www.tldp.org/docs.html#howto>. If you use this driver,
978 you will still be able to use the parallel port for other tasks,
979 such as a printer; it is safe to compile both drivers into the
982 To compile this driver as a module, choose M here: the
983 module will be called ppa.
986 tristate "IOMEGA parallel port (imm - newer drives)"
987 depends on SCSI && PARPORT_PC
989 This driver supports newer versions of IOMEGA's parallel port ZIP
990 drive (a 100 MB removable media device).
992 Note that you can say N here if you have the SCSI version of the ZIP
993 drive: it will be supported automatically if you said Y to the
994 generic "SCSI disk support", above.
996 If you have the ZIP Plus drive or a more recent parallel port ZIP
997 drive (if the supplied cable with the drive is labeled "AutoDetect")
998 then you should say Y here; if you have an older ZIP drive, say N
999 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
1001 For more information about this driver and how to use it you should
1002 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1003 the SCSI-HOWTO, which is available from
1004 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1005 you will still be able to use the parallel port for other tasks,
1006 such as a printer; it is safe to compile both drivers into the
1009 To compile this driver as a module, choose M here: the
1010 module will be called imm.
1012 config SCSI_IZIP_EPP16
1013 bool "ppa/imm option - Use slow (but safe) EPP-16"
1014 depends on SCSI_PPA || SCSI_IMM
1016 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1017 allows them to act as expansion buses that can handle up to 64
1020 Some parallel port chipsets are slower than their motherboard, and
1021 so we have to control the state of the chipset's FIFO queue every
1022 now and then to avoid data loss. This will be done if you say Y
1025 Generally, saying Y is the safe option and slows things down a bit.
1027 config SCSI_IZIP_SLOW_CTR
1028 bool "ppa/imm option - Assume slow parport control register"
1029 depends on SCSI_PPA || SCSI_IMM
1031 Some parallel ports are known to have excessive delays between
1032 changing the parallel port control register and good data being
1033 available on the parallel port data/status register. This option
1034 forces a small delay (1.0 usec to be exact) after changing the
1035 control register to let things settle out. Enabling this option may
1036 result in a big drop in performance but some very old parallel ports
1037 (found in 386 vintage machines) will not work properly.
1039 Generally, saying N is fine.
1041 config SCSI_NCR53C406A
1042 tristate "NCR53c406a SCSI support"
1043 depends on ISA && SCSI
1045 This is support for the NCR53c406a SCSI host adapter. For user
1046 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1047 in the kernel source. Also read the SCSI-HOWTO, available from
1048 <http://www.tldp.org/docs.html#howto>.
1050 To compile this driver as a module, choose M here: the
1051 module will be called NCR53c406.
1053 config SCSI_NCR_D700
1054 tristate "NCR Dual 700 MCA SCSI support"
1055 depends on MCA && SCSI
1056 select SCSI_SPI_ATTRS
1058 This is a driver for the MicroChannel Dual 700 card produced by
1059 NCR and commonly used in 345x/35xx/4100 class machines. It always
1060 tries to negotiate sync and uses tag command queueing.
1062 Unless you have an NCR manufactured machine, the chances are that
1063 you do not have this SCSI card, so say N.
1066 tristate "HP Lasi SCSI support for 53c700/710"
1067 depends on GSC && SCSI
1068 select SCSI_SPI_ATTRS
1070 This is a driver for the SCSI controller in the Lasi chip found in
1071 many PA-RISC workstations & servers. If you do not know whether you
1072 have a Lasi chip, it is safe to say "Y" here.
1074 config 53C700_LE_ON_BE
1076 depends on SCSI_LASI700
1080 tristate "Promise SuperTrak EX Series support"
1081 depends on PCI && SCSI
1083 This driver supports Promise SuperTrak EX8350/8300/16350/16300
1084 Storage controllers.
1086 config SCSI_SYM53C8XX_2
1087 tristate "SYM53C8XX Version 2 SCSI support"
1088 depends on PCI && SCSI
1089 select SCSI_SPI_ATTRS
1091 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1092 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1093 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1094 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1095 controllers; you need to use the Fusion MPT driver for that.
1097 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1100 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1101 int "DMA addressing mode"
1102 depends on SCSI_SYM53C8XX_2
1105 This option only applies to PCI-SCSI chips that are PCI DAC
1106 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1108 When set to 0, the driver will program the chip to only perform
1109 32-bit DMA. When set to 1, the chip will be able to perform DMA
1110 to addresses up to 1TB. When set to 2, the driver supports the
1111 full 64-bit DMA address range, but can only address 16 segments
1112 of 4 GB each. This limits the total addressable range to 64 GB.
1114 Most machines with less than 4GB of memory should use a setting
1115 of 0 for best performance. If your machine has 4GB of memory
1116 or more, you should set this option to 1 (the default).
1118 The still experimental value 2 (64 bit DMA addressing with 16
1119 x 4GB segments limitation) can be used on systems that require
1120 PCI address bits past bit 39 to be set for the addressing of
1121 memory using PCI DAC cycles.
1123 config SCSI_SYM53C8XX_DEFAULT_TAGS
1124 int "Default tagged command queue depth"
1125 depends on SCSI_SYM53C8XX_2
1128 This is the default value of the command queue depth the
1129 driver will announce to the generic SCSI layer for devices
1130 that support tagged command queueing. This value can be changed
1131 from the boot command line. This is a soft limit that cannot
1132 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1134 config SCSI_SYM53C8XX_MAX_TAGS
1135 int "Maximum number of queued commands"
1136 depends on SCSI_SYM53C8XX_2
1139 This option allows you to specify the maximum number of commands
1140 that can be queued to any device, when tagged command queuing is
1141 possible. The driver supports up to 256 queued commands per device.
1142 This value is used as a compiled-in hard limit.
1144 config SCSI_SYM53C8XX_MMIO
1145 bool "Use memory mapped IO"
1146 depends on SCSI_SYM53C8XX_2
1149 Memory mapped IO is faster than Port IO. Most people should
1150 answer Y here, but some machines may have problems. If you have
1151 to answer N here, please report the problem to the maintainer.
1154 tristate "IBM Power Linux RAID adapter support"
1155 depends on PCI && SCSI
1158 This driver supports the IBM Power Linux family RAID adapters.
1159 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1160 as IBM iSeries 5702, 5703, 5709, and 570A.
1162 config SCSI_IPR_TRACE
1163 bool "enable driver internal trace"
1166 If you say Y here, the driver will trace all commands issued
1167 to the adapter. Performance impact is minimal. Trace can be
1168 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1170 config SCSI_IPR_DUMP
1171 bool "enable adapter dump support"
1174 If you say Y here, the driver will support adapter crash dump.
1175 If you enable this support, the iprdump daemon can be used
1176 to capture adapter failure analysis information.
1179 tristate "Zalon SCSI support"
1180 depends on GSC && SCSI
1181 select SCSI_SPI_ATTRS
1183 The Zalon is a GSC/HSC bus interface chip that sits between the
1184 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1185 C110, J200, J210 and some D, K & R-class machines. It's also
1186 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1187 Say Y here if you have one of these machines or cards.
1189 config SCSI_NCR_Q720
1190 tristate "NCR Quad 720 MCA SCSI support"
1191 depends on MCA && SCSI
1192 select SCSI_SPI_ATTRS
1194 This is a driver for the MicroChannel Quad 720 card produced by
1195 NCR and commonly used in 345x/35xx/4100 class machines. It always
1196 tries to negotiate sync and uses tag command queueing.
1198 Unless you have an NCR manufactured machine, the chances are that
1199 you do not have this SCSI card, so say N.
1201 config SCSI_NCR53C8XX_DEFAULT_TAGS
1202 int "default tagged command queue depth"
1203 depends on SCSI_ZALON || SCSI_NCR_Q720
1206 "Tagged command queuing" is a feature of SCSI-2 which improves
1207 performance: the host adapter can send several SCSI commands to a
1208 device's queue even if previous commands haven't finished yet.
1209 Because the device is intelligent, it can optimize its operations
1210 (like head positioning) based on its own request queue. Some SCSI
1211 devices don't implement this properly; if you want to disable this
1212 feature, enter 0 or 1 here (it doesn't matter which).
1214 The default value is 8 and should be supported by most hard disks.
1215 This value can be overridden from the boot command line using the
1216 'tags' option as follows (example):
1217 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1218 4, set queue depth to 16 for target 2 and target 3 on controller 0
1219 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1221 The normal answer therefore is to go with the default 8 and to use
1222 a boot command line option for devices that need to use a different
1223 command queue depth.
1225 There is no safe option other than using good SCSI devices.
1227 config SCSI_NCR53C8XX_MAX_TAGS
1228 int "maximum number of queued commands"
1229 depends on SCSI_ZALON || SCSI_NCR_Q720
1232 This option allows you to specify the maximum number of commands
1233 that can be queued to any device, when tagged command queuing is
1234 possible. The default value is 32. Minimum is 2, maximum is 64.
1235 Modern hard disks are able to support 64 tags and even more, but
1236 do not seem to be faster when more than 32 tags are being used.
1238 So, the normal answer here is to go with the default value 32 unless
1239 you are using very large hard disks with large cache (>= 1 MB) that
1240 are able to take advantage of more than 32 tagged commands.
1242 There is no safe option and the default answer is recommended.
1244 config SCSI_NCR53C8XX_SYNC
1245 int "synchronous transfers frequency in MHz"
1246 depends on SCSI_ZALON || SCSI_NCR_Q720
1249 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1250 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1251 are respectively the maximum data transfer rates in mega-transfers
1252 per second for each class. For example, a FAST-20 Wide 16 device is
1253 able to transfer data at 20 million 16 bit packets per second for a
1254 total rate of 40 MB/s.
1256 You may specify 0 if you want to only use asynchronous data
1257 transfers. This is the safest and slowest option. Otherwise, specify
1258 a value between 5 and 80, depending on the capability of your SCSI
1259 controller. The higher the number, the faster the data transfer.
1260 Note that 80 should normally be ok since the driver decreases the
1261 value automatically according to the controller's capabilities.
1263 Your answer to this question is ignored for controllers with NVRAM,
1264 since the driver will get this information from the user set-up. It
1265 also can be overridden using a boot setup option, as follows
1266 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1267 for FAST-20 synchronous data transfer (20 mega-transfers per
1270 The normal answer therefore is not to go with the default but to
1271 select the maximum value 80 allowing the driver to use the maximum
1272 value supported by each controller. If this causes problems with
1273 your SCSI devices, you should come back and decrease the value.
1275 There is no safe option other than using good cabling, right
1276 terminations and SCSI conformant devices.
1278 config SCSI_NCR53C8XX_PROFILE
1279 bool "enable profiling"
1280 depends on SCSI_ZALON || SCSI_NCR_Q720
1282 This option allows you to enable profiling information gathering.
1283 These statistics are not very accurate due to the low frequency
1284 of the kernel clock (100 Hz on i386) and have performance impact
1285 on systems that use very fast devices.
1287 The normal answer therefore is N.
1289 config SCSI_NCR53C8XX_NO_DISCONNECT
1290 bool "not allow targets to disconnect"
1291 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1293 This option is only provided for safety if you suspect some SCSI
1294 device of yours to not support properly the target-disconnect
1295 feature. In that case, you would say Y here. In general however, to
1296 not allow targets to disconnect is not reasonable if there is more
1297 than 1 device on a SCSI bus. The normal answer therefore is N.
1299 config SCSI_MCA_53C9X
1300 tristate "NCR MCA 53C9x SCSI support"
1301 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1303 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1304 controller based on the NCR 53C94. This driver will allow use of
1305 the controller on the 3550, and very possibly others.
1307 To compile this driver as a module, choose M here: the
1308 module will be called mca_53c9x.
1311 tristate "PAS16 SCSI support"
1312 depends on ISA && SCSI
1313 select SCSI_SPI_ATTRS
1315 This is support for a SCSI host adapter. It is explained in section
1316 3.10 of the SCSI-HOWTO, available from
1317 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1318 of the box, you may have to change some settings in
1319 <file:drivers/scsi/pas16.h>.
1321 To compile this driver as a module, choose M here: the
1322 module will be called pas16.
1325 tristate "PSI240i support"
1326 depends on ISA && SCSI
1328 This is support for the PSI240i EIDE interface card which acts as a
1329 SCSI host adapter. Please read the SCSI-HOWTO, available from
1330 <http://www.tldp.org/docs.html#howto>.
1332 To compile this driver as a module, choose M here: the
1333 module will be called psi240i.
1335 config SCSI_QLOGIC_FAS
1336 tristate "Qlogic FAS SCSI support"
1337 depends on ISA && SCSI
1339 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1340 FastSCSI! cards as well as any other card based on the FASXX chip
1341 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1343 This driver does NOT support the PCI versions of these cards. The
1344 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1345 SCSI support"), below.
1347 Information about this driver is contained in
1348 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1349 SCSI-HOWTO, available from
1350 <http://www.tldp.org/docs.html#howto>.
1352 To compile this driver as a module, choose M here: the
1353 module will be called qlogicfas.
1355 config SCSI_QLOGIC_FC_FIRMWARE
1356 bool "Include loadable firmware in driver"
1357 depends on SCSI_QLOGIC_FC
1359 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1360 expanded LUN addressing and FcTape (FCP-2) support, in the
1361 qlogicfc driver. This is required on some platforms.
1363 config SCSI_QLOGIC_1280
1364 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1365 depends on PCI && SCSI
1367 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1369 To compile this driver as a module, choose M here: the
1370 module will be called qla1280.
1372 config SCSI_QLOGICPTI
1373 tristate "PTI Qlogic, ISP Driver"
1374 depends on SBUS && SCSI
1376 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1377 controllers are known under Solaris as qpti and in the openprom as
1378 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1379 driven by a different driver.
1381 To compile this driver as a module, choose M here: the
1382 module will be called qlogicpti.
1384 source "drivers/scsi/qla2xxx/Kconfig"
1387 tristate "Emulex LightPulse Fibre Channel Support"
1388 depends on PCI && SCSI
1389 select SCSI_FC_ATTRS
1391 This lpfc driver supports the Emulex LightPulse
1392 Family of Fibre Channel PCI host adapters.
1395 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1396 depends on X86 && ISA && SCSI && BROKEN
1398 These are 8-bit SCSI controllers; the ST-01 is also supported by
1399 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1400 available from <http://www.tldp.org/docs.html#howto>. If it
1401 doesn't work out of the box, you may have to change some settings in
1402 <file:drivers/scsi/seagate.h>.
1404 To compile this driver as a module, choose M here: the
1405 module will be called seagate.
1407 # definitely looks not 64bit safe:
1409 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1410 depends on (EISA || MCA) && SCSI
1411 select SCSI_SPI_ATTRS
1413 This driver for NCR53c710 based SCSI host adapters.
1415 It currently supports Compaq EISA cards and NCR MCA cards
1417 config 53C700_IO_MAPPED
1419 depends on SCSI_SIM710
1422 config SCSI_SYM53C416
1423 tristate "Symbios 53c416 SCSI support"
1424 depends on ISA && SCSI
1426 This is support for the sym53c416 SCSI host adapter, the SCSI
1427 adapter that comes with some HP scanners. This driver requires that
1428 the sym53c416 is configured first using some sort of PnP
1429 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1430 are using isapnp then you need to compile this driver as a module
1431 and then load it using insmod after isapnp has run. The parameters
1432 of the configured card(s) should be passed to the driver. The format
1435 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1437 To compile this driver as a module, choose M here: the
1438 module will be called sym53c416.
1441 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1442 depends on PCI && SCSI && EXPERIMENTAL
1444 This driver supports PCI SCSI host adapters based on the ASIC
1445 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1447 This driver works, but is still in experimental status. So better
1448 have a bootable disk and a backup in case of emergency.
1450 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1452 To compile this driver as a module, choose M here: the
1453 module will be called dc395x.
1456 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1457 depends on PCI && SCSI
1459 This driver supports PCI SCSI host adapters based on the Am53C974A
1460 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1461 PCscsi/PCnet (Am53/79C974) solutions.
1463 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1465 Note that this driver does NOT support Tekram DC390W/U/F, which are
1466 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1468 To compile this driver as a module, choose M here: the
1469 module will be called tmscsim.
1472 tristate "Trantor T128/T128F/T228 SCSI support"
1473 depends on ISA && SCSI
1474 select SCSI_SPI_ATTRS
1476 This is support for a SCSI host adapter. It is explained in section
1477 3.11 of the SCSI-HOWTO, available from
1478 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1479 of the box, you may have to change some settings in
1480 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1481 Adaptec, and some former Trantor products are being sold under the
1484 To compile this driver as a module, choose M here: the
1485 module will be called t128.
1488 tristate "UltraStor 14F/34F support"
1489 depends on ISA && SCSI && ISA_DMA_API
1491 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1492 The source at <file:drivers/scsi/u14-34f.c> contains some
1493 information about this hardware. If the driver doesn't work out of
1494 the box, you may have to change some settings in
1495 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1496 <http://www.tldp.org/docs.html#howto>. Note that there is also
1497 another driver for the same hardware: "UltraStor SCSI support",
1498 below. You should say Y to both only if you want 24F support as
1501 To compile this driver as a module, choose M here: the
1502 module will be called u14-34f.
1504 config SCSI_U14_34F_TAGGED_QUEUE
1505 bool "enable tagged command queueing"
1506 depends on SCSI_U14_34F
1508 This is a feature of SCSI-2 which improves performance: the host
1509 adapter can send several SCSI commands to a device's queue even if
1510 previous commands haven't finished yet.
1511 This is equivalent to the "u14-34f=tc:y" boot option.
1513 config SCSI_U14_34F_LINKED_COMMANDS
1514 bool "enable elevator sorting"
1515 depends on SCSI_U14_34F
1517 This option enables elevator sorting for all probed SCSI disks and
1518 CD-ROMs. It definitely reduces the average seek distance when doing
1519 random seeks, but this does not necessarily result in a noticeable
1520 performance improvement: your mileage may vary...
1521 This is equivalent to the "u14-34f=lc:y" boot option.
1523 config SCSI_U14_34F_MAX_TAGS
1524 int "maximum number of queued commands"
1525 depends on SCSI_U14_34F
1528 This specifies how many SCSI commands can be maximally queued for
1529 each probed SCSI device. You should reduce the default value of 8
1530 only if you have disks with buggy or limited tagged command support.
1531 Minimum is 2 and maximum is 14. This value is also the window size
1532 used by the elevator sorting option above. The effective value used
1533 by the driver for each probed SCSI device is reported at boot time.
1534 This is equivalent to the "u14-34f=mq:8" boot option.
1536 config SCSI_ULTRASTOR
1537 tristate "UltraStor SCSI support"
1538 depends on X86 && ISA && SCSI
1540 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1541 adapter family. This driver is explained in section 3.12 of the
1542 SCSI-HOWTO, available from
1543 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1544 of the box, you may have to change some settings in
1545 <file:drivers/scsi/ultrastor.h>.
1547 Note that there is also another driver for the same hardware:
1548 "UltraStor 14F/34F support", above.
1550 To compile this driver as a module, choose M here: the
1551 module will be called ultrastor.
1554 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1555 depends on PCI && SCSI && !64BIT
1557 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1558 SCSI host adapter. Please read the SCSI-HOWTO, available from
1559 <http://www.tldp.org/docs.html#howto>.
1561 To compile this driver as a module, choose M here: the
1562 module will be called nsp32.
1565 tristate "SCSI debugging host simulator"
1568 This is a host adapter simulator that can simulate multiple hosts
1569 each with multiple dummy SCSI devices (disks). It defaults to one
1570 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1571 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1572 dummy disks are simulated, they share the same kernel RAM for
1573 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1574 information. This driver is primarily of use to those testing the
1575 SCSI and block subsystems. If unsure, say N.
1578 tristate "MESH (Power Mac internal SCSI) support"
1579 depends on PPC32 && PPC_PMAC && SCSI
1581 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1582 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1583 other Power Macintoshes do). Say Y to include support for this SCSI
1586 To compile this driver as a module, choose M here: the
1587 module will be called mesh.
1589 config SCSI_MESH_SYNC_RATE
1590 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1591 depends on SCSI_MESH
1594 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1595 drives a bus which is entirely internal to the machine (such as the
1596 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1597 operation at up to 10 MB/s. On machines where the SCSI bus
1598 controlled by the MESH can have external devices connected, it is
1599 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1600 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1601 to disable synchronous operation.
1603 config SCSI_MESH_RESET_DELAY_MS
1604 int "initial bus reset delay (ms) (0 = no reset)"
1605 depends on SCSI_MESH
1608 config SCSI_MAC53C94
1609 tristate "53C94 (Power Mac external SCSI) support"
1610 depends on PPC32 && PPC_PMAC && SCSI
1612 On Power Macintoshes (and clones) with two SCSI buses, the external
1613 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1614 machines which only have one SCSI bus, such as the 7200, also use
1615 the 53C94. Say Y to include support for the 53C94.
1617 To compile this driver as a module, choose M here: the
1618 module will be called mac53c94.
1620 source "drivers/scsi/arm/Kconfig"
1623 bool "MIPS JAZZ FAS216 SCSI support"
1624 depends on MACH_JAZZ && SCSI
1626 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1627 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1631 tristate "A3000 WD33C93A support"
1632 depends on AMIGA && SCSI
1634 If you have an Amiga 3000 and have SCSI devices connected to the
1635 built-in SCSI controller, say Y. Otherwise, say N.
1637 To compile this driver as a module, choose M here: the
1638 module will be called wd33c93.
1641 tristate "A2091/A590 WD33C93A support"
1642 depends on ZORRO && SCSI
1644 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1647 To compile this driver as a module, choose M here: the
1648 module will be called wd33c93.
1651 tristate "GVP Series II WD33C93A support"
1652 depends on ZORRO && SCSI
1654 If you have a Great Valley Products Series II SCSI controller,
1655 answer Y. Also say Y if you have a later model of GVP SCSI
1656 controller (such as the GVP A4008 or a Combo board). Otherwise,
1657 answer N. This driver does NOT work for the T-Rex series of
1658 accelerators from TekMagic and GVP-M.
1660 To compile this driver as a module, choose M here: the
1661 module will be called gvp11.
1663 config CYBERSTORM_SCSI
1664 tristate "CyberStorm SCSI support"
1665 depends on ZORRO && SCSI
1667 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1668 accelerator board and the optional Cyberstorm SCSI controller,
1669 answer Y. Otherwise, say N.
1671 config CYBERSTORMII_SCSI
1672 tristate "CyberStorm Mk II SCSI support"
1673 depends on ZORRO && SCSI
1675 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1676 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1680 tristate "Blizzard 2060 SCSI support"
1681 depends on ZORRO && SCSI
1683 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1684 and want to use the onboard SCSI controller, say Y. Otherwise,
1688 tristate "Blizzard 1230IV/1260 SCSI support"
1689 depends on ZORRO && SCSI
1691 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1692 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1695 config FASTLANE_SCSI
1696 tristate "Fastlane SCSI support"
1697 depends on ZORRO && SCSI
1699 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1700 one in the near future, say Y to this question. Otherwise, say N.
1702 config SCSI_AMIGA7XX
1703 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1704 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1706 Support for various NCR53c710-based SCSI controllers on the Amiga.
1708 - the builtin SCSI controller on the Amiga 4000T,
1709 - the Amiga 4091 Zorro III SCSI-2 controller,
1710 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1712 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1713 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1714 accelerator card for the Amiga 1200,
1715 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1716 Note that all of the above SCSI controllers, except for the builtin
1717 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1718 bus, so you also have to enable Zorro bus support if you want to use
1722 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1723 depends on ZORRO && SCSI && EXPERIMENTAL
1725 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1726 Y to this question. If you're in doubt about whether you have one,
1728 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1731 tristate "Atari native SCSI support"
1732 depends on ATARI && SCSI && BROKEN
1733 select SCSI_SPI_ATTRS
1735 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1736 Falcon, ...) say Y to get it supported. Of course also, if you have
1737 a compatible SCSI controller (e.g. for Medusa).
1739 To compile this driver as a module, choose M here: the
1740 module will be called atari_scsi.
1742 This driver supports both styles of NCR integration into the
1743 system: the TT style (separate DMA), and the Falcon style (via
1744 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1745 in the Hades (without DMA).
1747 config ATARI_SCSI_TOSHIBA_DELAY
1748 bool "Long delays for Toshiba CD-ROMs"
1749 depends on ATARI_SCSI
1751 This option increases the delay after a SCSI arbitration to
1752 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1753 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1754 would impact performance a bit, so say N.
1756 config ATARI_SCSI_RESET_BOOT
1757 bool "Reset SCSI-devices at boottime"
1758 depends on ATARI_SCSI
1760 Reset the devices on your Atari whenever it boots. This makes the
1761 boot process fractionally longer but may assist recovery from errors
1762 that leave the devices with SCSI operations partway completed.
1765 bool "Hades SCSI DMA emulator"
1766 depends on ATARI_SCSI && HADES
1768 This option enables code which emulates the TT SCSI DMA chip on the
1769 Hades. This increases the SCSI transfer rates at least ten times
1770 compared to PIO transfers.
1773 bool "Macintosh NCR5380 SCSI"
1774 depends on MAC && SCSI=y
1775 select SCSI_SPI_ATTRS
1777 This is the NCR 5380 SCSI controller included on most of the 68030
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>.
1783 tristate "Macintosh NCR53c9[46] SCSI"
1784 depends on MAC && SCSI
1786 This is the NCR 53c9x SCSI controller found on most of the 68040
1787 based Macintoshes. If you have one of these say Y and read the
1788 SCSI-HOWTO, available from
1789 <http://www.tldp.org/docs.html#howto>.
1791 To compile this driver as a module, choose M here: the
1792 module will be called mac_esp.
1795 bool "WD33C93 SCSI driver for MVME147"
1796 depends on MVME147 && SCSI=y
1797 select SCSI_SPI_ATTRS
1799 Support for the on-board SCSI controller on the Motorola MVME147
1800 single-board computer.
1803 bool "NCR53C710 SCSI driver for MVME16x"
1804 depends on MVME16x && SCSI && BROKEN
1805 select SCSI_SPI_ATTRS
1807 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1808 SCSI controller chip. Almost everyone using one of these boards
1809 will want to say Y to this question.
1811 config BVME6000_SCSI
1812 bool "NCR53C710 SCSI driver for BVME6000"
1813 depends on BVME6000 && SCSI && BROKEN
1814 select SCSI_SPI_ATTRS
1816 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1817 SCSI controller chip. Almost everyone using one of these boards
1818 will want to say Y to this question.
1820 config SCSI_NCR53C7xx_FAST
1821 bool "allow FAST-SCSI [10MHz]"
1822 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1824 This will enable 10MHz FAST-SCSI transfers with your host
1825 adapter. Some systems have problems with that speed, so it's safest
1829 tristate "Sun3 NCR5380 SCSI"
1830 depends on SUN3 && SCSI && BROKEN
1831 select SCSI_SPI_ATTRS
1833 This option will enable support for the OBIO (onboard io) NCR5380
1834 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1835 "Sun3" type VME scsi controllers also based on the NCR5380.
1836 General Linux information on the Sun 3 series (now discontinued)
1837 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1840 bool "Sun3x ESP SCSI"
1841 depends on SUN3X && SCSI=y
1843 The ESP was an on-board SCSI controller used on Sun 3/80
1844 machines. Say Y here to compile in support for it.
1847 tristate "Sparc ESP Scsi Driver"
1848 depends on SBUS && SCSI
1850 This is the driver for the Sun ESP SCSI host adapter. The ESP
1851 chipset is present in most SPARC SBUS-based computers.
1853 To compile this driver as a module, choose M here: the
1854 module will be called esp.
1856 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1859 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1860 depends on S390 && QDIO && SCSI
1861 select SCSI_FC_ATTRS
1863 If you want to access SCSI devices attached to your IBM eServer
1864 zSeries by means of Fibre Channel interfaces say Y.
1865 For details please refer to the documentation provided by IBM at
1866 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1868 This driver is also available as a module. This module will be
1869 called zfcp. If you want to compile it as a module, say M here
1870 and read <file:Documentation/modules.txt>.
1874 source "drivers/scsi/pcmcia/Kconfig"