1 menu "SCSI device support"
5 default y if SCSI=n || SCSI=y
9 tristate "RAID Transport Class"
17 tristate "SCSI device support"
19 select SCSI_DMA if HAS_DMA
21 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
22 any other SCSI device under Linux, say Y and make sure that you know
23 the name of your SCSI host adapter (the card inside your computer
24 that "speaks" the SCSI protocol, also called SCSI controller),
25 because you will be asked for it.
27 You also need to say Y here if you have a device which speaks
28 the SCSI protocol. Examples of this include the parallel port
29 version of the IOMEGA ZIP drive, USB storage devices, Fibre
30 Channel, and FireWire storage.
32 To compile this driver as a module, choose M here and read
33 <file:Documentation/scsi/scsi.txt>.
34 The module will be called scsi_mod.
36 However, do not compile this as a module if your root file system
37 (the one containing the directory /) is located on a SCSI device.
48 config SCSI_MQ_DEFAULT
49 bool "SCSI: use blk-mq I/O path by default"
52 This option enables the new blk-mq based I/O path for SCSI
53 devices by default. With the option the scsi_mod.use_blk_mq
54 module/boot option defaults to Y, without it to N, but it can
55 still be overriden either way.
60 bool "legacy /proc/scsi/ support"
61 depends on SCSI && PROC_FS
64 This option enables support for the various files in
65 /proc/scsi. In Linux 2.6 this has been superseded by
66 files in sysfs but many legacy applications rely on this.
70 comment "SCSI support type (disk, tape, CD-ROM)"
74 tristate "SCSI disk support"
76 select CRC_T10DIF if BLK_DEV_INTEGRITY
78 If you want to use SCSI hard disks, Fibre Channel disks,
79 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
80 USB storage or the SCSI or parallel port version of
81 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
82 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
86 To compile this driver as a module, choose M here and read
87 <file:Documentation/scsi/scsi.txt>.
88 The module will be called sd_mod.
90 Do not compile this driver as a module if your root file system
91 (the one containing the directory /) is located on a SCSI disk.
92 In this case, do not compile the driver for your SCSI host adapter
93 (below) as a module either.
96 tristate "SCSI tape support"
99 If you want to use a SCSI tape drive under Linux, say Y and read the
100 SCSI-HOWTO, available from
101 <http://www.tldp.org/docs.html#howto>, and
102 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
105 To compile this driver as a module, choose M here and read
106 <file:Documentation/scsi/scsi.txt>. The module will be called st.
109 tristate "SCSI OnStream SC-x0 tape support"
112 The OnStream SC-x0 SCSI tape drives cannot be driven by the
113 standard st driver, but instead need this special osst driver and
114 use the /dev/osstX char device nodes (major 206). Via usb-storage,
115 you may be able to drive the USB-x0 and DI-x0 drives as well.
116 Note that there is also a second generation of OnStream
117 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
118 tapes (QIC-157) and can be driven by the standard driver st.
119 For more information, you may have a look at the SCSI-HOWTO
120 <http://www.tldp.org/docs.html#howto> and
121 <file:Documentation/scsi/osst.txt> in the kernel source.
122 More info on the OnStream driver may be found on
123 <http://sourceforge.net/projects/osst/>
124 Please also have a look at the standard st docu, as most of it
125 applies to osst as well.
127 To compile this driver as a module, choose M here and read
128 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
131 tristate "SCSI CDROM support"
134 If you want to use a CD or DVD drive attached to your computer
135 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
136 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
138 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
140 To compile this driver as a module, choose M here and read
141 <file:Documentation/scsi/scsi.txt>.
142 The module will be called sr_mod.
144 config BLK_DEV_SR_VENDOR
145 bool "Enable vendor-specific extensions (for SCSI CDROM)"
146 depends on BLK_DEV_SR
148 This enables the usage of vendor specific SCSI commands. This is
149 required to support multisession CDs with old NEC/TOSHIBA cdrom
150 drives (and HP Writers). If you have such a drive and get the first
151 session only, try saying Y here; everybody else says N.
154 tristate "SCSI generic support"
157 If you want to use SCSI scanners, synthesizers or CD-writers or just
158 about anything having "SCSI" in its name other than hard disks,
159 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
160 directly, so you need some additional software which knows how to
161 talk to these devices using the SCSI protocol:
163 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
164 writer software look at Cdrtools
165 (<http://cdrecord.berlios.de/private/cdrecord.html>)
166 and for burning a "disk at once": CDRDAO
167 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
168 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
169 For other devices, it's possible that you'll have to write the
170 driver software yourself. Please read the file
171 <file:Documentation/scsi/scsi-generic.txt> for more information.
173 To compile this driver as a module, choose M here and read
174 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
179 tristate "SCSI media changer support"
182 This is a driver for SCSI media changers. Most common devices are
183 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
184 don't need this for those tiny 6-slot cdrom changers. Media
185 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
186 If you have such hardware and want to use it with linux, say Y
187 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
189 If you want to compile this as a module ( = code which can be
190 inserted in and removed from the running kernel whenever you want),
191 say M here and read <file:Documentation/kbuild/modules.txt> and
192 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
195 config SCSI_ENCLOSURE
196 tristate "SCSI Enclosure Support"
197 depends on SCSI && ENCLOSURE_SERVICES
199 Enclosures are devices sitting on or in SCSI backplanes that
200 manage devices. If you have a disk cage, the chances are that
201 it has an enclosure device. Selecting this option will just allow
202 certain enclosure conditions to be reported and is not required.
204 config SCSI_CONSTANTS
205 bool "Verbose SCSI error reporting (kernel size +=12K)"
208 The error messages regarding your SCSI hardware will be easier to
209 understand if you say Y here; it will enlarge your kernel by about
210 12 KB. If in doubt, say Y.
213 bool "SCSI logging facility"
216 This turns on a logging facility that can be used to debug a number
217 of SCSI related problems.
219 If you say Y here, no logging output will appear by default, but you
220 can enable logging by saying Y to "/proc file system support" and
221 "Sysctl support" below and executing the command
223 echo <bitmask> > /proc/sys/dev/scsi/logging_level
225 where <bitmask> is a four byte value representing the logging type
226 and logging level for each type of logging selected.
228 There are a number of logging types and you can find them in the
229 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
230 are also described in that file and they determine the verbosity of
231 the logging for each logging type.
233 If you say N here, it may be harder to track down some types of SCSI
234 problems. If you say Y here your kernel will be somewhat larger, but
235 there should be no noticeable performance impact as long as you have
238 config SCSI_SCAN_ASYNC
239 bool "Asynchronous SCSI scanning"
242 The SCSI subsystem can probe for devices while the rest of the
243 system continues booting, and even probe devices on different
244 busses in parallel, leading to a significant speed-up.
246 If you have built SCSI as modules, enabling this option can
247 be a problem as the devices may not have been found by the
248 time your system expects them to have been. You can load the
249 scsi_wait_scan module to ensure that all scans have completed.
250 If you build your SCSI drivers into the kernel, then everything
251 will work fine if you say Y here.
253 You can override this choice by specifying "scsi_mod.scan=sync"
254 or async on the kernel's command line.
256 Note that this setting also affects whether resuming from
257 system suspend will be performed asynchronously.
259 menu "SCSI Transports"
262 config SCSI_SPI_ATTRS
263 tristate "Parallel SCSI (SPI) Transport Attributes"
266 If you wish to export transport-specific information about
267 each attached SCSI device to sysfs, say Y. Otherwise, say N.
270 tristate "FiberChannel Transport Attributes"
271 depends on SCSI && NET
274 If you wish to export transport-specific information about
275 each attached FiberChannel device to sysfs, say Y.
278 config SCSI_ISCSI_ATTRS
279 tristate "iSCSI Transport Attributes"
280 depends on SCSI && NET
281 select BLK_DEV_BSGLIB
283 If you wish to export transport-specific information about
284 each attached iSCSI device to sysfs, say Y.
287 config SCSI_SAS_ATTRS
288 tristate "SAS Transport Attributes"
292 If you wish to export transport-specific information about
293 each attached SAS device to sysfs, say Y.
295 source "drivers/scsi/libsas/Kconfig"
297 config SCSI_SRP_ATTRS
298 tristate "SRP Transport Attributes"
301 If you wish to export transport-specific information about
302 each attached SRP device to sysfs, say Y.
306 menuconfig SCSI_LOWLEVEL
307 bool "SCSI low-level drivers"
311 if SCSI_LOWLEVEL && SCSI
314 tristate "iSCSI Initiator over TCP/IP"
315 depends on SCSI && INET
319 select SCSI_ISCSI_ATTRS
321 The iSCSI Driver provides a host with the ability to access storage
322 through an IP network. The driver uses the iSCSI protocol to transport
323 SCSI requests and responses over a TCP/IP network between the host
324 (the "initiator") and "targets". Architecturally, the iSCSI driver
325 combines with the host's TCP/IP stack, network drivers, and Network
326 Interface Card (NIC) to provide the same functions as a SCSI or a
327 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
329 To compile this driver as a module, choose M here: the
330 module will be called iscsi_tcp.
332 The userspace component needed to initialize the driver, documentation,
333 and sample configuration files can be found here:
335 http://open-iscsi.org
337 config ISCSI_BOOT_SYSFS
338 tristate "iSCSI Boot Sysfs Interface"
341 This option enables support for exposing iSCSI boot information
342 via sysfs to userspace. If you wish to export this information,
343 say Y. Otherwise, say N.
345 source "drivers/scsi/cxgbi/Kconfig"
346 source "drivers/scsi/bnx2i/Kconfig"
347 source "drivers/scsi/bnx2fc/Kconfig"
348 source "drivers/scsi/be2iscsi/Kconfig"
351 tristate "SGI WD93C93 SCSI Driver"
352 depends on SGI_HAS_WD93 && SCSI
354 If you have a Western Digital WD93 SCSI controller on
355 an SGI MIPS system, say Y. Otherwise, say N.
357 config BLK_DEV_3W_XXXX_RAID
358 tristate "3ware 5/6/7/8xxx ATA-RAID support"
359 depends on PCI && SCSI
361 3ware is the only hardware ATA-Raid product in Linux to date.
362 This card is 2,4, or 8 channel master mode support only.
363 SCSI support required!!!
365 <http://www.3ware.com/>
367 Please read the comments at the top of
368 <file:drivers/scsi/3w-xxxx.c>.
371 tristate "HP Smart Array SCSI driver"
372 depends on PCI && SCSI
373 select CHECK_SIGNATURE
375 This driver supports HP Smart Array Controllers (circa 2009).
376 It is a SCSI alternative to the cciss driver, which is a block
377 driver. Anyone wishing to use HP Smart Array controllers who
378 would prefer the devices be presented to linux as SCSI devices,
379 rather than as generic block devices should say Y here.
382 tristate "3ware 9xxx SATA-RAID support"
383 depends on PCI && SCSI
385 This driver supports the 9000 series 3ware SATA-RAID cards.
387 <http://www.amcc.com>
389 Please read the comments at the top of
390 <file:drivers/scsi/3w-9xxx.c>.
393 tristate "3ware 97xx SAS/SATA-RAID support"
394 depends on PCI && SCSI
396 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
400 Please read the comments at the top of
401 <file:drivers/scsi/3w-sas.c>.
403 config SCSI_7000FASST
404 tristate "7000FASST SCSI support"
405 depends on ISA && SCSI && ISA_DMA_API
406 select CHECK_SIGNATURE
408 This driver supports the Western Digital 7000 SCSI host adapter
409 family. Some information is in the source:
410 <file:drivers/scsi/wd7000.c>.
412 To compile this driver as a module, choose M here: the
413 module will be called wd7000.
416 tristate "ACARD SCSI support"
417 depends on PCI && SCSI
419 This driver supports the ACARD SCSI host adapter.
420 Support Chip <ATP870 ATP876 ATP880 ATP885>
421 To compile this driver as a module, choose M here: the
422 module will be called atp870u.
425 tristate "Adaptec AHA152X/2825 support"
426 depends on ISA && SCSI
427 select SCSI_SPI_ATTRS
428 select CHECK_SIGNATURE
430 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
431 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
432 must be manually specified in this case.
434 It is explained in section 3.3 of the SCSI-HOWTO, available from
435 <http://www.tldp.org/docs.html#howto>. You might also want to
436 read the file <file:Documentation/scsi/aha152x.txt>.
438 To compile this driver as a module, choose M here: the
439 module will be called aha152x.
442 tristate "Adaptec AHA1542 support"
443 depends on ISA && SCSI && ISA_DMA_API
445 This is support for a SCSI host adapter. It is explained in section
446 3.4 of the SCSI-HOWTO, available from
447 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
448 purchased by Adaptec, and some former Trantor products are being
449 sold under the Adaptec name. If it doesn't work out of the box, you
450 may have to change some settings in <file:drivers/scsi/aha1542.h>.
452 To compile this driver as a module, choose M here: the
453 module will be called aha1542.
456 tristate "Adaptec AHA1740 support"
457 depends on EISA && SCSI
459 This is support for a SCSI host adapter. It is explained in section
460 3.5 of the SCSI-HOWTO, available from
461 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
462 of the box, you may have to change some settings in
463 <file:drivers/scsi/aha1740.h>.
465 To compile this driver as a module, choose M here: the
466 module will be called aha1740.
469 tristate "Adaptec AACRAID support"
470 depends on SCSI && PCI
472 This driver supports a variety of Dell, HP, Adaptec, IBM and
473 ICP storage products. For a list of supported products, refer
474 to <file:Documentation/scsi/aacraid.txt>.
476 To compile this driver as a module, choose M here: the module
477 will be called aacraid.
480 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
481 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
482 source "drivers/scsi/aic94xx/Kconfig"
483 source "drivers/scsi/mvsas/Kconfig"
486 tristate "Marvell UMI driver"
487 depends on SCSI && PCI
489 Module for Marvell Universal Message Interface(UMI) driver
491 To compile this driver as a module, choose M here: the
492 module will be called mvumi.
495 tristate "Adaptec I2O RAID support "
496 depends on SCSI && PCI && VIRT_TO_BUS
498 This driver supports all of Adaptec's I2O based RAID controllers as
499 well as the DPT SmartRaid V cards. This is an Adaptec maintained
500 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
502 To compile this driver as a module, choose M here: the
503 module will be called dpt_i2o.
506 tristate "AdvanSys SCSI support"
507 depends on SCSI && VIRT_TO_BUS && !ARM
508 depends on ISA || EISA || PCI
510 This is a driver for all SCSI host adapters manufactured by
511 AdvanSys. It is documented in the kernel source in
512 <file:drivers/scsi/advansys.c>.
514 To compile this driver as a module, choose M here: the
515 module will be called advansys.
518 tristate "Always IN2000 SCSI support"
519 depends on ISA && SCSI
521 This is support for an ISA bus SCSI host adapter. You'll find more
522 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
523 out of the box, you may have to change the jumpers for IRQ or
526 To compile this driver as a module, choose M here: the
527 module will be called in2000.
530 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
531 depends on PCI && SCSI
533 This driver supports all of ARECA's SATA/SAS RAID controller cards.
534 This is an ARECA-maintained driver by Erich Chen.
535 If you have any problems, please mail to: <erich@areca.com.tw>.
536 Areca supports Linux RAID config tools.
537 Please link <http://www.areca.com.tw>
539 To compile this driver as a module, choose M here: the
540 module will be called arcmsr (modprobe arcmsr).
542 source "drivers/scsi/esas2r/Kconfig"
543 source "drivers/scsi/megaraid/Kconfig.megaraid"
544 source "drivers/scsi/mpt2sas/Kconfig"
545 source "drivers/scsi/mpt3sas/Kconfig"
546 source "drivers/scsi/ufs/Kconfig"
549 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
550 depends on SCSI && PCI
552 This option enables support for HighPoint RocketRAID 3xxx/4xxx
555 To compile this driver as a module, choose M here; the module
556 will be called hptiop. If unsure, say N.
559 tristate "BusLogic SCSI support"
560 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
562 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
563 Adapters. Consult the SCSI-HOWTO, available from
564 <http://www.tldp.org/docs.html#howto>, and the files
565 <file:Documentation/scsi/BusLogic.txt> and
566 <file:Documentation/scsi/FlashPoint.txt> for more information.
567 Note that support for FlashPoint is only available for 32-bit
570 To compile this driver as a module, choose M here: the
571 module will be called BusLogic.
573 config SCSI_FLASHPOINT
574 bool "FlashPoint support"
575 depends on SCSI_BUSLOGIC && PCI
577 This option allows you to add FlashPoint support to the
578 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
579 substantial, so users of MultiMaster Host Adapters may not
583 tristate "VMware PVSCSI driver support"
584 depends on PCI && SCSI && X86
586 This driver supports VMware's para virtualized SCSI HBA.
587 To compile this driver as a module, choose M here: the
588 module will be called vmw_pvscsi.
590 config XEN_SCSI_FRONTEND
591 tristate "XEN SCSI frontend driver"
592 depends on SCSI && XEN
593 select XEN_XENBUS_FRONTEND
595 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
596 within another guest OS (usually Dom0).
597 Only needed if the kernel is running in a XEN guest and generic
598 SCSI access to a device is needed.
600 config HYPERV_STORAGE
601 tristate "Microsoft Hyper-V virtual storage driver"
602 depends on SCSI && HYPERV
605 Select this option to enable the Hyper-V virtual storage driver.
608 tristate "LibFC module"
609 depends on SCSI_FC_ATTRS
612 Fibre Channel library module
615 tristate "LibFCoE module"
618 Library for Fibre Channel over Ethernet module
621 tristate "FCoE module"
625 Fibre Channel over Ethernet module
628 tristate "Cisco FNIC Driver"
629 depends on PCI && X86
632 This is support for the Cisco PCI-Express FCoE HBA.
634 To compile this driver as a module, choose M here and read
635 <file:Documentation/scsi/scsi.txt>.
636 The module will be called fnic.
639 tristate "DMX3191D SCSI support"
640 depends on PCI && SCSI
641 select SCSI_SPI_ATTRS
643 This is support for Domex DMX3191D SCSI Host Adapters.
645 To compile this driver as a module, choose M here: the
646 module will be called dmx3191d.
649 tristate "DTC3180/3280 SCSI support"
650 depends on ISA && SCSI
651 select SCSI_SPI_ATTRS
652 select CHECK_SIGNATURE
654 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
655 the SCSI-HOWTO, available from
656 <http://www.tldp.org/docs.html#howto>, and the file
657 <file:Documentation/scsi/dtc3x80.txt>.
659 To compile this driver as a module, choose M here: the
660 module will be called dtc.
663 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
664 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
666 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
667 ISA and all EISA I/O addresses are probed looking for the "EATA"
668 signature. The addresses of all the PCI SCSI controllers reported
669 by the PCI subsystem are probed as well.
671 You want to read the start of <file:drivers/scsi/eata.c> and the
672 SCSI-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 To compile this driver as a module, choose M here: the
676 module will be called eata.
678 config SCSI_EATA_TAGGED_QUEUE
679 bool "enable tagged command queueing"
682 This is a feature of SCSI-2 which improves performance: the host
683 adapter can send several SCSI commands to a device's queue even if
684 previous commands haven't finished yet.
685 This is equivalent to the "eata=tc:y" boot option.
687 config SCSI_EATA_LINKED_COMMANDS
688 bool "enable elevator sorting"
691 This option enables elevator sorting for all probed SCSI disks and
692 CD-ROMs. It definitely reduces the average seek distance when doing
693 random seeks, but this does not necessarily result in a noticeable
694 performance improvement: your mileage may vary...
695 This is equivalent to the "eata=lc:y" boot option.
697 config SCSI_EATA_MAX_TAGS
698 int "maximum number of queued commands"
702 This specifies how many SCSI commands can be maximally queued for
703 each probed SCSI device. You should reduce the default value of 16
704 only if you have disks with buggy or limited tagged command support.
705 Minimum is 2 and maximum is 62. This value is also the window size
706 used by the elevator sorting option above. The effective value used
707 by the driver for each probed SCSI device is reported at boot time.
708 This is equivalent to the "eata=mq:8" boot option.
711 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
712 depends on (ISA || EISA || PCI) && SCSI && BROKEN
714 This driver supports all EATA-PIO protocol compliant SCSI Host
715 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
716 host adapters could also use this driver but are discouraged from
717 doing so, since this driver only supports hard disks and lacks
718 numerous features. You might want to have a look at the SCSI-HOWTO,
719 available from <http://www.tldp.org/docs.html#howto>.
721 To compile this driver as a module, choose M here: the
722 module will be called eata_pio.
724 config SCSI_FUTURE_DOMAIN
725 tristate "Future Domain 16xx SCSI/AHA-2920A support"
726 depends on (ISA || PCI) && SCSI
727 select CHECK_SIGNATURE
729 This is support for Future Domain's 16-bit SCSI host adapters
730 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
731 other adapters based on the Future Domain chipsets (Quantum
732 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
733 It is explained in section 3.7 of the SCSI-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
736 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
737 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
738 controller support"). This Future Domain driver works with the older
739 Adaptec AHA-2920A boards with a Future Domain chip on them.
741 To compile this driver as a module, choose M here: the
742 module will be called fdomain.
745 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
746 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
748 Formerly called GDT SCSI Disk Array Controller Support.
750 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
751 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
752 in the kernel source in <file:drivers/scsi/gdth.c> and
753 <file:drivers/scsi/gdth.h>.
755 To compile this driver as a module, choose M here: the
756 module will be called gdth.
759 tristate "Intel(R) C600 Series Chipset SAS Controller"
760 depends on PCI && SCSI
762 select SCSI_SAS_LIBSAS
764 This driver supports the 6Gb/s SAS capabilities of the storage
765 control unit found in the Intel(R) C600 series chipset.
767 config SCSI_GENERIC_NCR5380
768 tristate "Generic NCR5380/53c400 SCSI PIO support"
769 depends on ISA && SCSI
770 select SCSI_SPI_ATTRS
772 This is a driver for the old NCR 53c80 series of SCSI controllers
773 on boards using PIO. Most boards such as the Trantor T130 fit this
774 category, along with a large number of ISA 8bit controllers shipped
775 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
776 you should select the specific driver for that card rather than
777 generic 5380 support.
779 It is explained in section 3.8 of the SCSI-HOWTO, available from
780 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
781 of the box, you may have to change some settings in
782 <file:drivers/scsi/g_NCR5380.h>.
784 To compile this driver as a module, choose M here: the
785 module will be called g_NCR5380.
787 config SCSI_GENERIC_NCR5380_MMIO
788 tristate "Generic NCR5380/53c400 SCSI MMIO support"
789 depends on ISA && SCSI
790 select SCSI_SPI_ATTRS
792 This is a driver for the old NCR 53c80 series of SCSI controllers
793 on boards using memory mapped I/O.
794 It is explained in section 3.8 of the SCSI-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
796 of the box, you may have to change some settings in
797 <file:drivers/scsi/g_NCR5380.h>.
799 To compile this driver as a module, choose M here: the
800 module will be called g_NCR5380_mmio.
802 config SCSI_GENERIC_NCR53C400
803 bool "Enable NCR53c400 extensions"
804 depends on SCSI_GENERIC_NCR5380
806 This enables certain optimizations for the NCR53c400 SCSI cards.
807 You might as well try it out. Note that this driver will only probe
808 for the Trantor T130B in its default configuration; you might have
809 to pass a command line option to the kernel at boot time if it does
810 not detect your card. See the file
811 <file:Documentation/scsi/g_NCR5380.txt> for details.
814 tristate "IBM ServeRAID support"
815 depends on PCI && SCSI
817 This is support for the IBM ServeRAID hardware RAID controllers.
818 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
819 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
820 for more information. If this driver does not work correctly
821 without modification please contact the author by email at
822 <ipslinux@adaptec.com>.
824 To compile this driver as a module, choose M here: the
825 module will be called ips.
828 tristate "IBM Virtual SCSI support"
829 depends on PPC_PSERIES
830 select SCSI_SRP_ATTRS
832 This is the IBM POWER Virtual SCSI Client
834 To compile this driver as a module, choose M here: the
835 module will be called ibmvscsi.
838 tristate "IBM Virtual FC support"
839 depends on PPC_PSERIES && SCSI
840 depends on SCSI_FC_ATTRS
842 This is the IBM POWER Virtual FC Client
844 To compile this driver as a module, choose M here: the
845 module will be called ibmvfc.
847 config SCSI_IBMVFC_TRACE
848 bool "enable driver internal trace"
849 depends on SCSI_IBMVFC
852 If you say Y here, the driver will trace all commands issued
853 to the adapter. Performance impact is minimal. Trace can be
854 dumped using /sys/class/scsi_host/hostXX/trace.
857 tristate "Initio 9100U(W) support"
858 depends on PCI && SCSI
860 This is support for the Initio 91XXU(W) SCSI host adapter. Please
861 read the SCSI-HOWTO, available from
862 <http://www.tldp.org/docs.html#howto>.
864 To compile this driver as a module, choose M here: the
865 module will be called initio.
868 tristate "Initio INI-A100U2W support"
869 depends on PCI && SCSI
871 This is support for the Initio INI-A100U2W SCSI host adapter.
872 Please read the SCSI-HOWTO, available from
873 <http://www.tldp.org/docs.html#howto>.
875 To compile this driver as a module, choose M here: the
876 module will be called a100u2w.
879 tristate "IOMEGA parallel port (ppa - older drives)"
880 depends on SCSI && PARPORT_PC
882 This driver supports older versions of IOMEGA's parallel port ZIP
883 drive (a 100 MB removable media device).
885 Note that you can say N here if you have the SCSI version of the ZIP
886 drive: it will be supported automatically if you said Y to the
887 generic "SCSI disk support", above.
889 If you have the ZIP Plus drive or a more recent parallel port ZIP
890 drive (if the supplied cable with the drive is labeled "AutoDetect")
891 then you should say N here and Y to "IOMEGA parallel port (imm -
892 newer drives)", below.
894 For more information about this driver and how to use it you should
895 read the file <file:Documentation/scsi/ppa.txt>. You should also read
896 the SCSI-HOWTO, which is available from
897 <http://www.tldp.org/docs.html#howto>. If you use this driver,
898 you will still be able to use the parallel port for other tasks,
899 such as a printer; it is safe to compile both drivers into the
902 To compile this driver as a module, choose M here: the
903 module will be called ppa.
906 tristate "IOMEGA parallel port (imm - newer drives)"
907 depends on SCSI && PARPORT_PC
909 This driver supports newer versions of IOMEGA's parallel port ZIP
910 drive (a 100 MB removable media device).
912 Note that you can say N here if you have the SCSI version of the ZIP
913 drive: it will be supported automatically if you said Y to the
914 generic "SCSI disk support", above.
916 If you have the ZIP Plus drive or a more recent parallel port ZIP
917 drive (if the supplied cable with the drive is labeled "AutoDetect")
918 then you should say Y here; if you have an older ZIP drive, say N
919 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
921 For more information about this driver and how to use it you should
922 read the file <file:Documentation/scsi/ppa.txt>. You should also read
923 the SCSI-HOWTO, which is available from
924 <http://www.tldp.org/docs.html#howto>. If you use this driver,
925 you will still be able to use the parallel port for other tasks,
926 such as a printer; it is safe to compile both drivers into the
929 To compile this driver as a module, choose M here: the
930 module will be called imm.
932 config SCSI_IZIP_EPP16
933 bool "ppa/imm option - Use slow (but safe) EPP-16"
934 depends on SCSI_PPA || SCSI_IMM
936 EPP (Enhanced Parallel Port) is a standard for parallel ports which
937 allows them to act as expansion buses that can handle up to 64
940 Some parallel port chipsets are slower than their motherboard, and
941 so we have to control the state of the chipset's FIFO queue every
942 now and then to avoid data loss. This will be done if you say Y
945 Generally, saying Y is the safe option and slows things down a bit.
947 config SCSI_IZIP_SLOW_CTR
948 bool "ppa/imm option - Assume slow parport control register"
949 depends on SCSI_PPA || SCSI_IMM
951 Some parallel ports are known to have excessive delays between
952 changing the parallel port control register and good data being
953 available on the parallel port data/status register. This option
954 forces a small delay (1.0 usec to be exact) after changing the
955 control register to let things settle out. Enabling this option may
956 result in a big drop in performance but some very old parallel ports
957 (found in 386 vintage machines) will not work properly.
959 Generally, saying N is fine.
961 config SCSI_NCR53C406A
962 tristate "NCR53c406a SCSI support"
963 depends on ISA && SCSI
965 This is support for the NCR53c406a SCSI host adapter. For user
966 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
967 in the kernel source. Also read the SCSI-HOWTO, available from
968 <http://www.tldp.org/docs.html#howto>.
970 To compile this driver as a module, choose M here: the
971 module will be called NCR53c406.
974 tristate "NCR Dual 700 MCA SCSI support"
975 depends on MCA && SCSI
976 select SCSI_SPI_ATTRS
978 This is a driver for the MicroChannel Dual 700 card produced by
979 NCR and commonly used in 345x/35xx/4100 class machines. It always
980 tries to negotiate sync and uses tag command queueing.
982 Unless you have an NCR manufactured machine, the chances are that
983 you do not have this SCSI card, so say N.
986 tristate "HP Lasi SCSI support for 53c700/710"
987 depends on GSC && SCSI
988 select SCSI_SPI_ATTRS
990 This is a driver for the SCSI controller in the Lasi chip found in
991 many PA-RISC workstations & servers. If you do not know whether you
992 have a Lasi chip, it is safe to say "Y" here.
994 config SCSI_SNI_53C710
995 tristate "SNI RM SCSI support for 53c710"
996 depends on SNI_RM && SCSI
997 select SCSI_SPI_ATTRS
998 select 53C700_LE_ON_BE
1000 This is a driver for the onboard SCSI controller found in older
1001 SNI RM workstations & servers.
1003 config 53C700_LE_ON_BE
1005 depends on SCSI_LASI700
1009 tristate "Promise SuperTrak EX Series support"
1010 depends on PCI && SCSI
1012 This driver supports Promise SuperTrak EX series storage controllers.
1014 Promise provides Linux RAID configuration utility for these
1015 controllers. Please visit <http://www.promise.com> to download.
1017 To compile this driver as a module, choose M here: the
1018 module will be called stex.
1020 config 53C700_BE_BUS
1022 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1025 config SCSI_SYM53C8XX_2
1026 tristate "SYM53C8XX Version 2 SCSI support"
1027 depends on PCI && SCSI
1028 select SCSI_SPI_ATTRS
1030 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1031 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1032 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1033 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1034 controllers; you need to use the Fusion MPT driver for that.
1036 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1039 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1040 int "DMA addressing mode"
1041 depends on SCSI_SYM53C8XX_2
1044 This option only applies to PCI-SCSI chips that are PCI DAC
1045 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1047 When set to 0, the driver will program the chip to only perform
1048 32-bit DMA. When set to 1, the chip will be able to perform DMA
1049 to addresses up to 1TB. When set to 2, the driver supports the
1050 full 64-bit DMA address range, but can only address 16 segments
1051 of 4 GB each. This limits the total addressable range to 64 GB.
1053 Most machines with less than 4GB of memory should use a setting
1054 of 0 for best performance. If your machine has 4GB of memory
1055 or more, you should set this option to 1 (the default).
1057 The still experimental value 2 (64 bit DMA addressing with 16
1058 x 4GB segments limitation) can be used on systems that require
1059 PCI address bits past bit 39 to be set for the addressing of
1060 memory using PCI DAC cycles.
1062 config SCSI_SYM53C8XX_DEFAULT_TAGS
1063 int "Default tagged command queue depth"
1064 depends on SCSI_SYM53C8XX_2
1067 This is the default value of the command queue depth the
1068 driver will announce to the generic SCSI layer for devices
1069 that support tagged command queueing. This value can be changed
1070 from the boot command line. This is a soft limit that cannot
1071 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1073 config SCSI_SYM53C8XX_MAX_TAGS
1074 int "Maximum number of queued commands"
1075 depends on SCSI_SYM53C8XX_2
1078 This option allows you to specify the maximum number of commands
1079 that can be queued to any device, when tagged command queuing is
1080 possible. The driver supports up to 256 queued commands per device.
1081 This value is used as a compiled-in hard limit.
1083 config SCSI_SYM53C8XX_MMIO
1084 bool "Use memory mapped IO"
1085 depends on SCSI_SYM53C8XX_2
1088 Memory mapped IO is faster than Port IO. Most people should
1089 answer Y here, but some machines may have problems. If you have
1090 to answer N here, please report the problem to the maintainer.
1093 tristate "IBM Power Linux RAID adapter support"
1094 depends on PCI && SCSI && ATA
1097 This driver supports the IBM Power Linux family RAID adapters.
1098 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1099 as IBM iSeries 5702, 5703, 5709, and 570A.
1101 config SCSI_IPR_TRACE
1102 bool "enable driver internal trace"
1106 If you say Y here, the driver will trace all commands issued
1107 to the adapter. Performance impact is minimal. Trace can be
1108 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1110 config SCSI_IPR_DUMP
1111 bool "enable adapter dump support"
1115 If you say Y here, the driver will support adapter crash dump.
1116 If you enable this support, the iprdump daemon can be used
1117 to capture adapter failure analysis information.
1120 tristate "Zalon SCSI support"
1121 depends on GSC && SCSI
1122 select SCSI_SPI_ATTRS
1124 The Zalon is a GSC/HSC bus interface chip that sits between the
1125 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1126 C110, J200, J210 and some D, K & R-class machines. It's also
1127 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1128 Say Y here if you have one of these machines or cards.
1130 config SCSI_NCR_Q720
1131 tristate "NCR Quad 720 MCA SCSI support"
1132 depends on MCA && SCSI
1133 select SCSI_SPI_ATTRS
1135 This is a driver for the MicroChannel Quad 720 card produced by
1136 NCR and commonly used in 345x/35xx/4100 class machines. It always
1137 tries to negotiate sync and uses tag command queueing.
1139 Unless you have an NCR manufactured machine, the chances are that
1140 you do not have this SCSI card, so say N.
1142 config SCSI_NCR53C8XX_DEFAULT_TAGS
1143 int "default tagged command queue depth"
1144 depends on SCSI_ZALON || SCSI_NCR_Q720
1147 "Tagged command queuing" is a feature of SCSI-2 which improves
1148 performance: the host adapter can send several SCSI commands to a
1149 device's queue even if previous commands haven't finished yet.
1150 Because the device is intelligent, it can optimize its operations
1151 (like head positioning) based on its own request queue. Some SCSI
1152 devices don't implement this properly; if you want to disable this
1153 feature, enter 0 or 1 here (it doesn't matter which).
1155 The default value is 8 and should be supported by most hard disks.
1156 This value can be overridden from the boot command line using the
1157 'tags' option as follows (example):
1158 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1159 4, set queue depth to 16 for target 2 and target 3 on controller 0
1160 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1162 The normal answer therefore is to go with the default 8 and to use
1163 a boot command line option for devices that need to use a different
1164 command queue depth.
1166 There is no safe option other than using good SCSI devices.
1168 config SCSI_NCR53C8XX_MAX_TAGS
1169 int "maximum number of queued commands"
1170 depends on SCSI_ZALON || SCSI_NCR_Q720
1173 This option allows you to specify the maximum number of commands
1174 that can be queued to any device, when tagged command queuing is
1175 possible. The default value is 32. Minimum is 2, maximum is 64.
1176 Modern hard disks are able to support 64 tags and even more, but
1177 do not seem to be faster when more than 32 tags are being used.
1179 So, the normal answer here is to go with the default value 32 unless
1180 you are using very large hard disks with large cache (>= 1 MB) that
1181 are able to take advantage of more than 32 tagged commands.
1183 There is no safe option and the default answer is recommended.
1185 config SCSI_NCR53C8XX_SYNC
1186 int "synchronous transfers frequency in MHz"
1187 depends on SCSI_ZALON || SCSI_NCR_Q720
1190 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1191 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1192 are respectively the maximum data transfer rates in mega-transfers
1193 per second for each class. For example, a FAST-20 Wide 16 device is
1194 able to transfer data at 20 million 16 bit packets per second for a
1195 total rate of 40 MB/s.
1197 You may specify 0 if you want to only use asynchronous data
1198 transfers. This is the safest and slowest option. Otherwise, specify
1199 a value between 5 and 80, depending on the capability of your SCSI
1200 controller. The higher the number, the faster the data transfer.
1201 Note that 80 should normally be ok since the driver decreases the
1202 value automatically according to the controller's capabilities.
1204 Your answer to this question is ignored for controllers with NVRAM,
1205 since the driver will get this information from the user set-up. It
1206 also can be overridden using a boot setup option, as follows
1207 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1208 for FAST-20 synchronous data transfer (20 mega-transfers per
1211 The normal answer therefore is not to go with the default but to
1212 select the maximum value 80 allowing the driver to use the maximum
1213 value supported by each controller. If this causes problems with
1214 your SCSI devices, you should come back and decrease the value.
1216 There is no safe option other than using good cabling, right
1217 terminations and SCSI conformant devices.
1219 config SCSI_NCR53C8XX_NO_DISCONNECT
1220 bool "not allow targets to disconnect"
1221 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1223 This option is only provided for safety if you suspect some SCSI
1224 device of yours to not support properly the target-disconnect
1225 feature. In that case, you would say Y here. In general however, to
1226 not allow targets to disconnect is not reasonable if there is more
1227 than 1 device on a SCSI bus. The normal answer therefore is N.
1230 tristate "PAS16 SCSI support"
1231 depends on ISA && SCSI
1232 select SCSI_SPI_ATTRS
1234 This is support for a SCSI host adapter. It is explained in section
1235 3.10 of the SCSI-HOWTO, available from
1236 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1237 of the box, you may have to change some settings in
1238 <file:drivers/scsi/pas16.h>.
1240 To compile this driver as a module, choose M here: the
1241 module will be called pas16.
1243 config SCSI_QLOGIC_FAS
1244 tristate "Qlogic FAS SCSI support"
1245 depends on ISA && SCSI
1247 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1248 FastSCSI! cards as well as any other card based on the FASXX chip
1249 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1251 This driver does NOT support the PCI versions of these cards. The
1252 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1253 SCSI support"), below.
1255 Information about this driver is contained in
1256 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1257 SCSI-HOWTO, available from
1258 <http://www.tldp.org/docs.html#howto>.
1260 To compile this driver as a module, choose M here: the
1261 module will be called qlogicfas.
1263 config SCSI_QLOGIC_1280
1264 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1265 depends on PCI && SCSI
1267 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1269 To compile this driver as a module, choose M here: the
1270 module will be called qla1280.
1272 config SCSI_QLOGICPTI
1273 tristate "PTI Qlogic, ISP Driver"
1274 depends on SBUS && SCSI
1276 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1277 controllers are known under Solaris as qpti and in the openprom as
1278 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1279 driven by a different driver.
1281 To compile this driver as a module, choose M here: the
1282 module will be called qlogicpti.
1284 source "drivers/scsi/qla2xxx/Kconfig"
1285 source "drivers/scsi/qla4xxx/Kconfig"
1288 tristate "Emulex LightPulse Fibre Channel Support"
1289 depends on PCI && SCSI
1290 depends on SCSI_FC_ATTRS
1293 This lpfc driver supports the Emulex LightPulse
1294 Family of Fibre Channel PCI host adapters.
1296 config SCSI_LPFC_DEBUG_FS
1297 bool "Emulex LightPulse Fibre Channel debugfs Support"
1298 depends on SCSI_LPFC && DEBUG_FS
1300 This makes debugging information from the lpfc driver
1301 available via the debugfs filesystem.
1304 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1305 depends on (EISA || MCA) && SCSI
1306 select SCSI_SPI_ATTRS
1308 This driver is for NCR53c710 based SCSI host adapters.
1310 It currently supports Compaq EISA cards and NCR MCA cards
1312 config SCSI_SYM53C416
1313 tristate "Symbios 53c416 SCSI support"
1314 depends on ISA && SCSI
1316 This is support for the sym53c416 SCSI host adapter, the SCSI
1317 adapter that comes with some HP scanners. This driver requires that
1318 the sym53c416 is configured first using some sort of PnP
1319 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1320 are using isapnp then you need to compile this driver as a module
1321 and then load it using insmod after isapnp has run. The parameters
1322 of the configured card(s) should be passed to the driver. The format
1325 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1327 To compile this driver as a module, choose M here: the
1328 module will be called sym53c416.
1331 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1332 depends on PCI && SCSI
1334 This driver supports PCI SCSI host adapters based on the ASIC
1335 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1337 This driver works, but is still in experimental status. So better
1338 have a bootable disk and a backup in case of emergency.
1340 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1342 To compile this driver as a module, choose M here: the
1343 module will be called dc395x.
1346 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1347 depends on PCI && SCSI
1349 This driver supports PCI SCSI host adapters based on the Am53C974A
1350 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1351 PCscsi/PCnet (Am53/79C974) solutions.
1353 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1355 Note that this driver does NOT support Tekram DC390W/U/F, which are
1356 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1358 To compile this driver as a module, choose M here: the
1359 module will be called tmscsim.
1362 tristate "Trantor T128/T128F/T228 SCSI support"
1363 depends on ISA && SCSI
1364 select SCSI_SPI_ATTRS
1365 select CHECK_SIGNATURE
1367 This is support for a SCSI host adapter. It is explained in section
1368 3.11 of the SCSI-HOWTO, available from
1369 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1370 of the box, you may have to change some settings in
1371 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1372 Adaptec, and some former Trantor products are being sold under the
1375 To compile this driver as a module, choose M here: the
1376 module will be called t128.
1379 tristate "UltraStor 14F/34F support"
1380 depends on ISA && SCSI && ISA_DMA_API
1382 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1383 The source at <file:drivers/scsi/u14-34f.c> contains some
1384 information about this hardware. If the driver doesn't work out of
1385 the box, you may have to change some settings in
1386 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1387 <http://www.tldp.org/docs.html#howto>. Note that there is also
1388 another driver for the same hardware: "UltraStor SCSI support",
1389 below. You should say Y to both only if you want 24F support as
1392 To compile this driver as a module, choose M here: the
1393 module will be called u14-34f.
1395 config SCSI_U14_34F_TAGGED_QUEUE
1396 bool "enable tagged command queueing"
1397 depends on SCSI_U14_34F
1399 This is a feature of SCSI-2 which improves performance: the host
1400 adapter can send several SCSI commands to a device's queue even if
1401 previous commands haven't finished yet.
1402 This is equivalent to the "u14-34f=tc:y" boot option.
1404 config SCSI_U14_34F_LINKED_COMMANDS
1405 bool "enable elevator sorting"
1406 depends on SCSI_U14_34F
1408 This option enables elevator sorting for all probed SCSI disks and
1409 CD-ROMs. It definitely reduces the average seek distance when doing
1410 random seeks, but this does not necessarily result in a noticeable
1411 performance improvement: your mileage may vary...
1412 This is equivalent to the "u14-34f=lc:y" boot option.
1414 config SCSI_U14_34F_MAX_TAGS
1415 int "maximum number of queued commands"
1416 depends on SCSI_U14_34F
1419 This specifies how many SCSI commands can be maximally queued for
1420 each probed SCSI device. You should reduce the default value of 8
1421 only if you have disks with buggy or limited tagged command support.
1422 Minimum is 2 and maximum is 14. This value is also the window size
1423 used by the elevator sorting option above. The effective value used
1424 by the driver for each probed SCSI device is reported at boot time.
1425 This is equivalent to the "u14-34f=mq:8" boot option.
1427 config SCSI_ULTRASTOR
1428 tristate "UltraStor SCSI support"
1429 depends on X86 && ISA && SCSI
1431 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1432 adapter family. This driver is explained in section 3.12 of the
1433 SCSI-HOWTO, available from
1434 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1435 of the box, you may have to change some settings in
1436 <file:drivers/scsi/ultrastor.h>.
1438 Note that there is also another driver for the same hardware:
1439 "UltraStor 14F/34F support", above.
1441 To compile this driver as a module, choose M here: the
1442 module will be called ultrastor.
1445 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1446 depends on PCI && SCSI && !64BIT
1448 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1449 SCSI host adapter. Please read the SCSI-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>.
1452 To compile this driver as a module, choose M here: the
1453 module will be called nsp32.
1456 tristate "SCSI debugging host simulator"
1460 This is a host adapter simulator that can simulate multiple hosts
1461 each with multiple dummy SCSI devices (disks). It defaults to one
1462 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1463 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1464 dummy disks are simulated, they share the same kernel RAM for
1465 their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
1466 information. This driver is primarily of use to those testing the
1467 SCSI and block subsystems. If unsure, say N.
1470 tristate "MESH (Power Mac internal SCSI) support"
1471 depends on PPC32 && PPC_PMAC && SCSI
1473 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1474 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1475 other Power Macintoshes do). Say Y to include support for this SCSI
1478 To compile this driver as a module, choose M here: the
1479 module will be called mesh.
1481 config SCSI_MESH_SYNC_RATE
1482 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1483 depends on SCSI_MESH
1486 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1487 drives a bus which is entirely internal to the machine (such as the
1488 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1489 operation at up to 10 MB/s. On machines where the SCSI bus
1490 controlled by the MESH can have external devices connected, it is
1491 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1492 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1493 to disable synchronous operation.
1495 config SCSI_MESH_RESET_DELAY_MS
1496 int "initial bus reset delay (ms) (0 = no reset)"
1497 depends on SCSI_MESH
1500 config SCSI_MAC53C94
1501 tristate "53C94 (Power Mac external SCSI) support"
1502 depends on PPC32 && PPC_PMAC && SCSI
1504 On Power Macintoshes (and clones) with two SCSI buses, the external
1505 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1506 machines which only have one SCSI bus, such as the 7200, also use
1507 the 53C94. Say Y to include support for the 53C94.
1509 To compile this driver as a module, choose M here: the
1510 module will be called mac53c94.
1512 source "drivers/scsi/arm/Kconfig"
1515 bool "MIPS JAZZ FAS216 SCSI support"
1516 depends on MACH_JAZZ && SCSI
1517 select SCSI_SPI_ATTRS
1519 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1520 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1524 tristate "A3000 WD33C93A support"
1525 depends on AMIGA && SCSI
1527 If you have an Amiga 3000 and have SCSI devices connected to the
1528 built-in SCSI controller, say Y. Otherwise, say N.
1530 To compile this driver as a module, choose M here: the
1531 module will be called a3000.
1534 tristate "A2091/A590 WD33C93A support"
1535 depends on ZORRO && SCSI
1537 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1540 To compile this driver as a module, choose M here: the
1541 module will be called a2091.
1544 tristate "GVP Series II WD33C93A support"
1545 depends on ZORRO && SCSI
1547 If you have a Great Valley Products Series II SCSI controller,
1548 answer Y. Also say Y if you have a later model of GVP SCSI
1549 controller (such as the GVP A4008 or a Combo board). Otherwise,
1550 answer N. This driver does NOT work for the T-Rex series of
1551 accelerators from TekMagic and GVP-M.
1553 To compile this driver as a module, choose M here: the
1554 module will be called gvp11.
1557 tristate "A4000T NCR53c710 SCSI support"
1558 depends on AMIGA && SCSI
1559 select SCSI_SPI_ATTRS
1561 If you have an Amiga 4000T and have SCSI devices connected to the
1562 built-in SCSI controller, say Y. Otherwise, say N.
1564 To compile this driver as a module, choose M here: the
1565 module will be called a4000t.
1567 config SCSI_ZORRO7XX
1568 tristate "Zorro NCR53c710 SCSI support"
1569 depends on ZORRO && SCSI
1570 select SCSI_SPI_ATTRS
1572 Support for various NCR53c710-based SCSI controllers on Zorro
1573 expansion boards for the Amiga.
1575 - the Amiga 4091 Zorro III SCSI-2 controller,
1576 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1578 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1579 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1580 accelerator card for the Amiga 1200,
1581 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1584 tristate "Atari native SCSI support"
1585 depends on ATARI && SCSI
1586 select SCSI_SPI_ATTRS
1589 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1590 Falcon, ...) say Y to get it supported. Of course also, if you have
1591 a compatible SCSI controller (e.g. for Medusa).
1593 To compile this driver as a module, choose M here: the
1594 module will be called atari_scsi.
1596 This driver supports both styles of NCR integration into the
1597 system: the TT style (separate DMA), and the Falcon style (via
1598 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1599 in the Hades (without DMA).
1601 config ATARI_SCSI_TOSHIBA_DELAY
1602 bool "Long delays for Toshiba CD-ROMs"
1603 depends on ATARI_SCSI
1605 This option increases the delay after a SCSI arbitration to
1606 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1607 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1608 would impact performance a bit, so say N.
1610 config ATARI_SCSI_RESET_BOOT
1611 bool "Reset SCSI-devices at boottime"
1612 depends on ATARI_SCSI
1614 Reset the devices on your Atari whenever it boots. This makes the
1615 boot process fractionally longer but may assist recovery from errors
1616 that leave the devices with SCSI operations partway completed.
1619 bool "Macintosh NCR5380 SCSI"
1620 depends on MAC && SCSI=y
1621 select SCSI_SPI_ATTRS
1623 This is the NCR 5380 SCSI controller included on most of the 68030
1624 based Macintoshes. If you have one of these say Y and read the
1625 SCSI-HOWTO, available from
1626 <http://www.tldp.org/docs.html#howto>.
1629 tristate "Macintosh NCR53c9[46] SCSI"
1630 depends on MAC && SCSI
1631 select SCSI_SPI_ATTRS
1633 This is the NCR 53c9x SCSI controller found on most of the 68040
1636 To compile this driver as a module, choose M here: the module
1637 will be called mac_esp.
1640 bool "WD33C93 SCSI driver for MVME147"
1641 depends on MVME147 && SCSI=y
1642 select SCSI_SPI_ATTRS
1644 Support for the on-board SCSI controller on the Motorola MVME147
1645 single-board computer.
1648 tristate "NCR53C710 SCSI driver for MVME16x"
1649 depends on MVME16x && SCSI
1650 select SCSI_SPI_ATTRS
1652 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1653 SCSI controller chip. Almost everyone using one of these boards
1654 will want to say Y to this question.
1656 config BVME6000_SCSI
1657 tristate "NCR53C710 SCSI driver for BVME6000"
1658 depends on BVME6000 && SCSI
1659 select SCSI_SPI_ATTRS
1661 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1662 SCSI controller chip. Almost everyone using one of these boards
1663 will want to say Y to this question.
1666 tristate "Sun3 NCR5380 SCSI"
1667 depends on SUN3 && SCSI
1668 select SCSI_SPI_ATTRS
1670 This option will enable support for the OBIO (onboard io) NCR5380
1671 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1672 "Sun3" type VME scsi controllers also based on the NCR5380.
1673 General Linux information on the Sun 3 series (now discontinued)
1674 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1677 bool "Sun3x ESP SCSI"
1678 depends on SUN3X && SCSI=y
1679 select SCSI_SPI_ATTRS
1681 The ESP was an on-board SCSI controller used on Sun 3/80
1682 machines. Say Y here to compile in support for it.
1685 tristate "Sparc ESP Scsi Driver"
1686 depends on SBUS && SCSI
1687 select SCSI_SPI_ATTRS
1689 This is the driver for the Sun ESP SCSI host adapter. The ESP
1690 chipset is present in most SPARC SBUS-based computers and
1691 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1692 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1694 To compile this driver as a module, choose M here: the
1695 module will be called sun_esp.
1698 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1699 depends on S390 && QDIO && SCSI
1700 depends on SCSI_FC_ATTRS
1702 If you want to access SCSI devices attached to your IBM eServer
1703 zSeries by means of Fibre Channel interfaces say Y.
1704 For details please refer to the documentation provided by IBM at
1705 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1707 This driver is also available as a module. This module will be
1708 called zfcp. If you want to compile it as a module, say M here
1709 and read <file:Documentation/kbuild/modules.txt>.
1712 tristate "PMC SIERRA Linux MaxRAID adapter support"
1713 depends on PCI && SCSI && NET
1715 This driver supports the PMC SIERRA MaxRAID adapters.
1718 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1719 depends on PCI && SCSI
1720 select SCSI_SAS_LIBSAS
1722 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1723 based host adapters.
1726 tristate "Brocade BFA Fibre Channel Support"
1727 depends on PCI && SCSI
1728 depends on SCSI_FC_ATTRS
1730 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1732 To compile this driver as a module, choose M here. The module will
1736 tristate "virtio-scsi support"
1738 select BLK_DEV_INTEGRITY
1740 This is the virtual HBA driver for virtio. If the kernel will
1741 be used in a virtual machine, say Y or M.
1743 source "drivers/scsi/csiostor/Kconfig"
1745 endif # SCSI_LOWLEVEL
1747 source "drivers/scsi/pcmcia/Kconfig"
1749 source "drivers/scsi/device_handler/Kconfig"
1751 source "drivers/scsi/osd/Kconfig"