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 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
69 USB storage or the SCSI or parallel port version of
70 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
71 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
72 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
75 To compile this driver as a module, choose M here and read
76 <file:Documentation/scsi/scsi.txt>.
77 The module will be called sd_mod.
79 Do not compile this driver as a module if your root file system
80 (the one containing the directory /) is located on a SCSI disk.
81 In this case, do not compile the driver for your SCSI host adapter
82 (below) as a module either.
85 tristate "SCSI tape support"
88 If you want to use a SCSI tape drive under Linux, say Y and read the
89 SCSI-HOWTO, available from
90 <http://www.tldp.org/docs.html#howto>, and
91 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
94 To compile this driver as a module, choose M here and read
95 <file:Documentation/scsi/scsi.txt>. The module will be called st.
98 tristate "SCSI OnStream SC-x0 tape support"
101 The OnStream SC-x0 SCSI tape drives cannot be driven by the
102 standard st driver, but instead need this special osst driver and
103 use the /dev/osstX char device nodes (major 206). Via usb-storage
104 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
105 as well. Note that there is also a second generation of OnStream
106 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
107 tapes (QIC-157) and can be driven by the standard driver st.
108 For more information, you may have a look at the SCSI-HOWTO
109 <http://www.tldp.org/docs.html#howto> and
110 <file:Documentation/scsi/osst.txt> in the kernel source.
111 More info on the OnStream driver may be found on
112 <http://linux1.onstream.nl/test/>
113 Please also have a look at the standard st docu, as most of it
114 applies to osst as well.
116 To compile this driver as a module, choose M here and read
117 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
120 tristate "SCSI CDROM support"
123 If you want to use a SCSI or FireWire CD-ROM under Linux,
124 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
125 <http://www.tldp.org/docs.html#howto>. Also make sure to say
126 Y or M to "ISO 9660 CD-ROM file system support" later.
128 To compile this driver as a module, choose M here and read
129 <file:Documentation/scsi/scsi.txt>.
130 The module will be called sr_mod.
132 config BLK_DEV_SR_VENDOR
133 bool "Enable vendor-specific extensions (for SCSI CDROM)"
134 depends on BLK_DEV_SR
136 This enables the usage of vendor specific SCSI commands. This is
137 required to support multisession CDs with old NEC/TOSHIBA cdrom
138 drives (and HP Writers). If you have such a drive and get the first
139 session only, try saying Y here; everybody else says N.
142 tristate "SCSI generic support"
145 If you want to use SCSI scanners, synthesizers or CD-writers or just
146 about anything having "SCSI" in its name other than hard disks,
147 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
148 directly, so you need some additional software which knows how to
149 talk to these devices using the SCSI protocol:
151 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
152 writer software look at Cdrtools
153 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
154 and for burning a "disk at once": CDRDAO
155 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
156 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
157 For other devices, it's possible that you'll have to write the
158 driver software yourself. Please read the file
159 <file:Documentation/scsi/scsi-generic.txt> for more information.
161 To compile this driver as a module, choose M here and read
162 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
167 tristate "SCSI media changer support"
170 This is a driver for SCSI media changers. Most common devices are
171 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
172 don't need this for those tiny 6-slot cdrom changers. Media
173 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
174 If you have such hardware and want to use it with linux, say Y
175 here. Check <file:Documentation/scsi-changer.txt> for details.
177 If you want to compile this as a module ( = code which can be
178 inserted in and removed from the running kernel whenever you want),
179 say M here and read <file:Documentation/kbuild/modules.txt> and
180 <file:Documentation/scsi.txt>. The module will be called ch.o.
184 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
187 config SCSI_MULTI_LUN
188 bool "Probe all LUNs on each SCSI device"
191 If you have a SCSI device that supports more than one LUN (Logical
192 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
193 can say Y here to force the SCSI driver to probe for multiple LUNs.
194 A SCSI device with multiple LUNs acts logically like multiple SCSI
195 devices. The vast majority of SCSI devices have only one LUN, and
196 so most people can say N here. The max_luns boot/module parameter
197 allows to override this setting.
199 config SCSI_CONSTANTS
200 bool "Verbose SCSI error reporting (kernel size +=12K)"
203 The error messages regarding your SCSI hardware will be easier to
204 understand if you say Y here; it will enlarge your kernel by about
205 12 KB. If in doubt, say Y.
208 bool "SCSI logging facility"
211 This turns on a logging facility that can be used to debug a number
212 of SCSI related problems.
214 If you say Y here, no logging output will appear by default, but you
215 can enable logging by saying Y to "/proc file system support" and
216 "Sysctl support" below and executing the command
218 echo "scsi log token [level]" > /proc/scsi/scsi
220 at boot time after the /proc file system has been mounted.
222 There are a number of things that can be used for 'token' (you can
223 find them in the source: <file:drivers/scsi/scsi.c>), and this
224 allows you to select the types of information you want, and the
225 level allows you to select the level of verbosity.
227 If you say N here, it may be harder to track down some types of SCSI
228 problems. If you say Y here your kernel will be somewhat larger, but
229 there should be no noticeable performance impact as long as you have
232 config SCSI_SCAN_ASYNC
233 bool "Asynchronous SCSI scanning"
236 The SCSI subsystem can probe for devices while the rest of the
237 system continues booting, and even probe devices on different
238 busses in parallel, leading to a significant speed-up.
240 If you have built SCSI as modules, enabling this option can
241 be a problem as the devices may not have been found by the
242 time your system expects them to have been. You can load the
243 scsi_wait_scan module to ensure that all scans have completed.
244 If you build your SCSI drivers into the kernel, then everything
245 will work fine if you say Y here.
247 You can override this choice by specifying "scsi_mod.scan=sync"
248 or async on the kernel's command line.
250 config SCSI_WAIT_SCAN
256 menu "SCSI Transports"
259 config SCSI_SPI_ATTRS
260 tristate "Parallel SCSI (SPI) Transport Attributes"
263 If you wish to export transport-specific information about
264 each attached SCSI device to sysfs, say Y. Otherwise, say N.
267 tristate "FiberChannel Transport Attributes"
271 If you wish to export transport-specific information about
272 each attached FiberChannel device to sysfs, say Y.
275 config SCSI_ISCSI_ATTRS
276 tristate "iSCSI Transport Attributes"
277 depends on SCSI && NET
279 If you wish to export transport-specific information about
280 each attached iSCSI device to sysfs, say Y.
283 config SCSI_SAS_ATTRS
284 tristate "SAS Transport Attributes"
285 depends on SCSI && BLK_DEV_BSG
287 If you wish to export transport-specific information about
288 each attached SAS device to sysfs, say Y.
290 source "drivers/scsi/libsas/Kconfig"
292 config SCSI_SRP_ATTRS
293 tristate "SRP Transport Attributes"
296 If you wish to export transport-specific information about
297 each attached SRP device to sysfs, say Y.
301 menuconfig SCSI_LOWLEVEL
302 bool "SCSI low-level drivers"
309 tristate "iSCSI Initiator over TCP/IP"
310 depends on SCSI && INET
314 select SCSI_ISCSI_ATTRS
316 The iSCSI Driver provides a host with the ability to access storage
317 through an IP network. The driver uses the iSCSI protocol to transport
318 SCSI requests and responses over a TCP/IP network between the host
319 (the "initiator") and "targets". Architecturally, the iSCSI driver
320 combines with the host's TCP/IP stack, network drivers, and Network
321 Interface Card (NIC) to provide the same functions as a SCSI or a
322 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
324 To compile this driver as a module, choose M here: the
325 module will be called iscsi_tcp.
327 The userspace component needed to initialize the driver, documentation,
328 and sample configuration files can be found here:
330 http://linux-iscsi.sf.net
333 tristate "SGI WD93C93 SCSI Driver"
334 depends on SGI_IP22 && SCSI
336 If you have a Western Digital WD93 SCSI controller on
337 an SGI MIPS system, say Y. Otherwise, say N.
340 tristate "DEC NCR53C94 Scsi Driver"
341 depends on MACH_DECSTATION && SCSI && TC
343 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
344 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
347 tristate "DEC SII Scsi Driver"
348 depends on MACH_DECSTATION && SCSI && 32BIT
350 config BLK_DEV_3W_XXXX_RAID
351 tristate "3ware 5/6/7/8xxx ATA-RAID support"
352 depends on PCI && SCSI
354 3ware is the only hardware ATA-Raid product in Linux to date.
355 This card is 2,4, or 8 channel master mode support only.
356 SCSI support required!!!
358 <http://www.3ware.com/>
360 Please read the comments at the top of
361 <file:drivers/scsi/3w-xxxx.c>.
364 tristate "3ware 9xxx SATA-RAID support"
365 depends on PCI && SCSI
367 This driver supports the 9000 series 3ware SATA-RAID cards.
369 <http://www.amcc.com>
371 Please read the comments at the top of
372 <file:drivers/scsi/3w-9xxx.c>.
374 config SCSI_7000FASST
375 tristate "7000FASST SCSI support"
376 depends on ISA && SCSI && ISA_DMA_API
378 This driver supports the Western Digital 7000 SCSI host adapter
379 family. Some information is in the source:
380 <file:drivers/scsi/wd7000.c>.
382 To compile this driver as a module, choose M here: the
383 module will be called wd7000.
386 tristate "ACARD SCSI support"
387 depends on PCI && SCSI
389 This driver supports the ACARD SCSI host adapter.
390 Support Chip <ATP870 ATP876 ATP880 ATP885>
391 To compile this driver as a module, choose M here: the
392 module will be called atp870u.
395 tristate "Adaptec AHA152X/2825 support"
396 depends on ISA && SCSI && !64BIT
397 select SCSI_SPI_ATTRS
399 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
400 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
401 must be manually specified in this case.
403 It is explained in section 3.3 of the SCSI-HOWTO, available from
404 <http://www.tldp.org/docs.html#howto>. You might also want to
405 read the file <file:Documentation/scsi/aha152x.txt>.
407 To compile this driver as a module, choose M here: the
408 module will be called aha152x.
411 tristate "Adaptec AHA1542 support"
412 depends on ISA && SCSI && ISA_DMA_API
414 This is support for a SCSI host adapter. It is explained in section
415 3.4 of the SCSI-HOWTO, available from
416 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
417 purchased by Adaptec, and some former Trantor products are being
418 sold under the Adaptec name. If it doesn't work out of the box, you
419 may have to change some settings in <file:drivers/scsi/aha1542.h>.
421 To compile this driver as a module, choose M here: the
422 module will be called aha1542.
425 tristate "Adaptec AHA1740 support"
426 depends on EISA && SCSI
428 This is support for a SCSI host adapter. It is explained in section
429 3.5 of the SCSI-HOWTO, available from
430 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
431 of the box, you may have to change some settings in
432 <file:drivers/scsi/aha1740.h>.
434 To compile this driver as a module, choose M here: the
435 module will be called aha1740.
438 tristate "Adaptec AACRAID support"
439 depends on SCSI && PCI
441 This driver supports a variety of Dell, HP, Adaptec, IBM and
442 ICP storage products. For a list of supported products, refer
443 to <file:Documentation/scsi/aacraid.txt>.
445 To compile this driver as a module, choose M here: the module
446 will be called aacraid.
449 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
451 config SCSI_AIC7XXX_OLD
452 tristate "Adaptec AIC7xxx support (old driver)"
453 depends on (ISA || EISA || PCI ) && SCSI
455 WARNING This driver is an older aic7xxx driver and is no longer
456 under active development. Adaptec, Inc. is writing a new driver to
457 take the place of this one, and it is recommended that whenever
458 possible, people should use the new Adaptec written driver instead
459 of this one. This driver will eventually be phased out entirely.
461 This is support for the various aic7xxx based Adaptec SCSI
462 controllers. These include the 274x EISA cards; 284x VLB cards;
463 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
464 motherboard based SCSI controllers from Adaptec. It does not support
465 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
466 support them. It does not support the 2920 cards from Adaptec that
467 use the Future Domain SCSI controller chip. For those cards, you
468 need the "Future Domain 16xx SCSI support" driver.
470 In general, if the controller is based on an Adaptec SCSI controller
471 chip from the aic777x series or the aic78xx series, this driver
472 should work. The only exception is the 7810 which is specifically
473 not supported (that's the RAID controller chip on the AAA-13x
476 Note that the AHA2920 SCSI host adapter is *not* supported by this
477 driver; choose "Future Domain 16xx SCSI support" instead if you have
480 Information on the configuration options for this controller can be
481 found by checking the help file for each of the available
482 configuration options. You should read
483 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
484 contacting the maintainer with any questions. The SCSI-HOWTO,
485 available from <http://www.tldp.org/docs.html#howto>, can also
488 To compile this driver as a module, choose M here: the
489 module will be called aic7xxx_old.
491 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
492 source "drivers/scsi/aic94xx/Kconfig"
494 # All the I2O code and drivers do not seem to be 64bit safe.
496 tristate "Adaptec I2O RAID support "
497 depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
499 This driver supports all of Adaptec's I2O based RAID controllers as
500 well as the DPT SmartRaid V cards. This is an Adaptec maintained
501 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
503 To compile this driver as a module, choose M here: the
504 module will be called dpt_i2o.
507 tristate "AdvanSys SCSI support"
509 depends on ISA || EISA || PCI
510 depends on BROKEN || X86_32
512 This is a driver for all SCSI host adapters manufactured by
513 AdvanSys. It is documented in the kernel source in
514 <file:drivers/scsi/advansys.c>.
516 To compile this driver as a module, choose M here: the
517 module will be called advansys.
520 tristate "Always IN2000 SCSI support"
521 depends on ISA && SCSI
523 This is support for an ISA bus SCSI host adapter. You'll find more
524 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
525 out of the box, you may have to change the jumpers for IRQ or
528 To compile this driver as a module, choose M here: the
529 module will be called in2000.
532 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
533 depends on PCI && SCSI
535 This driver supports all of ARECA's SATA RAID controller cards.
536 This is an ARECA-maintained driver by Erich Chen.
537 If you have any problems, please mail to: < erich@areca.com.tw >
538 Areca supports Linux RAID config tools.
540 < http://www.areca.com.tw >
542 To compile this driver as a module, choose M here: the
543 module will be called arcmsr (modprobe arcmsr).
545 source "drivers/scsi/megaraid/Kconfig.megaraid"
548 tristate "HighPoint RocketRAID 3xxx Controller support"
549 depends on SCSI && PCI
551 This option enables support for HighPoint RocketRAID 3xxx
554 To compile this driver as a module, choose M here; the module
555 will be called hptiop. If unsure, say N.
558 tristate "BusLogic SCSI support"
559 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
561 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
562 Adapters. Consult the SCSI-HOWTO, available from
563 <http://www.tldp.org/docs.html#howto>, and the files
564 <file:Documentation/scsi/BusLogic.txt> and
565 <file:Documentation/scsi/FlashPoint.txt> for more information.
567 To compile this driver as a module, choose M here: the
568 module will be called BusLogic.
570 config SCSI_OMIT_FLASHPOINT
571 bool "Omit FlashPoint support"
572 depends on SCSI_BUSLOGIC
574 This option allows you to omit the FlashPoint support from the
575 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
576 substantial, so users of MultiMaster Host Adapters may wish to omit
580 tristate "DMX3191D SCSI support"
581 depends on PCI && SCSI
582 select SCSI_SPI_ATTRS
584 This is support for Domex DMX3191D SCSI Host Adapters.
586 To compile this driver as a module, choose M here: the
587 module will be called dmx3191d.
590 tristate "DTC3180/3280 SCSI support"
591 depends on ISA && SCSI
592 select SCSI_SPI_ATTRS
594 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
595 the SCSI-HOWTO, available from
596 <http://www.tldp.org/docs.html#howto>, and the file
597 <file:Documentation/scsi/dtc3x80.txt>.
599 To compile this driver as a module, choose M here: the
600 module will be called dtc.
603 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
604 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
606 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
607 ISA and all EISA I/O addresses are probed looking for the "EATA"
608 signature. The addresses of all the PCI SCSI controllers reported
609 by the PCI subsystem are probed as well.
611 You want to read the start of <file:drivers/scsi/eata.c> and the
612 SCSI-HOWTO, available from
613 <http://www.tldp.org/docs.html#howto>.
615 To compile this driver as a module, choose M here: the
616 module will be called eata.
618 config SCSI_EATA_TAGGED_QUEUE
619 bool "enable tagged command queueing"
622 This is a feature of SCSI-2 which improves performance: the host
623 adapter can send several SCSI commands to a device's queue even if
624 previous commands haven't finished yet.
625 This is equivalent to the "eata=tc:y" boot option.
627 config SCSI_EATA_LINKED_COMMANDS
628 bool "enable elevator sorting"
631 This option enables elevator sorting for all probed SCSI disks and
632 CD-ROMs. It definitely reduces the average seek distance when doing
633 random seeks, but this does not necessarily result in a noticeable
634 performance improvement: your mileage may vary...
635 This is equivalent to the "eata=lc:y" boot option.
637 config SCSI_EATA_MAX_TAGS
638 int "maximum number of queued commands"
642 This specifies how many SCSI commands can be maximally queued for
643 each probed SCSI device. You should reduce the default value of 16
644 only if you have disks with buggy or limited tagged command support.
645 Minimum is 2 and maximum is 62. This value is also the window size
646 used by the elevator sorting option above. The effective value used
647 by the driver for each probed SCSI device is reported at boot time.
648 This is equivalent to the "eata=mq:8" boot option.
651 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
652 depends on (ISA || EISA || PCI) && SCSI && BROKEN
654 This driver supports all EATA-PIO protocol compliant SCSI Host
655 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
656 host adapters could also use this driver but are discouraged from
657 doing so, since this driver only supports hard disks and lacks
658 numerous features. You might want to have a look at the SCSI-HOWTO,
659 available from <http://www.tldp.org/docs.html#howto>.
661 To compile this driver as a module, choose M here: the
662 module will be called eata_pio.
664 config SCSI_FUTURE_DOMAIN
665 tristate "Future Domain 16xx SCSI/AHA-2920A support"
666 depends on (ISA || PCI) && SCSI
668 This is support for Future Domain's 16-bit SCSI host adapters
669 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
670 other adapters based on the Future Domain chipsets (Quantum
671 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
672 It is explained in section 3.7 of the SCSI-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
676 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
677 controller support"). This Future Domain driver works with the older
678 Adaptec AHA-2920A boards with a Future Domain chip on them.
680 To compile this driver as a module, choose M here: the
681 module will be called fdomain.
684 tristate "Future Domain MCS-600/700 SCSI support"
685 depends on MCA_LEGACY && SCSI
687 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
688 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
689 is identical to the MCS 700 and hence also supported by this driver.
690 This driver also supports the Reply SB16/SCSI card (the SCSI part).
691 It supports multiple adapters in the same system.
693 To compile this driver as a module, choose M here: the
694 module will be called fd_mcs.
697 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
698 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
700 Formerly called GDT SCSI Disk Array Controller Support.
702 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
703 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
704 in the kernel source in <file:drivers/scsi/gdth.c> and
705 <file:drivers/scsi/gdth.h.>
707 To compile this driver as a module, choose M here: the
708 module will be called gdth.
710 config SCSI_GENERIC_NCR5380
711 tristate "Generic NCR5380/53c400 SCSI PIO support"
712 depends on ISA && SCSI
713 select SCSI_SPI_ATTRS
715 This is a driver for the old NCR 53c80 series of SCSI controllers
716 on boards using PIO. Most boards such as the Trantor T130 fit this
717 category, along with a large number of ISA 8bit controllers shipped
718 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
719 you should select the specific driver for that card rather than
720 generic 5380 support.
722 It is explained in section 3.8 of the SCSI-HOWTO, available from
723 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
724 of the box, you may have to change some settings in
725 <file:drivers/scsi/g_NCR5380.h>.
727 To compile this driver as a module, choose M here: the
728 module will be called g_NCR5380.
730 config SCSI_GENERIC_NCR5380_MMIO
731 tristate "Generic NCR5380/53c400 SCSI MMIO support"
732 depends on ISA && SCSI
733 select SCSI_SPI_ATTRS
735 This is a driver for the old NCR 53c80 series of SCSI controllers
736 on boards using memory mapped I/O.
737 It is explained in section 3.8 of the SCSI-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
739 of the box, you may have to change some settings in
740 <file:drivers/scsi/g_NCR5380.h>.
742 To compile this driver as a module, choose M here: the
743 module will be called g_NCR5380_mmio.
745 config SCSI_GENERIC_NCR53C400
746 bool "Enable NCR53c400 extensions"
747 depends on SCSI_GENERIC_NCR5380
749 This enables certain optimizations for the NCR53c400 SCSI cards.
750 You might as well try it out. Note that this driver will only probe
751 for the Trantor T130B in its default configuration; you might have
752 to pass a command line option to the kernel at boot time if it does
753 not detect your card. See the file
754 <file:Documentation/scsi/g_NCR5380.txt> for details.
757 tristate "IBMMCA SCSI support"
758 depends on MCA && SCSI
760 This is support for the IBM SCSI adapter found in many of the PS/2
761 series computers. These machines have an MCA bus, so you need to
762 answer Y to "MCA support" as well and read
763 <file:Documentation/mca.txt>.
765 If the adapter isn't found during boot (a common problem for models
766 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
767 option, where <pun> is the id of the SCSI subsystem (usually 7, but
768 if that doesn't work check your reference diskette). Owners of
769 model 95 with a LED-matrix-display can in addition activate some
770 activity info like under OS/2, but more informative, by setting
771 'ibmmcascsi=display' as an additional kernel parameter. Try "man
772 bootparam" or see the documentation of your boot loader about how to
773 pass options to the kernel.
775 To compile this driver as a module, choose M here: the
776 module will be called ibmmca.
778 config IBMMCA_SCSI_ORDER_STANDARD
779 bool "Standard SCSI-order"
780 depends on SCSI_IBMMCA
782 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
783 are assigned to the drive letters, starting with the lowest SCSI-id
784 (physical number -- pun) to be drive C:, as seen from DOS and
785 similar operating systems. When looking into papers describing the
786 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
787 The SCSI-standard follows a hardware-hierarchy which says that id 7
788 has the highest priority and id 0 the lowest. Therefore, the host
789 adapters are still today everywhere placed as SCSI-id 7 by default.
790 In the SCSI-standard, the drive letters express the priority of the
791 disk. C: should be the hard disk, or a partition on it, with the
792 highest priority. This must therefore be the disk with the highest
793 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
794 original definition of the SCSI-standard as also industrial- and
795 process-control-machines, like VME-CPUs running under realtime-OSes
796 (e.g. LynxOS, OS9) do.
798 If you like to run Linux on your MCA-machine with the same
799 assignment of hard disks as seen from e.g. DOS or OS/2 on your
800 machine, which is in addition conformant to the SCSI-standard, you
801 must say Y here. This is also necessary for MCA-Linux users who want
802 to keep downward compatibility to older releases of the
803 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
806 If you like to have the lowest SCSI-id assigned as drive C:, as
807 modern SCSI-BIOSes do, which does not conform to the standard, but
808 is widespread and common in the PC-world of today, you must say N
809 here. If unsure, say Y.
811 config IBMMCA_SCSI_DEV_RESET
812 bool "Reset SCSI-devices at boottime"
813 depends on SCSI_IBMMCA
815 By default, SCSI-devices are reset when the machine is powered on.
816 However, some devices exist, like special-control-devices,
817 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
818 not reset when switched on. If you say Y here, each device connected
819 to your SCSI-bus will be issued a reset-command after it has been
820 probed, while the kernel is booting. This may cause problems with
821 more modern devices, like hard disks, which do not appreciate these
822 reset commands, and can cause your system to hang. So say Y only if
823 you know that one of your older devices needs it; N is the safe
827 tristate "IBM ServeRAID support"
828 depends on PCI && SCSI
830 This is support for the IBM ServeRAID hardware RAID controllers.
831 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
832 for more information. If this driver does not work correctly
833 without modification please contact the author by email at
834 <ipslinux@adaptec.com>.
836 To compile this driver as a module, choose M here: the
837 module will be called ips.
840 tristate "IBM Virtual SCSI support"
841 depends on PPC_PSERIES || PPC_ISERIES
843 This is the IBM POWER Virtual SCSI Client
845 To compile this driver as a module, choose M here: the
846 module will be called ibmvscsic.
848 config SCSI_IBMVSCSIS
849 tristate "IBM Virtual SCSI Server support"
850 depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
852 This is the SRP target driver for IBM pSeries virtual environments.
854 The userspace component needed to initialize the driver and
855 documentation can be found:
857 http://stgt.berlios.de/
859 To compile this driver as a module, choose M here: the
860 module will be called ibmvstgt.
863 tristate "Initio 9100U(W) support"
864 depends on PCI && SCSI
866 This is support for the Initio 91XXU(W) SCSI host adapter. Please
867 read the SCSI-HOWTO, available from
868 <http://www.tldp.org/docs.html#howto>.
870 To compile this driver as a module, choose M here: the
871 module will be called initio.
874 tristate "Initio INI-A100U2W support"
875 depends on PCI && SCSI
877 This is support for the Initio INI-A100U2W SCSI host adapter.
878 Please read the SCSI-HOWTO, available from
879 <http://www.tldp.org/docs.html#howto>.
881 To compile this driver as a module, choose M here: the
882 module will be called a100u2w.
885 tristate "IOMEGA parallel port (ppa - older drives)"
886 depends on SCSI && PARPORT_PC
888 This driver supports older versions of IOMEGA's parallel port ZIP
889 drive (a 100 MB removable media device).
891 Note that you can say N here if you have the SCSI version of the ZIP
892 drive: it will be supported automatically if you said Y to the
893 generic "SCSI disk support", above.
895 If you have the ZIP Plus drive or a more recent parallel port ZIP
896 drive (if the supplied cable with the drive is labeled "AutoDetect")
897 then you should say N here and Y to "IOMEGA parallel port (imm -
898 newer drives)", below.
900 For more information about this driver and how to use it you should
901 read the file <file:Documentation/scsi/ppa.txt>. You should also read
902 the SCSI-HOWTO, which is available from
903 <http://www.tldp.org/docs.html#howto>. If you use this driver,
904 you will still be able to use the parallel port for other tasks,
905 such as a printer; it is safe to compile both drivers into the
908 To compile this driver as a module, choose M here: the
909 module will be called ppa.
912 tristate "IOMEGA parallel port (imm - newer drives)"
913 depends on SCSI && PARPORT_PC
915 This driver supports newer versions of IOMEGA's parallel port ZIP
916 drive (a 100 MB removable media device).
918 Note that you can say N here if you have the SCSI version of the ZIP
919 drive: it will be supported automatically if you said Y to the
920 generic "SCSI disk support", above.
922 If you have the ZIP Plus drive or a more recent parallel port ZIP
923 drive (if the supplied cable with the drive is labeled "AutoDetect")
924 then you should say Y here; if you have an older ZIP drive, say N
925 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
927 For more information about this driver and how to use it you should
928 read the file <file:Documentation/scsi/ppa.txt>. You should also read
929 the SCSI-HOWTO, which is available from
930 <http://www.tldp.org/docs.html#howto>. If you use this driver,
931 you will still be able to use the parallel port for other tasks,
932 such as a printer; it is safe to compile both drivers into the
935 To compile this driver as a module, choose M here: the
936 module will be called imm.
938 config SCSI_IZIP_EPP16
939 bool "ppa/imm option - Use slow (but safe) EPP-16"
940 depends on SCSI_PPA || SCSI_IMM
942 EPP (Enhanced Parallel Port) is a standard for parallel ports which
943 allows them to act as expansion buses that can handle up to 64
946 Some parallel port chipsets are slower than their motherboard, and
947 so we have to control the state of the chipset's FIFO queue every
948 now and then to avoid data loss. This will be done if you say Y
951 Generally, saying Y is the safe option and slows things down a bit.
953 config SCSI_IZIP_SLOW_CTR
954 bool "ppa/imm option - Assume slow parport control register"
955 depends on SCSI_PPA || SCSI_IMM
957 Some parallel ports are known to have excessive delays between
958 changing the parallel port control register and good data being
959 available on the parallel port data/status register. This option
960 forces a small delay (1.0 usec to be exact) after changing the
961 control register to let things settle out. Enabling this option may
962 result in a big drop in performance but some very old parallel ports
963 (found in 386 vintage machines) will not work properly.
965 Generally, saying N is fine.
967 config SCSI_NCR53C406A
968 tristate "NCR53c406a SCSI support"
969 depends on ISA && SCSI
971 This is support for the NCR53c406a SCSI host adapter. For user
972 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
973 in the kernel source. Also read the SCSI-HOWTO, available from
974 <http://www.tldp.org/docs.html#howto>.
976 To compile this driver as a module, choose M here: the
977 module will be called NCR53c406.
980 tristate "NCR Dual 700 MCA SCSI support"
981 depends on MCA && SCSI
982 select SCSI_SPI_ATTRS
984 This is a driver for the MicroChannel Dual 700 card produced by
985 NCR and commonly used in 345x/35xx/4100 class machines. It always
986 tries to negotiate sync and uses tag command queueing.
988 Unless you have an NCR manufactured machine, the chances are that
989 you do not have this SCSI card, so say N.
992 tristate "HP Lasi SCSI support for 53c700/710"
993 depends on GSC && SCSI
994 select SCSI_SPI_ATTRS
996 This is a driver for the SCSI controller in the Lasi chip found in
997 many PA-RISC workstations & servers. If you do not know whether you
998 have a Lasi chip, it is safe to say "Y" here.
1000 config SCSI_SNI_53C710
1001 tristate "SNI RM SCSI support for 53c710"
1002 depends on SNI_RM && SCSI
1003 select SCSI_SPI_ATTRS
1004 select 53C700_LE_ON_BE
1006 This is a driver for the onboard SCSI controller found in older
1007 SNI RM workstations & servers.
1009 config 53C700_LE_ON_BE
1011 depends on SCSI_LASI700
1015 tristate "Promise SuperTrak EX Series support"
1016 depends on PCI && SCSI
1018 This driver supports Promise SuperTrak EX series storage controllers.
1020 Promise provides Linux RAID configuration utility for these
1021 controllers. Please visit <http://www.promise.com> to download.
1023 To compile this driver as a module, choose M here: the
1024 module will be called stex.
1026 config 53C700_BE_BUS
1028 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1031 config SCSI_SYM53C8XX_2
1032 tristate "SYM53C8XX Version 2 SCSI support"
1033 depends on PCI && SCSI
1034 select SCSI_SPI_ATTRS
1036 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1037 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1038 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1039 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1040 controllers; you need to use the Fusion MPT driver for that.
1042 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1045 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1046 int "DMA addressing mode"
1047 depends on SCSI_SYM53C8XX_2
1050 This option only applies to PCI-SCSI chips that are PCI DAC
1051 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1053 When set to 0, the driver will program the chip to only perform
1054 32-bit DMA. When set to 1, the chip will be able to perform DMA
1055 to addresses up to 1TB. When set to 2, the driver supports the
1056 full 64-bit DMA address range, but can only address 16 segments
1057 of 4 GB each. This limits the total addressable range to 64 GB.
1059 Most machines with less than 4GB of memory should use a setting
1060 of 0 for best performance. If your machine has 4GB of memory
1061 or more, you should set this option to 1 (the default).
1063 The still experimental value 2 (64 bit DMA addressing with 16
1064 x 4GB segments limitation) can be used on systems that require
1065 PCI address bits past bit 39 to be set for the addressing of
1066 memory using PCI DAC cycles.
1068 config SCSI_SYM53C8XX_DEFAULT_TAGS
1069 int "Default tagged command queue depth"
1070 depends on SCSI_SYM53C8XX_2
1073 This is the default value of the command queue depth the
1074 driver will announce to the generic SCSI layer for devices
1075 that support tagged command queueing. This value can be changed
1076 from the boot command line. This is a soft limit that cannot
1077 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1079 config SCSI_SYM53C8XX_MAX_TAGS
1080 int "Maximum number of queued commands"
1081 depends on SCSI_SYM53C8XX_2
1084 This option allows you to specify the maximum number of commands
1085 that can be queued to any device, when tagged command queuing is
1086 possible. The driver supports up to 256 queued commands per device.
1087 This value is used as a compiled-in hard limit.
1089 config SCSI_SYM53C8XX_MMIO
1090 bool "Use memory mapped IO"
1091 depends on SCSI_SYM53C8XX_2
1094 Memory mapped IO is faster than Port IO. Most people should
1095 answer Y here, but some machines may have problems. If you have
1096 to answer N here, please report the problem to the maintainer.
1099 tristate "IBM Power Linux RAID adapter support"
1100 depends on PCI && SCSI && ATA
1103 This driver supports the IBM Power Linux family RAID adapters.
1104 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1105 as IBM iSeries 5702, 5703, 5709, and 570A.
1107 config SCSI_IPR_TRACE
1108 bool "enable driver internal trace"
1112 If you say Y here, the driver will trace all commands issued
1113 to the adapter. Performance impact is minimal. Trace can be
1114 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1116 config SCSI_IPR_DUMP
1117 bool "enable adapter dump support"
1121 If you say Y here, the driver will support adapter crash dump.
1122 If you enable this support, the iprdump daemon can be used
1123 to capture adapter failure analysis information.
1126 tristate "Zalon SCSI support"
1127 depends on GSC && SCSI
1128 select SCSI_SPI_ATTRS
1130 The Zalon is a GSC/HSC bus interface chip that sits between the
1131 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1132 C110, J200, J210 and some D, K & R-class machines. It's also
1133 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1134 Say Y here if you have one of these machines or cards.
1136 config SCSI_NCR_Q720
1137 tristate "NCR Quad 720 MCA SCSI support"
1138 depends on MCA && SCSI
1139 select SCSI_SPI_ATTRS
1141 This is a driver for the MicroChannel Quad 720 card produced by
1142 NCR and commonly used in 345x/35xx/4100 class machines. It always
1143 tries to negotiate sync and uses tag command queueing.
1145 Unless you have an NCR manufactured machine, the chances are that
1146 you do not have this SCSI card, so say N.
1148 config SCSI_NCR53C8XX_DEFAULT_TAGS
1149 int "default tagged command queue depth"
1150 depends on SCSI_ZALON || SCSI_NCR_Q720
1153 "Tagged command queuing" is a feature of SCSI-2 which improves
1154 performance: the host adapter can send several SCSI commands to a
1155 device's queue even if previous commands haven't finished yet.
1156 Because the device is intelligent, it can optimize its operations
1157 (like head positioning) based on its own request queue. Some SCSI
1158 devices don't implement this properly; if you want to disable this
1159 feature, enter 0 or 1 here (it doesn't matter which).
1161 The default value is 8 and should be supported by most hard disks.
1162 This value can be overridden from the boot command line using the
1163 'tags' option as follows (example):
1164 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1165 4, set queue depth to 16 for target 2 and target 3 on controller 0
1166 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1168 The normal answer therefore is to go with the default 8 and to use
1169 a boot command line option for devices that need to use a different
1170 command queue depth.
1172 There is no safe option other than using good SCSI devices.
1174 config SCSI_NCR53C8XX_MAX_TAGS
1175 int "maximum number of queued commands"
1176 depends on SCSI_ZALON || SCSI_NCR_Q720
1179 This option allows you to specify the maximum number of commands
1180 that can be queued to any device, when tagged command queuing is
1181 possible. The default value is 32. Minimum is 2, maximum is 64.
1182 Modern hard disks are able to support 64 tags and even more, but
1183 do not seem to be faster when more than 32 tags are being used.
1185 So, the normal answer here is to go with the default value 32 unless
1186 you are using very large hard disks with large cache (>= 1 MB) that
1187 are able to take advantage of more than 32 tagged commands.
1189 There is no safe option and the default answer is recommended.
1191 config SCSI_NCR53C8XX_SYNC
1192 int "synchronous transfers frequency in MHz"
1193 depends on SCSI_ZALON || SCSI_NCR_Q720
1196 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1197 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1198 are respectively the maximum data transfer rates in mega-transfers
1199 per second for each class. For example, a FAST-20 Wide 16 device is
1200 able to transfer data at 20 million 16 bit packets per second for a
1201 total rate of 40 MB/s.
1203 You may specify 0 if you want to only use asynchronous data
1204 transfers. This is the safest and slowest option. Otherwise, specify
1205 a value between 5 and 80, depending on the capability of your SCSI
1206 controller. The higher the number, the faster the data transfer.
1207 Note that 80 should normally be ok since the driver decreases the
1208 value automatically according to the controller's capabilities.
1210 Your answer to this question is ignored for controllers with NVRAM,
1211 since the driver will get this information from the user set-up. It
1212 also can be overridden using a boot setup option, as follows
1213 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1214 for FAST-20 synchronous data transfer (20 mega-transfers per
1217 The normal answer therefore is not to go with the default but to
1218 select the maximum value 80 allowing the driver to use the maximum
1219 value supported by each controller. If this causes problems with
1220 your SCSI devices, you should come back and decrease the value.
1222 There is no safe option other than using good cabling, right
1223 terminations and SCSI conformant devices.
1225 config SCSI_NCR53C8XX_NO_DISCONNECT
1226 bool "not allow targets to disconnect"
1227 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1229 This option is only provided for safety if you suspect some SCSI
1230 device of yours to not support properly the target-disconnect
1231 feature. In that case, you would say Y here. In general however, to
1232 not allow targets to disconnect is not reasonable if there is more
1233 than 1 device on a SCSI bus. The normal answer therefore is N.
1235 config SCSI_MCA_53C9X
1236 tristate "NCR MCA 53C9x SCSI support"
1237 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1239 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1240 controller based on the NCR 53C94. This driver will allow use of
1241 the controller on the 3550, and very possibly others.
1243 To compile this driver as a module, choose M here: the
1244 module will be called mca_53c9x.
1247 tristate "PAS16 SCSI support"
1248 depends on ISA && SCSI
1249 select SCSI_SPI_ATTRS
1251 This is support for a SCSI host adapter. It is explained in section
1252 3.10 of the SCSI-HOWTO, available from
1253 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1254 of the box, you may have to change some settings in
1255 <file:drivers/scsi/pas16.h>.
1257 To compile this driver as a module, choose M here: the
1258 module will be called pas16.
1261 tristate "PSI240i support"
1262 depends on ISA && SCSI
1264 This is support for the PSI240i EIDE interface card which acts as a
1265 SCSI host adapter. Please read the SCSI-HOWTO, available from
1266 <http://www.tldp.org/docs.html#howto>.
1268 To compile this driver as a module, choose M here: the
1269 module will be called psi240i.
1271 config SCSI_QLOGIC_FAS
1272 tristate "Qlogic FAS SCSI support"
1273 depends on ISA && SCSI
1275 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1276 FastSCSI! cards as well as any other card based on the FASXX chip
1277 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1279 This driver does NOT support the PCI versions of these cards. The
1280 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1281 SCSI support"), below.
1283 Information about this driver is contained in
1284 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1285 SCSI-HOWTO, available from
1286 <http://www.tldp.org/docs.html#howto>.
1288 To compile this driver as a module, choose M here: the
1289 module will be called qlogicfas.
1291 config SCSI_QLOGIC_FC_FIRMWARE
1292 bool "Include loadable firmware in driver"
1293 depends on SCSI_QLOGIC_FC
1295 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1296 expanded LUN addressing and FcTape (FCP-2) support, in the
1297 qlogicfc driver. This is required on some platforms.
1299 config SCSI_QLOGIC_1280
1300 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1301 depends on PCI && SCSI
1303 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1305 To compile this driver as a module, choose M here: the
1306 module will be called qla1280.
1308 config SCSI_QLOGICPTI
1309 tristate "PTI Qlogic, ISP Driver"
1310 depends on SBUS && SCSI
1312 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1313 controllers are known under Solaris as qpti and in the openprom as
1314 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1315 driven by a different driver.
1317 To compile this driver as a module, choose M here: the
1318 module will be called qlogicpti.
1320 source "drivers/scsi/qla2xxx/Kconfig"
1321 source "drivers/scsi/qla4xxx/Kconfig"
1324 tristate "Emulex LightPulse Fibre Channel Support"
1325 depends on PCI && SCSI
1326 select SCSI_FC_ATTRS
1328 This lpfc driver supports the Emulex LightPulse
1329 Family of Fibre Channel PCI host adapters.
1332 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1333 depends on X86 && ISA && SCSI
1335 These are 8-bit SCSI controllers; the ST-01 is also supported by
1336 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1337 available from <http://www.tldp.org/docs.html#howto>. If it
1338 doesn't work out of the box, you may have to change some macros at
1339 compiletime, which are described in <file:drivers/scsi/seagate.c>.
1341 To compile this driver as a module, choose M here: the
1342 module will be called seagate.
1344 # definitely looks not 64bit safe:
1346 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1347 depends on (EISA || MCA) && SCSI
1348 select SCSI_SPI_ATTRS
1350 This driver for NCR53c710 based SCSI host adapters.
1352 It currently supports Compaq EISA cards and NCR MCA cards
1354 config SCSI_SYM53C416
1355 tristate "Symbios 53c416 SCSI support"
1356 depends on ISA && SCSI
1358 This is support for the sym53c416 SCSI host adapter, the SCSI
1359 adapter that comes with some HP scanners. This driver requires that
1360 the sym53c416 is configured first using some sort of PnP
1361 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1362 are using isapnp then you need to compile this driver as a module
1363 and then load it using insmod after isapnp has run. The parameters
1364 of the configured card(s) should be passed to the driver. The format
1367 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1369 To compile this driver as a module, choose M here: the
1370 module will be called sym53c416.
1373 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1374 depends on PCI && SCSI && EXPERIMENTAL
1376 This driver supports PCI SCSI host adapters based on the ASIC
1377 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1379 This driver works, but is still in experimental status. So better
1380 have a bootable disk and a backup in case of emergency.
1382 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1384 To compile this driver as a module, choose M here: the
1385 module will be called dc395x.
1388 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1389 depends on PCI && SCSI
1391 This driver supports PCI SCSI host adapters based on the Am53C974A
1392 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1393 PCscsi/PCnet (Am53/79C974) solutions.
1395 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1397 Note that this driver does NOT support Tekram DC390W/U/F, which are
1398 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1400 To compile this driver as a module, choose M here: the
1401 module will be called tmscsim.
1404 tristate "Trantor T128/T128F/T228 SCSI support"
1405 depends on ISA && SCSI
1406 select SCSI_SPI_ATTRS
1408 This is support for a SCSI host adapter. It is explained in section
1409 3.11 of the SCSI-HOWTO, available from
1410 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1411 of the box, you may have to change some settings in
1412 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1413 Adaptec, and some former Trantor products are being sold under the
1416 To compile this driver as a module, choose M here: the
1417 module will be called t128.
1420 tristate "UltraStor 14F/34F support"
1421 depends on ISA && SCSI && ISA_DMA_API
1423 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1424 The source at <file:drivers/scsi/u14-34f.c> contains some
1425 information about this hardware. If the driver doesn't work out of
1426 the box, you may have to change some settings in
1427 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1428 <http://www.tldp.org/docs.html#howto>. Note that there is also
1429 another driver for the same hardware: "UltraStor SCSI support",
1430 below. You should say Y to both only if you want 24F support as
1433 To compile this driver as a module, choose M here: the
1434 module will be called u14-34f.
1436 config SCSI_U14_34F_TAGGED_QUEUE
1437 bool "enable tagged command queueing"
1438 depends on SCSI_U14_34F
1440 This is a feature of SCSI-2 which improves performance: the host
1441 adapter can send several SCSI commands to a device's queue even if
1442 previous commands haven't finished yet.
1443 This is equivalent to the "u14-34f=tc:y" boot option.
1445 config SCSI_U14_34F_LINKED_COMMANDS
1446 bool "enable elevator sorting"
1447 depends on SCSI_U14_34F
1449 This option enables elevator sorting for all probed SCSI disks and
1450 CD-ROMs. It definitely reduces the average seek distance when doing
1451 random seeks, but this does not necessarily result in a noticeable
1452 performance improvement: your mileage may vary...
1453 This is equivalent to the "u14-34f=lc:y" boot option.
1455 config SCSI_U14_34F_MAX_TAGS
1456 int "maximum number of queued commands"
1457 depends on SCSI_U14_34F
1460 This specifies how many SCSI commands can be maximally queued for
1461 each probed SCSI device. You should reduce the default value of 8
1462 only if you have disks with buggy or limited tagged command support.
1463 Minimum is 2 and maximum is 14. This value is also the window size
1464 used by the elevator sorting option above. The effective value used
1465 by the driver for each probed SCSI device is reported at boot time.
1466 This is equivalent to the "u14-34f=mq:8" boot option.
1468 config SCSI_ULTRASTOR
1469 tristate "UltraStor SCSI support"
1470 depends on X86 && ISA && SCSI
1472 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1473 adapter family. This driver is explained in section 3.12 of the
1474 SCSI-HOWTO, available from
1475 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1476 of the box, you may have to change some settings in
1477 <file:drivers/scsi/ultrastor.h>.
1479 Note that there is also another driver for the same hardware:
1480 "UltraStor 14F/34F support", above.
1482 To compile this driver as a module, choose M here: the
1483 module will be called ultrastor.
1486 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1487 depends on PCI && SCSI && !64BIT
1489 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1490 SCSI host adapter. Please read the SCSI-HOWTO, available from
1491 <http://www.tldp.org/docs.html#howto>.
1493 To compile this driver as a module, choose M here: the
1494 module will be called nsp32.
1497 tristate "SCSI debugging host simulator"
1500 This is a host adapter simulator that can simulate multiple hosts
1501 each with multiple dummy SCSI devices (disks). It defaults to one
1502 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1503 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1504 dummy disks are simulated, they share the same kernel RAM for
1505 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1506 information. This driver is primarily of use to those testing the
1507 SCSI and block subsystems. If unsure, say N.
1510 tristate "MESH (Power Mac internal SCSI) support"
1511 depends on PPC32 && PPC_PMAC && SCSI
1513 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1514 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1515 other Power Macintoshes do). Say Y to include support for this SCSI
1518 To compile this driver as a module, choose M here: the
1519 module will be called mesh.
1521 config SCSI_MESH_SYNC_RATE
1522 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1523 depends on SCSI_MESH
1526 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1527 drives a bus which is entirely internal to the machine (such as the
1528 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1529 operation at up to 10 MB/s. On machines where the SCSI bus
1530 controlled by the MESH can have external devices connected, it is
1531 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1532 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1533 to disable synchronous operation.
1535 config SCSI_MESH_RESET_DELAY_MS
1536 int "initial bus reset delay (ms) (0 = no reset)"
1537 depends on SCSI_MESH
1540 config SCSI_MAC53C94
1541 tristate "53C94 (Power Mac external SCSI) support"
1542 depends on PPC32 && PPC_PMAC && SCSI
1544 On Power Macintoshes (and clones) with two SCSI buses, the external
1545 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1546 machines which only have one SCSI bus, such as the 7200, also use
1547 the 53C94. Say Y to include support for the 53C94.
1549 To compile this driver as a module, choose M here: the
1550 module will be called mac53c94.
1552 source "drivers/scsi/arm/Kconfig"
1555 bool "MIPS JAZZ FAS216 SCSI support"
1556 depends on MACH_JAZZ && SCSI
1557 select SCSI_SPI_ATTRS
1559 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1560 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1564 tristate "A3000 WD33C93A support"
1565 depends on AMIGA && SCSI
1567 If you have an Amiga 3000 and have SCSI devices connected to the
1568 built-in SCSI controller, say Y. Otherwise, say N.
1570 To compile this driver as a module, choose M here: the
1571 module will be called wd33c93.
1574 tristate "A2091/A590 WD33C93A support"
1575 depends on ZORRO && SCSI
1577 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1580 To compile this driver as a module, choose M here: the
1581 module will be called wd33c93.
1584 tristate "GVP Series II WD33C93A support"
1585 depends on ZORRO && SCSI
1587 If you have a Great Valley Products Series II SCSI controller,
1588 answer Y. Also say Y if you have a later model of GVP SCSI
1589 controller (such as the GVP A4008 or a Combo board). Otherwise,
1590 answer N. This driver does NOT work for the T-Rex series of
1591 accelerators from TekMagic and GVP-M.
1593 To compile this driver as a module, choose M here: the
1594 module will be called gvp11.
1596 config CYBERSTORM_SCSI
1597 tristate "CyberStorm SCSI support"
1598 depends on ZORRO && SCSI
1600 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1601 accelerator board and the optional Cyberstorm SCSI controller,
1602 answer Y. Otherwise, say N.
1604 config CYBERSTORMII_SCSI
1605 tristate "CyberStorm Mk II SCSI support"
1606 depends on ZORRO && SCSI
1608 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1609 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1613 tristate "Blizzard 2060 SCSI support"
1614 depends on ZORRO && SCSI
1616 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1617 and want to use the onboard SCSI controller, say Y. Otherwise,
1621 tristate "Blizzard 1230IV/1260 SCSI support"
1622 depends on ZORRO && SCSI
1624 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1625 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1628 config FASTLANE_SCSI
1629 tristate "Fastlane SCSI support"
1630 depends on ZORRO && SCSI
1632 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1633 one in the near future, say Y to this question. Otherwise, say N.
1636 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1637 depends on AMIGA && SCSI && EXPERIMENTAL
1638 select SCSI_SPI_ATTRS
1640 If you have an Amiga 4000T and have SCSI devices connected to the
1641 built-in SCSI controller, say Y. Otherwise, say N.
1643 To compile this driver as a module, choose M here: the
1644 module will be called a4000t.
1646 config SCSI_ZORRO7XX
1647 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1648 depends on ZORRO && SCSI && EXPERIMENTAL
1649 select SCSI_SPI_ATTRS
1651 Support for various NCR53c710-based SCSI controllers on Zorro
1652 expansion boards for the Amiga.
1654 - the Amiga 4091 Zorro III SCSI-2 controller,
1655 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1657 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1658 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1659 accelerator card for the Amiga 1200,
1660 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1663 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1664 depends on ZORRO && SCSI && EXPERIMENTAL
1666 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1667 Y to this question. If you're in doubt about whether you have one,
1669 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1672 tristate "Atari native SCSI support"
1673 depends on ATARI && SCSI
1674 select SCSI_SPI_ATTRS
1676 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1677 Falcon, ...) say Y to get it supported. Of course also, if you have
1678 a compatible SCSI controller (e.g. for Medusa).
1680 To compile this driver as a module, choose M here: the
1681 module will be called atari_scsi.
1683 This driver supports both styles of NCR integration into the
1684 system: the TT style (separate DMA), and the Falcon style (via
1685 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1686 in the Hades (without DMA).
1688 config ATARI_SCSI_TOSHIBA_DELAY
1689 bool "Long delays for Toshiba CD-ROMs"
1690 depends on ATARI_SCSI
1692 This option increases the delay after a SCSI arbitration to
1693 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1694 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1695 would impact performance a bit, so say N.
1697 config ATARI_SCSI_RESET_BOOT
1698 bool "Reset SCSI-devices at boottime"
1699 depends on ATARI_SCSI
1701 Reset the devices on your Atari whenever it boots. This makes the
1702 boot process fractionally longer but may assist recovery from errors
1703 that leave the devices with SCSI operations partway completed.
1706 bool "Hades SCSI DMA emulator"
1707 depends on ATARI_SCSI && HADES
1709 This option enables code which emulates the TT SCSI DMA chip on the
1710 Hades. This increases the SCSI transfer rates at least ten times
1711 compared to PIO transfers.
1714 bool "Macintosh NCR5380 SCSI"
1715 depends on MAC && SCSI=y
1716 select SCSI_SPI_ATTRS
1718 This is the NCR 5380 SCSI controller included on most of the 68030
1719 based Macintoshes. If you have one of these say Y and read the
1720 SCSI-HOWTO, available from
1721 <http://www.tldp.org/docs.html#howto>.
1724 tristate "Macintosh NCR53c9[46] SCSI"
1725 depends on MAC && SCSI
1727 This is the NCR 53c9x SCSI controller found on most of the 68040
1728 based Macintoshes. If you have one of these say Y and read the
1729 SCSI-HOWTO, available from
1730 <http://www.tldp.org/docs.html#howto>.
1732 To compile this driver as a module, choose M here: the
1733 module will be called mac_esp.
1736 bool "WD33C93 SCSI driver for MVME147"
1737 depends on MVME147 && SCSI=y
1738 select SCSI_SPI_ATTRS
1740 Support for the on-board SCSI controller on the Motorola MVME147
1741 single-board computer.
1744 tristate "NCR53C710 SCSI driver for MVME16x"
1745 depends on MVME16x && SCSI
1746 select SCSI_SPI_ATTRS
1748 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1749 SCSI controller chip. Almost everyone using one of these boards
1750 will want to say Y to this question.
1752 config BVME6000_SCSI
1753 tristate "NCR53C710 SCSI driver for BVME6000"
1754 depends on BVME6000 && SCSI
1755 select SCSI_SPI_ATTRS
1757 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1758 SCSI controller chip. Almost everyone using one of these boards
1759 will want to say Y to this question.
1762 tristate "Sun3 NCR5380 SCSI"
1763 depends on SUN3 && SCSI
1764 select SCSI_SPI_ATTRS
1766 This option will enable support for the OBIO (onboard io) NCR5380
1767 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1768 "Sun3" type VME scsi controllers also based on the NCR5380.
1769 General Linux information on the Sun 3 series (now discontinued)
1770 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1773 bool "Sun3x ESP SCSI"
1774 depends on SUN3X && SCSI=y
1776 The ESP was an on-board SCSI controller used on Sun 3/80
1777 machines. Say Y here to compile in support for it.
1780 tristate "Sparc ESP Scsi Driver"
1781 depends on SBUS && SCSI
1782 select SCSI_SPI_ATTRS
1784 This is the driver for the Sun ESP SCSI host adapter. The ESP
1785 chipset is present in most SPARC SBUS-based computers.
1787 To compile this driver as a module, choose M here: the
1788 module will be called esp.
1791 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1792 depends on S390 && QDIO && SCSI
1793 select SCSI_FC_ATTRS
1795 If you want to access SCSI devices attached to your IBM eServer
1796 zSeries by means of Fibre Channel interfaces say Y.
1797 For details please refer to the documentation provided by IBM at
1798 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1800 This driver is also available as a module. This module will be
1801 called zfcp. If you want to compile it as a module, say M here
1802 and read <file:Documentation/kbuild/modules.txt>.
1805 tristate "SCSI RDMA Protocol helper library"
1806 depends on SCSI && PCI
1809 If you wish to use SRP target drivers, say Y.
1811 To compile this driver as a module, choose M here: the
1812 module will be called libsrp.
1814 endif # SCSI_LOWLEVEL
1816 source "drivers/scsi/pcmcia/Kconfig"