1 menu "SCSI device support"
4 tristate "RAID Transport Class"
10 tristate "SCSI device support"
12 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
13 any other SCSI device under Linux, say Y and make sure that you know
14 the name of your SCSI host adapter (the card inside your computer
15 that "speaks" the SCSI protocol, also called SCSI controller),
16 because you will be asked for it.
18 You also need to say Y here if you have a device which speaks
19 the SCSI protocol. Examples of this include the parallel port
20 version of the IOMEGA ZIP drive, USB storage devices, Fibre
21 Channel, FireWire storage and the IDE-SCSI emulation driver.
23 To compile this driver as a module, choose M here and read
24 <file:Documentation/scsi/scsi.txt>.
25 The module will be called scsi_mod.
27 However, do not compile this as a module if your root file system
28 (the one containing the directory /) is located on a SCSI device.
31 bool "legacy /proc/scsi/ support"
32 depends on SCSI && PROC_FS
35 This option enables support for the various files in
36 /proc/scsi. In Linux 2.6 this has been superceeded by
37 files in sysfs but many legacy applications rely on this.
41 comment "SCSI support type (disk, tape, CD-ROM)"
45 tristate "SCSI disk support"
48 If you want to use SCSI hard disks, Fibre Channel disks,
49 USB storage or the SCSI or parallel port version of
50 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
51 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
52 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
55 To compile this driver as a module, choose M here and read
56 <file:Documentation/scsi/scsi.txt>.
57 The module will be called sd_mod.
59 Do not compile this driver as a module if your root file system
60 (the one containing the directory /) is located on a SCSI disk.
61 In this case, do not compile the driver for your SCSI host adapter
62 (below) as a module either.
65 tristate "SCSI tape support"
68 If you want to use a SCSI tape drive under Linux, say Y and read the
69 SCSI-HOWTO, available from
70 <http://www.tldp.org/docs.html#howto>, and
71 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
74 To compile this driver as a module, choose M here and read
75 <file:Documentation/scsi/scsi.txt>. The module will be called st.
78 tristate "SCSI OnStream SC-x0 tape support"
81 The OnStream SC-x0 SCSI tape drives can not be driven by the
82 standard st driver, but instead need this special osst driver and
83 use the /dev/osstX char device nodes (major 206). Via usb-storage
84 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
85 as well. Note that there is also a second generation of OnStream
86 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
87 tapes (QIC-157) and can be driven by the standard driver st.
88 For more information, you may have a look at the SCSI-HOWTO
89 <http://www.tldp.org/docs.html#howto> and
90 <file:Documentation/scsi/osst.txt> in the kernel source.
91 More info on the OnStream driver may be found on
92 <http://linux1.onstream.nl/test/>
93 Please also have a look at the standard st docu, as most of it
94 applies to osst as well.
96 To compile this driver as a module, choose M here and read
97 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
100 tristate "SCSI CDROM support"
103 If you want to use a SCSI or FireWire CD-ROM under Linux,
104 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
105 <http://www.tldp.org/docs.html#howto>. Also make sure to say
106 Y or M to "ISO 9660 CD-ROM file system support" later.
108 To compile this driver as a module, choose M here and read
109 <file:Documentation/scsi/scsi.txt>.
110 The module will be called sr_mod.
112 config BLK_DEV_SR_VENDOR
113 bool "Enable vendor-specific extensions (for SCSI CDROM)"
114 depends on BLK_DEV_SR
116 This enables the usage of vendor specific SCSI commands. This is
117 required to support multisession CDs with old NEC/TOSHIBA cdrom
118 drives (and HP Writers). If you have such a drive and get the first
119 session only, try saying Y here; everybody else says N.
122 tristate "SCSI generic support"
125 If you want to use SCSI scanners, synthesizers or CD-writers or just
126 about anything having "SCSI" in its name other than hard disks,
127 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
128 directly, so you need some additional software which knows how to
129 talk to these devices using the SCSI protocol:
131 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
132 writer software look at Cdrtools
133 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
134 and for burning a "disk at once": CDRDAO
135 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
136 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
137 For other devices, it's possible that you'll have to write the
138 driver software yourself. Please read the file
139 <file:Documentation/scsi/scsi-generic.txt> for more information.
141 To compile this driver as a module, choose M here and read
142 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
147 tristate "SCSI media changer support"
150 This is a driver for SCSI media changers. Most common devices are
151 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
152 don't need this for those tiny 6-slot cdrom changers. Media
153 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
154 If you have such hardware and want to use it with linux, say Y
155 here. Check <file:Documentation/scsi-changer.txt> for details.
157 If you want to compile this as a module ( = code which can be
158 inserted in and removed from the running kernel whenever you want),
159 say M here and read <file:Documentation/modules.txt> and
160 <file:Documentation/scsi.txt>. The module will be called ch.o.
164 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
167 config SCSI_MULTI_LUN
168 bool "Probe all LUNs on each SCSI device"
171 If you have a SCSI device that supports more than one LUN (Logical
172 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
173 can say Y here to force the SCSI driver to probe for multiple LUNs.
174 A SCSI device with multiple LUNs acts logically like multiple SCSI
175 devices. The vast majority of SCSI devices have only one LUN, and
176 so most people can say N here. The max_luns boot/module parameter
177 allows to override this setting.
179 config SCSI_CONSTANTS
180 bool "Verbose SCSI error reporting (kernel size +=12K)"
183 The error messages regarding your SCSI hardware will be easier to
184 understand if you say Y here; it will enlarge your kernel by about
185 12 KB. If in doubt, say Y.
188 bool "SCSI logging facility"
191 This turns on a logging facility that can be used to debug a number
192 of SCSI related problems.
194 If you say Y here, no logging output will appear by default, but you
195 can enable logging by saying Y to "/proc file system support" and
196 "Sysctl support" below and executing the command
198 echo "scsi log token [level]" > /proc/scsi/scsi
200 at boot time after the /proc file system has been mounted.
202 There are a number of things that can be used for 'token' (you can
203 find them in the source: <file:drivers/scsi/scsi.c>), and this
204 allows you to select the types of information you want, and the
205 level allows you to select the level of verbosity.
207 If you say N here, it may be harder to track down some types of SCSI
208 problems. If you say Y here your kernel will be somewhat larger, but
209 there should be no noticeable performance impact as long as you have
212 menu "SCSI Transport Attributes"
215 config SCSI_SPI_ATTRS
216 tristate "Parallel SCSI (SPI) Transport Attributes"
219 If you wish to export transport-specific information about
220 each attached SCSI device to sysfs, say Y. Otherwise, say N.
223 tristate "FiberChannel Transport Attributes"
226 If you wish to export transport-specific information about
227 each attached FiberChannel device to sysfs, say Y.
230 config SCSI_ISCSI_ATTRS
231 tristate "iSCSI Transport Attributes"
232 depends on SCSI && NET
234 If you wish to export transport-specific information about
235 each attached iSCSI device to sysfs, say Y.
239 tristate "iSCSI Initiator over TCP/IP"
240 depends on SCSI && INET && SCSI_ISCSI_ATTRS
245 The iSCSI Driver provides a host with the ability to access storage
246 through an IP network. The driver uses the iSCSI protocol to transport
247 SCSI requests and responses over a TCP/IP network between the host
248 (the "initiator") and "targets". Architecturally, the iSCSI driver
249 combines with the host's TCP/IP stack, network drivers, and Network
250 Interface Card (NIC) to provide the same functions as a SCSI or a
251 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
253 To compile this driver as a module, choose M here: the
254 module will be called iscsi_tcp.
256 The userspace component needed to initialize the driver, documentation,
257 and sample configuration files can be found here:
259 http://linux-iscsi.sf.net
263 menu "SCSI low-level drivers"
267 tristate "SGI WD93C93 SCSI Driver"
268 depends on SGI_IP22 && SCSI
270 If you have a Western Digital WD93 SCSI controller on
271 an SGI MIPS system, say Y. Otherwise, say N.
274 tristate "DEC NCR53C94 Scsi Driver"
275 depends on MACH_DECSTATION && SCSI && TC
277 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
278 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
281 tristate "DEC SII Scsi Driver"
282 depends on MACH_DECSTATION && SCSI && 32BIT
284 config BLK_DEV_3W_XXXX_RAID
285 tristate "3ware 5/6/7/8xxx ATA-RAID support"
286 depends on PCI && SCSI
288 3ware is the only hardware ATA-Raid product in Linux to date.
289 This card is 2,4, or 8 channel master mode support only.
290 SCSI support required!!!
292 <http://www.3ware.com/>
294 Please read the comments at the top of
295 <file:drivers/scsi/3w-xxxx.c>.
298 tristate "3ware 9xxx SATA-RAID support"
299 depends on PCI && SCSI
301 This driver supports the 9000 series 3ware SATA-RAID cards.
303 <http://www.amcc.com>
305 Please read the comments at the top of
306 <file:drivers/scsi/3w-9xxx.c>.
308 config SCSI_7000FASST
309 tristate "7000FASST SCSI support"
310 depends on ISA && SCSI && ISA_DMA_API
312 This driver supports the Western Digital 7000 SCSI host adapter
313 family. Some information is in the source:
314 <file:drivers/scsi/wd7000.c>.
316 To compile this driver as a module, choose M here: the
317 module will be called wd7000.
320 tristate "ACARD SCSI support"
321 depends on PCI && SCSI
323 This driver supports the ACARD SCSI host adapter.
324 Support Chip <ATP870 ATP876 ATP880 ATP885>
325 To compile this driver as a module, choose M here: the
326 module will be called atp870u.
329 tristate "Adaptec AHA152X/2825 support"
330 depends on ISA && SCSI && !64BIT
332 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
333 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
334 must be manually specified in this case.
336 It is explained in section 3.3 of the SCSI-HOWTO, available from
337 <http://www.tldp.org/docs.html#howto>. You might also want to
338 read the file <file:Documentation/scsi/aha152x.txt>.
340 To compile this driver as a module, choose M here: the
341 module will be called aha152x.
344 tristate "Adaptec AHA1542 support"
345 depends on ISA && SCSI && ISA_DMA_API
347 This is support for a SCSI host adapter. It is explained in section
348 3.4 of the SCSI-HOWTO, available from
349 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
350 purchased by Adaptec, and some former Trantor products are being
351 sold under the Adaptec name. If it doesn't work out of the box, you
352 may have to change some settings in <file:drivers/scsi/aha1542.h>.
354 To compile this driver as a module, choose M here: the
355 module will be called aha1542.
358 tristate "Adaptec AHA1740 support"
359 depends on EISA && SCSI
361 This is support for a SCSI host adapter. It is explained in section
362 3.5 of the SCSI-HOWTO, available from
363 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
364 of the box, you may have to change some settings in
365 <file:drivers/scsi/aha1740.h>.
367 To compile this driver as a module, choose M here: the
368 module will be called aha1740.
371 tristate "Adaptec AACRAID support"
372 depends on SCSI && PCI
374 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
376 config SCSI_AIC7XXX_OLD
377 tristate "Adaptec AIC7xxx support (old driver)"
378 depends on (ISA || EISA || PCI ) && SCSI
380 WARNING This driver is an older aic7xxx driver and is no longer
381 under active development. Adaptec, Inc. is writing a new driver to
382 take the place of this one, and it is recommended that whenever
383 possible, people should use the new Adaptec written driver instead
384 of this one. This driver will eventually be phased out entirely.
386 This is support for the various aic7xxx based Adaptec SCSI
387 controllers. These include the 274x EISA cards; 284x VLB cards;
388 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
389 motherboard based SCSI controllers from Adaptec. It does not support
390 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
391 support them. It does not support the 2920 cards from Adaptec that
392 use the Future Domain SCSI controller chip. For those cards, you
393 need the "Future Domain 16xx SCSI support" driver.
395 In general, if the controller is based on an Adaptec SCSI controller
396 chip from the aic777x series or the aic78xx series, this driver
397 should work. The only exception is the 7810 which is specifically
398 not supported (that's the RAID controller chip on the AAA-13x
401 Note that the AHA2920 SCSI host adapter is *not* supported by this
402 driver; choose "Future Domain 16xx SCSI support" instead if you have
405 Information on the configuration options for this controller can be
406 found by checking the help file for each of the available
407 configuration options. You should read
408 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
409 contacting the maintainer with any questions. The SCSI-HOWTO,
410 available from <http://www.tldp.org/docs.html#howto>, can also
413 To compile this driver as a module, choose M here: the
414 module will be called aic7xxx_old.
416 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
418 # All the I2O code and drivers do not seem to be 64bit safe.
420 tristate "Adaptec I2O RAID support "
421 depends on !64BIT && SCSI && PCI
423 This driver supports all of Adaptec's I2O based RAID controllers as
424 well as the DPT SmartRaid V cards. This is an Adaptec maintained
425 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
427 To compile this driver as a module, choose M here: the
428 module will be called dpt_i2o.
431 tristate "AdvanSys SCSI support"
432 depends on (ISA || EISA || PCI) && SCSI && BROKEN
434 This is a driver for all SCSI host adapters manufactured by
435 AdvanSys. It is documented in the kernel source in
436 <file:drivers/scsi/advansys.c>.
438 To compile this driver as a module, choose M here: the
439 module will be called advansys.
442 tristate "Always IN2000 SCSI support"
443 depends on ISA && SCSI
445 This is support for an ISA bus SCSI host adapter. You'll find more
446 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
447 out of the box, you may have to change the jumpers for IRQ or
450 To compile this driver as a module, choose M here: the
451 module will be called in2000.
453 source "drivers/scsi/megaraid/Kconfig.megaraid"
456 tristate "Serial ATA (SATA) support"
459 This driver family supports Serial ATA host controllers
464 config SCSI_SATA_AHCI
465 tristate "AHCI SATA support"
466 depends on SCSI_SATA && PCI
468 This option enables support for AHCI Serial ATA.
473 tristate "ServerWorks Frodo / Apple K2 SATA support"
474 depends on SCSI_SATA && PCI
476 This option enables support for Broadcom/Serverworks/Apple K2
482 tristate "Intel PIIX/ICH SATA support"
483 depends on SCSI_SATA && PCI
485 This option enables support for ICH5 Serial ATA.
486 If PATA support was enabled previously, this enables
487 support for select Intel PIIX/ICH PATA host controllers.
492 tristate "Marvell SATA support"
493 depends on SCSI_SATA && PCI && EXPERIMENTAL
495 This option enables support for the Marvell Serial ATA family.
496 Currently supports 88SX[56]0[48][01] chips.
501 tristate "NVIDIA SATA support"
502 depends on SCSI_SATA && PCI && EXPERIMENTAL
504 This option enables support for NVIDIA Serial ATA.
508 config SCSI_SATA_PROMISE
509 tristate "Promise SATA TX2/TX4 support"
510 depends on SCSI_SATA && PCI
512 This option enables support for Promise Serial ATA TX2/TX4.
516 config SCSI_SATA_QSTOR
517 tristate "Pacific Digital SATA QStor support"
518 depends on SCSI_SATA && PCI
520 This option enables support for Pacific Digital Serial ATA QStor.
525 tristate "Promise SATA SX4 support"
526 depends on SCSI_SATA && PCI && EXPERIMENTAL
528 This option enables support for Promise Serial ATA SX4.
533 tristate "Silicon Image SATA support"
534 depends on SCSI_SATA && PCI && EXPERIMENTAL
536 This option enables support for Silicon Image Serial ATA.
541 tristate "SiS 964/180 SATA support"
542 depends on SCSI_SATA && PCI && EXPERIMENTAL
544 This option enables support for SiS Serial ATA 964/180.
549 tristate "ULi Electronics SATA support"
550 depends on SCSI_SATA && PCI && EXPERIMENTAL
552 This option enables support for ULi Electronics SATA.
557 tristate "VIA SATA support"
558 depends on SCSI_SATA && PCI
560 This option enables support for VIA Serial ATA.
564 config SCSI_SATA_VITESSE
565 tristate "VITESSE VSC-7174 SATA support"
566 depends on SCSI_SATA && PCI
568 This option enables support for Vitesse VSC7174 Serial ATA.
573 tristate "BusLogic SCSI support"
574 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
576 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
577 Adapters. Consult the SCSI-HOWTO, available from
578 <http://www.tldp.org/docs.html#howto>, and the files
579 <file:Documentation/scsi/BusLogic.txt> and
580 <file:Documentation/scsi/FlashPoint.txt> for more information.
582 To compile this driver as a module, choose M here: the
583 module will be called BusLogic.
585 config SCSI_OMIT_FLASHPOINT
586 bool "Omit FlashPoint support"
587 depends on SCSI_BUSLOGIC
589 This option allows you to omit the FlashPoint support from the
590 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
591 substantial, so users of MultiMaster Host Adapters may wish to omit
595 # This is marked broken because it uses over 4kB of stack in
597 # 2076 CpqTsProcessIMQEntry
601 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
602 depends on PCI && SCSI && BROKEN
604 Say Y here to compile in support for the Compaq StorageWorks Fibre
605 Channel 64-bit/66Mhz Host Bus Adapter.
608 tristate "DMX3191D SCSI support"
609 depends on PCI && SCSI
611 This is support for Domex DMX3191D SCSI Host Adapters.
613 To compile this driver as a module, choose M here: the
614 module will be called dmx3191d.
617 tristate "DTC3180/3280 SCSI support"
618 depends on ISA && SCSI
620 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
621 the SCSI-HOWTO, available from
622 <http://www.tldp.org/docs.html#howto>, and the file
623 <file:Documentation/scsi/dtc3x80.txt>.
625 To compile this driver as a module, choose M here: the
626 module will be called dtc.
629 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
630 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
632 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
633 ISA and all EISA I/O addresses are probed looking for the "EATA"
634 signature. The addresses of all the PCI SCSI controllers reported
635 by the PCI subsystem are probed as well.
637 You want to read the start of <file:drivers/scsi/eata.c> and the
638 SCSI-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
641 To compile this driver as a module, choose M here: the
642 module will be called eata.
644 config SCSI_EATA_TAGGED_QUEUE
645 bool "enable tagged command queueing"
648 This is a feature of SCSI-2 which improves performance: the host
649 adapter can send several SCSI commands to a device's queue even if
650 previous commands haven't finished yet.
651 This is equivalent to the "eata=tc:y" boot option.
653 config SCSI_EATA_LINKED_COMMANDS
654 bool "enable elevator sorting"
657 This option enables elevator sorting for all probed SCSI disks and
658 CD-ROMs. It definitely reduces the average seek distance when doing
659 random seeks, but this does not necessarily result in a noticeable
660 performance improvement: your mileage may vary...
661 This is equivalent to the "eata=lc:y" boot option.
663 config SCSI_EATA_MAX_TAGS
664 int "maximum number of queued commands"
668 This specifies how many SCSI commands can be maximally queued for
669 each probed SCSI device. You should reduce the default value of 16
670 only if you have disks with buggy or limited tagged command support.
671 Minimum is 2 and maximum is 62. This value is also the window size
672 used by the elevator sorting option above. The effective value used
673 by the driver for each probed SCSI device is reported at boot time.
674 This is equivalent to the "eata=mq:8" boot option.
677 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
678 depends on (ISA || EISA || PCI) && SCSI && BROKEN
680 This driver supports all EATA-PIO protocol compliant SCSI Host
681 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
682 host adapters could also use this driver but are discouraged from
683 doing so, since this driver only supports hard disks and lacks
684 numerous features. You might want to have a look at the SCSI-HOWTO,
685 available from <http://www.tldp.org/docs.html#howto>.
687 To compile this driver as a module, choose M here: the
688 module will be called eata_pio.
690 config SCSI_FUTURE_DOMAIN
691 tristate "Future Domain 16xx SCSI/AHA-2920A support"
692 depends on (ISA || PCI) && SCSI
694 This is support for Future Domain's 16-bit SCSI host adapters
695 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
696 other adapters based on the Future Domain chipsets (Quantum
697 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
698 It is explained in section 3.7 of the SCSI-HOWTO, available from
699 <http://www.tldp.org/docs.html#howto>.
701 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
702 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
703 controller support"). This Future Domain driver works with the older
704 Adaptec AHA-2920A boards with a Future Domain chip on them.
706 To compile this driver as a module, choose M here: the
707 module will be called fdomain.
710 tristate "Future Domain MCS-600/700 SCSI support"
711 depends on MCA_LEGACY && SCSI
713 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
714 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
715 is identical to the MCS 700 and hence also supported by this driver.
716 This driver also supports the Reply SB16/SCSI card (the SCSI part).
717 It supports multiple adapters in the same system.
719 To compile this driver as a module, choose M here: the
720 module will be called fd_mcs.
723 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
724 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
726 Formerly called GDT SCSI Disk Array Controller Support.
728 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
729 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
730 in the kernel source in <file:drivers/scsi/gdth.c> and
731 <file:drivers/scsi/gdth.h.>
733 To compile this driver as a module, choose M here: the
734 module will be called gdth.
736 config SCSI_GENERIC_NCR5380
737 tristate "Generic NCR5380/53c400 SCSI PIO support"
738 depends on ISA && SCSI
740 This is a driver for the old NCR 53c80 series of SCSI controllers
741 on boards using PIO. Most boards such as the Trantor T130 fit this
742 category, along with a large number of ISA 8bit controllers shipped
743 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
744 you should select the specific driver for that card rather than
745 generic 5380 support.
747 It is explained in section 3.8 of the SCSI-HOWTO, available from
748 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
749 of the box, you may have to change some settings in
750 <file:drivers/scsi/g_NCR5380.h>.
752 To compile this driver as a module, choose M here: the
753 module will be called g_NCR5380.
755 config SCSI_GENERIC_NCR5380_MMIO
756 tristate "Generic NCR5380/53c400 SCSI MMIO support"
757 depends on ISA && SCSI
759 This is a driver for the old NCR 53c80 series of SCSI controllers
760 on boards using memory mapped I/O.
761 It is explained in section 3.8 of the SCSI-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
763 of the box, you may have to change some settings in
764 <file:drivers/scsi/g_NCR5380.h>.
766 To compile this driver as a module, choose M here: the
767 module will be called g_NCR5380_mmio.
769 config SCSI_GENERIC_NCR53C400
770 bool "Enable NCR53c400 extensions"
771 depends on SCSI_GENERIC_NCR5380
773 This enables certain optimizations for the NCR53c400 SCSI cards.
774 You might as well try it out. Note that this driver will only probe
775 for the Trantor T130B in its default configuration; you might have
776 to pass a command line option to the kernel at boot time if it does
777 not detect your card. See the file
778 <file:Documentation/scsi/g_NCR5380.txt> for details.
781 tristate "IBMMCA SCSI support"
782 depends on MCA_LEGACY && SCSI
784 This is support for the IBM SCSI adapter found in many of the PS/2
785 series computers. These machines have an MCA bus, so you need to
786 answer Y to "MCA support" as well and read
787 <file:Documentation/mca.txt>.
789 If the adapter isn't found during boot (a common problem for models
790 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
791 option, where <pun> is the id of the SCSI subsystem (usually 7, but
792 if that doesn't work check your reference diskette). Owners of
793 model 95 with a LED-matrix-display can in addition activate some
794 activity info like under OS/2, but more informative, by setting
795 'ibmmcascsi=display' as an additional kernel parameter. Try "man
796 bootparam" or see the documentation of your boot loader about how to
797 pass options to the kernel.
799 To compile this driver as a module, choose M here: the
800 module will be called ibmmca.
802 config IBMMCA_SCSI_ORDER_STANDARD
803 bool "Standard SCSI-order"
804 depends on SCSI_IBMMCA
806 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
807 are assigned to the drive letters, starting with the lowest SCSI-id
808 (physical number -- pun) to be drive C:, as seen from DOS and
809 similar operating systems. When looking into papers describing the
810 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
811 The SCSI-standard follows a hardware-hierarchy which says that id 7
812 has the highest priority and id 0 the lowest. Therefore, the host
813 adapters are still today everywhere placed as SCSI-id 7 by default.
814 In the SCSI-standard, the drive letters express the priority of the
815 disk. C: should be the hard disk, or a partition on it, with the
816 highest priority. This must therefore be the disk with the highest
817 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
818 original definition of the SCSI-standard as also industrial- and
819 process-control-machines, like VME-CPUs running under realtime-OSes
820 (e.g. LynxOS, OS9) do.
822 If you like to run Linux on your MCA-machine with the same
823 assignment of hard disks as seen from e.g. DOS or OS/2 on your
824 machine, which is in addition conformant to the SCSI-standard, you
825 must say Y here. This is also necessary for MCA-Linux users who want
826 to keep downward compatibility to older releases of the
827 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
830 If you like to have the lowest SCSI-id assigned as drive C:, as
831 modern SCSI-BIOSes do, which does not conform to the standard, but
832 is widespread and common in the PC-world of today, you must say N
833 here. If unsure, say Y.
835 config IBMMCA_SCSI_DEV_RESET
836 bool "Reset SCSI-devices at boottime"
837 depends on SCSI_IBMMCA
839 By default, SCSI-devices are reset when the machine is powered on.
840 However, some devices exist, like special-control-devices,
841 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
842 not reset when switched on. If you say Y here, each device connected
843 to your SCSI-bus will be issued a reset-command after it has been
844 probed, while the kernel is booting. This may cause problems with
845 more modern devices, like hard disks, which do not appreciate these
846 reset commands, and can cause your system to hang. So say Y only if
847 you know that one of your older devices needs it; N is the safe
851 tristate "IBM ServeRAID support"
852 depends on PCI && SCSI
854 This is support for the IBM ServeRAID hardware RAID controllers.
855 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
856 for more information. If this driver does not work correctly
857 without modification please contact the author by email at
858 <ipslinux@adaptec.com>.
860 To compile this driver as a module, choose M here: the
861 module will be called ips.
864 tristate "IBM Virtual SCSI support"
865 depends on PPC_PSERIES || PPC_ISERIES
867 This is the IBM POWER Virtual SCSI Client
869 To compile this driver as a module, choose M here: the
870 module will be called ibmvscsic.
873 tristate "Initio 9100U(W) support"
874 depends on PCI && SCSI
876 This is support for the Initio 91XXU(W) SCSI host adapter. Please
877 read the SCSI-HOWTO, available from
878 <http://www.tldp.org/docs.html#howto>.
880 To compile this driver as a module, choose M here: the
881 module will be called initio.
884 tristate "Initio INI-A100U2W support"
885 depends on PCI && SCSI
887 This is support for the Initio INI-A100U2W SCSI host adapter.
888 Please read the SCSI-HOWTO, available from
889 <http://www.tldp.org/docs.html#howto>.
891 To compile this driver as a module, choose M here: the
892 module will be called a100u2w.
895 tristate "IOMEGA parallel port (ppa - older drives)"
896 depends on SCSI && PARPORT
898 This driver supports older versions of IOMEGA's parallel port ZIP
899 drive (a 100 MB removable media device).
901 Note that you can say N here if you have the SCSI version of the ZIP
902 drive: it will be supported automatically if you said Y to the
903 generic "SCSI disk support", above.
905 If you have the ZIP Plus drive or a more recent parallel port ZIP
906 drive (if the supplied cable with the drive is labeled "AutoDetect")
907 then you should say N here and Y to "IOMEGA parallel port (imm -
908 newer drives)", below.
910 For more information about this driver and how to use it you should
911 read the file <file:Documentation/scsi/ppa.txt>. You should also read
912 the SCSI-HOWTO, which is available from
913 <http://www.tldp.org/docs.html#howto>. If you use this driver,
914 you will still be able to use the parallel port for other tasks,
915 such as a printer; it is safe to compile both drivers into the
918 To compile this driver as a module, choose M here: the
919 module will be called ppa.
922 tristate "IOMEGA parallel port (imm - newer drives)"
923 depends on SCSI && PARPORT
925 This driver supports newer versions of IOMEGA's parallel port ZIP
926 drive (a 100 MB removable media device).
928 Note that you can say N here if you have the SCSI version of the ZIP
929 drive: it will be supported automatically if you said Y to the
930 generic "SCSI disk support", above.
932 If you have the ZIP Plus drive or a more recent parallel port ZIP
933 drive (if the supplied cable with the drive is labeled "AutoDetect")
934 then you should say Y here; if you have an older ZIP drive, say N
935 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
937 For more information about this driver and how to use it you should
938 read the file <file:Documentation/scsi/ppa.txt>. You should also read
939 the SCSI-HOWTO, which is available from
940 <http://www.tldp.org/docs.html#howto>. If you use this driver,
941 you will still be able to use the parallel port for other tasks,
942 such as a printer; it is safe to compile both drivers into the
945 To compile this driver as a module, choose M here: the
946 module will be called imm.
948 config SCSI_IZIP_EPP16
949 bool "ppa/imm option - Use slow (but safe) EPP-16"
950 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
952 EPP (Enhanced Parallel Port) is a standard for parallel ports which
953 allows them to act as expansion buses that can handle up to 64
956 Some parallel port chipsets are slower than their motherboard, and
957 so we have to control the state of the chipset's FIFO queue every
958 now and then to avoid data loss. This will be done if you say Y
961 Generally, saying Y is the safe option and slows things down a bit.
963 config SCSI_IZIP_SLOW_CTR
964 bool "ppa/imm option - Assume slow parport control register"
965 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
967 Some parallel ports are known to have excessive delays between
968 changing the parallel port control register and good data being
969 available on the parallel port data/status register. This option
970 forces a small delay (1.0 usec to be exact) after changing the
971 control register to let things settle out. Enabling this option may
972 result in a big drop in performance but some very old parallel ports
973 (found in 386 vintage machines) will not work properly.
975 Generally, saying N is fine.
977 config SCSI_NCR53C406A
978 tristate "NCR53c406a SCSI support"
979 depends on ISA && SCSI
981 This is support for the NCR53c406a SCSI host adapter. For user
982 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
983 in the kernel source. Also read the SCSI-HOWTO, available from
984 <http://www.tldp.org/docs.html#howto>.
986 To compile this driver as a module, choose M here: the
987 module will be called NCR53c406.
990 tristate "NCR Dual 700 MCA SCSI support"
991 depends on MCA && SCSI
992 select SCSI_SPI_ATTRS
994 This is a driver for the MicroChannel Dual 700 card produced by
995 NCR and commonly used in 345x/35xx/4100 class machines. It always
996 tries to negotiate sync and uses tag command queueing.
998 Unless you have an NCR manufactured machine, the chances are that
999 you do not have this SCSI card, so say N.
1002 tristate "HP Lasi SCSI support for 53c700/710"
1003 depends on GSC && SCSI
1004 select SCSI_SPI_ATTRS
1006 This is a driver for the SCSI controller in the Lasi chip found in
1007 many PA-RISC workstations & servers. If you do not know whether you
1008 have a Lasi chip, it is safe to say "Y" here.
1010 config 53C700_LE_ON_BE
1012 depends on SCSI_LASI700
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_IOMAPPED
1075 depends on SCSI_SYM53C8XX_2
1077 If you say Y here, the driver will use port IO to access
1078 the card. This is significantly slower then using memory
1079 mapped IO. Most people should answer N.
1082 tristate "IBM Power Linux RAID adapter support"
1083 depends on PCI && SCSI
1086 This driver supports the IBM Power Linux family RAID adapters.
1087 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1088 as IBM iSeries 5702, 5703, 5709, and 570A.
1090 config SCSI_IPR_TRACE
1091 bool "enable driver internal trace"
1094 If you say Y here, the driver will trace all commands issued
1095 to the adapter. Performance impact is minimal. Trace can be
1096 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1098 config SCSI_IPR_DUMP
1099 bool "enable adapter dump support"
1102 If you say Y here, the driver will support adapter crash dump.
1103 If you enable this support, the iprdump daemon can be used
1104 to capture adapter failure analysis information.
1107 tristate "Zalon SCSI support"
1108 depends on GSC && SCSI
1109 select SCSI_SPI_ATTRS
1111 The Zalon is a GSC/HSC bus interface chip that sits between the
1112 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1113 C110, J200, J210 and some D, K & R-class machines. It's also
1114 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1115 Say Y here if you have one of these machines or cards.
1117 config SCSI_NCR_Q720
1118 tristate "NCR Quad 720 MCA SCSI support"
1119 depends on MCA && SCSI
1120 select SCSI_SPI_ATTRS
1122 This is a driver for the MicroChannel Quad 720 card produced by
1123 NCR and commonly used in 345x/35xx/4100 class machines. It always
1124 tries to negotiate sync and uses tag command queueing.
1126 Unless you have an NCR manufactured machine, the chances are that
1127 you do not have this SCSI card, so say N.
1129 config SCSI_NCR53C8XX_DEFAULT_TAGS
1130 int " default tagged command queue depth"
1131 depends on SCSI_ZALON || SCSI_NCR_Q720
1134 "Tagged command queuing" is a feature of SCSI-2 which improves
1135 performance: the host adapter can send several SCSI commands to a
1136 device's queue even if previous commands haven't finished yet.
1137 Because the device is intelligent, it can optimize its operations
1138 (like head positioning) based on its own request queue. Some SCSI
1139 devices don't implement this properly; if you want to disable this
1140 feature, enter 0 or 1 here (it doesn't matter which).
1142 The default value is 8 and should be supported by most hard disks.
1143 This value can be overridden from the boot command line using the
1144 'tags' option as follows (example):
1145 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1146 4, set queue depth to 16 for target 2 and target 3 on controller 0
1147 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1149 The normal answer therefore is to go with the default 8 and to use
1150 a boot command line option for devices that need to use a different
1151 command queue depth.
1153 There is no safe option other than using good SCSI devices.
1155 config SCSI_NCR53C8XX_MAX_TAGS
1156 int " maximum number of queued commands"
1157 depends on SCSI_ZALON || SCSI_NCR_Q720
1160 This option allows you to specify the maximum number of commands
1161 that can be queued to any device, when tagged command queuing is
1162 possible. The default value is 32. Minimum is 2, maximum is 64.
1163 Modern hard disks are able to support 64 tags and even more, but
1164 do not seem to be faster when more than 32 tags are being used.
1166 So, the normal answer here is to go with the default value 32 unless
1167 you are using very large hard disks with large cache (>= 1 MB) that
1168 are able to take advantage of more than 32 tagged commands.
1170 There is no safe option and the default answer is recommended.
1172 config SCSI_NCR53C8XX_SYNC
1173 int " synchronous transfers frequency in MHz"
1174 depends on SCSI_ZALON || SCSI_NCR_Q720
1177 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1178 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1179 are respectively the maximum data transfer rates in mega-transfers
1180 per second for each class. For example, a FAST-20 Wide 16 device is
1181 able to transfer data at 20 million 16 bit packets per second for a
1182 total rate of 40 MB/s.
1184 You may specify 0 if you want to only use asynchronous data
1185 transfers. This is the safest and slowest option. Otherwise, specify
1186 a value between 5 and 80, depending on the capability of your SCSI
1187 controller. The higher the number, the faster the data transfer.
1188 Note that 80 should normally be ok since the driver decreases the
1189 value automatically according to the controller's capabilities.
1191 Your answer to this question is ignored for controllers with NVRAM,
1192 since the driver will get this information from the user set-up. It
1193 also can be overridden using a boot setup option, as follows
1194 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1195 for FAST-20 synchronous data transfer (20 mega-transfers per
1198 The normal answer therefore is not to go with the default but to
1199 select the maximum value 80 allowing the driver to use the maximum
1200 value supported by each controller. If this causes problems with
1201 your SCSI devices, you should come back and decrease the value.
1203 There is no safe option other than using good cabling, right
1204 terminations and SCSI conformant devices.
1206 config SCSI_NCR53C8XX_PROFILE
1207 bool " enable profiling"
1208 depends on SCSI_ZALON || SCSI_NCR_Q720
1210 This option allows you to enable profiling information gathering.
1211 These statistics are not very accurate due to the low frequency
1212 of the kernel clock (100 Hz on i386) and have performance impact
1213 on systems that use very fast devices.
1215 The normal answer therefore is N.
1217 config SCSI_NCR53C8XX_NO_DISCONNECT
1218 bool " not allow targets to disconnect"
1219 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1221 This option is only provided for safety if you suspect some SCSI
1222 device of yours to not support properly the target-disconnect
1223 feature. In that case, you would say Y here. In general however, to
1224 not allow targets to disconnect is not reasonable if there is more
1225 than 1 device on a SCSI bus. The normal answer therefore is N.
1227 config SCSI_MCA_53C9X
1228 tristate "NCR MCA 53C9x SCSI support"
1229 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1231 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1232 controller based on the NCR 53C94. This driver will allow use of
1233 the controller on the 3550, and very possibly others.
1235 To compile this driver as a module, choose M here: the
1236 module will be called mca_53c9x.
1239 tristate "PAS16 SCSI support"
1240 depends on ISA && SCSI
1242 This is support for a SCSI host adapter. It is explained in section
1243 3.10 of the SCSI-HOWTO, available from
1244 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1245 of the box, you may have to change some settings in
1246 <file:drivers/scsi/pas16.h>.
1248 To compile this driver as a module, choose M here: the
1249 module will be called pas16.
1252 tristate "PSI240i support"
1253 depends on ISA && SCSI
1255 This is support for the PSI240i EIDE interface card which acts as a
1256 SCSI host adapter. Please read the SCSI-HOWTO, available from
1257 <http://www.tldp.org/docs.html#howto>.
1259 To compile this driver as a module, choose M here: the
1260 module will be called psi240i.
1262 config SCSI_QLOGIC_FAS
1263 tristate "Qlogic FAS SCSI support"
1264 depends on ISA && SCSI
1266 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1267 FastSCSI! cards as well as any other card based on the FASXX chip
1268 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1270 This driver does NOT support the PCI versions of these cards. The
1271 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1272 SCSI support"), below.
1274 Information about this driver is contained in
1275 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1276 SCSI-HOWTO, available from
1277 <http://www.tldp.org/docs.html#howto>.
1279 To compile this driver as a module, choose M here: the
1280 module will be called qlogicfas.
1282 config SCSI_QLOGIC_ISP
1283 tristate "Qlogic ISP SCSI support (old driver)"
1284 depends on PCI && SCSI && BROKEN
1286 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1287 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1288 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1290 If you say Y here, make sure to choose "BIOS" at the question "PCI
1293 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1294 should also read the SCSI-HOWTO, available from
1295 <http://www.tldp.org/docs.html#howto>.
1297 To compile this driver as a module, choose M here: the
1298 module will be called qlogicisp.
1300 These days the hardware is also supported by the more modern qla1280
1301 driver. In doubt use that one instead of qlogicisp.
1303 config SCSI_QLOGIC_FC
1304 tristate "Qlogic ISP FC SCSI support"
1305 depends on PCI && SCSI
1307 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1309 To compile this driver as a module, choose M here: the
1310 module will be called qlogicfc.
1312 config SCSI_QLOGIC_FC_FIRMWARE
1313 bool "Include loadable firmware in driver"
1314 depends on SCSI_QLOGIC_FC
1316 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1317 expanded LUN addressing and FcTape (FCP-2) support, in the
1318 qlogicfc driver. This is required on some platforms.
1320 config SCSI_QLOGIC_1280
1321 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1322 depends on PCI && SCSI
1324 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1326 To compile this driver as a module, choose M here: the
1327 module will be called qla1280.
1329 config SCSI_QLOGIC_1280_1040
1330 bool "Qlogic QLA 1020/1040 SCSI support"
1331 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1333 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1334 do not want to use the old driver. This option enables support in
1335 the qla1280 driver for those host adapters.
1337 config SCSI_QLOGICPTI
1338 tristate "PTI Qlogic, ISP Driver"
1339 depends on SBUS && SCSI
1341 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1342 controllers are known under Solaris as qpti and in the openprom as
1343 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1344 driven by a different driver.
1346 To compile this driver as a module, choose M here: the
1347 module will be called qlogicpti.
1349 source "drivers/scsi/qla2xxx/Kconfig"
1352 tristate "Emulex LightPulse Fibre Channel Support"
1353 depends on PCI && SCSI
1354 select SCSI_FC_ATTRS
1356 This lpfc driver supports the Emulex LightPulse
1357 Family of Fibre Channel PCI host adapters.
1360 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1361 depends on X86 && ISA && SCSI && BROKEN
1363 These are 8-bit SCSI controllers; the ST-01 is also supported by
1364 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1365 available from <http://www.tldp.org/docs.html#howto>. If it
1366 doesn't work out of the box, you may have to change some settings in
1367 <file:drivers/scsi/seagate.h>.
1369 To compile this driver as a module, choose M here: the
1370 module will be called seagate.
1372 # definitely looks not 64bit safe:
1374 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1375 depends on (EISA || MCA) && SCSI
1376 select SCSI_SPI_ATTRS
1378 This driver for NCR53c710 based SCSI host adapters.
1380 It currently supports Compaq EISA cards and NCR MCA cards
1382 config 53C700_IO_MAPPED
1384 depends on SCSI_SIM710
1387 config SCSI_SYM53C416
1388 tristate "Symbios 53c416 SCSI support"
1389 depends on ISA && SCSI
1391 This is support for the sym53c416 SCSI host adapter, the SCSI
1392 adapter that comes with some HP scanners. This driver requires that
1393 the sym53c416 is configured first using some sort of PnP
1394 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1395 are using isapnp then you need to compile this driver as a module
1396 and then load it using insmod after isapnp has run. The parameters
1397 of the configured card(s) should be passed to the driver. The format
1400 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1402 To compile this driver as a module, choose M here: the
1403 module will be called sym53c416.
1406 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1407 depends on PCI && SCSI && EXPERIMENTAL
1409 This driver supports PCI SCSI host adapters based on the ASIC
1410 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1412 This driver works, but is still in experimental status. So better
1413 have a bootable disk and a backup in case of emergency.
1415 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1417 To compile this driver as a module, choose M here: the
1418 module will be called dc395x.
1421 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1422 depends on PCI && SCSI
1424 This driver supports PCI SCSI host adapters based on the Am53C974A
1425 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1426 PCscsi/PCnet (Am53/79C974) solutions.
1428 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1430 Note that this driver does NOT support Tekram DC390W/U/F, which are
1431 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1433 To compile this driver as a module, choose M here: the
1434 module will be called tmscsim.
1437 tristate "Trantor T128/T128F/T228 SCSI support"
1438 depends on ISA && SCSI
1440 This is support for a SCSI host adapter. It is explained in section
1441 3.11 of the SCSI-HOWTO, available from
1442 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1443 of the box, you may have to change some settings in
1444 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1445 Adaptec, and some former Trantor products are being sold under the
1448 To compile this driver as a module, choose M here: the
1449 module will be called t128.
1452 tristate "UltraStor 14F/34F support"
1453 depends on ISA && SCSI && ISA_DMA_API
1455 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1456 The source at <file:drivers/scsi/u14-34f.c> contains some
1457 information about this hardware. If the driver doesn't work out of
1458 the box, you may have to change some settings in
1459 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1460 <http://www.tldp.org/docs.html#howto>. Note that there is also
1461 another driver for the same hardware: "UltraStor SCSI support",
1462 below. You should say Y to both only if you want 24F support as
1465 To compile this driver as a module, choose M here: the
1466 module will be called u14-34f.
1468 config SCSI_U14_34F_TAGGED_QUEUE
1469 bool "enable tagged command queueing"
1470 depends on SCSI_U14_34F
1472 This is a feature of SCSI-2 which improves performance: the host
1473 adapter can send several SCSI commands to a device's queue even if
1474 previous commands haven't finished yet.
1475 This is equivalent to the "u14-34f=tc:y" boot option.
1477 config SCSI_U14_34F_LINKED_COMMANDS
1478 bool "enable elevator sorting"
1479 depends on SCSI_U14_34F
1481 This option enables elevator sorting for all probed SCSI disks and
1482 CD-ROMs. It definitely reduces the average seek distance when doing
1483 random seeks, but this does not necessarily result in a noticeable
1484 performance improvement: your mileage may vary...
1485 This is equivalent to the "u14-34f=lc:y" boot option.
1487 config SCSI_U14_34F_MAX_TAGS
1488 int "maximum number of queued commands"
1489 depends on SCSI_U14_34F
1492 This specifies how many SCSI commands can be maximally queued for
1493 each probed SCSI device. You should reduce the default value of 8
1494 only if you have disks with buggy or limited tagged command support.
1495 Minimum is 2 and maximum is 14. This value is also the window size
1496 used by the elevator sorting option above. The effective value used
1497 by the driver for each probed SCSI device is reported at boot time.
1498 This is equivalent to the "u14-34f=mq:8" boot option.
1500 config SCSI_ULTRASTOR
1501 tristate "UltraStor SCSI support"
1502 depends on X86 && ISA && SCSI
1504 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1505 adapter family. This driver is explained in section 3.12 of the
1506 SCSI-HOWTO, available from
1507 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1508 of the box, you may have to change some settings in
1509 <file:drivers/scsi/ultrastor.h>.
1511 Note that there is also another driver for the same hardware:
1512 "UltraStor 14F/34F support", above.
1514 To compile this driver as a module, choose M here: the
1515 module will be called ultrastor.
1518 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1519 depends on PCI && SCSI && !64BIT
1521 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1522 SCSI host adapter. Please read the SCSI-HOWTO, available from
1523 <http://www.tldp.org/docs.html#howto>.
1525 To compile this driver as a module, choose M here: the
1526 module will be called nsp32.
1529 tristate "SCSI debugging host simulator"
1532 This is a host adapter simulator that can simulate multiple hosts
1533 each with multiple dummy SCSI devices (disks). It defaults to one
1534 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1535 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1536 dummy disks are simulated, they share the same kernel RAM for
1537 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1538 information. This driver is primarily of use to those testing the
1539 SCSI and block subsystems. If unsure, say N.
1542 tristate "MESH (Power Mac internal SCSI) support"
1543 depends on PPC32 && PPC_PMAC && SCSI
1545 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1546 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1547 other Power Macintoshes do). Say Y to include support for this SCSI
1550 To compile this driver as a module, choose M here: the
1551 module will be called mesh.
1553 config SCSI_MESH_SYNC_RATE
1554 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1555 depends on SCSI_MESH
1558 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1559 drives a bus which is entirely internal to the machine (such as the
1560 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1561 operation at up to 10 MB/s. On machines where the SCSI bus
1562 controlled by the MESH can have external devices connected, it is
1563 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1564 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1565 to disable synchronous operation.
1567 config SCSI_MESH_RESET_DELAY_MS
1568 int "initial bus reset delay (ms) (0 = no reset)"
1569 depends on SCSI_MESH
1572 config SCSI_MAC53C94
1573 tristate "53C94 (Power Mac external SCSI) support"
1574 depends on PPC32 && PPC_PMAC && SCSI
1576 On Power Macintoshes (and clones) with two SCSI buses, the external
1577 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1578 machines which only have one SCSI bus, such as the 7200, also use
1579 the 53C94. Say Y to include support for the 53C94.
1581 To compile this driver as a module, choose M here: the
1582 module will be called mac53c94.
1584 source "drivers/scsi/arm/Kconfig"
1587 bool "MIPS JAZZ FAS216 SCSI support"
1588 depends on MACH_JAZZ && SCSI
1590 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1591 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1595 tristate "A3000 WD33C93A support"
1596 depends on AMIGA && SCSI
1598 If you have an Amiga 3000 and have SCSI devices connected to the
1599 built-in SCSI controller, say Y. Otherwise, say N.
1601 To compile this driver as a module, choose M here: the
1602 module will be called wd33c93.
1605 tristate "A2091/A590 WD33C93A support"
1606 depends on ZORRO && SCSI
1608 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1611 To compile this driver as a module, choose M here: the
1612 module will be called wd33c93.
1615 tristate "GVP Series II WD33C93A support"
1616 depends on ZORRO && SCSI
1618 If you have a Great Valley Products Series II SCSI controller,
1619 answer Y. Also say Y if you have a later model of GVP SCSI
1620 controller (such as the GVP A4008 or a Combo board). Otherwise,
1621 answer N. This driver does NOT work for the T-Rex series of
1622 accelerators from TekMagic and GVP-M.
1624 To compile this driver as a module, choose M here: the
1625 module will be called gvp11.
1627 config CYBERSTORM_SCSI
1628 tristate "CyberStorm SCSI support"
1629 depends on ZORRO && SCSI
1631 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1632 accelerator board and the optional Cyberstorm SCSI controller,
1633 answer Y. Otherwise, say N.
1635 config CYBERSTORMII_SCSI
1636 tristate "CyberStorm Mk II SCSI support"
1637 depends on ZORRO && SCSI
1639 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1640 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1644 tristate "Blizzard 2060 SCSI support"
1645 depends on ZORRO && SCSI
1647 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1648 and want to use the onboard SCSI controller, say Y. Otherwise,
1652 tristate "Blizzard 1230IV/1260 SCSI support"
1653 depends on ZORRO && SCSI
1655 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1656 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1659 config FASTLANE_SCSI
1660 tristate "Fastlane SCSI support"
1661 depends on ZORRO && SCSI
1663 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1664 one in the near future, say Y to this question. Otherwise, say N.
1666 config SCSI_AMIGA7XX
1667 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1668 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1670 Support for various NCR53c710-based SCSI controllers on the Amiga.
1672 - the builtin SCSI controller on the Amiga 4000T,
1673 - the Amiga 4091 Zorro III SCSI-2 controller,
1674 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1676 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1677 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1678 accelerator card for the Amiga 1200,
1679 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1680 Note that all of the above SCSI controllers, except for the builtin
1681 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1682 bus, so you also have to enable Zorro bus support if you want to use
1686 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1687 depends on ZORRO && SCSI && EXPERIMENTAL
1689 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1690 Y to this question. If you're in doubt about whether you have one,
1692 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1695 tristate "Atari native SCSI support"
1696 depends on ATARI && SCSI && BROKEN
1698 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1699 Falcon, ...) say Y to get it supported. Of course also, if you have
1700 a compatible SCSI controller (e.g. for Medusa).
1702 To compile this driver as a module, choose M here: the
1703 module will be called atari_scsi.
1705 This driver supports both styles of NCR integration into the
1706 system: the TT style (separate DMA), and the Falcon style (via
1707 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1708 in the Hades (without DMA).
1710 config ATARI_SCSI_TOSHIBA_DELAY
1711 bool "Long delays for Toshiba CD-ROMs"
1712 depends on ATARI_SCSI
1714 This option increases the delay after a SCSI arbitration to
1715 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1716 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1717 would impact performance a bit, so say N.
1719 config ATARI_SCSI_RESET_BOOT
1720 bool "Reset SCSI-devices at boottime"
1721 depends on ATARI_SCSI
1723 Reset the devices on your Atari whenever it boots. This makes the
1724 boot process fractionally longer but may assist recovery from errors
1725 that leave the devices with SCSI operations partway completed.
1728 bool "Hades SCSI DMA emulator"
1729 depends on ATARI_SCSI && HADES
1731 This option enables code which emulates the TT SCSI DMA chip on the
1732 Hades. This increases the SCSI transfer rates at least ten times
1733 compared to PIO transfers.
1736 bool "Macintosh NCR5380 SCSI"
1737 depends on MAC && SCSI=y
1739 This is the NCR 5380 SCSI controller included on most of the 68030
1740 based Macintoshes. If you have one of these say Y and read the
1741 SCSI-HOWTO, available from
1742 <http://www.tldp.org/docs.html#howto>.
1745 tristate "Macintosh NCR53c9[46] SCSI"
1746 depends on MAC && SCSI
1748 This is the NCR 53c9x SCSI controller found on most of the 68040
1749 based Macintoshes. If you have one of these say Y and read the
1750 SCSI-HOWTO, available from
1751 <http://www.tldp.org/docs.html#howto>.
1753 To compile this driver as a module, choose M here: the
1754 module will be called mac_esp.
1757 bool "WD33C93 SCSI driver for MVME147"
1758 depends on MVME147 && SCSI=y
1760 Support for the on-board SCSI controller on the Motorola MVME147
1761 single-board computer.
1764 bool "NCR53C710 SCSI driver for MVME16x"
1765 depends on MVME16x && SCSI && BROKEN
1767 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1768 SCSI controller chip. Almost everyone using one of these boards
1769 will want to say Y to this question.
1771 config BVME6000_SCSI
1772 bool "NCR53C710 SCSI driver for BVME6000"
1773 depends on BVME6000 && SCSI && BROKEN
1775 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1776 SCSI controller chip. Almost everyone using one of these boards
1777 will want to say Y to this question.
1779 config SCSI_NCR53C7xx_FAST
1780 bool "allow FAST-SCSI [10MHz]"
1781 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1783 This will enable 10MHz FAST-SCSI transfers with your host
1784 adapter. Some systems have problems with that speed, so it's safest
1788 tristate "Sun3 NCR5380 SCSI"
1789 depends on SUN3 && SCSI && BROKEN
1791 This option will enable support for the OBIO (onboard io) NCR5380
1792 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1793 "Sun3" type VME scsi controllers also based on the NCR5380.
1794 General Linux information on the Sun 3 series (now discontinued)
1795 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1798 bool "Sun3x ESP SCSI"
1799 depends on SUN3X && SCSI=y
1801 The ESP was an on-board SCSI controller used on Sun 3/80
1802 machines. Say Y here to compile in support for it.
1805 tristate "Sparc ESP Scsi Driver"
1806 depends on SBUS && SCSI
1808 This is the driver for the Sun ESP SCSI host adapter. The ESP
1809 chipset is present in most SPARC SBUS-based computers.
1811 To compile this driver as a module, choose M here: the
1812 module will be called esp.
1814 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1817 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1818 depends on ARCH_S390 && QDIO && SCSI
1819 select SCSI_FC_ATTRS
1821 If you want to access SCSI devices attached to your IBM eServer
1822 zSeries by means of Fibre Channel interfaces say Y.
1823 For details please refer to the documentation provided by IBM at
1824 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1826 This driver is also available as a module. This module will be
1827 called zfcp. If you want to compile it as a module, say M here
1828 and read <file:Documentation/modules.txt>.
1832 source "drivers/scsi/pcmcia/Kconfig"