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 && MIPS32
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 "NVIDIA SATA support"
464 depends on SCSI_SATA && PCI && EXPERIMENTAL
466 This option enables support for NVIDIA Serial ATA.
470 config SCSI_SATA_PROMISE
471 tristate "Promise SATA TX2/TX4 support"
472 depends on SCSI_SATA && PCI
474 This option enables support for Promise Serial ATA TX2/TX4.
478 config SCSI_SATA_QSTOR
479 tristate "Pacific Digital SATA QStor support"
480 depends on SCSI_SATA && PCI
482 This option enables support for Pacific Digital Serial ATA QStor.
487 tristate "Promise SATA SX4 support"
488 depends on SCSI_SATA && PCI && EXPERIMENTAL
490 This option enables support for Promise Serial ATA SX4.
495 tristate "Silicon Image SATA support"
496 depends on SCSI_SATA && PCI && EXPERIMENTAL
498 This option enables support for Silicon Image Serial ATA.
502 config SCSI_SATA_SIL24
503 tristate "Silicon Image 3124/3132 SATA support"
504 depends on SCSI_SATA && PCI && EXPERIMENTAL
506 This option enables support for Silicon Image 3124/3132 Serial ATA.
511 tristate "SiS 964/180 SATA support"
512 depends on SCSI_SATA && PCI && EXPERIMENTAL
514 This option enables support for SiS Serial ATA 964/180.
519 tristate "ULi Electronics SATA support"
520 depends on SCSI_SATA && PCI && EXPERIMENTAL
522 This option enables support for ULi Electronics SATA.
527 tristate "VIA SATA support"
528 depends on SCSI_SATA && PCI
530 This option enables support for VIA Serial ATA.
534 config SCSI_SATA_VITESSE
535 tristate "VITESSE VSC-7174 SATA support"
536 depends on SCSI_SATA && PCI
538 This option enables support for Vitesse VSC7174 Serial ATA.
543 tristate "BusLogic SCSI support"
544 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
546 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
547 Adapters. Consult the SCSI-HOWTO, available from
548 <http://www.tldp.org/docs.html#howto>, and the files
549 <file:Documentation/scsi/BusLogic.txt> and
550 <file:Documentation/scsi/FlashPoint.txt> for more information.
552 To compile this driver as a module, choose M here: the
553 module will be called BusLogic.
555 config SCSI_OMIT_FLASHPOINT
556 bool "Omit FlashPoint support"
557 depends on SCSI_BUSLOGIC
559 This option allows you to omit the FlashPoint support from the
560 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
561 substantial, so users of MultiMaster Host Adapters may wish to omit
565 # This is marked broken because it uses over 4kB of stack in
567 # 2076 CpqTsProcessIMQEntry
571 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
572 depends on PCI && SCSI && BROKEN
574 Say Y here to compile in support for the Compaq StorageWorks Fibre
575 Channel 64-bit/66Mhz Host Bus Adapter.
578 tristate "DMX3191D SCSI support"
579 depends on PCI && SCSI
581 This is support for Domex DMX3191D SCSI Host Adapters.
583 To compile this driver as a module, choose M here: the
584 module will be called dmx3191d.
587 tristate "DTC3180/3280 SCSI support"
588 depends on ISA && SCSI
590 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
591 the SCSI-HOWTO, available from
592 <http://www.tldp.org/docs.html#howto>, and the file
593 <file:Documentation/scsi/dtc3x80.txt>.
595 To compile this driver as a module, choose M here: the
596 module will be called dtc.
599 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
600 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
602 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
603 ISA and all EISA I/O addresses are probed looking for the "EATA"
604 signature. The addresses of all the PCI SCSI controllers reported
605 by the PCI subsystem are probed as well.
607 You want to read the start of <file:drivers/scsi/eata.c> and the
608 SCSI-HOWTO, available from
609 <http://www.tldp.org/docs.html#howto>.
611 To compile this driver as a module, choose M here: the
612 module will be called eata.
614 config SCSI_EATA_TAGGED_QUEUE
615 bool "enable tagged command queueing"
618 This is a feature of SCSI-2 which improves performance: the host
619 adapter can send several SCSI commands to a device's queue even if
620 previous commands haven't finished yet.
621 This is equivalent to the "eata=tc:y" boot option.
623 config SCSI_EATA_LINKED_COMMANDS
624 bool "enable elevator sorting"
627 This option enables elevator sorting for all probed SCSI disks and
628 CD-ROMs. It definitely reduces the average seek distance when doing
629 random seeks, but this does not necessarily result in a noticeable
630 performance improvement: your mileage may vary...
631 This is equivalent to the "eata=lc:y" boot option.
633 config SCSI_EATA_MAX_TAGS
634 int "maximum number of queued commands"
638 This specifies how many SCSI commands can be maximally queued for
639 each probed SCSI device. You should reduce the default value of 16
640 only if you have disks with buggy or limited tagged command support.
641 Minimum is 2 and maximum is 62. This value is also the window size
642 used by the elevator sorting option above. The effective value used
643 by the driver for each probed SCSI device is reported at boot time.
644 This is equivalent to the "eata=mq:8" boot option.
647 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
648 depends on (ISA || EISA || PCI) && SCSI && BROKEN
650 This driver supports all EATA-PIO protocol compliant SCSI Host
651 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
652 host adapters could also use this driver but are discouraged from
653 doing so, since this driver only supports hard disks and lacks
654 numerous features. You might want to have a look at the SCSI-HOWTO,
655 available from <http://www.tldp.org/docs.html#howto>.
657 To compile this driver as a module, choose M here: the
658 module will be called eata_pio.
660 config SCSI_FUTURE_DOMAIN
661 tristate "Future Domain 16xx SCSI/AHA-2920A support"
662 depends on (ISA || PCI) && SCSI
664 This is support for Future Domain's 16-bit SCSI host adapters
665 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
666 other adapters based on the Future Domain chipsets (Quantum
667 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
668 It is explained in section 3.7 of the SCSI-HOWTO, available from
669 <http://www.tldp.org/docs.html#howto>.
671 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
672 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
673 controller support"). This Future Domain driver works with the older
674 Adaptec AHA-2920A boards with a Future Domain chip on them.
676 To compile this driver as a module, choose M here: the
677 module will be called fdomain.
680 tristate "Future Domain MCS-600/700 SCSI support"
681 depends on MCA_LEGACY && SCSI
683 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
684 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
685 is identical to the MCS 700 and hence also supported by this driver.
686 This driver also supports the Reply SB16/SCSI card (the SCSI part).
687 It supports multiple adapters in the same system.
689 To compile this driver as a module, choose M here: the
690 module will be called fd_mcs.
693 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
694 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
696 Formerly called GDT SCSI Disk Array Controller Support.
698 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
699 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
700 in the kernel source in <file:drivers/scsi/gdth.c> and
701 <file:drivers/scsi/gdth.h.>
703 To compile this driver as a module, choose M here: the
704 module will be called gdth.
706 config SCSI_GENERIC_NCR5380
707 tristate "Generic NCR5380/53c400 SCSI PIO support"
708 depends on ISA && SCSI
710 This is a driver for the old NCR 53c80 series of SCSI controllers
711 on boards using PIO. Most boards such as the Trantor T130 fit this
712 category, along with a large number of ISA 8bit controllers shipped
713 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
714 you should select the specific driver for that card rather than
715 generic 5380 support.
717 It is explained in section 3.8 of the SCSI-HOWTO, available from
718 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
719 of the box, you may have to change some settings in
720 <file:drivers/scsi/g_NCR5380.h>.
722 To compile this driver as a module, choose M here: the
723 module will be called g_NCR5380.
725 config SCSI_GENERIC_NCR5380_MMIO
726 tristate "Generic NCR5380/53c400 SCSI MMIO support"
727 depends on ISA && SCSI
729 This is a driver for the old NCR 53c80 series of SCSI controllers
730 on boards using memory mapped I/O.
731 It is explained in section 3.8 of the SCSI-HOWTO, available from
732 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
733 of the box, you may have to change some settings in
734 <file:drivers/scsi/g_NCR5380.h>.
736 To compile this driver as a module, choose M here: the
737 module will be called g_NCR5380_mmio.
739 config SCSI_GENERIC_NCR53C400
740 bool "Enable NCR53c400 extensions"
741 depends on SCSI_GENERIC_NCR5380
743 This enables certain optimizations for the NCR53c400 SCSI cards.
744 You might as well try it out. Note that this driver will only probe
745 for the Trantor T130B in its default configuration; you might have
746 to pass a command line option to the kernel at boot time if it does
747 not detect your card. See the file
748 <file:Documentation/scsi/g_NCR5380.txt> for details.
751 tristate "IBMMCA SCSI support"
752 depends on MCA_LEGACY && SCSI
754 This is support for the IBM SCSI adapter found in many of the PS/2
755 series computers. These machines have an MCA bus, so you need to
756 answer Y to "MCA support" as well and read
757 <file:Documentation/mca.txt>.
759 If the adapter isn't found during boot (a common problem for models
760 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
761 option, where <pun> is the id of the SCSI subsystem (usually 7, but
762 if that doesn't work check your reference diskette). Owners of
763 model 95 with a LED-matrix-display can in addition activate some
764 activity info like under OS/2, but more informative, by setting
765 'ibmmcascsi=display' as an additional kernel parameter. Try "man
766 bootparam" or see the documentation of your boot loader about how to
767 pass options to the kernel.
769 To compile this driver as a module, choose M here: the
770 module will be called ibmmca.
772 config IBMMCA_SCSI_ORDER_STANDARD
773 bool "Standard SCSI-order"
774 depends on SCSI_IBMMCA
776 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
777 are assigned to the drive letters, starting with the lowest SCSI-id
778 (physical number -- pun) to be drive C:, as seen from DOS and
779 similar operating systems. When looking into papers describing the
780 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
781 The SCSI-standard follows a hardware-hierarchy which says that id 7
782 has the highest priority and id 0 the lowest. Therefore, the host
783 adapters are still today everywhere placed as SCSI-id 7 by default.
784 In the SCSI-standard, the drive letters express the priority of the
785 disk. C: should be the hard disk, or a partition on it, with the
786 highest priority. This must therefore be the disk with the highest
787 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
788 original definition of the SCSI-standard as also industrial- and
789 process-control-machines, like VME-CPUs running under realtime-OSes
790 (e.g. LynxOS, OS9) do.
792 If you like to run Linux on your MCA-machine with the same
793 assignment of hard disks as seen from e.g. DOS or OS/2 on your
794 machine, which is in addition conformant to the SCSI-standard, you
795 must say Y here. This is also necessary for MCA-Linux users who want
796 to keep downward compatibility to older releases of the
797 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
800 If you like to have the lowest SCSI-id assigned as drive C:, as
801 modern SCSI-BIOSes do, which does not conform to the standard, but
802 is widespread and common in the PC-world of today, you must say N
803 here. If unsure, say Y.
805 config IBMMCA_SCSI_DEV_RESET
806 bool "Reset SCSI-devices at boottime"
807 depends on SCSI_IBMMCA
809 By default, SCSI-devices are reset when the machine is powered on.
810 However, some devices exist, like special-control-devices,
811 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
812 not reset when switched on. If you say Y here, each device connected
813 to your SCSI-bus will be issued a reset-command after it has been
814 probed, while the kernel is booting. This may cause problems with
815 more modern devices, like hard disks, which do not appreciate these
816 reset commands, and can cause your system to hang. So say Y only if
817 you know that one of your older devices needs it; N is the safe
821 tristate "IBM ServeRAID support"
822 depends on PCI && SCSI
824 This is support for the IBM ServeRAID hardware RAID controllers.
825 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
826 for more information. If this driver does not work correctly
827 without modification please contact the author by email at
828 <ipslinux@adaptec.com>.
830 To compile this driver as a module, choose M here: the
831 module will be called ips.
834 tristate "IBM Virtual SCSI support"
835 depends on PPC_PSERIES || PPC_ISERIES
837 This is the IBM POWER Virtual SCSI Client
839 To compile this driver as a module, choose M here: the
840 module will be called ibmvscsic.
843 tristate "Initio 9100U(W) support"
844 depends on PCI && SCSI
846 This is support for the Initio 91XXU(W) SCSI host adapter. Please
847 read the SCSI-HOWTO, available from
848 <http://www.tldp.org/docs.html#howto>.
850 To compile this driver as a module, choose M here: the
851 module will be called initio.
854 tristate "Initio INI-A100U2W support"
855 depends on PCI && SCSI
857 This is support for the Initio INI-A100U2W SCSI host adapter.
858 Please read the SCSI-HOWTO, available from
859 <http://www.tldp.org/docs.html#howto>.
861 To compile this driver as a module, choose M here: the
862 module will be called a100u2w.
865 tristate "IOMEGA parallel port (ppa - older drives)"
866 depends on SCSI && PARPORT
868 This driver supports older versions of IOMEGA's parallel port ZIP
869 drive (a 100 MB removable media device).
871 Note that you can say N here if you have the SCSI version of the ZIP
872 drive: it will be supported automatically if you said Y to the
873 generic "SCSI disk support", above.
875 If you have the ZIP Plus drive or a more recent parallel port ZIP
876 drive (if the supplied cable with the drive is labeled "AutoDetect")
877 then you should say N here and Y to "IOMEGA parallel port (imm -
878 newer drives)", below.
880 For more information about this driver and how to use it you should
881 read the file <file:Documentation/scsi/ppa.txt>. You should also read
882 the SCSI-HOWTO, which is available from
883 <http://www.tldp.org/docs.html#howto>. If you use this driver,
884 you will still be able to use the parallel port for other tasks,
885 such as a printer; it is safe to compile both drivers into the
888 To compile this driver as a module, choose M here: the
889 module will be called ppa.
892 tristate "IOMEGA parallel port (imm - newer drives)"
893 depends on SCSI && PARPORT
895 This driver supports newer versions of IOMEGA's parallel port ZIP
896 drive (a 100 MB removable media device).
898 Note that you can say N here if you have the SCSI version of the ZIP
899 drive: it will be supported automatically if you said Y to the
900 generic "SCSI disk support", above.
902 If you have the ZIP Plus drive or a more recent parallel port ZIP
903 drive (if the supplied cable with the drive is labeled "AutoDetect")
904 then you should say Y here; if you have an older ZIP drive, say N
905 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
907 For more information about this driver and how to use it you should
908 read the file <file:Documentation/scsi/ppa.txt>. You should also read
909 the SCSI-HOWTO, which is available from
910 <http://www.tldp.org/docs.html#howto>. If you use this driver,
911 you will still be able to use the parallel port for other tasks,
912 such as a printer; it is safe to compile both drivers into the
915 To compile this driver as a module, choose M here: the
916 module will be called imm.
918 config SCSI_IZIP_EPP16
919 bool "ppa/imm option - Use slow (but safe) EPP-16"
920 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
922 EPP (Enhanced Parallel Port) is a standard for parallel ports which
923 allows them to act as expansion buses that can handle up to 64
926 Some parallel port chipsets are slower than their motherboard, and
927 so we have to control the state of the chipset's FIFO queue every
928 now and then to avoid data loss. This will be done if you say Y
931 Generally, saying Y is the safe option and slows things down a bit.
933 config SCSI_IZIP_SLOW_CTR
934 bool "ppa/imm option - Assume slow parport control register"
935 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
937 Some parallel ports are known to have excessive delays between
938 changing the parallel port control register and good data being
939 available on the parallel port data/status register. This option
940 forces a small delay (1.0 usec to be exact) after changing the
941 control register to let things settle out. Enabling this option may
942 result in a big drop in performance but some very old parallel ports
943 (found in 386 vintage machines) will not work properly.
945 Generally, saying N is fine.
947 config SCSI_NCR53C406A
948 tristate "NCR53c406a SCSI support"
949 depends on ISA && SCSI
951 This is support for the NCR53c406a SCSI host adapter. For user
952 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
953 in the kernel source. Also read the SCSI-HOWTO, available from
954 <http://www.tldp.org/docs.html#howto>.
956 To compile this driver as a module, choose M here: the
957 module will be called NCR53c406.
960 tristate "NCR Dual 700 MCA SCSI support"
961 depends on MCA && SCSI
962 select SCSI_SPI_ATTRS
964 This is a driver for the MicroChannel Dual 700 card produced by
965 NCR and commonly used in 345x/35xx/4100 class machines. It always
966 tries to negotiate sync and uses tag command queueing.
968 Unless you have an NCR manufactured machine, the chances are that
969 you do not have this SCSI card, so say N.
972 tristate "HP Lasi SCSI support for 53c700/710"
973 depends on GSC && SCSI
974 select SCSI_SPI_ATTRS
976 This is a driver for the SCSI controller in the Lasi chip found in
977 many PA-RISC workstations & servers. If you do not know whether you
978 have a Lasi chip, it is safe to say "Y" here.
980 config 53C700_LE_ON_BE
982 depends on SCSI_LASI700
985 config SCSI_SYM53C8XX_2
986 tristate "SYM53C8XX Version 2 SCSI support"
987 depends on PCI && SCSI
988 select SCSI_SPI_ATTRS
990 This driver supports the whole NCR53C8XX/SYM53C8XX family of
991 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
992 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
993 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
994 controllers; you need to use the Fusion MPT driver for that.
996 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
999 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1000 int "DMA addressing mode"
1001 depends on SCSI_SYM53C8XX_2
1004 This option only applies to PCI-SCSI chips that are PCI DAC
1005 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1007 When set to 0, the driver will program the chip to only perform
1008 32-bit DMA. When set to 1, the chip will be able to perform DMA
1009 to addresses up to 1TB. When set to 2, the driver supports the
1010 full 64-bit DMA address range, but can only address 16 segments
1011 of 4 GB each. This limits the total addressable range to 64 GB.
1013 Most machines with less than 4GB of memory should use a setting
1014 of 0 for best performance. If your machine has 4GB of memory
1015 or more, you should set this option to 1 (the default).
1017 The still experimental value 2 (64 bit DMA addressing with 16
1018 x 4GB segments limitation) can be used on systems that require
1019 PCI address bits past bit 39 to be set for the addressing of
1020 memory using PCI DAC cycles.
1022 config SCSI_SYM53C8XX_DEFAULT_TAGS
1023 int "default tagged command queue depth"
1024 depends on SCSI_SYM53C8XX_2
1027 This is the default value of the command queue depth the
1028 driver will announce to the generic SCSI layer for devices
1029 that support tagged command queueing. This value can be changed
1030 from the boot command line. This is a soft limit that cannot
1031 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1033 config SCSI_SYM53C8XX_MAX_TAGS
1034 int "maximum number of queued commands"
1035 depends on SCSI_SYM53C8XX_2
1038 This option allows you to specify the maximum number of commands
1039 that can be queued to any device, when tagged command queuing is
1040 possible. The driver supports up to 256 queued commands per device.
1041 This value is used as a compiled-in hard limit.
1043 config SCSI_SYM53C8XX_IOMAPPED
1045 depends on SCSI_SYM53C8XX_2
1047 If you say Y here, the driver will use port IO to access
1048 the card. This is significantly slower then using memory
1049 mapped IO. Most people should answer N.
1052 tristate "IBM Power Linux RAID adapter support"
1053 depends on PCI && SCSI
1056 This driver supports the IBM Power Linux family RAID adapters.
1057 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1058 as IBM iSeries 5702, 5703, 5709, and 570A.
1060 config SCSI_IPR_TRACE
1061 bool "enable driver internal trace"
1064 If you say Y here, the driver will trace all commands issued
1065 to the adapter. Performance impact is minimal. Trace can be
1066 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1068 config SCSI_IPR_DUMP
1069 bool "enable adapter dump support"
1072 If you say Y here, the driver will support adapter crash dump.
1073 If you enable this support, the iprdump daemon can be used
1074 to capture adapter failure analysis information.
1077 tristate "Zalon SCSI support"
1078 depends on GSC && SCSI
1079 select SCSI_SPI_ATTRS
1081 The Zalon is a GSC/HSC bus interface chip that sits between the
1082 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1083 C110, J200, J210 and some D, K & R-class machines. It's also
1084 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1085 Say Y here if you have one of these machines or cards.
1087 config SCSI_NCR_Q720
1088 tristate "NCR Quad 720 MCA SCSI support"
1089 depends on MCA && SCSI
1090 select SCSI_SPI_ATTRS
1092 This is a driver for the MicroChannel Quad 720 card produced by
1093 NCR and commonly used in 345x/35xx/4100 class machines. It always
1094 tries to negotiate sync and uses tag command queueing.
1096 Unless you have an NCR manufactured machine, the chances are that
1097 you do not have this SCSI card, so say N.
1099 config SCSI_NCR53C8XX_DEFAULT_TAGS
1100 int " default tagged command queue depth"
1101 depends on SCSI_ZALON || SCSI_NCR_Q720
1104 "Tagged command queuing" is a feature of SCSI-2 which improves
1105 performance: the host adapter can send several SCSI commands to a
1106 device's queue even if previous commands haven't finished yet.
1107 Because the device is intelligent, it can optimize its operations
1108 (like head positioning) based on its own request queue. Some SCSI
1109 devices don't implement this properly; if you want to disable this
1110 feature, enter 0 or 1 here (it doesn't matter which).
1112 The default value is 8 and should be supported by most hard disks.
1113 This value can be overridden from the boot command line using the
1114 'tags' option as follows (example):
1115 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1116 4, set queue depth to 16 for target 2 and target 3 on controller 0
1117 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1119 The normal answer therefore is to go with the default 8 and to use
1120 a boot command line option for devices that need to use a different
1121 command queue depth.
1123 There is no safe option other than using good SCSI devices.
1125 config SCSI_NCR53C8XX_MAX_TAGS
1126 int " maximum number of queued commands"
1127 depends on SCSI_ZALON || SCSI_NCR_Q720
1130 This option allows you to specify the maximum number of commands
1131 that can be queued to any device, when tagged command queuing is
1132 possible. The default value is 32. Minimum is 2, maximum is 64.
1133 Modern hard disks are able to support 64 tags and even more, but
1134 do not seem to be faster when more than 32 tags are being used.
1136 So, the normal answer here is to go with the default value 32 unless
1137 you are using very large hard disks with large cache (>= 1 MB) that
1138 are able to take advantage of more than 32 tagged commands.
1140 There is no safe option and the default answer is recommended.
1142 config SCSI_NCR53C8XX_SYNC
1143 int " synchronous transfers frequency in MHz"
1144 depends on SCSI_ZALON || SCSI_NCR_Q720
1147 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1148 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1149 are respectively the maximum data transfer rates in mega-transfers
1150 per second for each class. For example, a FAST-20 Wide 16 device is
1151 able to transfer data at 20 million 16 bit packets per second for a
1152 total rate of 40 MB/s.
1154 You may specify 0 if you want to only use asynchronous data
1155 transfers. This is the safest and slowest option. Otherwise, specify
1156 a value between 5 and 80, depending on the capability of your SCSI
1157 controller. The higher the number, the faster the data transfer.
1158 Note that 80 should normally be ok since the driver decreases the
1159 value automatically according to the controller's capabilities.
1161 Your answer to this question is ignored for controllers with NVRAM,
1162 since the driver will get this information from the user set-up. It
1163 also can be overridden using a boot setup option, as follows
1164 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1165 for FAST-20 synchronous data transfer (20 mega-transfers per
1168 The normal answer therefore is not to go with the default but to
1169 select the maximum value 80 allowing the driver to use the maximum
1170 value supported by each controller. If this causes problems with
1171 your SCSI devices, you should come back and decrease the value.
1173 There is no safe option other than using good cabling, right
1174 terminations and SCSI conformant devices.
1176 config SCSI_NCR53C8XX_PROFILE
1177 bool " enable profiling"
1178 depends on SCSI_ZALON || SCSI_NCR_Q720
1180 This option allows you to enable profiling information gathering.
1181 These statistics are not very accurate due to the low frequency
1182 of the kernel clock (100 Hz on i386) and have performance impact
1183 on systems that use very fast devices.
1185 The normal answer therefore is N.
1187 config SCSI_NCR53C8XX_NO_DISCONNECT
1188 bool " not allow targets to disconnect"
1189 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1191 This option is only provided for safety if you suspect some SCSI
1192 device of yours to not support properly the target-disconnect
1193 feature. In that case, you would say Y here. In general however, to
1194 not allow targets to disconnect is not reasonable if there is more
1195 than 1 device on a SCSI bus. The normal answer therefore is N.
1197 config SCSI_MCA_53C9X
1198 tristate "NCR MCA 53C9x SCSI support"
1199 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1201 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1202 controller based on the NCR 53C94. This driver will allow use of
1203 the controller on the 3550, and very possibly others.
1205 To compile this driver as a module, choose M here: the
1206 module will be called mca_53c9x.
1209 tristate "PAS16 SCSI support"
1210 depends on ISA && SCSI
1212 This is support for a SCSI host adapter. It is explained in section
1213 3.10 of the SCSI-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1215 of the box, you may have to change some settings in
1216 <file:drivers/scsi/pas16.h>.
1218 To compile this driver as a module, choose M here: the
1219 module will be called pas16.
1222 tristate "PSI240i support"
1223 depends on ISA && SCSI
1225 This is support for the PSI240i EIDE interface card which acts as a
1226 SCSI host adapter. Please read the SCSI-HOWTO, available from
1227 <http://www.tldp.org/docs.html#howto>.
1229 To compile this driver as a module, choose M here: the
1230 module will be called psi240i.
1232 config SCSI_QLOGIC_FAS
1233 tristate "Qlogic FAS SCSI support"
1234 depends on ISA && SCSI
1236 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1237 FastSCSI! cards as well as any other card based on the FASXX chip
1238 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1240 This driver does NOT support the PCI versions of these cards. The
1241 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1242 SCSI support"), below.
1244 Information about this driver is contained in
1245 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1246 SCSI-HOWTO, available from
1247 <http://www.tldp.org/docs.html#howto>.
1249 To compile this driver as a module, choose M here: the
1250 module will be called qlogicfas.
1252 config SCSI_QLOGIC_ISP
1253 tristate "Qlogic ISP SCSI support (old driver)"
1254 depends on PCI && SCSI && BROKEN
1256 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1257 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1258 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1260 If you say Y here, make sure to choose "BIOS" at the question "PCI
1263 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1264 should also read the SCSI-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>.
1267 To compile this driver as a module, choose M here: the
1268 module will be called qlogicisp.
1270 These days the hardware is also supported by the more modern qla1280
1271 driver. In doubt use that one instead of qlogicisp.
1273 config SCSI_QLOGIC_FC
1274 tristate "Qlogic ISP FC SCSI support"
1275 depends on PCI && SCSI
1277 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1279 To compile this driver as a module, choose M here: the
1280 module will be called qlogicfc.
1282 config SCSI_QLOGIC_FC_FIRMWARE
1283 bool "Include loadable firmware in driver"
1284 depends on SCSI_QLOGIC_FC
1286 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1287 expanded LUN addressing and FcTape (FCP-2) support, in the
1288 qlogicfc driver. This is required on some platforms.
1290 config SCSI_QLOGIC_1280
1291 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1292 depends on PCI && SCSI
1294 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1296 To compile this driver as a module, choose M here: the
1297 module will be called qla1280.
1299 config SCSI_QLOGIC_1280_1040
1300 bool "Qlogic QLA 1020/1040 SCSI support"
1301 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1303 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1304 do not want to use the old driver. This option enables support in
1305 the qla1280 driver for those host adapters.
1307 config SCSI_QLOGICPTI
1308 tristate "PTI Qlogic, ISP Driver"
1309 depends on SBUS && SCSI
1311 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1312 controllers are known under Solaris as qpti and in the openprom as
1313 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1314 driven by a different driver.
1316 To compile this driver as a module, choose M here: the
1317 module will be called qlogicpti.
1319 source "drivers/scsi/qla2xxx/Kconfig"
1322 tristate "Emulex LightPulse Fibre Channel Support"
1323 depends on PCI && SCSI
1324 select SCSI_FC_ATTRS
1326 This lpfc driver supports the Emulex LightPulse
1327 Family of Fibre Channel PCI host adapters.
1330 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1331 depends on X86 && ISA && SCSI && BROKEN
1333 These are 8-bit SCSI controllers; the ST-01 is also supported by
1334 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1335 available from <http://www.tldp.org/docs.html#howto>. If it
1336 doesn't work out of the box, you may have to change some settings in
1337 <file:drivers/scsi/seagate.h>.
1339 To compile this driver as a module, choose M here: the
1340 module will be called seagate.
1342 # definitely looks not 64bit safe:
1344 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1345 depends on (EISA || MCA) && SCSI
1346 select SCSI_SPI_ATTRS
1348 This driver for NCR53c710 based SCSI host adapters.
1350 It currently supports Compaq EISA cards and NCR MCA cards
1352 config 53C700_IO_MAPPED
1354 depends on SCSI_SIM710
1357 config SCSI_SYM53C416
1358 tristate "Symbios 53c416 SCSI support"
1359 depends on ISA && SCSI
1361 This is support for the sym53c416 SCSI host adapter, the SCSI
1362 adapter that comes with some HP scanners. This driver requires that
1363 the sym53c416 is configured first using some sort of PnP
1364 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1365 are using isapnp then you need to compile this driver as a module
1366 and then load it using insmod after isapnp has run. The parameters
1367 of the configured card(s) should be passed to the driver. The format
1370 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1372 To compile this driver as a module, choose M here: the
1373 module will be called sym53c416.
1376 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1377 depends on PCI && SCSI && EXPERIMENTAL
1379 This driver supports PCI SCSI host adapters based on the ASIC
1380 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1382 This driver works, but is still in experimental status. So better
1383 have a bootable disk and a backup in case of emergency.
1385 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1387 To compile this driver as a module, choose M here: the
1388 module will be called dc395x.
1391 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1392 depends on PCI && SCSI
1394 This driver supports PCI SCSI host adapters based on the Am53C974A
1395 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1396 PCscsi/PCnet (Am53/79C974) solutions.
1398 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1400 Note that this driver does NOT support Tekram DC390W/U/F, which are
1401 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1403 To compile this driver as a module, choose M here: the
1404 module will be called tmscsim.
1407 tristate "Trantor T128/T128F/T228 SCSI support"
1408 depends on ISA && SCSI
1410 This is support for a SCSI host adapter. It is explained in section
1411 3.11 of the SCSI-HOWTO, available from
1412 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1413 of the box, you may have to change some settings in
1414 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1415 Adaptec, and some former Trantor products are being sold under the
1418 To compile this driver as a module, choose M here: the
1419 module will be called t128.
1422 tristate "UltraStor 14F/34F support"
1423 depends on ISA && SCSI && ISA_DMA_API
1425 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1426 The source at <file:drivers/scsi/u14-34f.c> contains some
1427 information about this hardware. If the driver doesn't work out of
1428 the box, you may have to change some settings in
1429 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1430 <http://www.tldp.org/docs.html#howto>. Note that there is also
1431 another driver for the same hardware: "UltraStor SCSI support",
1432 below. You should say Y to both only if you want 24F support as
1435 To compile this driver as a module, choose M here: the
1436 module will be called u14-34f.
1438 config SCSI_U14_34F_TAGGED_QUEUE
1439 bool "enable tagged command queueing"
1440 depends on SCSI_U14_34F
1442 This is a feature of SCSI-2 which improves performance: the host
1443 adapter can send several SCSI commands to a device's queue even if
1444 previous commands haven't finished yet.
1445 This is equivalent to the "u14-34f=tc:y" boot option.
1447 config SCSI_U14_34F_LINKED_COMMANDS
1448 bool "enable elevator sorting"
1449 depends on SCSI_U14_34F
1451 This option enables elevator sorting for all probed SCSI disks and
1452 CD-ROMs. It definitely reduces the average seek distance when doing
1453 random seeks, but this does not necessarily result in a noticeable
1454 performance improvement: your mileage may vary...
1455 This is equivalent to the "u14-34f=lc:y" boot option.
1457 config SCSI_U14_34F_MAX_TAGS
1458 int "maximum number of queued commands"
1459 depends on SCSI_U14_34F
1462 This specifies how many SCSI commands can be maximally queued for
1463 each probed SCSI device. You should reduce the default value of 8
1464 only if you have disks with buggy or limited tagged command support.
1465 Minimum is 2 and maximum is 14. This value is also the window size
1466 used by the elevator sorting option above. The effective value used
1467 by the driver for each probed SCSI device is reported at boot time.
1468 This is equivalent to the "u14-34f=mq:8" boot option.
1470 config SCSI_ULTRASTOR
1471 tristate "UltraStor SCSI support"
1472 depends on X86 && ISA && SCSI
1474 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1475 adapter family. This driver is explained in section 3.12 of the
1476 SCSI-HOWTO, available from
1477 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1478 of the box, you may have to change some settings in
1479 <file:drivers/scsi/ultrastor.h>.
1481 Note that there is also another driver for the same hardware:
1482 "UltraStor 14F/34F support", above.
1484 To compile this driver as a module, choose M here: the
1485 module will be called ultrastor.
1488 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1489 depends on PCI && SCSI && !64BIT
1491 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1492 SCSI host adapter. Please read the SCSI-HOWTO, available from
1493 <http://www.tldp.org/docs.html#howto>.
1495 To compile this driver as a module, choose M here: the
1496 module will be called nsp32.
1499 tristate "SCSI debugging host simulator"
1502 This is a host adapter simulator that can simulate multiple hosts
1503 each with multiple dummy SCSI devices (disks). It defaults to one
1504 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1505 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1506 dummy disks are simulated, they share the same kernel RAM for
1507 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1508 information. This driver is primarily of use to those testing the
1509 SCSI and block subsystems. If unsure, say N.
1512 tristate "MESH (Power Mac internal SCSI) support"
1513 depends on PPC32 && PPC_PMAC && SCSI
1515 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1516 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1517 other Power Macintoshes do). Say Y to include support for this SCSI
1520 To compile this driver as a module, choose M here: the
1521 module will be called mesh.
1523 config SCSI_MESH_SYNC_RATE
1524 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1525 depends on SCSI_MESH
1528 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1529 drives a bus which is entirely internal to the machine (such as the
1530 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1531 operation at up to 10 MB/s. On machines where the SCSI bus
1532 controlled by the MESH can have external devices connected, it is
1533 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1534 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1535 to disable synchronous operation.
1537 config SCSI_MESH_RESET_DELAY_MS
1538 int "initial bus reset delay (ms) (0 = no reset)"
1539 depends on SCSI_MESH
1542 config SCSI_MAC53C94
1543 tristate "53C94 (Power Mac external SCSI) support"
1544 depends on PPC32 && PPC_PMAC && SCSI
1546 On Power Macintoshes (and clones) with two SCSI buses, the external
1547 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1548 machines which only have one SCSI bus, such as the 7200, also use
1549 the 53C94. Say Y to include support for the 53C94.
1551 To compile this driver as a module, choose M here: the
1552 module will be called mac53c94.
1554 source "drivers/scsi/arm/Kconfig"
1557 bool "MIPS JAZZ FAS216 SCSI support"
1558 depends on MACH_JAZZ && SCSI
1560 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1561 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1565 tristate "A3000 WD33C93A support"
1566 depends on AMIGA && SCSI
1568 If you have an Amiga 3000 and have SCSI devices connected to the
1569 built-in SCSI controller, say Y. Otherwise, say N.
1571 To compile this driver as a module, choose M here: the
1572 module will be called wd33c93.
1575 tristate "A2091/A590 WD33C93A support"
1576 depends on ZORRO && SCSI
1578 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1581 To compile this driver as a module, choose M here: the
1582 module will be called wd33c93.
1585 tristate "GVP Series II WD33C93A support"
1586 depends on ZORRO && SCSI
1588 If you have a Great Valley Products Series II SCSI controller,
1589 answer Y. Also say Y if you have a later model of GVP SCSI
1590 controller (such as the GVP A4008 or a Combo board). Otherwise,
1591 answer N. This driver does NOT work for the T-Rex series of
1592 accelerators from TekMagic and GVP-M.
1594 To compile this driver as a module, choose M here: the
1595 module will be called gvp11.
1597 config CYBERSTORM_SCSI
1598 tristate "CyberStorm SCSI support"
1599 depends on ZORRO && SCSI
1601 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1602 accelerator board and the optional Cyberstorm SCSI controller,
1603 answer Y. Otherwise, say N.
1605 config CYBERSTORMII_SCSI
1606 tristate "CyberStorm Mk II SCSI support"
1607 depends on ZORRO && SCSI
1609 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1610 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1614 tristate "Blizzard 2060 SCSI support"
1615 depends on ZORRO && SCSI
1617 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1618 and want to use the onboard SCSI controller, say Y. Otherwise,
1622 tristate "Blizzard 1230IV/1260 SCSI support"
1623 depends on ZORRO && SCSI
1625 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1626 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1629 config FASTLANE_SCSI
1630 tristate "Fastlane SCSI support"
1631 depends on ZORRO && SCSI
1633 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1634 one in the near future, say Y to this question. Otherwise, say N.
1636 config SCSI_AMIGA7XX
1637 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1638 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1640 Support for various NCR53c710-based SCSI controllers on the Amiga.
1642 - the builtin SCSI controller on the Amiga 4000T,
1643 - the Amiga 4091 Zorro III SCSI-2 controller,
1644 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1646 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1647 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1648 accelerator card for the Amiga 1200,
1649 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1650 Note that all of the above SCSI controllers, except for the builtin
1651 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1652 bus, so you also have to enable Zorro bus support if you want to use
1656 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1657 depends on ZORRO && SCSI && EXPERIMENTAL
1659 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1660 Y to this question. If you're in doubt about whether you have one,
1662 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1665 tristate "Atari native SCSI support"
1666 depends on ATARI && SCSI && BROKEN
1668 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1669 Falcon, ...) say Y to get it supported. Of course also, if you have
1670 a compatible SCSI controller (e.g. for Medusa).
1672 To compile this driver as a module, choose M here: the
1673 module will be called atari_scsi.
1675 This driver supports both styles of NCR integration into the
1676 system: the TT style (separate DMA), and the Falcon style (via
1677 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1678 in the Hades (without DMA).
1680 config ATARI_SCSI_TOSHIBA_DELAY
1681 bool "Long delays for Toshiba CD-ROMs"
1682 depends on ATARI_SCSI
1684 This option increases the delay after a SCSI arbitration to
1685 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1686 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1687 would impact performance a bit, so say N.
1689 config ATARI_SCSI_RESET_BOOT
1690 bool "Reset SCSI-devices at boottime"
1691 depends on ATARI_SCSI
1693 Reset the devices on your Atari whenever it boots. This makes the
1694 boot process fractionally longer but may assist recovery from errors
1695 that leave the devices with SCSI operations partway completed.
1698 bool "Hades SCSI DMA emulator"
1699 depends on ATARI_SCSI && HADES
1701 This option enables code which emulates the TT SCSI DMA chip on the
1702 Hades. This increases the SCSI transfer rates at least ten times
1703 compared to PIO transfers.
1706 bool "Macintosh NCR5380 SCSI"
1707 depends on MAC && SCSI
1709 This is the NCR 5380 SCSI controller included on most of the 68030
1710 based Macintoshes. If you have one of these say Y and read the
1711 SCSI-HOWTO, available from
1712 <http://www.tldp.org/docs.html#howto>.
1715 tristate "Macintosh NCR53c9[46] SCSI"
1716 depends on MAC && SCSI
1718 This is the NCR 53c9x SCSI controller found on most of the 68040
1719 based Macintoshes. If you have one of these say Y and read the
1720 SCSI-HOWTO, available from
1721 <http://www.tldp.org/docs.html#howto>.
1723 To compile this driver as a module, choose M here: the
1724 module will be called mac_esp.
1727 bool "WD33C93 SCSI driver for MVME147"
1728 depends on MVME147 && SCSI
1730 Support for the on-board SCSI controller on the Motorola MVME147
1731 single-board computer.
1734 bool "NCR53C710 SCSI driver for MVME16x"
1735 depends on MVME16x && SCSI && BROKEN
1737 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1738 SCSI controller chip. Almost everyone using one of these boards
1739 will want to say Y to this question.
1741 config BVME6000_SCSI
1742 bool "NCR53C710 SCSI driver for BVME6000"
1743 depends on BVME6000 && SCSI && BROKEN
1745 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1746 SCSI controller chip. Almost everyone using one of these boards
1747 will want to say Y to this question.
1749 config SCSI_NCR53C7xx_FAST
1750 bool "allow FAST-SCSI [10MHz]"
1751 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1753 This will enable 10MHz FAST-SCSI transfers with your host
1754 adapter. Some systems have problems with that speed, so it's safest
1758 tristate "Sun3 NCR5380 SCSI"
1759 depends on SUN3 && SCSI && BROKEN
1761 This option will enable support for the OBIO (onboard io) NCR5380
1762 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1763 "Sun3" type VME scsi controllers also based on the NCR5380.
1764 General Linux information on the Sun 3 series (now discontinued)
1765 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1768 bool "Sun3x ESP SCSI"
1769 depends on SUN3X && SCSI
1771 The ESP was an on-board SCSI controller used on Sun 3/80
1772 machines. Say Y here to compile in support for it.
1775 tristate "Sparc ESP Scsi Driver"
1776 depends on SBUS && SCSI
1778 This is the driver for the Sun ESP SCSI host adapter. The ESP
1779 chipset is present in most SPARC SBUS-based computers.
1781 To compile this driver as a module, choose M here: the
1782 module will be called esp.
1784 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1787 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1788 depends on ARCH_S390 && QDIO && SCSI
1789 select SCSI_FC_ATTRS
1791 If you want to access SCSI devices attached to your IBM eServer
1792 zSeries by means of Fibre Channel interfaces say Y.
1793 For details please refer to the documentation provided by IBM at
1794 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1796 This driver is also available as a module. This module will be
1797 called zfcp. If you want to compile it as a module, say M here
1798 and read <file:Documentation/modules.txt>.
1802 source "drivers/scsi/pcmcia/Kconfig"