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
339 select SCSI_SPI_ATTRS
341 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
342 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
343 must be manually specified in this case.
345 It is explained in section 3.3 of the SCSI-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>. You might also want to
347 read the file <file:Documentation/scsi/aha152x.txt>.
349 To compile this driver as a module, choose M here: the
350 module will be called aha152x.
353 tristate "Adaptec AHA1542 support"
354 depends on ISA && SCSI && ISA_DMA_API
356 This is support for a SCSI host adapter. It is explained in section
357 3.4 of the SCSI-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
359 purchased by Adaptec, and some former Trantor products are being
360 sold under the Adaptec name. If it doesn't work out of the box, you
361 may have to change some settings in <file:drivers/scsi/aha1542.h>.
363 To compile this driver as a module, choose M here: the
364 module will be called aha1542.
367 tristate "Adaptec AHA1740 support"
368 depends on EISA && SCSI
370 This is support for a SCSI host adapter. It is explained in section
371 3.5 of the SCSI-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
373 of the box, you may have to change some settings in
374 <file:drivers/scsi/aha1740.h>.
376 To compile this driver as a module, choose M here: the
377 module will be called aha1740.
380 tristate "Adaptec AACRAID support"
381 depends on SCSI && PCI
383 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
385 config SCSI_AIC7XXX_OLD
386 tristate "Adaptec AIC7xxx support (old driver)"
387 depends on (ISA || EISA || PCI ) && SCSI
389 WARNING This driver is an older aic7xxx driver and is no longer
390 under active development. Adaptec, Inc. is writing a new driver to
391 take the place of this one, and it is recommended that whenever
392 possible, people should use the new Adaptec written driver instead
393 of this one. This driver will eventually be phased out entirely.
395 This is support for the various aic7xxx based Adaptec SCSI
396 controllers. These include the 274x EISA cards; 284x VLB cards;
397 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
398 motherboard based SCSI controllers from Adaptec. It does not support
399 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
400 support them. It does not support the 2920 cards from Adaptec that
401 use the Future Domain SCSI controller chip. For those cards, you
402 need the "Future Domain 16xx SCSI support" driver.
404 In general, if the controller is based on an Adaptec SCSI controller
405 chip from the aic777x series or the aic78xx series, this driver
406 should work. The only exception is the 7810 which is specifically
407 not supported (that's the RAID controller chip on the AAA-13x
410 Note that the AHA2920 SCSI host adapter is *not* supported by this
411 driver; choose "Future Domain 16xx SCSI support" instead if you have
414 Information on the configuration options for this controller can be
415 found by checking the help file for each of the available
416 configuration options. You should read
417 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
418 contacting the maintainer with any questions. The SCSI-HOWTO,
419 available from <http://www.tldp.org/docs.html#howto>, can also
422 To compile this driver as a module, choose M here: the
423 module will be called aic7xxx_old.
425 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
427 # All the I2O code and drivers do not seem to be 64bit safe.
429 tristate "Adaptec I2O RAID support "
430 depends on !64BIT && SCSI && PCI
432 This driver supports all of Adaptec's I2O based RAID controllers as
433 well as the DPT SmartRaid V cards. This is an Adaptec maintained
434 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
436 To compile this driver as a module, choose M here: the
437 module will be called dpt_i2o.
440 tristate "AdvanSys SCSI support"
442 depends on ISA || EISA || PCI
443 depends on BROKEN || X86_32
445 This is a driver for all SCSI host adapters manufactured by
446 AdvanSys. It is documented in the kernel source in
447 <file:drivers/scsi/advansys.c>.
449 To compile this driver as a module, choose M here: the
450 module will be called advansys.
453 tristate "Always IN2000 SCSI support"
454 depends on ISA && SCSI
456 This is support for an ISA bus SCSI host adapter. You'll find more
457 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
458 out of the box, you may have to change the jumpers for IRQ or
461 To compile this driver as a module, choose M here: the
462 module will be called in2000.
464 source "drivers/scsi/megaraid/Kconfig.megaraid"
467 tristate "Serial ATA (SATA) support"
470 This driver family supports Serial ATA host controllers
475 config SCSI_SATA_AHCI
476 tristate "AHCI SATA support"
477 depends on SCSI_SATA && PCI
479 This option enables support for AHCI Serial ATA.
484 tristate "ServerWorks Frodo / Apple K2 SATA support"
485 depends on SCSI_SATA && PCI
487 This option enables support for Broadcom/Serverworks/Apple K2
493 tristate "Intel PIIX/ICH SATA support"
494 depends on SCSI_SATA && PCI
496 This option enables support for ICH5 Serial ATA.
497 If PATA support was enabled previously, this enables
498 support for select Intel PIIX/ICH PATA host controllers.
503 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
504 depends on SCSI_SATA && PCI && EXPERIMENTAL
506 This option enables support for the Marvell Serial ATA family.
507 Currently supports 88SX[56]0[48][01] chips.
512 tristate "NVIDIA SATA support"
513 depends on SCSI_SATA && PCI && EXPERIMENTAL
515 This option enables support for NVIDIA Serial ATA.
520 tristate "Pacific Digital ADMA support"
521 depends on SCSI_SATA && PCI
523 This option enables support for Pacific Digital ADMA controllers
528 tristate "HighPoint RocketRAID 3xxx Controller support"
529 depends on SCSI && PCI
531 This option enables support for HighPoint RocketRAID 3xxx
534 To compile this driver as a module, choose M here; the module
535 will be called hptiop. If unsure, say N.
537 config SCSI_SATA_QSTOR
538 tristate "Pacific Digital SATA QStor support"
539 depends on SCSI_SATA && PCI
541 This option enables support for Pacific Digital Serial ATA QStor.
545 config SCSI_SATA_PROMISE
546 tristate "Promise SATA TX2/TX4 support"
547 depends on SCSI_SATA && PCI
549 This option enables support for Promise Serial ATA TX2/TX4.
554 tristate "Promise SATA SX4 support"
555 depends on SCSI_SATA && PCI && EXPERIMENTAL
557 This option enables support for Promise Serial ATA SX4.
562 tristate "Silicon Image SATA support"
563 depends on SCSI_SATA && PCI && EXPERIMENTAL
565 This option enables support for Silicon Image Serial ATA.
569 config SCSI_SATA_SIL24
570 tristate "Silicon Image 3124/3132 SATA support"
571 depends on SCSI_SATA && PCI && EXPERIMENTAL
573 This option enables support for Silicon Image 3124/3132 Serial ATA.
578 tristate "SiS 964/180 SATA support"
579 depends on SCSI_SATA && PCI && EXPERIMENTAL
581 This option enables support for SiS Serial ATA 964/180.
586 tristate "ULi Electronics SATA support"
587 depends on SCSI_SATA && PCI && EXPERIMENTAL
589 This option enables support for ULi Electronics SATA.
594 tristate "VIA SATA support"
595 depends on SCSI_SATA && PCI
597 This option enables support for VIA Serial ATA.
601 config SCSI_SATA_VITESSE
602 tristate "VITESSE VSC-7174 SATA support"
603 depends on SCSI_SATA && PCI
605 This option enables support for Vitesse VSC7174 Serial ATA.
609 config SCSI_SATA_INTEL_COMBINED
611 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
615 tristate "BusLogic SCSI support"
616 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
618 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
619 Adapters. Consult the SCSI-HOWTO, available from
620 <http://www.tldp.org/docs.html#howto>, and the files
621 <file:Documentation/scsi/BusLogic.txt> and
622 <file:Documentation/scsi/FlashPoint.txt> for more information.
624 To compile this driver as a module, choose M here: the
625 module will be called BusLogic.
627 config SCSI_OMIT_FLASHPOINT
628 bool "Omit FlashPoint support"
629 depends on SCSI_BUSLOGIC
631 This option allows you to omit the FlashPoint support from the
632 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
633 substantial, so users of MultiMaster Host Adapters may wish to omit
637 tristate "DMX3191D SCSI support"
638 depends on PCI && SCSI
639 select SCSI_SPI_ATTRS
641 This is support for Domex DMX3191D SCSI Host Adapters.
643 To compile this driver as a module, choose M here: the
644 module will be called dmx3191d.
647 tristate "DTC3180/3280 SCSI support"
648 depends on ISA && SCSI
649 select SCSI_SPI_ATTRS
651 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
652 the SCSI-HOWTO, available from
653 <http://www.tldp.org/docs.html#howto>, and the file
654 <file:Documentation/scsi/dtc3x80.txt>.
656 To compile this driver as a module, choose M here: the
657 module will be called dtc.
660 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
661 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
663 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
664 ISA and all EISA I/O addresses are probed looking for the "EATA"
665 signature. The addresses of all the PCI SCSI controllers reported
666 by the PCI subsystem are probed as well.
668 You want to read the start of <file:drivers/scsi/eata.c> and the
669 SCSI-HOWTO, available from
670 <http://www.tldp.org/docs.html#howto>.
672 To compile this driver as a module, choose M here: the
673 module will be called eata.
675 config SCSI_EATA_TAGGED_QUEUE
676 bool "enable tagged command queueing"
679 This is a feature of SCSI-2 which improves performance: the host
680 adapter can send several SCSI commands to a device's queue even if
681 previous commands haven't finished yet.
682 This is equivalent to the "eata=tc:y" boot option.
684 config SCSI_EATA_LINKED_COMMANDS
685 bool "enable elevator sorting"
688 This option enables elevator sorting for all probed SCSI disks and
689 CD-ROMs. It definitely reduces the average seek distance when doing
690 random seeks, but this does not necessarily result in a noticeable
691 performance improvement: your mileage may vary...
692 This is equivalent to the "eata=lc:y" boot option.
694 config SCSI_EATA_MAX_TAGS
695 int "maximum number of queued commands"
699 This specifies how many SCSI commands can be maximally queued for
700 each probed SCSI device. You should reduce the default value of 16
701 only if you have disks with buggy or limited tagged command support.
702 Minimum is 2 and maximum is 62. This value is also the window size
703 used by the elevator sorting option above. The effective value used
704 by the driver for each probed SCSI device is reported at boot time.
705 This is equivalent to the "eata=mq:8" boot option.
708 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
709 depends on (ISA || EISA || PCI) && SCSI && BROKEN
711 This driver supports all EATA-PIO protocol compliant SCSI Host
712 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
713 host adapters could also use this driver but are discouraged from
714 doing so, since this driver only supports hard disks and lacks
715 numerous features. You might want to have a look at the SCSI-HOWTO,
716 available from <http://www.tldp.org/docs.html#howto>.
718 To compile this driver as a module, choose M here: the
719 module will be called eata_pio.
721 config SCSI_FUTURE_DOMAIN
722 tristate "Future Domain 16xx SCSI/AHA-2920A support"
723 depends on (ISA || PCI) && SCSI
725 This is support for Future Domain's 16-bit SCSI host adapters
726 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
727 other adapters based on the Future Domain chipsets (Quantum
728 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
729 It is explained in section 3.7 of the SCSI-HOWTO, available from
730 <http://www.tldp.org/docs.html#howto>.
732 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
733 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
734 controller support"). This Future Domain driver works with the older
735 Adaptec AHA-2920A boards with a Future Domain chip on them.
737 To compile this driver as a module, choose M here: the
738 module will be called fdomain.
741 tristate "Future Domain MCS-600/700 SCSI support"
742 depends on MCA_LEGACY && SCSI
744 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
745 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
746 is identical to the MCS 700 and hence also supported by this driver.
747 This driver also supports the Reply SB16/SCSI card (the SCSI part).
748 It supports multiple adapters in the same system.
750 To compile this driver as a module, choose M here: the
751 module will be called fd_mcs.
754 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
755 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
757 Formerly called GDT SCSI Disk Array Controller Support.
759 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
760 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
761 in the kernel source in <file:drivers/scsi/gdth.c> and
762 <file:drivers/scsi/gdth.h.>
764 To compile this driver as a module, choose M here: the
765 module will be called gdth.
767 config SCSI_GENERIC_NCR5380
768 tristate "Generic NCR5380/53c400 SCSI PIO support"
769 depends on ISA && SCSI
770 select SCSI_SPI_ATTRS
772 This is a driver for the old NCR 53c80 series of SCSI controllers
773 on boards using PIO. Most boards such as the Trantor T130 fit this
774 category, along with a large number of ISA 8bit controllers shipped
775 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
776 you should select the specific driver for that card rather than
777 generic 5380 support.
779 It is explained in section 3.8 of the SCSI-HOWTO, available from
780 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
781 of the box, you may have to change some settings in
782 <file:drivers/scsi/g_NCR5380.h>.
784 To compile this driver as a module, choose M here: the
785 module will be called g_NCR5380.
787 config SCSI_GENERIC_NCR5380_MMIO
788 tristate "Generic NCR5380/53c400 SCSI MMIO support"
789 depends on ISA && SCSI
790 select SCSI_SPI_ATTRS
792 This is a driver for the old NCR 53c80 series of SCSI controllers
793 on boards using memory mapped I/O.
794 It is explained in section 3.8 of the SCSI-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
796 of the box, you may have to change some settings in
797 <file:drivers/scsi/g_NCR5380.h>.
799 To compile this driver as a module, choose M here: the
800 module will be called g_NCR5380_mmio.
802 config SCSI_GENERIC_NCR53C400
803 bool "Enable NCR53c400 extensions"
804 depends on SCSI_GENERIC_NCR5380
806 This enables certain optimizations for the NCR53c400 SCSI cards.
807 You might as well try it out. Note that this driver will only probe
808 for the Trantor T130B in its default configuration; you might have
809 to pass a command line option to the kernel at boot time if it does
810 not detect your card. See the file
811 <file:Documentation/scsi/g_NCR5380.txt> for details.
814 tristate "IBMMCA SCSI support"
815 depends on MCA_LEGACY && SCSI
817 This is support for the IBM SCSI adapter found in many of the PS/2
818 series computers. These machines have an MCA bus, so you need to
819 answer Y to "MCA support" as well and read
820 <file:Documentation/mca.txt>.
822 If the adapter isn't found during boot (a common problem for models
823 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
824 option, where <pun> is the id of the SCSI subsystem (usually 7, but
825 if that doesn't work check your reference diskette). Owners of
826 model 95 with a LED-matrix-display can in addition activate some
827 activity info like under OS/2, but more informative, by setting
828 'ibmmcascsi=display' as an additional kernel parameter. Try "man
829 bootparam" or see the documentation of your boot loader about how to
830 pass options to the kernel.
832 To compile this driver as a module, choose M here: the
833 module will be called ibmmca.
835 config IBMMCA_SCSI_ORDER_STANDARD
836 bool "Standard SCSI-order"
837 depends on SCSI_IBMMCA
839 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
840 are assigned to the drive letters, starting with the lowest SCSI-id
841 (physical number -- pun) to be drive C:, as seen from DOS and
842 similar operating systems. When looking into papers describing the
843 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
844 The SCSI-standard follows a hardware-hierarchy which says that id 7
845 has the highest priority and id 0 the lowest. Therefore, the host
846 adapters are still today everywhere placed as SCSI-id 7 by default.
847 In the SCSI-standard, the drive letters express the priority of the
848 disk. C: should be the hard disk, or a partition on it, with the
849 highest priority. This must therefore be the disk with the highest
850 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
851 original definition of the SCSI-standard as also industrial- and
852 process-control-machines, like VME-CPUs running under realtime-OSes
853 (e.g. LynxOS, OS9) do.
855 If you like to run Linux on your MCA-machine with the same
856 assignment of hard disks as seen from e.g. DOS or OS/2 on your
857 machine, which is in addition conformant to the SCSI-standard, you
858 must say Y here. This is also necessary for MCA-Linux users who want
859 to keep downward compatibility to older releases of the
860 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
863 If you like to have the lowest SCSI-id assigned as drive C:, as
864 modern SCSI-BIOSes do, which does not conform to the standard, but
865 is widespread and common in the PC-world of today, you must say N
866 here. If unsure, say Y.
868 config IBMMCA_SCSI_DEV_RESET
869 bool "Reset SCSI-devices at boottime"
870 depends on SCSI_IBMMCA
872 By default, SCSI-devices are reset when the machine is powered on.
873 However, some devices exist, like special-control-devices,
874 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
875 not reset when switched on. If you say Y here, each device connected
876 to your SCSI-bus will be issued a reset-command after it has been
877 probed, while the kernel is booting. This may cause problems with
878 more modern devices, like hard disks, which do not appreciate these
879 reset commands, and can cause your system to hang. So say Y only if
880 you know that one of your older devices needs it; N is the safe
884 tristate "IBM ServeRAID support"
885 depends on PCI && SCSI
887 This is support for the IBM ServeRAID hardware RAID controllers.
888 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
889 for more information. If this driver does not work correctly
890 without modification please contact the author by email at
891 <ipslinux@adaptec.com>.
893 To compile this driver as a module, choose M here: the
894 module will be called ips.
897 tristate "IBM Virtual SCSI support"
898 depends on PPC_PSERIES || PPC_ISERIES
900 This is the IBM POWER Virtual SCSI Client
902 To compile this driver as a module, choose M here: the
903 module will be called ibmvscsic.
906 tristate "Initio 9100U(W) support"
907 depends on PCI && SCSI
909 This is support for the Initio 91XXU(W) SCSI host adapter. Please
910 read the SCSI-HOWTO, available from
911 <http://www.tldp.org/docs.html#howto>.
913 To compile this driver as a module, choose M here: the
914 module will be called initio.
917 tristate "Initio INI-A100U2W support"
918 depends on PCI && SCSI
920 This is support for the Initio INI-A100U2W SCSI host adapter.
921 Please read the SCSI-HOWTO, available from
922 <http://www.tldp.org/docs.html#howto>.
924 To compile this driver as a module, choose M here: the
925 module will be called a100u2w.
928 tristate "IOMEGA parallel port (ppa - older drives)"
929 depends on SCSI && PARPORT_PC
931 This driver supports older versions of IOMEGA's parallel port ZIP
932 drive (a 100 MB removable media device).
934 Note that you can say N here if you have the SCSI version of the ZIP
935 drive: it will be supported automatically if you said Y to the
936 generic "SCSI disk support", above.
938 If you have the ZIP Plus drive or a more recent parallel port ZIP
939 drive (if the supplied cable with the drive is labeled "AutoDetect")
940 then you should say N here and Y to "IOMEGA parallel port (imm -
941 newer drives)", below.
943 For more information about this driver and how to use it you should
944 read the file <file:Documentation/scsi/ppa.txt>. You should also read
945 the SCSI-HOWTO, which is available from
946 <http://www.tldp.org/docs.html#howto>. If you use this driver,
947 you will still be able to use the parallel port for other tasks,
948 such as a printer; it is safe to compile both drivers into the
951 To compile this driver as a module, choose M here: the
952 module will be called ppa.
955 tristate "IOMEGA parallel port (imm - newer drives)"
956 depends on SCSI && PARPORT_PC
958 This driver supports newer versions of IOMEGA's parallel port ZIP
959 drive (a 100 MB removable media device).
961 Note that you can say N here if you have the SCSI version of the ZIP
962 drive: it will be supported automatically if you said Y to the
963 generic "SCSI disk support", above.
965 If you have the ZIP Plus drive or a more recent parallel port ZIP
966 drive (if the supplied cable with the drive is labeled "AutoDetect")
967 then you should say Y here; if you have an older ZIP drive, say N
968 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
970 For more information about this driver and how to use it you should
971 read the file <file:Documentation/scsi/ppa.txt>. You should also read
972 the SCSI-HOWTO, which is available from
973 <http://www.tldp.org/docs.html#howto>. If you use this driver,
974 you will still be able to use the parallel port for other tasks,
975 such as a printer; it is safe to compile both drivers into the
978 To compile this driver as a module, choose M here: the
979 module will be called imm.
981 config SCSI_IZIP_EPP16
982 bool "ppa/imm option - Use slow (but safe) EPP-16"
983 depends on SCSI_PPA || SCSI_IMM
985 EPP (Enhanced Parallel Port) is a standard for parallel ports which
986 allows them to act as expansion buses that can handle up to 64
989 Some parallel port chipsets are slower than their motherboard, and
990 so we have to control the state of the chipset's FIFO queue every
991 now and then to avoid data loss. This will be done if you say Y
994 Generally, saying Y is the safe option and slows things down a bit.
996 config SCSI_IZIP_SLOW_CTR
997 bool "ppa/imm option - Assume slow parport control register"
998 depends on SCSI_PPA || SCSI_IMM
1000 Some parallel ports are known to have excessive delays between
1001 changing the parallel port control register and good data being
1002 available on the parallel port data/status register. This option
1003 forces a small delay (1.0 usec to be exact) after changing the
1004 control register to let things settle out. Enabling this option may
1005 result in a big drop in performance but some very old parallel ports
1006 (found in 386 vintage machines) will not work properly.
1008 Generally, saying N is fine.
1010 config SCSI_NCR53C406A
1011 tristate "NCR53c406a SCSI support"
1012 depends on ISA && SCSI
1014 This is support for the NCR53c406a SCSI host adapter. For user
1015 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1016 in the kernel source. Also read the SCSI-HOWTO, available from
1017 <http://www.tldp.org/docs.html#howto>.
1019 To compile this driver as a module, choose M here: the
1020 module will be called NCR53c406.
1022 config SCSI_NCR_D700
1023 tristate "NCR Dual 700 MCA SCSI support"
1024 depends on MCA && SCSI
1025 select SCSI_SPI_ATTRS
1027 This is a driver for the MicroChannel Dual 700 card produced by
1028 NCR and commonly used in 345x/35xx/4100 class machines. It always
1029 tries to negotiate sync and uses tag command queueing.
1031 Unless you have an NCR manufactured machine, the chances are that
1032 you do not have this SCSI card, so say N.
1035 tristate "HP Lasi SCSI support for 53c700/710"
1036 depends on GSC && SCSI
1037 select SCSI_SPI_ATTRS
1039 This is a driver for the SCSI controller in the Lasi chip found in
1040 many PA-RISC workstations & servers. If you do not know whether you
1041 have a Lasi chip, it is safe to say "Y" here.
1043 config 53C700_LE_ON_BE
1045 depends on SCSI_LASI700
1048 config SCSI_SYM53C8XX_2
1049 tristate "SYM53C8XX Version 2 SCSI support"
1050 depends on PCI && SCSI
1051 select SCSI_SPI_ATTRS
1053 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1054 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1055 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1056 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1057 controllers; you need to use the Fusion MPT driver for that.
1059 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1062 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1063 int "DMA addressing mode"
1064 depends on SCSI_SYM53C8XX_2
1067 This option only applies to PCI-SCSI chips that are PCI DAC
1068 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1070 When set to 0, the driver will program the chip to only perform
1071 32-bit DMA. When set to 1, the chip will be able to perform DMA
1072 to addresses up to 1TB. When set to 2, the driver supports the
1073 full 64-bit DMA address range, but can only address 16 segments
1074 of 4 GB each. This limits the total addressable range to 64 GB.
1076 Most machines with less than 4GB of memory should use a setting
1077 of 0 for best performance. If your machine has 4GB of memory
1078 or more, you should set this option to 1 (the default).
1080 The still experimental value 2 (64 bit DMA addressing with 16
1081 x 4GB segments limitation) can be used on systems that require
1082 PCI address bits past bit 39 to be set for the addressing of
1083 memory using PCI DAC cycles.
1085 config SCSI_SYM53C8XX_DEFAULT_TAGS
1086 int "default tagged command queue depth"
1087 depends on SCSI_SYM53C8XX_2
1090 This is the default value of the command queue depth the
1091 driver will announce to the generic SCSI layer for devices
1092 that support tagged command queueing. This value can be changed
1093 from the boot command line. This is a soft limit that cannot
1094 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1096 config SCSI_SYM53C8XX_MAX_TAGS
1097 int "maximum number of queued commands"
1098 depends on SCSI_SYM53C8XX_2
1101 This option allows you to specify the maximum number of commands
1102 that can be queued to any device, when tagged command queuing is
1103 possible. The driver supports up to 256 queued commands per device.
1104 This value is used as a compiled-in hard limit.
1106 config SCSI_SYM53C8XX_IOMAPPED
1108 depends on SCSI_SYM53C8XX_2
1110 If you say Y here, the driver will use port IO to access
1111 the card. This is significantly slower then using memory
1112 mapped IO. Most people should answer N.
1115 tristate "IBM Power Linux RAID adapter support"
1116 depends on PCI && SCSI
1119 This driver supports the IBM Power Linux family RAID adapters.
1120 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1121 as IBM iSeries 5702, 5703, 5709, and 570A.
1123 config SCSI_IPR_TRACE
1124 bool "enable driver internal trace"
1127 If you say Y here, the driver will trace all commands issued
1128 to the adapter. Performance impact is minimal. Trace can be
1129 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1131 config SCSI_IPR_DUMP
1132 bool "enable adapter dump support"
1135 If you say Y here, the driver will support adapter crash dump.
1136 If you enable this support, the iprdump daemon can be used
1137 to capture adapter failure analysis information.
1140 tristate "Zalon SCSI support"
1141 depends on GSC && SCSI
1142 select SCSI_SPI_ATTRS
1144 The Zalon is a GSC/HSC bus interface chip that sits between the
1145 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1146 C110, J200, J210 and some D, K & R-class machines. It's also
1147 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1148 Say Y here if you have one of these machines or cards.
1150 config SCSI_NCR_Q720
1151 tristate "NCR Quad 720 MCA SCSI support"
1152 depends on MCA && SCSI
1153 select SCSI_SPI_ATTRS
1155 This is a driver for the MicroChannel Quad 720 card produced by
1156 NCR and commonly used in 345x/35xx/4100 class machines. It always
1157 tries to negotiate sync and uses tag command queueing.
1159 Unless you have an NCR manufactured machine, the chances are that
1160 you do not have this SCSI card, so say N.
1162 config SCSI_NCR53C8XX_DEFAULT_TAGS
1163 int " default tagged command queue depth"
1164 depends on SCSI_ZALON || SCSI_NCR_Q720
1167 "Tagged command queuing" is a feature of SCSI-2 which improves
1168 performance: the host adapter can send several SCSI commands to a
1169 device's queue even if previous commands haven't finished yet.
1170 Because the device is intelligent, it can optimize its operations
1171 (like head positioning) based on its own request queue. Some SCSI
1172 devices don't implement this properly; if you want to disable this
1173 feature, enter 0 or 1 here (it doesn't matter which).
1175 The default value is 8 and should be supported by most hard disks.
1176 This value can be overridden from the boot command line using the
1177 'tags' option as follows (example):
1178 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1179 4, set queue depth to 16 for target 2 and target 3 on controller 0
1180 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1182 The normal answer therefore is to go with the default 8 and to use
1183 a boot command line option for devices that need to use a different
1184 command queue depth.
1186 There is no safe option other than using good SCSI devices.
1188 config SCSI_NCR53C8XX_MAX_TAGS
1189 int " maximum number of queued commands"
1190 depends on SCSI_ZALON || SCSI_NCR_Q720
1193 This option allows you to specify the maximum number of commands
1194 that can be queued to any device, when tagged command queuing is
1195 possible. The default value is 32. Minimum is 2, maximum is 64.
1196 Modern hard disks are able to support 64 tags and even more, but
1197 do not seem to be faster when more than 32 tags are being used.
1199 So, the normal answer here is to go with the default value 32 unless
1200 you are using very large hard disks with large cache (>= 1 MB) that
1201 are able to take advantage of more than 32 tagged commands.
1203 There is no safe option and the default answer is recommended.
1205 config SCSI_NCR53C8XX_SYNC
1206 int " synchronous transfers frequency in MHz"
1207 depends on SCSI_ZALON || SCSI_NCR_Q720
1210 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1211 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1212 are respectively the maximum data transfer rates in mega-transfers
1213 per second for each class. For example, a FAST-20 Wide 16 device is
1214 able to transfer data at 20 million 16 bit packets per second for a
1215 total rate of 40 MB/s.
1217 You may specify 0 if you want to only use asynchronous data
1218 transfers. This is the safest and slowest option. Otherwise, specify
1219 a value between 5 and 80, depending on the capability of your SCSI
1220 controller. The higher the number, the faster the data transfer.
1221 Note that 80 should normally be ok since the driver decreases the
1222 value automatically according to the controller's capabilities.
1224 Your answer to this question is ignored for controllers with NVRAM,
1225 since the driver will get this information from the user set-up. It
1226 also can be overridden using a boot setup option, as follows
1227 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1228 for FAST-20 synchronous data transfer (20 mega-transfers per
1231 The normal answer therefore is not to go with the default but to
1232 select the maximum value 80 allowing the driver to use the maximum
1233 value supported by each controller. If this causes problems with
1234 your SCSI devices, you should come back and decrease the value.
1236 There is no safe option other than using good cabling, right
1237 terminations and SCSI conformant devices.
1239 config SCSI_NCR53C8XX_PROFILE
1240 bool " enable profiling"
1241 depends on SCSI_ZALON || SCSI_NCR_Q720
1243 This option allows you to enable profiling information gathering.
1244 These statistics are not very accurate due to the low frequency
1245 of the kernel clock (100 Hz on i386) and have performance impact
1246 on systems that use very fast devices.
1248 The normal answer therefore is N.
1250 config SCSI_NCR53C8XX_NO_DISCONNECT
1251 bool " not allow targets to disconnect"
1252 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1254 This option is only provided for safety if you suspect some SCSI
1255 device of yours to not support properly the target-disconnect
1256 feature. In that case, you would say Y here. In general however, to
1257 not allow targets to disconnect is not reasonable if there is more
1258 than 1 device on a SCSI bus. The normal answer therefore is N.
1260 config SCSI_MCA_53C9X
1261 tristate "NCR MCA 53C9x SCSI support"
1262 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1264 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1265 controller based on the NCR 53C94. This driver will allow use of
1266 the controller on the 3550, and very possibly others.
1268 To compile this driver as a module, choose M here: the
1269 module will be called mca_53c9x.
1272 tristate "PAS16 SCSI support"
1273 depends on ISA && SCSI
1274 select SCSI_SPI_ATTRS
1276 This is support for a SCSI host adapter. It is explained in section
1277 3.10 of the SCSI-HOWTO, available from
1278 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1279 of the box, you may have to change some settings in
1280 <file:drivers/scsi/pas16.h>.
1282 To compile this driver as a module, choose M here: the
1283 module will be called pas16.
1286 tristate "PSI240i support"
1287 depends on ISA && SCSI
1289 This is support for the PSI240i EIDE interface card which acts as a
1290 SCSI host adapter. Please read the SCSI-HOWTO, available from
1291 <http://www.tldp.org/docs.html#howto>.
1293 To compile this driver as a module, choose M here: the
1294 module will be called psi240i.
1296 config SCSI_QLOGIC_FAS
1297 tristate "Qlogic FAS SCSI support"
1298 depends on ISA && SCSI
1300 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1301 FastSCSI! cards as well as any other card based on the FASXX chip
1302 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1304 This driver does NOT support the PCI versions of these cards. The
1305 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1306 SCSI support"), below.
1308 Information about this driver is contained in
1309 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1310 SCSI-HOWTO, available from
1311 <http://www.tldp.org/docs.html#howto>.
1313 To compile this driver as a module, choose M here: the
1314 module will be called qlogicfas.
1316 config SCSI_QLOGIC_FC
1317 tristate "Qlogic ISP FC SCSI support"
1318 depends on PCI && SCSI
1320 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1322 To compile this driver as a module, choose M here: the
1323 module will be called qlogicfc.
1325 config SCSI_QLOGIC_FC_FIRMWARE
1326 bool "Include loadable firmware in driver"
1327 depends on SCSI_QLOGIC_FC
1329 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1330 expanded LUN addressing and FcTape (FCP-2) support, in the
1331 qlogicfc driver. This is required on some platforms.
1333 config SCSI_QLOGIC_1280
1334 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1335 depends on PCI && SCSI
1337 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1339 To compile this driver as a module, choose M here: the
1340 module will be called qla1280.
1342 config SCSI_QLOGICPTI
1343 tristate "PTI Qlogic, ISP Driver"
1344 depends on SBUS && SCSI
1346 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1347 controllers are known under Solaris as qpti and in the openprom as
1348 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1349 driven by a different driver.
1351 To compile this driver as a module, choose M here: the
1352 module will be called qlogicpti.
1354 source "drivers/scsi/qla2xxx/Kconfig"
1357 tristate "Emulex LightPulse Fibre Channel Support"
1358 depends on PCI && SCSI
1359 select SCSI_FC_ATTRS
1361 This lpfc driver supports the Emulex LightPulse
1362 Family of Fibre Channel PCI host adapters.
1365 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1366 depends on X86 && ISA && SCSI && BROKEN
1368 These are 8-bit SCSI controllers; the ST-01 is also supported by
1369 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1370 available from <http://www.tldp.org/docs.html#howto>. If it
1371 doesn't work out of the box, you may have to change some settings in
1372 <file:drivers/scsi/seagate.h>.
1374 To compile this driver as a module, choose M here: the
1375 module will be called seagate.
1377 # definitely looks not 64bit safe:
1379 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1380 depends on (EISA || MCA) && SCSI
1381 select SCSI_SPI_ATTRS
1383 This driver for NCR53c710 based SCSI host adapters.
1385 It currently supports Compaq EISA cards and NCR MCA cards
1387 config 53C700_IO_MAPPED
1389 depends on SCSI_SIM710
1392 config SCSI_SYM53C416
1393 tristate "Symbios 53c416 SCSI support"
1394 depends on ISA && SCSI
1396 This is support for the sym53c416 SCSI host adapter, the SCSI
1397 adapter that comes with some HP scanners. This driver requires that
1398 the sym53c416 is configured first using some sort of PnP
1399 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1400 are using isapnp then you need to compile this driver as a module
1401 and then load it using insmod after isapnp has run. The parameters
1402 of the configured card(s) should be passed to the driver. The format
1405 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1407 To compile this driver as a module, choose M here: the
1408 module will be called sym53c416.
1411 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1412 depends on PCI && SCSI && EXPERIMENTAL
1414 This driver supports PCI SCSI host adapters based on the ASIC
1415 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1417 This driver works, but is still in experimental status. So better
1418 have a bootable disk and a backup in case of emergency.
1420 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1422 To compile this driver as a module, choose M here: the
1423 module will be called dc395x.
1426 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1427 depends on PCI && SCSI
1429 This driver supports PCI SCSI host adapters based on the Am53C974A
1430 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1431 PCscsi/PCnet (Am53/79C974) solutions.
1433 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1435 Note that this driver does NOT support Tekram DC390W/U/F, which are
1436 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1438 To compile this driver as a module, choose M here: the
1439 module will be called tmscsim.
1442 tristate "Trantor T128/T128F/T228 SCSI support"
1443 depends on ISA && SCSI
1444 select SCSI_SPI_ATTRS
1446 This is support for a SCSI host adapter. It is explained in section
1447 3.11 of the SCSI-HOWTO, available from
1448 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1449 of the box, you may have to change some settings in
1450 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1451 Adaptec, and some former Trantor products are being sold under the
1454 To compile this driver as a module, choose M here: the
1455 module will be called t128.
1458 tristate "UltraStor 14F/34F support"
1459 depends on ISA && SCSI && ISA_DMA_API
1461 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1462 The source at <file:drivers/scsi/u14-34f.c> contains some
1463 information about this hardware. If the driver doesn't work out of
1464 the box, you may have to change some settings in
1465 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1466 <http://www.tldp.org/docs.html#howto>. Note that there is also
1467 another driver for the same hardware: "UltraStor SCSI support",
1468 below. You should say Y to both only if you want 24F support as
1471 To compile this driver as a module, choose M here: the
1472 module will be called u14-34f.
1474 config SCSI_U14_34F_TAGGED_QUEUE
1475 bool "enable tagged command queueing"
1476 depends on SCSI_U14_34F
1478 This is a feature of SCSI-2 which improves performance: the host
1479 adapter can send several SCSI commands to a device's queue even if
1480 previous commands haven't finished yet.
1481 This is equivalent to the "u14-34f=tc:y" boot option.
1483 config SCSI_U14_34F_LINKED_COMMANDS
1484 bool "enable elevator sorting"
1485 depends on SCSI_U14_34F
1487 This option enables elevator sorting for all probed SCSI disks and
1488 CD-ROMs. It definitely reduces the average seek distance when doing
1489 random seeks, but this does not necessarily result in a noticeable
1490 performance improvement: your mileage may vary...
1491 This is equivalent to the "u14-34f=lc:y" boot option.
1493 config SCSI_U14_34F_MAX_TAGS
1494 int "maximum number of queued commands"
1495 depends on SCSI_U14_34F
1498 This specifies how many SCSI commands can be maximally queued for
1499 each probed SCSI device. You should reduce the default value of 8
1500 only if you have disks with buggy or limited tagged command support.
1501 Minimum is 2 and maximum is 14. This value is also the window size
1502 used by the elevator sorting option above. The effective value used
1503 by the driver for each probed SCSI device is reported at boot time.
1504 This is equivalent to the "u14-34f=mq:8" boot option.
1506 config SCSI_ULTRASTOR
1507 tristate "UltraStor SCSI support"
1508 depends on X86 && ISA && SCSI
1510 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1511 adapter family. This driver is explained in section 3.12 of the
1512 SCSI-HOWTO, available from
1513 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1514 of the box, you may have to change some settings in
1515 <file:drivers/scsi/ultrastor.h>.
1517 Note that there is also another driver for the same hardware:
1518 "UltraStor 14F/34F support", above.
1520 To compile this driver as a module, choose M here: the
1521 module will be called ultrastor.
1524 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1525 depends on PCI && SCSI && !64BIT
1527 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1528 SCSI host adapter. Please read the SCSI-HOWTO, available from
1529 <http://www.tldp.org/docs.html#howto>.
1531 To compile this driver as a module, choose M here: the
1532 module will be called nsp32.
1535 tristate "SCSI debugging host simulator"
1538 This is a host adapter simulator that can simulate multiple hosts
1539 each with multiple dummy SCSI devices (disks). It defaults to one
1540 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1541 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1542 dummy disks are simulated, they share the same kernel RAM for
1543 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1544 information. This driver is primarily of use to those testing the
1545 SCSI and block subsystems. If unsure, say N.
1548 tristate "MESH (Power Mac internal SCSI) support"
1549 depends on PPC32 && PPC_PMAC && SCSI
1551 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1552 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1553 other Power Macintoshes do). Say Y to include support for this SCSI
1556 To compile this driver as a module, choose M here: the
1557 module will be called mesh.
1559 config SCSI_MESH_SYNC_RATE
1560 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1561 depends on SCSI_MESH
1564 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1565 drives a bus which is entirely internal to the machine (such as the
1566 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1567 operation at up to 10 MB/s. On machines where the SCSI bus
1568 controlled by the MESH can have external devices connected, it is
1569 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1570 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1571 to disable synchronous operation.
1573 config SCSI_MESH_RESET_DELAY_MS
1574 int "initial bus reset delay (ms) (0 = no reset)"
1575 depends on SCSI_MESH
1578 config SCSI_MAC53C94
1579 tristate "53C94 (Power Mac external SCSI) support"
1580 depends on PPC32 && PPC_PMAC && SCSI
1582 On Power Macintoshes (and clones) with two SCSI buses, the external
1583 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1584 machines which only have one SCSI bus, such as the 7200, also use
1585 the 53C94. Say Y to include support for the 53C94.
1587 To compile this driver as a module, choose M here: the
1588 module will be called mac53c94.
1590 source "drivers/scsi/arm/Kconfig"
1593 bool "MIPS JAZZ FAS216 SCSI support"
1594 depends on MACH_JAZZ && SCSI
1596 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1597 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1601 tristate "A3000 WD33C93A support"
1602 depends on AMIGA && SCSI
1604 If you have an Amiga 3000 and have SCSI devices connected to the
1605 built-in SCSI controller, say Y. Otherwise, say N.
1607 To compile this driver as a module, choose M here: the
1608 module will be called wd33c93.
1611 tristate "A2091/A590 WD33C93A support"
1612 depends on ZORRO && SCSI
1614 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1617 To compile this driver as a module, choose M here: the
1618 module will be called wd33c93.
1621 tristate "GVP Series II WD33C93A support"
1622 depends on ZORRO && SCSI
1624 If you have a Great Valley Products Series II SCSI controller,
1625 answer Y. Also say Y if you have a later model of GVP SCSI
1626 controller (such as the GVP A4008 or a Combo board). Otherwise,
1627 answer N. This driver does NOT work for the T-Rex series of
1628 accelerators from TekMagic and GVP-M.
1630 To compile this driver as a module, choose M here: the
1631 module will be called gvp11.
1633 config CYBERSTORM_SCSI
1634 tristate "CyberStorm SCSI support"
1635 depends on ZORRO && SCSI
1637 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1638 accelerator board and the optional Cyberstorm SCSI controller,
1639 answer Y. Otherwise, say N.
1641 config CYBERSTORMII_SCSI
1642 tristate "CyberStorm Mk II SCSI support"
1643 depends on ZORRO && SCSI
1645 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1646 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1650 tristate "Blizzard 2060 SCSI support"
1651 depends on ZORRO && SCSI
1653 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1654 and want to use the onboard SCSI controller, say Y. Otherwise,
1658 tristate "Blizzard 1230IV/1260 SCSI support"
1659 depends on ZORRO && SCSI
1661 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1662 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1665 config FASTLANE_SCSI
1666 tristate "Fastlane SCSI support"
1667 depends on ZORRO && SCSI
1669 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1670 one in the near future, say Y to this question. Otherwise, say N.
1672 config SCSI_AMIGA7XX
1673 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1674 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1676 Support for various NCR53c710-based SCSI controllers on the Amiga.
1678 - the builtin SCSI controller on the Amiga 4000T,
1679 - the Amiga 4091 Zorro III SCSI-2 controller,
1680 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1682 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1683 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1684 accelerator card for the Amiga 1200,
1685 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1686 Note that all of the above SCSI controllers, except for the builtin
1687 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1688 bus, so you also have to enable Zorro bus support if you want to use
1692 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1693 depends on ZORRO && SCSI && EXPERIMENTAL
1695 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1696 Y to this question. If you're in doubt about whether you have one,
1698 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1701 tristate "Atari native SCSI support"
1702 depends on ATARI && SCSI && BROKEN
1703 select SCSI_SPI_ATTRS
1705 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1706 Falcon, ...) say Y to get it supported. Of course also, if you have
1707 a compatible SCSI controller (e.g. for Medusa).
1709 To compile this driver as a module, choose M here: the
1710 module will be called atari_scsi.
1712 This driver supports both styles of NCR integration into the
1713 system: the TT style (separate DMA), and the Falcon style (via
1714 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1715 in the Hades (without DMA).
1717 config ATARI_SCSI_TOSHIBA_DELAY
1718 bool "Long delays for Toshiba CD-ROMs"
1719 depends on ATARI_SCSI
1721 This option increases the delay after a SCSI arbitration to
1722 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1723 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1724 would impact performance a bit, so say N.
1726 config ATARI_SCSI_RESET_BOOT
1727 bool "Reset SCSI-devices at boottime"
1728 depends on ATARI_SCSI
1730 Reset the devices on your Atari whenever it boots. This makes the
1731 boot process fractionally longer but may assist recovery from errors
1732 that leave the devices with SCSI operations partway completed.
1735 bool "Hades SCSI DMA emulator"
1736 depends on ATARI_SCSI && HADES
1738 This option enables code which emulates the TT SCSI DMA chip on the
1739 Hades. This increases the SCSI transfer rates at least ten times
1740 compared to PIO transfers.
1743 bool "Macintosh NCR5380 SCSI"
1744 depends on MAC && SCSI=y
1745 select SCSI_SPI_ATTRS
1747 This is the NCR 5380 SCSI controller included on most of the 68030
1748 based Macintoshes. If you have one of these say Y and read the
1749 SCSI-HOWTO, available from
1750 <http://www.tldp.org/docs.html#howto>.
1753 tristate "Macintosh NCR53c9[46] SCSI"
1754 depends on MAC && SCSI
1756 This is the NCR 53c9x SCSI controller found on most of the 68040
1757 based Macintoshes. If you have one of these say Y and read the
1758 SCSI-HOWTO, available from
1759 <http://www.tldp.org/docs.html#howto>.
1761 To compile this driver as a module, choose M here: the
1762 module will be called mac_esp.
1765 bool "WD33C93 SCSI driver for MVME147"
1766 depends on MVME147 && SCSI=y
1767 select SCSI_SPI_ATTRS
1769 Support for the on-board SCSI controller on the Motorola MVME147
1770 single-board computer.
1773 bool "NCR53C710 SCSI driver for MVME16x"
1774 depends on MVME16x && SCSI && BROKEN
1775 select SCSI_SPI_ATTRS
1777 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1778 SCSI controller chip. Almost everyone using one of these boards
1779 will want to say Y to this question.
1781 config BVME6000_SCSI
1782 bool "NCR53C710 SCSI driver for BVME6000"
1783 depends on BVME6000 && SCSI && BROKEN
1784 select SCSI_SPI_ATTRS
1786 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1787 SCSI controller chip. Almost everyone using one of these boards
1788 will want to say Y to this question.
1790 config SCSI_NCR53C7xx_FAST
1791 bool "allow FAST-SCSI [10MHz]"
1792 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1794 This will enable 10MHz FAST-SCSI transfers with your host
1795 adapter. Some systems have problems with that speed, so it's safest
1799 tristate "Sun3 NCR5380 SCSI"
1800 depends on SUN3 && SCSI && BROKEN
1801 select SCSI_SPI_ATTRS
1803 This option will enable support for the OBIO (onboard io) NCR5380
1804 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1805 "Sun3" type VME scsi controllers also based on the NCR5380.
1806 General Linux information on the Sun 3 series (now discontinued)
1807 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1810 bool "Sun3x ESP SCSI"
1811 depends on SUN3X && SCSI=y
1813 The ESP was an on-board SCSI controller used on Sun 3/80
1814 machines. Say Y here to compile in support for it.
1817 tristate "Sparc ESP Scsi Driver"
1818 depends on SBUS && SCSI
1820 This is the driver for the Sun ESP SCSI host adapter. The ESP
1821 chipset is present in most SPARC SBUS-based computers.
1823 To compile this driver as a module, choose M here: the
1824 module will be called esp.
1826 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1829 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1830 depends on S390 && QDIO && SCSI
1831 select SCSI_FC_ATTRS
1833 If you want to access SCSI devices attached to your IBM eServer
1834 zSeries by means of Fibre Channel interfaces say Y.
1835 For details please refer to the documentation provided by IBM at
1836 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1838 This driver is also available as a module. This module will be
1839 called zfcp. If you want to compile it as a module, say M here
1840 and read <file:Documentation/modules.txt>.
1844 source "drivers/scsi/pcmcia/Kconfig"