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"
234 If you wish to export transport-specific information about
235 each attached iSCSI device to sysfs, say Y.
240 menu "SCSI low-level drivers"
244 tristate "SGI WD93C93 SCSI Driver"
245 depends on SGI_IP22 && SCSI
247 If you have a Western Digital WD93 SCSI controller on
248 an SGI MIPS system, say Y. Otherwise, say N.
251 tristate "DEC NCR53C94 Scsi Driver"
252 depends on MACH_DECSTATION && SCSI && TC
254 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
255 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
258 tristate "DEC SII Scsi Driver"
259 depends on MACH_DECSTATION && SCSI && 32BIT
261 config BLK_DEV_3W_XXXX_RAID
262 tristate "3ware 5/6/7/8xxx ATA-RAID support"
263 depends on PCI && SCSI
265 3ware is the only hardware ATA-Raid product in Linux to date.
266 This card is 2,4, or 8 channel master mode support only.
267 SCSI support required!!!
269 <http://www.3ware.com/>
271 Please read the comments at the top of
272 <file:drivers/scsi/3w-xxxx.c>.
275 tristate "3ware 9xxx SATA-RAID support"
276 depends on PCI && SCSI
278 This driver supports the 9000 series 3ware SATA-RAID cards.
280 <http://www.amcc.com>
282 Please read the comments at the top of
283 <file:drivers/scsi/3w-9xxx.c>.
285 config SCSI_7000FASST
286 tristate "7000FASST SCSI support"
287 depends on ISA && SCSI && ISA_DMA_API
289 This driver supports the Western Digital 7000 SCSI host adapter
290 family. Some information is in the source:
291 <file:drivers/scsi/wd7000.c>.
293 To compile this driver as a module, choose M here: the
294 module will be called wd7000.
297 tristate "ACARD SCSI support"
298 depends on PCI && SCSI
300 This driver supports the ACARD SCSI host adapter.
301 Support Chip <ATP870 ATP876 ATP880 ATP885>
302 To compile this driver as a module, choose M here: the
303 module will be called atp870u.
306 tristate "Adaptec AHA152X/2825 support"
307 depends on ISA && SCSI && !64BIT
309 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
310 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
311 must be manually specified in this case.
313 It is explained in section 3.3 of the SCSI-HOWTO, available from
314 <http://www.tldp.org/docs.html#howto>. You might also want to
315 read the file <file:Documentation/scsi/aha152x.txt>.
317 To compile this driver as a module, choose M here: the
318 module will be called aha152x.
321 tristate "Adaptec AHA1542 support"
322 depends on ISA && SCSI && ISA_DMA_API
324 This is support for a SCSI host adapter. It is explained in section
325 3.4 of the SCSI-HOWTO, available from
326 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
327 purchased by Adaptec, and some former Trantor products are being
328 sold under the Adaptec name. If it doesn't work out of the box, you
329 may have to change some settings in <file:drivers/scsi/aha1542.h>.
331 To compile this driver as a module, choose M here: the
332 module will be called aha1542.
335 tristate "Adaptec AHA1740 support"
336 depends on EISA && SCSI
338 This is support for a SCSI host adapter. It is explained in section
339 3.5 of the SCSI-HOWTO, available from
340 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
341 of the box, you may have to change some settings in
342 <file:drivers/scsi/aha1740.h>.
344 To compile this driver as a module, choose M here: the
345 module will be called aha1740.
348 tristate "Adaptec AACRAID support"
349 depends on SCSI && PCI
351 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
353 config SCSI_AIC7XXX_OLD
354 tristate "Adaptec AIC7xxx support (old driver)"
355 depends on (ISA || EISA || PCI ) && SCSI
357 WARNING This driver is an older aic7xxx driver and is no longer
358 under active development. Adaptec, Inc. is writing a new driver to
359 take the place of this one, and it is recommended that whenever
360 possible, people should use the new Adaptec written driver instead
361 of this one. This driver will eventually be phased out entirely.
363 This is support for the various aic7xxx based Adaptec SCSI
364 controllers. These include the 274x EISA cards; 284x VLB cards;
365 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
366 motherboard based SCSI controllers from Adaptec. It does not support
367 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
368 support them. It does not support the 2920 cards from Adaptec that
369 use the Future Domain SCSI controller chip. For those cards, you
370 need the "Future Domain 16xx SCSI support" driver.
372 In general, if the controller is based on an Adaptec SCSI controller
373 chip from the aic777x series or the aic78xx series, this driver
374 should work. The only exception is the 7810 which is specifically
375 not supported (that's the RAID controller chip on the AAA-13x
378 Note that the AHA2920 SCSI host adapter is *not* supported by this
379 driver; choose "Future Domain 16xx SCSI support" instead if you have
382 Information on the configuration options for this controller can be
383 found by checking the help file for each of the available
384 configuration options. You should read
385 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
386 contacting the maintainer with any questions. The SCSI-HOWTO,
387 available from <http://www.tldp.org/docs.html#howto>, can also
390 To compile this driver as a module, choose M here: the
391 module will be called aic7xxx_old.
393 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
395 # All the I2O code and drivers do not seem to be 64bit safe.
397 tristate "Adaptec I2O RAID support "
398 depends on !64BIT && SCSI && PCI
400 This driver supports all of Adaptec's I2O based RAID controllers as
401 well as the DPT SmartRaid V cards. This is an Adaptec maintained
402 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
404 To compile this driver as a module, choose M here: the
405 module will be called dpt_i2o.
408 tristate "AdvanSys SCSI support"
409 depends on (ISA || EISA || PCI) && SCSI && BROKEN
411 This is a driver for all SCSI host adapters manufactured by
412 AdvanSys. It is documented in the kernel source in
413 <file:drivers/scsi/advansys.c>.
415 To compile this driver as a module, choose M here: the
416 module will be called advansys.
419 tristate "Always IN2000 SCSI support"
420 depends on ISA && SCSI
422 This is support for an ISA bus SCSI host adapter. You'll find more
423 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
424 out of the box, you may have to change the jumpers for IRQ or
427 To compile this driver as a module, choose M here: the
428 module will be called in2000.
430 source "drivers/scsi/megaraid/Kconfig.megaraid"
433 tristate "Serial ATA (SATA) support"
436 This driver family supports Serial ATA host controllers
441 config SCSI_SATA_AHCI
442 tristate "AHCI SATA support"
443 depends on SCSI_SATA && PCI
445 This option enables support for AHCI Serial ATA.
450 tristate "ServerWorks Frodo / Apple K2 SATA support"
451 depends on SCSI_SATA && PCI
453 This option enables support for Broadcom/Serverworks/Apple K2
459 tristate "Intel PIIX/ICH SATA support"
460 depends on SCSI_SATA && PCI
462 This option enables support for ICH5 Serial ATA.
463 If PATA support was enabled previously, this enables
464 support for select Intel PIIX/ICH PATA host controllers.
469 tristate "Marvell SATA support"
470 depends on SCSI_SATA && PCI && EXPERIMENTAL
472 This option enables support for the Marvell Serial ATA family.
473 Currently supports 88SX[56]0[48][01] chips.
478 tristate "NVIDIA SATA support"
479 depends on SCSI_SATA && PCI && EXPERIMENTAL
481 This option enables support for NVIDIA Serial ATA.
485 config SCSI_SATA_PROMISE
486 tristate "Promise SATA TX2/TX4 support"
487 depends on SCSI_SATA && PCI
489 This option enables support for Promise Serial ATA TX2/TX4.
493 config SCSI_SATA_QSTOR
494 tristate "Pacific Digital SATA QStor support"
495 depends on SCSI_SATA && PCI
497 This option enables support for Pacific Digital Serial ATA QStor.
502 tristate "Promise SATA SX4 support"
503 depends on SCSI_SATA && PCI && EXPERIMENTAL
505 This option enables support for Promise Serial ATA SX4.
510 tristate "Silicon Image SATA support"
511 depends on SCSI_SATA && PCI && EXPERIMENTAL
513 This option enables support for Silicon Image Serial ATA.
517 config SCSI_SATA_SIL24
518 tristate "Silicon Image 3124/3132 SATA support"
519 depends on SCSI_SATA && PCI && EXPERIMENTAL
521 This option enables support for Silicon Image 3124/3132 Serial ATA.
526 tristate "SiS 964/180 SATA support"
527 depends on SCSI_SATA && PCI && EXPERIMENTAL
529 This option enables support for SiS Serial ATA 964/180.
534 tristate "ULi Electronics SATA support"
535 depends on SCSI_SATA && PCI && EXPERIMENTAL
537 This option enables support for ULi Electronics SATA.
542 tristate "VIA SATA support"
543 depends on SCSI_SATA && PCI
545 This option enables support for VIA Serial ATA.
549 config SCSI_SATA_VITESSE
550 tristate "VITESSE VSC-7174 SATA support"
551 depends on SCSI_SATA && PCI
553 This option enables support for Vitesse VSC7174 Serial ATA.
558 tristate "BusLogic SCSI support"
559 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
561 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
562 Adapters. Consult the SCSI-HOWTO, available from
563 <http://www.tldp.org/docs.html#howto>, and the files
564 <file:Documentation/scsi/BusLogic.txt> and
565 <file:Documentation/scsi/FlashPoint.txt> for more information.
567 To compile this driver as a module, choose M here: the
568 module will be called BusLogic.
570 config SCSI_OMIT_FLASHPOINT
571 bool "Omit FlashPoint support"
572 depends on SCSI_BUSLOGIC
574 This option allows you to omit the FlashPoint support from the
575 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
576 substantial, so users of MultiMaster Host Adapters may wish to omit
580 # This is marked broken because it uses over 4kB of stack in
582 # 2076 CpqTsProcessIMQEntry
586 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
587 depends on PCI && SCSI && BROKEN
589 Say Y here to compile in support for the Compaq StorageWorks Fibre
590 Channel 64-bit/66Mhz Host Bus Adapter.
593 tristate "DMX3191D SCSI support"
594 depends on PCI && SCSI
596 This is support for Domex DMX3191D SCSI Host Adapters.
598 To compile this driver as a module, choose M here: the
599 module will be called dmx3191d.
602 tristate "DTC3180/3280 SCSI support"
603 depends on ISA && SCSI
605 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
606 the SCSI-HOWTO, available from
607 <http://www.tldp.org/docs.html#howto>, and the file
608 <file:Documentation/scsi/dtc3x80.txt>.
610 To compile this driver as a module, choose M here: the
611 module will be called dtc.
614 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
615 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
617 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
618 ISA and all EISA I/O addresses are probed looking for the "EATA"
619 signature. The addresses of all the PCI SCSI controllers reported
620 by the PCI subsystem are probed as well.
622 You want to read the start of <file:drivers/scsi/eata.c> and the
623 SCSI-HOWTO, available from
624 <http://www.tldp.org/docs.html#howto>.
626 To compile this driver as a module, choose M here: the
627 module will be called eata.
629 config SCSI_EATA_TAGGED_QUEUE
630 bool "enable tagged command queueing"
633 This is a feature of SCSI-2 which improves performance: the host
634 adapter can send several SCSI commands to a device's queue even if
635 previous commands haven't finished yet.
636 This is equivalent to the "eata=tc:y" boot option.
638 config SCSI_EATA_LINKED_COMMANDS
639 bool "enable elevator sorting"
642 This option enables elevator sorting for all probed SCSI disks and
643 CD-ROMs. It definitely reduces the average seek distance when doing
644 random seeks, but this does not necessarily result in a noticeable
645 performance improvement: your mileage may vary...
646 This is equivalent to the "eata=lc:y" boot option.
648 config SCSI_EATA_MAX_TAGS
649 int "maximum number of queued commands"
653 This specifies how many SCSI commands can be maximally queued for
654 each probed SCSI device. You should reduce the default value of 16
655 only if you have disks with buggy or limited tagged command support.
656 Minimum is 2 and maximum is 62. This value is also the window size
657 used by the elevator sorting option above. The effective value used
658 by the driver for each probed SCSI device is reported at boot time.
659 This is equivalent to the "eata=mq:8" boot option.
662 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
663 depends on (ISA || EISA || PCI) && SCSI && BROKEN
665 This driver supports all EATA-PIO protocol compliant SCSI Host
666 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
667 host adapters could also use this driver but are discouraged from
668 doing so, since this driver only supports hard disks and lacks
669 numerous features. You might want to have a look at the SCSI-HOWTO,
670 available from <http://www.tldp.org/docs.html#howto>.
672 To compile this driver as a module, choose M here: the
673 module will be called eata_pio.
675 config SCSI_FUTURE_DOMAIN
676 tristate "Future Domain 16xx SCSI/AHA-2920A support"
677 depends on (ISA || PCI) && SCSI
679 This is support for Future Domain's 16-bit SCSI host adapters
680 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
681 other adapters based on the Future Domain chipsets (Quantum
682 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
683 It is explained in section 3.7 of the SCSI-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>.
686 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
687 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
688 controller support"). This Future Domain driver works with the older
689 Adaptec AHA-2920A boards with a Future Domain chip on them.
691 To compile this driver as a module, choose M here: the
692 module will be called fdomain.
695 tristate "Future Domain MCS-600/700 SCSI support"
696 depends on MCA_LEGACY && SCSI
698 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
699 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
700 is identical to the MCS 700 and hence also supported by this driver.
701 This driver also supports the Reply SB16/SCSI card (the SCSI part).
702 It supports multiple adapters in the same system.
704 To compile this driver as a module, choose M here: the
705 module will be called fd_mcs.
708 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
709 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
711 Formerly called GDT SCSI Disk Array Controller Support.
713 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
714 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
715 in the kernel source in <file:drivers/scsi/gdth.c> and
716 <file:drivers/scsi/gdth.h.>
718 To compile this driver as a module, choose M here: the
719 module will be called gdth.
721 config SCSI_GENERIC_NCR5380
722 tristate "Generic NCR5380/53c400 SCSI PIO support"
723 depends on ISA && SCSI
725 This is a driver for the old NCR 53c80 series of SCSI controllers
726 on boards using PIO. Most boards such as the Trantor T130 fit this
727 category, along with a large number of ISA 8bit controllers shipped
728 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
729 you should select the specific driver for that card rather than
730 generic 5380 support.
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.
740 config SCSI_GENERIC_NCR5380_MMIO
741 tristate "Generic NCR5380/53c400 SCSI MMIO support"
742 depends on ISA && SCSI
744 This is a driver for the old NCR 53c80 series of SCSI controllers
745 on boards using memory mapped I/O.
746 It is explained in section 3.8 of the SCSI-HOWTO, available from
747 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
748 of the box, you may have to change some settings in
749 <file:drivers/scsi/g_NCR5380.h>.
751 To compile this driver as a module, choose M here: the
752 module will be called g_NCR5380_mmio.
754 config SCSI_GENERIC_NCR53C400
755 bool "Enable NCR53c400 extensions"
756 depends on SCSI_GENERIC_NCR5380
758 This enables certain optimizations for the NCR53c400 SCSI cards.
759 You might as well try it out. Note that this driver will only probe
760 for the Trantor T130B in its default configuration; you might have
761 to pass a command line option to the kernel at boot time if it does
762 not detect your card. See the file
763 <file:Documentation/scsi/g_NCR5380.txt> for details.
766 tristate "IBMMCA SCSI support"
767 depends on MCA_LEGACY && SCSI
769 This is support for the IBM SCSI adapter found in many of the PS/2
770 series computers. These machines have an MCA bus, so you need to
771 answer Y to "MCA support" as well and read
772 <file:Documentation/mca.txt>.
774 If the adapter isn't found during boot (a common problem for models
775 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
776 option, where <pun> is the id of the SCSI subsystem (usually 7, but
777 if that doesn't work check your reference diskette). Owners of
778 model 95 with a LED-matrix-display can in addition activate some
779 activity info like under OS/2, but more informative, by setting
780 'ibmmcascsi=display' as an additional kernel parameter. Try "man
781 bootparam" or see the documentation of your boot loader about how to
782 pass options to the kernel.
784 To compile this driver as a module, choose M here: the
785 module will be called ibmmca.
787 config IBMMCA_SCSI_ORDER_STANDARD
788 bool "Standard SCSI-order"
789 depends on SCSI_IBMMCA
791 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
792 are assigned to the drive letters, starting with the lowest SCSI-id
793 (physical number -- pun) to be drive C:, as seen from DOS and
794 similar operating systems. When looking into papers describing the
795 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
796 The SCSI-standard follows a hardware-hierarchy which says that id 7
797 has the highest priority and id 0 the lowest. Therefore, the host
798 adapters are still today everywhere placed as SCSI-id 7 by default.
799 In the SCSI-standard, the drive letters express the priority of the
800 disk. C: should be the hard disk, or a partition on it, with the
801 highest priority. This must therefore be the disk with the highest
802 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
803 original definition of the SCSI-standard as also industrial- and
804 process-control-machines, like VME-CPUs running under realtime-OSes
805 (e.g. LynxOS, OS9) do.
807 If you like to run Linux on your MCA-machine with the same
808 assignment of hard disks as seen from e.g. DOS or OS/2 on your
809 machine, which is in addition conformant to the SCSI-standard, you
810 must say Y here. This is also necessary for MCA-Linux users who want
811 to keep downward compatibility to older releases of the
812 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
815 If you like to have the lowest SCSI-id assigned as drive C:, as
816 modern SCSI-BIOSes do, which does not conform to the standard, but
817 is widespread and common in the PC-world of today, you must say N
818 here. If unsure, say Y.
820 config IBMMCA_SCSI_DEV_RESET
821 bool "Reset SCSI-devices at boottime"
822 depends on SCSI_IBMMCA
824 By default, SCSI-devices are reset when the machine is powered on.
825 However, some devices exist, like special-control-devices,
826 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
827 not reset when switched on. If you say Y here, each device connected
828 to your SCSI-bus will be issued a reset-command after it has been
829 probed, while the kernel is booting. This may cause problems with
830 more modern devices, like hard disks, which do not appreciate these
831 reset commands, and can cause your system to hang. So say Y only if
832 you know that one of your older devices needs it; N is the safe
836 tristate "IBM ServeRAID support"
837 depends on PCI && SCSI
839 This is support for the IBM ServeRAID hardware RAID controllers.
840 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
841 for more information. If this driver does not work correctly
842 without modification please contact the author by email at
843 <ipslinux@adaptec.com>.
845 To compile this driver as a module, choose M here: the
846 module will be called ips.
849 tristate "IBM Virtual SCSI support"
850 depends on PPC_PSERIES || PPC_ISERIES
852 This is the IBM POWER Virtual SCSI Client
854 To compile this driver as a module, choose M here: the
855 module will be called ibmvscsic.
858 tristate "Initio 9100U(W) support"
859 depends on PCI && SCSI
861 This is support for the Initio 91XXU(W) SCSI host adapter. Please
862 read the SCSI-HOWTO, available from
863 <http://www.tldp.org/docs.html#howto>.
865 To compile this driver as a module, choose M here: the
866 module will be called initio.
869 tristate "Initio INI-A100U2W support"
870 depends on PCI && SCSI
872 This is support for the Initio INI-A100U2W SCSI host adapter.
873 Please read the SCSI-HOWTO, available from
874 <http://www.tldp.org/docs.html#howto>.
876 To compile this driver as a module, choose M here: the
877 module will be called a100u2w.
880 tristate "IOMEGA parallel port (ppa - older drives)"
881 depends on SCSI && PARPORT
883 This driver supports older versions of IOMEGA's parallel port ZIP
884 drive (a 100 MB removable media device).
886 Note that you can say N here if you have the SCSI version of the ZIP
887 drive: it will be supported automatically if you said Y to the
888 generic "SCSI disk support", above.
890 If you have the ZIP Plus drive or a more recent parallel port ZIP
891 drive (if the supplied cable with the drive is labeled "AutoDetect")
892 then you should say N here and Y to "IOMEGA parallel port (imm -
893 newer drives)", below.
895 For more information about this driver and how to use it you should
896 read the file <file:Documentation/scsi/ppa.txt>. You should also read
897 the SCSI-HOWTO, which is available from
898 <http://www.tldp.org/docs.html#howto>. If you use this driver,
899 you will still be able to use the parallel port for other tasks,
900 such as a printer; it is safe to compile both drivers into the
903 To compile this driver as a module, choose M here: the
904 module will be called ppa.
907 tristate "IOMEGA parallel port (imm - newer drives)"
908 depends on SCSI && PARPORT
910 This driver supports newer versions of IOMEGA's parallel port ZIP
911 drive (a 100 MB removable media device).
913 Note that you can say N here if you have the SCSI version of the ZIP
914 drive: it will be supported automatically if you said Y to the
915 generic "SCSI disk support", above.
917 If you have the ZIP Plus drive or a more recent parallel port ZIP
918 drive (if the supplied cable with the drive is labeled "AutoDetect")
919 then you should say Y here; if you have an older ZIP drive, say N
920 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
922 For more information about this driver and how to use it you should
923 read the file <file:Documentation/scsi/ppa.txt>. You should also read
924 the SCSI-HOWTO, which is available from
925 <http://www.tldp.org/docs.html#howto>. If you use this driver,
926 you will still be able to use the parallel port for other tasks,
927 such as a printer; it is safe to compile both drivers into the
930 To compile this driver as a module, choose M here: the
931 module will be called imm.
933 config SCSI_IZIP_EPP16
934 bool "ppa/imm option - Use slow (but safe) EPP-16"
935 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
937 EPP (Enhanced Parallel Port) is a standard for parallel ports which
938 allows them to act as expansion buses that can handle up to 64
941 Some parallel port chipsets are slower than their motherboard, and
942 so we have to control the state of the chipset's FIFO queue every
943 now and then to avoid data loss. This will be done if you say Y
946 Generally, saying Y is the safe option and slows things down a bit.
948 config SCSI_IZIP_SLOW_CTR
949 bool "ppa/imm option - Assume slow parport control register"
950 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
952 Some parallel ports are known to have excessive delays between
953 changing the parallel port control register and good data being
954 available on the parallel port data/status register. This option
955 forces a small delay (1.0 usec to be exact) after changing the
956 control register to let things settle out. Enabling this option may
957 result in a big drop in performance but some very old parallel ports
958 (found in 386 vintage machines) will not work properly.
960 Generally, saying N is fine.
962 config SCSI_NCR53C406A
963 tristate "NCR53c406a SCSI support"
964 depends on ISA && SCSI
966 This is support for the NCR53c406a SCSI host adapter. For user
967 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
968 in the kernel source. Also read the SCSI-HOWTO, available from
969 <http://www.tldp.org/docs.html#howto>.
971 To compile this driver as a module, choose M here: the
972 module will be called NCR53c406.
975 tristate "NCR Dual 700 MCA SCSI support"
976 depends on MCA && SCSI
977 select SCSI_SPI_ATTRS
979 This is a driver for the MicroChannel Dual 700 card produced by
980 NCR and commonly used in 345x/35xx/4100 class machines. It always
981 tries to negotiate sync and uses tag command queueing.
983 Unless you have an NCR manufactured machine, the chances are that
984 you do not have this SCSI card, so say N.
987 tristate "HP Lasi SCSI support for 53c700/710"
988 depends on GSC && SCSI
989 select SCSI_SPI_ATTRS
991 This is a driver for the SCSI controller in the Lasi chip found in
992 many PA-RISC workstations & servers. If you do not know whether you
993 have a Lasi chip, it is safe to say "Y" here.
995 config 53C700_LE_ON_BE
997 depends on SCSI_LASI700
1000 config SCSI_SYM53C8XX_2
1001 tristate "SYM53C8XX Version 2 SCSI support"
1002 depends on PCI && SCSI
1003 select SCSI_SPI_ATTRS
1005 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1006 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1007 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1008 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1009 controllers; you need to use the Fusion MPT driver for that.
1011 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1014 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1015 int "DMA addressing mode"
1016 depends on SCSI_SYM53C8XX_2
1019 This option only applies to PCI-SCSI chips that are PCI DAC
1020 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1022 When set to 0, the driver will program the chip to only perform
1023 32-bit DMA. When set to 1, the chip will be able to perform DMA
1024 to addresses up to 1TB. When set to 2, the driver supports the
1025 full 64-bit DMA address range, but can only address 16 segments
1026 of 4 GB each. This limits the total addressable range to 64 GB.
1028 Most machines with less than 4GB of memory should use a setting
1029 of 0 for best performance. If your machine has 4GB of memory
1030 or more, you should set this option to 1 (the default).
1032 The still experimental value 2 (64 bit DMA addressing with 16
1033 x 4GB segments limitation) can be used on systems that require
1034 PCI address bits past bit 39 to be set for the addressing of
1035 memory using PCI DAC cycles.
1037 config SCSI_SYM53C8XX_DEFAULT_TAGS
1038 int "default tagged command queue depth"
1039 depends on SCSI_SYM53C8XX_2
1042 This is the default value of the command queue depth the
1043 driver will announce to the generic SCSI layer for devices
1044 that support tagged command queueing. This value can be changed
1045 from the boot command line. This is a soft limit that cannot
1046 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1048 config SCSI_SYM53C8XX_MAX_TAGS
1049 int "maximum number of queued commands"
1050 depends on SCSI_SYM53C8XX_2
1053 This option allows you to specify the maximum number of commands
1054 that can be queued to any device, when tagged command queuing is
1055 possible. The driver supports up to 256 queued commands per device.
1056 This value is used as a compiled-in hard limit.
1058 config SCSI_SYM53C8XX_IOMAPPED
1060 depends on SCSI_SYM53C8XX_2
1062 If you say Y here, the driver will use port IO to access
1063 the card. This is significantly slower then using memory
1064 mapped IO. Most people should answer N.
1067 tristate "IBM Power Linux RAID adapter support"
1068 depends on PCI && SCSI
1071 This driver supports the IBM Power Linux family RAID adapters.
1072 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1073 as IBM iSeries 5702, 5703, 5709, and 570A.
1075 config SCSI_IPR_TRACE
1076 bool "enable driver internal trace"
1079 If you say Y here, the driver will trace all commands issued
1080 to the adapter. Performance impact is minimal. Trace can be
1081 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1083 config SCSI_IPR_DUMP
1084 bool "enable adapter dump support"
1087 If you say Y here, the driver will support adapter crash dump.
1088 If you enable this support, the iprdump daemon can be used
1089 to capture adapter failure analysis information.
1092 tristate "Zalon SCSI support"
1093 depends on GSC && SCSI
1094 select SCSI_SPI_ATTRS
1096 The Zalon is a GSC/HSC bus interface chip that sits between the
1097 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1098 C110, J200, J210 and some D, K & R-class machines. It's also
1099 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1100 Say Y here if you have one of these machines or cards.
1102 config SCSI_NCR_Q720
1103 tristate "NCR Quad 720 MCA SCSI support"
1104 depends on MCA && SCSI
1105 select SCSI_SPI_ATTRS
1107 This is a driver for the MicroChannel Quad 720 card produced by
1108 NCR and commonly used in 345x/35xx/4100 class machines. It always
1109 tries to negotiate sync and uses tag command queueing.
1111 Unless you have an NCR manufactured machine, the chances are that
1112 you do not have this SCSI card, so say N.
1114 config SCSI_NCR53C8XX_DEFAULT_TAGS
1115 int " default tagged command queue depth"
1116 depends on SCSI_ZALON || SCSI_NCR_Q720
1119 "Tagged command queuing" is a feature of SCSI-2 which improves
1120 performance: the host adapter can send several SCSI commands to a
1121 device's queue even if previous commands haven't finished yet.
1122 Because the device is intelligent, it can optimize its operations
1123 (like head positioning) based on its own request queue. Some SCSI
1124 devices don't implement this properly; if you want to disable this
1125 feature, enter 0 or 1 here (it doesn't matter which).
1127 The default value is 8 and should be supported by most hard disks.
1128 This value can be overridden from the boot command line using the
1129 'tags' option as follows (example):
1130 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1131 4, set queue depth to 16 for target 2 and target 3 on controller 0
1132 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1134 The normal answer therefore is to go with the default 8 and to use
1135 a boot command line option for devices that need to use a different
1136 command queue depth.
1138 There is no safe option other than using good SCSI devices.
1140 config SCSI_NCR53C8XX_MAX_TAGS
1141 int " maximum number of queued commands"
1142 depends on SCSI_ZALON || SCSI_NCR_Q720
1145 This option allows you to specify the maximum number of commands
1146 that can be queued to any device, when tagged command queuing is
1147 possible. The default value is 32. Minimum is 2, maximum is 64.
1148 Modern hard disks are able to support 64 tags and even more, but
1149 do not seem to be faster when more than 32 tags are being used.
1151 So, the normal answer here is to go with the default value 32 unless
1152 you are using very large hard disks with large cache (>= 1 MB) that
1153 are able to take advantage of more than 32 tagged commands.
1155 There is no safe option and the default answer is recommended.
1157 config SCSI_NCR53C8XX_SYNC
1158 int " synchronous transfers frequency in MHz"
1159 depends on SCSI_ZALON || SCSI_NCR_Q720
1162 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1163 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1164 are respectively the maximum data transfer rates in mega-transfers
1165 per second for each class. For example, a FAST-20 Wide 16 device is
1166 able to transfer data at 20 million 16 bit packets per second for a
1167 total rate of 40 MB/s.
1169 You may specify 0 if you want to only use asynchronous data
1170 transfers. This is the safest and slowest option. Otherwise, specify
1171 a value between 5 and 80, depending on the capability of your SCSI
1172 controller. The higher the number, the faster the data transfer.
1173 Note that 80 should normally be ok since the driver decreases the
1174 value automatically according to the controller's capabilities.
1176 Your answer to this question is ignored for controllers with NVRAM,
1177 since the driver will get this information from the user set-up. It
1178 also can be overridden using a boot setup option, as follows
1179 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1180 for FAST-20 synchronous data transfer (20 mega-transfers per
1183 The normal answer therefore is not to go with the default but to
1184 select the maximum value 80 allowing the driver to use the maximum
1185 value supported by each controller. If this causes problems with
1186 your SCSI devices, you should come back and decrease the value.
1188 There is no safe option other than using good cabling, right
1189 terminations and SCSI conformant devices.
1191 config SCSI_NCR53C8XX_PROFILE
1192 bool " enable profiling"
1193 depends on SCSI_ZALON || SCSI_NCR_Q720
1195 This option allows you to enable profiling information gathering.
1196 These statistics are not very accurate due to the low frequency
1197 of the kernel clock (100 Hz on i386) and have performance impact
1198 on systems that use very fast devices.
1200 The normal answer therefore is N.
1202 config SCSI_NCR53C8XX_NO_DISCONNECT
1203 bool " not allow targets to disconnect"
1204 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1206 This option is only provided for safety if you suspect some SCSI
1207 device of yours to not support properly the target-disconnect
1208 feature. In that case, you would say Y here. In general however, to
1209 not allow targets to disconnect is not reasonable if there is more
1210 than 1 device on a SCSI bus. The normal answer therefore is N.
1212 config SCSI_MCA_53C9X
1213 tristate "NCR MCA 53C9x SCSI support"
1214 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1216 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1217 controller based on the NCR 53C94. This driver will allow use of
1218 the controller on the 3550, and very possibly others.
1220 To compile this driver as a module, choose M here: the
1221 module will be called mca_53c9x.
1224 tristate "PAS16 SCSI support"
1225 depends on ISA && SCSI
1227 This is support for a SCSI host adapter. It is explained in section
1228 3.10 of the SCSI-HOWTO, available from
1229 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1230 of the box, you may have to change some settings in
1231 <file:drivers/scsi/pas16.h>.
1233 To compile this driver as a module, choose M here: the
1234 module will be called pas16.
1237 tristate "PSI240i support"
1238 depends on ISA && SCSI
1240 This is support for the PSI240i EIDE interface card which acts as a
1241 SCSI host adapter. Please read the SCSI-HOWTO, available from
1242 <http://www.tldp.org/docs.html#howto>.
1244 To compile this driver as a module, choose M here: the
1245 module will be called psi240i.
1247 config SCSI_QLOGIC_FAS
1248 tristate "Qlogic FAS SCSI support"
1249 depends on ISA && SCSI
1251 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1252 FastSCSI! cards as well as any other card based on the FASXX chip
1253 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1255 This driver does NOT support the PCI versions of these cards. The
1256 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1257 SCSI support"), below.
1259 Information about this driver is contained in
1260 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1261 SCSI-HOWTO, available from
1262 <http://www.tldp.org/docs.html#howto>.
1264 To compile this driver as a module, choose M here: the
1265 module will be called qlogicfas.
1267 config SCSI_QLOGIC_ISP
1268 tristate "Qlogic ISP SCSI support (old driver)"
1269 depends on PCI && SCSI && BROKEN
1271 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1272 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1273 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1275 If you say Y here, make sure to choose "BIOS" at the question "PCI
1278 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1279 should also read the SCSI-HOWTO, available from
1280 <http://www.tldp.org/docs.html#howto>.
1282 To compile this driver as a module, choose M here: the
1283 module will be called qlogicisp.
1285 These days the hardware is also supported by the more modern qla1280
1286 driver. In doubt use that one instead of qlogicisp.
1288 config SCSI_QLOGIC_FC
1289 tristate "Qlogic ISP FC SCSI support"
1290 depends on PCI && SCSI
1292 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1294 To compile this driver as a module, choose M here: the
1295 module will be called qlogicfc.
1297 config SCSI_QLOGIC_FC_FIRMWARE
1298 bool "Include loadable firmware in driver"
1299 depends on SCSI_QLOGIC_FC
1301 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1302 expanded LUN addressing and FcTape (FCP-2) support, in the
1303 qlogicfc driver. This is required on some platforms.
1305 config SCSI_QLOGIC_1280
1306 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1307 depends on PCI && SCSI
1309 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1311 To compile this driver as a module, choose M here: the
1312 module will be called qla1280.
1314 config SCSI_QLOGIC_1280_1040
1315 bool "Qlogic QLA 1020/1040 SCSI support"
1316 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1318 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1319 do not want to use the old driver. This option enables support in
1320 the qla1280 driver for those host adapters.
1322 config SCSI_QLOGICPTI
1323 tristate "PTI Qlogic, ISP Driver"
1324 depends on SBUS && SCSI
1326 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1327 controllers are known under Solaris as qpti and in the openprom as
1328 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1329 driven by a different driver.
1331 To compile this driver as a module, choose M here: the
1332 module will be called qlogicpti.
1334 source "drivers/scsi/qla2xxx/Kconfig"
1337 tristate "Emulex LightPulse Fibre Channel Support"
1338 depends on PCI && SCSI
1339 select SCSI_FC_ATTRS
1341 This lpfc driver supports the Emulex LightPulse
1342 Family of Fibre Channel PCI host adapters.
1345 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1346 depends on X86 && ISA && SCSI && BROKEN
1348 These are 8-bit SCSI controllers; the ST-01 is also supported by
1349 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1350 available from <http://www.tldp.org/docs.html#howto>. If it
1351 doesn't work out of the box, you may have to change some settings in
1352 <file:drivers/scsi/seagate.h>.
1354 To compile this driver as a module, choose M here: the
1355 module will be called seagate.
1357 # definitely looks not 64bit safe:
1359 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1360 depends on (EISA || MCA) && SCSI
1361 select SCSI_SPI_ATTRS
1363 This driver for NCR53c710 based SCSI host adapters.
1365 It currently supports Compaq EISA cards and NCR MCA cards
1367 config 53C700_IO_MAPPED
1369 depends on SCSI_SIM710
1372 config SCSI_SYM53C416
1373 tristate "Symbios 53c416 SCSI support"
1374 depends on ISA && SCSI
1376 This is support for the sym53c416 SCSI host adapter, the SCSI
1377 adapter that comes with some HP scanners. This driver requires that
1378 the sym53c416 is configured first using some sort of PnP
1379 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1380 are using isapnp then you need to compile this driver as a module
1381 and then load it using insmod after isapnp has run. The parameters
1382 of the configured card(s) should be passed to the driver. The format
1385 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1387 To compile this driver as a module, choose M here: the
1388 module will be called sym53c416.
1391 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1392 depends on PCI && SCSI && EXPERIMENTAL
1394 This driver supports PCI SCSI host adapters based on the ASIC
1395 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1397 This driver works, but is still in experimental status. So better
1398 have a bootable disk and a backup in case of emergency.
1400 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1402 To compile this driver as a module, choose M here: the
1403 module will be called dc395x.
1406 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1407 depends on PCI && SCSI
1409 This driver supports PCI SCSI host adapters based on the Am53C974A
1410 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1411 PCscsi/PCnet (Am53/79C974) solutions.
1413 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1415 Note that this driver does NOT support Tekram DC390W/U/F, which are
1416 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1418 To compile this driver as a module, choose M here: the
1419 module will be called tmscsim.
1422 tristate "Trantor T128/T128F/T228 SCSI support"
1423 depends on ISA && SCSI
1425 This is support for a SCSI host adapter. It is explained in section
1426 3.11 of the SCSI-HOWTO, available from
1427 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1428 of the box, you may have to change some settings in
1429 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1430 Adaptec, and some former Trantor products are being sold under the
1433 To compile this driver as a module, choose M here: the
1434 module will be called t128.
1437 tristate "UltraStor 14F/34F support"
1438 depends on ISA && SCSI && ISA_DMA_API
1440 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1441 The source at <file:drivers/scsi/u14-34f.c> contains some
1442 information about this hardware. If the driver doesn't work out of
1443 the box, you may have to change some settings in
1444 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1445 <http://www.tldp.org/docs.html#howto>. Note that there is also
1446 another driver for the same hardware: "UltraStor SCSI support",
1447 below. You should say Y to both only if you want 24F support as
1450 To compile this driver as a module, choose M here: the
1451 module will be called u14-34f.
1453 config SCSI_U14_34F_TAGGED_QUEUE
1454 bool "enable tagged command queueing"
1455 depends on SCSI_U14_34F
1457 This is a feature of SCSI-2 which improves performance: the host
1458 adapter can send several SCSI commands to a device's queue even if
1459 previous commands haven't finished yet.
1460 This is equivalent to the "u14-34f=tc:y" boot option.
1462 config SCSI_U14_34F_LINKED_COMMANDS
1463 bool "enable elevator sorting"
1464 depends on SCSI_U14_34F
1466 This option enables elevator sorting for all probed SCSI disks and
1467 CD-ROMs. It definitely reduces the average seek distance when doing
1468 random seeks, but this does not necessarily result in a noticeable
1469 performance improvement: your mileage may vary...
1470 This is equivalent to the "u14-34f=lc:y" boot option.
1472 config SCSI_U14_34F_MAX_TAGS
1473 int "maximum number of queued commands"
1474 depends on SCSI_U14_34F
1477 This specifies how many SCSI commands can be maximally queued for
1478 each probed SCSI device. You should reduce the default value of 8
1479 only if you have disks with buggy or limited tagged command support.
1480 Minimum is 2 and maximum is 14. This value is also the window size
1481 used by the elevator sorting option above. The effective value used
1482 by the driver for each probed SCSI device is reported at boot time.
1483 This is equivalent to the "u14-34f=mq:8" boot option.
1485 config SCSI_ULTRASTOR
1486 tristate "UltraStor SCSI support"
1487 depends on X86 && ISA && SCSI
1489 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1490 adapter family. This driver is explained in section 3.12 of the
1491 SCSI-HOWTO, available from
1492 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1493 of the box, you may have to change some settings in
1494 <file:drivers/scsi/ultrastor.h>.
1496 Note that there is also another driver for the same hardware:
1497 "UltraStor 14F/34F support", above.
1499 To compile this driver as a module, choose M here: the
1500 module will be called ultrastor.
1503 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1504 depends on PCI && SCSI && !64BIT
1506 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1507 SCSI host adapter. Please read the SCSI-HOWTO, available from
1508 <http://www.tldp.org/docs.html#howto>.
1510 To compile this driver as a module, choose M here: the
1511 module will be called nsp32.
1514 tristate "SCSI debugging host simulator"
1517 This is a host adapter simulator that can simulate multiple hosts
1518 each with multiple dummy SCSI devices (disks). It defaults to one
1519 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1520 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1521 dummy disks are simulated, they share the same kernel RAM for
1522 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1523 information. This driver is primarily of use to those testing the
1524 SCSI and block subsystems. If unsure, say N.
1527 tristate "MESH (Power Mac internal SCSI) support"
1528 depends on PPC32 && PPC_PMAC && SCSI
1530 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1531 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1532 other Power Macintoshes do). Say Y to include support for this SCSI
1535 To compile this driver as a module, choose M here: the
1536 module will be called mesh.
1538 config SCSI_MESH_SYNC_RATE
1539 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1540 depends on SCSI_MESH
1543 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1544 drives a bus which is entirely internal to the machine (such as the
1545 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1546 operation at up to 10 MB/s. On machines where the SCSI bus
1547 controlled by the MESH can have external devices connected, it is
1548 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1549 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1550 to disable synchronous operation.
1552 config SCSI_MESH_RESET_DELAY_MS
1553 int "initial bus reset delay (ms) (0 = no reset)"
1554 depends on SCSI_MESH
1557 config SCSI_MAC53C94
1558 tristate "53C94 (Power Mac external SCSI) support"
1559 depends on PPC32 && PPC_PMAC && SCSI
1561 On Power Macintoshes (and clones) with two SCSI buses, the external
1562 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1563 machines which only have one SCSI bus, such as the 7200, also use
1564 the 53C94. Say Y to include support for the 53C94.
1566 To compile this driver as a module, choose M here: the
1567 module will be called mac53c94.
1569 source "drivers/scsi/arm/Kconfig"
1572 bool "MIPS JAZZ FAS216 SCSI support"
1573 depends on MACH_JAZZ && SCSI
1575 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1576 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1580 tristate "A3000 WD33C93A support"
1581 depends on AMIGA && SCSI
1583 If you have an Amiga 3000 and have SCSI devices connected to the
1584 built-in SCSI controller, say Y. Otherwise, say N.
1586 To compile this driver as a module, choose M here: the
1587 module will be called wd33c93.
1590 tristate "A2091/A590 WD33C93A support"
1591 depends on ZORRO && SCSI
1593 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1596 To compile this driver as a module, choose M here: the
1597 module will be called wd33c93.
1600 tristate "GVP Series II WD33C93A support"
1601 depends on ZORRO && SCSI
1603 If you have a Great Valley Products Series II SCSI controller,
1604 answer Y. Also say Y if you have a later model of GVP SCSI
1605 controller (such as the GVP A4008 or a Combo board). Otherwise,
1606 answer N. This driver does NOT work for the T-Rex series of
1607 accelerators from TekMagic and GVP-M.
1609 To compile this driver as a module, choose M here: the
1610 module will be called gvp11.
1612 config CYBERSTORM_SCSI
1613 tristate "CyberStorm SCSI support"
1614 depends on ZORRO && SCSI
1616 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1617 accelerator board and the optional Cyberstorm SCSI controller,
1618 answer Y. Otherwise, say N.
1620 config CYBERSTORMII_SCSI
1621 tristate "CyberStorm Mk II SCSI support"
1622 depends on ZORRO && SCSI
1624 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1625 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1629 tristate "Blizzard 2060 SCSI support"
1630 depends on ZORRO && SCSI
1632 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1633 and want to use the onboard SCSI controller, say Y. Otherwise,
1637 tristate "Blizzard 1230IV/1260 SCSI support"
1638 depends on ZORRO && SCSI
1640 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1641 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1644 config FASTLANE_SCSI
1645 tristate "Fastlane SCSI support"
1646 depends on ZORRO && SCSI
1648 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1649 one in the near future, say Y to this question. Otherwise, say N.
1651 config SCSI_AMIGA7XX
1652 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1653 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1655 Support for various NCR53c710-based SCSI controllers on the Amiga.
1657 - the builtin SCSI controller on the Amiga 4000T,
1658 - the Amiga 4091 Zorro III SCSI-2 controller,
1659 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1661 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1662 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1663 accelerator card for the Amiga 1200,
1664 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1665 Note that all of the above SCSI controllers, except for the builtin
1666 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1667 bus, so you also have to enable Zorro bus support if you want to use
1671 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1672 depends on ZORRO && SCSI && EXPERIMENTAL
1674 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1675 Y to this question. If you're in doubt about whether you have one,
1677 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1680 tristate "Atari native SCSI support"
1681 depends on ATARI && SCSI && BROKEN
1683 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1684 Falcon, ...) say Y to get it supported. Of course also, if you have
1685 a compatible SCSI controller (e.g. for Medusa).
1687 To compile this driver as a module, choose M here: the
1688 module will be called atari_scsi.
1690 This driver supports both styles of NCR integration into the
1691 system: the TT style (separate DMA), and the Falcon style (via
1692 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1693 in the Hades (without DMA).
1695 config ATARI_SCSI_TOSHIBA_DELAY
1696 bool "Long delays for Toshiba CD-ROMs"
1697 depends on ATARI_SCSI
1699 This option increases the delay after a SCSI arbitration to
1700 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1701 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1702 would impact performance a bit, so say N.
1704 config ATARI_SCSI_RESET_BOOT
1705 bool "Reset SCSI-devices at boottime"
1706 depends on ATARI_SCSI
1708 Reset the devices on your Atari whenever it boots. This makes the
1709 boot process fractionally longer but may assist recovery from errors
1710 that leave the devices with SCSI operations partway completed.
1713 bool "Hades SCSI DMA emulator"
1714 depends on ATARI_SCSI && HADES
1716 This option enables code which emulates the TT SCSI DMA chip on the
1717 Hades. This increases the SCSI transfer rates at least ten times
1718 compared to PIO transfers.
1721 bool "Macintosh NCR5380 SCSI"
1722 depends on MAC && SCSI=y
1724 This is the NCR 5380 SCSI controller included on most of the 68030
1725 based Macintoshes. If you have one of these say Y and read the
1726 SCSI-HOWTO, available from
1727 <http://www.tldp.org/docs.html#howto>.
1730 tristate "Macintosh NCR53c9[46] SCSI"
1731 depends on MAC && SCSI
1733 This is the NCR 53c9x SCSI controller found on most of the 68040
1734 based Macintoshes. If you have one of these say Y and read the
1735 SCSI-HOWTO, available from
1736 <http://www.tldp.org/docs.html#howto>.
1738 To compile this driver as a module, choose M here: the
1739 module will be called mac_esp.
1742 bool "WD33C93 SCSI driver for MVME147"
1743 depends on MVME147 && SCSI=y
1745 Support for the on-board SCSI controller on the Motorola MVME147
1746 single-board computer.
1749 bool "NCR53C710 SCSI driver for MVME16x"
1750 depends on MVME16x && SCSI && BROKEN
1752 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1753 SCSI controller chip. Almost everyone using one of these boards
1754 will want to say Y to this question.
1756 config BVME6000_SCSI
1757 bool "NCR53C710 SCSI driver for BVME6000"
1758 depends on BVME6000 && SCSI && BROKEN
1760 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1761 SCSI controller chip. Almost everyone using one of these boards
1762 will want to say Y to this question.
1764 config SCSI_NCR53C7xx_FAST
1765 bool "allow FAST-SCSI [10MHz]"
1766 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1768 This will enable 10MHz FAST-SCSI transfers with your host
1769 adapter. Some systems have problems with that speed, so it's safest
1773 tristate "Sun3 NCR5380 SCSI"
1774 depends on SUN3 && SCSI && BROKEN
1776 This option will enable support for the OBIO (onboard io) NCR5380
1777 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1778 "Sun3" type VME scsi controllers also based on the NCR5380.
1779 General Linux information on the Sun 3 series (now discontinued)
1780 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1783 bool "Sun3x ESP SCSI"
1784 depends on SUN3X && SCSI=y
1786 The ESP was an on-board SCSI controller used on Sun 3/80
1787 machines. Say Y here to compile in support for it.
1790 tristate "Sparc ESP Scsi Driver"
1791 depends on SBUS && SCSI
1793 This is the driver for the Sun ESP SCSI host adapter. The ESP
1794 chipset is present in most SPARC SBUS-based computers.
1796 To compile this driver as a module, choose M here: the
1797 module will be called esp.
1799 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1802 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1803 depends on ARCH_S390 && QDIO && SCSI
1804 select SCSI_FC_ATTRS
1806 If you want to access SCSI devices attached to your IBM eServer
1807 zSeries by means of Fibre Channel interfaces say Y.
1808 For details please refer to the documentation provided by IBM at
1809 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1811 This driver is also available as a module. This module will be
1812 called zfcp. If you want to compile it as a module, say M here
1813 and read <file:Documentation/modules.txt>.
1817 source "drivers/scsi/pcmcia/Kconfig"