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 This driver supports a variety of Dell, HP, Adaptec, IBM and
384 ICP storage products. For a list of supported products, refer
385 to <file:Documentation/scsi/aacraid.txt>.
387 To compile this driver as a module, choose M here: the module
388 will be called aacraid.
391 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
393 config SCSI_AIC7XXX_OLD
394 tristate "Adaptec AIC7xxx support (old driver)"
395 depends on (ISA || EISA || PCI ) && SCSI
397 WARNING This driver is an older aic7xxx driver and is no longer
398 under active development. Adaptec, Inc. is writing a new driver to
399 take the place of this one, and it is recommended that whenever
400 possible, people should use the new Adaptec written driver instead
401 of this one. This driver will eventually be phased out entirely.
403 This is support for the various aic7xxx based Adaptec SCSI
404 controllers. These include the 274x EISA cards; 284x VLB cards;
405 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
406 motherboard based SCSI controllers from Adaptec. It does not support
407 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
408 support them. It does not support the 2920 cards from Adaptec that
409 use the Future Domain SCSI controller chip. For those cards, you
410 need the "Future Domain 16xx SCSI support" driver.
412 In general, if the controller is based on an Adaptec SCSI controller
413 chip from the aic777x series or the aic78xx series, this driver
414 should work. The only exception is the 7810 which is specifically
415 not supported (that's the RAID controller chip on the AAA-13x
418 Note that the AHA2920 SCSI host adapter is *not* supported by this
419 driver; choose "Future Domain 16xx SCSI support" instead if you have
422 Information on the configuration options for this controller can be
423 found by checking the help file for each of the available
424 configuration options. You should read
425 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
426 contacting the maintainer with any questions. The SCSI-HOWTO,
427 available from <http://www.tldp.org/docs.html#howto>, can also
430 To compile this driver as a module, choose M here: the
431 module will be called aic7xxx_old.
433 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
435 # All the I2O code and drivers do not seem to be 64bit safe.
437 tristate "Adaptec I2O RAID support "
438 depends on !64BIT && SCSI && PCI
440 This driver supports all of Adaptec's I2O based RAID controllers as
441 well as the DPT SmartRaid V cards. This is an Adaptec maintained
442 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
444 To compile this driver as a module, choose M here: the
445 module will be called dpt_i2o.
448 tristate "AdvanSys SCSI support"
449 depends on (ISA || EISA || PCI) && SCSI && BROKEN
451 This is a driver for all SCSI host adapters manufactured by
452 AdvanSys. It is documented in the kernel source in
453 <file:drivers/scsi/advansys.c>.
455 To compile this driver as a module, choose M here: the
456 module will be called advansys.
459 tristate "Always IN2000 SCSI support"
460 depends on ISA && SCSI
462 This is support for an ISA bus SCSI host adapter. You'll find more
463 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
464 out of the box, you may have to change the jumpers for IRQ or
467 To compile this driver as a module, choose M here: the
468 module will be called in2000.
470 source "drivers/scsi/megaraid/Kconfig.megaraid"
473 tristate "Serial ATA (SATA) support"
476 This driver family supports Serial ATA host controllers
481 config SCSI_SATA_AHCI
482 tristate "AHCI SATA support"
483 depends on SCSI_SATA && PCI
485 This option enables support for AHCI Serial ATA.
490 tristate "ServerWorks Frodo / Apple K2 SATA support"
491 depends on SCSI_SATA && PCI
493 This option enables support for Broadcom/Serverworks/Apple K2
499 tristate "Intel PIIX/ICH SATA support"
500 depends on SCSI_SATA && PCI
502 This option enables support for ICH5 Serial ATA.
503 If PATA support was enabled previously, this enables
504 support for select Intel PIIX/ICH PATA host controllers.
509 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
510 depends on SCSI_SATA && PCI && EXPERIMENTAL
512 This option enables support for the Marvell Serial ATA family.
513 Currently supports 88SX[56]0[48][01] chips.
518 tristate "NVIDIA SATA support"
519 depends on SCSI_SATA && PCI && EXPERIMENTAL
521 This option enables support for NVIDIA Serial ATA.
526 tristate "Pacific Digital ADMA support"
527 depends on SCSI_SATA && PCI
529 This option enables support for Pacific Digital ADMA controllers
534 tristate "HighPoint RocketRAID 3xxx Controller support"
535 depends on SCSI && PCI
537 This option enables support for HighPoint RocketRAID 3xxx
540 To compile this driver as a module, choose M here; the module
541 will be called hptiop. If unsure, say N.
543 config SCSI_SATA_QSTOR
544 tristate "Pacific Digital SATA QStor support"
545 depends on SCSI_SATA && PCI
547 This option enables support for Pacific Digital Serial ATA QStor.
551 config SCSI_SATA_PROMISE
552 tristate "Promise SATA TX2/TX4 support"
553 depends on SCSI_SATA && PCI
555 This option enables support for Promise Serial ATA TX2/TX4.
560 tristate "Promise SATA SX4 support"
561 depends on SCSI_SATA && PCI && EXPERIMENTAL
563 This option enables support for Promise Serial ATA SX4.
568 tristate "Silicon Image SATA support"
569 depends on SCSI_SATA && PCI && EXPERIMENTAL
571 This option enables support for Silicon Image Serial ATA.
575 config SCSI_SATA_SIL24
576 tristate "Silicon Image 3124/3132 SATA support"
577 depends on SCSI_SATA && PCI && EXPERIMENTAL
579 This option enables support for Silicon Image 3124/3132 Serial ATA.
584 tristate "SiS 964/180 SATA support"
585 depends on SCSI_SATA && PCI && EXPERIMENTAL
587 This option enables support for SiS Serial ATA 964/180.
592 tristate "ULi Electronics SATA support"
593 depends on SCSI_SATA && PCI && EXPERIMENTAL
595 This option enables support for ULi Electronics SATA.
600 tristate "VIA SATA support"
601 depends on SCSI_SATA && PCI
603 This option enables support for VIA Serial ATA.
607 config SCSI_SATA_VITESSE
608 tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
609 depends on SCSI_SATA && PCI
611 This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
615 config SCSI_SATA_INTEL_COMBINED
617 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
621 tristate "BusLogic SCSI support"
622 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
624 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
625 Adapters. Consult the SCSI-HOWTO, available from
626 <http://www.tldp.org/docs.html#howto>, and the files
627 <file:Documentation/scsi/BusLogic.txt> and
628 <file:Documentation/scsi/FlashPoint.txt> for more information.
630 To compile this driver as a module, choose M here: the
631 module will be called BusLogic.
633 config SCSI_OMIT_FLASHPOINT
634 bool "Omit FlashPoint support"
635 depends on SCSI_BUSLOGIC
637 This option allows you to omit the FlashPoint support from the
638 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
639 substantial, so users of MultiMaster Host Adapters may wish to omit
643 tristate "DMX3191D SCSI support"
644 depends on PCI && SCSI
645 select SCSI_SPI_ATTRS
647 This is support for Domex DMX3191D SCSI Host Adapters.
649 To compile this driver as a module, choose M here: the
650 module will be called dmx3191d.
653 tristate "DTC3180/3280 SCSI support"
654 depends on ISA && SCSI
655 select SCSI_SPI_ATTRS
657 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
658 the SCSI-HOWTO, available from
659 <http://www.tldp.org/docs.html#howto>, and the file
660 <file:Documentation/scsi/dtc3x80.txt>.
662 To compile this driver as a module, choose M here: the
663 module will be called dtc.
666 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
667 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
669 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
670 ISA and all EISA I/O addresses are probed looking for the "EATA"
671 signature. The addresses of all the PCI SCSI controllers reported
672 by the PCI subsystem are probed as well.
674 You want to read the start of <file:drivers/scsi/eata.c> and the
675 SCSI-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>.
678 To compile this driver as a module, choose M here: the
679 module will be called eata.
681 config SCSI_EATA_TAGGED_QUEUE
682 bool "enable tagged command queueing"
685 This is a feature of SCSI-2 which improves performance: the host
686 adapter can send several SCSI commands to a device's queue even if
687 previous commands haven't finished yet.
688 This is equivalent to the "eata=tc:y" boot option.
690 config SCSI_EATA_LINKED_COMMANDS
691 bool "enable elevator sorting"
694 This option enables elevator sorting for all probed SCSI disks and
695 CD-ROMs. It definitely reduces the average seek distance when doing
696 random seeks, but this does not necessarily result in a noticeable
697 performance improvement: your mileage may vary...
698 This is equivalent to the "eata=lc:y" boot option.
700 config SCSI_EATA_MAX_TAGS
701 int "maximum number of queued commands"
705 This specifies how many SCSI commands can be maximally queued for
706 each probed SCSI device. You should reduce the default value of 16
707 only if you have disks with buggy or limited tagged command support.
708 Minimum is 2 and maximum is 62. This value is also the window size
709 used by the elevator sorting option above. The effective value used
710 by the driver for each probed SCSI device is reported at boot time.
711 This is equivalent to the "eata=mq:8" boot option.
714 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
715 depends on (ISA || EISA || PCI) && SCSI && BROKEN
717 This driver supports all EATA-PIO protocol compliant SCSI Host
718 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
719 host adapters could also use this driver but are discouraged from
720 doing so, since this driver only supports hard disks and lacks
721 numerous features. You might want to have a look at the SCSI-HOWTO,
722 available from <http://www.tldp.org/docs.html#howto>.
724 To compile this driver as a module, choose M here: the
725 module will be called eata_pio.
727 config SCSI_FUTURE_DOMAIN
728 tristate "Future Domain 16xx SCSI/AHA-2920A support"
729 depends on (ISA || PCI) && SCSI
731 This is support for Future Domain's 16-bit SCSI host adapters
732 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
733 other adapters based on the Future Domain chipsets (Quantum
734 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
735 It is explained in section 3.7 of the SCSI-HOWTO, available from
736 <http://www.tldp.org/docs.html#howto>.
738 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
739 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
740 controller support"). This Future Domain driver works with the older
741 Adaptec AHA-2920A boards with a Future Domain chip on them.
743 To compile this driver as a module, choose M here: the
744 module will be called fdomain.
747 tristate "Future Domain MCS-600/700 SCSI support"
748 depends on MCA_LEGACY && SCSI
750 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
751 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
752 is identical to the MCS 700 and hence also supported by this driver.
753 This driver also supports the Reply SB16/SCSI card (the SCSI part).
754 It supports multiple adapters in the same system.
756 To compile this driver as a module, choose M here: the
757 module will be called fd_mcs.
760 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
761 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
763 Formerly called GDT SCSI Disk Array Controller Support.
765 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
766 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
767 in the kernel source in <file:drivers/scsi/gdth.c> and
768 <file:drivers/scsi/gdth.h.>
770 To compile this driver as a module, choose M here: the
771 module will be called gdth.
773 config SCSI_GENERIC_NCR5380
774 tristate "Generic NCR5380/53c400 SCSI PIO support"
775 depends on ISA && SCSI
776 select SCSI_SPI_ATTRS
778 This is a driver for the old NCR 53c80 series of SCSI controllers
779 on boards using PIO. Most boards such as the Trantor T130 fit this
780 category, along with a large number of ISA 8bit controllers shipped
781 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
782 you should select the specific driver for that card rather than
783 generic 5380 support.
785 It is explained in section 3.8 of the SCSI-HOWTO, available from
786 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
787 of the box, you may have to change some settings in
788 <file:drivers/scsi/g_NCR5380.h>.
790 To compile this driver as a module, choose M here: the
791 module will be called g_NCR5380.
793 config SCSI_GENERIC_NCR5380_MMIO
794 tristate "Generic NCR5380/53c400 SCSI MMIO support"
795 depends on ISA && SCSI
796 select SCSI_SPI_ATTRS
798 This is a driver for the old NCR 53c80 series of SCSI controllers
799 on boards using memory mapped I/O.
800 It is explained in section 3.8 of the SCSI-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
802 of the box, you may have to change some settings in
803 <file:drivers/scsi/g_NCR5380.h>.
805 To compile this driver as a module, choose M here: the
806 module will be called g_NCR5380_mmio.
808 config SCSI_GENERIC_NCR53C400
809 bool "Enable NCR53c400 extensions"
810 depends on SCSI_GENERIC_NCR5380
812 This enables certain optimizations for the NCR53c400 SCSI cards.
813 You might as well try it out. Note that this driver will only probe
814 for the Trantor T130B in its default configuration; you might have
815 to pass a command line option to the kernel at boot time if it does
816 not detect your card. See the file
817 <file:Documentation/scsi/g_NCR5380.txt> for details.
820 tristate "IBMMCA SCSI support"
821 depends on MCA_LEGACY && SCSI
823 This is support for the IBM SCSI adapter found in many of the PS/2
824 series computers. These machines have an MCA bus, so you need to
825 answer Y to "MCA support" as well and read
826 <file:Documentation/mca.txt>.
828 If the adapter isn't found during boot (a common problem for models
829 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
830 option, where <pun> is the id of the SCSI subsystem (usually 7, but
831 if that doesn't work check your reference diskette). Owners of
832 model 95 with a LED-matrix-display can in addition activate some
833 activity info like under OS/2, but more informative, by setting
834 'ibmmcascsi=display' as an additional kernel parameter. Try "man
835 bootparam" or see the documentation of your boot loader about how to
836 pass options to the kernel.
838 To compile this driver as a module, choose M here: the
839 module will be called ibmmca.
841 config IBMMCA_SCSI_ORDER_STANDARD
842 bool "Standard SCSI-order"
843 depends on SCSI_IBMMCA
845 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
846 are assigned to the drive letters, starting with the lowest SCSI-id
847 (physical number -- pun) to be drive C:, as seen from DOS and
848 similar operating systems. When looking into papers describing the
849 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
850 The SCSI-standard follows a hardware-hierarchy which says that id 7
851 has the highest priority and id 0 the lowest. Therefore, the host
852 adapters are still today everywhere placed as SCSI-id 7 by default.
853 In the SCSI-standard, the drive letters express the priority of the
854 disk. C: should be the hard disk, or a partition on it, with the
855 highest priority. This must therefore be the disk with the highest
856 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
857 original definition of the SCSI-standard as also industrial- and
858 process-control-machines, like VME-CPUs running under realtime-OSes
859 (e.g. LynxOS, OS9) do.
861 If you like to run Linux on your MCA-machine with the same
862 assignment of hard disks as seen from e.g. DOS or OS/2 on your
863 machine, which is in addition conformant to the SCSI-standard, you
864 must say Y here. This is also necessary for MCA-Linux users who want
865 to keep downward compatibility to older releases of the
866 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
869 If you like to have the lowest SCSI-id assigned as drive C:, as
870 modern SCSI-BIOSes do, which does not conform to the standard, but
871 is widespread and common in the PC-world of today, you must say N
872 here. If unsure, say Y.
874 config IBMMCA_SCSI_DEV_RESET
875 bool "Reset SCSI-devices at boottime"
876 depends on SCSI_IBMMCA
878 By default, SCSI-devices are reset when the machine is powered on.
879 However, some devices exist, like special-control-devices,
880 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
881 not reset when switched on. If you say Y here, each device connected
882 to your SCSI-bus will be issued a reset-command after it has been
883 probed, while the kernel is booting. This may cause problems with
884 more modern devices, like hard disks, which do not appreciate these
885 reset commands, and can cause your system to hang. So say Y only if
886 you know that one of your older devices needs it; N is the safe
890 tristate "IBM ServeRAID support"
891 depends on PCI && SCSI
893 This is support for the IBM ServeRAID hardware RAID controllers.
894 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
895 for more information. If this driver does not work correctly
896 without modification please contact the author by email at
897 <ipslinux@adaptec.com>.
899 To compile this driver as a module, choose M here: the
900 module will be called ips.
903 tristate "IBM Virtual SCSI support"
904 depends on PPC_PSERIES || PPC_ISERIES
906 This is the IBM POWER Virtual SCSI Client
908 To compile this driver as a module, choose M here: the
909 module will be called ibmvscsic.
912 tristate "Initio 9100U(W) support"
913 depends on PCI && SCSI
915 This is support for the Initio 91XXU(W) SCSI host adapter. Please
916 read the SCSI-HOWTO, available from
917 <http://www.tldp.org/docs.html#howto>.
919 To compile this driver as a module, choose M here: the
920 module will be called initio.
923 tristate "Initio INI-A100U2W support"
924 depends on PCI && SCSI
926 This is support for the Initio INI-A100U2W SCSI host adapter.
927 Please read the SCSI-HOWTO, available from
928 <http://www.tldp.org/docs.html#howto>.
930 To compile this driver as a module, choose M here: the
931 module will be called a100u2w.
934 tristate "IOMEGA parallel port (ppa - older drives)"
935 depends on SCSI && PARPORT_PC
937 This driver supports older versions of IOMEGA's parallel port ZIP
938 drive (a 100 MB removable media device).
940 Note that you can say N here if you have the SCSI version of the ZIP
941 drive: it will be supported automatically if you said Y to the
942 generic "SCSI disk support", above.
944 If you have the ZIP Plus drive or a more recent parallel port ZIP
945 drive (if the supplied cable with the drive is labeled "AutoDetect")
946 then you should say N here and Y to "IOMEGA parallel port (imm -
947 newer drives)", below.
949 For more information about this driver and how to use it you should
950 read the file <file:Documentation/scsi/ppa.txt>. You should also read
951 the SCSI-HOWTO, which is available from
952 <http://www.tldp.org/docs.html#howto>. If you use this driver,
953 you will still be able to use the parallel port for other tasks,
954 such as a printer; it is safe to compile both drivers into the
957 To compile this driver as a module, choose M here: the
958 module will be called ppa.
961 tristate "IOMEGA parallel port (imm - newer drives)"
962 depends on SCSI && PARPORT_PC
964 This driver supports newer versions of IOMEGA's parallel port ZIP
965 drive (a 100 MB removable media device).
967 Note that you can say N here if you have the SCSI version of the ZIP
968 drive: it will be supported automatically if you said Y to the
969 generic "SCSI disk support", above.
971 If you have the ZIP Plus drive or a more recent parallel port ZIP
972 drive (if the supplied cable with the drive is labeled "AutoDetect")
973 then you should say Y here; if you have an older ZIP drive, say N
974 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
976 For more information about this driver and how to use it you should
977 read the file <file:Documentation/scsi/ppa.txt>. You should also read
978 the SCSI-HOWTO, which is available from
979 <http://www.tldp.org/docs.html#howto>. If you use this driver,
980 you will still be able to use the parallel port for other tasks,
981 such as a printer; it is safe to compile both drivers into the
984 To compile this driver as a module, choose M here: the
985 module will be called imm.
987 config SCSI_IZIP_EPP16
988 bool "ppa/imm option - Use slow (but safe) EPP-16"
989 depends on SCSI_PPA || SCSI_IMM
991 EPP (Enhanced Parallel Port) is a standard for parallel ports which
992 allows them to act as expansion buses that can handle up to 64
995 Some parallel port chipsets are slower than their motherboard, and
996 so we have to control the state of the chipset's FIFO queue every
997 now and then to avoid data loss. This will be done if you say Y
1000 Generally, saying Y is the safe option and slows things down a bit.
1002 config SCSI_IZIP_SLOW_CTR
1003 bool "ppa/imm option - Assume slow parport control register"
1004 depends on SCSI_PPA || SCSI_IMM
1006 Some parallel ports are known to have excessive delays between
1007 changing the parallel port control register and good data being
1008 available on the parallel port data/status register. This option
1009 forces a small delay (1.0 usec to be exact) after changing the
1010 control register to let things settle out. Enabling this option may
1011 result in a big drop in performance but some very old parallel ports
1012 (found in 386 vintage machines) will not work properly.
1014 Generally, saying N is fine.
1016 config SCSI_NCR53C406A
1017 tristate "NCR53c406a SCSI support"
1018 depends on ISA && SCSI
1020 This is support for the NCR53c406a SCSI host adapter. For user
1021 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1022 in the kernel source. Also read the SCSI-HOWTO, available from
1023 <http://www.tldp.org/docs.html#howto>.
1025 To compile this driver as a module, choose M here: the
1026 module will be called NCR53c406.
1028 config SCSI_NCR_D700
1029 tristate "NCR Dual 700 MCA SCSI support"
1030 depends on MCA && SCSI
1031 select SCSI_SPI_ATTRS
1033 This is a driver for the MicroChannel Dual 700 card produced by
1034 NCR and commonly used in 345x/35xx/4100 class machines. It always
1035 tries to negotiate sync and uses tag command queueing.
1037 Unless you have an NCR manufactured machine, the chances are that
1038 you do not have this SCSI card, so say N.
1041 tristate "HP Lasi SCSI support for 53c700/710"
1042 depends on GSC && SCSI
1043 select SCSI_SPI_ATTRS
1045 This is a driver for the SCSI controller in the Lasi chip found in
1046 many PA-RISC workstations & servers. If you do not know whether you
1047 have a Lasi chip, it is safe to say "Y" here.
1049 config 53C700_LE_ON_BE
1051 depends on SCSI_LASI700
1054 config SCSI_SYM53C8XX_2
1055 tristate "SYM53C8XX Version 2 SCSI support"
1056 depends on PCI && SCSI
1057 select SCSI_SPI_ATTRS
1059 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1060 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1061 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1062 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1063 controllers; you need to use the Fusion MPT driver for that.
1065 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1068 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1069 int "DMA addressing mode"
1070 depends on SCSI_SYM53C8XX_2
1073 This option only applies to PCI-SCSI chips that are PCI DAC
1074 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1076 When set to 0, the driver will program the chip to only perform
1077 32-bit DMA. When set to 1, the chip will be able to perform DMA
1078 to addresses up to 1TB. When set to 2, the driver supports the
1079 full 64-bit DMA address range, but can only address 16 segments
1080 of 4 GB each. This limits the total addressable range to 64 GB.
1082 Most machines with less than 4GB of memory should use a setting
1083 of 0 for best performance. If your machine has 4GB of memory
1084 or more, you should set this option to 1 (the default).
1086 The still experimental value 2 (64 bit DMA addressing with 16
1087 x 4GB segments limitation) can be used on systems that require
1088 PCI address bits past bit 39 to be set for the addressing of
1089 memory using PCI DAC cycles.
1091 config SCSI_SYM53C8XX_DEFAULT_TAGS
1092 int "Default tagged command queue depth"
1093 depends on SCSI_SYM53C8XX_2
1096 This is the default value of the command queue depth the
1097 driver will announce to the generic SCSI layer for devices
1098 that support tagged command queueing. This value can be changed
1099 from the boot command line. This is a soft limit that cannot
1100 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1102 config SCSI_SYM53C8XX_MAX_TAGS
1103 int "Maximum number of queued commands"
1104 depends on SCSI_SYM53C8XX_2
1107 This option allows you to specify the maximum number of commands
1108 that can be queued to any device, when tagged command queuing is
1109 possible. The driver supports up to 256 queued commands per device.
1110 This value is used as a compiled-in hard limit.
1112 config SCSI_SYM53C8XX_MMIO
1113 bool "Use memory mapped IO"
1114 depends on SCSI_SYM53C8XX_2
1117 Memory mapped IO is faster than Port IO. Most people should
1118 answer Y here, but some machines may have problems. If you have
1119 to answer N here, please report the problem to the maintainer.
1122 tristate "IBM Power Linux RAID adapter support"
1123 depends on PCI && SCSI
1126 This driver supports the IBM Power Linux family RAID adapters.
1127 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1128 as IBM iSeries 5702, 5703, 5709, and 570A.
1130 config SCSI_IPR_TRACE
1131 bool "enable driver internal trace"
1134 If you say Y here, the driver will trace all commands issued
1135 to the adapter. Performance impact is minimal. Trace can be
1136 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1138 config SCSI_IPR_DUMP
1139 bool "enable adapter dump support"
1142 If you say Y here, the driver will support adapter crash dump.
1143 If you enable this support, the iprdump daemon can be used
1144 to capture adapter failure analysis information.
1147 tristate "Zalon SCSI support"
1148 depends on GSC && SCSI
1149 select SCSI_SPI_ATTRS
1151 The Zalon is a GSC/HSC bus interface chip that sits between the
1152 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1153 C110, J200, J210 and some D, K & R-class machines. It's also
1154 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1155 Say Y here if you have one of these machines or cards.
1157 config SCSI_NCR_Q720
1158 tristate "NCR Quad 720 MCA SCSI support"
1159 depends on MCA && SCSI
1160 select SCSI_SPI_ATTRS
1162 This is a driver for the MicroChannel Quad 720 card produced by
1163 NCR and commonly used in 345x/35xx/4100 class machines. It always
1164 tries to negotiate sync and uses tag command queueing.
1166 Unless you have an NCR manufactured machine, the chances are that
1167 you do not have this SCSI card, so say N.
1169 config SCSI_NCR53C8XX_DEFAULT_TAGS
1170 int " default tagged command queue depth"
1171 depends on SCSI_ZALON || SCSI_NCR_Q720
1174 "Tagged command queuing" is a feature of SCSI-2 which improves
1175 performance: the host adapter can send several SCSI commands to a
1176 device's queue even if previous commands haven't finished yet.
1177 Because the device is intelligent, it can optimize its operations
1178 (like head positioning) based on its own request queue. Some SCSI
1179 devices don't implement this properly; if you want to disable this
1180 feature, enter 0 or 1 here (it doesn't matter which).
1182 The default value is 8 and should be supported by most hard disks.
1183 This value can be overridden from the boot command line using the
1184 'tags' option as follows (example):
1185 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1186 4, set queue depth to 16 for target 2 and target 3 on controller 0
1187 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1189 The normal answer therefore is to go with the default 8 and to use
1190 a boot command line option for devices that need to use a different
1191 command queue depth.
1193 There is no safe option other than using good SCSI devices.
1195 config SCSI_NCR53C8XX_MAX_TAGS
1196 int " maximum number of queued commands"
1197 depends on SCSI_ZALON || SCSI_NCR_Q720
1200 This option allows you to specify the maximum number of commands
1201 that can be queued to any device, when tagged command queuing is
1202 possible. The default value is 32. Minimum is 2, maximum is 64.
1203 Modern hard disks are able to support 64 tags and even more, but
1204 do not seem to be faster when more than 32 tags are being used.
1206 So, the normal answer here is to go with the default value 32 unless
1207 you are using very large hard disks with large cache (>= 1 MB) that
1208 are able to take advantage of more than 32 tagged commands.
1210 There is no safe option and the default answer is recommended.
1212 config SCSI_NCR53C8XX_SYNC
1213 int " synchronous transfers frequency in MHz"
1214 depends on SCSI_ZALON || SCSI_NCR_Q720
1217 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1218 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1219 are respectively the maximum data transfer rates in mega-transfers
1220 per second for each class. For example, a FAST-20 Wide 16 device is
1221 able to transfer data at 20 million 16 bit packets per second for a
1222 total rate of 40 MB/s.
1224 You may specify 0 if you want to only use asynchronous data
1225 transfers. This is the safest and slowest option. Otherwise, specify
1226 a value between 5 and 80, depending on the capability of your SCSI
1227 controller. The higher the number, the faster the data transfer.
1228 Note that 80 should normally be ok since the driver decreases the
1229 value automatically according to the controller's capabilities.
1231 Your answer to this question is ignored for controllers with NVRAM,
1232 since the driver will get this information from the user set-up. It
1233 also can be overridden using a boot setup option, as follows
1234 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1235 for FAST-20 synchronous data transfer (20 mega-transfers per
1238 The normal answer therefore is not to go with the default but to
1239 select the maximum value 80 allowing the driver to use the maximum
1240 value supported by each controller. If this causes problems with
1241 your SCSI devices, you should come back and decrease the value.
1243 There is no safe option other than using good cabling, right
1244 terminations and SCSI conformant devices.
1246 config SCSI_NCR53C8XX_PROFILE
1247 bool " enable profiling"
1248 depends on SCSI_ZALON || SCSI_NCR_Q720
1250 This option allows you to enable profiling information gathering.
1251 These statistics are not very accurate due to the low frequency
1252 of the kernel clock (100 Hz on i386) and have performance impact
1253 on systems that use very fast devices.
1255 The normal answer therefore is N.
1257 config SCSI_NCR53C8XX_NO_DISCONNECT
1258 bool " not allow targets to disconnect"
1259 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1261 This option is only provided for safety if you suspect some SCSI
1262 device of yours to not support properly the target-disconnect
1263 feature. In that case, you would say Y here. In general however, to
1264 not allow targets to disconnect is not reasonable if there is more
1265 than 1 device on a SCSI bus. The normal answer therefore is N.
1267 config SCSI_MCA_53C9X
1268 tristate "NCR MCA 53C9x SCSI support"
1269 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1271 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1272 controller based on the NCR 53C94. This driver will allow use of
1273 the controller on the 3550, and very possibly others.
1275 To compile this driver as a module, choose M here: the
1276 module will be called mca_53c9x.
1279 tristate "PAS16 SCSI support"
1280 depends on ISA && SCSI
1281 select SCSI_SPI_ATTRS
1283 This is support for a SCSI host adapter. It is explained in section
1284 3.10 of the SCSI-HOWTO, available from
1285 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1286 of the box, you may have to change some settings in
1287 <file:drivers/scsi/pas16.h>.
1289 To compile this driver as a module, choose M here: the
1290 module will be called pas16.
1293 tristate "PSI240i support"
1294 depends on ISA && SCSI
1296 This is support for the PSI240i EIDE interface card which acts as a
1297 SCSI host adapter. Please read the SCSI-HOWTO, available from
1298 <http://www.tldp.org/docs.html#howto>.
1300 To compile this driver as a module, choose M here: the
1301 module will be called psi240i.
1303 config SCSI_QLOGIC_FAS
1304 tristate "Qlogic FAS SCSI support"
1305 depends on ISA && SCSI
1307 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1308 FastSCSI! cards as well as any other card based on the FASXX chip
1309 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1311 This driver does NOT support the PCI versions of these cards. The
1312 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1313 SCSI support"), below.
1315 Information about this driver is contained in
1316 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1317 SCSI-HOWTO, available from
1318 <http://www.tldp.org/docs.html#howto>.
1320 To compile this driver as a module, choose M here: the
1321 module will be called qlogicfas.
1323 config SCSI_QLOGIC_FC_FIRMWARE
1324 bool "Include loadable firmware in driver"
1325 depends on SCSI_QLOGIC_FC
1327 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1328 expanded LUN addressing and FcTape (FCP-2) support, in the
1329 qlogicfc driver. This is required on some platforms.
1331 config SCSI_QLOGIC_1280
1332 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1333 depends on PCI && SCSI
1335 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1337 To compile this driver as a module, choose M here: the
1338 module will be called qla1280.
1340 config SCSI_QLOGICPTI
1341 tristate "PTI Qlogic, ISP Driver"
1342 depends on SBUS && SCSI
1344 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1345 controllers are known under Solaris as qpti and in the openprom as
1346 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1347 driven by a different driver.
1349 To compile this driver as a module, choose M here: the
1350 module will be called qlogicpti.
1352 source "drivers/scsi/qla2xxx/Kconfig"
1355 tristate "Emulex LightPulse Fibre Channel Support"
1356 depends on PCI && SCSI
1357 select SCSI_FC_ATTRS
1359 This lpfc driver supports the Emulex LightPulse
1360 Family of Fibre Channel PCI host adapters.
1363 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1364 depends on X86 && ISA && SCSI && BROKEN
1366 These are 8-bit SCSI controllers; the ST-01 is also supported by
1367 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1368 available from <http://www.tldp.org/docs.html#howto>. If it
1369 doesn't work out of the box, you may have to change some settings in
1370 <file:drivers/scsi/seagate.h>.
1372 To compile this driver as a module, choose M here: the
1373 module will be called seagate.
1375 # definitely looks not 64bit safe:
1377 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1378 depends on (EISA || MCA) && SCSI
1379 select SCSI_SPI_ATTRS
1381 This driver for NCR53c710 based SCSI host adapters.
1383 It currently supports Compaq EISA cards and NCR MCA cards
1385 config 53C700_IO_MAPPED
1387 depends on SCSI_SIM710
1390 config SCSI_SYM53C416
1391 tristate "Symbios 53c416 SCSI support"
1392 depends on ISA && SCSI
1394 This is support for the sym53c416 SCSI host adapter, the SCSI
1395 adapter that comes with some HP scanners. This driver requires that
1396 the sym53c416 is configured first using some sort of PnP
1397 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1398 are using isapnp then you need to compile this driver as a module
1399 and then load it using insmod after isapnp has run. The parameters
1400 of the configured card(s) should be passed to the driver. The format
1403 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1405 To compile this driver as a module, choose M here: the
1406 module will be called sym53c416.
1409 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1410 depends on PCI && SCSI && EXPERIMENTAL
1412 This driver supports PCI SCSI host adapters based on the ASIC
1413 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1415 This driver works, but is still in experimental status. So better
1416 have a bootable disk and a backup in case of emergency.
1418 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1420 To compile this driver as a module, choose M here: the
1421 module will be called dc395x.
1424 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1425 depends on PCI && SCSI
1427 This driver supports PCI SCSI host adapters based on the Am53C974A
1428 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1429 PCscsi/PCnet (Am53/79C974) solutions.
1431 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1433 Note that this driver does NOT support Tekram DC390W/U/F, which are
1434 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1436 To compile this driver as a module, choose M here: the
1437 module will be called tmscsim.
1440 tristate "Trantor T128/T128F/T228 SCSI support"
1441 depends on ISA && SCSI
1442 select SCSI_SPI_ATTRS
1444 This is support for a SCSI host adapter. It is explained in section
1445 3.11 of the SCSI-HOWTO, available from
1446 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1447 of the box, you may have to change some settings in
1448 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1449 Adaptec, and some former Trantor products are being sold under the
1452 To compile this driver as a module, choose M here: the
1453 module will be called t128.
1456 tristate "UltraStor 14F/34F support"
1457 depends on ISA && SCSI && ISA_DMA_API
1459 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1460 The source at <file:drivers/scsi/u14-34f.c> contains some
1461 information about this hardware. If the driver doesn't work out of
1462 the box, you may have to change some settings in
1463 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1464 <http://www.tldp.org/docs.html#howto>. Note that there is also
1465 another driver for the same hardware: "UltraStor SCSI support",
1466 below. You should say Y to both only if you want 24F support as
1469 To compile this driver as a module, choose M here: the
1470 module will be called u14-34f.
1472 config SCSI_U14_34F_TAGGED_QUEUE
1473 bool "enable tagged command queueing"
1474 depends on SCSI_U14_34F
1476 This is a feature of SCSI-2 which improves performance: the host
1477 adapter can send several SCSI commands to a device's queue even if
1478 previous commands haven't finished yet.
1479 This is equivalent to the "u14-34f=tc:y" boot option.
1481 config SCSI_U14_34F_LINKED_COMMANDS
1482 bool "enable elevator sorting"
1483 depends on SCSI_U14_34F
1485 This option enables elevator sorting for all probed SCSI disks and
1486 CD-ROMs. It definitely reduces the average seek distance when doing
1487 random seeks, but this does not necessarily result in a noticeable
1488 performance improvement: your mileage may vary...
1489 This is equivalent to the "u14-34f=lc:y" boot option.
1491 config SCSI_U14_34F_MAX_TAGS
1492 int "maximum number of queued commands"
1493 depends on SCSI_U14_34F
1496 This specifies how many SCSI commands can be maximally queued for
1497 each probed SCSI device. You should reduce the default value of 8
1498 only if you have disks with buggy or limited tagged command support.
1499 Minimum is 2 and maximum is 14. This value is also the window size
1500 used by the elevator sorting option above. The effective value used
1501 by the driver for each probed SCSI device is reported at boot time.
1502 This is equivalent to the "u14-34f=mq:8" boot option.
1504 config SCSI_ULTRASTOR
1505 tristate "UltraStor SCSI support"
1506 depends on X86 && ISA && SCSI
1508 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1509 adapter family. This driver is explained in section 3.12 of the
1510 SCSI-HOWTO, available from
1511 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1512 of the box, you may have to change some settings in
1513 <file:drivers/scsi/ultrastor.h>.
1515 Note that there is also another driver for the same hardware:
1516 "UltraStor 14F/34F support", above.
1518 To compile this driver as a module, choose M here: the
1519 module will be called ultrastor.
1522 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1523 depends on PCI && SCSI && !64BIT
1525 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1526 SCSI host adapter. Please read the SCSI-HOWTO, available from
1527 <http://www.tldp.org/docs.html#howto>.
1529 To compile this driver as a module, choose M here: the
1530 module will be called nsp32.
1533 tristate "SCSI debugging host simulator"
1536 This is a host adapter simulator that can simulate multiple hosts
1537 each with multiple dummy SCSI devices (disks). It defaults to one
1538 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1539 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1540 dummy disks are simulated, they share the same kernel RAM for
1541 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1542 information. This driver is primarily of use to those testing the
1543 SCSI and block subsystems. If unsure, say N.
1546 tristate "MESH (Power Mac internal SCSI) support"
1547 depends on PPC32 && PPC_PMAC && SCSI
1549 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1550 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1551 other Power Macintoshes do). Say Y to include support for this SCSI
1554 To compile this driver as a module, choose M here: the
1555 module will be called mesh.
1557 config SCSI_MESH_SYNC_RATE
1558 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1559 depends on SCSI_MESH
1562 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1563 drives a bus which is entirely internal to the machine (such as the
1564 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1565 operation at up to 10 MB/s. On machines where the SCSI bus
1566 controlled by the MESH can have external devices connected, it is
1567 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1568 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1569 to disable synchronous operation.
1571 config SCSI_MESH_RESET_DELAY_MS
1572 int "initial bus reset delay (ms) (0 = no reset)"
1573 depends on SCSI_MESH
1576 config SCSI_MAC53C94
1577 tristate "53C94 (Power Mac external SCSI) support"
1578 depends on PPC32 && PPC_PMAC && SCSI
1580 On Power Macintoshes (and clones) with two SCSI buses, the external
1581 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1582 machines which only have one SCSI bus, such as the 7200, also use
1583 the 53C94. Say Y to include support for the 53C94.
1585 To compile this driver as a module, choose M here: the
1586 module will be called mac53c94.
1588 source "drivers/scsi/arm/Kconfig"
1591 bool "MIPS JAZZ FAS216 SCSI support"
1592 depends on MACH_JAZZ && SCSI
1594 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1595 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1599 tristate "A3000 WD33C93A support"
1600 depends on AMIGA && SCSI
1602 If you have an Amiga 3000 and have SCSI devices connected to the
1603 built-in SCSI controller, say Y. Otherwise, say N.
1605 To compile this driver as a module, choose M here: the
1606 module will be called wd33c93.
1609 tristate "A2091/A590 WD33C93A support"
1610 depends on ZORRO && SCSI
1612 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1615 To compile this driver as a module, choose M here: the
1616 module will be called wd33c93.
1619 tristate "GVP Series II WD33C93A support"
1620 depends on ZORRO && SCSI
1622 If you have a Great Valley Products Series II SCSI controller,
1623 answer Y. Also say Y if you have a later model of GVP SCSI
1624 controller (such as the GVP A4008 or a Combo board). Otherwise,
1625 answer N. This driver does NOT work for the T-Rex series of
1626 accelerators from TekMagic and GVP-M.
1628 To compile this driver as a module, choose M here: the
1629 module will be called gvp11.
1631 config CYBERSTORM_SCSI
1632 tristate "CyberStorm SCSI support"
1633 depends on ZORRO && SCSI
1635 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1636 accelerator board and the optional Cyberstorm SCSI controller,
1637 answer Y. Otherwise, say N.
1639 config CYBERSTORMII_SCSI
1640 tristate "CyberStorm Mk II SCSI support"
1641 depends on ZORRO && SCSI
1643 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1644 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1648 tristate "Blizzard 2060 SCSI support"
1649 depends on ZORRO && SCSI
1651 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1652 and want to use the onboard SCSI controller, say Y. Otherwise,
1656 tristate "Blizzard 1230IV/1260 SCSI support"
1657 depends on ZORRO && SCSI
1659 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1660 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1663 config FASTLANE_SCSI
1664 tristate "Fastlane SCSI support"
1665 depends on ZORRO && SCSI
1667 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1668 one in the near future, say Y to this question. Otherwise, say N.
1670 config SCSI_AMIGA7XX
1671 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1672 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1674 Support for various NCR53c710-based SCSI controllers on the Amiga.
1676 - the builtin SCSI controller on the Amiga 4000T,
1677 - the Amiga 4091 Zorro III SCSI-2 controller,
1678 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1680 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1681 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1682 accelerator card for the Amiga 1200,
1683 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1684 Note that all of the above SCSI controllers, except for the builtin
1685 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1686 bus, so you also have to enable Zorro bus support if you want to use
1690 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1691 depends on ZORRO && SCSI && EXPERIMENTAL
1693 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1694 Y to this question. If you're in doubt about whether you have one,
1696 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1699 tristate "Atari native SCSI support"
1700 depends on ATARI && SCSI && BROKEN
1701 select SCSI_SPI_ATTRS
1703 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1704 Falcon, ...) say Y to get it supported. Of course also, if you have
1705 a compatible SCSI controller (e.g. for Medusa).
1707 To compile this driver as a module, choose M here: the
1708 module will be called atari_scsi.
1710 This driver supports both styles of NCR integration into the
1711 system: the TT style (separate DMA), and the Falcon style (via
1712 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1713 in the Hades (without DMA).
1715 config ATARI_SCSI_TOSHIBA_DELAY
1716 bool "Long delays for Toshiba CD-ROMs"
1717 depends on ATARI_SCSI
1719 This option increases the delay after a SCSI arbitration to
1720 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1721 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1722 would impact performance a bit, so say N.
1724 config ATARI_SCSI_RESET_BOOT
1725 bool "Reset SCSI-devices at boottime"
1726 depends on ATARI_SCSI
1728 Reset the devices on your Atari whenever it boots. This makes the
1729 boot process fractionally longer but may assist recovery from errors
1730 that leave the devices with SCSI operations partway completed.
1733 bool "Hades SCSI DMA emulator"
1734 depends on ATARI_SCSI && HADES
1736 This option enables code which emulates the TT SCSI DMA chip on the
1737 Hades. This increases the SCSI transfer rates at least ten times
1738 compared to PIO transfers.
1741 bool "Macintosh NCR5380 SCSI"
1742 depends on MAC && SCSI=y
1743 select SCSI_SPI_ATTRS
1745 This is the NCR 5380 SCSI controller included on most of the 68030
1746 based Macintoshes. If you have one of these say Y and read the
1747 SCSI-HOWTO, available from
1748 <http://www.tldp.org/docs.html#howto>.
1751 tristate "Macintosh NCR53c9[46] SCSI"
1752 depends on MAC && SCSI
1754 This is the NCR 53c9x SCSI controller found on most of the 68040
1755 based Macintoshes. If you have one of these say Y and read the
1756 SCSI-HOWTO, available from
1757 <http://www.tldp.org/docs.html#howto>.
1759 To compile this driver as a module, choose M here: the
1760 module will be called mac_esp.
1763 bool "WD33C93 SCSI driver for MVME147"
1764 depends on MVME147 && SCSI=y
1765 select SCSI_SPI_ATTRS
1767 Support for the on-board SCSI controller on the Motorola MVME147
1768 single-board computer.
1771 bool "NCR53C710 SCSI driver for MVME16x"
1772 depends on MVME16x && SCSI && BROKEN
1773 select SCSI_SPI_ATTRS
1775 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1776 SCSI controller chip. Almost everyone using one of these boards
1777 will want to say Y to this question.
1779 config BVME6000_SCSI
1780 bool "NCR53C710 SCSI driver for BVME6000"
1781 depends on BVME6000 && SCSI && BROKEN
1782 select SCSI_SPI_ATTRS
1784 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1785 SCSI controller chip. Almost everyone using one of these boards
1786 will want to say Y to this question.
1788 config SCSI_NCR53C7xx_FAST
1789 bool "allow FAST-SCSI [10MHz]"
1790 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1792 This will enable 10MHz FAST-SCSI transfers with your host
1793 adapter. Some systems have problems with that speed, so it's safest
1797 tristate "Sun3 NCR5380 SCSI"
1798 depends on SUN3 && SCSI && BROKEN
1799 select SCSI_SPI_ATTRS
1801 This option will enable support for the OBIO (onboard io) NCR5380
1802 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1803 "Sun3" type VME scsi controllers also based on the NCR5380.
1804 General Linux information on the Sun 3 series (now discontinued)
1805 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1808 bool "Sun3x ESP SCSI"
1809 depends on SUN3X && SCSI=y
1811 The ESP was an on-board SCSI controller used on Sun 3/80
1812 machines. Say Y here to compile in support for it.
1815 tristate "Sparc ESP Scsi Driver"
1816 depends on SBUS && SCSI
1818 This is the driver for the Sun ESP SCSI host adapter. The ESP
1819 chipset is present in most SPARC SBUS-based computers.
1821 To compile this driver as a module, choose M here: the
1822 module will be called esp.
1824 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1827 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1828 depends on S390 && QDIO && SCSI
1829 select SCSI_FC_ATTRS
1831 If you want to access SCSI devices attached to your IBM eServer
1832 zSeries by means of Fibre Channel interfaces say Y.
1833 For details please refer to the documentation provided by IBM at
1834 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1836 This driver is also available as a module. This module will be
1837 called zfcp. If you want to compile it as a module, say M here
1838 and read <file:Documentation/modules.txt>.
1842 source "drivers/scsi/pcmcia/Kconfig"