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 HYPERV_STORAGE
591 tristate "Microsoft Hyper-V virtual storage driver"
592 depends on SCSI && HYPERV
595 Select this option to enable the Hyper-V virtual storage driver.
598 tristate "LibFC module"
599 depends on SCSI_FC_ATTRS
602 Fibre Channel library module
605 tristate "LibFCoE module"
608 Library for Fibre Channel over Ethernet module
611 tristate "FCoE module"
615 Fibre Channel over Ethernet module
618 tristate "Cisco FNIC Driver"
619 depends on PCI && X86
622 This is support for the Cisco PCI-Express FCoE HBA.
624 To compile this driver as a module, choose M here and read
625 <file:Documentation/scsi/scsi.txt>.
626 The module will be called fnic.
629 tristate "DMX3191D SCSI support"
630 depends on PCI && SCSI
631 select SCSI_SPI_ATTRS
633 This is support for Domex DMX3191D SCSI Host Adapters.
635 To compile this driver as a module, choose M here: the
636 module will be called dmx3191d.
639 tristate "DTC3180/3280 SCSI support"
640 depends on ISA && SCSI
641 select SCSI_SPI_ATTRS
642 select CHECK_SIGNATURE
644 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
645 the SCSI-HOWTO, available from
646 <http://www.tldp.org/docs.html#howto>, and the file
647 <file:Documentation/scsi/dtc3x80.txt>.
649 To compile this driver as a module, choose M here: the
650 module will be called dtc.
653 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
654 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
656 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
657 ISA and all EISA I/O addresses are probed looking for the "EATA"
658 signature. The addresses of all the PCI SCSI controllers reported
659 by the PCI subsystem are probed as well.
661 You want to read the start of <file:drivers/scsi/eata.c> and the
662 SCSI-HOWTO, available from
663 <http://www.tldp.org/docs.html#howto>.
665 To compile this driver as a module, choose M here: the
666 module will be called eata.
668 config SCSI_EATA_TAGGED_QUEUE
669 bool "enable tagged command queueing"
672 This is a feature of SCSI-2 which improves performance: the host
673 adapter can send several SCSI commands to a device's queue even if
674 previous commands haven't finished yet.
675 This is equivalent to the "eata=tc:y" boot option.
677 config SCSI_EATA_LINKED_COMMANDS
678 bool "enable elevator sorting"
681 This option enables elevator sorting for all probed SCSI disks and
682 CD-ROMs. It definitely reduces the average seek distance when doing
683 random seeks, but this does not necessarily result in a noticeable
684 performance improvement: your mileage may vary...
685 This is equivalent to the "eata=lc:y" boot option.
687 config SCSI_EATA_MAX_TAGS
688 int "maximum number of queued commands"
692 This specifies how many SCSI commands can be maximally queued for
693 each probed SCSI device. You should reduce the default value of 16
694 only if you have disks with buggy or limited tagged command support.
695 Minimum is 2 and maximum is 62. This value is also the window size
696 used by the elevator sorting option above. The effective value used
697 by the driver for each probed SCSI device is reported at boot time.
698 This is equivalent to the "eata=mq:8" boot option.
701 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
702 depends on (ISA || EISA || PCI) && SCSI && BROKEN
704 This driver supports all EATA-PIO protocol compliant SCSI Host
705 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
706 host adapters could also use this driver but are discouraged from
707 doing so, since this driver only supports hard disks and lacks
708 numerous features. You might want to have a look at the SCSI-HOWTO,
709 available from <http://www.tldp.org/docs.html#howto>.
711 To compile this driver as a module, choose M here: the
712 module will be called eata_pio.
714 config SCSI_FUTURE_DOMAIN
715 tristate "Future Domain 16xx SCSI/AHA-2920A support"
716 depends on (ISA || PCI) && SCSI
717 select CHECK_SIGNATURE
719 This is support for Future Domain's 16-bit SCSI host adapters
720 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
721 other adapters based on the Future Domain chipsets (Quantum
722 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
723 It is explained in section 3.7 of the SCSI-HOWTO, available from
724 <http://www.tldp.org/docs.html#howto>.
726 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
727 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
728 controller support"). This Future Domain driver works with the older
729 Adaptec AHA-2920A boards with a Future Domain chip on them.
731 To compile this driver as a module, choose M here: the
732 module will be called fdomain.
735 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
736 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
738 Formerly called GDT SCSI Disk Array Controller Support.
740 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
741 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
742 in the kernel source in <file:drivers/scsi/gdth.c> and
743 <file:drivers/scsi/gdth.h>.
745 To compile this driver as a module, choose M here: the
746 module will be called gdth.
749 tristate "Intel(R) C600 Series Chipset SAS Controller"
750 depends on PCI && SCSI
752 select SCSI_SAS_LIBSAS
754 This driver supports the 6Gb/s SAS capabilities of the storage
755 control unit found in the Intel(R) C600 series chipset.
757 config SCSI_GENERIC_NCR5380
758 tristate "Generic NCR5380/53c400 SCSI PIO support"
759 depends on ISA && SCSI
760 select SCSI_SPI_ATTRS
762 This is a driver for the old NCR 53c80 series of SCSI controllers
763 on boards using PIO. Most boards such as the Trantor T130 fit this
764 category, along with a large number of ISA 8bit controllers shipped
765 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
766 you should select the specific driver for that card rather than
767 generic 5380 support.
769 It is explained in section 3.8 of the SCSI-HOWTO, available from
770 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
771 of the box, you may have to change some settings in
772 <file:drivers/scsi/g_NCR5380.h>.
774 To compile this driver as a module, choose M here: the
775 module will be called g_NCR5380.
777 config SCSI_GENERIC_NCR5380_MMIO
778 tristate "Generic NCR5380/53c400 SCSI MMIO support"
779 depends on ISA && SCSI
780 select SCSI_SPI_ATTRS
782 This is a driver for the old NCR 53c80 series of SCSI controllers
783 on boards using memory mapped I/O.
784 It is explained in section 3.8 of the SCSI-HOWTO, available from
785 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
786 of the box, you may have to change some settings in
787 <file:drivers/scsi/g_NCR5380.h>.
789 To compile this driver as a module, choose M here: the
790 module will be called g_NCR5380_mmio.
792 config SCSI_GENERIC_NCR53C400
793 bool "Enable NCR53c400 extensions"
794 depends on SCSI_GENERIC_NCR5380
796 This enables certain optimizations for the NCR53c400 SCSI cards.
797 You might as well try it out. Note that this driver will only probe
798 for the Trantor T130B in its default configuration; you might have
799 to pass a command line option to the kernel at boot time if it does
800 not detect your card. See the file
801 <file:Documentation/scsi/g_NCR5380.txt> for details.
804 tristate "IBM ServeRAID support"
805 depends on PCI && SCSI
807 This is support for the IBM ServeRAID hardware RAID controllers.
808 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
809 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
810 for more information. If this driver does not work correctly
811 without modification please contact the author by email at
812 <ipslinux@adaptec.com>.
814 To compile this driver as a module, choose M here: the
815 module will be called ips.
818 tristate "IBM Virtual SCSI support"
819 depends on PPC_PSERIES
820 select SCSI_SRP_ATTRS
822 This is the IBM POWER Virtual SCSI Client
824 To compile this driver as a module, choose M here: the
825 module will be called ibmvscsi.
828 tristate "IBM Virtual FC support"
829 depends on PPC_PSERIES && SCSI
830 depends on SCSI_FC_ATTRS
832 This is the IBM POWER Virtual FC Client
834 To compile this driver as a module, choose M here: the
835 module will be called ibmvfc.
837 config SCSI_IBMVFC_TRACE
838 bool "enable driver internal trace"
839 depends on SCSI_IBMVFC
842 If you say Y here, the driver will trace all commands issued
843 to the adapter. Performance impact is minimal. Trace can be
844 dumped using /sys/class/scsi_host/hostXX/trace.
847 tristate "Initio 9100U(W) support"
848 depends on PCI && SCSI
850 This is support for the Initio 91XXU(W) SCSI host adapter. Please
851 read the SCSI-HOWTO, available from
852 <http://www.tldp.org/docs.html#howto>.
854 To compile this driver as a module, choose M here: the
855 module will be called initio.
858 tristate "Initio INI-A100U2W support"
859 depends on PCI && SCSI
861 This is support for the Initio INI-A100U2W SCSI host adapter.
862 Please read the SCSI-HOWTO, available from
863 <http://www.tldp.org/docs.html#howto>.
865 To compile this driver as a module, choose M here: the
866 module will be called a100u2w.
869 tristate "IOMEGA parallel port (ppa - older drives)"
870 depends on SCSI && PARPORT_PC
872 This driver supports older versions of IOMEGA's parallel port ZIP
873 drive (a 100 MB removable media device).
875 Note that you can say N here if you have the SCSI version of the ZIP
876 drive: it will be supported automatically if you said Y to the
877 generic "SCSI disk support", above.
879 If you have the ZIP Plus drive or a more recent parallel port ZIP
880 drive (if the supplied cable with the drive is labeled "AutoDetect")
881 then you should say N here and Y to "IOMEGA parallel port (imm -
882 newer drives)", below.
884 For more information about this driver and how to use it you should
885 read the file <file:Documentation/scsi/ppa.txt>. You should also read
886 the SCSI-HOWTO, which is available from
887 <http://www.tldp.org/docs.html#howto>. If you use this driver,
888 you will still be able to use the parallel port for other tasks,
889 such as a printer; it is safe to compile both drivers into the
892 To compile this driver as a module, choose M here: the
893 module will be called ppa.
896 tristate "IOMEGA parallel port (imm - newer drives)"
897 depends on SCSI && PARPORT_PC
899 This driver supports newer versions of IOMEGA's parallel port ZIP
900 drive (a 100 MB removable media device).
902 Note that you can say N here if you have the SCSI version of the ZIP
903 drive: it will be supported automatically if you said Y to the
904 generic "SCSI disk support", above.
906 If you have the ZIP Plus drive or a more recent parallel port ZIP
907 drive (if the supplied cable with the drive is labeled "AutoDetect")
908 then you should say Y here; if you have an older ZIP drive, say N
909 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
911 For more information about this driver and how to use it you should
912 read the file <file:Documentation/scsi/ppa.txt>. You should also read
913 the SCSI-HOWTO, which is available from
914 <http://www.tldp.org/docs.html#howto>. If you use this driver,
915 you will still be able to use the parallel port for other tasks,
916 such as a printer; it is safe to compile both drivers into the
919 To compile this driver as a module, choose M here: the
920 module will be called imm.
922 config SCSI_IZIP_EPP16
923 bool "ppa/imm option - Use slow (but safe) EPP-16"
924 depends on SCSI_PPA || SCSI_IMM
926 EPP (Enhanced Parallel Port) is a standard for parallel ports which
927 allows them to act as expansion buses that can handle up to 64
930 Some parallel port chipsets are slower than their motherboard, and
931 so we have to control the state of the chipset's FIFO queue every
932 now and then to avoid data loss. This will be done if you say Y
935 Generally, saying Y is the safe option and slows things down a bit.
937 config SCSI_IZIP_SLOW_CTR
938 bool "ppa/imm option - Assume slow parport control register"
939 depends on SCSI_PPA || SCSI_IMM
941 Some parallel ports are known to have excessive delays between
942 changing the parallel port control register and good data being
943 available on the parallel port data/status register. This option
944 forces a small delay (1.0 usec to be exact) after changing the
945 control register to let things settle out. Enabling this option may
946 result in a big drop in performance but some very old parallel ports
947 (found in 386 vintage machines) will not work properly.
949 Generally, saying N is fine.
951 config SCSI_NCR53C406A
952 tristate "NCR53c406a SCSI support"
953 depends on ISA && SCSI
955 This is support for the NCR53c406a SCSI host adapter. For user
956 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
957 in the kernel source. Also read the SCSI-HOWTO, available from
958 <http://www.tldp.org/docs.html#howto>.
960 To compile this driver as a module, choose M here: the
961 module will be called NCR53c406.
964 tristate "NCR Dual 700 MCA SCSI support"
965 depends on MCA && SCSI
966 select SCSI_SPI_ATTRS
968 This is a driver for the MicroChannel Dual 700 card produced by
969 NCR and commonly used in 345x/35xx/4100 class machines. It always
970 tries to negotiate sync and uses tag command queueing.
972 Unless you have an NCR manufactured machine, the chances are that
973 you do not have this SCSI card, so say N.
976 tristate "HP Lasi SCSI support for 53c700/710"
977 depends on GSC && SCSI
978 select SCSI_SPI_ATTRS
980 This is a driver for the SCSI controller in the Lasi chip found in
981 many PA-RISC workstations & servers. If you do not know whether you
982 have a Lasi chip, it is safe to say "Y" here.
984 config SCSI_SNI_53C710
985 tristate "SNI RM SCSI support for 53c710"
986 depends on SNI_RM && SCSI
987 select SCSI_SPI_ATTRS
988 select 53C700_LE_ON_BE
990 This is a driver for the onboard SCSI controller found in older
991 SNI RM workstations & servers.
993 config 53C700_LE_ON_BE
995 depends on SCSI_LASI700
999 tristate "Promise SuperTrak EX Series support"
1000 depends on PCI && SCSI
1002 This driver supports Promise SuperTrak EX series storage controllers.
1004 Promise provides Linux RAID configuration utility for these
1005 controllers. Please visit <http://www.promise.com> to download.
1007 To compile this driver as a module, choose M here: the
1008 module will be called stex.
1010 config 53C700_BE_BUS
1012 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1015 config SCSI_SYM53C8XX_2
1016 tristate "SYM53C8XX Version 2 SCSI support"
1017 depends on PCI && SCSI
1018 select SCSI_SPI_ATTRS
1020 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1021 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1022 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1023 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1024 controllers; you need to use the Fusion MPT driver for that.
1026 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1029 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1030 int "DMA addressing mode"
1031 depends on SCSI_SYM53C8XX_2
1034 This option only applies to PCI-SCSI chips that are PCI DAC
1035 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1037 When set to 0, the driver will program the chip to only perform
1038 32-bit DMA. When set to 1, the chip will be able to perform DMA
1039 to addresses up to 1TB. When set to 2, the driver supports the
1040 full 64-bit DMA address range, but can only address 16 segments
1041 of 4 GB each. This limits the total addressable range to 64 GB.
1043 Most machines with less than 4GB of memory should use a setting
1044 of 0 for best performance. If your machine has 4GB of memory
1045 or more, you should set this option to 1 (the default).
1047 The still experimental value 2 (64 bit DMA addressing with 16
1048 x 4GB segments limitation) can be used on systems that require
1049 PCI address bits past bit 39 to be set for the addressing of
1050 memory using PCI DAC cycles.
1052 config SCSI_SYM53C8XX_DEFAULT_TAGS
1053 int "Default tagged command queue depth"
1054 depends on SCSI_SYM53C8XX_2
1057 This is the default value of the command queue depth the
1058 driver will announce to the generic SCSI layer for devices
1059 that support tagged command queueing. This value can be changed
1060 from the boot command line. This is a soft limit that cannot
1061 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1063 config SCSI_SYM53C8XX_MAX_TAGS
1064 int "Maximum number of queued commands"
1065 depends on SCSI_SYM53C8XX_2
1068 This option allows you to specify the maximum number of commands
1069 that can be queued to any device, when tagged command queuing is
1070 possible. The driver supports up to 256 queued commands per device.
1071 This value is used as a compiled-in hard limit.
1073 config SCSI_SYM53C8XX_MMIO
1074 bool "Use memory mapped IO"
1075 depends on SCSI_SYM53C8XX_2
1078 Memory mapped IO is faster than Port IO. Most people should
1079 answer Y here, but some machines may have problems. If you have
1080 to answer N here, please report the problem to the maintainer.
1083 tristate "IBM Power Linux RAID adapter support"
1084 depends on PCI && SCSI && ATA
1087 This driver supports the IBM Power Linux family RAID adapters.
1088 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1089 as IBM iSeries 5702, 5703, 5709, and 570A.
1091 config SCSI_IPR_TRACE
1092 bool "enable driver internal trace"
1096 If you say Y here, the driver will trace all commands issued
1097 to the adapter. Performance impact is minimal. Trace can be
1098 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1100 config SCSI_IPR_DUMP
1101 bool "enable adapter dump support"
1105 If you say Y here, the driver will support adapter crash dump.
1106 If you enable this support, the iprdump daemon can be used
1107 to capture adapter failure analysis information.
1110 tristate "Zalon SCSI support"
1111 depends on GSC && SCSI
1112 select SCSI_SPI_ATTRS
1114 The Zalon is a GSC/HSC bus interface chip that sits between the
1115 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1116 C110, J200, J210 and some D, K & R-class machines. It's also
1117 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1118 Say Y here if you have one of these machines or cards.
1120 config SCSI_NCR_Q720
1121 tristate "NCR Quad 720 MCA SCSI support"
1122 depends on MCA && SCSI
1123 select SCSI_SPI_ATTRS
1125 This is a driver for the MicroChannel Quad 720 card produced by
1126 NCR and commonly used in 345x/35xx/4100 class machines. It always
1127 tries to negotiate sync and uses tag command queueing.
1129 Unless you have an NCR manufactured machine, the chances are that
1130 you do not have this SCSI card, so say N.
1132 config SCSI_NCR53C8XX_DEFAULT_TAGS
1133 int "default tagged command queue depth"
1134 depends on SCSI_ZALON || SCSI_NCR_Q720
1137 "Tagged command queuing" is a feature of SCSI-2 which improves
1138 performance: the host adapter can send several SCSI commands to a
1139 device's queue even if previous commands haven't finished yet.
1140 Because the device is intelligent, it can optimize its operations
1141 (like head positioning) based on its own request queue. Some SCSI
1142 devices don't implement this properly; if you want to disable this
1143 feature, enter 0 or 1 here (it doesn't matter which).
1145 The default value is 8 and should be supported by most hard disks.
1146 This value can be overridden from the boot command line using the
1147 'tags' option as follows (example):
1148 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1149 4, set queue depth to 16 for target 2 and target 3 on controller 0
1150 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1152 The normal answer therefore is to go with the default 8 and to use
1153 a boot command line option for devices that need to use a different
1154 command queue depth.
1156 There is no safe option other than using good SCSI devices.
1158 config SCSI_NCR53C8XX_MAX_TAGS
1159 int "maximum number of queued commands"
1160 depends on SCSI_ZALON || SCSI_NCR_Q720
1163 This option allows you to specify the maximum number of commands
1164 that can be queued to any device, when tagged command queuing is
1165 possible. The default value is 32. Minimum is 2, maximum is 64.
1166 Modern hard disks are able to support 64 tags and even more, but
1167 do not seem to be faster when more than 32 tags are being used.
1169 So, the normal answer here is to go with the default value 32 unless
1170 you are using very large hard disks with large cache (>= 1 MB) that
1171 are able to take advantage of more than 32 tagged commands.
1173 There is no safe option and the default answer is recommended.
1175 config SCSI_NCR53C8XX_SYNC
1176 int "synchronous transfers frequency in MHz"
1177 depends on SCSI_ZALON || SCSI_NCR_Q720
1180 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1181 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1182 are respectively the maximum data transfer rates in mega-transfers
1183 per second for each class. For example, a FAST-20 Wide 16 device is
1184 able to transfer data at 20 million 16 bit packets per second for a
1185 total rate of 40 MB/s.
1187 You may specify 0 if you want to only use asynchronous data
1188 transfers. This is the safest and slowest option. Otherwise, specify
1189 a value between 5 and 80, depending on the capability of your SCSI
1190 controller. The higher the number, the faster the data transfer.
1191 Note that 80 should normally be ok since the driver decreases the
1192 value automatically according to the controller's capabilities.
1194 Your answer to this question is ignored for controllers with NVRAM,
1195 since the driver will get this information from the user set-up. It
1196 also can be overridden using a boot setup option, as follows
1197 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1198 for FAST-20 synchronous data transfer (20 mega-transfers per
1201 The normal answer therefore is not to go with the default but to
1202 select the maximum value 80 allowing the driver to use the maximum
1203 value supported by each controller. If this causes problems with
1204 your SCSI devices, you should come back and decrease the value.
1206 There is no safe option other than using good cabling, right
1207 terminations and SCSI conformant devices.
1209 config SCSI_NCR53C8XX_NO_DISCONNECT
1210 bool "not allow targets to disconnect"
1211 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1213 This option is only provided for safety if you suspect some SCSI
1214 device of yours to not support properly the target-disconnect
1215 feature. In that case, you would say Y here. In general however, to
1216 not allow targets to disconnect is not reasonable if there is more
1217 than 1 device on a SCSI bus. The normal answer therefore is N.
1220 tristate "PAS16 SCSI support"
1221 depends on ISA && SCSI
1222 select SCSI_SPI_ATTRS
1224 This is support for a SCSI host adapter. It is explained in section
1225 3.10 of the SCSI-HOWTO, available from
1226 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1227 of the box, you may have to change some settings in
1228 <file:drivers/scsi/pas16.h>.
1230 To compile this driver as a module, choose M here: the
1231 module will be called pas16.
1233 config SCSI_QLOGIC_FAS
1234 tristate "Qlogic FAS SCSI support"
1235 depends on ISA && SCSI
1237 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1238 FastSCSI! cards as well as any other card based on the FASXX chip
1239 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1241 This driver does NOT support the PCI versions of these cards. The
1242 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1243 SCSI support"), below.
1245 Information about this driver is contained in
1246 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1247 SCSI-HOWTO, available from
1248 <http://www.tldp.org/docs.html#howto>.
1250 To compile this driver as a module, choose M here: the
1251 module will be called qlogicfas.
1253 config SCSI_QLOGIC_1280
1254 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1255 depends on PCI && SCSI
1257 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1259 To compile this driver as a module, choose M here: the
1260 module will be called qla1280.
1262 config SCSI_QLOGICPTI
1263 tristate "PTI Qlogic, ISP Driver"
1264 depends on SBUS && SCSI
1266 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1267 controllers are known under Solaris as qpti and in the openprom as
1268 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1269 driven by a different driver.
1271 To compile this driver as a module, choose M here: the
1272 module will be called qlogicpti.
1274 source "drivers/scsi/qla2xxx/Kconfig"
1275 source "drivers/scsi/qla4xxx/Kconfig"
1278 tristate "Emulex LightPulse Fibre Channel Support"
1279 depends on PCI && SCSI
1280 depends on SCSI_FC_ATTRS
1283 This lpfc driver supports the Emulex LightPulse
1284 Family of Fibre Channel PCI host adapters.
1286 config SCSI_LPFC_DEBUG_FS
1287 bool "Emulex LightPulse Fibre Channel debugfs Support"
1288 depends on SCSI_LPFC && DEBUG_FS
1290 This makes debugging information from the lpfc driver
1291 available via the debugfs filesystem.
1294 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1295 depends on (EISA || MCA) && SCSI
1296 select SCSI_SPI_ATTRS
1298 This driver is for NCR53c710 based SCSI host adapters.
1300 It currently supports Compaq EISA cards and NCR MCA cards
1302 config SCSI_SYM53C416
1303 tristate "Symbios 53c416 SCSI support"
1304 depends on ISA && SCSI
1306 This is support for the sym53c416 SCSI host adapter, the SCSI
1307 adapter that comes with some HP scanners. This driver requires that
1308 the sym53c416 is configured first using some sort of PnP
1309 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1310 are using isapnp then you need to compile this driver as a module
1311 and then load it using insmod after isapnp has run. The parameters
1312 of the configured card(s) should be passed to the driver. The format
1315 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1317 To compile this driver as a module, choose M here: the
1318 module will be called sym53c416.
1321 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1322 depends on PCI && SCSI
1324 This driver supports PCI SCSI host adapters based on the ASIC
1325 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1327 This driver works, but is still in experimental status. So better
1328 have a bootable disk and a backup in case of emergency.
1330 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1332 To compile this driver as a module, choose M here: the
1333 module will be called dc395x.
1336 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1337 depends on PCI && SCSI
1339 This driver supports PCI SCSI host adapters based on the Am53C974A
1340 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1341 PCscsi/PCnet (Am53/79C974) solutions.
1343 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1345 Note that this driver does NOT support Tekram DC390W/U/F, which are
1346 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1348 To compile this driver as a module, choose M here: the
1349 module will be called tmscsim.
1352 tristate "Trantor T128/T128F/T228 SCSI support"
1353 depends on ISA && SCSI
1354 select SCSI_SPI_ATTRS
1355 select CHECK_SIGNATURE
1357 This is support for a SCSI host adapter. It is explained in section
1358 3.11 of the SCSI-HOWTO, available from
1359 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1360 of the box, you may have to change some settings in
1361 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1362 Adaptec, and some former Trantor products are being sold under the
1365 To compile this driver as a module, choose M here: the
1366 module will be called t128.
1369 tristate "UltraStor 14F/34F support"
1370 depends on ISA && SCSI && ISA_DMA_API
1372 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1373 The source at <file:drivers/scsi/u14-34f.c> contains some
1374 information about this hardware. If the driver doesn't work out of
1375 the box, you may have to change some settings in
1376 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1377 <http://www.tldp.org/docs.html#howto>. Note that there is also
1378 another driver for the same hardware: "UltraStor SCSI support",
1379 below. You should say Y to both only if you want 24F support as
1382 To compile this driver as a module, choose M here: the
1383 module will be called u14-34f.
1385 config SCSI_U14_34F_TAGGED_QUEUE
1386 bool "enable tagged command queueing"
1387 depends on SCSI_U14_34F
1389 This is a feature of SCSI-2 which improves performance: the host
1390 adapter can send several SCSI commands to a device's queue even if
1391 previous commands haven't finished yet.
1392 This is equivalent to the "u14-34f=tc:y" boot option.
1394 config SCSI_U14_34F_LINKED_COMMANDS
1395 bool "enable elevator sorting"
1396 depends on SCSI_U14_34F
1398 This option enables elevator sorting for all probed SCSI disks and
1399 CD-ROMs. It definitely reduces the average seek distance when doing
1400 random seeks, but this does not necessarily result in a noticeable
1401 performance improvement: your mileage may vary...
1402 This is equivalent to the "u14-34f=lc:y" boot option.
1404 config SCSI_U14_34F_MAX_TAGS
1405 int "maximum number of queued commands"
1406 depends on SCSI_U14_34F
1409 This specifies how many SCSI commands can be maximally queued for
1410 each probed SCSI device. You should reduce the default value of 8
1411 only if you have disks with buggy or limited tagged command support.
1412 Minimum is 2 and maximum is 14. This value is also the window size
1413 used by the elevator sorting option above. The effective value used
1414 by the driver for each probed SCSI device is reported at boot time.
1415 This is equivalent to the "u14-34f=mq:8" boot option.
1417 config SCSI_ULTRASTOR
1418 tristate "UltraStor SCSI support"
1419 depends on X86 && ISA && SCSI
1421 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1422 adapter family. This driver is explained in section 3.12 of the
1423 SCSI-HOWTO, available from
1424 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1425 of the box, you may have to change some settings in
1426 <file:drivers/scsi/ultrastor.h>.
1428 Note that there is also another driver for the same hardware:
1429 "UltraStor 14F/34F support", above.
1431 To compile this driver as a module, choose M here: the
1432 module will be called ultrastor.
1435 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1436 depends on PCI && SCSI && !64BIT
1438 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1439 SCSI host adapter. Please read the SCSI-HOWTO, available from
1440 <http://www.tldp.org/docs.html#howto>.
1442 To compile this driver as a module, choose M here: the
1443 module will be called nsp32.
1446 tristate "SCSI debugging host simulator"
1450 This is a host adapter simulator that can simulate multiple hosts
1451 each with multiple dummy SCSI devices (disks). It defaults to one
1452 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1453 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1454 dummy disks are simulated, they share the same kernel RAM for
1455 their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
1456 information. This driver is primarily of use to those testing the
1457 SCSI and block subsystems. If unsure, say N.
1460 tristate "MESH (Power Mac internal SCSI) support"
1461 depends on PPC32 && PPC_PMAC && SCSI
1463 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1464 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1465 other Power Macintoshes do). Say Y to include support for this SCSI
1468 To compile this driver as a module, choose M here: the
1469 module will be called mesh.
1471 config SCSI_MESH_SYNC_RATE
1472 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1473 depends on SCSI_MESH
1476 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1477 drives a bus which is entirely internal to the machine (such as the
1478 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1479 operation at up to 10 MB/s. On machines where the SCSI bus
1480 controlled by the MESH can have external devices connected, it is
1481 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1482 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1483 to disable synchronous operation.
1485 config SCSI_MESH_RESET_DELAY_MS
1486 int "initial bus reset delay (ms) (0 = no reset)"
1487 depends on SCSI_MESH
1490 config SCSI_MAC53C94
1491 tristate "53C94 (Power Mac external SCSI) support"
1492 depends on PPC32 && PPC_PMAC && SCSI
1494 On Power Macintoshes (and clones) with two SCSI buses, the external
1495 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1496 machines which only have one SCSI bus, such as the 7200, also use
1497 the 53C94. Say Y to include support for the 53C94.
1499 To compile this driver as a module, choose M here: the
1500 module will be called mac53c94.
1502 source "drivers/scsi/arm/Kconfig"
1505 bool "MIPS JAZZ FAS216 SCSI support"
1506 depends on MACH_JAZZ && SCSI
1507 select SCSI_SPI_ATTRS
1509 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1510 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1514 tristate "A3000 WD33C93A support"
1515 depends on AMIGA && SCSI
1517 If you have an Amiga 3000 and have SCSI devices connected to the
1518 built-in SCSI controller, say Y. Otherwise, say N.
1520 To compile this driver as a module, choose M here: the
1521 module will be called a3000.
1524 tristate "A2091/A590 WD33C93A support"
1525 depends on ZORRO && SCSI
1527 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1530 To compile this driver as a module, choose M here: the
1531 module will be called a2091.
1534 tristate "GVP Series II WD33C93A support"
1535 depends on ZORRO && SCSI
1537 If you have a Great Valley Products Series II SCSI controller,
1538 answer Y. Also say Y if you have a later model of GVP SCSI
1539 controller (such as the GVP A4008 or a Combo board). Otherwise,
1540 answer N. This driver does NOT work for the T-Rex series of
1541 accelerators from TekMagic and GVP-M.
1543 To compile this driver as a module, choose M here: the
1544 module will be called gvp11.
1547 tristate "A4000T NCR53c710 SCSI support"
1548 depends on AMIGA && SCSI
1549 select SCSI_SPI_ATTRS
1551 If you have an Amiga 4000T and have SCSI devices connected to the
1552 built-in SCSI controller, say Y. Otherwise, say N.
1554 To compile this driver as a module, choose M here: the
1555 module will be called a4000t.
1557 config SCSI_ZORRO7XX
1558 tristate "Zorro NCR53c710 SCSI support"
1559 depends on ZORRO && SCSI
1560 select SCSI_SPI_ATTRS
1562 Support for various NCR53c710-based SCSI controllers on Zorro
1563 expansion boards for the Amiga.
1565 - the Amiga 4091 Zorro III SCSI-2 controller,
1566 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1568 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1569 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1570 accelerator card for the Amiga 1200,
1571 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1574 tristate "Atari native SCSI support"
1575 depends on ATARI && SCSI
1576 select SCSI_SPI_ATTRS
1579 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1580 Falcon, ...) say Y to get it supported. Of course also, if you have
1581 a compatible SCSI controller (e.g. for Medusa).
1583 To compile this driver as a module, choose M here: the
1584 module will be called atari_scsi.
1586 This driver supports both styles of NCR integration into the
1587 system: the TT style (separate DMA), and the Falcon style (via
1588 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1589 in the Hades (without DMA).
1591 config ATARI_SCSI_TOSHIBA_DELAY
1592 bool "Long delays for Toshiba CD-ROMs"
1593 depends on ATARI_SCSI
1595 This option increases the delay after a SCSI arbitration to
1596 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1597 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1598 would impact performance a bit, so say N.
1600 config ATARI_SCSI_RESET_BOOT
1601 bool "Reset SCSI-devices at boottime"
1602 depends on ATARI_SCSI
1604 Reset the devices on your Atari whenever it boots. This makes the
1605 boot process fractionally longer but may assist recovery from errors
1606 that leave the devices with SCSI operations partway completed.
1609 bool "Macintosh NCR5380 SCSI"
1610 depends on MAC && SCSI=y
1611 select SCSI_SPI_ATTRS
1613 This is the NCR 5380 SCSI controller included on most of the 68030
1614 based Macintoshes. If you have one of these say Y and read the
1615 SCSI-HOWTO, available from
1616 <http://www.tldp.org/docs.html#howto>.
1619 tristate "Macintosh NCR53c9[46] SCSI"
1620 depends on MAC && SCSI
1621 select SCSI_SPI_ATTRS
1623 This is the NCR 53c9x SCSI controller found on most of the 68040
1626 To compile this driver as a module, choose M here: the module
1627 will be called mac_esp.
1630 bool "WD33C93 SCSI driver for MVME147"
1631 depends on MVME147 && SCSI=y
1632 select SCSI_SPI_ATTRS
1634 Support for the on-board SCSI controller on the Motorola MVME147
1635 single-board computer.
1638 tristate "NCR53C710 SCSI driver for MVME16x"
1639 depends on MVME16x && SCSI
1640 select SCSI_SPI_ATTRS
1642 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1643 SCSI controller chip. Almost everyone using one of these boards
1644 will want to say Y to this question.
1646 config BVME6000_SCSI
1647 tristate "NCR53C710 SCSI driver for BVME6000"
1648 depends on BVME6000 && SCSI
1649 select SCSI_SPI_ATTRS
1651 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1652 SCSI controller chip. Almost everyone using one of these boards
1653 will want to say Y to this question.
1656 tristate "Sun3 NCR5380 SCSI"
1657 depends on SUN3 && SCSI
1658 select SCSI_SPI_ATTRS
1660 This option will enable support for the OBIO (onboard io) NCR5380
1661 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1662 "Sun3" type VME scsi controllers also based on the NCR5380.
1663 General Linux information on the Sun 3 series (now discontinued)
1664 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1667 bool "Sun3x ESP SCSI"
1668 depends on SUN3X && SCSI=y
1669 select SCSI_SPI_ATTRS
1671 The ESP was an on-board SCSI controller used on Sun 3/80
1672 machines. Say Y here to compile in support for it.
1675 tristate "Sparc ESP Scsi Driver"
1676 depends on SBUS && SCSI
1677 select SCSI_SPI_ATTRS
1679 This is the driver for the Sun ESP SCSI host adapter. The ESP
1680 chipset is present in most SPARC SBUS-based computers and
1681 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1682 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1684 To compile this driver as a module, choose M here: the
1685 module will be called sun_esp.
1688 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1689 depends on S390 && QDIO && SCSI
1690 depends on SCSI_FC_ATTRS
1692 If you want to access SCSI devices attached to your IBM eServer
1693 zSeries by means of Fibre Channel interfaces say Y.
1694 For details please refer to the documentation provided by IBM at
1695 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1697 This driver is also available as a module. This module will be
1698 called zfcp. If you want to compile it as a module, say M here
1699 and read <file:Documentation/kbuild/modules.txt>.
1702 tristate "PMC SIERRA Linux MaxRAID adapter support"
1703 depends on PCI && SCSI && NET
1705 This driver supports the PMC SIERRA MaxRAID adapters.
1708 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1709 depends on PCI && SCSI
1710 select SCSI_SAS_LIBSAS
1712 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1713 based host adapters.
1716 tristate "Brocade BFA Fibre Channel Support"
1717 depends on PCI && SCSI
1718 depends on SCSI_FC_ATTRS
1720 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1722 To compile this driver as a module, choose M here. The module will
1726 tristate "virtio-scsi support"
1728 select BLK_DEV_INTEGRITY
1730 This is the virtual HBA driver for virtio. If the kernel will
1731 be used in a virtual machine, say Y or M.
1733 source "drivers/scsi/csiostor/Kconfig"
1735 endif # SCSI_LOWLEVEL
1737 source "drivers/scsi/pcmcia/Kconfig"
1739 source "drivers/scsi/device_handler/Kconfig"
1741 source "drivers/scsi/osd/Kconfig"