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"
613 Fibre Channel library module
616 tristate "FCoE module"
620 Fibre Channel over Ethernet module
623 tristate "DMX3191D SCSI support"
624 depends on PCI && SCSI
625 select SCSI_SPI_ATTRS
627 This is support for Domex DMX3191D SCSI Host Adapters.
629 To compile this driver as a module, choose M here: the
630 module will be called dmx3191d.
633 tristate "DTC3180/3280 SCSI support"
634 depends on ISA && SCSI
635 select SCSI_SPI_ATTRS
636 select CHECK_SIGNATURE
638 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
639 the SCSI-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>, and the file
641 <file:Documentation/scsi/dtc3x80.txt>.
643 To compile this driver as a module, choose M here: the
644 module will be called dtc.
647 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
648 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
650 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
651 ISA and all EISA I/O addresses are probed looking for the "EATA"
652 signature. The addresses of all the PCI SCSI controllers reported
653 by the PCI subsystem are probed as well.
655 You want to read the start of <file:drivers/scsi/eata.c> and the
656 SCSI-HOWTO, available from
657 <http://www.tldp.org/docs.html#howto>.
659 To compile this driver as a module, choose M here: the
660 module will be called eata.
662 config SCSI_EATA_TAGGED_QUEUE
663 bool "enable tagged command queueing"
666 This is a feature of SCSI-2 which improves performance: the host
667 adapter can send several SCSI commands to a device's queue even if
668 previous commands haven't finished yet.
669 This is equivalent to the "eata=tc:y" boot option.
671 config SCSI_EATA_LINKED_COMMANDS
672 bool "enable elevator sorting"
675 This option enables elevator sorting for all probed SCSI disks and
676 CD-ROMs. It definitely reduces the average seek distance when doing
677 random seeks, but this does not necessarily result in a noticeable
678 performance improvement: your mileage may vary...
679 This is equivalent to the "eata=lc:y" boot option.
681 config SCSI_EATA_MAX_TAGS
682 int "maximum number of queued commands"
686 This specifies how many SCSI commands can be maximally queued for
687 each probed SCSI device. You should reduce the default value of 16
688 only if you have disks with buggy or limited tagged command support.
689 Minimum is 2 and maximum is 62. This value is also the window size
690 used by the elevator sorting option above. The effective value used
691 by the driver for each probed SCSI device is reported at boot time.
692 This is equivalent to the "eata=mq:8" boot option.
695 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
696 depends on (ISA || EISA || PCI) && SCSI && BROKEN
698 This driver supports all EATA-PIO protocol compliant SCSI Host
699 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
700 host adapters could also use this driver but are discouraged from
701 doing so, since this driver only supports hard disks and lacks
702 numerous features. You might want to have a look at the SCSI-HOWTO,
703 available from <http://www.tldp.org/docs.html#howto>.
705 To compile this driver as a module, choose M here: the
706 module will be called eata_pio.
708 config SCSI_FUTURE_DOMAIN
709 tristate "Future Domain 16xx SCSI/AHA-2920A support"
710 depends on (ISA || PCI) && SCSI
711 select CHECK_SIGNATURE
713 This is support for Future Domain's 16-bit SCSI host adapters
714 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
715 other adapters based on the Future Domain chipsets (Quantum
716 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
717 It is explained in section 3.7 of the SCSI-HOWTO, available from
718 <http://www.tldp.org/docs.html#howto>.
720 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
721 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
722 controller support"). This Future Domain driver works with the older
723 Adaptec AHA-2920A boards with a Future Domain chip on them.
725 To compile this driver as a module, choose M here: the
726 module will be called fdomain.
729 tristate "Future Domain MCS-600/700 SCSI support"
730 depends on MCA_LEGACY && SCSI
732 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
733 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
734 is identical to the MCS 700 and hence also supported by this driver.
735 This driver also supports the Reply SB16/SCSI card (the SCSI part).
736 It supports multiple adapters in the same system.
738 To compile this driver as a module, choose M here: the
739 module will be called fd_mcs.
742 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
743 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
745 Formerly called GDT SCSI Disk Array Controller Support.
747 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
748 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
749 in the kernel source in <file:drivers/scsi/gdth.c> and
750 <file:drivers/scsi/gdth.h>.
752 To compile this driver as a module, choose M here: the
753 module will be called gdth.
755 config SCSI_GENERIC_NCR5380
756 tristate "Generic NCR5380/53c400 SCSI PIO support"
757 depends on ISA && SCSI
758 select SCSI_SPI_ATTRS
760 This is a driver for the old NCR 53c80 series of SCSI controllers
761 on boards using PIO. Most boards such as the Trantor T130 fit this
762 category, along with a large number of ISA 8bit controllers shipped
763 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
764 you should select the specific driver for that card rather than
765 generic 5380 support.
767 It is explained in section 3.8 of the SCSI-HOWTO, available from
768 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
769 of the box, you may have to change some settings in
770 <file:drivers/scsi/g_NCR5380.h>.
772 To compile this driver as a module, choose M here: the
773 module will be called g_NCR5380.
775 config SCSI_GENERIC_NCR5380_MMIO
776 tristate "Generic NCR5380/53c400 SCSI MMIO support"
777 depends on ISA && SCSI
778 select SCSI_SPI_ATTRS
780 This is a driver for the old NCR 53c80 series of SCSI controllers
781 on boards using memory mapped I/O.
782 It is explained in section 3.8 of the SCSI-HOWTO, available from
783 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
784 of the box, you may have to change some settings in
785 <file:drivers/scsi/g_NCR5380.h>.
787 To compile this driver as a module, choose M here: the
788 module will be called g_NCR5380_mmio.
790 config SCSI_GENERIC_NCR53C400
791 bool "Enable NCR53c400 extensions"
792 depends on SCSI_GENERIC_NCR5380
794 This enables certain optimizations for the NCR53c400 SCSI cards.
795 You might as well try it out. Note that this driver will only probe
796 for the Trantor T130B in its default configuration; you might have
797 to pass a command line option to the kernel at boot time if it does
798 not detect your card. See the file
799 <file:Documentation/scsi/g_NCR5380.txt> for details.
802 tristate "IBMMCA SCSI support"
803 depends on MCA && SCSI
805 This is support for the IBM SCSI adapter found in many of the PS/2
806 series computers. These machines have an MCA bus, so you need to
807 answer Y to "MCA support" as well and read
808 <file:Documentation/mca.txt>.
810 If the adapter isn't found during boot (a common problem for models
811 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
812 option, where <pun> is the id of the SCSI subsystem (usually 7, but
813 if that doesn't work check your reference diskette). Owners of
814 model 95 with a LED-matrix-display can in addition activate some
815 activity info like under OS/2, but more informative, by setting
816 'ibmmcascsi=display' as an additional kernel parameter. Try "man
817 bootparam" or see the documentation of your boot loader about how to
818 pass options to the kernel.
820 To compile this driver as a module, choose M here: the
821 module will be called ibmmca.
823 config IBMMCA_SCSI_ORDER_STANDARD
824 bool "Standard SCSI-order"
825 depends on SCSI_IBMMCA
827 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
828 are assigned to the drive letters, starting with the lowest SCSI-id
829 (physical number -- pun) to be drive C:, as seen from DOS and
830 similar operating systems. When looking into papers describing the
831 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
832 The SCSI-standard follows a hardware-hierarchy which says that id 7
833 has the highest priority and id 0 the lowest. Therefore, the host
834 adapters are still today everywhere placed as SCSI-id 7 by default.
835 In the SCSI-standard, the drive letters express the priority of the
836 disk. C: should be the hard disk, or a partition on it, with the
837 highest priority. This must therefore be the disk with the highest
838 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
839 original definition of the SCSI-standard as also industrial- and
840 process-control-machines, like VME-CPUs running under realtime-OSes
841 (e.g. LynxOS, OS9) do.
843 If you like to run Linux on your MCA-machine with the same
844 assignment of hard disks as seen from e.g. DOS or OS/2 on your
845 machine, which is in addition conformant to the SCSI-standard, you
846 must say Y here. This is also necessary for MCA-Linux users who want
847 to keep downward compatibility to older releases of the
848 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
851 If you like to have the lowest SCSI-id assigned as drive C:, as
852 modern SCSI-BIOSes do, which does not conform to the standard, but
853 is widespread and common in the PC-world of today, you must say N
854 here. If unsure, say Y.
856 config IBMMCA_SCSI_DEV_RESET
857 bool "Reset SCSI-devices at boottime"
858 depends on SCSI_IBMMCA
860 By default, SCSI-devices are reset when the machine is powered on.
861 However, some devices exist, like special-control-devices,
862 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
863 not reset when switched on. If you say Y here, each device connected
864 to your SCSI-bus will be issued a reset-command after it has been
865 probed, while the kernel is booting. This may cause problems with
866 more modern devices, like hard disks, which do not appreciate these
867 reset commands, and can cause your system to hang. So say Y only if
868 you know that one of your older devices needs it; N is the safe
872 tristate "IBM ServeRAID support"
873 depends on PCI && SCSI
875 This is support for the IBM ServeRAID hardware RAID controllers.
876 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
877 for more information. If this driver does not work correctly
878 without modification please contact the author by email at
879 <ipslinux@adaptec.com>.
881 To compile this driver as a module, choose M here: the
882 module will be called ips.
885 tristate "IBM Virtual SCSI support"
886 depends on PPC_PSERIES || PPC_ISERIES
887 select SCSI_SRP_ATTRS
888 select VIOPATH if PPC_ISERIES
890 This is the IBM POWER Virtual SCSI Client
892 To compile this driver as a module, choose M here: the
893 module will be called ibmvscsic.
895 config SCSI_IBMVSCSIS
896 tristate "IBM Virtual SCSI Server support"
897 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
899 This is the SRP target driver for IBM pSeries virtual environments.
901 The userspace component needed to initialize the driver and
902 documentation can be found:
904 http://stgt.berlios.de/
906 To compile this driver as a module, choose M here: the
907 module will be called ibmvstgt.
910 tristate "IBM Virtual FC support"
911 depends on PPC_PSERIES && SCSI
914 This is the IBM POWER Virtual FC Client
916 To compile this driver as a module, choose M here: the
917 module will be called ibmvfc.
919 config SCSI_IBMVFC_TRACE
920 bool "enable driver internal trace"
921 depends on SCSI_IBMVFC
924 If you say Y here, the driver will trace all commands issued
925 to the adapter. Performance impact is minimal. Trace can be
926 dumped using /sys/class/scsi_host/hostXX/trace.
929 tristate "Initio 9100U(W) support"
930 depends on PCI && SCSI
932 This is support for the Initio 91XXU(W) SCSI host adapter. Please
933 read the SCSI-HOWTO, available from
934 <http://www.tldp.org/docs.html#howto>.
936 To compile this driver as a module, choose M here: the
937 module will be called initio.
940 tristate "Initio INI-A100U2W support"
941 depends on PCI && SCSI
943 This is support for the Initio INI-A100U2W SCSI host adapter.
944 Please read the SCSI-HOWTO, available from
945 <http://www.tldp.org/docs.html#howto>.
947 To compile this driver as a module, choose M here: the
948 module will be called a100u2w.
951 tristate "IOMEGA parallel port (ppa - older drives)"
952 depends on SCSI && PARPORT_PC
954 This driver supports older versions of IOMEGA's parallel port ZIP
955 drive (a 100 MB removable media device).
957 Note that you can say N here if you have the SCSI version of the ZIP
958 drive: it will be supported automatically if you said Y to the
959 generic "SCSI disk support", above.
961 If you have the ZIP Plus drive or a more recent parallel port ZIP
962 drive (if the supplied cable with the drive is labeled "AutoDetect")
963 then you should say N here and Y to "IOMEGA parallel port (imm -
964 newer drives)", below.
966 For more information about this driver and how to use it you should
967 read the file <file:Documentation/scsi/ppa.txt>. You should also read
968 the SCSI-HOWTO, which is available from
969 <http://www.tldp.org/docs.html#howto>. If you use this driver,
970 you will still be able to use the parallel port for other tasks,
971 such as a printer; it is safe to compile both drivers into the
974 To compile this driver as a module, choose M here: the
975 module will be called ppa.
978 tristate "IOMEGA parallel port (imm - newer drives)"
979 depends on SCSI && PARPORT_PC
981 This driver supports newer versions of IOMEGA's parallel port ZIP
982 drive (a 100 MB removable media device).
984 Note that you can say N here if you have the SCSI version of the ZIP
985 drive: it will be supported automatically if you said Y to the
986 generic "SCSI disk support", above.
988 If you have the ZIP Plus drive or a more recent parallel port ZIP
989 drive (if the supplied cable with the drive is labeled "AutoDetect")
990 then you should say Y here; if you have an older ZIP drive, say N
991 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
993 For more information about this driver and how to use it you should
994 read the file <file:Documentation/scsi/ppa.txt>. You should also read
995 the SCSI-HOWTO, which is available from
996 <http://www.tldp.org/docs.html#howto>. If you use this driver,
997 you will still be able to use the parallel port for other tasks,
998 such as a printer; it is safe to compile both drivers into the
1001 To compile this driver as a module, choose M here: the
1002 module will be called imm.
1004 config SCSI_IZIP_EPP16
1005 bool "ppa/imm option - Use slow (but safe) EPP-16"
1006 depends on SCSI_PPA || SCSI_IMM
1008 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1009 allows them to act as expansion buses that can handle up to 64
1012 Some parallel port chipsets are slower than their motherboard, and
1013 so we have to control the state of the chipset's FIFO queue every
1014 now and then to avoid data loss. This will be done if you say Y
1017 Generally, saying Y is the safe option and slows things down a bit.
1019 config SCSI_IZIP_SLOW_CTR
1020 bool "ppa/imm option - Assume slow parport control register"
1021 depends on SCSI_PPA || SCSI_IMM
1023 Some parallel ports are known to have excessive delays between
1024 changing the parallel port control register and good data being
1025 available on the parallel port data/status register. This option
1026 forces a small delay (1.0 usec to be exact) after changing the
1027 control register to let things settle out. Enabling this option may
1028 result in a big drop in performance but some very old parallel ports
1029 (found in 386 vintage machines) will not work properly.
1031 Generally, saying N is fine.
1034 tristate "Marvell 88SE6440 SAS/SATA support"
1035 depends on PCI && SCSI
1036 select SCSI_SAS_LIBSAS
1038 This driver supports Marvell SAS/SATA PCI devices.
1040 To compiler this driver as a module, choose M here: the module
1041 will be called mvsas.
1043 config SCSI_NCR53C406A
1044 tristate "NCR53c406a SCSI support"
1045 depends on ISA && SCSI
1047 This is support for the NCR53c406a SCSI host adapter. For user
1048 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1049 in the kernel source. Also read the SCSI-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto>.
1052 To compile this driver as a module, choose M here: the
1053 module will be called NCR53c406.
1055 config SCSI_NCR_D700
1056 tristate "NCR Dual 700 MCA SCSI support"
1057 depends on MCA && SCSI
1058 select SCSI_SPI_ATTRS
1060 This is a driver for the MicroChannel Dual 700 card produced by
1061 NCR and commonly used in 345x/35xx/4100 class machines. It always
1062 tries to negotiate sync and uses tag command queueing.
1064 Unless you have an NCR manufactured machine, the chances are that
1065 you do not have this SCSI card, so say N.
1068 tristate "HP Lasi SCSI support for 53c700/710"
1069 depends on GSC && SCSI
1070 select SCSI_SPI_ATTRS
1072 This is a driver for the SCSI controller in the Lasi chip found in
1073 many PA-RISC workstations & servers. If you do not know whether you
1074 have a Lasi chip, it is safe to say "Y" here.
1076 config SCSI_SNI_53C710
1077 tristate "SNI RM SCSI support for 53c710"
1078 depends on SNI_RM && SCSI
1079 select SCSI_SPI_ATTRS
1080 select 53C700_LE_ON_BE
1082 This is a driver for the onboard SCSI controller found in older
1083 SNI RM workstations & servers.
1085 config 53C700_LE_ON_BE
1087 depends on SCSI_LASI700
1091 tristate "Promise SuperTrak EX Series support"
1092 depends on PCI && SCSI
1094 This driver supports Promise SuperTrak EX series storage controllers.
1096 Promise provides Linux RAID configuration utility for these
1097 controllers. Please visit <http://www.promise.com> to download.
1099 To compile this driver as a module, choose M here: the
1100 module will be called stex.
1102 config 53C700_BE_BUS
1104 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1107 config SCSI_SYM53C8XX_2
1108 tristate "SYM53C8XX Version 2 SCSI support"
1109 depends on PCI && SCSI
1110 select SCSI_SPI_ATTRS
1112 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1113 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1114 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1115 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1116 controllers; you need to use the Fusion MPT driver for that.
1118 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1121 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1122 int "DMA addressing mode"
1123 depends on SCSI_SYM53C8XX_2
1126 This option only applies to PCI-SCSI chips that are PCI DAC
1127 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1129 When set to 0, the driver will program the chip to only perform
1130 32-bit DMA. When set to 1, the chip will be able to perform DMA
1131 to addresses up to 1TB. When set to 2, the driver supports the
1132 full 64-bit DMA address range, but can only address 16 segments
1133 of 4 GB each. This limits the total addressable range to 64 GB.
1135 Most machines with less than 4GB of memory should use a setting
1136 of 0 for best performance. If your machine has 4GB of memory
1137 or more, you should set this option to 1 (the default).
1139 The still experimental value 2 (64 bit DMA addressing with 16
1140 x 4GB segments limitation) can be used on systems that require
1141 PCI address bits past bit 39 to be set for the addressing of
1142 memory using PCI DAC cycles.
1144 config SCSI_SYM53C8XX_DEFAULT_TAGS
1145 int "Default tagged command queue depth"
1146 depends on SCSI_SYM53C8XX_2
1149 This is the default value of the command queue depth the
1150 driver will announce to the generic SCSI layer for devices
1151 that support tagged command queueing. This value can be changed
1152 from the boot command line. This is a soft limit that cannot
1153 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1155 config SCSI_SYM53C8XX_MAX_TAGS
1156 int "Maximum number of queued commands"
1157 depends on SCSI_SYM53C8XX_2
1160 This option allows you to specify the maximum number of commands
1161 that can be queued to any device, when tagged command queuing is
1162 possible. The driver supports up to 256 queued commands per device.
1163 This value is used as a compiled-in hard limit.
1165 config SCSI_SYM53C8XX_MMIO
1166 bool "Use memory mapped IO"
1167 depends on SCSI_SYM53C8XX_2
1170 Memory mapped IO is faster than Port IO. Most people should
1171 answer Y here, but some machines may have problems. If you have
1172 to answer N here, please report the problem to the maintainer.
1175 tristate "IBM Power Linux RAID adapter support"
1176 depends on PCI && SCSI && ATA
1179 This driver supports the IBM Power Linux family RAID adapters.
1180 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1181 as IBM iSeries 5702, 5703, 5709, and 570A.
1183 config SCSI_IPR_TRACE
1184 bool "enable driver internal trace"
1188 If you say Y here, the driver will trace all commands issued
1189 to the adapter. Performance impact is minimal. Trace can be
1190 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1192 config SCSI_IPR_DUMP
1193 bool "enable adapter dump support"
1197 If you say Y here, the driver will support adapter crash dump.
1198 If you enable this support, the iprdump daemon can be used
1199 to capture adapter failure analysis information.
1202 tristate "Zalon SCSI support"
1203 depends on GSC && SCSI
1204 select SCSI_SPI_ATTRS
1206 The Zalon is a GSC/HSC bus interface chip that sits between the
1207 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1208 C110, J200, J210 and some D, K & R-class machines. It's also
1209 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1210 Say Y here if you have one of these machines or cards.
1212 config SCSI_NCR_Q720
1213 tristate "NCR Quad 720 MCA SCSI support"
1214 depends on MCA && SCSI
1215 select SCSI_SPI_ATTRS
1217 This is a driver for the MicroChannel Quad 720 card produced by
1218 NCR and commonly used in 345x/35xx/4100 class machines. It always
1219 tries to negotiate sync and uses tag command queueing.
1221 Unless you have an NCR manufactured machine, the chances are that
1222 you do not have this SCSI card, so say N.
1224 config SCSI_NCR53C8XX_DEFAULT_TAGS
1225 int "default tagged command queue depth"
1226 depends on SCSI_ZALON || SCSI_NCR_Q720
1229 "Tagged command queuing" is a feature of SCSI-2 which improves
1230 performance: the host adapter can send several SCSI commands to a
1231 device's queue even if previous commands haven't finished yet.
1232 Because the device is intelligent, it can optimize its operations
1233 (like head positioning) based on its own request queue. Some SCSI
1234 devices don't implement this properly; if you want to disable this
1235 feature, enter 0 or 1 here (it doesn't matter which).
1237 The default value is 8 and should be supported by most hard disks.
1238 This value can be overridden from the boot command line using the
1239 'tags' option as follows (example):
1240 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1241 4, set queue depth to 16 for target 2 and target 3 on controller 0
1242 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1244 The normal answer therefore is to go with the default 8 and to use
1245 a boot command line option for devices that need to use a different
1246 command queue depth.
1248 There is no safe option other than using good SCSI devices.
1250 config SCSI_NCR53C8XX_MAX_TAGS
1251 int "maximum number of queued commands"
1252 depends on SCSI_ZALON || SCSI_NCR_Q720
1255 This option allows you to specify the maximum number of commands
1256 that can be queued to any device, when tagged command queuing is
1257 possible. The default value is 32. Minimum is 2, maximum is 64.
1258 Modern hard disks are able to support 64 tags and even more, but
1259 do not seem to be faster when more than 32 tags are being used.
1261 So, the normal answer here is to go with the default value 32 unless
1262 you are using very large hard disks with large cache (>= 1 MB) that
1263 are able to take advantage of more than 32 tagged commands.
1265 There is no safe option and the default answer is recommended.
1267 config SCSI_NCR53C8XX_SYNC
1268 int "synchronous transfers frequency in MHz"
1269 depends on SCSI_ZALON || SCSI_NCR_Q720
1272 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1273 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1274 are respectively the maximum data transfer rates in mega-transfers
1275 per second for each class. For example, a FAST-20 Wide 16 device is
1276 able to transfer data at 20 million 16 bit packets per second for a
1277 total rate of 40 MB/s.
1279 You may specify 0 if you want to only use asynchronous data
1280 transfers. This is the safest and slowest option. Otherwise, specify
1281 a value between 5 and 80, depending on the capability of your SCSI
1282 controller. The higher the number, the faster the data transfer.
1283 Note that 80 should normally be ok since the driver decreases the
1284 value automatically according to the controller's capabilities.
1286 Your answer to this question is ignored for controllers with NVRAM,
1287 since the driver will get this information from the user set-up. It
1288 also can be overridden using a boot setup option, as follows
1289 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1290 for FAST-20 synchronous data transfer (20 mega-transfers per
1293 The normal answer therefore is not to go with the default but to
1294 select the maximum value 80 allowing the driver to use the maximum
1295 value supported by each controller. If this causes problems with
1296 your SCSI devices, you should come back and decrease the value.
1298 There is no safe option other than using good cabling, right
1299 terminations and SCSI conformant devices.
1301 config SCSI_NCR53C8XX_NO_DISCONNECT
1302 bool "not allow targets to disconnect"
1303 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1305 This option is only provided for safety if you suspect some SCSI
1306 device of yours to not support properly the target-disconnect
1307 feature. In that case, you would say Y here. In general however, to
1308 not allow targets to disconnect is not reasonable if there is more
1309 than 1 device on a SCSI bus. The normal answer therefore is N.
1312 tristate "PAS16 SCSI support"
1313 depends on ISA && SCSI
1314 select SCSI_SPI_ATTRS
1316 This is support for a SCSI host adapter. It is explained in section
1317 3.10 of the SCSI-HOWTO, available from
1318 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1319 of the box, you may have to change some settings in
1320 <file:drivers/scsi/pas16.h>.
1322 To compile this driver as a module, choose M here: the
1323 module will be called pas16.
1325 config SCSI_QLOGIC_FAS
1326 tristate "Qlogic FAS SCSI support"
1327 depends on ISA && SCSI
1329 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1330 FastSCSI! cards as well as any other card based on the FASXX chip
1331 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1333 This driver does NOT support the PCI versions of these cards. The
1334 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1335 SCSI support"), below.
1337 Information about this driver is contained in
1338 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1339 SCSI-HOWTO, available from
1340 <http://www.tldp.org/docs.html#howto>.
1342 To compile this driver as a module, choose M here: the
1343 module will be called qlogicfas.
1345 config SCSI_QLOGIC_1280
1346 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1347 depends on PCI && SCSI
1349 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1351 To compile this driver as a module, choose M here: the
1352 module will be called qla1280.
1354 config SCSI_QLOGICPTI
1355 tristate "PTI Qlogic, ISP Driver"
1356 depends on SBUS && SCSI
1358 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1359 controllers are known under Solaris as qpti and in the openprom as
1360 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1361 driven by a different driver.
1363 To compile this driver as a module, choose M here: the
1364 module will be called qlogicpti.
1366 source "drivers/scsi/qla2xxx/Kconfig"
1367 source "drivers/scsi/qla4xxx/Kconfig"
1370 tristate "Emulex LightPulse Fibre Channel Support"
1371 depends on PCI && SCSI
1372 select SCSI_FC_ATTRS
1374 This lpfc driver supports the Emulex LightPulse
1375 Family of Fibre Channel PCI host adapters.
1377 config SCSI_LPFC_DEBUG_FS
1378 bool "Emulex LightPulse Fibre Channel debugfs Support"
1379 depends on SCSI_LPFC && DEBUG_FS
1381 This makes debugging infomation from the lpfc driver
1382 available via the debugfs filesystem.
1385 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1386 depends on (EISA || MCA) && SCSI
1387 select SCSI_SPI_ATTRS
1389 This driver for NCR53c710 based SCSI host adapters.
1391 It currently supports Compaq EISA cards and NCR MCA cards
1393 config SCSI_SYM53C416
1394 tristate "Symbios 53c416 SCSI support"
1395 depends on ISA && SCSI
1397 This is support for the sym53c416 SCSI host adapter, the SCSI
1398 adapter that comes with some HP scanners. This driver requires that
1399 the sym53c416 is configured first using some sort of PnP
1400 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1401 are using isapnp then you need to compile this driver as a module
1402 and then load it using insmod after isapnp has run. The parameters
1403 of the configured card(s) should be passed to the driver. The format
1406 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1408 To compile this driver as a module, choose M here: the
1409 module will be called sym53c416.
1412 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1413 depends on PCI && SCSI && EXPERIMENTAL
1415 This driver supports PCI SCSI host adapters based on the ASIC
1416 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1418 This driver works, but is still in experimental status. So better
1419 have a bootable disk and a backup in case of emergency.
1421 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1423 To compile this driver as a module, choose M here: the
1424 module will be called dc395x.
1427 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1428 depends on PCI && SCSI
1430 This driver supports PCI SCSI host adapters based on the Am53C974A
1431 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1432 PCscsi/PCnet (Am53/79C974) solutions.
1434 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1436 Note that this driver does NOT support Tekram DC390W/U/F, which are
1437 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1439 To compile this driver as a module, choose M here: the
1440 module will be called tmscsim.
1443 tristate "Trantor T128/T128F/T228 SCSI support"
1444 depends on ISA && SCSI
1445 select SCSI_SPI_ATTRS
1446 select CHECK_SIGNATURE
1448 This is support for a SCSI host adapter. It is explained in section
1449 3.11 of the SCSI-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1451 of the box, you may have to change some settings in
1452 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1453 Adaptec, and some former Trantor products are being sold under the
1456 To compile this driver as a module, choose M here: the
1457 module will be called t128.
1460 tristate "UltraStor 14F/34F support"
1461 depends on ISA && SCSI && ISA_DMA_API
1463 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1464 The source at <file:drivers/scsi/u14-34f.c> contains some
1465 information about this hardware. If the driver doesn't work out of
1466 the box, you may have to change some settings in
1467 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1468 <http://www.tldp.org/docs.html#howto>. Note that there is also
1469 another driver for the same hardware: "UltraStor SCSI support",
1470 below. You should say Y to both only if you want 24F support as
1473 To compile this driver as a module, choose M here: the
1474 module will be called u14-34f.
1476 config SCSI_U14_34F_TAGGED_QUEUE
1477 bool "enable tagged command queueing"
1478 depends on SCSI_U14_34F
1480 This is a feature of SCSI-2 which improves performance: the host
1481 adapter can send several SCSI commands to a device's queue even if
1482 previous commands haven't finished yet.
1483 This is equivalent to the "u14-34f=tc:y" boot option.
1485 config SCSI_U14_34F_LINKED_COMMANDS
1486 bool "enable elevator sorting"
1487 depends on SCSI_U14_34F
1489 This option enables elevator sorting for all probed SCSI disks and
1490 CD-ROMs. It definitely reduces the average seek distance when doing
1491 random seeks, but this does not necessarily result in a noticeable
1492 performance improvement: your mileage may vary...
1493 This is equivalent to the "u14-34f=lc:y" boot option.
1495 config SCSI_U14_34F_MAX_TAGS
1496 int "maximum number of queued commands"
1497 depends on SCSI_U14_34F
1500 This specifies how many SCSI commands can be maximally queued for
1501 each probed SCSI device. You should reduce the default value of 8
1502 only if you have disks with buggy or limited tagged command support.
1503 Minimum is 2 and maximum is 14. This value is also the window size
1504 used by the elevator sorting option above. The effective value used
1505 by the driver for each probed SCSI device is reported at boot time.
1506 This is equivalent to the "u14-34f=mq:8" boot option.
1508 config SCSI_ULTRASTOR
1509 tristate "UltraStor SCSI support"
1510 depends on X86 && ISA && SCSI
1512 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1513 adapter family. This driver is explained in section 3.12 of the
1514 SCSI-HOWTO, available from
1515 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1516 of the box, you may have to change some settings in
1517 <file:drivers/scsi/ultrastor.h>.
1519 Note that there is also another driver for the same hardware:
1520 "UltraStor 14F/34F support", above.
1522 To compile this driver as a module, choose M here: the
1523 module will be called ultrastor.
1526 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1527 depends on PCI && SCSI && !64BIT
1529 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1530 SCSI host adapter. Please read the SCSI-HOWTO, available from
1531 <http://www.tldp.org/docs.html#howto>.
1533 To compile this driver as a module, choose M here: the
1534 module will be called nsp32.
1537 tristate "SCSI debugging host simulator"
1541 This is a host adapter simulator that can simulate multiple hosts
1542 each with multiple dummy SCSI devices (disks). It defaults to one
1543 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1544 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1545 dummy disks are simulated, they share the same kernel RAM for
1546 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1547 information. This driver is primarily of use to those testing the
1548 SCSI and block subsystems. If unsure, say N.
1551 tristate "MESH (Power Mac internal SCSI) support"
1552 depends on PPC32 && PPC_PMAC && SCSI
1554 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1555 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1556 other Power Macintoshes do). Say Y to include support for this SCSI
1559 To compile this driver as a module, choose M here: the
1560 module will be called mesh.
1562 config SCSI_MESH_SYNC_RATE
1563 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1564 depends on SCSI_MESH
1567 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1568 drives a bus which is entirely internal to the machine (such as the
1569 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1570 operation at up to 10 MB/s. On machines where the SCSI bus
1571 controlled by the MESH can have external devices connected, it is
1572 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1573 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1574 to disable synchronous operation.
1576 config SCSI_MESH_RESET_DELAY_MS
1577 int "initial bus reset delay (ms) (0 = no reset)"
1578 depends on SCSI_MESH
1581 config SCSI_MAC53C94
1582 tristate "53C94 (Power Mac external SCSI) support"
1583 depends on PPC32 && PPC_PMAC && SCSI
1585 On Power Macintoshes (and clones) with two SCSI buses, the external
1586 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1587 machines which only have one SCSI bus, such as the 7200, also use
1588 the 53C94. Say Y to include support for the 53C94.
1590 To compile this driver as a module, choose M here: the
1591 module will be called mac53c94.
1593 source "drivers/scsi/arm/Kconfig"
1596 bool "MIPS JAZZ FAS216 SCSI support"
1597 depends on MACH_JAZZ && SCSI
1598 select SCSI_SPI_ATTRS
1600 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1601 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1605 tristate "A3000 WD33C93A support"
1606 depends on AMIGA && SCSI
1608 If you have an Amiga 3000 and have SCSI devices connected to the
1609 built-in SCSI controller, say Y. Otherwise, say N.
1611 To compile this driver as a module, choose M here: the
1612 module will be called a3000.
1615 tristate "A2091/A590 WD33C93A support"
1616 depends on ZORRO && SCSI
1618 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1621 To compile this driver as a module, choose M here: the
1622 module will be called a2091.
1625 tristate "GVP Series II WD33C93A support"
1626 depends on ZORRO && SCSI
1628 If you have a Great Valley Products Series II SCSI controller,
1629 answer Y. Also say Y if you have a later model of GVP SCSI
1630 controller (such as the GVP A4008 or a Combo board). Otherwise,
1631 answer N. This driver does NOT work for the T-Rex series of
1632 accelerators from TekMagic and GVP-M.
1634 To compile this driver as a module, choose M here: the
1635 module will be called gvp11.
1638 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1639 depends on AMIGA && SCSI && EXPERIMENTAL
1640 select SCSI_SPI_ATTRS
1642 If you have an Amiga 4000T and have SCSI devices connected to the
1643 built-in SCSI controller, say Y. Otherwise, say N.
1645 To compile this driver as a module, choose M here: the
1646 module will be called a4000t.
1648 config SCSI_ZORRO7XX
1649 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1650 depends on ZORRO && SCSI && EXPERIMENTAL
1651 select SCSI_SPI_ATTRS
1653 Support for various NCR53c710-based SCSI controllers on Zorro
1654 expansion boards for the Amiga.
1656 - the Amiga 4091 Zorro III SCSI-2 controller,
1657 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1659 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1660 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1661 accelerator card for the Amiga 1200,
1662 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1665 tristate "Atari native SCSI support"
1666 depends on ATARI && SCSI
1667 select SCSI_SPI_ATTRS
1670 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1671 Falcon, ...) say Y to get it supported. Of course also, if you have
1672 a compatible SCSI controller (e.g. for Medusa).
1674 To compile this driver as a module, choose M here: the
1675 module will be called atari_scsi.
1677 This driver supports both styles of NCR integration into the
1678 system: the TT style (separate DMA), and the Falcon style (via
1679 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1680 in the Hades (without DMA).
1682 config ATARI_SCSI_TOSHIBA_DELAY
1683 bool "Long delays for Toshiba CD-ROMs"
1684 depends on ATARI_SCSI
1686 This option increases the delay after a SCSI arbitration to
1687 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1688 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1689 would impact performance a bit, so say N.
1691 config ATARI_SCSI_RESET_BOOT
1692 bool "Reset SCSI-devices at boottime"
1693 depends on ATARI_SCSI
1695 Reset the devices on your Atari whenever it boots. This makes the
1696 boot process fractionally longer but may assist recovery from errors
1697 that leave the devices with SCSI operations partway completed.
1700 bool "Macintosh NCR5380 SCSI"
1701 depends on MAC && SCSI=y
1702 select SCSI_SPI_ATTRS
1704 This is the NCR 5380 SCSI controller included on most of the 68030
1705 based Macintoshes. If you have one of these say Y and read the
1706 SCSI-HOWTO, available from
1707 <http://www.tldp.org/docs.html#howto>.
1710 tristate "Macintosh NCR53c9[46] SCSI"
1711 depends on MAC && SCSI
1712 select SCSI_SPI_ATTRS
1714 This is the NCR 53c9x SCSI controller found on most of the 68040
1717 To compile this driver as a module, choose M here: the module
1718 will be called mac_esp.
1721 bool "WD33C93 SCSI driver for MVME147"
1722 depends on MVME147 && SCSI=y
1723 select SCSI_SPI_ATTRS
1725 Support for the on-board SCSI controller on the Motorola MVME147
1726 single-board computer.
1729 tristate "NCR53C710 SCSI driver for MVME16x"
1730 depends on MVME16x && SCSI
1731 select SCSI_SPI_ATTRS
1733 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1734 SCSI controller chip. Almost everyone using one of these boards
1735 will want to say Y to this question.
1737 config BVME6000_SCSI
1738 tristate "NCR53C710 SCSI driver for BVME6000"
1739 depends on BVME6000 && SCSI
1740 select SCSI_SPI_ATTRS
1742 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1743 SCSI controller chip. Almost everyone using one of these boards
1744 will want to say Y to this question.
1747 tristate "Sun3 NCR5380 SCSI"
1748 depends on SUN3 && SCSI
1749 select SCSI_SPI_ATTRS
1751 This option will enable support for the OBIO (onboard io) NCR5380
1752 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1753 "Sun3" type VME scsi controllers also based on the NCR5380.
1754 General Linux information on the Sun 3 series (now discontinued)
1755 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1758 bool "Sun3x ESP SCSI"
1759 depends on SUN3X && SCSI=y
1760 select SCSI_SPI_ATTRS
1762 The ESP was an on-board SCSI controller used on Sun 3/80
1763 machines. Say Y here to compile in support for it.
1766 tristate "Sparc ESP Scsi Driver"
1767 depends on SBUS && SCSI
1768 select SCSI_SPI_ATTRS
1770 This is the driver for the Sun ESP SCSI host adapter. The ESP
1771 chipset is present in most SPARC SBUS-based computers and
1772 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1773 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1775 To compile this driver as a module, choose M here: the
1776 module will be called sun_esp.
1779 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1780 depends on S390 && QDIO && SCSI
1781 select SCSI_FC_ATTRS
1783 If you want to access SCSI devices attached to your IBM eServer
1784 zSeries by means of Fibre Channel interfaces say Y.
1785 For details please refer to the documentation provided by IBM at
1786 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1788 This driver is also available as a module. This module will be
1789 called zfcp. If you want to compile it as a module, say M here
1790 and read <file:Documentation/kbuild/modules.txt>.
1793 tristate "SCSI RDMA Protocol helper library"
1794 depends on SCSI && PCI
1797 If you wish to use SRP target drivers, say Y.
1799 To compile this driver as a module, choose M here: the
1800 module will be called libsrp.
1802 endif # SCSI_LOWLEVEL
1804 source "drivers/scsi/pcmcia/Kconfig"
1806 source "drivers/scsi/device_handler/Kconfig"