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, and FireWire storage.
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"
66 select CRC_T10DIF if BLK_DEV_INTEGRITY
68 If you want to use SCSI hard disks, Fibre Channel disks,
69 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
70 USB storage or the SCSI or parallel port version of
71 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
72 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
73 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
76 To compile this driver as a module, choose M here and read
77 <file:Documentation/scsi/scsi.txt>.
78 The module will be called sd_mod.
80 Do not compile this driver as a module if your root file system
81 (the one containing the directory /) is located on a SCSI disk.
82 In this case, do not compile the driver for your SCSI host adapter
83 (below) as a module either.
86 tristate "SCSI tape support"
89 If you want to use a SCSI tape drive under Linux, say Y and read the
90 SCSI-HOWTO, available from
91 <http://www.tldp.org/docs.html#howto>, and
92 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
95 To compile this driver as a module, choose M here and read
96 <file:Documentation/scsi/scsi.txt>. The module will be called st.
99 tristate "SCSI OnStream SC-x0 tape support"
102 The OnStream SC-x0 SCSI tape drives cannot be driven by the
103 standard st driver, but instead need this special osst driver and
104 use the /dev/osstX char device nodes (major 206). Via usb-storage,
105 you may be able to drive the USB-x0 and DI-x0 drives as well.
106 Note that there is also a second generation of OnStream
107 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
108 tapes (QIC-157) and can be driven by the standard driver st.
109 For more information, you may have a look at the SCSI-HOWTO
110 <http://www.tldp.org/docs.html#howto> and
111 <file:Documentation/scsi/osst.txt> in the kernel source.
112 More info on the OnStream driver may be found on
113 <http://linux1.onstream.nl/test/>
114 Please also have a look at the standard st docu, as most of it
115 applies to osst as well.
117 To compile this driver as a module, choose M here and read
118 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
121 tristate "SCSI CDROM support"
124 If you want to use a SCSI or FireWire CD-ROM under Linux,
125 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
126 <http://www.tldp.org/docs.html#howto>. Also make sure to say
127 Y or M to "ISO 9660 CD-ROM file system support" later.
129 To compile this driver as a module, choose M here and read
130 <file:Documentation/scsi/scsi.txt>.
131 The module will be called sr_mod.
133 config BLK_DEV_SR_VENDOR
134 bool "Enable vendor-specific extensions (for SCSI CDROM)"
135 depends on BLK_DEV_SR
137 This enables the usage of vendor specific SCSI commands. This is
138 required to support multisession CDs with old NEC/TOSHIBA cdrom
139 drives (and HP Writers). If you have such a drive and get the first
140 session only, try saying Y here; everybody else says N.
143 tristate "SCSI generic support"
146 If you want to use SCSI scanners, synthesizers or CD-writers or just
147 about anything having "SCSI" in its name other than hard disks,
148 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
149 directly, so you need some additional software which knows how to
150 talk to these devices using the SCSI protocol:
152 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
153 writer software look at Cdrtools
154 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
155 and for burning a "disk at once": CDRDAO
156 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
157 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
158 For other devices, it's possible that you'll have to write the
159 driver software yourself. Please read the file
160 <file:Documentation/scsi/scsi-generic.txt> for more information.
162 To compile this driver as a module, choose M here and read
163 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
168 tristate "SCSI media changer support"
171 This is a driver for SCSI media changers. Most common devices are
172 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
173 don't need this for those tiny 6-slot cdrom changers. Media
174 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
175 If you have such hardware and want to use it with linux, say Y
176 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
178 If you want to compile this as a module ( = code which can be
179 inserted in and removed from the running kernel whenever you want),
180 say M here and read <file:Documentation/kbuild/modules.txt> and
181 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
184 config SCSI_ENCLOSURE
185 tristate "SCSI Enclosure Support"
186 depends on SCSI && ENCLOSURE_SERVICES
188 Enclosures are devices sitting on or in SCSI backplanes that
189 manage devices. If you have a disk cage, the chances are that
190 it has an enclosure device. Selecting this option will just allow
191 certain enclosure conditions to be reported and is not required.
193 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
196 config SCSI_MULTI_LUN
197 bool "Probe all LUNs on each SCSI device"
200 If you have a SCSI device that supports more than one LUN (Logical
201 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
202 can say Y here to force the SCSI driver to probe for multiple LUNs.
203 A SCSI device with multiple LUNs acts logically like multiple SCSI
204 devices. The vast majority of SCSI devices have only one LUN, and
205 so most people can say N here. The max_luns boot/module parameter
206 allows to override this setting.
208 config SCSI_CONSTANTS
209 bool "Verbose SCSI error reporting (kernel size +=12K)"
212 The error messages regarding your SCSI hardware will be easier to
213 understand if you say Y here; it will enlarge your kernel by about
214 12 KB. If in doubt, say Y.
217 bool "SCSI logging facility"
220 This turns on a logging facility that can be used to debug a number
221 of SCSI related problems.
223 If you say Y here, no logging output will appear by default, but you
224 can enable logging by saying Y to "/proc file system support" and
225 "Sysctl support" below and executing the command
227 echo "scsi log token [level]" > /proc/scsi/scsi
229 at boot time after the /proc file system has been mounted.
231 There are a number of things that can be used for 'token' (you can
232 find them in the source: <file:drivers/scsi/scsi.c>), and this
233 allows you to select the types of information you want, and the
234 level allows you to select the level of verbosity.
236 If you say N here, it may be harder to track down some types of SCSI
237 problems. If you say Y here your kernel will be somewhat larger, but
238 there should be no noticeable performance impact as long as you have
241 config SCSI_SCAN_ASYNC
242 bool "Asynchronous SCSI scanning"
245 The SCSI subsystem can probe for devices while the rest of the
246 system continues booting, and even probe devices on different
247 busses in parallel, leading to a significant speed-up.
249 If you have built SCSI as modules, enabling this option can
250 be a problem as the devices may not have been found by the
251 time your system expects them to have been. You can load the
252 scsi_wait_scan module to ensure that all scans have completed.
253 If you build your SCSI drivers into the kernel, then everything
254 will work fine if you say Y here.
256 You can override this choice by specifying "scsi_mod.scan=sync"
257 or async on the kernel's command line.
259 config SCSI_WAIT_SCAN
265 menu "SCSI Transports"
268 config SCSI_SPI_ATTRS
269 tristate "Parallel SCSI (SPI) Transport Attributes"
272 If you wish to export transport-specific information about
273 each attached SCSI device to sysfs, say Y. Otherwise, say N.
276 tristate "FiberChannel Transport Attributes"
280 If you wish to export transport-specific information about
281 each attached FiberChannel device to sysfs, say Y.
284 config SCSI_FC_TGT_ATTRS
285 bool "SCSI target support for FiberChannel Transport Attributes"
286 depends on SCSI_FC_ATTRS
287 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
289 If you want to use SCSI target mode drivers enable this option.
291 config SCSI_ISCSI_ATTRS
292 tristate "iSCSI Transport Attributes"
293 depends on SCSI && NET
295 If you wish to export transport-specific information about
296 each attached iSCSI device to sysfs, say Y.
299 config SCSI_SAS_ATTRS
300 tristate "SAS Transport Attributes"
301 depends on SCSI && BLK_DEV_BSG
303 If you wish to export transport-specific information about
304 each attached SAS device to sysfs, say Y.
306 source "drivers/scsi/libsas/Kconfig"
308 config SCSI_SRP_ATTRS
309 tristate "SRP Transport Attributes"
312 If you wish to export transport-specific information about
313 each attached SRP device to sysfs, say Y.
315 config SCSI_SRP_TGT_ATTRS
316 bool "SCSI target support for SRP Transport Attributes"
317 depends on SCSI_SRP_ATTRS
318 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
320 If you want to use SCSI target mode drivers enable this option.
324 menuconfig SCSI_LOWLEVEL
325 bool "SCSI low-level drivers"
329 if SCSI_LOWLEVEL && SCSI
332 tristate "iSCSI Initiator over TCP/IP"
333 depends on SCSI && INET
337 select SCSI_ISCSI_ATTRS
339 The iSCSI Driver provides a host with the ability to access storage
340 through an IP network. The driver uses the iSCSI protocol to transport
341 SCSI requests and responses over a TCP/IP network between the host
342 (the "initiator") and "targets". Architecturally, the iSCSI driver
343 combines with the host's TCP/IP stack, network drivers, and Network
344 Interface Card (NIC) to provide the same functions as a SCSI or a
345 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
347 To compile this driver as a module, choose M here: the
348 module will be called iscsi_tcp.
350 The userspace component needed to initialize the driver, documentation,
351 and sample configuration files can be found here:
353 http://open-iscsi.org
355 source "drivers/scsi/cxgb3i/Kconfig"
358 tristate "SGI WD93C93 SCSI Driver"
359 depends on SGI_HAS_WD93 && SCSI
361 If you have a Western Digital WD93 SCSI controller on
362 an SGI MIPS system, say Y. Otherwise, say N.
364 config BLK_DEV_3W_XXXX_RAID
365 tristate "3ware 5/6/7/8xxx ATA-RAID support"
366 depends on PCI && SCSI
368 3ware is the only hardware ATA-Raid product in Linux to date.
369 This card is 2,4, or 8 channel master mode support only.
370 SCSI support required!!!
372 <http://www.3ware.com/>
374 Please read the comments at the top of
375 <file:drivers/scsi/3w-xxxx.c>.
378 tristate "3ware 9xxx SATA-RAID support"
379 depends on PCI && SCSI
381 This driver supports the 9000 series 3ware SATA-RAID cards.
383 <http://www.amcc.com>
385 Please read the comments at the top of
386 <file:drivers/scsi/3w-9xxx.c>.
388 config SCSI_7000FASST
389 tristate "7000FASST SCSI support"
390 depends on ISA && SCSI && ISA_DMA_API
391 select CHECK_SIGNATURE
393 This driver supports the Western Digital 7000 SCSI host adapter
394 family. Some information is in the source:
395 <file:drivers/scsi/wd7000.c>.
397 To compile this driver as a module, choose M here: the
398 module will be called wd7000.
401 tristate "ACARD SCSI support"
402 depends on PCI && SCSI
404 This driver supports the ACARD SCSI host adapter.
405 Support Chip <ATP870 ATP876 ATP880 ATP885>
406 To compile this driver as a module, choose M here: the
407 module will be called atp870u.
410 tristate "Adaptec AHA152X/2825 support"
411 depends on ISA && SCSI && !64BIT
412 select SCSI_SPI_ATTRS
413 select CHECK_SIGNATURE
415 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
416 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
417 must be manually specified in this case.
419 It is explained in section 3.3 of the SCSI-HOWTO, available from
420 <http://www.tldp.org/docs.html#howto>. You might also want to
421 read the file <file:Documentation/scsi/aha152x.txt>.
423 To compile this driver as a module, choose M here: the
424 module will be called aha152x.
427 tristate "Adaptec AHA1542 support"
428 depends on ISA && SCSI && ISA_DMA_API
430 This is support for a SCSI host adapter. It is explained in section
431 3.4 of the SCSI-HOWTO, available from
432 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
433 purchased by Adaptec, and some former Trantor products are being
434 sold under the Adaptec name. If it doesn't work out of the box, you
435 may have to change some settings in <file:drivers/scsi/aha1542.h>.
437 To compile this driver as a module, choose M here: the
438 module will be called aha1542.
441 tristate "Adaptec AHA1740 support"
442 depends on EISA && SCSI
444 This is support for a SCSI host adapter. It is explained in section
445 3.5 of the SCSI-HOWTO, available from
446 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
447 of the box, you may have to change some settings in
448 <file:drivers/scsi/aha1740.h>.
450 To compile this driver as a module, choose M here: the
451 module will be called aha1740.
454 tristate "Adaptec AACRAID support"
455 depends on SCSI && PCI
457 This driver supports a variety of Dell, HP, Adaptec, IBM and
458 ICP storage products. For a list of supported products, refer
459 to <file:Documentation/scsi/aacraid.txt>.
461 To compile this driver as a module, choose M here: the module
462 will be called aacraid.
465 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
467 config SCSI_AIC7XXX_OLD
468 tristate "Adaptec AIC7xxx support (old driver)"
469 depends on (ISA || EISA || PCI ) && SCSI
471 WARNING This driver is an older aic7xxx driver and is no longer
472 under active development. Adaptec, Inc. is writing a new driver to
473 take the place of this one, and it is recommended that whenever
474 possible, people should use the new Adaptec written driver instead
475 of this one. This driver will eventually be phased out entirely.
477 This is support for the various aic7xxx based Adaptec SCSI
478 controllers. These include the 274x EISA cards; 284x VLB cards;
479 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
480 motherboard based SCSI controllers from Adaptec. It does not support
481 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
482 support them. It does not support the 2920 cards from Adaptec that
483 use the Future Domain SCSI controller chip. For those cards, you
484 need the "Future Domain 16xx SCSI support" driver.
486 In general, if the controller is based on an Adaptec SCSI controller
487 chip from the aic777x series or the aic78xx series, this driver
488 should work. The only exception is the 7810 which is specifically
489 not supported (that's the RAID controller chip on the AAA-13x
492 Note that the AHA2920 SCSI host adapter is *not* supported by this
493 driver; choose "Future Domain 16xx SCSI support" instead if you have
496 Information on the configuration options for this controller can be
497 found by checking the help file for each of the available
498 configuration options. You should read
499 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
500 contacting the maintainer with any questions. The SCSI-HOWTO,
501 available from <http://www.tldp.org/docs.html#howto>, can also
504 To compile this driver as a module, choose M here: the
505 module will be called aic7xxx_old.
507 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
508 source "drivers/scsi/aic94xx/Kconfig"
511 tristate "Adaptec I2O RAID support "
512 depends on SCSI && PCI && VIRT_TO_BUS
514 This driver supports all of Adaptec's I2O based RAID controllers as
515 well as the DPT SmartRaid V cards. This is an Adaptec maintained
516 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
518 To compile this driver as a module, choose M here: the
519 module will be called dpt_i2o.
522 tristate "AdvanSys SCSI support"
523 depends on SCSI && VIRT_TO_BUS
524 depends on ISA || EISA || PCI
526 This is a driver for all SCSI host adapters manufactured by
527 AdvanSys. It is documented in the kernel source in
528 <file:drivers/scsi/advansys.c>.
530 To compile this driver as a module, choose M here: the
531 module will be called advansys.
534 tristate "Always IN2000 SCSI support"
535 depends on ISA && SCSI
537 This is support for an ISA bus SCSI host adapter. You'll find more
538 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
539 out of the box, you may have to change the jumpers for IRQ or
542 To compile this driver as a module, choose M here: the
543 module will be called in2000.
546 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
547 depends on PCI && SCSI
549 This driver supports all of ARECA's SATA/SAS RAID controller cards.
550 This is an ARECA-maintained driver by Erich Chen.
551 If you have any problems, please mail to: <erich@areca.com.tw>.
552 Areca supports Linux RAID config tools.
553 Please link <http://www.areca.com.tw>
555 To compile this driver as a module, choose M here: the
556 module will be called arcmsr (modprobe arcmsr).
558 config SCSI_ARCMSR_AER
559 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
560 depends on SCSI_ARCMSR && PCIEAER
563 The advanced error reporting(AER) capability is "NOT" provided by
564 ARC1200/1201/1202 SATA RAID controllers cards.
565 If your card is one of ARC1200/1201/1202, please use the default setting, n.
566 If your card is other models, you could pick it
567 on condition that the kernel version is greater than 2.6.19.
568 This function is maintained driver by Nick Cheng. If you have any
569 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
570 To enable this function, choose Y here.
572 source "drivers/scsi/megaraid/Kconfig.megaraid"
575 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
576 depends on SCSI && PCI
578 This option enables support for HighPoint RocketRAID 3xxx/4xxx
581 To compile this driver as a module, choose M here; the module
582 will be called hptiop. If unsure, say N.
585 tristate "BusLogic SCSI support"
586 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
588 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
589 Adapters. Consult the SCSI-HOWTO, available from
590 <http://www.tldp.org/docs.html#howto>, and the files
591 <file:Documentation/scsi/BusLogic.txt> and
592 <file:Documentation/scsi/FlashPoint.txt> for more information.
593 Note that support for FlashPoint is only available for 32-bit
596 To compile this driver as a module, choose M here: the
597 module will be called BusLogic.
599 config SCSI_FLASHPOINT
600 bool "FlashPoint support"
601 depends on SCSI_BUSLOGIC && PCI && X86_32
603 This option allows you to add FlashPoint support to the
604 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
605 substantial, so users of MultiMaster Host Adapters may not
609 tristate "LibFC module"
612 Fibre Channel library module
615 tristate "FCoE module"
619 Fibre Channel over Ethernet module
622 tristate "DMX3191D SCSI support"
623 depends on PCI && SCSI
624 select SCSI_SPI_ATTRS
626 This is support for Domex DMX3191D SCSI Host Adapters.
628 To compile this driver as a module, choose M here: the
629 module will be called dmx3191d.
632 tristate "DTC3180/3280 SCSI support"
633 depends on ISA && SCSI
634 select SCSI_SPI_ATTRS
635 select CHECK_SIGNATURE
637 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
638 the SCSI-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>, and the file
640 <file:Documentation/scsi/dtc3x80.txt>.
642 To compile this driver as a module, choose M here: the
643 module will be called dtc.
646 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
647 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
649 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
650 ISA and all EISA I/O addresses are probed looking for the "EATA"
651 signature. The addresses of all the PCI SCSI controllers reported
652 by the PCI subsystem are probed as well.
654 You want to read the start of <file:drivers/scsi/eata.c> and the
655 SCSI-HOWTO, available from
656 <http://www.tldp.org/docs.html#howto>.
658 To compile this driver as a module, choose M here: the
659 module will be called eata.
661 config SCSI_EATA_TAGGED_QUEUE
662 bool "enable tagged command queueing"
665 This is a feature of SCSI-2 which improves performance: the host
666 adapter can send several SCSI commands to a device's queue even if
667 previous commands haven't finished yet.
668 This is equivalent to the "eata=tc:y" boot option.
670 config SCSI_EATA_LINKED_COMMANDS
671 bool "enable elevator sorting"
674 This option enables elevator sorting for all probed SCSI disks and
675 CD-ROMs. It definitely reduces the average seek distance when doing
676 random seeks, but this does not necessarily result in a noticeable
677 performance improvement: your mileage may vary...
678 This is equivalent to the "eata=lc:y" boot option.
680 config SCSI_EATA_MAX_TAGS
681 int "maximum number of queued commands"
685 This specifies how many SCSI commands can be maximally queued for
686 each probed SCSI device. You should reduce the default value of 16
687 only if you have disks with buggy or limited tagged command support.
688 Minimum is 2 and maximum is 62. This value is also the window size
689 used by the elevator sorting option above. The effective value used
690 by the driver for each probed SCSI device is reported at boot time.
691 This is equivalent to the "eata=mq:8" boot option.
694 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
695 depends on (ISA || EISA || PCI) && SCSI && BROKEN
697 This driver supports all EATA-PIO protocol compliant SCSI Host
698 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
699 host adapters could also use this driver but are discouraged from
700 doing so, since this driver only supports hard disks and lacks
701 numerous features. You might want to have a look at the SCSI-HOWTO,
702 available from <http://www.tldp.org/docs.html#howto>.
704 To compile this driver as a module, choose M here: the
705 module will be called eata_pio.
707 config SCSI_FUTURE_DOMAIN
708 tristate "Future Domain 16xx SCSI/AHA-2920A support"
709 depends on (ISA || PCI) && SCSI
710 select CHECK_SIGNATURE
712 This is support for Future Domain's 16-bit SCSI host adapters
713 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
714 other adapters based on the Future Domain chipsets (Quantum
715 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
716 It is explained in section 3.7 of the SCSI-HOWTO, available from
717 <http://www.tldp.org/docs.html#howto>.
719 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
720 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
721 controller support"). This Future Domain driver works with the older
722 Adaptec AHA-2920A boards with a Future Domain chip on them.
724 To compile this driver as a module, choose M here: the
725 module will be called fdomain.
728 tristate "Future Domain MCS-600/700 SCSI support"
729 depends on MCA_LEGACY && SCSI
731 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
732 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
733 is identical to the MCS 700 and hence also supported by this driver.
734 This driver also supports the Reply SB16/SCSI card (the SCSI part).
735 It supports multiple adapters in the same system.
737 To compile this driver as a module, choose M here: the
738 module will be called fd_mcs.
741 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
742 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
744 Formerly called GDT SCSI Disk Array Controller Support.
746 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
747 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
748 in the kernel source in <file:drivers/scsi/gdth.c> and
749 <file:drivers/scsi/gdth.h>.
751 To compile this driver as a module, choose M here: the
752 module will be called gdth.
754 config SCSI_GENERIC_NCR5380
755 tristate "Generic NCR5380/53c400 SCSI PIO support"
756 depends on ISA && SCSI
757 select SCSI_SPI_ATTRS
759 This is a driver for the old NCR 53c80 series of SCSI controllers
760 on boards using PIO. Most boards such as the Trantor T130 fit this
761 category, along with a large number of ISA 8bit controllers shipped
762 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
763 you should select the specific driver for that card rather than
764 generic 5380 support.
766 It is explained in section 3.8 of the SCSI-HOWTO, available from
767 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
768 of the box, you may have to change some settings in
769 <file:drivers/scsi/g_NCR5380.h>.
771 To compile this driver as a module, choose M here: the
772 module will be called g_NCR5380.
774 config SCSI_GENERIC_NCR5380_MMIO
775 tristate "Generic NCR5380/53c400 SCSI MMIO support"
776 depends on ISA && SCSI
777 select SCSI_SPI_ATTRS
779 This is a driver for the old NCR 53c80 series of SCSI controllers
780 on boards using memory mapped I/O.
781 It is explained in section 3.8 of the SCSI-HOWTO, available from
782 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
783 of the box, you may have to change some settings in
784 <file:drivers/scsi/g_NCR5380.h>.
786 To compile this driver as a module, choose M here: the
787 module will be called g_NCR5380_mmio.
789 config SCSI_GENERIC_NCR53C400
790 bool "Enable NCR53c400 extensions"
791 depends on SCSI_GENERIC_NCR5380
793 This enables certain optimizations for the NCR53c400 SCSI cards.
794 You might as well try it out. Note that this driver will only probe
795 for the Trantor T130B in its default configuration; you might have
796 to pass a command line option to the kernel at boot time if it does
797 not detect your card. See the file
798 <file:Documentation/scsi/g_NCR5380.txt> for details.
801 tristate "IBMMCA SCSI support"
802 depends on MCA && SCSI
804 This is support for the IBM SCSI adapter found in many of the PS/2
805 series computers. These machines have an MCA bus, so you need to
806 answer Y to "MCA support" as well and read
807 <file:Documentation/mca.txt>.
809 If the adapter isn't found during boot (a common problem for models
810 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
811 option, where <pun> is the id of the SCSI subsystem (usually 7, but
812 if that doesn't work check your reference diskette). Owners of
813 model 95 with a LED-matrix-display can in addition activate some
814 activity info like under OS/2, but more informative, by setting
815 'ibmmcascsi=display' as an additional kernel parameter. Try "man
816 bootparam" or see the documentation of your boot loader about how to
817 pass options to the kernel.
819 To compile this driver as a module, choose M here: the
820 module will be called ibmmca.
822 config IBMMCA_SCSI_ORDER_STANDARD
823 bool "Standard SCSI-order"
824 depends on SCSI_IBMMCA
826 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
827 are assigned to the drive letters, starting with the lowest SCSI-id
828 (physical number -- pun) to be drive C:, as seen from DOS and
829 similar operating systems. When looking into papers describing the
830 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
831 The SCSI-standard follows a hardware-hierarchy which says that id 7
832 has the highest priority and id 0 the lowest. Therefore, the host
833 adapters are still today everywhere placed as SCSI-id 7 by default.
834 In the SCSI-standard, the drive letters express the priority of the
835 disk. C: should be the hard disk, or a partition on it, with the
836 highest priority. This must therefore be the disk with the highest
837 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
838 original definition of the SCSI-standard as also industrial- and
839 process-control-machines, like VME-CPUs running under realtime-OSes
840 (e.g. LynxOS, OS9) do.
842 If you like to run Linux on your MCA-machine with the same
843 assignment of hard disks as seen from e.g. DOS or OS/2 on your
844 machine, which is in addition conformant to the SCSI-standard, you
845 must say Y here. This is also necessary for MCA-Linux users who want
846 to keep downward compatibility to older releases of the
847 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
850 If you like to have the lowest SCSI-id assigned as drive C:, as
851 modern SCSI-BIOSes do, which does not conform to the standard, but
852 is widespread and common in the PC-world of today, you must say N
853 here. If unsure, say Y.
855 config IBMMCA_SCSI_DEV_RESET
856 bool "Reset SCSI-devices at boottime"
857 depends on SCSI_IBMMCA
859 By default, SCSI-devices are reset when the machine is powered on.
860 However, some devices exist, like special-control-devices,
861 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
862 not reset when switched on. If you say Y here, each device connected
863 to your SCSI-bus will be issued a reset-command after it has been
864 probed, while the kernel is booting. This may cause problems with
865 more modern devices, like hard disks, which do not appreciate these
866 reset commands, and can cause your system to hang. So say Y only if
867 you know that one of your older devices needs it; N is the safe
871 tristate "IBM ServeRAID support"
872 depends on PCI && SCSI
874 This is support for the IBM ServeRAID hardware RAID controllers.
875 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
876 for more information. If this driver does not work correctly
877 without modification please contact the author by email at
878 <ipslinux@adaptec.com>.
880 To compile this driver as a module, choose M here: the
881 module will be called ips.
884 tristate "IBM Virtual SCSI support"
885 depends on PPC_PSERIES || PPC_ISERIES
886 select SCSI_SRP_ATTRS
887 select VIOPATH if PPC_ISERIES
889 This is the IBM POWER Virtual SCSI Client
891 To compile this driver as a module, choose M here: the
892 module will be called ibmvscsic.
894 config SCSI_IBMVSCSIS
895 tristate "IBM Virtual SCSI Server support"
896 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
898 This is the SRP target driver for IBM pSeries virtual environments.
900 The userspace component needed to initialize the driver and
901 documentation can be found:
903 http://stgt.berlios.de/
905 To compile this driver as a module, choose M here: the
906 module will be called ibmvstgt.
909 tristate "IBM Virtual FC support"
910 depends on PPC_PSERIES && SCSI
913 This is the IBM POWER Virtual FC Client
915 To compile this driver as a module, choose M here: the
916 module will be called ibmvfc.
918 config SCSI_IBMVFC_TRACE
919 bool "enable driver internal trace"
920 depends on SCSI_IBMVFC
923 If you say Y here, the driver will trace all commands issued
924 to the adapter. Performance impact is minimal. Trace can be
925 dumped using /sys/class/scsi_host/hostXX/trace.
928 tristate "Initio 9100U(W) support"
929 depends on PCI && SCSI
931 This is support for the Initio 91XXU(W) SCSI host adapter. Please
932 read the SCSI-HOWTO, available from
933 <http://www.tldp.org/docs.html#howto>.
935 To compile this driver as a module, choose M here: the
936 module will be called initio.
939 tristate "Initio INI-A100U2W support"
940 depends on PCI && SCSI
942 This is support for the Initio INI-A100U2W SCSI host adapter.
943 Please read the SCSI-HOWTO, available from
944 <http://www.tldp.org/docs.html#howto>.
946 To compile this driver as a module, choose M here: the
947 module will be called a100u2w.
950 tristate "IOMEGA parallel port (ppa - older drives)"
951 depends on SCSI && PARPORT_PC
953 This driver supports older versions of IOMEGA's parallel port ZIP
954 drive (a 100 MB removable media device).
956 Note that you can say N here if you have the SCSI version of the ZIP
957 drive: it will be supported automatically if you said Y to the
958 generic "SCSI disk support", above.
960 If you have the ZIP Plus drive or a more recent parallel port ZIP
961 drive (if the supplied cable with the drive is labeled "AutoDetect")
962 then you should say N here and Y to "IOMEGA parallel port (imm -
963 newer drives)", below.
965 For more information about this driver and how to use it you should
966 read the file <file:Documentation/scsi/ppa.txt>. You should also read
967 the SCSI-HOWTO, which is available from
968 <http://www.tldp.org/docs.html#howto>. If you use this driver,
969 you will still be able to use the parallel port for other tasks,
970 such as a printer; it is safe to compile both drivers into the
973 To compile this driver as a module, choose M here: the
974 module will be called ppa.
977 tristate "IOMEGA parallel port (imm - newer drives)"
978 depends on SCSI && PARPORT_PC
980 This driver supports newer versions of IOMEGA's parallel port ZIP
981 drive (a 100 MB removable media device).
983 Note that you can say N here if you have the SCSI version of the ZIP
984 drive: it will be supported automatically if you said Y to the
985 generic "SCSI disk support", above.
987 If you have the ZIP Plus drive or a more recent parallel port ZIP
988 drive (if the supplied cable with the drive is labeled "AutoDetect")
989 then you should say Y here; if you have an older ZIP drive, say N
990 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
992 For more information about this driver and how to use it you should
993 read the file <file:Documentation/scsi/ppa.txt>. You should also read
994 the SCSI-HOWTO, which is available from
995 <http://www.tldp.org/docs.html#howto>. If you use this driver,
996 you will still be able to use the parallel port for other tasks,
997 such as a printer; it is safe to compile both drivers into the
1000 To compile this driver as a module, choose M here: the
1001 module will be called imm.
1003 config SCSI_IZIP_EPP16
1004 bool "ppa/imm option - Use slow (but safe) EPP-16"
1005 depends on SCSI_PPA || SCSI_IMM
1007 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1008 allows them to act as expansion buses that can handle up to 64
1011 Some parallel port chipsets are slower than their motherboard, and
1012 so we have to control the state of the chipset's FIFO queue every
1013 now and then to avoid data loss. This will be done if you say Y
1016 Generally, saying Y is the safe option and slows things down a bit.
1018 config SCSI_IZIP_SLOW_CTR
1019 bool "ppa/imm option - Assume slow parport control register"
1020 depends on SCSI_PPA || SCSI_IMM
1022 Some parallel ports are known to have excessive delays between
1023 changing the parallel port control register and good data being
1024 available on the parallel port data/status register. This option
1025 forces a small delay (1.0 usec to be exact) after changing the
1026 control register to let things settle out. Enabling this option may
1027 result in a big drop in performance but some very old parallel ports
1028 (found in 386 vintage machines) will not work properly.
1030 Generally, saying N is fine.
1033 tristate "Marvell 88SE6440 SAS/SATA support"
1034 depends on PCI && SCSI
1035 select SCSI_SAS_LIBSAS
1037 This driver supports Marvell SAS/SATA PCI devices.
1039 To compiler this driver as a module, choose M here: the module
1040 will be called mvsas.
1042 config SCSI_NCR53C406A
1043 tristate "NCR53c406a SCSI support"
1044 depends on ISA && SCSI
1046 This is support for the NCR53c406a SCSI host adapter. For user
1047 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1048 in the kernel source. Also read the SCSI-HOWTO, available from
1049 <http://www.tldp.org/docs.html#howto>.
1051 To compile this driver as a module, choose M here: the
1052 module will be called NCR53c406.
1054 config SCSI_NCR_D700
1055 tristate "NCR Dual 700 MCA SCSI support"
1056 depends on MCA && SCSI
1057 select SCSI_SPI_ATTRS
1059 This is a driver for the MicroChannel Dual 700 card produced by
1060 NCR and commonly used in 345x/35xx/4100 class machines. It always
1061 tries to negotiate sync and uses tag command queueing.
1063 Unless you have an NCR manufactured machine, the chances are that
1064 you do not have this SCSI card, so say N.
1067 tristate "HP Lasi SCSI support for 53c700/710"
1068 depends on GSC && SCSI
1069 select SCSI_SPI_ATTRS
1071 This is a driver for the SCSI controller in the Lasi chip found in
1072 many PA-RISC workstations & servers. If you do not know whether you
1073 have a Lasi chip, it is safe to say "Y" here.
1075 config SCSI_SNI_53C710
1076 tristate "SNI RM SCSI support for 53c710"
1077 depends on SNI_RM && SCSI
1078 select SCSI_SPI_ATTRS
1079 select 53C700_LE_ON_BE
1081 This is a driver for the onboard SCSI controller found in older
1082 SNI RM workstations & servers.
1084 config 53C700_LE_ON_BE
1086 depends on SCSI_LASI700
1090 tristate "Promise SuperTrak EX Series support"
1091 depends on PCI && SCSI
1093 This driver supports Promise SuperTrak EX series storage controllers.
1095 Promise provides Linux RAID configuration utility for these
1096 controllers. Please visit <http://www.promise.com> to download.
1098 To compile this driver as a module, choose M here: the
1099 module will be called stex.
1101 config 53C700_BE_BUS
1103 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1106 config SCSI_SYM53C8XX_2
1107 tristate "SYM53C8XX Version 2 SCSI support"
1108 depends on PCI && SCSI
1109 select SCSI_SPI_ATTRS
1111 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1112 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1113 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1114 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1115 controllers; you need to use the Fusion MPT driver for that.
1117 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1120 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1121 int "DMA addressing mode"
1122 depends on SCSI_SYM53C8XX_2
1125 This option only applies to PCI-SCSI chips that are PCI DAC
1126 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1128 When set to 0, the driver will program the chip to only perform
1129 32-bit DMA. When set to 1, the chip will be able to perform DMA
1130 to addresses up to 1TB. When set to 2, the driver supports the
1131 full 64-bit DMA address range, but can only address 16 segments
1132 of 4 GB each. This limits the total addressable range to 64 GB.
1134 Most machines with less than 4GB of memory should use a setting
1135 of 0 for best performance. If your machine has 4GB of memory
1136 or more, you should set this option to 1 (the default).
1138 The still experimental value 2 (64 bit DMA addressing with 16
1139 x 4GB segments limitation) can be used on systems that require
1140 PCI address bits past bit 39 to be set for the addressing of
1141 memory using PCI DAC cycles.
1143 config SCSI_SYM53C8XX_DEFAULT_TAGS
1144 int "Default tagged command queue depth"
1145 depends on SCSI_SYM53C8XX_2
1148 This is the default value of the command queue depth the
1149 driver will announce to the generic SCSI layer for devices
1150 that support tagged command queueing. This value can be changed
1151 from the boot command line. This is a soft limit that cannot
1152 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1154 config SCSI_SYM53C8XX_MAX_TAGS
1155 int "Maximum number of queued commands"
1156 depends on SCSI_SYM53C8XX_2
1159 This option allows you to specify the maximum number of commands
1160 that can be queued to any device, when tagged command queuing is
1161 possible. The driver supports up to 256 queued commands per device.
1162 This value is used as a compiled-in hard limit.
1164 config SCSI_SYM53C8XX_MMIO
1165 bool "Use memory mapped IO"
1166 depends on SCSI_SYM53C8XX_2
1169 Memory mapped IO is faster than Port IO. Most people should
1170 answer Y here, but some machines may have problems. If you have
1171 to answer N here, please report the problem to the maintainer.
1174 tristate "IBM Power Linux RAID adapter support"
1175 depends on PCI && SCSI && ATA
1178 This driver supports the IBM Power Linux family RAID adapters.
1179 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1180 as IBM iSeries 5702, 5703, 5709, and 570A.
1182 config SCSI_IPR_TRACE
1183 bool "enable driver internal trace"
1187 If you say Y here, the driver will trace all commands issued
1188 to the adapter. Performance impact is minimal. Trace can be
1189 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1191 config SCSI_IPR_DUMP
1192 bool "enable adapter dump support"
1196 If you say Y here, the driver will support adapter crash dump.
1197 If you enable this support, the iprdump daemon can be used
1198 to capture adapter failure analysis information.
1201 tristate "Zalon SCSI support"
1202 depends on GSC && SCSI
1203 select SCSI_SPI_ATTRS
1205 The Zalon is a GSC/HSC bus interface chip that sits between the
1206 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1207 C110, J200, J210 and some D, K & R-class machines. It's also
1208 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1209 Say Y here if you have one of these machines or cards.
1211 config SCSI_NCR_Q720
1212 tristate "NCR Quad 720 MCA SCSI support"
1213 depends on MCA && SCSI
1214 select SCSI_SPI_ATTRS
1216 This is a driver for the MicroChannel Quad 720 card produced by
1217 NCR and commonly used in 345x/35xx/4100 class machines. It always
1218 tries to negotiate sync and uses tag command queueing.
1220 Unless you have an NCR manufactured machine, the chances are that
1221 you do not have this SCSI card, so say N.
1223 config SCSI_NCR53C8XX_DEFAULT_TAGS
1224 int "default tagged command queue depth"
1225 depends on SCSI_ZALON || SCSI_NCR_Q720
1228 "Tagged command queuing" is a feature of SCSI-2 which improves
1229 performance: the host adapter can send several SCSI commands to a
1230 device's queue even if previous commands haven't finished yet.
1231 Because the device is intelligent, it can optimize its operations
1232 (like head positioning) based on its own request queue. Some SCSI
1233 devices don't implement this properly; if you want to disable this
1234 feature, enter 0 or 1 here (it doesn't matter which).
1236 The default value is 8 and should be supported by most hard disks.
1237 This value can be overridden from the boot command line using the
1238 'tags' option as follows (example):
1239 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1240 4, set queue depth to 16 for target 2 and target 3 on controller 0
1241 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1243 The normal answer therefore is to go with the default 8 and to use
1244 a boot command line option for devices that need to use a different
1245 command queue depth.
1247 There is no safe option other than using good SCSI devices.
1249 config SCSI_NCR53C8XX_MAX_TAGS
1250 int "maximum number of queued commands"
1251 depends on SCSI_ZALON || SCSI_NCR_Q720
1254 This option allows you to specify the maximum number of commands
1255 that can be queued to any device, when tagged command queuing is
1256 possible. The default value is 32. Minimum is 2, maximum is 64.
1257 Modern hard disks are able to support 64 tags and even more, but
1258 do not seem to be faster when more than 32 tags are being used.
1260 So, the normal answer here is to go with the default value 32 unless
1261 you are using very large hard disks with large cache (>= 1 MB) that
1262 are able to take advantage of more than 32 tagged commands.
1264 There is no safe option and the default answer is recommended.
1266 config SCSI_NCR53C8XX_SYNC
1267 int "synchronous transfers frequency in MHz"
1268 depends on SCSI_ZALON || SCSI_NCR_Q720
1271 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1272 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1273 are respectively the maximum data transfer rates in mega-transfers
1274 per second for each class. For example, a FAST-20 Wide 16 device is
1275 able to transfer data at 20 million 16 bit packets per second for a
1276 total rate of 40 MB/s.
1278 You may specify 0 if you want to only use asynchronous data
1279 transfers. This is the safest and slowest option. Otherwise, specify
1280 a value between 5 and 80, depending on the capability of your SCSI
1281 controller. The higher the number, the faster the data transfer.
1282 Note that 80 should normally be ok since the driver decreases the
1283 value automatically according to the controller's capabilities.
1285 Your answer to this question is ignored for controllers with NVRAM,
1286 since the driver will get this information from the user set-up. It
1287 also can be overridden using a boot setup option, as follows
1288 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1289 for FAST-20 synchronous data transfer (20 mega-transfers per
1292 The normal answer therefore is not to go with the default but to
1293 select the maximum value 80 allowing the driver to use the maximum
1294 value supported by each controller. If this causes problems with
1295 your SCSI devices, you should come back and decrease the value.
1297 There is no safe option other than using good cabling, right
1298 terminations and SCSI conformant devices.
1300 config SCSI_NCR53C8XX_NO_DISCONNECT
1301 bool "not allow targets to disconnect"
1302 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1304 This option is only provided for safety if you suspect some SCSI
1305 device of yours to not support properly the target-disconnect
1306 feature. In that case, you would say Y here. In general however, to
1307 not allow targets to disconnect is not reasonable if there is more
1308 than 1 device on a SCSI bus. The normal answer therefore is N.
1311 tristate "PAS16 SCSI support"
1312 depends on ISA && SCSI
1313 select SCSI_SPI_ATTRS
1315 This is support for a SCSI host adapter. It is explained in section
1316 3.10 of the SCSI-HOWTO, available from
1317 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1318 of the box, you may have to change some settings in
1319 <file:drivers/scsi/pas16.h>.
1321 To compile this driver as a module, choose M here: the
1322 module will be called pas16.
1324 config SCSI_QLOGIC_FAS
1325 tristate "Qlogic FAS SCSI support"
1326 depends on ISA && SCSI
1328 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1329 FastSCSI! cards as well as any other card based on the FASXX chip
1330 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1332 This driver does NOT support the PCI versions of these cards. The
1333 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1334 SCSI support"), below.
1336 Information about this driver is contained in
1337 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1338 SCSI-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here: the
1342 module will be called qlogicfas.
1344 config SCSI_QLOGIC_1280
1345 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1346 depends on PCI && SCSI
1348 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1350 To compile this driver as a module, choose M here: the
1351 module will be called qla1280.
1353 config SCSI_QLOGICPTI
1354 tristate "PTI Qlogic, ISP Driver"
1355 depends on SBUS && SCSI
1357 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1358 controllers are known under Solaris as qpti and in the openprom as
1359 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1360 driven by a different driver.
1362 To compile this driver as a module, choose M here: the
1363 module will be called qlogicpti.
1365 source "drivers/scsi/qla2xxx/Kconfig"
1366 source "drivers/scsi/qla4xxx/Kconfig"
1369 tristate "Emulex LightPulse Fibre Channel Support"
1370 depends on PCI && SCSI
1371 select SCSI_FC_ATTRS
1373 This lpfc driver supports the Emulex LightPulse
1374 Family of Fibre Channel PCI host adapters.
1376 config SCSI_LPFC_DEBUG_FS
1377 bool "Emulex LightPulse Fibre Channel debugfs Support"
1378 depends on SCSI_LPFC && DEBUG_FS
1380 This makes debugging infomation from the lpfc driver
1381 available via the debugfs filesystem.
1384 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1385 depends on (EISA || MCA) && SCSI
1386 select SCSI_SPI_ATTRS
1388 This driver for NCR53c710 based SCSI host adapters.
1390 It currently supports Compaq EISA cards and NCR MCA cards
1392 config SCSI_SYM53C416
1393 tristate "Symbios 53c416 SCSI support"
1394 depends on ISA && SCSI
1396 This is support for the sym53c416 SCSI host adapter, the SCSI
1397 adapter that comes with some HP scanners. This driver requires that
1398 the sym53c416 is configured first using some sort of PnP
1399 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1400 are using isapnp then you need to compile this driver as a module
1401 and then load it using insmod after isapnp has run. The parameters
1402 of the configured card(s) should be passed to the driver. The format
1405 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1407 To compile this driver as a module, choose M here: the
1408 module will be called sym53c416.
1411 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1412 depends on PCI && SCSI && EXPERIMENTAL
1414 This driver supports PCI SCSI host adapters based on the ASIC
1415 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1417 This driver works, but is still in experimental status. So better
1418 have a bootable disk and a backup in case of emergency.
1420 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1422 To compile this driver as a module, choose M here: the
1423 module will be called dc395x.
1426 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1427 depends on PCI && SCSI
1429 This driver supports PCI SCSI host adapters based on the Am53C974A
1430 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1431 PCscsi/PCnet (Am53/79C974) solutions.
1433 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1435 Note that this driver does NOT support Tekram DC390W/U/F, which are
1436 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1438 To compile this driver as a module, choose M here: the
1439 module will be called tmscsim.
1442 tristate "Trantor T128/T128F/T228 SCSI support"
1443 depends on ISA && SCSI
1444 select SCSI_SPI_ATTRS
1445 select CHECK_SIGNATURE
1447 This is support for a SCSI host adapter. It is explained in section
1448 3.11 of the SCSI-HOWTO, available from
1449 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1450 of the box, you may have to change some settings in
1451 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1452 Adaptec, and some former Trantor products are being sold under the
1455 To compile this driver as a module, choose M here: the
1456 module will be called t128.
1459 tristate "UltraStor 14F/34F support"
1460 depends on ISA && SCSI && ISA_DMA_API
1462 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1463 The source at <file:drivers/scsi/u14-34f.c> contains some
1464 information about this hardware. If the driver doesn't work out of
1465 the box, you may have to change some settings in
1466 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1467 <http://www.tldp.org/docs.html#howto>. Note that there is also
1468 another driver for the same hardware: "UltraStor SCSI support",
1469 below. You should say Y to both only if you want 24F support as
1472 To compile this driver as a module, choose M here: the
1473 module will be called u14-34f.
1475 config SCSI_U14_34F_TAGGED_QUEUE
1476 bool "enable tagged command queueing"
1477 depends on SCSI_U14_34F
1479 This is a feature of SCSI-2 which improves performance: the host
1480 adapter can send several SCSI commands to a device's queue even if
1481 previous commands haven't finished yet.
1482 This is equivalent to the "u14-34f=tc:y" boot option.
1484 config SCSI_U14_34F_LINKED_COMMANDS
1485 bool "enable elevator sorting"
1486 depends on SCSI_U14_34F
1488 This option enables elevator sorting for all probed SCSI disks and
1489 CD-ROMs. It definitely reduces the average seek distance when doing
1490 random seeks, but this does not necessarily result in a noticeable
1491 performance improvement: your mileage may vary...
1492 This is equivalent to the "u14-34f=lc:y" boot option.
1494 config SCSI_U14_34F_MAX_TAGS
1495 int "maximum number of queued commands"
1496 depends on SCSI_U14_34F
1499 This specifies how many SCSI commands can be maximally queued for
1500 each probed SCSI device. You should reduce the default value of 8
1501 only if you have disks with buggy or limited tagged command support.
1502 Minimum is 2 and maximum is 14. This value is also the window size
1503 used by the elevator sorting option above. The effective value used
1504 by the driver for each probed SCSI device is reported at boot time.
1505 This is equivalent to the "u14-34f=mq:8" boot option.
1507 config SCSI_ULTRASTOR
1508 tristate "UltraStor SCSI support"
1509 depends on X86 && ISA && SCSI
1511 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1512 adapter family. This driver is explained in section 3.12 of the
1513 SCSI-HOWTO, available from
1514 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1515 of the box, you may have to change some settings in
1516 <file:drivers/scsi/ultrastor.h>.
1518 Note that there is also another driver for the same hardware:
1519 "UltraStor 14F/34F support", above.
1521 To compile this driver as a module, choose M here: the
1522 module will be called ultrastor.
1525 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1526 depends on PCI && SCSI && !64BIT
1528 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1529 SCSI host adapter. Please read the SCSI-HOWTO, available from
1530 <http://www.tldp.org/docs.html#howto>.
1532 To compile this driver as a module, choose M here: the
1533 module will be called nsp32.
1536 tristate "SCSI debugging host simulator"
1539 This is a host adapter simulator that can simulate multiple hosts
1540 each with multiple dummy SCSI devices (disks). It defaults to one
1541 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1542 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1543 dummy disks are simulated, they share the same kernel RAM for
1544 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1545 information. This driver is primarily of use to those testing the
1546 SCSI and block subsystems. If unsure, say N.
1549 tristate "MESH (Power Mac internal SCSI) support"
1550 depends on PPC32 && PPC_PMAC && SCSI
1552 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1553 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1554 other Power Macintoshes do). Say Y to include support for this SCSI
1557 To compile this driver as a module, choose M here: the
1558 module will be called mesh.
1560 config SCSI_MESH_SYNC_RATE
1561 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1562 depends on SCSI_MESH
1565 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1566 drives a bus which is entirely internal to the machine (such as the
1567 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1568 operation at up to 10 MB/s. On machines where the SCSI bus
1569 controlled by the MESH can have external devices connected, it is
1570 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1571 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1572 to disable synchronous operation.
1574 config SCSI_MESH_RESET_DELAY_MS
1575 int "initial bus reset delay (ms) (0 = no reset)"
1576 depends on SCSI_MESH
1579 config SCSI_MAC53C94
1580 tristate "53C94 (Power Mac external SCSI) support"
1581 depends on PPC32 && PPC_PMAC && SCSI
1583 On Power Macintoshes (and clones) with two SCSI buses, the external
1584 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1585 machines which only have one SCSI bus, such as the 7200, also use
1586 the 53C94. Say Y to include support for the 53C94.
1588 To compile this driver as a module, choose M here: the
1589 module will be called mac53c94.
1591 source "drivers/scsi/arm/Kconfig"
1594 bool "MIPS JAZZ FAS216 SCSI support"
1595 depends on MACH_JAZZ && SCSI
1596 select SCSI_SPI_ATTRS
1598 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1599 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1603 tristate "A3000 WD33C93A support"
1604 depends on AMIGA && SCSI
1606 If you have an Amiga 3000 and have SCSI devices connected to the
1607 built-in SCSI controller, say Y. Otherwise, say N.
1609 To compile this driver as a module, choose M here: the
1610 module will be called a3000.
1613 tristate "A2091/A590 WD33C93A support"
1614 depends on ZORRO && SCSI
1616 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1619 To compile this driver as a module, choose M here: the
1620 module will be called a2091.
1623 tristate "GVP Series II WD33C93A support"
1624 depends on ZORRO && SCSI
1626 If you have a Great Valley Products Series II SCSI controller,
1627 answer Y. Also say Y if you have a later model of GVP SCSI
1628 controller (such as the GVP A4008 or a Combo board). Otherwise,
1629 answer N. This driver does NOT work for the T-Rex series of
1630 accelerators from TekMagic and GVP-M.
1632 To compile this driver as a module, choose M here: the
1633 module will be called gvp11.
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 "Atari native SCSI support"
1664 depends on ATARI && SCSI
1665 select SCSI_SPI_ATTRS
1668 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1669 Falcon, ...) say Y to get it supported. Of course also, if you have
1670 a compatible SCSI controller (e.g. for Medusa).
1672 To compile this driver as a module, choose M here: the
1673 module will be called atari_scsi.
1675 This driver supports both styles of NCR integration into the
1676 system: the TT style (separate DMA), and the Falcon style (via
1677 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1678 in the Hades (without DMA).
1680 config ATARI_SCSI_TOSHIBA_DELAY
1681 bool "Long delays for Toshiba CD-ROMs"
1682 depends on ATARI_SCSI
1684 This option increases the delay after a SCSI arbitration to
1685 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1686 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1687 would impact performance a bit, so say N.
1689 config ATARI_SCSI_RESET_BOOT
1690 bool "Reset SCSI-devices at boottime"
1691 depends on ATARI_SCSI
1693 Reset the devices on your Atari whenever it boots. This makes the
1694 boot process fractionally longer but may assist recovery from errors
1695 that leave the devices with SCSI operations partway completed.
1698 bool "Macintosh NCR5380 SCSI"
1699 depends on MAC && SCSI=y
1700 select SCSI_SPI_ATTRS
1702 This is the NCR 5380 SCSI controller included on most of the 68030
1703 based Macintoshes. If you have one of these say Y and read the
1704 SCSI-HOWTO, available from
1705 <http://www.tldp.org/docs.html#howto>.
1708 tristate "Macintosh NCR53c9[46] SCSI"
1709 depends on MAC && SCSI
1710 select SCSI_SPI_ATTRS
1712 This is the NCR 53c9x SCSI controller found on most of the 68040
1715 To compile this driver as a module, choose M here: the module
1716 will be called mac_esp.
1719 bool "WD33C93 SCSI driver for MVME147"
1720 depends on MVME147 && SCSI=y
1721 select SCSI_SPI_ATTRS
1723 Support for the on-board SCSI controller on the Motorola MVME147
1724 single-board computer.
1727 tristate "NCR53C710 SCSI driver for MVME16x"
1728 depends on MVME16x && SCSI
1729 select SCSI_SPI_ATTRS
1731 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1732 SCSI controller chip. Almost everyone using one of these boards
1733 will want to say Y to this question.
1735 config BVME6000_SCSI
1736 tristate "NCR53C710 SCSI driver for BVME6000"
1737 depends on BVME6000 && SCSI
1738 select SCSI_SPI_ATTRS
1740 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1741 SCSI controller chip. Almost everyone using one of these boards
1742 will want to say Y to this question.
1745 tristate "Sun3 NCR5380 SCSI"
1746 depends on SUN3 && SCSI
1747 select SCSI_SPI_ATTRS
1749 This option will enable support for the OBIO (onboard io) NCR5380
1750 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1751 "Sun3" type VME scsi controllers also based on the NCR5380.
1752 General Linux information on the Sun 3 series (now discontinued)
1753 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1756 bool "Sun3x ESP SCSI"
1757 depends on SUN3X && SCSI=y
1758 select SCSI_SPI_ATTRS
1760 The ESP was an on-board SCSI controller used on Sun 3/80
1761 machines. Say Y here to compile in support for it.
1764 tristate "Sparc ESP Scsi Driver"
1765 depends on SBUS && SCSI
1766 select SCSI_SPI_ATTRS
1768 This is the driver for the Sun ESP SCSI host adapter. The ESP
1769 chipset is present in most SPARC SBUS-based computers and
1770 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1771 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1773 To compile this driver as a module, choose M here: the
1774 module will be called sun_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.
1800 endif # SCSI_LOWLEVEL
1802 source "drivers/scsi/pcmcia/Kconfig"
1804 source "drivers/scsi/device_handler/Kconfig"
projects / linux-2.6 / blob