1 menu "SCSI device support"
4 tristate "SCSI device support"
6 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
7 any other SCSI device under Linux, say Y and make sure that you know
8 the name of your SCSI host adapter (the card inside your computer
9 that "speaks" the SCSI protocol, also called SCSI controller),
10 because you will be asked for it.
12 You also need to say Y here if you have a device which speaks
13 the SCSI protocol. Examples of this include the parallel port
14 version of the IOMEGA ZIP drive, USB storage devices, Fibre
15 Channel, FireWire storage and the IDE-SCSI emulation driver.
17 To compile this driver as a module, choose M here and read
18 <file:Documentation/scsi/scsi.txt>.
19 The module will be called scsi_mod.
21 However, do not compile this as a module if your root file system
22 (the one containing the directory /) is located on a SCSI device.
25 bool "legacy /proc/scsi/ support"
26 depends on SCSI && PROC_FS
29 This option enables support for the various files in
30 /proc/scsi. In Linux 2.6 this has been superceeded by
31 files in sysfs but many legacy applications rely on this.
35 comment "SCSI support type (disk, tape, CD-ROM)"
39 tristate "SCSI disk support"
42 If you want to use SCSI hard disks, Fibre Channel disks,
43 USB storage or the SCSI or parallel port version of
44 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
45 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
46 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
49 To compile this driver as a module, choose M here and read
50 <file:Documentation/scsi/scsi.txt>.
51 The module will be called sd_mod.
53 Do not compile this driver as a module if your root file system
54 (the one containing the directory /) is located on a SCSI disk.
55 In this case, do not compile the driver for your SCSI host adapter
56 (below) as a module either.
59 tristate "SCSI tape support"
62 If you want to use a SCSI tape drive under Linux, say Y and read the
63 SCSI-HOWTO, available from
64 <http://www.tldp.org/docs.html#howto>, and
65 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
68 To compile this driver as a module, choose M here and read
69 <file:Documentation/scsi/scsi.txt>. The module will be called st.
72 tristate "SCSI OnStream SC-x0 tape support"
75 The OnStream SC-x0 SCSI tape drives can not be driven by the
76 standard st driver, but instead need this special osst driver and
77 use the /dev/osstX char device nodes (major 206). Via usb-storage
78 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
79 as well. Note that there is also a second generation of OnStream
80 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
81 tapes (QIC-157) and can be driven by the standard driver st.
82 For more information, you may have a look at the SCSI-HOWTO
83 <http://www.tldp.org/docs.html#howto> and
84 <file:Documentation/scsi/osst.txt> in the kernel source.
85 More info on the OnStream driver may be found on
86 <http://linux1.onstream.nl/test/>
87 Please also have a look at the standard st docu, as most of it
88 applies to osst as well.
90 To compile this driver as a module, choose M here and read
91 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
94 tristate "SCSI CDROM support"
97 If you want to use a SCSI or FireWire CD-ROM under Linux,
98 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
99 <http://www.tldp.org/docs.html#howto>. Also make sure to say
100 Y or M to "ISO 9660 CD-ROM file system support" later.
102 To compile this driver as a module, choose M here and read
103 <file:Documentation/scsi/scsi.txt>.
104 The module will be called sr_mod.
106 config BLK_DEV_SR_VENDOR
107 bool "Enable vendor-specific extensions (for SCSI CDROM)"
108 depends on BLK_DEV_SR
110 This enables the usage of vendor specific SCSI commands. This is
111 required to support multisession CDs with old NEC/TOSHIBA cdrom
112 drives (and HP Writers). If you have such a drive and get the first
113 session only, try saying Y here; everybody else says N.
116 tristate "SCSI generic support"
119 If you want to use SCSI scanners, synthesizers or CD-writers or just
120 about anything having "SCSI" in its name other than hard disks,
121 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
122 directly, so you need some additional software which knows how to
123 talk to these devices using the SCSI protocol:
125 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
126 writer software look at Cdrtools
127 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
128 and for burning a "disk at once": CDRDAO
129 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
130 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
131 For other devices, it's possible that you'll have to write the
132 driver software yourself. Please read the file
133 <file:Documentation/scsi/scsi-generic.txt> for more information.
135 To compile this driver as a module, choose M here and read
136 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
141 tristate "SCSI media changer support"
144 This is a driver for SCSI media changers. Most common devices are
145 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
146 don't need this for those tiny 6-slot cdrom changers. Media
147 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
148 If you have such hardware and want to use it with linux, say Y
149 here. Check <file:Documentation/scsi-changer.txt> for details.
151 If you want to compile this as a module ( = code which can be
152 inserted in and removed from the running kernel whenever you want),
153 say M here and read <file:Documentation/modules.txt> and
154 <file:Documentation/scsi.txt>. The module will be called ch.o.
158 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
161 config SCSI_MULTI_LUN
162 bool "Probe all LUNs on each SCSI device"
165 If you have a SCSI device that supports more than one LUN (Logical
166 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
167 can say Y here to force the SCSI driver to probe for multiple LUNs.
168 A SCSI device with multiple LUNs acts logically like multiple SCSI
169 devices. The vast majority of SCSI devices have only one LUN, and
170 so most people can say N here. The max_luns boot/module parameter
171 allows to override this setting.
173 config SCSI_CONSTANTS
174 bool "Verbose SCSI error reporting (kernel size +=12K)"
177 The error messages regarding your SCSI hardware will be easier to
178 understand if you say Y here; it will enlarge your kernel by about
179 12 KB. If in doubt, say Y.
182 bool "SCSI logging facility"
185 This turns on a logging facility that can be used to debug a number
186 of SCSI related problems.
188 If you say Y here, no logging output will appear by default, but you
189 can enable logging by saying Y to "/proc file system support" and
190 "Sysctl support" below and executing the command
192 echo "scsi log token [level]" > /proc/scsi/scsi
194 at boot time after the /proc file system has been mounted.
196 There are a number of things that can be used for 'token' (you can
197 find them in the source: <file:drivers/scsi/scsi.c>), and this
198 allows you to select the types of information you want, and the
199 level allows you to select the level of verbosity.
201 If you say N here, it may be harder to track down some types of SCSI
202 problems. If you say Y here your kernel will be somewhat larger, but
203 there should be no noticeable performance impact as long as you have
206 menu "SCSI Transport Attributes"
209 config SCSI_SPI_ATTRS
210 tristate "Parallel SCSI (SPI) Transport Attributes"
213 If you wish to export transport-specific information about
214 each attached SCSI device to sysfs, say Y. Otherwise, say N.
217 tristate "FiberChannel Transport Attributes"
220 If you wish to export transport-specific information about
221 each attached FiberChannel device to sysfs, say Y.
224 config SCSI_ISCSI_ATTRS
225 tristate "iSCSI Transport Attributes"
228 If you wish to export transport-specific information about
229 each attached iSCSI device to sysfs, say Y.
234 menu "SCSI low-level drivers"
238 tristate "SGI WD93C93 SCSI Driver"
239 depends on SGI_IP22 && SCSI
241 If you have a Western Digital WD93 SCSI controller on
242 an SGI MIPS system, say Y. Otherwise, say N.
245 tristate "DEC NCR53C94 Scsi Driver"
246 depends on MACH_DECSTATION && SCSI && TC
248 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
249 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
252 tristate "DEC SII Scsi Driver"
253 depends on MACH_DECSTATION && SCSI && 32BIT
255 config BLK_DEV_3W_XXXX_RAID
256 tristate "3ware 5/6/7/8xxx ATA-RAID support"
257 depends on PCI && SCSI
259 3ware is the only hardware ATA-Raid product in Linux to date.
260 This card is 2,4, or 8 channel master mode support only.
261 SCSI support required!!!
263 <http://www.3ware.com/>
265 Please read the comments at the top of
266 <file:drivers/scsi/3w-xxxx.c>.
269 tristate "3ware 9xxx SATA-RAID support"
270 depends on PCI && SCSI
272 This driver supports the 9000 series 3ware SATA-RAID cards.
274 <http://www.amcc.com>
276 Please read the comments at the top of
277 <file:drivers/scsi/3w-9xxx.c>.
279 config SCSI_7000FASST
280 tristate "7000FASST SCSI support"
281 depends on ISA && SCSI && ISA_DMA_API
283 This driver supports the Western Digital 7000 SCSI host adapter
284 family. Some information is in the source:
285 <file:drivers/scsi/wd7000.c>.
287 To compile this driver as a module, choose M here: the
288 module will be called wd7000.
291 tristate "ACARD SCSI support"
292 depends on PCI && SCSI
294 This driver supports the ACARD SCSI host adapter.
295 Support Chip <ATP870 ATP876 ATP880 ATP885>
296 To compile this driver as a module, choose M here: the
297 module will be called atp870u.
300 tristate "Adaptec AHA152X/2825 support"
301 depends on ISA && SCSI && !64BIT
303 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
304 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
305 must be manually specified in this case.
307 It is explained in section 3.3 of the SCSI-HOWTO, available from
308 <http://www.tldp.org/docs.html#howto>. You might also want to
309 read the file <file:Documentation/scsi/aha152x.txt>.
311 To compile this driver as a module, choose M here: the
312 module will be called aha152x.
315 tristate "Adaptec AHA1542 support"
316 depends on ISA && SCSI && ISA_DMA_API
318 This is support for a SCSI host adapter. It is explained in section
319 3.4 of the SCSI-HOWTO, available from
320 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
321 purchased by Adaptec, and some former Trantor products are being
322 sold under the Adaptec name. If it doesn't work out of the box, you
323 may have to change some settings in <file:drivers/scsi/aha1542.h>.
325 To compile this driver as a module, choose M here: the
326 module will be called aha1542.
329 tristate "Adaptec AHA1740 support"
330 depends on EISA && SCSI
332 This is support for a SCSI host adapter. It is explained in section
333 3.5 of the SCSI-HOWTO, available from
334 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
335 of the box, you may have to change some settings in
336 <file:drivers/scsi/aha1740.h>.
338 To compile this driver as a module, choose M here: the
339 module will be called aha1740.
342 tristate "Adaptec AACRAID support"
343 depends on SCSI && PCI
345 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
347 config SCSI_AIC7XXX_OLD
348 tristate "Adaptec AIC7xxx support (old driver)"
349 depends on (ISA || EISA || PCI ) && SCSI
351 WARNING This driver is an older aic7xxx driver and is no longer
352 under active development. Adaptec, Inc. is writing a new driver to
353 take the place of this one, and it is recommended that whenever
354 possible, people should use the new Adaptec written driver instead
355 of this one. This driver will eventually be phased out entirely.
357 This is support for the various aic7xxx based Adaptec SCSI
358 controllers. These include the 274x EISA cards; 284x VLB cards;
359 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
360 motherboard based SCSI controllers from Adaptec. It does not support
361 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
362 support them. It does not support the 2920 cards from Adaptec that
363 use the Future Domain SCSI controller chip. For those cards, you
364 need the "Future Domain 16xx SCSI support" driver.
366 In general, if the controller is based on an Adaptec SCSI controller
367 chip from the aic777x series or the aic78xx series, this driver
368 should work. The only exception is the 7810 which is specifically
369 not supported (that's the RAID controller chip on the AAA-13x
372 Note that the AHA2920 SCSI host adapter is *not* supported by this
373 driver; choose "Future Domain 16xx SCSI support" instead if you have
376 Information on the configuration options for this controller can be
377 found by checking the help file for each of the available
378 configuration options. You should read
379 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
380 contacting the maintainer with any questions. The SCSI-HOWTO,
381 available from <http://www.tldp.org/docs.html#howto>, can also
384 To compile this driver as a module, choose M here: the
385 module will be called aic7xxx_old.
387 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
389 # All the I2O code and drivers do not seem to be 64bit safe.
391 tristate "Adaptec I2O RAID support "
392 depends on !64BIT && SCSI && PCI
394 This driver supports all of Adaptec's I2O based RAID controllers as
395 well as the DPT SmartRaid V cards. This is an Adaptec maintained
396 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
398 To compile this driver as a module, choose M here: the
399 module will be called dpt_i2o.
402 tristate "AdvanSys SCSI support"
403 depends on (ISA || EISA || PCI) && SCSI && BROKEN
405 This is a driver for all SCSI host adapters manufactured by
406 AdvanSys. It is documented in the kernel source in
407 <file:drivers/scsi/advansys.c>.
409 To compile this driver as a module, choose M here: the
410 module will be called advansys.
413 tristate "Always IN2000 SCSI support"
414 depends on ISA && SCSI
416 This is support for an ISA bus SCSI host adapter. You'll find more
417 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
418 out of the box, you may have to change the jumpers for IRQ or
421 To compile this driver as a module, choose M here: the
422 module will be called in2000.
424 source "drivers/scsi/megaraid/Kconfig.megaraid"
427 tristate "Serial ATA (SATA) support"
430 This driver family supports Serial ATA host controllers
435 config SCSI_SATA_AHCI
436 tristate "AHCI SATA support"
437 depends on SCSI_SATA && PCI
439 This option enables support for AHCI Serial ATA.
444 tristate "ServerWorks Frodo / Apple K2 SATA support"
445 depends on SCSI_SATA && PCI
447 This option enables support for Broadcom/Serverworks/Apple K2
453 tristate "Intel PIIX/ICH SATA support"
454 depends on SCSI_SATA && PCI
456 This option enables support for ICH5 Serial ATA.
457 If PATA support was enabled previously, this enables
458 support for select Intel PIIX/ICH PATA host controllers.
463 tristate "Marvell SATA support"
464 depends on SCSI_SATA && PCI && EXPERIMENTAL
466 This option enables support for the Marvell Serial ATA family.
467 Currently supports 88SX[56]0[48][01] chips.
472 tristate "NVIDIA SATA support"
473 depends on SCSI_SATA && PCI && EXPERIMENTAL
475 This option enables support for NVIDIA Serial ATA.
479 config SCSI_SATA_PROMISE
480 tristate "Promise SATA TX2/TX4 support"
481 depends on SCSI_SATA && PCI
483 This option enables support for Promise Serial ATA TX2/TX4.
487 config SCSI_SATA_QSTOR
488 tristate "Pacific Digital SATA QStor support"
489 depends on SCSI_SATA && PCI
491 This option enables support for Pacific Digital Serial ATA QStor.
496 tristate "Promise SATA SX4 support"
497 depends on SCSI_SATA && PCI && EXPERIMENTAL
499 This option enables support for Promise Serial ATA SX4.
504 tristate "Silicon Image SATA support"
505 depends on SCSI_SATA && PCI && EXPERIMENTAL
507 This option enables support for Silicon Image Serial ATA.
512 tristate "SiS 964/180 SATA support"
513 depends on SCSI_SATA && PCI && EXPERIMENTAL
515 This option enables support for SiS Serial ATA 964/180.
520 tristate "ULi Electronics SATA support"
521 depends on SCSI_SATA && PCI && EXPERIMENTAL
523 This option enables support for ULi Electronics SATA.
528 tristate "VIA SATA support"
529 depends on SCSI_SATA && PCI
531 This option enables support for VIA Serial ATA.
535 config SCSI_SATA_VITESSE
536 tristate "VITESSE VSC-7174 SATA support"
537 depends on SCSI_SATA && PCI
539 This option enables support for Vitesse VSC7174 Serial ATA.
544 tristate "BusLogic SCSI support"
545 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
547 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
548 Adapters. Consult the SCSI-HOWTO, available from
549 <http://www.tldp.org/docs.html#howto>, and the files
550 <file:Documentation/scsi/BusLogic.txt> and
551 <file:Documentation/scsi/FlashPoint.txt> for more information.
553 To compile this driver as a module, choose M here: the
554 module will be called BusLogic.
556 config SCSI_OMIT_FLASHPOINT
557 bool "Omit FlashPoint support"
558 depends on SCSI_BUSLOGIC
560 This option allows you to omit the FlashPoint support from the
561 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
562 substantial, so users of MultiMaster Host Adapters may wish to omit
566 # This is marked broken because it uses over 4kB of stack in
568 # 2076 CpqTsProcessIMQEntry
572 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
573 depends on PCI && SCSI && BROKEN
575 Say Y here to compile in support for the Compaq StorageWorks Fibre
576 Channel 64-bit/66Mhz Host Bus Adapter.
579 tristate "DMX3191D SCSI support"
580 depends on PCI && SCSI
582 This is support for Domex DMX3191D SCSI Host Adapters.
584 To compile this driver as a module, choose M here: the
585 module will be called dmx3191d.
588 tristate "DTC3180/3280 SCSI support"
589 depends on ISA && SCSI
591 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
592 the SCSI-HOWTO, available from
593 <http://www.tldp.org/docs.html#howto>, and the file
594 <file:Documentation/scsi/dtc3x80.txt>.
596 To compile this driver as a module, choose M here: the
597 module will be called dtc.
600 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
601 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
603 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
604 ISA and all EISA I/O addresses are probed looking for the "EATA"
605 signature. The addresses of all the PCI SCSI controllers reported
606 by the PCI subsystem are probed as well.
608 You want to read the start of <file:drivers/scsi/eata.c> and the
609 SCSI-HOWTO, available from
610 <http://www.tldp.org/docs.html#howto>.
612 To compile this driver as a module, choose M here: the
613 module will be called eata.
615 config SCSI_EATA_TAGGED_QUEUE
616 bool "enable tagged command queueing"
619 This is a feature of SCSI-2 which improves performance: the host
620 adapter can send several SCSI commands to a device's queue even if
621 previous commands haven't finished yet.
622 This is equivalent to the "eata=tc:y" boot option.
624 config SCSI_EATA_LINKED_COMMANDS
625 bool "enable elevator sorting"
628 This option enables elevator sorting for all probed SCSI disks and
629 CD-ROMs. It definitely reduces the average seek distance when doing
630 random seeks, but this does not necessarily result in a noticeable
631 performance improvement: your mileage may vary...
632 This is equivalent to the "eata=lc:y" boot option.
634 config SCSI_EATA_MAX_TAGS
635 int "maximum number of queued commands"
639 This specifies how many SCSI commands can be maximally queued for
640 each probed SCSI device. You should reduce the default value of 16
641 only if you have disks with buggy or limited tagged command support.
642 Minimum is 2 and maximum is 62. This value is also the window size
643 used by the elevator sorting option above. The effective value used
644 by the driver for each probed SCSI device is reported at boot time.
645 This is equivalent to the "eata=mq:8" boot option.
648 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
649 depends on (ISA || EISA || PCI) && SCSI && BROKEN
651 This driver supports all EATA-PIO protocol compliant SCSI Host
652 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
653 host adapters could also use this driver but are discouraged from
654 doing so, since this driver only supports hard disks and lacks
655 numerous features. You might want to have a look at the SCSI-HOWTO,
656 available from <http://www.tldp.org/docs.html#howto>.
658 To compile this driver as a module, choose M here: the
659 module will be called eata_pio.
661 config SCSI_FUTURE_DOMAIN
662 tristate "Future Domain 16xx SCSI/AHA-2920A support"
663 depends on (ISA || PCI) && SCSI
665 This is support for Future Domain's 16-bit SCSI host adapters
666 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
667 other adapters based on the Future Domain chipsets (Quantum
668 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
669 It is explained in section 3.7 of the SCSI-HOWTO, available from
670 <http://www.tldp.org/docs.html#howto>.
672 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
673 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
674 controller support"). This Future Domain driver works with the older
675 Adaptec AHA-2920A boards with a Future Domain chip on them.
677 To compile this driver as a module, choose M here: the
678 module will be called fdomain.
681 tristate "Future Domain MCS-600/700 SCSI support"
682 depends on MCA_LEGACY && SCSI
684 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
685 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
686 is identical to the MCS 700 and hence also supported by this driver.
687 This driver also supports the Reply SB16/SCSI card (the SCSI part).
688 It supports multiple adapters in the same system.
690 To compile this driver as a module, choose M here: the
691 module will be called fd_mcs.
694 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
695 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
697 Formerly called GDT SCSI Disk Array Controller Support.
699 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
700 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
701 in the kernel source in <file:drivers/scsi/gdth.c> and
702 <file:drivers/scsi/gdth.h.>
704 To compile this driver as a module, choose M here: the
705 module will be called gdth.
707 config SCSI_GENERIC_NCR5380
708 tristate "Generic NCR5380/53c400 SCSI PIO support"
709 depends on ISA && SCSI
711 This is a driver for the old NCR 53c80 series of SCSI controllers
712 on boards using PIO. Most boards such as the Trantor T130 fit this
713 category, along with a large number of ISA 8bit controllers shipped
714 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
715 you should select the specific driver for that card rather than
716 generic 5380 support.
718 It is explained in section 3.8 of the SCSI-HOWTO, available from
719 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
720 of the box, you may have to change some settings in
721 <file:drivers/scsi/g_NCR5380.h>.
723 To compile this driver as a module, choose M here: the
724 module will be called g_NCR5380.
726 config SCSI_GENERIC_NCR5380_MMIO
727 tristate "Generic NCR5380/53c400 SCSI MMIO support"
728 depends on ISA && SCSI
730 This is a driver for the old NCR 53c80 series of SCSI controllers
731 on boards using memory mapped I/O.
732 It is explained in section 3.8 of the SCSI-HOWTO, available from
733 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
734 of the box, you may have to change some settings in
735 <file:drivers/scsi/g_NCR5380.h>.
737 To compile this driver as a module, choose M here: the
738 module will be called g_NCR5380_mmio.
740 config SCSI_GENERIC_NCR53C400
741 bool "Enable NCR53c400 extensions"
742 depends on SCSI_GENERIC_NCR5380
744 This enables certain optimizations for the NCR53c400 SCSI cards.
745 You might as well try it out. Note that this driver will only probe
746 for the Trantor T130B in its default configuration; you might have
747 to pass a command line option to the kernel at boot time if it does
748 not detect your card. See the file
749 <file:Documentation/scsi/g_NCR5380.txt> for details.
752 tristate "IBMMCA SCSI support"
753 depends on MCA_LEGACY && SCSI
755 This is support for the IBM SCSI adapter found in many of the PS/2
756 series computers. These machines have an MCA bus, so you need to
757 answer Y to "MCA support" as well and read
758 <file:Documentation/mca.txt>.
760 If the adapter isn't found during boot (a common problem for models
761 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
762 option, where <pun> is the id of the SCSI subsystem (usually 7, but
763 if that doesn't work check your reference diskette). Owners of
764 model 95 with a LED-matrix-display can in addition activate some
765 activity info like under OS/2, but more informative, by setting
766 'ibmmcascsi=display' as an additional kernel parameter. Try "man
767 bootparam" or see the documentation of your boot loader about how to
768 pass options to the kernel.
770 To compile this driver as a module, choose M here: the
771 module will be called ibmmca.
773 config IBMMCA_SCSI_ORDER_STANDARD
774 bool "Standard SCSI-order"
775 depends on SCSI_IBMMCA
777 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
778 are assigned to the drive letters, starting with the lowest SCSI-id
779 (physical number -- pun) to be drive C:, as seen from DOS and
780 similar operating systems. When looking into papers describing the
781 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
782 The SCSI-standard follows a hardware-hierarchy which says that id 7
783 has the highest priority and id 0 the lowest. Therefore, the host
784 adapters are still today everywhere placed as SCSI-id 7 by default.
785 In the SCSI-standard, the drive letters express the priority of the
786 disk. C: should be the hard disk, or a partition on it, with the
787 highest priority. This must therefore be the disk with the highest
788 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
789 original definition of the SCSI-standard as also industrial- and
790 process-control-machines, like VME-CPUs running under realtime-OSes
791 (e.g. LynxOS, OS9) do.
793 If you like to run Linux on your MCA-machine with the same
794 assignment of hard disks as seen from e.g. DOS or OS/2 on your
795 machine, which is in addition conformant to the SCSI-standard, you
796 must say Y here. This is also necessary for MCA-Linux users who want
797 to keep downward compatibility to older releases of the
798 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
801 If you like to have the lowest SCSI-id assigned as drive C:, as
802 modern SCSI-BIOSes do, which does not conform to the standard, but
803 is widespread and common in the PC-world of today, you must say N
804 here. If unsure, say Y.
806 config IBMMCA_SCSI_DEV_RESET
807 bool "Reset SCSI-devices at boottime"
808 depends on SCSI_IBMMCA
810 By default, SCSI-devices are reset when the machine is powered on.
811 However, some devices exist, like special-control-devices,
812 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
813 not reset when switched on. If you say Y here, each device connected
814 to your SCSI-bus will be issued a reset-command after it has been
815 probed, while the kernel is booting. This may cause problems with
816 more modern devices, like hard disks, which do not appreciate these
817 reset commands, and can cause your system to hang. So say Y only if
818 you know that one of your older devices needs it; N is the safe
822 tristate "IBM ServeRAID support"
823 depends on PCI && SCSI
825 This is support for the IBM ServeRAID hardware RAID controllers.
826 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
827 for more information. If this driver does not work correctly
828 without modification please contact the author by email at
829 <ipslinux@adaptec.com>.
831 To compile this driver as a module, choose M here: the
832 module will be called ips.
835 tristate "IBM Virtual SCSI support"
836 depends on PPC_PSERIES || PPC_ISERIES
838 This is the IBM POWER Virtual SCSI Client
840 To compile this driver as a module, choose M here: the
841 module will be called ibmvscsic.
844 tristate "Initio 9100U(W) support"
845 depends on PCI && SCSI
847 This is support for the Initio 91XXU(W) SCSI host adapter. Please
848 read the SCSI-HOWTO, available from
849 <http://www.tldp.org/docs.html#howto>.
851 To compile this driver as a module, choose M here: the
852 module will be called initio.
855 tristate "Initio INI-A100U2W support"
856 depends on PCI && SCSI
858 This is support for the Initio INI-A100U2W SCSI host adapter.
859 Please read the SCSI-HOWTO, available from
860 <http://www.tldp.org/docs.html#howto>.
862 To compile this driver as a module, choose M here: the
863 module will be called a100u2w.
866 tristate "IOMEGA parallel port (ppa - older drives)"
867 depends on SCSI && PARPORT
869 This driver supports older versions of IOMEGA's parallel port ZIP
870 drive (a 100 MB removable media device).
872 Note that you can say N here if you have the SCSI version of the ZIP
873 drive: it will be supported automatically if you said Y to the
874 generic "SCSI disk support", above.
876 If you have the ZIP Plus drive or a more recent parallel port ZIP
877 drive (if the supplied cable with the drive is labeled "AutoDetect")
878 then you should say N here and Y to "IOMEGA parallel port (imm -
879 newer drives)", below.
881 For more information about this driver and how to use it you should
882 read the file <file:Documentation/scsi/ppa.txt>. You should also read
883 the SCSI-HOWTO, which is available from
884 <http://www.tldp.org/docs.html#howto>. If you use this driver,
885 you will still be able to use the parallel port for other tasks,
886 such as a printer; it is safe to compile both drivers into the
889 To compile this driver as a module, choose M here: the
890 module will be called ppa.
893 tristate "IOMEGA parallel port (imm - newer drives)"
894 depends on SCSI && PARPORT
896 This driver supports newer versions of IOMEGA's parallel port ZIP
897 drive (a 100 MB removable media device).
899 Note that you can say N here if you have the SCSI version of the ZIP
900 drive: it will be supported automatically if you said Y to the
901 generic "SCSI disk support", above.
903 If you have the ZIP Plus drive or a more recent parallel port ZIP
904 drive (if the supplied cable with the drive is labeled "AutoDetect")
905 then you should say Y here; if you have an older ZIP drive, say N
906 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
908 For more information about this driver and how to use it you should
909 read the file <file:Documentation/scsi/ppa.txt>. You should also read
910 the SCSI-HOWTO, which is available from
911 <http://www.tldp.org/docs.html#howto>. If you use this driver,
912 you will still be able to use the parallel port for other tasks,
913 such as a printer; it is safe to compile both drivers into the
916 To compile this driver as a module, choose M here: the
917 module will be called imm.
919 config SCSI_IZIP_EPP16
920 bool "ppa/imm option - Use slow (but safe) EPP-16"
921 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
923 EPP (Enhanced Parallel Port) is a standard for parallel ports which
924 allows them to act as expansion buses that can handle up to 64
927 Some parallel port chipsets are slower than their motherboard, and
928 so we have to control the state of the chipset's FIFO queue every
929 now and then to avoid data loss. This will be done if you say Y
932 Generally, saying Y is the safe option and slows things down a bit.
934 config SCSI_IZIP_SLOW_CTR
935 bool "ppa/imm option - Assume slow parport control register"
936 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
938 Some parallel ports are known to have excessive delays between
939 changing the parallel port control register and good data being
940 available on the parallel port data/status register. This option
941 forces a small delay (1.0 usec to be exact) after changing the
942 control register to let things settle out. Enabling this option may
943 result in a big drop in performance but some very old parallel ports
944 (found in 386 vintage machines) will not work properly.
946 Generally, saying N is fine.
948 config SCSI_NCR53C406A
949 tristate "NCR53c406a SCSI support"
950 depends on ISA && SCSI
952 This is support for the NCR53c406a SCSI host adapter. For user
953 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
954 in the kernel source. Also read the SCSI-HOWTO, available from
955 <http://www.tldp.org/docs.html#howto>.
957 To compile this driver as a module, choose M here: the
958 module will be called NCR53c406.
961 tristate "NCR Dual 700 MCA SCSI support"
962 depends on MCA && SCSI
963 select SCSI_SPI_ATTRS
965 This is a driver for the MicroChannel Dual 700 card produced by
966 NCR and commonly used in 345x/35xx/4100 class machines. It always
967 tries to negotiate sync and uses tag command queueing.
969 Unless you have an NCR manufactured machine, the chances are that
970 you do not have this SCSI card, so say N.
973 tristate "HP Lasi SCSI support for 53c700/710"
974 depends on GSC && SCSI
975 select SCSI_SPI_ATTRS
977 This is a driver for the SCSI controller in the Lasi chip found in
978 many PA-RISC workstations & servers. If you do not know whether you
979 have a Lasi chip, it is safe to say "Y" here.
981 config 53C700_LE_ON_BE
983 depends on SCSI_LASI700
986 config SCSI_SYM53C8XX_2
987 tristate "SYM53C8XX Version 2 SCSI support"
988 depends on PCI && SCSI
989 select SCSI_SPI_ATTRS
991 This driver supports the whole NCR53C8XX/SYM53C8XX family of
992 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
993 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
994 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
995 controllers; you need to use the Fusion MPT driver for that.
997 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1000 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1001 int "DMA addressing mode"
1002 depends on SCSI_SYM53C8XX_2
1005 This option only applies to PCI-SCSI chips that are PCI DAC
1006 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1008 When set to 0, the driver will program the chip to only perform
1009 32-bit DMA. When set to 1, the chip will be able to perform DMA
1010 to addresses up to 1TB. When set to 2, the driver supports the
1011 full 64-bit DMA address range, but can only address 16 segments
1012 of 4 GB each. This limits the total addressable range to 64 GB.
1014 Most machines with less than 4GB of memory should use a setting
1015 of 0 for best performance. If your machine has 4GB of memory
1016 or more, you should set this option to 1 (the default).
1018 The still experimental value 2 (64 bit DMA addressing with 16
1019 x 4GB segments limitation) can be used on systems that require
1020 PCI address bits past bit 39 to be set for the addressing of
1021 memory using PCI DAC cycles.
1023 config SCSI_SYM53C8XX_DEFAULT_TAGS
1024 int "default tagged command queue depth"
1025 depends on SCSI_SYM53C8XX_2
1028 This is the default value of the command queue depth the
1029 driver will announce to the generic SCSI layer for devices
1030 that support tagged command queueing. This value can be changed
1031 from the boot command line. This is a soft limit that cannot
1032 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1034 config SCSI_SYM53C8XX_MAX_TAGS
1035 int "maximum number of queued commands"
1036 depends on SCSI_SYM53C8XX_2
1039 This option allows you to specify the maximum number of commands
1040 that can be queued to any device, when tagged command queuing is
1041 possible. The driver supports up to 256 queued commands per device.
1042 This value is used as a compiled-in hard limit.
1044 config SCSI_SYM53C8XX_IOMAPPED
1046 depends on SCSI_SYM53C8XX_2
1048 If you say Y here, the driver will use port IO to access
1049 the card. This is significantly slower then using memory
1050 mapped IO. Most people should answer N.
1053 tristate "IBM Power Linux RAID adapter support"
1054 depends on PCI && SCSI
1057 This driver supports the IBM Power Linux family RAID adapters.
1058 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1059 as IBM iSeries 5702, 5703, 5709, and 570A.
1061 config SCSI_IPR_TRACE
1062 bool "enable driver internal trace"
1065 If you say Y here, the driver will trace all commands issued
1066 to the adapter. Performance impact is minimal. Trace can be
1067 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1069 config SCSI_IPR_DUMP
1070 bool "enable adapter dump support"
1073 If you say Y here, the driver will support adapter crash dump.
1074 If you enable this support, the iprdump daemon can be used
1075 to capture adapter failure analysis information.
1078 tristate "Zalon SCSI support"
1079 depends on GSC && SCSI
1080 select SCSI_SPI_ATTRS
1082 The Zalon is a GSC/HSC bus interface chip that sits between the
1083 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1084 C110, J200, J210 and some D, K & R-class machines. It's also
1085 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1086 Say Y here if you have one of these machines or cards.
1088 config SCSI_NCR_Q720
1089 tristate "NCR Quad 720 MCA SCSI support"
1090 depends on MCA && SCSI
1091 select SCSI_SPI_ATTRS
1093 This is a driver for the MicroChannel Quad 720 card produced by
1094 NCR and commonly used in 345x/35xx/4100 class machines. It always
1095 tries to negotiate sync and uses tag command queueing.
1097 Unless you have an NCR manufactured machine, the chances are that
1098 you do not have this SCSI card, so say N.
1100 config SCSI_NCR53C8XX_DEFAULT_TAGS
1101 int " default tagged command queue depth"
1102 depends on SCSI_ZALON || SCSI_NCR_Q720
1105 "Tagged command queuing" is a feature of SCSI-2 which improves
1106 performance: the host adapter can send several SCSI commands to a
1107 device's queue even if previous commands haven't finished yet.
1108 Because the device is intelligent, it can optimize its operations
1109 (like head positioning) based on its own request queue. Some SCSI
1110 devices don't implement this properly; if you want to disable this
1111 feature, enter 0 or 1 here (it doesn't matter which).
1113 The default value is 8 and should be supported by most hard disks.
1114 This value can be overridden from the boot command line using the
1115 'tags' option as follows (example):
1116 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1117 4, set queue depth to 16 for target 2 and target 3 on controller 0
1118 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1120 The normal answer therefore is to go with the default 8 and to use
1121 a boot command line option for devices that need to use a different
1122 command queue depth.
1124 There is no safe option other than using good SCSI devices.
1126 config SCSI_NCR53C8XX_MAX_TAGS
1127 int " maximum number of queued commands"
1128 depends on SCSI_ZALON || SCSI_NCR_Q720
1131 This option allows you to specify the maximum number of commands
1132 that can be queued to any device, when tagged command queuing is
1133 possible. The default value is 32. Minimum is 2, maximum is 64.
1134 Modern hard disks are able to support 64 tags and even more, but
1135 do not seem to be faster when more than 32 tags are being used.
1137 So, the normal answer here is to go with the default value 32 unless
1138 you are using very large hard disks with large cache (>= 1 MB) that
1139 are able to take advantage of more than 32 tagged commands.
1141 There is no safe option and the default answer is recommended.
1143 config SCSI_NCR53C8XX_SYNC
1144 int " synchronous transfers frequency in MHz"
1145 depends on SCSI_ZALON || SCSI_NCR_Q720
1148 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1149 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1150 are respectively the maximum data transfer rates in mega-transfers
1151 per second for each class. For example, a FAST-20 Wide 16 device is
1152 able to transfer data at 20 million 16 bit packets per second for a
1153 total rate of 40 MB/s.
1155 You may specify 0 if you want to only use asynchronous data
1156 transfers. This is the safest and slowest option. Otherwise, specify
1157 a value between 5 and 80, depending on the capability of your SCSI
1158 controller. The higher the number, the faster the data transfer.
1159 Note that 80 should normally be ok since the driver decreases the
1160 value automatically according to the controller's capabilities.
1162 Your answer to this question is ignored for controllers with NVRAM,
1163 since the driver will get this information from the user set-up. It
1164 also can be overridden using a boot setup option, as follows
1165 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1166 for FAST-20 synchronous data transfer (20 mega-transfers per
1169 The normal answer therefore is not to go with the default but to
1170 select the maximum value 80 allowing the driver to use the maximum
1171 value supported by each controller. If this causes problems with
1172 your SCSI devices, you should come back and decrease the value.
1174 There is no safe option other than using good cabling, right
1175 terminations and SCSI conformant devices.
1177 config SCSI_NCR53C8XX_PROFILE
1178 bool " enable profiling"
1179 depends on SCSI_ZALON || SCSI_NCR_Q720
1181 This option allows you to enable profiling information gathering.
1182 These statistics are not very accurate due to the low frequency
1183 of the kernel clock (100 Hz on i386) and have performance impact
1184 on systems that use very fast devices.
1186 The normal answer therefore is N.
1188 config SCSI_NCR53C8XX_NO_DISCONNECT
1189 bool " not allow targets to disconnect"
1190 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1192 This option is only provided for safety if you suspect some SCSI
1193 device of yours to not support properly the target-disconnect
1194 feature. In that case, you would say Y here. In general however, to
1195 not allow targets to disconnect is not reasonable if there is more
1196 than 1 device on a SCSI bus. The normal answer therefore is N.
1198 config SCSI_MCA_53C9X
1199 tristate "NCR MCA 53C9x SCSI support"
1200 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1202 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1203 controller based on the NCR 53C94. This driver will allow use of
1204 the controller on the 3550, and very possibly others.
1206 To compile this driver as a module, choose M here: the
1207 module will be called mca_53c9x.
1210 tristate "PAS16 SCSI support"
1211 depends on ISA && SCSI
1213 This is support for a SCSI host adapter. It is explained in section
1214 3.10 of the SCSI-HOWTO, available from
1215 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1216 of the box, you may have to change some settings in
1217 <file:drivers/scsi/pas16.h>.
1219 To compile this driver as a module, choose M here: the
1220 module will be called pas16.
1223 tristate "PSI240i support"
1224 depends on ISA && SCSI
1226 This is support for the PSI240i EIDE interface card which acts as a
1227 SCSI host adapter. Please read the SCSI-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here: the
1231 module will be called psi240i.
1233 config SCSI_QLOGIC_FAS
1234 tristate "Qlogic FAS SCSI support"
1235 depends on ISA && SCSI
1237 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1238 FastSCSI! cards as well as any other card based on the FASXX chip
1239 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1241 This driver does NOT support the PCI versions of these cards. The
1242 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1243 SCSI support"), below.
1245 Information about this driver is contained in
1246 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1247 SCSI-HOWTO, available from
1248 <http://www.tldp.org/docs.html#howto>.
1250 To compile this driver as a module, choose M here: the
1251 module will be called qlogicfas.
1253 config SCSI_QLOGIC_ISP
1254 tristate "Qlogic ISP SCSI support (old driver)"
1255 depends on PCI && SCSI && BROKEN
1257 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1258 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1259 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1261 If you say Y here, make sure to choose "BIOS" at the question "PCI
1264 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1265 should also read the SCSI-HOWTO, available from
1266 <http://www.tldp.org/docs.html#howto>.
1268 To compile this driver as a module, choose M here: the
1269 module will be called qlogicisp.
1271 These days the hardware is also supported by the more modern qla1280
1272 driver. In doubt use that one instead of qlogicisp.
1274 config SCSI_QLOGIC_FC
1275 tristate "Qlogic ISP FC SCSI support"
1276 depends on PCI && SCSI
1278 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1280 To compile this driver as a module, choose M here: the
1281 module will be called qlogicfc.
1283 config SCSI_QLOGIC_FC_FIRMWARE
1284 bool "Include loadable firmware in driver"
1285 depends on SCSI_QLOGIC_FC
1287 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1288 expanded LUN addressing and FcTape (FCP-2) support, in the
1289 qlogicfc driver. This is required on some platforms.
1291 config SCSI_QLOGIC_1280
1292 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1293 depends on PCI && SCSI
1295 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1297 To compile this driver as a module, choose M here: the
1298 module will be called qla1280.
1300 config SCSI_QLOGIC_1280_1040
1301 bool "Qlogic QLA 1020/1040 SCSI support"
1302 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1304 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1305 do not want to use the old driver. This option enables support in
1306 the qla1280 driver for those host adapters.
1308 config SCSI_QLOGICPTI
1309 tristate "PTI Qlogic, ISP Driver"
1310 depends on SBUS && SCSI
1312 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1313 controllers are known under Solaris as qpti and in the openprom as
1314 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1315 driven by a different driver.
1317 To compile this driver as a module, choose M here: the
1318 module will be called qlogicpti.
1320 source "drivers/scsi/qla2xxx/Kconfig"
1323 tristate "Emulex LightPulse Fibre Channel Support"
1324 depends on PCI && SCSI
1325 select SCSI_FC_ATTRS
1327 This lpfc driver supports the Emulex LightPulse
1328 Family of Fibre Channel PCI host adapters.
1331 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1332 depends on X86 && ISA && SCSI && BROKEN
1334 These are 8-bit SCSI controllers; the ST-01 is also supported by
1335 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1336 available from <http://www.tldp.org/docs.html#howto>. If it
1337 doesn't work out of the box, you may have to change some settings in
1338 <file:drivers/scsi/seagate.h>.
1340 To compile this driver as a module, choose M here: the
1341 module will be called seagate.
1343 # definitely looks not 64bit safe:
1345 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1346 depends on (EISA || MCA) && SCSI
1347 select SCSI_SPI_ATTRS
1349 This driver for NCR53c710 based SCSI host adapters.
1351 It currently supports Compaq EISA cards and NCR MCA cards
1353 config 53C700_IO_MAPPED
1355 depends on SCSI_SIM710
1358 config SCSI_SYM53C416
1359 tristate "Symbios 53c416 SCSI support"
1360 depends on ISA && SCSI
1362 This is support for the sym53c416 SCSI host adapter, the SCSI
1363 adapter that comes with some HP scanners. This driver requires that
1364 the sym53c416 is configured first using some sort of PnP
1365 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1366 are using isapnp then you need to compile this driver as a module
1367 and then load it using insmod after isapnp has run. The parameters
1368 of the configured card(s) should be passed to the driver. The format
1371 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1373 To compile this driver as a module, choose M here: the
1374 module will be called sym53c416.
1377 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1378 depends on PCI && SCSI && EXPERIMENTAL
1380 This driver supports PCI SCSI host adapters based on the ASIC
1381 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1383 This driver works, but is still in experimental status. So better
1384 have a bootable disk and a backup in case of emergency.
1386 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1388 To compile this driver as a module, choose M here: the
1389 module will be called dc395x.
1392 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1393 depends on PCI && SCSI
1395 This driver supports PCI SCSI host adapters based on the Am53C974A
1396 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1397 PCscsi/PCnet (Am53/79C974) solutions.
1399 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1401 Note that this driver does NOT support Tekram DC390W/U/F, which are
1402 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1404 To compile this driver as a module, choose M here: the
1405 module will be called tmscsim.
1408 tristate "Trantor T128/T128F/T228 SCSI support"
1409 depends on ISA && SCSI
1411 This is support for a SCSI host adapter. It is explained in section
1412 3.11 of the SCSI-HOWTO, available from
1413 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1414 of the box, you may have to change some settings in
1415 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1416 Adaptec, and some former Trantor products are being sold under the
1419 To compile this driver as a module, choose M here: the
1420 module will be called t128.
1423 tristate "UltraStor 14F/34F support"
1424 depends on ISA && SCSI && ISA_DMA_API
1426 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1427 The source at <file:drivers/scsi/u14-34f.c> contains some
1428 information about this hardware. If the driver doesn't work out of
1429 the box, you may have to change some settings in
1430 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1431 <http://www.tldp.org/docs.html#howto>. Note that there is also
1432 another driver for the same hardware: "UltraStor SCSI support",
1433 below. You should say Y to both only if you want 24F support as
1436 To compile this driver as a module, choose M here: the
1437 module will be called u14-34f.
1439 config SCSI_U14_34F_TAGGED_QUEUE
1440 bool "enable tagged command queueing"
1441 depends on SCSI_U14_34F
1443 This is a feature of SCSI-2 which improves performance: the host
1444 adapter can send several SCSI commands to a device's queue even if
1445 previous commands haven't finished yet.
1446 This is equivalent to the "u14-34f=tc:y" boot option.
1448 config SCSI_U14_34F_LINKED_COMMANDS
1449 bool "enable elevator sorting"
1450 depends on SCSI_U14_34F
1452 This option enables elevator sorting for all probed SCSI disks and
1453 CD-ROMs. It definitely reduces the average seek distance when doing
1454 random seeks, but this does not necessarily result in a noticeable
1455 performance improvement: your mileage may vary...
1456 This is equivalent to the "u14-34f=lc:y" boot option.
1458 config SCSI_U14_34F_MAX_TAGS
1459 int "maximum number of queued commands"
1460 depends on SCSI_U14_34F
1463 This specifies how many SCSI commands can be maximally queued for
1464 each probed SCSI device. You should reduce the default value of 8
1465 only if you have disks with buggy or limited tagged command support.
1466 Minimum is 2 and maximum is 14. This value is also the window size
1467 used by the elevator sorting option above. The effective value used
1468 by the driver for each probed SCSI device is reported at boot time.
1469 This is equivalent to the "u14-34f=mq:8" boot option.
1471 config SCSI_ULTRASTOR
1472 tristate "UltraStor SCSI support"
1473 depends on X86 && ISA && SCSI
1475 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1476 adapter family. This driver is explained in section 3.12 of the
1477 SCSI-HOWTO, available from
1478 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1479 of the box, you may have to change some settings in
1480 <file:drivers/scsi/ultrastor.h>.
1482 Note that there is also another driver for the same hardware:
1483 "UltraStor 14F/34F support", above.
1485 To compile this driver as a module, choose M here: the
1486 module will be called ultrastor.
1489 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1490 depends on PCI && SCSI && !64BIT
1492 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1493 SCSI host adapter. Please read the SCSI-HOWTO, available from
1494 <http://www.tldp.org/docs.html#howto>.
1496 To compile this driver as a module, choose M here: the
1497 module will be called nsp32.
1500 tristate "SCSI debugging host simulator"
1503 This is a host adapter simulator that can simulate multiple hosts
1504 each with multiple dummy SCSI devices (disks). It defaults to one
1505 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1506 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1507 dummy disks are simulated, they share the same kernel RAM for
1508 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1509 information. This driver is primarily of use to those testing the
1510 SCSI and block subsystems. If unsure, say N.
1513 tristate "MESH (Power Mac internal SCSI) support"
1514 depends on PPC32 && PPC_PMAC && SCSI
1516 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1517 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1518 other Power Macintoshes do). Say Y to include support for this SCSI
1521 To compile this driver as a module, choose M here: the
1522 module will be called mesh.
1524 config SCSI_MESH_SYNC_RATE
1525 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1526 depends on SCSI_MESH
1529 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1530 drives a bus which is entirely internal to the machine (such as the
1531 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1532 operation at up to 10 MB/s. On machines where the SCSI bus
1533 controlled by the MESH can have external devices connected, it is
1534 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1535 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1536 to disable synchronous operation.
1538 config SCSI_MESH_RESET_DELAY_MS
1539 int "initial bus reset delay (ms) (0 = no reset)"
1540 depends on SCSI_MESH
1543 config SCSI_MAC53C94
1544 tristate "53C94 (Power Mac external SCSI) support"
1545 depends on PPC32 && PPC_PMAC && SCSI
1547 On Power Macintoshes (and clones) with two SCSI buses, the external
1548 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1549 machines which only have one SCSI bus, such as the 7200, also use
1550 the 53C94. Say Y to include support for the 53C94.
1552 To compile this driver as a module, choose M here: the
1553 module will be called mac53c94.
1555 source "drivers/scsi/arm/Kconfig"
1558 bool "MIPS JAZZ FAS216 SCSI support"
1559 depends on MACH_JAZZ && SCSI
1561 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1562 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1566 tristate "A3000 WD33C93A support"
1567 depends on AMIGA && SCSI
1569 If you have an Amiga 3000 and have SCSI devices connected to the
1570 built-in SCSI controller, say Y. Otherwise, say N.
1572 To compile this driver as a module, choose M here: the
1573 module will be called wd33c93.
1576 tristate "A2091/A590 WD33C93A support"
1577 depends on ZORRO && SCSI
1579 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1582 To compile this driver as a module, choose M here: the
1583 module will be called wd33c93.
1586 tristate "GVP Series II WD33C93A support"
1587 depends on ZORRO && SCSI
1589 If you have a Great Valley Products Series II SCSI controller,
1590 answer Y. Also say Y if you have a later model of GVP SCSI
1591 controller (such as the GVP A4008 or a Combo board). Otherwise,
1592 answer N. This driver does NOT work for the T-Rex series of
1593 accelerators from TekMagic and GVP-M.
1595 To compile this driver as a module, choose M here: the
1596 module will be called gvp11.
1598 config CYBERSTORM_SCSI
1599 tristate "CyberStorm SCSI support"
1600 depends on ZORRO && SCSI
1602 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1603 accelerator board and the optional Cyberstorm SCSI controller,
1604 answer Y. Otherwise, say N.
1606 config CYBERSTORMII_SCSI
1607 tristate "CyberStorm Mk II SCSI support"
1608 depends on ZORRO && SCSI
1610 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1611 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1615 tristate "Blizzard 2060 SCSI support"
1616 depends on ZORRO && SCSI
1618 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1619 and want to use the onboard SCSI controller, say Y. Otherwise,
1623 tristate "Blizzard 1230IV/1260 SCSI support"
1624 depends on ZORRO && SCSI
1626 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1627 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1630 config FASTLANE_SCSI
1631 tristate "Fastlane SCSI support"
1632 depends on ZORRO && SCSI
1634 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1635 one in the near future, say Y to this question. Otherwise, say N.
1637 config SCSI_AMIGA7XX
1638 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1639 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1641 Support for various NCR53c710-based SCSI controllers on the Amiga.
1643 - the builtin SCSI controller on the Amiga 4000T,
1644 - the Amiga 4091 Zorro III SCSI-2 controller,
1645 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1647 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1648 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1649 accelerator card for the Amiga 1200,
1650 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1651 Note that all of the above SCSI controllers, except for the builtin
1652 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1653 bus, so you also have to enable Zorro bus support if you want to use
1657 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1658 depends on ZORRO && SCSI && EXPERIMENTAL
1660 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1661 Y to this question. If you're in doubt about whether you have one,
1663 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1666 tristate "Atari native SCSI support"
1667 depends on ATARI && SCSI && BROKEN
1669 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1670 Falcon, ...) say Y to get it supported. Of course also, if you have
1671 a compatible SCSI controller (e.g. for Medusa).
1673 To compile this driver as a module, choose M here: the
1674 module will be called atari_scsi.
1676 This driver supports both styles of NCR integration into the
1677 system: the TT style (separate DMA), and the Falcon style (via
1678 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1679 in the Hades (without DMA).
1681 config ATARI_SCSI_TOSHIBA_DELAY
1682 bool "Long delays for Toshiba CD-ROMs"
1683 depends on ATARI_SCSI
1685 This option increases the delay after a SCSI arbitration to
1686 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1687 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1688 would impact performance a bit, so say N.
1690 config ATARI_SCSI_RESET_BOOT
1691 bool "Reset SCSI-devices at boottime"
1692 depends on ATARI_SCSI
1694 Reset the devices on your Atari whenever it boots. This makes the
1695 boot process fractionally longer but may assist recovery from errors
1696 that leave the devices with SCSI operations partway completed.
1699 bool "Hades SCSI DMA emulator"
1700 depends on ATARI_SCSI && HADES
1702 This option enables code which emulates the TT SCSI DMA chip on the
1703 Hades. This increases the SCSI transfer rates at least ten times
1704 compared to PIO transfers.
1707 bool "Macintosh NCR5380 SCSI"
1708 depends on MAC && SCSI=y
1710 This is the NCR 5380 SCSI controller included on most of the 68030
1711 based Macintoshes. If you have one of these say Y and read the
1712 SCSI-HOWTO, available from
1713 <http://www.tldp.org/docs.html#howto>.
1716 tristate "Macintosh NCR53c9[46] SCSI"
1717 depends on MAC && SCSI
1719 This is the NCR 53c9x SCSI controller found on most of the 68040
1720 based Macintoshes. If you have one of these say Y and read the
1721 SCSI-HOWTO, available from
1722 <http://www.tldp.org/docs.html#howto>.
1724 To compile this driver as a module, choose M here: the
1725 module will be called mac_esp.
1728 bool "WD33C93 SCSI driver for MVME147"
1729 depends on MVME147 && SCSI=y
1731 Support for the on-board SCSI controller on the Motorola MVME147
1732 single-board computer.
1735 bool "NCR53C710 SCSI driver for MVME16x"
1736 depends on MVME16x && SCSI && BROKEN
1738 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1739 SCSI controller chip. Almost everyone using one of these boards
1740 will want to say Y to this question.
1742 config BVME6000_SCSI
1743 bool "NCR53C710 SCSI driver for BVME6000"
1744 depends on BVME6000 && SCSI && BROKEN
1746 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1747 SCSI controller chip. Almost everyone using one of these boards
1748 will want to say Y to this question.
1750 config SCSI_NCR53C7xx_FAST
1751 bool "allow FAST-SCSI [10MHz]"
1752 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1754 This will enable 10MHz FAST-SCSI transfers with your host
1755 adapter. Some systems have problems with that speed, so it's safest
1759 tristate "Sun3 NCR5380 SCSI"
1760 depends on SUN3 && SCSI && BROKEN
1762 This option will enable support for the OBIO (onboard io) NCR5380
1763 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1764 "Sun3" type VME scsi controllers also based on the NCR5380.
1765 General Linux information on the Sun 3 series (now discontinued)
1766 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1769 bool "Sun3x ESP SCSI"
1770 depends on SUN3X && SCSI=y
1772 The ESP was an on-board SCSI controller used on Sun 3/80
1773 machines. Say Y here to compile in support for it.
1776 tristate "Sparc ESP Scsi Driver"
1777 depends on SBUS && SCSI
1779 This is the driver for the Sun ESP SCSI host adapter. The ESP
1780 chipset is present in most SPARC SBUS-based computers.
1782 To compile this driver as a module, choose M here: the
1783 module will be called esp.
1785 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1788 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1789 depends on ARCH_S390 && QDIO && SCSI
1790 select SCSI_FC_ATTRS
1792 If you want to access SCSI devices attached to your IBM eServer
1793 zSeries by means of Fibre Channel interfaces say Y.
1794 For details please refer to the documentation provided by IBM at
1795 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1797 This driver is also available as a module. This module will be
1798 called zfcp. If you want to compile it as a module, say M here
1799 and read <file:Documentation/modules.txt>.
1803 source "drivers/scsi/pcmcia/Kconfig"