1 menu "SCSI device support"
4 tristate "RAID Transport Class"
11 tristate "SCSI device support"
13 select SCSI_DMA if HAS_DMA
15 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
16 any other SCSI device under Linux, say Y and make sure that you know
17 the name of your SCSI host adapter (the card inside your computer
18 that "speaks" the SCSI protocol, also called SCSI controller),
19 because you will be asked for it.
21 You also need to say Y here if you have a device which speaks
22 the SCSI protocol. Examples of this include the parallel port
23 version of the IOMEGA ZIP drive, USB storage devices, Fibre
24 Channel, FireWire storage and the IDE-SCSI emulation driver.
26 To compile this driver as a module, choose M here and read
27 <file:Documentation/scsi/scsi.txt>.
28 The module will be called scsi_mod.
30 However, do not compile this as a module if your root file system
31 (the one containing the directory /) is located on a SCSI device.
38 tristate "SCSI target support"
39 depends on SCSI && EXPERIMENTAL
41 If you want to use SCSI target mode drivers enable this option.
42 If you choose M, the module will be called scsi_tgt.
50 bool "legacy /proc/scsi/ support"
51 depends on SCSI && PROC_FS
54 This option enables support for the various files in
55 /proc/scsi. In Linux 2.6 this has been superseded by
56 files in sysfs but many legacy applications rely on this.
60 comment "SCSI support type (disk, tape, CD-ROM)"
64 tristate "SCSI disk support"
67 If you want to use SCSI hard disks, Fibre Channel disks,
68 USB storage or the SCSI or parallel port version of
69 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
70 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
71 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
74 To compile this driver as a module, choose M here and read
75 <file:Documentation/scsi/scsi.txt>.
76 The module will be called sd_mod.
78 Do not compile this driver as a module if your root file system
79 (the one containing the directory /) is located on a SCSI disk.
80 In this case, do not compile the driver for your SCSI host adapter
81 (below) as a module either.
84 tristate "SCSI tape support"
87 If you want to use a SCSI tape drive under Linux, say Y and read the
88 SCSI-HOWTO, available from
89 <http://www.tldp.org/docs.html#howto>, and
90 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
93 To compile this driver as a module, choose M here and read
94 <file:Documentation/scsi/scsi.txt>. The module will be called st.
97 tristate "SCSI OnStream SC-x0 tape support"
100 The OnStream SC-x0 SCSI tape drives cannot be driven by the
101 standard st driver, but instead need this special osst driver and
102 use the /dev/osstX char device nodes (major 206). Via usb-storage
103 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
104 as well. Note that there is also a second generation of OnStream
105 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
106 tapes (QIC-157) and can be driven by the standard driver st.
107 For more information, you may have a look at the SCSI-HOWTO
108 <http://www.tldp.org/docs.html#howto> and
109 <file:Documentation/scsi/osst.txt> in the kernel source.
110 More info on the OnStream driver may be found on
111 <http://linux1.onstream.nl/test/>
112 Please also have a look at the standard st docu, as most of it
113 applies to osst as well.
115 To compile this driver as a module, choose M here and read
116 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
119 tristate "SCSI CDROM support"
122 If you want to use a SCSI or FireWire CD-ROM under Linux,
123 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
124 <http://www.tldp.org/docs.html#howto>. Also make sure to say
125 Y or M to "ISO 9660 CD-ROM file system support" later.
127 To compile this driver as a module, choose M here and read
128 <file:Documentation/scsi/scsi.txt>.
129 The module will be called sr_mod.
131 config BLK_DEV_SR_VENDOR
132 bool "Enable vendor-specific extensions (for SCSI CDROM)"
133 depends on BLK_DEV_SR
135 This enables the usage of vendor specific SCSI commands. This is
136 required to support multisession CDs with old NEC/TOSHIBA cdrom
137 drives (and HP Writers). If you have such a drive and get the first
138 session only, try saying Y here; everybody else says N.
141 tristate "SCSI generic support"
144 If you want to use SCSI scanners, synthesizers or CD-writers or just
145 about anything having "SCSI" in its name other than hard disks,
146 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
147 directly, so you need some additional software which knows how to
148 talk to these devices using the SCSI protocol:
150 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
151 writer software look at Cdrtools
152 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
153 and for burning a "disk at once": CDRDAO
154 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
155 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
156 For other devices, it's possible that you'll have to write the
157 driver software yourself. Please read the file
158 <file:Documentation/scsi/scsi-generic.txt> for more information.
160 To compile this driver as a module, choose M here and read
161 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
166 tristate "SCSI media changer support"
169 This is a driver for SCSI media changers. Most common devices are
170 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
171 don't need this for those tiny 6-slot cdrom changers. Media
172 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
173 If you have such hardware and want to use it with linux, say Y
174 here. Check <file:Documentation/scsi-changer.txt> for details.
176 If you want to compile this as a module ( = code which can be
177 inserted in and removed from the running kernel whenever you want),
178 say M here and read <file:Documentation/kbuild/modules.txt> and
179 <file:Documentation/scsi.txt>. The module will be called ch.o.
183 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
186 config SCSI_MULTI_LUN
187 bool "Probe all LUNs on each SCSI device"
190 If you have a SCSI device that supports more than one LUN (Logical
191 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
192 can say Y here to force the SCSI driver to probe for multiple LUNs.
193 A SCSI device with multiple LUNs acts logically like multiple SCSI
194 devices. The vast majority of SCSI devices have only one LUN, and
195 so most people can say N here. The max_luns boot/module parameter
196 allows to override this setting.
198 config SCSI_CONSTANTS
199 bool "Verbose SCSI error reporting (kernel size +=12K)"
202 The error messages regarding your SCSI hardware will be easier to
203 understand if you say Y here; it will enlarge your kernel by about
204 12 KB. If in doubt, say Y.
207 bool "SCSI logging facility"
210 This turns on a logging facility that can be used to debug a number
211 of SCSI related problems.
213 If you say Y here, no logging output will appear by default, but you
214 can enable logging by saying Y to "/proc file system support" and
215 "Sysctl support" below and executing the command
217 echo "scsi log token [level]" > /proc/scsi/scsi
219 at boot time after the /proc file system has been mounted.
221 There are a number of things that can be used for 'token' (you can
222 find them in the source: <file:drivers/scsi/scsi.c>), and this
223 allows you to select the types of information you want, and the
224 level allows you to select the level of verbosity.
226 If you say N here, it may be harder to track down some types of SCSI
227 problems. If you say Y here your kernel will be somewhat larger, but
228 there should be no noticeable performance impact as long as you have
231 config SCSI_SCAN_ASYNC
232 bool "Asynchronous SCSI scanning"
235 The SCSI subsystem can probe for devices while the rest of the
236 system continues booting, and even probe devices on different
237 busses in parallel, leading to a significant speed-up.
239 If you have built SCSI as modules, enabling this option can
240 be a problem as the devices may not have been found by the
241 time your system expects them to have been. You can load the
242 scsi_wait_scan module to ensure that all scans have completed.
243 If you build your SCSI drivers into the kernel, then everything
244 will work fine if you say Y here.
246 You can override this choice by specifying "scsi_mod.scan=sync"
247 or async on the kernel's command line.
249 config SCSI_WAIT_SCAN
255 menu "SCSI Transports"
258 config SCSI_SPI_ATTRS
259 tristate "Parallel SCSI (SPI) Transport Attributes"
262 If you wish to export transport-specific information about
263 each attached SCSI device to sysfs, say Y. Otherwise, say N.
266 tristate "FiberChannel Transport Attributes"
270 If you wish to export transport-specific information about
271 each attached FiberChannel device to sysfs, say Y.
274 config SCSI_ISCSI_ATTRS
275 tristate "iSCSI Transport Attributes"
276 depends on SCSI && NET
278 If you wish to export transport-specific information about
279 each attached iSCSI device to sysfs, say Y.
282 config SCSI_SAS_ATTRS
283 tristate "SAS Transport Attributes"
286 If you wish to export transport-specific information about
287 each attached SAS device to sysfs, say Y.
289 source "drivers/scsi/libsas/Kconfig"
293 menu "SCSI low-level drivers"
297 tristate "iSCSI Initiator over TCP/IP"
298 depends on SCSI && INET
302 select SCSI_ISCSI_ATTRS
304 The iSCSI Driver provides a host with the ability to access storage
305 through an IP network. The driver uses the iSCSI protocol to transport
306 SCSI requests and responses over a TCP/IP network between the host
307 (the "initiator") and "targets". Architecturally, the iSCSI driver
308 combines with the host's TCP/IP stack, network drivers, and Network
309 Interface Card (NIC) to provide the same functions as a SCSI or a
310 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
312 To compile this driver as a module, choose M here: the
313 module will be called iscsi_tcp.
315 The userspace component needed to initialize the driver, documentation,
316 and sample configuration files can be found here:
318 http://linux-iscsi.sf.net
321 tristate "SGI WD93C93 SCSI Driver"
322 depends on SGI_IP22 && SCSI
324 If you have a Western Digital WD93 SCSI controller on
325 an SGI MIPS system, say Y. Otherwise, say N.
328 tristate "DEC NCR53C94 Scsi Driver"
329 depends on MACH_DECSTATION && SCSI && TC
331 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
332 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
335 tristate "DEC SII Scsi Driver"
336 depends on MACH_DECSTATION && SCSI && 32BIT
338 config BLK_DEV_3W_XXXX_RAID
339 tristate "3ware 5/6/7/8xxx ATA-RAID support"
340 depends on PCI && SCSI
342 3ware is the only hardware ATA-Raid product in Linux to date.
343 This card is 2,4, or 8 channel master mode support only.
344 SCSI support required!!!
346 <http://www.3ware.com/>
348 Please read the comments at the top of
349 <file:drivers/scsi/3w-xxxx.c>.
352 tristate "3ware 9xxx SATA-RAID support"
353 depends on PCI && SCSI
355 This driver supports the 9000 series 3ware SATA-RAID cards.
357 <http://www.amcc.com>
359 Please read the comments at the top of
360 <file:drivers/scsi/3w-9xxx.c>.
362 config SCSI_7000FASST
363 tristate "7000FASST SCSI support"
364 depends on ISA && SCSI && ISA_DMA_API
366 This driver supports the Western Digital 7000 SCSI host adapter
367 family. Some information is in the source:
368 <file:drivers/scsi/wd7000.c>.
370 To compile this driver as a module, choose M here: the
371 module will be called wd7000.
374 tristate "ACARD SCSI support"
375 depends on PCI && SCSI
377 This driver supports the ACARD SCSI host adapter.
378 Support Chip <ATP870 ATP876 ATP880 ATP885>
379 To compile this driver as a module, choose M here: the
380 module will be called atp870u.
383 tristate "Adaptec AHA152X/2825 support"
384 depends on ISA && SCSI && !64BIT
385 select SCSI_SPI_ATTRS
387 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
388 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
389 must be manually specified in this case.
391 It is explained in section 3.3 of the SCSI-HOWTO, available from
392 <http://www.tldp.org/docs.html#howto>. You might also want to
393 read the file <file:Documentation/scsi/aha152x.txt>.
395 To compile this driver as a module, choose M here: the
396 module will be called aha152x.
399 tristate "Adaptec AHA1542 support"
400 depends on ISA && SCSI && ISA_DMA_API
402 This is support for a SCSI host adapter. It is explained in section
403 3.4 of the SCSI-HOWTO, available from
404 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
405 purchased by Adaptec, and some former Trantor products are being
406 sold under the Adaptec name. If it doesn't work out of the box, you
407 may have to change some settings in <file:drivers/scsi/aha1542.h>.
409 To compile this driver as a module, choose M here: the
410 module will be called aha1542.
413 tristate "Adaptec AHA1740 support"
414 depends on EISA && SCSI
416 This is support for a SCSI host adapter. It is explained in section
417 3.5 of the SCSI-HOWTO, available from
418 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
419 of the box, you may have to change some settings in
420 <file:drivers/scsi/aha1740.h>.
422 To compile this driver as a module, choose M here: the
423 module will be called aha1740.
426 tristate "Adaptec AACRAID support"
427 depends on SCSI && PCI
429 This driver supports a variety of Dell, HP, Adaptec, IBM and
430 ICP storage products. For a list of supported products, refer
431 to <file:Documentation/scsi/aacraid.txt>.
433 To compile this driver as a module, choose M here: the module
434 will be called aacraid.
437 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
439 config SCSI_AIC7XXX_OLD
440 tristate "Adaptec AIC7xxx support (old driver)"
441 depends on (ISA || EISA || PCI ) && SCSI
443 WARNING This driver is an older aic7xxx driver and is no longer
444 under active development. Adaptec, Inc. is writing a new driver to
445 take the place of this one, and it is recommended that whenever
446 possible, people should use the new Adaptec written driver instead
447 of this one. This driver will eventually be phased out entirely.
449 This is support for the various aic7xxx based Adaptec SCSI
450 controllers. These include the 274x EISA cards; 284x VLB cards;
451 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
452 motherboard based SCSI controllers from Adaptec. It does not support
453 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
454 support them. It does not support the 2920 cards from Adaptec that
455 use the Future Domain SCSI controller chip. For those cards, you
456 need the "Future Domain 16xx SCSI support" driver.
458 In general, if the controller is based on an Adaptec SCSI controller
459 chip from the aic777x series or the aic78xx series, this driver
460 should work. The only exception is the 7810 which is specifically
461 not supported (that's the RAID controller chip on the AAA-13x
464 Note that the AHA2920 SCSI host adapter is *not* supported by this
465 driver; choose "Future Domain 16xx SCSI support" instead if you have
468 Information on the configuration options for this controller can be
469 found by checking the help file for each of the available
470 configuration options. You should read
471 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
472 contacting the maintainer with any questions. The SCSI-HOWTO,
473 available from <http://www.tldp.org/docs.html#howto>, can also
476 To compile this driver as a module, choose M here: the
477 module will be called aic7xxx_old.
479 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
480 source "drivers/scsi/aic94xx/Kconfig"
482 # All the I2O code and drivers do not seem to be 64bit safe.
484 tristate "Adaptec I2O RAID support "
485 depends on !64BIT && SCSI && PCI
487 This driver supports all of Adaptec's I2O based RAID controllers as
488 well as the DPT SmartRaid V cards. This is an Adaptec maintained
489 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
491 To compile this driver as a module, choose M here: the
492 module will be called dpt_i2o.
495 tristate "AdvanSys SCSI support"
497 depends on ISA || EISA || PCI
498 depends on BROKEN || X86_32
500 This is a driver for all SCSI host adapters manufactured by
501 AdvanSys. It is documented in the kernel source in
502 <file:drivers/scsi/advansys.c>.
504 To compile this driver as a module, choose M here: the
505 module will be called advansys.
508 tristate "Always IN2000 SCSI support"
509 depends on ISA && SCSI
511 This is support for an ISA bus SCSI host adapter. You'll find more
512 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
513 out of the box, you may have to change the jumpers for IRQ or
516 To compile this driver as a module, choose M here: the
517 module will be called in2000.
520 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
521 depends on PCI && SCSI
523 This driver supports all of ARECA's SATA RAID controller cards.
524 This is an ARECA-maintained driver by Erich Chen.
525 If you have any problems, please mail to: < erich@areca.com.tw >
526 Areca supports Linux RAID config tools.
528 < http://www.areca.com.tw >
530 To compile this driver as a module, choose M here: the
531 module will be called arcmsr (modprobe arcmsr).
533 source "drivers/scsi/megaraid/Kconfig.megaraid"
536 tristate "HighPoint RocketRAID 3xxx Controller support"
537 depends on SCSI && PCI
539 This option enables support for HighPoint RocketRAID 3xxx
542 To compile this driver as a module, choose M here; the module
543 will be called hptiop. If unsure, say N.
546 tristate "BusLogic SCSI support"
547 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
549 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
550 Adapters. Consult the SCSI-HOWTO, available from
551 <http://www.tldp.org/docs.html#howto>, and the files
552 <file:Documentation/scsi/BusLogic.txt> and
553 <file:Documentation/scsi/FlashPoint.txt> for more information.
555 To compile this driver as a module, choose M here: the
556 module will be called BusLogic.
558 config SCSI_OMIT_FLASHPOINT
559 bool "Omit FlashPoint support"
560 depends on SCSI_BUSLOGIC
562 This option allows you to omit the FlashPoint support from the
563 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
564 substantial, so users of MultiMaster Host Adapters may wish to omit
568 tristate "DMX3191D SCSI support"
569 depends on PCI && SCSI
570 select SCSI_SPI_ATTRS
572 This is support for Domex DMX3191D SCSI Host Adapters.
574 To compile this driver as a module, choose M here: the
575 module will be called dmx3191d.
578 tristate "DTC3180/3280 SCSI support"
579 depends on ISA && SCSI
580 select SCSI_SPI_ATTRS
582 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
583 the SCSI-HOWTO, available from
584 <http://www.tldp.org/docs.html#howto>, and the file
585 <file:Documentation/scsi/dtc3x80.txt>.
587 To compile this driver as a module, choose M here: the
588 module will be called dtc.
591 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
592 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
594 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
595 ISA and all EISA I/O addresses are probed looking for the "EATA"
596 signature. The addresses of all the PCI SCSI controllers reported
597 by the PCI subsystem are probed as well.
599 You want to read the start of <file:drivers/scsi/eata.c> and the
600 SCSI-HOWTO, available from
601 <http://www.tldp.org/docs.html#howto>.
603 To compile this driver as a module, choose M here: the
604 module will be called eata.
606 config SCSI_EATA_TAGGED_QUEUE
607 bool "enable tagged command queueing"
610 This is a feature of SCSI-2 which improves performance: the host
611 adapter can send several SCSI commands to a device's queue even if
612 previous commands haven't finished yet.
613 This is equivalent to the "eata=tc:y" boot option.
615 config SCSI_EATA_LINKED_COMMANDS
616 bool "enable elevator sorting"
619 This option enables elevator sorting for all probed SCSI disks and
620 CD-ROMs. It definitely reduces the average seek distance when doing
621 random seeks, but this does not necessarily result in a noticeable
622 performance improvement: your mileage may vary...
623 This is equivalent to the "eata=lc:y" boot option.
625 config SCSI_EATA_MAX_TAGS
626 int "maximum number of queued commands"
630 This specifies how many SCSI commands can be maximally queued for
631 each probed SCSI device. You should reduce the default value of 16
632 only if you have disks with buggy or limited tagged command support.
633 Minimum is 2 and maximum is 62. This value is also the window size
634 used by the elevator sorting option above. The effective value used
635 by the driver for each probed SCSI device is reported at boot time.
636 This is equivalent to the "eata=mq:8" boot option.
639 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
640 depends on (ISA || EISA || PCI) && SCSI && BROKEN
642 This driver supports all EATA-PIO protocol compliant SCSI Host
643 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
644 host adapters could also use this driver but are discouraged from
645 doing so, since this driver only supports hard disks and lacks
646 numerous features. You might want to have a look at the SCSI-HOWTO,
647 available from <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here: the
650 module will be called eata_pio.
652 config SCSI_FUTURE_DOMAIN
653 tristate "Future Domain 16xx SCSI/AHA-2920A support"
654 depends on (ISA || PCI) && SCSI
656 This is support for Future Domain's 16-bit SCSI host adapters
657 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
658 other adapters based on the Future Domain chipsets (Quantum
659 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
660 It is explained in section 3.7 of the SCSI-HOWTO, available from
661 <http://www.tldp.org/docs.html#howto>.
663 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
664 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
665 controller support"). This Future Domain driver works with the older
666 Adaptec AHA-2920A boards with a Future Domain chip on them.
668 To compile this driver as a module, choose M here: the
669 module will be called fdomain.
672 tristate "Future Domain MCS-600/700 SCSI support"
673 depends on MCA_LEGACY && SCSI
675 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
676 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
677 is identical to the MCS 700 and hence also supported by this driver.
678 This driver also supports the Reply SB16/SCSI card (the SCSI part).
679 It supports multiple adapters in the same system.
681 To compile this driver as a module, choose M here: the
682 module will be called fd_mcs.
685 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
686 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
688 Formerly called GDT SCSI Disk Array Controller Support.
690 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
691 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
692 in the kernel source in <file:drivers/scsi/gdth.c> and
693 <file:drivers/scsi/gdth.h.>
695 To compile this driver as a module, choose M here: the
696 module will be called gdth.
698 config SCSI_GENERIC_NCR5380
699 tristate "Generic NCR5380/53c400 SCSI PIO support"
700 depends on ISA && SCSI
701 select SCSI_SPI_ATTRS
703 This is a driver for the old NCR 53c80 series of SCSI controllers
704 on boards using PIO. Most boards such as the Trantor T130 fit this
705 category, along with a large number of ISA 8bit controllers shipped
706 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
707 you should select the specific driver for that card rather than
708 generic 5380 support.
710 It is explained in section 3.8 of the SCSI-HOWTO, available from
711 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
712 of the box, you may have to change some settings in
713 <file:drivers/scsi/g_NCR5380.h>.
715 To compile this driver as a module, choose M here: the
716 module will be called g_NCR5380.
718 config SCSI_GENERIC_NCR5380_MMIO
719 tristate "Generic NCR5380/53c400 SCSI MMIO support"
720 depends on ISA && SCSI
721 select SCSI_SPI_ATTRS
723 This is a driver for the old NCR 53c80 series of SCSI controllers
724 on boards using memory mapped I/O.
725 It is explained in section 3.8 of the SCSI-HOWTO, available from
726 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
727 of the box, you may have to change some settings in
728 <file:drivers/scsi/g_NCR5380.h>.
730 To compile this driver as a module, choose M here: the
731 module will be called g_NCR5380_mmio.
733 config SCSI_GENERIC_NCR53C400
734 bool "Enable NCR53c400 extensions"
735 depends on SCSI_GENERIC_NCR5380
737 This enables certain optimizations for the NCR53c400 SCSI cards.
738 You might as well try it out. Note that this driver will only probe
739 for the Trantor T130B in its default configuration; you might have
740 to pass a command line option to the kernel at boot time if it does
741 not detect your card. See the file
742 <file:Documentation/scsi/g_NCR5380.txt> for details.
745 tristate "IBMMCA SCSI support"
746 depends on MCA && SCSI
748 This is support for the IBM SCSI adapter found in many of the PS/2
749 series computers. These machines have an MCA bus, so you need to
750 answer Y to "MCA support" as well and read
751 <file:Documentation/mca.txt>.
753 If the adapter isn't found during boot (a common problem for models
754 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
755 option, where <pun> is the id of the SCSI subsystem (usually 7, but
756 if that doesn't work check your reference diskette). Owners of
757 model 95 with a LED-matrix-display can in addition activate some
758 activity info like under OS/2, but more informative, by setting
759 'ibmmcascsi=display' as an additional kernel parameter. Try "man
760 bootparam" or see the documentation of your boot loader about how to
761 pass options to the kernel.
763 To compile this driver as a module, choose M here: the
764 module will be called ibmmca.
766 config IBMMCA_SCSI_ORDER_STANDARD
767 bool "Standard SCSI-order"
768 depends on SCSI_IBMMCA
770 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
771 are assigned to the drive letters, starting with the lowest SCSI-id
772 (physical number -- pun) to be drive C:, as seen from DOS and
773 similar operating systems. When looking into papers describing the
774 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
775 The SCSI-standard follows a hardware-hierarchy which says that id 7
776 has the highest priority and id 0 the lowest. Therefore, the host
777 adapters are still today everywhere placed as SCSI-id 7 by default.
778 In the SCSI-standard, the drive letters express the priority of the
779 disk. C: should be the hard disk, or a partition on it, with the
780 highest priority. This must therefore be the disk with the highest
781 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
782 original definition of the SCSI-standard as also industrial- and
783 process-control-machines, like VME-CPUs running under realtime-OSes
784 (e.g. LynxOS, OS9) do.
786 If you like to run Linux on your MCA-machine with the same
787 assignment of hard disks as seen from e.g. DOS or OS/2 on your
788 machine, which is in addition conformant to the SCSI-standard, you
789 must say Y here. This is also necessary for MCA-Linux users who want
790 to keep downward compatibility to older releases of the
791 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
794 If you like to have the lowest SCSI-id assigned as drive C:, as
795 modern SCSI-BIOSes do, which does not conform to the standard, but
796 is widespread and common in the PC-world of today, you must say N
797 here. If unsure, say Y.
799 config IBMMCA_SCSI_DEV_RESET
800 bool "Reset SCSI-devices at boottime"
801 depends on SCSI_IBMMCA
803 By default, SCSI-devices are reset when the machine is powered on.
804 However, some devices exist, like special-control-devices,
805 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
806 not reset when switched on. If you say Y here, each device connected
807 to your SCSI-bus will be issued a reset-command after it has been
808 probed, while the kernel is booting. This may cause problems with
809 more modern devices, like hard disks, which do not appreciate these
810 reset commands, and can cause your system to hang. So say Y only if
811 you know that one of your older devices needs it; N is the safe
815 tristate "IBM ServeRAID support"
816 depends on PCI && SCSI
818 This is support for the IBM ServeRAID hardware RAID controllers.
819 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
820 for more information. If this driver does not work correctly
821 without modification please contact the author by email at
822 <ipslinux@adaptec.com>.
824 To compile this driver as a module, choose M here: the
825 module will be called ips.
828 tristate "IBM Virtual SCSI support"
829 depends on PPC_PSERIES || PPC_ISERIES
831 This is the IBM POWER Virtual SCSI Client
833 To compile this driver as a module, choose M here: the
834 module will be called ibmvscsic.
836 config SCSI_IBMVSCSIS
837 tristate "IBM Virtual SCSI Server support"
838 depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
840 This is the SRP target driver for IBM pSeries virtual environments.
842 The userspace component needed to initialize the driver and
843 documentation can be found:
845 http://stgt.berlios.de/
847 To compile this driver as a module, choose M here: the
848 module will be called ibmvstgt.
851 tristate "Initio 9100U(W) support"
852 depends on PCI && SCSI
854 This is support for the Initio 91XXU(W) SCSI host adapter. Please
855 read the SCSI-HOWTO, available from
856 <http://www.tldp.org/docs.html#howto>.
858 To compile this driver as a module, choose M here: the
859 module will be called initio.
862 tristate "Initio INI-A100U2W support"
863 depends on PCI && SCSI
865 This is support for the Initio INI-A100U2W SCSI host adapter.
866 Please read the SCSI-HOWTO, available from
867 <http://www.tldp.org/docs.html#howto>.
869 To compile this driver as a module, choose M here: the
870 module will be called a100u2w.
873 tristate "IOMEGA parallel port (ppa - older drives)"
874 depends on SCSI && PARPORT_PC
876 This driver supports older versions of IOMEGA's parallel port ZIP
877 drive (a 100 MB removable media device).
879 Note that you can say N here if you have the SCSI version of the ZIP
880 drive: it will be supported automatically if you said Y to the
881 generic "SCSI disk support", above.
883 If you have the ZIP Plus drive or a more recent parallel port ZIP
884 drive (if the supplied cable with the drive is labeled "AutoDetect")
885 then you should say N here and Y to "IOMEGA parallel port (imm -
886 newer drives)", below.
888 For more information about this driver and how to use it you should
889 read the file <file:Documentation/scsi/ppa.txt>. You should also read
890 the SCSI-HOWTO, which is available from
891 <http://www.tldp.org/docs.html#howto>. If you use this driver,
892 you will still be able to use the parallel port for other tasks,
893 such as a printer; it is safe to compile both drivers into the
896 To compile this driver as a module, choose M here: the
897 module will be called ppa.
900 tristate "IOMEGA parallel port (imm - newer drives)"
901 depends on SCSI && PARPORT_PC
903 This driver supports newer versions of IOMEGA's parallel port ZIP
904 drive (a 100 MB removable media device).
906 Note that you can say N here if you have the SCSI version of the ZIP
907 drive: it will be supported automatically if you said Y to the
908 generic "SCSI disk support", above.
910 If you have the ZIP Plus drive or a more recent parallel port ZIP
911 drive (if the supplied cable with the drive is labeled "AutoDetect")
912 then you should say Y here; if you have an older ZIP drive, say N
913 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
915 For more information about this driver and how to use it you should
916 read the file <file:Documentation/scsi/ppa.txt>. You should also read
917 the SCSI-HOWTO, which is available from
918 <http://www.tldp.org/docs.html#howto>. If you use this driver,
919 you will still be able to use the parallel port for other tasks,
920 such as a printer; it is safe to compile both drivers into the
923 To compile this driver as a module, choose M here: the
924 module will be called imm.
926 config SCSI_IZIP_EPP16
927 bool "ppa/imm option - Use slow (but safe) EPP-16"
928 depends on SCSI_PPA || SCSI_IMM
930 EPP (Enhanced Parallel Port) is a standard for parallel ports which
931 allows them to act as expansion buses that can handle up to 64
934 Some parallel port chipsets are slower than their motherboard, and
935 so we have to control the state of the chipset's FIFO queue every
936 now and then to avoid data loss. This will be done if you say Y
939 Generally, saying Y is the safe option and slows things down a bit.
941 config SCSI_IZIP_SLOW_CTR
942 bool "ppa/imm option - Assume slow parport control register"
943 depends on SCSI_PPA || SCSI_IMM
945 Some parallel ports are known to have excessive delays between
946 changing the parallel port control register and good data being
947 available on the parallel port data/status register. This option
948 forces a small delay (1.0 usec to be exact) after changing the
949 control register to let things settle out. Enabling this option may
950 result in a big drop in performance but some very old parallel ports
951 (found in 386 vintage machines) will not work properly.
953 Generally, saying N is fine.
955 config SCSI_NCR53C406A
956 tristate "NCR53c406a SCSI support"
957 depends on ISA && SCSI
959 This is support for the NCR53c406a SCSI host adapter. For user
960 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
961 in the kernel source. Also read the SCSI-HOWTO, available from
962 <http://www.tldp.org/docs.html#howto>.
964 To compile this driver as a module, choose M here: the
965 module will be called NCR53c406.
968 tristate "NCR Dual 700 MCA SCSI support"
969 depends on MCA && SCSI
970 select SCSI_SPI_ATTRS
972 This is a driver for the MicroChannel Dual 700 card produced by
973 NCR and commonly used in 345x/35xx/4100 class machines. It always
974 tries to negotiate sync and uses tag command queueing.
976 Unless you have an NCR manufactured machine, the chances are that
977 you do not have this SCSI card, so say N.
980 tristate "HP Lasi SCSI support for 53c700/710"
981 depends on GSC && SCSI
982 select SCSI_SPI_ATTRS
984 This is a driver for the SCSI controller in the Lasi chip found in
985 many PA-RISC workstations & servers. If you do not know whether you
986 have a Lasi chip, it is safe to say "Y" here.
988 config SCSI_SNI_53C710
989 tristate "SNI RM SCSI support for 53c710"
990 depends on SNI_RM && SCSI
991 select SCSI_SPI_ATTRS
992 select 53C700_LE_ON_BE
994 This is a driver for the onboard SCSI controller found in older
995 SNI RM workstations & servers.
997 config 53C700_LE_ON_BE
999 depends on SCSI_LASI700
1003 tristate "Promise SuperTrak EX Series support"
1004 depends on PCI && SCSI
1006 This driver supports Promise SuperTrak EX series storage controllers.
1008 Promise provides Linux RAID configuration utility for these
1009 controllers. Please visit <http://www.promise.com> to download.
1011 To compile this driver as a module, choose M here: the
1012 module will be called stex.
1014 config 53C700_BE_BUS
1016 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1019 config SCSI_SYM53C8XX_2
1020 tristate "SYM53C8XX Version 2 SCSI support"
1021 depends on PCI && SCSI
1022 select SCSI_SPI_ATTRS
1024 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1025 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1026 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1027 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1028 controllers; you need to use the Fusion MPT driver for that.
1030 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1033 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1034 int "DMA addressing mode"
1035 depends on SCSI_SYM53C8XX_2
1038 This option only applies to PCI-SCSI chips that are PCI DAC
1039 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1041 When set to 0, the driver will program the chip to only perform
1042 32-bit DMA. When set to 1, the chip will be able to perform DMA
1043 to addresses up to 1TB. When set to 2, the driver supports the
1044 full 64-bit DMA address range, but can only address 16 segments
1045 of 4 GB each. This limits the total addressable range to 64 GB.
1047 Most machines with less than 4GB of memory should use a setting
1048 of 0 for best performance. If your machine has 4GB of memory
1049 or more, you should set this option to 1 (the default).
1051 The still experimental value 2 (64 bit DMA addressing with 16
1052 x 4GB segments limitation) can be used on systems that require
1053 PCI address bits past bit 39 to be set for the addressing of
1054 memory using PCI DAC cycles.
1056 config SCSI_SYM53C8XX_DEFAULT_TAGS
1057 int "Default tagged command queue depth"
1058 depends on SCSI_SYM53C8XX_2
1061 This is the default value of the command queue depth the
1062 driver will announce to the generic SCSI layer for devices
1063 that support tagged command queueing. This value can be changed
1064 from the boot command line. This is a soft limit that cannot
1065 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1067 config SCSI_SYM53C8XX_MAX_TAGS
1068 int "Maximum number of queued commands"
1069 depends on SCSI_SYM53C8XX_2
1072 This option allows you to specify the maximum number of commands
1073 that can be queued to any device, when tagged command queuing is
1074 possible. The driver supports up to 256 queued commands per device.
1075 This value is used as a compiled-in hard limit.
1077 config SCSI_SYM53C8XX_MMIO
1078 bool "Use memory mapped IO"
1079 depends on SCSI_SYM53C8XX_2
1082 Memory mapped IO is faster than Port IO. Most people should
1083 answer Y here, but some machines may have problems. If you have
1084 to answer N here, please report the problem to the maintainer.
1087 tristate "IBM Power Linux RAID adapter support"
1088 depends on PCI && SCSI && ATA
1091 This driver supports the IBM Power Linux family RAID adapters.
1092 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1093 as IBM iSeries 5702, 5703, 5709, and 570A.
1095 config SCSI_IPR_TRACE
1096 bool "enable driver internal trace"
1100 If you say Y here, the driver will trace all commands issued
1101 to the adapter. Performance impact is minimal. Trace can be
1102 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1104 config SCSI_IPR_DUMP
1105 bool "enable adapter dump support"
1109 If you say Y here, the driver will support adapter crash dump.
1110 If you enable this support, the iprdump daemon can be used
1111 to capture adapter failure analysis information.
1114 tristate "Zalon SCSI support"
1115 depends on GSC && SCSI
1116 select SCSI_SPI_ATTRS
1118 The Zalon is a GSC/HSC bus interface chip that sits between the
1119 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1120 C110, J200, J210 and some D, K & R-class machines. It's also
1121 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1122 Say Y here if you have one of these machines or cards.
1124 config SCSI_NCR_Q720
1125 tristate "NCR Quad 720 MCA SCSI support"
1126 depends on MCA && SCSI
1127 select SCSI_SPI_ATTRS
1129 This is a driver for the MicroChannel Quad 720 card produced by
1130 NCR and commonly used in 345x/35xx/4100 class machines. It always
1131 tries to negotiate sync and uses tag command queueing.
1133 Unless you have an NCR manufactured machine, the chances are that
1134 you do not have this SCSI card, so say N.
1136 config SCSI_NCR53C8XX_DEFAULT_TAGS
1137 int "default tagged command queue depth"
1138 depends on SCSI_ZALON || SCSI_NCR_Q720
1141 "Tagged command queuing" is a feature of SCSI-2 which improves
1142 performance: the host adapter can send several SCSI commands to a
1143 device's queue even if previous commands haven't finished yet.
1144 Because the device is intelligent, it can optimize its operations
1145 (like head positioning) based on its own request queue. Some SCSI
1146 devices don't implement this properly; if you want to disable this
1147 feature, enter 0 or 1 here (it doesn't matter which).
1149 The default value is 8 and should be supported by most hard disks.
1150 This value can be overridden from the boot command line using the
1151 'tags' option as follows (example):
1152 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1153 4, set queue depth to 16 for target 2 and target 3 on controller 0
1154 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1156 The normal answer therefore is to go with the default 8 and to use
1157 a boot command line option for devices that need to use a different
1158 command queue depth.
1160 There is no safe option other than using good SCSI devices.
1162 config SCSI_NCR53C8XX_MAX_TAGS
1163 int "maximum number of queued commands"
1164 depends on SCSI_ZALON || SCSI_NCR_Q720
1167 This option allows you to specify the maximum number of commands
1168 that can be queued to any device, when tagged command queuing is
1169 possible. The default value is 32. Minimum is 2, maximum is 64.
1170 Modern hard disks are able to support 64 tags and even more, but
1171 do not seem to be faster when more than 32 tags are being used.
1173 So, the normal answer here is to go with the default value 32 unless
1174 you are using very large hard disks with large cache (>= 1 MB) that
1175 are able to take advantage of more than 32 tagged commands.
1177 There is no safe option and the default answer is recommended.
1179 config SCSI_NCR53C8XX_SYNC
1180 int "synchronous transfers frequency in MHz"
1181 depends on SCSI_ZALON || SCSI_NCR_Q720
1184 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1185 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1186 are respectively the maximum data transfer rates in mega-transfers
1187 per second for each class. For example, a FAST-20 Wide 16 device is
1188 able to transfer data at 20 million 16 bit packets per second for a
1189 total rate of 40 MB/s.
1191 You may specify 0 if you want to only use asynchronous data
1192 transfers. This is the safest and slowest option. Otherwise, specify
1193 a value between 5 and 80, depending on the capability of your SCSI
1194 controller. The higher the number, the faster the data transfer.
1195 Note that 80 should normally be ok since the driver decreases the
1196 value automatically according to the controller's capabilities.
1198 Your answer to this question is ignored for controllers with NVRAM,
1199 since the driver will get this information from the user set-up. It
1200 also can be overridden using a boot setup option, as follows
1201 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1202 for FAST-20 synchronous data transfer (20 mega-transfers per
1205 The normal answer therefore is not to go with the default but to
1206 select the maximum value 80 allowing the driver to use the maximum
1207 value supported by each controller. If this causes problems with
1208 your SCSI devices, you should come back and decrease the value.
1210 There is no safe option other than using good cabling, right
1211 terminations and SCSI conformant devices.
1213 config SCSI_NCR53C8XX_NO_DISCONNECT
1214 bool "not allow targets to disconnect"
1215 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1217 This option is only provided for safety if you suspect some SCSI
1218 device of yours to not support properly the target-disconnect
1219 feature. In that case, you would say Y here. In general however, to
1220 not allow targets to disconnect is not reasonable if there is more
1221 than 1 device on a SCSI bus. The normal answer therefore is N.
1223 config SCSI_MCA_53C9X
1224 tristate "NCR MCA 53C9x SCSI support"
1225 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1227 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1228 controller based on the NCR 53C94. This driver will allow use of
1229 the controller on the 3550, and very possibly others.
1231 To compile this driver as a module, choose M here: the
1232 module will be called mca_53c9x.
1235 tristate "PAS16 SCSI support"
1236 depends on ISA && SCSI
1237 select SCSI_SPI_ATTRS
1239 This is support for a SCSI host adapter. It is explained in section
1240 3.10 of the SCSI-HOWTO, available from
1241 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1242 of the box, you may have to change some settings in
1243 <file:drivers/scsi/pas16.h>.
1245 To compile this driver as a module, choose M here: the
1246 module will be called pas16.
1249 tristate "PSI240i support"
1250 depends on ISA && SCSI
1252 This is support for the PSI240i EIDE interface card which acts as a
1253 SCSI host adapter. Please read the SCSI-HOWTO, available from
1254 <http://www.tldp.org/docs.html#howto>.
1256 To compile this driver as a module, choose M here: the
1257 module will be called psi240i.
1259 config SCSI_QLOGIC_FAS
1260 tristate "Qlogic FAS SCSI support"
1261 depends on ISA && SCSI
1263 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1264 FastSCSI! cards as well as any other card based on the FASXX chip
1265 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1267 This driver does NOT support the PCI versions of these cards. The
1268 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1269 SCSI support"), below.
1271 Information about this driver is contained in
1272 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1273 SCSI-HOWTO, available from
1274 <http://www.tldp.org/docs.html#howto>.
1276 To compile this driver as a module, choose M here: the
1277 module will be called qlogicfas.
1279 config SCSI_QLOGIC_FC_FIRMWARE
1280 bool "Include loadable firmware in driver"
1281 depends on SCSI_QLOGIC_FC
1283 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1284 expanded LUN addressing and FcTape (FCP-2) support, in the
1285 qlogicfc driver. This is required on some platforms.
1287 config SCSI_QLOGIC_1280
1288 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1289 depends on PCI && SCSI
1291 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1293 To compile this driver as a module, choose M here: the
1294 module will be called qla1280.
1296 config SCSI_QLOGICPTI
1297 tristate "PTI Qlogic, ISP Driver"
1298 depends on SBUS && SCSI
1300 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1301 controllers are known under Solaris as qpti and in the openprom as
1302 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1303 driven by a different driver.
1305 To compile this driver as a module, choose M here: the
1306 module will be called qlogicpti.
1308 source "drivers/scsi/qla2xxx/Kconfig"
1309 source "drivers/scsi/qla4xxx/Kconfig"
1312 tristate "Emulex LightPulse Fibre Channel Support"
1313 depends on PCI && SCSI
1314 select SCSI_FC_ATTRS
1316 This lpfc driver supports the Emulex LightPulse
1317 Family of Fibre Channel PCI host adapters.
1320 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1321 depends on X86 && ISA && SCSI
1323 These are 8-bit SCSI controllers; the ST-01 is also supported by
1324 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1325 available from <http://www.tldp.org/docs.html#howto>. If it
1326 doesn't work out of the box, you may have to change some macros at
1327 compiletime, which are described in <file:drivers/scsi/seagate.c>.
1329 To compile this driver as a module, choose M here: the
1330 module will be called seagate.
1332 # definitely looks not 64bit safe:
1334 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1335 depends on (EISA || MCA) && SCSI
1336 select SCSI_SPI_ATTRS
1338 This driver for NCR53c710 based SCSI host adapters.
1340 It currently supports Compaq EISA cards and NCR MCA cards
1342 config SCSI_SYM53C416
1343 tristate "Symbios 53c416 SCSI support"
1344 depends on ISA && SCSI
1346 This is support for the sym53c416 SCSI host adapter, the SCSI
1347 adapter that comes with some HP scanners. This driver requires that
1348 the sym53c416 is configured first using some sort of PnP
1349 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1350 are using isapnp then you need to compile this driver as a module
1351 and then load it using insmod after isapnp has run. The parameters
1352 of the configured card(s) should be passed to the driver. The format
1355 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1357 To compile this driver as a module, choose M here: the
1358 module will be called sym53c416.
1361 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1362 depends on PCI && SCSI && EXPERIMENTAL
1364 This driver supports PCI SCSI host adapters based on the ASIC
1365 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1367 This driver works, but is still in experimental status. So better
1368 have a bootable disk and a backup in case of emergency.
1370 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1372 To compile this driver as a module, choose M here: the
1373 module will be called dc395x.
1376 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1377 depends on PCI && SCSI
1379 This driver supports PCI SCSI host adapters based on the Am53C974A
1380 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1381 PCscsi/PCnet (Am53/79C974) solutions.
1383 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1385 Note that this driver does NOT support Tekram DC390W/U/F, which are
1386 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1388 To compile this driver as a module, choose M here: the
1389 module will be called tmscsim.
1392 tristate "Trantor T128/T128F/T228 SCSI support"
1393 depends on ISA && SCSI
1394 select SCSI_SPI_ATTRS
1396 This is support for a SCSI host adapter. It is explained in section
1397 3.11 of the SCSI-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1399 of the box, you may have to change some settings in
1400 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1401 Adaptec, and some former Trantor products are being sold under the
1404 To compile this driver as a module, choose M here: the
1405 module will be called t128.
1408 tristate "UltraStor 14F/34F support"
1409 depends on ISA && SCSI && ISA_DMA_API
1411 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1412 The source at <file:drivers/scsi/u14-34f.c> contains some
1413 information about this hardware. If the driver doesn't work out of
1414 the box, you may have to change some settings in
1415 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1416 <http://www.tldp.org/docs.html#howto>. Note that there is also
1417 another driver for the same hardware: "UltraStor SCSI support",
1418 below. You should say Y to both only if you want 24F support as
1421 To compile this driver as a module, choose M here: the
1422 module will be called u14-34f.
1424 config SCSI_U14_34F_TAGGED_QUEUE
1425 bool "enable tagged command queueing"
1426 depends on SCSI_U14_34F
1428 This is a feature of SCSI-2 which improves performance: the host
1429 adapter can send several SCSI commands to a device's queue even if
1430 previous commands haven't finished yet.
1431 This is equivalent to the "u14-34f=tc:y" boot option.
1433 config SCSI_U14_34F_LINKED_COMMANDS
1434 bool "enable elevator sorting"
1435 depends on SCSI_U14_34F
1437 This option enables elevator sorting for all probed SCSI disks and
1438 CD-ROMs. It definitely reduces the average seek distance when doing
1439 random seeks, but this does not necessarily result in a noticeable
1440 performance improvement: your mileage may vary...
1441 This is equivalent to the "u14-34f=lc:y" boot option.
1443 config SCSI_U14_34F_MAX_TAGS
1444 int "maximum number of queued commands"
1445 depends on SCSI_U14_34F
1448 This specifies how many SCSI commands can be maximally queued for
1449 each probed SCSI device. You should reduce the default value of 8
1450 only if you have disks with buggy or limited tagged command support.
1451 Minimum is 2 and maximum is 14. This value is also the window size
1452 used by the elevator sorting option above. The effective value used
1453 by the driver for each probed SCSI device is reported at boot time.
1454 This is equivalent to the "u14-34f=mq:8" boot option.
1456 config SCSI_ULTRASTOR
1457 tristate "UltraStor SCSI support"
1458 depends on X86 && ISA && SCSI
1460 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1461 adapter family. This driver is explained in section 3.12 of the
1462 SCSI-HOWTO, available from
1463 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1464 of the box, you may have to change some settings in
1465 <file:drivers/scsi/ultrastor.h>.
1467 Note that there is also another driver for the same hardware:
1468 "UltraStor 14F/34F support", above.
1470 To compile this driver as a module, choose M here: the
1471 module will be called ultrastor.
1474 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1475 depends on PCI && SCSI && !64BIT
1477 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1478 SCSI host adapter. Please read the SCSI-HOWTO, available from
1479 <http://www.tldp.org/docs.html#howto>.
1481 To compile this driver as a module, choose M here: the
1482 module will be called nsp32.
1485 tristate "SCSI debugging host simulator"
1488 This is a host adapter simulator that can simulate multiple hosts
1489 each with multiple dummy SCSI devices (disks). It defaults to one
1490 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1491 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1492 dummy disks are simulated, they share the same kernel RAM for
1493 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1494 information. This driver is primarily of use to those testing the
1495 SCSI and block subsystems. If unsure, say N.
1498 tristate "MESH (Power Mac internal SCSI) support"
1499 depends on PPC32 && PPC_PMAC && SCSI
1501 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1502 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1503 other Power Macintoshes do). Say Y to include support for this SCSI
1506 To compile this driver as a module, choose M here: the
1507 module will be called mesh.
1509 config SCSI_MESH_SYNC_RATE
1510 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1511 depends on SCSI_MESH
1514 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1515 drives a bus which is entirely internal to the machine (such as the
1516 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1517 operation at up to 10 MB/s. On machines where the SCSI bus
1518 controlled by the MESH can have external devices connected, it is
1519 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1520 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1521 to disable synchronous operation.
1523 config SCSI_MESH_RESET_DELAY_MS
1524 int "initial bus reset delay (ms) (0 = no reset)"
1525 depends on SCSI_MESH
1528 config SCSI_MAC53C94
1529 tristate "53C94 (Power Mac external SCSI) support"
1530 depends on PPC32 && PPC_PMAC && SCSI
1532 On Power Macintoshes (and clones) with two SCSI buses, the external
1533 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1534 machines which only have one SCSI bus, such as the 7200, also use
1535 the 53C94. Say Y to include support for the 53C94.
1537 To compile this driver as a module, choose M here: the
1538 module will be called mac53c94.
1540 source "drivers/scsi/arm/Kconfig"
1543 bool "MIPS JAZZ FAS216 SCSI support"
1544 depends on MACH_JAZZ && SCSI
1546 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1547 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1551 tristate "A3000 WD33C93A support"
1552 depends on AMIGA && SCSI
1554 If you have an Amiga 3000 and have SCSI devices connected to the
1555 built-in SCSI controller, say Y. Otherwise, say N.
1557 To compile this driver as a module, choose M here: the
1558 module will be called wd33c93.
1561 tristate "A2091/A590 WD33C93A support"
1562 depends on ZORRO && SCSI
1564 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1567 To compile this driver as a module, choose M here: the
1568 module will be called wd33c93.
1571 tristate "GVP Series II WD33C93A support"
1572 depends on ZORRO && SCSI
1574 If you have a Great Valley Products Series II SCSI controller,
1575 answer Y. Also say Y if you have a later model of GVP SCSI
1576 controller (such as the GVP A4008 or a Combo board). Otherwise,
1577 answer N. This driver does NOT work for the T-Rex series of
1578 accelerators from TekMagic and GVP-M.
1580 To compile this driver as a module, choose M here: the
1581 module will be called gvp11.
1583 config CYBERSTORM_SCSI
1584 tristate "CyberStorm SCSI support"
1585 depends on ZORRO && SCSI
1587 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1588 accelerator board and the optional Cyberstorm SCSI controller,
1589 answer Y. Otherwise, say N.
1591 config CYBERSTORMII_SCSI
1592 tristate "CyberStorm Mk II SCSI support"
1593 depends on ZORRO && SCSI
1595 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1596 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1600 tristate "Blizzard 2060 SCSI support"
1601 depends on ZORRO && SCSI
1603 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1604 and want to use the onboard SCSI controller, say Y. Otherwise,
1608 tristate "Blizzard 1230IV/1260 SCSI support"
1609 depends on ZORRO && SCSI
1611 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1612 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1615 config FASTLANE_SCSI
1616 tristate "Fastlane SCSI support"
1617 depends on ZORRO && SCSI
1619 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1620 one in the near future, say Y to this question. Otherwise, say N.
1623 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1624 depends on AMIGA && SCSI && EXPERIMENTAL
1625 select SCSI_SPI_ATTRS
1627 If you have an Amiga 4000T and have SCSI devices connected to the
1628 built-in SCSI controller, say Y. Otherwise, say N.
1630 To compile this driver as a module, choose M here: the
1631 module will be called a4000t.
1633 config SCSI_ZORRO7XX
1634 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1635 depends on ZORRO && SCSI && EXPERIMENTAL
1636 select SCSI_SPI_ATTRS
1638 Support for various NCR53c710-based SCSI controllers on Zorro
1639 expansion boards for the Amiga.
1641 - the Amiga 4091 Zorro III SCSI-2 controller,
1642 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1644 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1645 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1646 accelerator card for the Amiga 1200,
1647 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1650 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1651 depends on ZORRO && SCSI && EXPERIMENTAL
1653 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1654 Y to this question. If you're in doubt about whether you have one,
1656 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1659 tristate "Atari native SCSI support"
1660 depends on ATARI && SCSI
1661 select SCSI_SPI_ATTRS
1663 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1664 Falcon, ...) say Y to get it supported. Of course also, if you have
1665 a compatible SCSI controller (e.g. for Medusa).
1667 To compile this driver as a module, choose M here: the
1668 module will be called atari_scsi.
1670 This driver supports both styles of NCR integration into the
1671 system: the TT style (separate DMA), and the Falcon style (via
1672 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1673 in the Hades (without DMA).
1675 config ATARI_SCSI_TOSHIBA_DELAY
1676 bool "Long delays for Toshiba CD-ROMs"
1677 depends on ATARI_SCSI
1679 This option increases the delay after a SCSI arbitration to
1680 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1681 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1682 would impact performance a bit, so say N.
1684 config ATARI_SCSI_RESET_BOOT
1685 bool "Reset SCSI-devices at boottime"
1686 depends on ATARI_SCSI
1688 Reset the devices on your Atari whenever it boots. This makes the
1689 boot process fractionally longer but may assist recovery from errors
1690 that leave the devices with SCSI operations partway completed.
1693 bool "Hades SCSI DMA emulator"
1694 depends on ATARI_SCSI && HADES
1696 This option enables code which emulates the TT SCSI DMA chip on the
1697 Hades. This increases the SCSI transfer rates at least ten times
1698 compared to PIO transfers.
1701 bool "Macintosh NCR5380 SCSI"
1702 depends on MAC && SCSI=y
1703 select SCSI_SPI_ATTRS
1705 This is the NCR 5380 SCSI controller included on most of the 68030
1706 based Macintoshes. If you have one of these say Y and read the
1707 SCSI-HOWTO, available from
1708 <http://www.tldp.org/docs.html#howto>.
1711 tristate "Macintosh NCR53c9[46] SCSI"
1712 depends on MAC && SCSI
1714 This is the NCR 53c9x SCSI controller found on most of the 68040
1715 based Macintoshes. If you have one of these say Y and read the
1716 SCSI-HOWTO, available from
1717 <http://www.tldp.org/docs.html#howto>.
1719 To compile this driver as a module, choose M here: the
1720 module will be called mac_esp.
1723 bool "WD33C93 SCSI driver for MVME147"
1724 depends on MVME147 && SCSI=y
1725 select SCSI_SPI_ATTRS
1727 Support for the on-board SCSI controller on the Motorola MVME147
1728 single-board computer.
1731 tristate "NCR53C710 SCSI driver for MVME16x"
1732 depends on MVME16x && SCSI
1733 select SCSI_SPI_ATTRS
1735 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1736 SCSI controller chip. Almost everyone using one of these boards
1737 will want to say Y to this question.
1739 config BVME6000_SCSI
1740 tristate "NCR53C710 SCSI driver for BVME6000"
1741 depends on BVME6000 && SCSI
1742 select SCSI_SPI_ATTRS
1744 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1745 SCSI controller chip. Almost everyone using one of these boards
1746 will want to say Y to this question.
1749 tristate "Sun3 NCR5380 SCSI"
1750 depends on SUN3 && SCSI
1751 select SCSI_SPI_ATTRS
1753 This option will enable support for the OBIO (onboard io) NCR5380
1754 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1755 "Sun3" type VME scsi controllers also based on the NCR5380.
1756 General Linux information on the Sun 3 series (now discontinued)
1757 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1760 bool "Sun3x ESP SCSI"
1761 depends on SUN3X && SCSI=y
1763 The ESP was an on-board SCSI controller used on Sun 3/80
1764 machines. Say Y here to compile in support for it.
1767 tristate "Sparc ESP Scsi Driver"
1768 depends on SBUS && SCSI
1770 This is the driver for the Sun ESP SCSI host adapter. The ESP
1771 chipset is present in most SPARC SBUS-based computers.
1773 To compile this driver as a module, choose M here: the
1774 module will be called esp.
1777 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1778 depends on S390 && QDIO && SCSI
1779 select SCSI_FC_ATTRS
1781 If you want to access SCSI devices attached to your IBM eServer
1782 zSeries by means of Fibre Channel interfaces say Y.
1783 For details please refer to the documentation provided by IBM at
1784 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1786 This driver is also available as a module. This module will be
1787 called zfcp. If you want to compile it as a module, say M here
1788 and read <file:Documentation/kbuild/modules.txt>.
1791 tristate "SCSI RDMA Protocol helper library"
1792 depends on SCSI && PCI
1795 If you wish to use SRP target drivers, say Y.
1797 To compile this driver as a module, choose M here: the
1798 module will be called libsrp.
1802 source "drivers/scsi/pcmcia/Kconfig"