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 overridden 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"
77 If you want to use SCSI hard disks, Fibre Channel disks,
78 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
79 USB storage or the SCSI or parallel port version of
80 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
81 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
82 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
85 To compile this driver as a module, choose M here and read
86 <file:Documentation/scsi/scsi.txt>.
87 The module will be called sd_mod.
89 Do not compile this driver as a module if your root file system
90 (the one containing the directory /) is located on a SCSI disk.
91 In this case, do not compile the driver for your SCSI host adapter
92 (below) as a module either.
95 tristate "SCSI tape support"
98 If you want to use a SCSI tape drive under Linux, say Y and read the
99 SCSI-HOWTO, available from
100 <http://www.tldp.org/docs.html#howto>, and
101 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
104 To compile this driver as a module, choose M here and read
105 <file:Documentation/scsi/scsi.txt>. The module will be called st.
108 tristate "SCSI OnStream SC-x0 tape support"
111 The OnStream SC-x0 SCSI tape drives cannot be driven by the
112 standard st driver, but instead need this special osst driver and
113 use the /dev/osstX char device nodes (major 206). Via usb-storage,
114 you may be able to drive the USB-x0 and DI-x0 drives as well.
115 Note that there is also a second generation of OnStream
116 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
117 tapes (QIC-157) and can be driven by the standard driver st.
118 For more information, you may have a look at the SCSI-HOWTO
119 <http://www.tldp.org/docs.html#howto> and
120 <file:Documentation/scsi/osst.txt> in the kernel source.
121 More info on the OnStream driver may be found on
122 <http://sourceforge.net/projects/osst/>
123 Please also have a look at the standard st docu, as most of it
124 applies to osst as well.
126 To compile this driver as a module, choose M here and read
127 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
130 tristate "SCSI CDROM support"
133 If you want to use a CD or DVD drive attached to your computer
134 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
135 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
137 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
139 To compile this driver as a module, choose M here and read
140 <file:Documentation/scsi/scsi.txt>.
141 The module will be called sr_mod.
143 config BLK_DEV_SR_VENDOR
144 bool "Enable vendor-specific extensions (for SCSI CDROM)"
145 depends on BLK_DEV_SR
147 This enables the usage of vendor specific SCSI commands. This is
148 required to support multisession CDs with old NEC/TOSHIBA cdrom
149 drives (and HP Writers). If you have such a drive and get the first
150 session only, try saying Y here; everybody else says N.
153 tristate "SCSI generic support"
156 If you want to use SCSI scanners, synthesizers or CD-writers or just
157 about anything having "SCSI" in its name other than hard disks,
158 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
159 directly, so you need some additional software which knows how to
160 talk to these devices using the SCSI protocol:
162 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
163 writer software look at Cdrtools
164 (<http://cdrecord.berlios.de/private/cdrecord.html>)
165 and for burning a "disk at once": CDRDAO
166 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
167 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
168 For other devices, it's possible that you'll have to write the
169 driver software yourself. Please read the file
170 <file:Documentation/scsi/scsi-generic.txt> for more information.
172 To compile this driver as a module, choose M here and read
173 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
178 tristate "SCSI media changer support"
181 This is a driver for SCSI media changers. Most common devices are
182 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
183 don't need this for those tiny 6-slot cdrom changers. Media
184 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
185 If you have such hardware and want to use it with linux, say Y
186 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
188 If you want to compile this as a module ( = code which can be
189 inserted in and removed from the running kernel whenever you want),
190 say M here and read <file:Documentation/kbuild/modules.txt> and
191 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
194 config SCSI_ENCLOSURE
195 tristate "SCSI Enclosure Support"
196 depends on SCSI && ENCLOSURE_SERVICES
198 Enclosures are devices sitting on or in SCSI backplanes that
199 manage devices. If you have a disk cage, the chances are that
200 it has an enclosure device. Selecting this option will just allow
201 certain enclosure conditions to be reported and is not required.
203 config SCSI_CONSTANTS
204 bool "Verbose SCSI error reporting (kernel size +=75K)"
207 The error messages regarding your SCSI hardware will be easier to
208 understand if you say Y here; it will enlarge your kernel by about
209 75 KB. If in doubt, say Y.
212 bool "SCSI logging facility"
215 This turns on a logging facility that can be used to debug a number
216 of SCSI related problems.
218 If you say Y here, no logging output will appear by default, but you
219 can enable logging by saying Y to "/proc file system support" and
220 "Sysctl support" below and executing the command
222 echo <bitmask> > /proc/sys/dev/scsi/logging_level
224 where <bitmask> is a four byte value representing the logging type
225 and logging level for each type of logging selected.
227 There are a number of logging types and you can find them in the
228 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
229 are also described in that file and they determine the verbosity of
230 the logging for each logging type.
232 If you say N here, it may be harder to track down some types of SCSI
233 problems. If you say Y here your kernel will be somewhat larger, but
234 there should be no noticeable performance impact as long as you have
237 config SCSI_SCAN_ASYNC
238 bool "Asynchronous SCSI scanning"
241 The SCSI subsystem can probe for devices while the rest of the
242 system continues booting, and even probe devices on different
243 busses in parallel, leading to a significant speed-up.
245 If you have built SCSI as modules, enabling this option can
246 be a problem as the devices may not have been found by the
247 time your system expects them to have been. You can load the
248 scsi_wait_scan module to ensure that all scans have completed.
249 If you build your SCSI drivers into the kernel, then everything
250 will work fine if you say Y here.
252 You can override this choice by specifying "scsi_mod.scan=sync"
253 or async on the kernel's command line.
255 Note that this setting also affects whether resuming from
256 system suspend will be performed asynchronously.
258 menu "SCSI Transports"
261 config SCSI_SPI_ATTRS
262 tristate "Parallel SCSI (SPI) Transport Attributes"
265 If you wish to export transport-specific information about
266 each attached SCSI device to sysfs, say Y. Otherwise, say N.
269 tristate "FiberChannel Transport Attributes"
270 depends on SCSI && NET
273 If you wish to export transport-specific information about
274 each attached FiberChannel device to sysfs, say Y.
277 config SCSI_ISCSI_ATTRS
278 tristate "iSCSI Transport Attributes"
279 depends on SCSI && NET
280 select BLK_DEV_BSGLIB
282 If you wish to export transport-specific information about
283 each attached iSCSI device to sysfs, say Y.
286 config SCSI_SAS_ATTRS
287 tristate "SAS Transport Attributes"
291 If you wish to export transport-specific information about
292 each attached SAS device to sysfs, say Y.
294 source "drivers/scsi/libsas/Kconfig"
296 config SCSI_SRP_ATTRS
297 tristate "SRP Transport Attributes"
300 If you wish to export transport-specific information about
301 each attached SRP device to sysfs, say Y.
305 menuconfig SCSI_LOWLEVEL
306 bool "SCSI low-level drivers"
310 if SCSI_LOWLEVEL && SCSI
313 tristate "iSCSI Initiator over TCP/IP"
314 depends on SCSI && INET
318 select SCSI_ISCSI_ATTRS
320 The iSCSI Driver provides a host with the ability to access storage
321 through an IP network. The driver uses the iSCSI protocol to transport
322 SCSI requests and responses over a TCP/IP network between the host
323 (the "initiator") and "targets". Architecturally, the iSCSI driver
324 combines with the host's TCP/IP stack, network drivers, and Network
325 Interface Card (NIC) to provide the same functions as a SCSI or a
326 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
328 To compile this driver as a module, choose M here: the
329 module will be called iscsi_tcp.
331 The userspace component needed to initialize the driver, documentation,
332 and sample configuration files can be found here:
334 http://open-iscsi.org
336 config ISCSI_BOOT_SYSFS
337 tristate "iSCSI Boot Sysfs Interface"
340 This option enables support for exposing iSCSI boot information
341 via sysfs to userspace. If you wish to export this information,
342 say Y. Otherwise, say N.
344 source "drivers/scsi/cxgbi/Kconfig"
345 source "drivers/scsi/bnx2i/Kconfig"
346 source "drivers/scsi/bnx2fc/Kconfig"
347 source "drivers/scsi/be2iscsi/Kconfig"
348 source "drivers/scsi/cxlflash/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
374 select SCSI_SAS_ATTRS
376 This driver supports HP Smart Array Controllers (circa 2009).
377 It is a SCSI alternative to the cciss driver, which is a block
378 driver. Anyone wishing to use HP Smart Array controllers who
379 would prefer the devices be presented to linux as SCSI devices,
380 rather than as generic block devices should say Y here.
383 tristate "3ware 9xxx SATA-RAID support"
384 depends on PCI && SCSI
386 This driver supports the 9000 series 3ware SATA-RAID cards.
388 <http://www.amcc.com>
390 Please read the comments at the top of
391 <file:drivers/scsi/3w-9xxx.c>.
394 tristate "3ware 97xx SAS/SATA-RAID support"
395 depends on PCI && SCSI
397 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
401 Please read the comments at the top of
402 <file:drivers/scsi/3w-sas.c>.
404 config SCSI_7000FASST
405 tristate "7000FASST SCSI support"
406 depends on ISA && SCSI && ISA_DMA_API
407 select CHECK_SIGNATURE
409 This driver supports the Western Digital 7000 SCSI host adapter
410 family. Some information is in the source:
411 <file:drivers/scsi/wd7000.c>.
413 To compile this driver as a module, choose M here: the
414 module will be called wd7000.
417 tristate "ACARD SCSI support"
418 depends on PCI && SCSI
420 This driver supports the ACARD SCSI host adapter.
421 Support Chip <ATP870 ATP876 ATP880 ATP885>
422 To compile this driver as a module, choose M here: the
423 module will be called atp870u.
426 tristate "Adaptec AHA152X/2825 support"
427 depends on ISA && SCSI
428 select SCSI_SPI_ATTRS
429 select CHECK_SIGNATURE
431 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
432 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
433 must be manually specified in this case.
435 It is explained in section 3.3 of the SCSI-HOWTO, available from
436 <http://www.tldp.org/docs.html#howto>. You might also want to
437 read the file <file:Documentation/scsi/aha152x.txt>.
439 To compile this driver as a module, choose M here: the
440 module will be called aha152x.
443 tristate "Adaptec AHA1542 support"
444 depends on ISA && SCSI && ISA_DMA_API
446 This is support for a SCSI host adapter. It is explained in section
447 3.4 of the SCSI-HOWTO, available from
448 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
449 purchased by Adaptec, and some former Trantor products are being
450 sold under the Adaptec name. If it doesn't work out of the box, you
451 may have to change some settings in <file:drivers/scsi/aha1542.h>.
453 To compile this driver as a module, choose M here: the
454 module will be called aha1542.
457 tristate "Adaptec AHA1740 support"
458 depends on EISA && SCSI
460 This is support for a SCSI host adapter. It is explained in section
461 3.5 of the SCSI-HOWTO, available from
462 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
463 of the box, you may have to change some settings in
464 <file:drivers/scsi/aha1740.h>.
466 To compile this driver as a module, choose M here: the
467 module will be called aha1740.
470 tristate "Adaptec AACRAID support"
471 depends on SCSI && PCI
473 This driver supports a variety of Dell, HP, Adaptec, IBM and
474 ICP storage products. For a list of supported products, refer
475 to <file:Documentation/scsi/aacraid.txt>.
477 To compile this driver as a module, choose M here: the module
478 will be called aacraid.
481 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
482 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
483 source "drivers/scsi/aic94xx/Kconfig"
484 source "drivers/scsi/mvsas/Kconfig"
487 tristate "Marvell UMI driver"
488 depends on SCSI && PCI
490 Module for Marvell Universal Message Interface(UMI) driver
492 To compile this driver as a module, choose M here: the
493 module will be called mvumi.
496 tristate "Adaptec I2O RAID support "
497 depends on SCSI && PCI && VIRT_TO_BUS
499 This driver supports all of Adaptec's I2O based RAID controllers as
500 well as the DPT SmartRaid V cards. This is an Adaptec maintained
501 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
503 To compile this driver as a module, choose M here: the
504 module will be called dpt_i2o.
507 tristate "AdvanSys SCSI support"
509 depends on ISA || EISA || PCI
510 depends on ISA_DMA_API || !ISA
512 This is a driver for all SCSI host adapters manufactured by
513 AdvanSys. It is documented in the kernel source in
514 <file:drivers/scsi/advansys.c>.
516 To compile this driver as a module, choose M here: the
517 module will be called advansys.
520 tristate "Always IN2000 SCSI support"
521 depends on ISA && SCSI
523 This is support for an ISA bus SCSI host adapter. You'll find more
524 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
525 out of the box, you may have to change the jumpers for IRQ or
528 To compile this driver as a module, choose M here: the
529 module will be called in2000.
532 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
533 depends on PCI && SCSI
535 This driver supports all of ARECA's SATA/SAS RAID controller cards.
536 This is an ARECA-maintained driver by Erich Chen.
537 If you have any problems, please mail to: <erich@areca.com.tw>.
538 Areca supports Linux RAID config tools.
539 Please link <http://www.areca.com.tw>
541 To compile this driver as a module, choose M here: the
542 module will be called arcmsr (modprobe arcmsr).
544 source "drivers/scsi/esas2r/Kconfig"
545 source "drivers/scsi/megaraid/Kconfig.megaraid"
546 source "drivers/scsi/mpt3sas/Kconfig"
547 source "drivers/scsi/ufs/Kconfig"
550 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
551 depends on SCSI && PCI
553 This option enables support for HighPoint RocketRAID 3xxx/4xxx
556 To compile this driver as a module, choose M here; the module
557 will be called hptiop. If unsure, say N.
560 tristate "BusLogic SCSI support"
561 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
563 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
564 Adapters. Consult the SCSI-HOWTO, available from
565 <http://www.tldp.org/docs.html#howto>, and the files
566 <file:Documentation/scsi/BusLogic.txt> and
567 <file:Documentation/scsi/FlashPoint.txt> for more information.
568 Note that support for FlashPoint is only available for 32-bit
571 To compile this driver as a module, choose M here: the
572 module will be called BusLogic.
574 config SCSI_FLASHPOINT
575 bool "FlashPoint support"
576 depends on SCSI_BUSLOGIC && PCI
578 This option allows you to add FlashPoint support to the
579 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
580 substantial, so users of MultiMaster Host Adapters may not
584 tristate "VMware PVSCSI driver support"
585 depends on PCI && SCSI && X86
587 This driver supports VMware's para virtualized SCSI HBA.
588 To compile this driver as a module, choose M here: the
589 module will be called vmw_pvscsi.
591 config XEN_SCSI_FRONTEND
592 tristate "XEN SCSI frontend driver"
593 depends on SCSI && XEN
594 select XEN_XENBUS_FRONTEND
596 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
597 within another guest OS (usually Dom0).
598 Only needed if the kernel is running in a XEN guest and generic
599 SCSI access to a device is needed.
601 config HYPERV_STORAGE
602 tristate "Microsoft Hyper-V virtual storage driver"
603 depends on SCSI && HYPERV
606 Select this option to enable the Hyper-V virtual storage driver.
609 tristate "LibFC module"
610 depends on SCSI_FC_ATTRS
613 Fibre Channel library module
616 tristate "LibFCoE module"
619 Library for Fibre Channel over Ethernet module
622 tristate "FCoE module"
626 Fibre Channel over Ethernet module
629 tristate "Cisco FNIC Driver"
630 depends on PCI && X86
633 This is support for the Cisco PCI-Express FCoE HBA.
635 To compile this driver as a module, choose M here and read
636 <file:Documentation/scsi/scsi.txt>.
637 The module will be called fnic.
640 tristate "Cisco SNIC Driver"
641 depends on PCI && SCSI
643 This is support for the Cisco PCI-Express SCSI HBA.
645 To compile this driver as a module, choose M here and read
646 <file:Documentation/scsi/scsi.txt>.
647 The module will be called snic.
649 config SCSI_SNIC_DEBUG_FS
650 bool "Cisco SNIC Driver Debugfs Support"
651 depends on SCSI_SNIC && DEBUG_FS
653 This enables to list debugging information from SNIC Driver
654 available via debugfs file system
657 tristate "DMX3191D SCSI support"
658 depends on PCI && SCSI
659 select SCSI_SPI_ATTRS
661 This is support for Domex DMX3191D SCSI Host Adapters.
663 To compile this driver as a module, choose M here: the
664 module will be called dmx3191d.
667 tristate "DTC3180/3280 SCSI support"
668 depends on ISA && SCSI
669 select SCSI_SPI_ATTRS
670 select CHECK_SIGNATURE
672 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
673 the SCSI-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>, and the file
675 <file:Documentation/scsi/dtc3x80.txt>.
677 To compile this driver as a module, choose M here: the
678 module will be called dtc.
681 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
682 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
684 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
685 ISA and all EISA I/O addresses are probed looking for the "EATA"
686 signature. The addresses of all the PCI SCSI controllers reported
687 by the PCI subsystem are probed as well.
689 You want to read the start of <file:drivers/scsi/eata.c> and the
690 SCSI-HOWTO, available from
691 <http://www.tldp.org/docs.html#howto>.
693 To compile this driver as a module, choose M here: the
694 module will be called eata.
696 config SCSI_EATA_TAGGED_QUEUE
697 bool "enable tagged command queueing"
700 This is a feature of SCSI-2 which improves performance: the host
701 adapter can send several SCSI commands to a device's queue even if
702 previous commands haven't finished yet.
703 This is equivalent to the "eata=tc:y" boot option.
705 config SCSI_EATA_LINKED_COMMANDS
706 bool "enable elevator sorting"
709 This option enables elevator sorting for all probed SCSI disks and
710 CD-ROMs. It definitely reduces the average seek distance when doing
711 random seeks, but this does not necessarily result in a noticeable
712 performance improvement: your mileage may vary...
713 This is equivalent to the "eata=lc:y" boot option.
715 config SCSI_EATA_MAX_TAGS
716 int "maximum number of queued commands"
720 This specifies how many SCSI commands can be maximally queued for
721 each probed SCSI device. You should reduce the default value of 16
722 only if you have disks with buggy or limited tagged command support.
723 Minimum is 2 and maximum is 62. This value is also the window size
724 used by the elevator sorting option above. The effective value used
725 by the driver for each probed SCSI device is reported at boot time.
726 This is equivalent to the "eata=mq:8" boot option.
729 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
730 depends on (ISA || EISA || PCI) && SCSI && BROKEN
732 This driver supports all EATA-PIO protocol compliant SCSI Host
733 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
734 host adapters could also use this driver but are discouraged from
735 doing so, since this driver only supports hard disks and lacks
736 numerous features. You might want to have a look at the SCSI-HOWTO,
737 available from <http://www.tldp.org/docs.html#howto>.
739 To compile this driver as a module, choose M here: the
740 module will be called eata_pio.
742 config SCSI_FUTURE_DOMAIN
743 tristate "Future Domain 16xx SCSI/AHA-2920A support"
744 depends on (ISA || PCI) && SCSI
745 select CHECK_SIGNATURE
747 This is support for Future Domain's 16-bit SCSI host adapters
748 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
749 other adapters based on the Future Domain chipsets (Quantum
750 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
751 It is explained in section 3.7 of the SCSI-HOWTO, available from
752 <http://www.tldp.org/docs.html#howto>.
754 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
755 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
756 controller support"). This Future Domain driver works with the older
757 Adaptec AHA-2920A boards with a Future Domain chip on them.
759 To compile this driver as a module, choose M here: the
760 module will be called fdomain.
763 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
764 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
766 Formerly called GDT SCSI Disk Array Controller Support.
768 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
769 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
770 in the kernel source in <file:drivers/scsi/gdth.c> and
771 <file:drivers/scsi/gdth.h>.
773 To compile this driver as a module, choose M here: the
774 module will be called gdth.
777 tristate "Intel(R) C600 Series Chipset SAS Controller"
778 depends on PCI && SCSI
780 select SCSI_SAS_LIBSAS
782 This driver supports the 6Gb/s SAS capabilities of the storage
783 control unit found in the Intel(R) C600 series chipset.
785 config SCSI_GENERIC_NCR5380
786 tristate "Generic NCR5380/53c400 SCSI PIO support"
787 depends on ISA && SCSI
788 select SCSI_SPI_ATTRS
790 This is a driver for the old NCR 53c80 series of SCSI controllers
791 on boards using PIO. Most boards such as the Trantor T130 fit this
792 category, along with a large number of ISA 8bit controllers shipped
793 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
794 you should select the specific driver for that card rather than
795 generic 5380 support.
797 It is explained in section 3.8 of the SCSI-HOWTO, available from
798 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
799 of the box, you may have to change some settings in
800 <file:drivers/scsi/g_NCR5380.h>.
802 To compile this driver as a module, choose M here: the
803 module will be called g_NCR5380.
805 config SCSI_GENERIC_NCR5380_MMIO
806 tristate "Generic NCR5380/53c400 SCSI MMIO support"
807 depends on ISA && SCSI
808 select SCSI_SPI_ATTRS
810 This is a driver for the old NCR 53c80 series of SCSI controllers
811 on boards using memory mapped I/O.
812 It is explained in section 3.8 of the SCSI-HOWTO, available from
813 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
814 of the box, you may have to change some settings in
815 <file:drivers/scsi/g_NCR5380.h>.
817 To compile this driver as a module, choose M here: the
818 module will be called g_NCR5380_mmio.
820 config SCSI_GENERIC_NCR53C400
821 bool "Enable NCR53c400 extensions"
822 depends on SCSI_GENERIC_NCR5380
824 This enables certain optimizations for the NCR53c400 SCSI cards.
825 You might as well try it out. Note that this driver will only probe
826 for the Trantor T130B in its default configuration; you might have
827 to pass a command line option to the kernel at boot time if it does
828 not detect your card. See the file
829 <file:Documentation/scsi/g_NCR5380.txt> for details.
832 tristate "IBM ServeRAID support"
833 depends on PCI && SCSI
835 This is support for the IBM ServeRAID hardware RAID controllers.
836 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
837 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
838 for more information. If this driver does not work correctly
839 without modification please contact the author by email at
840 <ipslinux@adaptec.com>.
842 To compile this driver as a module, choose M here: the
843 module will be called ips.
846 tristate "IBM Virtual SCSI support"
847 depends on PPC_PSERIES
848 select SCSI_SRP_ATTRS
850 This is the IBM POWER Virtual SCSI Client
852 To compile this driver as a module, choose M here: the
853 module will be called ibmvscsi.
856 tristate "IBM Virtual FC support"
857 depends on PPC_PSERIES && SCSI
858 depends on SCSI_FC_ATTRS
860 This is the IBM POWER Virtual FC Client
862 To compile this driver as a module, choose M here: the
863 module will be called ibmvfc.
865 config SCSI_IBMVFC_TRACE
866 bool "enable driver internal trace"
867 depends on SCSI_IBMVFC
870 If you say Y here, the driver will trace all commands issued
871 to the adapter. Performance impact is minimal. Trace can be
872 dumped using /sys/class/scsi_host/hostXX/trace.
875 tristate "Initio 9100U(W) support"
876 depends on PCI && SCSI
878 This is support for the Initio 91XXU(W) SCSI host adapter. Please
879 read the SCSI-HOWTO, available from
880 <http://www.tldp.org/docs.html#howto>.
882 To compile this driver as a module, choose M here: the
883 module will be called initio.
886 tristate "Initio INI-A100U2W support"
887 depends on PCI && SCSI
889 This is support for the Initio INI-A100U2W SCSI host adapter.
890 Please read the SCSI-HOWTO, available from
891 <http://www.tldp.org/docs.html#howto>.
893 To compile this driver as a module, choose M here: the
894 module will be called a100u2w.
897 tristate "IOMEGA parallel port (ppa - older drives)"
898 depends on SCSI && PARPORT_PC
900 This driver supports older versions of IOMEGA's parallel port ZIP
901 drive (a 100 MB removable media device).
903 Note that you can say N here if you have the SCSI version of the ZIP
904 drive: it will be supported automatically if you said Y to the
905 generic "SCSI disk support", above.
907 If you have the ZIP Plus drive or a more recent parallel port ZIP
908 drive (if the supplied cable with the drive is labeled "AutoDetect")
909 then you should say N here and Y to "IOMEGA parallel port (imm -
910 newer drives)", below.
912 For more information about this driver and how to use it you should
913 read the file <file:Documentation/scsi/ppa.txt>. You should also read
914 the SCSI-HOWTO, which is available from
915 <http://www.tldp.org/docs.html#howto>. If you use this driver,
916 you will still be able to use the parallel port for other tasks,
917 such as a printer; it is safe to compile both drivers into the
920 To compile this driver as a module, choose M here: the
921 module will be called ppa.
924 tristate "IOMEGA parallel port (imm - newer drives)"
925 depends on SCSI && PARPORT_PC
927 This driver supports newer versions of IOMEGA's parallel port ZIP
928 drive (a 100 MB removable media device).
930 Note that you can say N here if you have the SCSI version of the ZIP
931 drive: it will be supported automatically if you said Y to the
932 generic "SCSI disk support", above.
934 If you have the ZIP Plus drive or a more recent parallel port ZIP
935 drive (if the supplied cable with the drive is labeled "AutoDetect")
936 then you should say Y here; if you have an older ZIP drive, say N
937 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
939 For more information about this driver and how to use it you should
940 read the file <file:Documentation/scsi/ppa.txt>. You should also read
941 the SCSI-HOWTO, which is available from
942 <http://www.tldp.org/docs.html#howto>. If you use this driver,
943 you will still be able to use the parallel port for other tasks,
944 such as a printer; it is safe to compile both drivers into the
947 To compile this driver as a module, choose M here: the
948 module will be called imm.
950 config SCSI_IZIP_EPP16
951 bool "ppa/imm option - Use slow (but safe) EPP-16"
952 depends on SCSI_PPA || SCSI_IMM
954 EPP (Enhanced Parallel Port) is a standard for parallel ports which
955 allows them to act as expansion buses that can handle up to 64
958 Some parallel port chipsets are slower than their motherboard, and
959 so we have to control the state of the chipset's FIFO queue every
960 now and then to avoid data loss. This will be done if you say Y
963 Generally, saying Y is the safe option and slows things down a bit.
965 config SCSI_IZIP_SLOW_CTR
966 bool "ppa/imm option - Assume slow parport control register"
967 depends on SCSI_PPA || SCSI_IMM
969 Some parallel ports are known to have excessive delays between
970 changing the parallel port control register and good data being
971 available on the parallel port data/status register. This option
972 forces a small delay (1.0 usec to be exact) after changing the
973 control register to let things settle out. Enabling this option may
974 result in a big drop in performance but some very old parallel ports
975 (found in 386 vintage machines) will not work properly.
977 Generally, saying N is fine.
979 config SCSI_NCR53C406A
980 tristate "NCR53c406a SCSI support"
981 depends on ISA && SCSI
983 This is support for the NCR53c406a SCSI host adapter. For user
984 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
985 in the kernel source. Also read the SCSI-HOWTO, available from
986 <http://www.tldp.org/docs.html#howto>.
988 To compile this driver as a module, choose M here: the
989 module will be called NCR53c406.
992 tristate "NCR Dual 700 MCA SCSI support"
993 depends on MCA && SCSI
994 select SCSI_SPI_ATTRS
996 This is a driver for the MicroChannel Dual 700 card produced by
997 NCR and commonly used in 345x/35xx/4100 class machines. It always
998 tries to negotiate sync and uses tag command queueing.
1000 Unless you have an NCR manufactured machine, the chances are that
1001 you do not have this SCSI card, so say N.
1004 tristate "HP Lasi SCSI support for 53c700/710"
1005 depends on GSC && SCSI
1006 select SCSI_SPI_ATTRS
1008 This is a driver for the SCSI controller in the Lasi chip found in
1009 many PA-RISC workstations & servers. If you do not know whether you
1010 have a Lasi chip, it is safe to say "Y" here.
1012 config SCSI_SNI_53C710
1013 tristate "SNI RM SCSI support for 53c710"
1014 depends on SNI_RM && SCSI
1015 select SCSI_SPI_ATTRS
1016 select 53C700_LE_ON_BE
1018 This is a driver for the onboard SCSI controller found in older
1019 SNI RM workstations & servers.
1021 config 53C700_LE_ON_BE
1023 depends on SCSI_LASI700
1027 tristate "Promise SuperTrak EX Series support"
1028 depends on PCI && SCSI
1030 This driver supports Promise SuperTrak EX series storage controllers.
1032 Promise provides Linux RAID configuration utility for these
1033 controllers. Please visit <http://www.promise.com> to download.
1035 To compile this driver as a module, choose M here: the
1036 module will be called stex.
1038 config 53C700_BE_BUS
1040 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1043 config SCSI_SYM53C8XX_2
1044 tristate "SYM53C8XX Version 2 SCSI support"
1045 depends on PCI && SCSI
1046 select SCSI_SPI_ATTRS
1048 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1049 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1050 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1051 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1052 controllers; you need to use the Fusion MPT driver for that.
1054 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1057 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1058 int "DMA addressing mode"
1059 depends on SCSI_SYM53C8XX_2
1062 This option only applies to PCI-SCSI chips that are PCI DAC
1063 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1065 When set to 0, the driver will program the chip to only perform
1066 32-bit DMA. When set to 1, the chip will be able to perform DMA
1067 to addresses up to 1TB. When set to 2, the driver supports the
1068 full 64-bit DMA address range, but can only address 16 segments
1069 of 4 GB each. This limits the total addressable range to 64 GB.
1071 Most machines with less than 4GB of memory should use a setting
1072 of 0 for best performance. If your machine has 4GB of memory
1073 or more, you should set this option to 1 (the default).
1075 The still experimental value 2 (64 bit DMA addressing with 16
1076 x 4GB segments limitation) can be used on systems that require
1077 PCI address bits past bit 39 to be set for the addressing of
1078 memory using PCI DAC cycles.
1080 config SCSI_SYM53C8XX_DEFAULT_TAGS
1081 int "Default tagged command queue depth"
1082 depends on SCSI_SYM53C8XX_2
1085 This is the default value of the command queue depth the
1086 driver will announce to the generic SCSI layer for devices
1087 that support tagged command queueing. This value can be changed
1088 from the boot command line. This is a soft limit that cannot
1089 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1091 config SCSI_SYM53C8XX_MAX_TAGS
1092 int "Maximum number of queued commands"
1093 depends on SCSI_SYM53C8XX_2
1096 This option allows you to specify the maximum number of commands
1097 that can be queued to any device, when tagged command queuing is
1098 possible. The driver supports up to 256 queued commands per device.
1099 This value is used as a compiled-in hard limit.
1101 config SCSI_SYM53C8XX_MMIO
1102 bool "Use memory mapped IO"
1103 depends on SCSI_SYM53C8XX_2
1106 Memory mapped IO is faster than Port IO. Most people should
1107 answer Y here, but some machines may have problems. If you have
1108 to answer N here, please report the problem to the maintainer.
1111 tristate "IBM Power Linux RAID adapter support"
1112 depends on PCI && SCSI && ATA
1115 This driver supports the IBM Power Linux family RAID adapters.
1116 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1117 as IBM iSeries 5702, 5703, 5709, and 570A.
1119 config SCSI_IPR_TRACE
1120 bool "enable driver internal trace"
1124 If you say Y here, the driver will trace all commands issued
1125 to the adapter. Performance impact is minimal. Trace can be
1126 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1128 config SCSI_IPR_DUMP
1129 bool "enable adapter dump support"
1133 If you say Y here, the driver will support adapter crash dump.
1134 If you enable this support, the iprdump daemon can be used
1135 to capture adapter failure analysis information.
1138 tristate "Zalon SCSI support"
1139 depends on GSC && SCSI
1140 select SCSI_SPI_ATTRS
1142 The Zalon is a GSC/HSC bus interface chip that sits between the
1143 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1144 C110, J200, J210 and some D, K & R-class machines. It's also
1145 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1146 Say Y here if you have one of these machines or cards.
1148 config SCSI_NCR_Q720
1149 tristate "NCR Quad 720 MCA SCSI support"
1150 depends on MCA && SCSI
1151 select SCSI_SPI_ATTRS
1153 This is a driver for the MicroChannel Quad 720 card produced by
1154 NCR and commonly used in 345x/35xx/4100 class machines. It always
1155 tries to negotiate sync and uses tag command queueing.
1157 Unless you have an NCR manufactured machine, the chances are that
1158 you do not have this SCSI card, so say N.
1160 config SCSI_NCR53C8XX_DEFAULT_TAGS
1161 int "default tagged command queue depth"
1162 depends on SCSI_ZALON || SCSI_NCR_Q720
1165 "Tagged command queuing" is a feature of SCSI-2 which improves
1166 performance: the host adapter can send several SCSI commands to a
1167 device's queue even if previous commands haven't finished yet.
1168 Because the device is intelligent, it can optimize its operations
1169 (like head positioning) based on its own request queue. Some SCSI
1170 devices don't implement this properly; if you want to disable this
1171 feature, enter 0 or 1 here (it doesn't matter which).
1173 The default value is 8 and should be supported by most hard disks.
1174 This value can be overridden from the boot command line using the
1175 'tags' option as follows (example):
1176 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1177 4, set queue depth to 16 for target 2 and target 3 on controller 0
1178 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1180 The normal answer therefore is to go with the default 8 and to use
1181 a boot command line option for devices that need to use a different
1182 command queue depth.
1184 There is no safe option other than using good SCSI devices.
1186 config SCSI_NCR53C8XX_MAX_TAGS
1187 int "maximum number of queued commands"
1188 depends on SCSI_ZALON || SCSI_NCR_Q720
1191 This option allows you to specify the maximum number of commands
1192 that can be queued to any device, when tagged command queuing is
1193 possible. The default value is 32. Minimum is 2, maximum is 64.
1194 Modern hard disks are able to support 64 tags and even more, but
1195 do not seem to be faster when more than 32 tags are being used.
1197 So, the normal answer here is to go with the default value 32 unless
1198 you are using very large hard disks with large cache (>= 1 MB) that
1199 are able to take advantage of more than 32 tagged commands.
1201 There is no safe option and the default answer is recommended.
1203 config SCSI_NCR53C8XX_SYNC
1204 int "synchronous transfers frequency in MHz"
1205 depends on SCSI_ZALON || SCSI_NCR_Q720
1208 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1209 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1210 are respectively the maximum data transfer rates in mega-transfers
1211 per second for each class. For example, a FAST-20 Wide 16 device is
1212 able to transfer data at 20 million 16 bit packets per second for a
1213 total rate of 40 MB/s.
1215 You may specify 0 if you want to only use asynchronous data
1216 transfers. This is the safest and slowest option. Otherwise, specify
1217 a value between 5 and 80, depending on the capability of your SCSI
1218 controller. The higher the number, the faster the data transfer.
1219 Note that 80 should normally be ok since the driver decreases the
1220 value automatically according to the controller's capabilities.
1222 Your answer to this question is ignored for controllers with NVRAM,
1223 since the driver will get this information from the user set-up. It
1224 also can be overridden using a boot setup option, as follows
1225 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1226 for FAST-20 synchronous data transfer (20 mega-transfers per
1229 The normal answer therefore is not to go with the default but to
1230 select the maximum value 80 allowing the driver to use the maximum
1231 value supported by each controller. If this causes problems with
1232 your SCSI devices, you should come back and decrease the value.
1234 There is no safe option other than using good cabling, right
1235 terminations and SCSI conformant devices.
1237 config SCSI_NCR53C8XX_NO_DISCONNECT
1238 bool "not allow targets to disconnect"
1239 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1241 This option is only provided for safety if you suspect some SCSI
1242 device of yours to not support properly the target-disconnect
1243 feature. In that case, you would say Y here. In general however, to
1244 not allow targets to disconnect is not reasonable if there is more
1245 than 1 device on a SCSI bus. The normal answer therefore is N.
1248 tristate "PAS16 SCSI support"
1249 depends on ISA && SCSI
1250 select SCSI_SPI_ATTRS
1252 This is support for a SCSI host adapter. It is explained in section
1253 3.10 of the SCSI-HOWTO, available from
1254 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1255 of the box, you may have to change some settings in
1256 <file:drivers/scsi/pas16.h>.
1258 To compile this driver as a module, choose M here: the
1259 module will be called pas16.
1261 config SCSI_QLOGIC_FAS
1262 tristate "Qlogic FAS SCSI support"
1263 depends on ISA && SCSI
1265 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1266 FastSCSI! cards as well as any other card based on the FASXX chip
1267 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1269 This driver does NOT support the PCI versions of these cards. The
1270 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1271 SCSI support"), below.
1273 Information about this driver is contained in
1274 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1275 SCSI-HOWTO, available from
1276 <http://www.tldp.org/docs.html#howto>.
1278 To compile this driver as a module, choose M here: the
1279 module will be called qlogicfas.
1281 config SCSI_QLOGIC_1280
1282 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1283 depends on PCI && SCSI
1285 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1287 To compile this driver as a module, choose M here: the
1288 module will be called qla1280.
1290 config SCSI_QLOGICPTI
1291 tristate "PTI Qlogic, ISP Driver"
1292 depends on SBUS && SCSI
1294 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1295 controllers are known under Solaris as qpti and in the openprom as
1296 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1297 driven by a different driver.
1299 To compile this driver as a module, choose M here: the
1300 module will be called qlogicpti.
1302 source "drivers/scsi/qla2xxx/Kconfig"
1303 source "drivers/scsi/qla4xxx/Kconfig"
1306 tristate "Emulex LightPulse Fibre Channel Support"
1307 depends on PCI && SCSI
1308 depends on SCSI_FC_ATTRS
1311 This lpfc driver supports the Emulex LightPulse
1312 Family of Fibre Channel PCI host adapters.
1314 config SCSI_LPFC_DEBUG_FS
1315 bool "Emulex LightPulse Fibre Channel debugfs Support"
1316 depends on SCSI_LPFC && DEBUG_FS
1318 This makes debugging information from the lpfc driver
1319 available via the debugfs filesystem.
1322 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1323 depends on (EISA || MCA) && SCSI
1324 select SCSI_SPI_ATTRS
1326 This driver is for NCR53c710 based SCSI host adapters.
1328 It currently supports Compaq EISA cards and NCR MCA cards
1330 config SCSI_SYM53C416
1331 tristate "Symbios 53c416 SCSI support"
1332 depends on ISA && SCSI
1334 This is support for the sym53c416 SCSI host adapter, the SCSI
1335 adapter that comes with some HP scanners. This driver requires that
1336 the sym53c416 is configured first using some sort of PnP
1337 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1338 are using isapnp then you need to compile this driver as a module
1339 and then load it using insmod after isapnp has run. The parameters
1340 of the configured card(s) should be passed to the driver. The format
1343 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1345 To compile this driver as a module, choose M here: the
1346 module will be called sym53c416.
1349 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1350 depends on PCI && SCSI
1352 This driver supports PCI SCSI host adapters based on the ASIC
1353 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1355 This driver works, but is still in experimental status. So better
1356 have a bootable disk and a backup in case of emergency.
1358 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1360 To compile this driver as a module, choose M here: the
1361 module will be called dc395x.
1363 config SCSI_AM53C974
1364 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1365 depends on PCI && SCSI
1366 select SCSI_SPI_ATTRS
1368 This driver supports PCI SCSI host adapters based on the Am53C974A
1369 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1370 PCscsi/PCnet (Am53/79C974) solutions.
1371 This is a new implementation base on the generic esp_scsi driver.
1373 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1375 Note that this driver does NOT support Tekram DC390W/U/F, which are
1376 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1378 To compile this driver as a module, choose M here: the
1379 module will be called am53c974.
1382 tristate "Trantor T128/T128F/T228 SCSI support"
1383 depends on ISA && SCSI
1384 select SCSI_SPI_ATTRS
1385 select CHECK_SIGNATURE
1387 This is support for a SCSI host adapter. It is explained in section
1388 3.11 of the SCSI-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1390 of the box, you may have to change some settings in
1391 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1392 Adaptec, and some former Trantor products are being sold under the
1395 To compile this driver as a module, choose M here: the
1396 module will be called t128.
1399 tristate "UltraStor 14F/34F support"
1400 depends on ISA && SCSI && ISA_DMA_API
1402 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1403 The source at <file:drivers/scsi/u14-34f.c> contains some
1404 information about this hardware. If the driver doesn't work out of
1405 the box, you may have to change some settings in
1406 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1407 <http://www.tldp.org/docs.html#howto>. Note that there is also
1408 another driver for the same hardware: "UltraStor SCSI support",
1409 below. You should say Y to both only if you want 24F support as
1412 To compile this driver as a module, choose M here: the
1413 module will be called u14-34f.
1415 config SCSI_U14_34F_TAGGED_QUEUE
1416 bool "enable tagged command queueing"
1417 depends on SCSI_U14_34F
1419 This is a feature of SCSI-2 which improves performance: the host
1420 adapter can send several SCSI commands to a device's queue even if
1421 previous commands haven't finished yet.
1422 This is equivalent to the "u14-34f=tc:y" boot option.
1424 config SCSI_U14_34F_LINKED_COMMANDS
1425 bool "enable elevator sorting"
1426 depends on SCSI_U14_34F
1428 This option enables elevator sorting for all probed SCSI disks and
1429 CD-ROMs. It definitely reduces the average seek distance when doing
1430 random seeks, but this does not necessarily result in a noticeable
1431 performance improvement: your mileage may vary...
1432 This is equivalent to the "u14-34f=lc:y" boot option.
1434 config SCSI_U14_34F_MAX_TAGS
1435 int "maximum number of queued commands"
1436 depends on SCSI_U14_34F
1439 This specifies how many SCSI commands can be maximally queued for
1440 each probed SCSI device. You should reduce the default value of 8
1441 only if you have disks with buggy or limited tagged command support.
1442 Minimum is 2 and maximum is 14. This value is also the window size
1443 used by the elevator sorting option above. The effective value used
1444 by the driver for each probed SCSI device is reported at boot time.
1445 This is equivalent to the "u14-34f=mq:8" boot option.
1447 config SCSI_ULTRASTOR
1448 tristate "UltraStor SCSI support"
1449 depends on X86 && ISA && SCSI
1451 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1452 adapter family. This driver is explained in section 3.12 of the
1453 SCSI-HOWTO, available from
1454 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1455 of the box, you may have to change some settings in
1456 <file:drivers/scsi/ultrastor.h>.
1458 Note that there is also another driver for the same hardware:
1459 "UltraStor 14F/34F support", above.
1461 To compile this driver as a module, choose M here: the
1462 module will be called ultrastor.
1465 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1466 depends on PCI && SCSI && !64BIT
1468 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1469 SCSI host adapter. Please read the SCSI-HOWTO, available from
1470 <http://www.tldp.org/docs.html#howto>.
1472 To compile this driver as a module, choose M here: the
1473 module will be called nsp32.
1476 tristate "Western Digital WD7193/7197/7296 support"
1477 depends on PCI && SCSI
1480 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1481 SCSI controllers (based on WD33C296A chip).
1484 tristate "SCSI debugging host and device simulator"
1488 This pseudo driver simulates one or more hosts (SCSI initiators),
1489 each with one or more targets, each with one or more logical units.
1490 Defaults to one of each, creating a small RAM disk device. Many
1491 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1492 directory can be tweaked at run time.
1493 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1494 Mainly used for testing and best as a module. If unsure, say N.
1497 tristate "MESH (Power Mac internal SCSI) support"
1498 depends on PPC32 && PPC_PMAC && SCSI
1500 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1501 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1502 other Power Macintoshes do). Say Y to include support for this SCSI
1505 To compile this driver as a module, choose M here: the
1506 module will be called mesh.
1508 config SCSI_MESH_SYNC_RATE
1509 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1510 depends on SCSI_MESH
1513 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1514 drives a bus which is entirely internal to the machine (such as the
1515 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1516 operation at up to 10 MB/s. On machines where the SCSI bus
1517 controlled by the MESH can have external devices connected, it is
1518 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1519 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1520 to disable synchronous operation.
1522 config SCSI_MESH_RESET_DELAY_MS
1523 int "initial bus reset delay (ms) (0 = no reset)"
1524 depends on SCSI_MESH
1527 config SCSI_MAC53C94
1528 tristate "53C94 (Power Mac external SCSI) support"
1529 depends on PPC32 && PPC_PMAC && SCSI
1531 On Power Macintoshes (and clones) with two SCSI buses, the external
1532 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1533 machines which only have one SCSI bus, such as the 7200, also use
1534 the 53C94. Say Y to include support for the 53C94.
1536 To compile this driver as a module, choose M here: the
1537 module will be called mac53c94.
1539 source "drivers/scsi/arm/Kconfig"
1542 bool "MIPS JAZZ FAS216 SCSI support"
1543 depends on MACH_JAZZ && SCSI
1544 select SCSI_SPI_ATTRS
1546 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1547 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1551 tristate "A3000 WD33C93A support"
1552 depends on AMIGA && SCSI
1554 If you have an Amiga 3000 and have SCSI devices connected to the
1555 built-in SCSI controller, say Y. Otherwise, say N.
1557 To compile this driver as a module, choose M here: the
1558 module will be called a3000.
1561 tristate "A2091/A590 WD33C93A support"
1562 depends on ZORRO && SCSI
1564 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1567 To compile this driver as a module, choose M here: the
1568 module will be called a2091.
1571 tristate "GVP Series II WD33C93A support"
1572 depends on ZORRO && SCSI
1574 If you have a Great Valley Products Series II SCSI controller,
1575 answer Y. Also say Y if you have a later model of GVP SCSI
1576 controller (such as the GVP A4008 or a Combo board). Otherwise,
1577 answer N. This driver does NOT work for the T-Rex series of
1578 accelerators from TekMagic and GVP-M.
1580 To compile this driver as a module, choose M here: the
1581 module will be called gvp11.
1584 tristate "A4000T NCR53c710 SCSI support"
1585 depends on AMIGA && SCSI
1586 select SCSI_SPI_ATTRS
1588 If you have an Amiga 4000T and have SCSI devices connected to the
1589 built-in SCSI controller, say Y. Otherwise, say N.
1591 To compile this driver as a module, choose M here: the
1592 module will be called a4000t.
1594 config SCSI_ZORRO7XX
1595 tristate "Zorro NCR53c710 SCSI support"
1596 depends on ZORRO && SCSI
1597 select SCSI_SPI_ATTRS
1599 Support for various NCR53c710-based SCSI controllers on Zorro
1600 expansion boards for the Amiga.
1602 - the Amiga 4091 Zorro III SCSI-2 controller,
1603 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1605 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1606 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1607 accelerator card for the Amiga 1200,
1608 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1611 tristate "Atari native SCSI support"
1612 depends on ATARI && SCSI
1613 select SCSI_SPI_ATTRS
1616 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1617 Falcon, ...) say Y to get it supported. Of course also, if you have
1618 a compatible SCSI controller (e.g. for Medusa).
1620 To compile this driver as a module, choose M here: the
1621 module will be called atari_scsi.
1623 This driver supports both styles of NCR integration into the
1624 system: the TT style (separate DMA), and the Falcon style (via
1625 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1626 in the Hades (without DMA).
1628 config ATARI_SCSI_TOSHIBA_DELAY
1629 bool "Long delays for Toshiba CD-ROMs"
1630 depends on ATARI_SCSI
1632 This option increases the delay after a SCSI arbitration to
1633 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1634 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1635 would impact performance a bit, so say N.
1637 config ATARI_SCSI_RESET_BOOT
1638 bool "Reset SCSI-devices at boottime"
1639 depends on ATARI_SCSI
1641 Reset the devices on your Atari whenever it boots. This makes the
1642 boot process fractionally longer but may assist recovery from errors
1643 that leave the devices with SCSI operations partway completed.
1646 tristate "Macintosh NCR5380 SCSI"
1647 depends on MAC && SCSI=y
1648 select SCSI_SPI_ATTRS
1650 This is the NCR 5380 SCSI controller included on most of the 68030
1651 based Macintoshes. If you have one of these say Y and read the
1652 SCSI-HOWTO, available from
1653 <http://www.tldp.org/docs.html#howto>.
1656 tristate "Macintosh NCR53c9[46] SCSI"
1657 depends on MAC && SCSI
1658 select SCSI_SPI_ATTRS
1660 This is the NCR 53c9x SCSI controller found on most of the 68040
1663 To compile this driver as a module, choose M here: the module
1664 will be called mac_esp.
1667 bool "WD33C93 SCSI driver for MVME147"
1668 depends on MVME147 && SCSI=y
1669 select SCSI_SPI_ATTRS
1671 Support for the on-board SCSI controller on the Motorola MVME147
1672 single-board computer.
1675 tristate "NCR53C710 SCSI driver for MVME16x"
1676 depends on MVME16x && SCSI
1677 select SCSI_SPI_ATTRS
1679 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1680 SCSI controller chip. Almost everyone using one of these boards
1681 will want to say Y to this question.
1683 config BVME6000_SCSI
1684 tristate "NCR53C710 SCSI driver for BVME6000"
1685 depends on BVME6000 && SCSI
1686 select SCSI_SPI_ATTRS
1688 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1689 SCSI controller chip. Almost everyone using one of these boards
1690 will want to say Y to this question.
1693 tristate "Sun3 NCR5380 SCSI"
1694 depends on SUN3 && SCSI
1695 select SCSI_SPI_ATTRS
1697 This option will enable support for the OBIO (onboard io) NCR5380
1698 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1699 "Sun3" type VME scsi controllers also based on the NCR5380.
1700 General Linux information on the Sun 3 series (now discontinued)
1701 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1704 bool "Sun3x ESP SCSI"
1705 depends on SUN3X && SCSI=y
1706 select SCSI_SPI_ATTRS
1708 The ESP was an on-board SCSI controller used on Sun 3/80
1709 machines. Say Y here to compile in support for it.
1712 tristate "Sparc ESP Scsi Driver"
1713 depends on SBUS && SCSI
1714 select SCSI_SPI_ATTRS
1716 This is the driver for the Sun ESP SCSI host adapter. The ESP
1717 chipset is present in most SPARC SBUS-based computers and
1718 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1719 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1721 To compile this driver as a module, choose M here: the
1722 module will be called sun_esp.
1725 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1726 depends on S390 && QDIO && SCSI
1727 depends on SCSI_FC_ATTRS
1729 If you want to access SCSI devices attached to your IBM eServer
1730 zSeries by means of Fibre Channel interfaces say Y.
1731 For details please refer to the documentation provided by IBM at
1732 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1734 This driver is also available as a module. This module will be
1735 called zfcp. If you want to compile it as a module, say M here
1736 and read <file:Documentation/kbuild/modules.txt>.
1739 tristate "PMC SIERRA Linux MaxRAID adapter support"
1740 depends on PCI && SCSI && NET
1742 This driver supports the PMC SIERRA MaxRAID adapters.
1745 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1746 depends on PCI && SCSI
1747 select SCSI_SAS_LIBSAS
1749 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1750 based host adapters.
1753 tristate "Brocade BFA Fibre Channel Support"
1754 depends on PCI && SCSI
1755 depends on SCSI_FC_ATTRS
1757 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1759 To compile this driver as a module, choose M here. The module will
1763 tristate "virtio-scsi support"
1766 This is the virtual HBA driver for virtio. If the kernel will
1767 be used in a virtual machine, say Y or M.
1769 source "drivers/scsi/csiostor/Kconfig"
1771 endif # SCSI_LOWLEVEL
1773 source "drivers/scsi/pcmcia/Kconfig"
1775 source "drivers/scsi/device_handler/Kconfig"
1777 source "drivers/scsi/osd/Kconfig"