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.
140 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
143 config SCSI_MULTI_LUN
144 bool "Probe all LUNs on each SCSI device"
147 If you have a SCSI device that supports more than one LUN (Logical
148 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
149 can say Y here to force the SCSI driver to probe for multiple LUNs.
150 A SCSI device with multiple LUNs acts logically like multiple SCSI
151 devices. The vast majority of SCSI devices have only one LUN, and
152 so most people can say N here. The max_luns boot/module parameter
153 allows to override this setting.
155 config SCSI_CONSTANTS
156 bool "Verbose SCSI error reporting (kernel size +=12K)"
159 The error messages regarding your SCSI hardware will be easier to
160 understand if you say Y here; it will enlarge your kernel by about
161 12 KB. If in doubt, say Y.
164 bool "SCSI logging facility"
167 This turns on a logging facility that can be used to debug a number
168 of SCSI related problems.
170 If you say Y here, no logging output will appear by default, but you
171 can enable logging by saying Y to "/proc file system support" and
172 "Sysctl support" below and executing the command
174 echo "scsi log token [level]" > /proc/scsi/scsi
176 at boot time after the /proc file system has been mounted.
178 There are a number of things that can be used for 'token' (you can
179 find them in the source: <file:drivers/scsi/scsi.c>), and this
180 allows you to select the types of information you want, and the
181 level allows you to select the level of verbosity.
183 If you say N here, it may be harder to track down some types of SCSI
184 problems. If you say Y here your kernel will be somewhat larger, but
185 there should be no noticeable performance impact as long as you have
188 menu "SCSI Transport Attributes"
191 config SCSI_SPI_ATTRS
192 tristate "Parallel SCSI (SPI) Transport Attributes"
195 If you wish to export transport-specific information about
196 each attached SCSI device to sysfs, say Y. Otherwise, say N.
199 tristate "FiberChannel Transport Attributes"
202 If you wish to export transport-specific information about
203 each attached FiberChannel device to sysfs, say Y.
208 menu "SCSI low-level drivers"
212 tristate "SGI WD93C93 SCSI Driver"
213 depends on SGI_IP22 && SCSI
215 If you have a Western Digital WD93 SCSI controller on
216 an SGI MIPS system, say Y. Otherwise, say N.
219 tristate "DEC NCR53C94 Scsi Driver"
220 depends on DECSTATION && TC && SCSI
222 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
223 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
226 tristate "DEC SII Scsi Driver"
227 depends on DECSTATION && SCSI
229 config BLK_DEV_3W_XXXX_RAID
230 tristate "3ware 5/6/7/8xxx ATA-RAID support"
231 depends on PCI && SCSI
233 3ware is the only hardware ATA-Raid product in Linux to date.
234 This card is 2,4, or 8 channel master mode support only.
235 SCSI support required!!!
237 <http://www.3ware.com/>
239 Please read the comments at the top of
240 <file:drivers/scsi/3w-xxxx.c>.
243 tristate "3ware 9xxx SATA-RAID support"
244 depends on PCI && SCSI
246 This driver supports the 9000 series 3ware SATA-RAID cards.
248 <http://www.amcc.com>
250 Please read the comments at the top of
251 <file:drivers/scsi/3w-9xxx.c>.
253 config SCSI_7000FASST
254 tristate "7000FASST SCSI support"
255 depends on ISA && SCSI
257 This driver supports the Western Digital 7000 SCSI host adapter
258 family. Some information is in the source:
259 <file:drivers/scsi/wd7000.c>.
261 To compile this driver as a module, choose M here: the
262 module will be called wd7000.
265 tristate "ACARD SCSI support"
266 depends on PCI && SCSI
268 This driver supports the ACARD 870U/W SCSI host adapter.
270 To compile this driver as a module, choose M here: the
271 module will be called atp870u.
274 tristate "Adaptec AHA152X/2825 support"
275 depends on ISA && SCSI && !64BIT
277 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
278 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
279 must be manually specified in this case.
281 It is explained in section 3.3 of the SCSI-HOWTO, available from
282 <http://www.tldp.org/docs.html#howto>. You might also want to
283 read the file <file:Documentation/scsi/aha152x.txt>.
285 To compile this driver as a module, choose M here: the
286 module will be called aha152x.
289 tristate "Adaptec AHA1542 support"
290 depends on ISA && SCSI
292 This is support for a SCSI host adapter. It is explained in section
293 3.4 of the SCSI-HOWTO, available from
294 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
295 purchased by Adaptec, and some former Trantor products are being
296 sold under the Adaptec name. If it doesn't work out of the box, you
297 may have to change some settings in <file:drivers/scsi/aha1542.h>.
299 To compile this driver as a module, choose M here: the
300 module will be called aha1542.
303 tristate "Adaptec AHA1740 support"
304 depends on EISA && SCSI
306 This is support for a SCSI host adapter. It is explained in section
307 3.5 of the SCSI-HOWTO, available from
308 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
309 of the box, you may have to change some settings in
310 <file:drivers/scsi/aha1740.h>.
312 To compile this driver as a module, choose M here: the
313 module will be called aha1740.
316 tristate "Adaptec AACRAID support (EXPERIMENTAL)"
317 depends on EXPERIMENTAL && SCSI && PCI
319 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
321 config SCSI_AIC7XXX_OLD
322 tristate "Adaptec AIC7xxx support (old driver)"
325 WARNING This driver is an older aic7xxx driver and is no longer
326 under active development. Adaptec, Inc. is writing a new driver to
327 take the place of this one, and it is recommended that whenever
328 possible, people should use the new Adaptec written driver instead
329 of this one. This driver will eventually be phased out entirely.
331 This is support for the various aic7xxx based Adaptec SCSI
332 controllers. These include the 274x EISA cards; 284x VLB cards;
333 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
334 motherboard based SCSI controllers from Adaptec. It does not support
335 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
336 support them. It does not support the 2920 cards from Adaptec that
337 use the Future Domain SCSI controller chip. For those cards, you
338 need the "Future Domain 16xx SCSI support" driver.
340 In general, if the controller is based on an Adaptec SCSI controller
341 chip from the aic777x series or the aic78xx series, this driver
342 should work. The only exception is the 7810 which is specifically
343 not supported (that's the RAID controller chip on the AAA-13x
346 Note that the AHA2920 SCSI host adapter is *not* supported by this
347 driver; choose "Future Domain 16xx SCSI support" instead if you have
350 Information on the configuration options for this controller can be
351 found by checking the help file for each of the available
352 configuration options. You should read
353 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
354 contacting the maintainer with any questions. The SCSI-HOWTO,
355 available from <http://www.tldp.org/docs.html#howto>, can also
358 To compile this driver as a module, choose M here: the
359 module will be called aic7xxx_old.
361 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
363 # All the I2O code and drivers do not seem to be 64bit safe.
365 tristate "Adaptec I2O RAID support "
366 depends on !64BIT && SCSI && PCI
368 This driver supports all of Adaptec's I2O based RAID controllers as
369 well as the DPT SmartRaid V cards. This is an Adaptec maintained
370 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
372 To compile this driver as a module, choose M here: the
373 module will be called dpt_i2o.
376 tristate "AdvanSys SCSI support"
377 depends on (ISA || EISA || PCI) && SCSI && BROKEN
379 This is a driver for all SCSI host adapters manufactured by
380 AdvanSys. It is documented in the kernel source in
381 <file:drivers/scsi/advansys.c>.
383 To compile this driver as a module, choose M here: the
384 module will be called advansys.
387 tristate "Always IN2000 SCSI support"
388 depends on ISA && SCSI
390 This is support for an ISA bus SCSI host adapter. You'll find more
391 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
392 out of the box, you may have to change the jumpers for IRQ or
395 To compile this driver as a module, choose M here: the
396 module will be called in2000.
399 tristate "AMI MegaRAID support"
400 depends on PCI && SCSI
402 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
403 and 467 SCSI host adapters.
405 To compile this driver as a module, choose M here: the
406 module will be called megaraid.
409 bool "Serial ATA (SATA) support"
410 depends on SCSI && EXPERIMENTAL
412 This driver family supports Serial ATA host controllers
418 tristate "ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL)"
419 depends on SCSI_SATA && PCI && EXPERIMENTAL
421 This option enables support for Broadcom/Serverworks/Apple K2
427 tristate "Intel PIIX/ICH SATA support"
428 depends on SCSI_SATA && PCI
430 This option enables support for ICH5 Serial ATA.
431 If PATA support was enabled previously, this enables
432 support for select Intel PIIX/ICH PATA host controllers.
437 tristate "NVIDIA SATA support"
438 depends on SCSI_SATA && PCI && EXPERIMENTAL
440 This option enables support for NVIDIA Serial ATA.
444 config SCSI_SATA_PROMISE
445 tristate "Promise SATA TX2/TX4 support"
446 depends on SCSI_SATA && PCI
448 This option enables support for Promise Serial ATA TX2/TX4.
453 tristate "Promise SATA SX4 support"
454 depends on SCSI_SATA && PCI && EXPERIMENTAL
456 This option enables support for Promise Serial ATA SX4.
461 tristate "Silicon Image SATA support"
462 depends on SCSI_SATA && PCI && EXPERIMENTAL
464 This option enables support for Silicon Image Serial ATA.
469 tristate "SiS 964/180 SATA support"
470 depends on SCSI_SATA && PCI
472 This option enables support for SiS Serial ATA 964/180.
477 tristate "VIA SATA support"
478 depends on SCSI_SATA && PCI && EXPERIMENTAL
480 This option enables support for VIA Serial ATA.
484 config SCSI_SATA_VITESSE
485 tristate "VITESSE VSC-7174 SATA support"
486 depends on SCSI_SATA && PCI && EXPERIMENTAL
488 This option enables support for Vitesse VSC7174 Serial ATA.
493 tristate "BusLogic SCSI support"
494 depends on (PCI || ISA || MCA) && SCSI
496 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
497 Adapters. Consult the SCSI-HOWTO, available from
498 <http://www.tldp.org/docs.html#howto>, and the files
499 <file:Documentation/scsi/BusLogic.txt> and
500 <file:Documentation/scsi/FlashPoint.txt> for more information.
502 To compile this driver as a module, choose M here: the
503 module will be called BusLogic.
505 config SCSI_OMIT_FLASHPOINT
506 bool "Omit FlashPoint support"
507 depends on SCSI_BUSLOGIC
509 This option allows you to omit the FlashPoint support from the
510 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
511 substantial, so users of MultiMaster Host Adapters may wish to omit
515 # This is marked broken because it uses over 4kB of stack in
517 # 2076 CpqTsProcessIMQEntry
521 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
522 depends on PCI && SCSI && BROKEN
524 Say Y here to compile in support for the Compaq StorageWorks Fibre
525 Channel 64-bit/66Mhz Host Bus Adapter.
528 tristate "DMX3191D SCSI support"
529 depends on PCI && SCSI
531 This is support for Domex DMX3191D SCSI Host Adapters.
533 To compile this driver as a module, choose M here: the
534 module will be called dmx3191d.
537 tristate "DTC3180/3280 SCSI support"
538 depends on ISA && SCSI
540 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
541 the SCSI-HOWTO, available from
542 <http://www.tldp.org/docs.html#howto>, and the file
543 <file:Documentation/scsi/dtc3x80.txt>.
545 To compile this driver as a module, choose M here: the
546 module will be called dtc.
549 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
550 depends on (ISA || EISA || PCI) && SCSI
552 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
553 ISA and all EISA I/O addresses are probed looking for the "EATA"
554 signature. The addresses of all the PCI SCSI controllers reported
555 by the PCI subsystem are probed as well.
557 You want to read the start of <file:drivers/scsi/eata.c> and the
558 SCSI-HOWTO, available from
559 <http://www.tldp.org/docs.html#howto>.
561 To compile this driver as a module, choose M here: the
562 module will be called eata.
564 config SCSI_EATA_TAGGED_QUEUE
565 bool "enable tagged command queueing"
568 This is a feature of SCSI-2 which improves performance: the host
569 adapter can send several SCSI commands to a device's queue even if
570 previous commands haven't finished yet.
571 This is equivalent to the "eata=tc:y" boot option.
573 config SCSI_EATA_LINKED_COMMANDS
574 bool "enable elevator sorting"
577 This option enables elevator sorting for all probed SCSI disks and
578 CD-ROMs. It definitely reduces the average seek distance when doing
579 random seeks, but this does not necessarily result in a noticeable
580 performance improvement: your mileage may vary...
581 This is equivalent to the "eata=lc:y" boot option.
583 config SCSI_EATA_MAX_TAGS
584 int "maximum number of queued commands"
588 This specifies how many SCSI commands can be maximally queued for
589 each probed SCSI device. You should reduce the default value of 16
590 only if you have disks with buggy or limited tagged command support.
591 Minimum is 2 and maximum is 62. This value is also the window size
592 used by the elevator sorting option above. The effective value used
593 by the driver for each probed SCSI device is reported at boot time.
594 This is equivalent to the "eata=mq:8" boot option.
597 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
600 This driver supports all EATA-PIO protocol compliant SCSI Host
601 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
602 host adapters could also use this driver but are discouraged from
603 doing so, since this driver only supports hard disks and lacks
604 numerous features. You might want to have a look at the SCSI-HOWTO,
605 available from <http://www.tldp.org/docs.html#howto>.
607 To compile this driver as a module, choose M here: the
608 module will be called eata_pio.
610 config SCSI_FUTURE_DOMAIN
611 tristate "Future Domain 16xx SCSI/AHA-2920A support"
612 depends on (ISA || PCI) && SCSI
614 This is support for Future Domain's 16-bit SCSI host adapters
615 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
616 other adapters based on the Future Domain chipsets (Quantum
617 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
618 It is explained in section 3.7 of the SCSI-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
622 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
623 controller support"). This Future Domain driver works with the older
624 Adaptec AHA-2920A boards with a Future Domain chip on them.
626 To compile this driver as a module, choose M here: the
627 module will be called fdomain.
630 tristate "Future Domain MCS-600/700 SCSI support"
631 depends on MCA_LEGACY && SCSI
633 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
634 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
635 is identical to the MCS 700 and hence also supported by this driver.
636 This driver also supports the Reply SB16/SCSI card (the SCSI part).
637 It supports multiple adapters in the same system.
639 To compile this driver as a module, choose M here: the
640 module will be called fd_mcs.
643 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
644 depends on (ISA || EISA || PCI) && SCSI
646 Formerly called GDT SCSI Disk Array Controller Support.
648 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
649 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
650 in the kernel source in <file:drivers/scsi/gdth.c> and
651 <file:drivers/scsi/gdth.h.>
653 To compile this driver as a module, choose M here: the
654 module will be called gdth.
656 config SCSI_GENERIC_NCR5380
657 tristate "Generic NCR5380/53c400 SCSI PIO support"
658 depends on ISA && SCSI
660 This is a driver for the old NCR 53c80 series of SCSI controllers
661 on boards using PIO. Most boards such as the Trantor T130 fit this
662 category, along with a large number of ISA 8bit controllers shipped
663 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
664 you should select the specific driver for that card rather than
665 generic 5380 support.
667 It is explained in section 3.8 of the SCSI-HOWTO, available from
668 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
669 of the box, you may have to change some settings in
670 <file:drivers/scsi/g_NCR5380.h>.
672 To compile this driver as a module, choose M here: the
673 module will be called g_NCR5380.
675 config SCSI_GENERIC_NCR5380_MMIO
676 tristate "Generic NCR5380/53c400 SCSI MMIO support"
677 depends on ISA && SCSI
679 This is a driver for the old NCR 53c80 series of SCSI controllers
680 on boards using memory mapped I/O.
681 It is explained in section 3.8 of the SCSI-HOWTO, available from
682 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
683 of the box, you may have to change some settings in
684 <file:drivers/scsi/g_NCR5380.h>.
686 To compile this driver as a module, choose M here: the
687 module will be called g_NCR5380_mmio.
689 config SCSI_GENERIC_NCR53C400
690 bool "Enable NCR53c400 extensions"
691 depends on SCSI_GENERIC_NCR5380
693 This enables certain optimizations for the NCR53c400 SCSI cards.
694 You might as well try it out. Note that this driver will only probe
695 for the Trantor T130B in its default configuration; you might have
696 to pass a command line option to the kernel at boot time if it does
697 not detect your card. See the file
698 <file:Documentation/scsi/g_NCR5380.txt> for details.
701 tristate "IBMMCA SCSI support"
702 depends on MCA_LEGACY && SCSI
704 This is support for the IBM SCSI adapter found in many of the PS/2
705 series computers. These machines have an MCA bus, so you need to
706 answer Y to "MCA support" as well and read
707 <file:Documentation/mca.txt>.
709 If the adapter isn't found during boot (a common problem for models
710 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
711 option, where <pun> is the id of the SCSI subsystem (usually 7, but
712 if that doesn't work check your reference diskette). Owners of
713 model 95 with a LED-matrix-display can in addition activate some
714 activity info like under OS/2, but more informative, by setting
715 'ibmmcascsi=display' as an additional kernel parameter. Try "man
716 bootparam" or see the documentation of your boot loader about how to
717 pass options to the kernel.
719 To compile this driver as a module, choose M here: the
720 module will be called ibmmca.
722 config IBMMCA_SCSI_ORDER_STANDARD
723 bool "Standard SCSI-order"
724 depends on SCSI_IBMMCA
726 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
727 are assigned to the drive letters, starting with the lowest SCSI-id
728 (physical number -- pun) to be drive C:, as seen from DOS and
729 similar operating systems. When looking into papers describing the
730 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
731 The SCSI-standard follows a hardware-hierarchy which says that id 7
732 has the highest priority and id 0 the lowest. Therefore, the host
733 adapters are still today everywhere placed as SCSI-id 7 by default.
734 In the SCSI-standard, the drive letters express the priority of the
735 disk. C: should be the hard disk, or a partition on it, with the
736 highest priority. This must therefore be the disk with the highest
737 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
738 original definition of the SCSI-standard as also industrial- and
739 process-control-machines, like VME-CPUs running under realtime-OSes
740 (e.g. LynxOS, OS9) do.
742 If you like to run Linux on your MCA-machine with the same
743 assignment of hard disks as seen from e.g. DOS or OS/2 on your
744 machine, which is in addition conformant to the SCSI-standard, you
745 must say Y here. This is also necessary for MCA-Linux users who want
746 to keep downward compatibility to older releases of the
747 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
750 If you like to have the lowest SCSI-id assigned as drive C:, as
751 modern SCSI-BIOSes do, which does not conform to the standard, but
752 is widespread and common in the PC-world of today, you must say N
753 here. If unsure, say Y.
755 config IBMMCA_SCSI_DEV_RESET
756 bool "Reset SCSI-devices at boottime"
757 depends on SCSI_IBMMCA
759 By default, SCSI-devices are reset when the machine is powered on.
760 However, some devices exist, like special-control-devices,
761 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
762 not reset when switched on. If you say Y here, each device connected
763 to your SCSI-bus will be issued a reset-command after it has been
764 probed, while the kernel is booting. This may cause problems with
765 more modern devices, like hard disks, which do not appreciate these
766 reset commands, and can cause your system to hang. So say Y only if
767 you know that one of your older devices needs it; N is the safe
771 tristate "IBM ServeRAID support"
772 depends on PCI && SCSI
774 This is support for the IBM ServeRAID hardware RAID controllers.
775 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
776 for more information. If this driver does not work correctly
777 without modification please contact the author by email at
778 ipslinux@adaptec.com.
780 To compile this driver as a module, choose M here: the
781 module will be called ips.
784 tristate "Initio 9100U(W) support"
785 depends on PCI && SCSI && BROKEN
787 This is support for the Initio 91XXU(W) SCSI host adapter. Please
788 read the SCSI-HOWTO, available from
789 <http://www.tldp.org/docs.html#howto>.
791 To compile this driver as a module, choose M here: the
792 module will be called initio.
795 tristate "Initio INI-A100U2W support"
796 depends on PCI && SCSI
798 This is support for the Initio INI-A100U2W SCSI host adapter.
799 Please read the SCSI-HOWTO, available from
800 <http://www.tldp.org/docs.html#howto>.
802 To compile this driver as a module, choose M here: the
803 module will be called a100u2w.
806 tristate "IOMEGA parallel port (ppa - older drives)"
807 depends on SCSI && PARPORT
809 This driver supports older versions of IOMEGA's parallel port ZIP
810 drive (a 100 MB removable media device).
812 Note that you can say N here if you have the SCSI version of the ZIP
813 drive: it will be supported automatically if you said Y to the
814 generic "SCSI disk support", above.
816 If you have the ZIP Plus drive or a more recent parallel port ZIP
817 drive (if the supplied cable with the drive is labeled "AutoDetect")
818 then you should say N here and Y to "IOMEGA parallel port (imm -
819 newer drives)", below.
821 For more information about this driver and how to use it you should
822 read the file <file:Documentation/scsi/ppa.txt>. You should also read
823 the SCSI-HOWTO, which is available from
824 <http://www.tldp.org/docs.html#howto>. If you use this driver,
825 you will still be able to use the parallel port for other tasks,
826 such as a printer; it is safe to compile both drivers into the
829 To compile this driver as a module, choose M here: the
830 module will be called ppa.
833 tristate "IOMEGA parallel port (imm - newer drives)"
834 depends on SCSI && PARPORT
836 This driver supports newer versions of IOMEGA's parallel port ZIP
837 drive (a 100 MB removable media device).
839 Note that you can say N here if you have the SCSI version of the ZIP
840 drive: it will be supported automatically if you said Y to the
841 generic "SCSI disk support", above.
843 If you have the ZIP Plus drive or a more recent parallel port ZIP
844 drive (if the supplied cable with the drive is labeled "AutoDetect")
845 then you should say Y here; if you have an older ZIP drive, say N
846 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
848 For more information about this driver and how to use it you should
849 read the file <file:Documentation/scsi/ppa.txt>. You should also read
850 the SCSI-HOWTO, which is available from
851 <http://www.tldp.org/docs.html#howto>. If you use this driver,
852 you will still be able to use the parallel port for other tasks,
853 such as a printer; it is safe to compile both drivers into the
856 To compile this driver as a module, choose M here: the
857 module will be called imm.
859 config SCSI_IZIP_EPP16
860 bool "ppa/imm option - Use slow (but safe) EPP-16"
861 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
863 EPP (Enhanced Parallel Port) is a standard for parallel ports which
864 allows them to act as expansion buses that can handle up to 64
867 Some parallel port chipsets are slower than their motherboard, and
868 so we have to control the state of the chipset's FIFO queue every
869 now and then to avoid data loss. This will be done if you say Y
872 Generally, saying Y is the safe option and slows things down a bit.
874 config SCSI_IZIP_SLOW_CTR
875 bool "ppa/imm option - Assume slow parport control register"
876 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
878 Some parallel ports are known to have excessive delays between
879 changing the parallel port control register and good data being
880 available on the parallel port data/status register. This option
881 forces a small delay (1.0 usec to be exact) after changing the
882 control register to let things settle out. Enabling this option may
883 result in a big drop in performance but some very old parallel ports
884 (found in 386 vintage machines) will not work properly.
886 Generally, saying N is fine.
888 config SCSI_NCR53C406A
889 tristate "NCR53c406a SCSI support"
890 depends on ISA && SCSI
892 This is support for the NCR53c406a SCSI host adapter. For user
893 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
894 in the kernel source. Also read the SCSI-HOWTO, available from
895 <http://www.tldp.org/docs.html#howto>.
897 To compile this driver as a module, choose M here: the
898 module will be called NCR53c406.
901 tristate "NCR Dual 700 MCA SCSI support"
902 depends on MCA && SCSI
903 select SCSI_SPI_ATTRS
905 This is a driver for the MicroChannel Dual 700 card produced by
906 NCR and commonly used in 345x/35xx/4100 class machines. It always
907 tries to negotiate sync and uses tag command queueing.
909 Unless you have an NCR manufactured machine, the chances are that
910 you do not have this SCSI card, so say N.
912 config 53C700_IO_MAPPED
914 depends on SCSI_NCR_D700
918 tristate "HP Lasi SCSI support for 53c700/710"
919 depends on GSC && SCSI
920 select SCSI_SPI_ATTRS
922 This is a driver for the SCSI controller in the Lasi chip found in
923 many PA-RISC workstations & servers. If you do not know whether you
924 have a Lasi chip, it is safe to say "Y" here.
926 config 53C700_MEM_MAPPED
928 depends on SCSI_LASI700
931 config 53C700_LE_ON_BE
933 depends on SCSI_LASI700
936 config SCSI_SYM53C8XX_2
937 tristate "SYM53C8XX Version 2 SCSI support"
938 depends on PCI && SCSI
939 select SCSI_SPI_ATTRS
941 This driver supports the whole NCR53C8XX/SYM53C8XX family of
942 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
943 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
944 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
945 controllers; you need to use the Fusion MPT driver for that.
947 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
950 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
951 int "DMA addressing mode"
952 depends on SCSI_SYM53C8XX_2
955 This option only applies to PCI-SCSI chips that are PCI DAC
956 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
958 When set to 0, the driver will program the chip to only perform
959 32-bit DMA. When set to 1, the chip will be able to perform DMA
960 to addresses up to 1TB. When set to 2, the driver supports the
961 full 64-bit DMA address range, but can only address 16 segments
962 of 4 GB each. This limits the total addressable range to 64 GB.
964 Most machines with less than 4GB of memory should use a setting
965 of 0 for best performance. If your machine has 4GB of memory
966 or more, you should set this option to 1 (the default).
968 The still experimental value 2 (64 bit DMA addressing with 16
969 x 4GB segments limitation) can be used on systems that require
970 PCI address bits past bit 39 to be set for the addressing of
971 memory using PCI DAC cycles.
973 config SCSI_SYM53C8XX_DEFAULT_TAGS
974 int "default tagged command queue depth"
975 depends on SCSI_SYM53C8XX_2
978 This is the default value of the command queue depth the
979 driver will announce to the generic SCSI layer for devices
980 that support tagged command queueing. This value can be changed
981 from the boot command line. This is a soft limit that cannot
982 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
984 config SCSI_SYM53C8XX_MAX_TAGS
985 int "maximum number of queued commands"
986 depends on SCSI_SYM53C8XX_2
989 This option allows you to specify the maximum number of commands
990 that can be queued to any device, when tagged command queuing is
991 possible. The driver supports up to 256 queued commands per device.
992 This value is used as a compiled-in hard limit.
994 config SCSI_SYM53C8XX_IOMAPPED
996 depends on SCSI_SYM53C8XX_2
998 If you say Y here, the driver will use port IO to access
999 the card. This is significantly slower then using memory
1000 mapped IO. Most people should answer N.
1003 tristate "IBM Power Linux RAID adapter support"
1004 depends on PCI && SCSI
1007 This driver supports the IBM Power Linux family RAID adapters.
1008 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1009 as IBM iSeries 5702, 5703, 5709, and 570A.
1011 config SCSI_IPR_TRACE
1012 bool "enable driver internal trace"
1015 If you say Y here, the driver will trace all commands issued
1016 to the adapter. Performance impact is minimal. Trace can be
1017 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1019 config SCSI_IPR_DUMP
1020 bool "enable adapter dump support"
1023 If you say Y here, the driver will support adapter crash dump.
1024 If you enable this support, the iprdump daemon can be used
1025 to capture adapter failure analysis information.
1028 tristate "Zalon SCSI support"
1029 depends on GSC && SCSI
1031 The Zalon is a GSC/HSC bus interface chip that sits between the
1032 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1033 C110, J200, J210 and some D, K & R-class machines. It's also
1034 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1035 Say Y here if you have one of these machines or cards.
1037 config SCSI_NCR_Q720
1038 tristate "NCR Quad 720 MCA SCSI support"
1039 depends on MCA && SCSI
1041 This is a driver for the MicroChannel Quad 720 card produced by
1042 NCR and commonly used in 345x/35xx/4100 class machines. It always
1043 tries to negotiate sync and uses tag command queueing.
1045 Unless you have an NCR manufactured machine, the chances are that
1046 you do not have this SCSI card, so say N.
1048 config SCSI_NCR53C8XX_DEFAULT_TAGS
1049 int " default tagged command queue depth"
1050 depends on SCSI_ZALON || SCSI_NCR_Q720
1053 "Tagged command queuing" is a feature of SCSI-2 which improves
1054 performance: the host adapter can send several SCSI commands to a
1055 device's queue even if previous commands haven't finished yet.
1056 Because the device is intelligent, it can optimize its operations
1057 (like head positioning) based on its own request queue. Some SCSI
1058 devices don't implement this properly; if you want to disable this
1059 feature, enter 0 or 1 here (it doesn't matter which).
1061 The default value is 8 and should be supported by most hard disks.
1062 This value can be overridden from the boot command line using the
1063 'tags' option as follows (example):
1064 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1065 4, set queue depth to 16 for target 2 and target 3 on controller 0
1066 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1068 The normal answer therefore is to go with the default 8 and to use
1069 a boot command line option for devices that need to use a different
1070 command queue depth.
1072 There is no safe option other than using good SCSI devices.
1074 config SCSI_NCR53C8XX_MAX_TAGS
1075 int " maximum number of queued commands"
1076 depends on SCSI_ZALON || SCSI_NCR_Q720
1079 This option allows you to specify the maximum number of commands
1080 that can be queued to any device, when tagged command queuing is
1081 possible. The default value is 32. Minimum is 2, maximum is 64.
1082 Modern hard disks are able to support 64 tags and even more, but
1083 do not seem to be faster when more than 32 tags are being used.
1085 So, the normal answer here is to go with the default value 32 unless
1086 you are using very large hard disks with large cache (>= 1 MB) that
1087 are able to take advantage of more than 32 tagged commands.
1089 There is no safe option and the default answer is recommended.
1091 config SCSI_NCR53C8XX_SYNC
1092 int " synchronous transfers frequency in MHz"
1093 depends on SCSI_ZALON || SCSI_NCR_Q720
1096 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1097 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1098 are respectively the maximum data transfer rates in mega-transfers
1099 per second for each class. For example, a FAST-20 Wide 16 device is
1100 able to transfer data at 20 million 16 bit packets per second for a
1101 total rate of 40 MB/s.
1103 You may specify 0 if you want to only use asynchronous data
1104 transfers. This is the safest and slowest option. Otherwise, specify
1105 a value between 5 and 80, depending on the capability of your SCSI
1106 controller. The higher the number, the faster the data transfer.
1107 Note that 80 should normally be ok since the driver decreases the
1108 value automatically according to the controller's capabilities.
1110 Your answer to this question is ignored for controllers with NVRAM,
1111 since the driver will get this information from the user set-up. It
1112 also can be overridden using a boot setup option, as follows
1113 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1114 for FAST-20 synchronous data transfer (20 mega-transfers per
1117 The normal answer therefore is not to go with the default but to
1118 select the maximum value 80 allowing the driver to use the maximum
1119 value supported by each controller. If this causes problems with
1120 your SCSI devices, you should come back and decrease the value.
1122 There is no safe option other than using good cabling, right
1123 terminations and SCSI conformant devices.
1125 config SCSI_NCR53C8XX_PROFILE
1126 bool " enable profiling"
1127 depends on SCSI_ZALON || SCSI_NCR_Q720
1129 This option allows you to enable profiling information gathering.
1130 These statistics are not very accurate due to the low frequency
1131 of the kernel clock (100 Hz on i386) and have performance impact
1132 on systems that use very fast devices.
1134 The normal answer therefore is N.
1136 config SCSI_NCR53C8XX_NO_DISCONNECT
1137 bool " not allow targets to disconnect"
1138 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1140 This option is only provided for safety if you suspect some SCSI
1141 device of yours to not support properly the target-disconnect
1142 feature. In that case, you would say Y here. In general however, to
1143 not allow targets to disconnect is not reasonable if there is more
1144 than 1 device on a SCSI bus. The normal answer therefore is N.
1146 config SCSI_MCA_53C9X
1147 tristate "NCR MCA 53C9x SCSI support"
1148 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1150 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1151 controller based on the NCR 53C94. This driver will allow use of
1152 the controller on the 3550, and very possibly others.
1154 To compile this driver as a module, choose M here: the
1155 module will be called mca_53c9x.
1158 tristate "PAS16 SCSI support"
1159 depends on ISA && SCSI
1161 This is support for a SCSI host adapter. It is explained in section
1162 3.10 of the SCSI-HOWTO, available from
1163 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1164 of the box, you may have to change some settings in
1165 <file:drivers/scsi/pas16.h>.
1167 To compile this driver as a module, choose M here: the
1168 module will be called pas16.
1171 tristate "PCI2000 support"
1172 depends on PCI && SCSI && BROKEN
1174 This is support for the PCI2000I EIDE interface card which acts as a
1175 SCSI host adapter. Please read the SCSI-HOWTO, available from
1176 <http://www.tldp.org/docs.html#howto>.
1178 To compile this driver as a module, choose M here: the
1179 module will be called pci2000.
1181 config SCSI_PCI2220I
1182 tristate "PCI2220i support"
1183 depends on PCI && SCSI && BROKEN
1185 This is support for the PCI2220i EIDE interface card which acts as a
1186 SCSI host adapter. Please read the SCSI-HOWTO, available from
1187 <http://www.tldp.org/docs.html#howto>.
1189 To compile this driver as a module, choose M here: the
1190 module will be called pci2220i.
1193 tristate "PSI240i support"
1194 depends on ISA && SCSI
1196 This is support for the PSI240i EIDE interface card which acts as a
1197 SCSI host adapter. Please read the SCSI-HOWTO, available from
1198 <http://www.tldp.org/docs.html#howto>.
1200 To compile this driver as a module, choose M here: the
1201 module will be called psi240i.
1203 config SCSI_QLOGIC_FAS
1204 tristate "Qlogic FAS SCSI support"
1205 depends on ISA && SCSI
1207 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1208 FastSCSI! cards as well as any other card based on the FASXX chip
1209 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1211 This driver does NOT support the PCI versions of these cards. The
1212 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1213 SCSI support"), below.
1215 Information about this driver is contained in
1216 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1217 SCSI-HOWTO, available from
1218 <http://www.tldp.org/docs.html#howto>.
1220 To compile this driver as a module, choose M here: the
1221 module will be called qlogicfas.
1223 config SCSI_QLOGIC_ISP
1224 tristate "Qlogic ISP SCSI support"
1225 depends on PCI && SCSI
1227 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1228 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1229 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1231 If you say Y here, make sure to choose "BIOS" at the question "PCI
1234 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1235 should also read the SCSI-HOWTO, available from
1236 <http://www.tldp.org/docs.html#howto>.
1238 To compile this driver as a module, choose M here: the
1239 module will be called qlogicisp.
1241 config SCSI_QLOGIC_FC
1242 tristate "Qlogic ISP FC SCSI support"
1243 depends on PCI && SCSI
1245 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1247 To compile this driver as a module, choose M here: the
1248 module will be called qlogicfc.
1250 config SCSI_QLOGIC_FC_FIRMWARE
1251 bool "Include loadable firmware in driver"
1252 depends on SCSI_QLOGIC_FC
1254 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1255 expanded LUN addressing and FcTape (FCP-2) support, in the
1256 qlogicfc driver. This is required on some platforms.
1258 config SCSI_QLOGIC_1280
1259 tristate "Qlogic QLA 1280 SCSI support"
1260 depends on PCI && SCSI
1262 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1264 To compile this driver as a module, choose M here: the
1265 module will be called qla1280.
1267 config SCSI_QLOGICPTI
1268 tristate "PTI Qlogic, ISP Driver"
1269 depends on SBUS && SCSI
1271 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1272 controllers are known under Solaris as qpti and in the openprom as
1273 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1274 driven by a different driver.
1276 To compile this driver as a module, choose M here: the
1277 module will be called qlogicpti.
1279 source "drivers/scsi/qla2xxx/Kconfig"
1282 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1283 depends on X86 && ISA && SCSI && BROKEN
1285 These are 8-bit SCSI controllers; the ST-01 is also supported by
1286 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1287 available from <http://www.tldp.org/docs.html#howto>. If it
1288 doesn't work out of the box, you may have to change some settings in
1289 <file:drivers/scsi/seagate.h>.
1291 To compile this driver as a module, choose M here: the
1292 module will be called seagate.
1294 # definitely looks not 64bit safe:
1296 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1297 depends on (EISA || MCA) && SCSI
1298 select SCSI_SPI_ATTRS
1300 This driver for NCR53c710 based SCSI host adapters.
1302 It currently supports Compaq EISA cards and NCR MCA cards
1304 config 53C700_IO_MAPPED
1306 depends on SCSI_SIM710
1309 config SCSI_SYM53C416
1310 tristate "Symbios 53c416 SCSI support"
1311 depends on ISA && SCSI
1313 This is support for the sym53c416 SCSI host adapter, the SCSI
1314 adapter that comes with some HP scanners. This driver requires that
1315 the sym53c416 is configured first using some sort of PnP
1316 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1317 are using isapnp then you need to compile this driver as a module
1318 and then load it using insmod after isapnp has run. The parameters
1319 of the configured card(s) should be passed to the driver. The format
1322 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1324 To compile this driver as a module, choose M here: the
1325 module will be called sym53c416.
1328 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1329 depends on PCI && SCSI && EXPERIMENTAL
1331 This driver supports PCI SCSI host adapters based on the ASIC
1332 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1334 This driver works, but is still in experimental status. So better
1335 have a bootable disk and a backup in case of emergency.
1337 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1339 To compile this driver as a module, choose M here: the
1340 module will be called dc395x.
1343 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1344 depends on PCI && SCSI
1346 This driver supports PCI SCSI host adapters based on the Am53C974A
1347 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1348 PCscsi/PCnet (Am53/79C974) solutions.
1350 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1352 Note that this driver does NOT support Tekram DC390W/U/F, which are
1353 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1355 To compile this driver as a module, choose M here: the
1356 module will be called tmscsim.
1359 tristate "Trantor T128/T128F/T228 SCSI support"
1360 depends on ISA && SCSI
1362 This is support for a SCSI host adapter. It is explained in section
1363 3.11 of the SCSI-HOWTO, available from
1364 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1365 of the box, you may have to change some settings in
1366 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1367 Adaptec, and some former Trantor products are being sold under the
1370 To compile this driver as a module, choose M here: the
1371 module will be called t128.
1374 tristate "UltraStor 14F/34F support"
1375 depends on ISA && SCSI
1377 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1378 The source at <file:drivers/scsi/u14-34f.c> contains some
1379 information about this hardware. If the driver doesn't work out of
1380 the box, you may have to change some settings in
1381 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1382 <http://www.tldp.org/docs.html#howto>. Note that there is also
1383 another driver for the same hardware: "UltraStor SCSI support",
1384 below. You should say Y to both only if you want 24F support as
1387 To compile this driver as a module, choose M here: the
1388 module will be called u14-34f.
1390 config SCSI_U14_34F_TAGGED_QUEUE
1391 bool "enable tagged command queueing"
1392 depends on SCSI_U14_34F
1394 This is a feature of SCSI-2 which improves performance: the host
1395 adapter can send several SCSI commands to a device's queue even if
1396 previous commands haven't finished yet.
1397 This is equivalent to the "u14-34f=tc:y" boot option.
1399 config SCSI_U14_34F_LINKED_COMMANDS
1400 bool "enable elevator sorting"
1401 depends on SCSI_U14_34F
1403 This option enables elevator sorting for all probed SCSI disks and
1404 CD-ROMs. It definitely reduces the average seek distance when doing
1405 random seeks, but this does not necessarily result in a noticeable
1406 performance improvement: your mileage may vary...
1407 This is equivalent to the "u14-34f=lc:y" boot option.
1409 config SCSI_U14_34F_MAX_TAGS
1410 int "maximum number of queued commands"
1411 depends on SCSI_U14_34F
1414 This specifies how many SCSI commands can be maximally queued for
1415 each probed SCSI device. You should reduce the default value of 8
1416 only if you have disks with buggy or limited tagged command support.
1417 Minimum is 2 and maximum is 14. This value is also the window size
1418 used by the elevator sorting option above. The effective value used
1419 by the driver for each probed SCSI device is reported at boot time.
1420 This is equivalent to the "u14-34f=mq:8" boot option.
1422 config SCSI_ULTRASTOR
1423 tristate "UltraStor SCSI support"
1424 depends on X86 && ISA && SCSI
1426 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1427 adapter family. This driver is explained in section 3.12 of the
1428 SCSI-HOWTO, available from
1429 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1430 of the box, you may have to change some settings in
1431 <file:drivers/scsi/ultrastor.h>.
1433 Note that there is also another driver for the same hardware:
1434 "UltraStor 14F/34F support", above.
1436 To compile this driver as a module, choose M here: the
1437 module will be called ultrastor.
1440 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1441 depends on PCI && SCSI && !64BIT
1443 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1444 SCSI host adapter. Please read the SCSI-HOWTO, available from
1445 <http://www.tldp.org/docs.html#howto>.
1447 To compile this driver as a module, choose M here: the
1448 module will be called nsp32.
1451 tristate "SCSI debugging host simulator"
1454 This is a host adapter simulator that can simulate multiple hosts
1455 each with multiple dummy SCSI devices (disks). It defaults to one
1456 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1457 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1458 dummy disks are simulated, they share the same kernel RAM for
1459 their storage. See http://www.torque.net/sg/sdebug.html for more
1460 information. This driver is primarily of use to those testing the
1461 SCSI and block subsystems. If unsure, say N.
1464 tristate "MESH (Power Mac internal SCSI) support"
1465 depends on PPC_PMAC && SCSI
1467 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1468 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1469 other Power Macintoshes do). Say Y to include support for this SCSI
1472 To compile this driver as a module, choose M here: the
1473 module will be called mesh.
1475 config SCSI_MESH_SYNC_RATE
1476 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1477 depends on SCSI_MESH
1480 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1481 drives a bus which is entirely internal to the machine (such as the
1482 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1483 operation at up to 10 MB/s. On machines where the SCSI bus
1484 controlled by the MESH can have external devices connected, it is
1485 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1486 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1487 to disable synchronous operation.
1489 config SCSI_MESH_RESET_DELAY_MS
1490 int "initial bus reset delay (ms) (0 = no reset)"
1491 depends on SCSI_MESH
1494 config SCSI_MAC53C94
1495 tristate "53C94 (Power Mac external SCSI) support"
1496 depends on PPC_PMAC && SCSI
1498 On Power Macintoshes (and clones) with two SCSI buses, the external
1499 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1500 machines which only have one SCSI bus, such as the 7200, also use
1501 the 53C94. Say Y to include support for the 53C94.
1503 To compile this driver as a module, choose M here: the
1504 module will be called mac53c94.
1506 source "drivers/scsi/arm/Kconfig"
1509 bool "MIPS JAZZ FAS216 SCSI support"
1510 depends on MIPS_JAZZ && SCSI
1512 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1513 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1517 tristate "A3000 WD33C93A support"
1518 depends on AMIGA && SCSI
1520 If you have an Amiga 3000 and have SCSI devices connected to the
1521 built-in SCSI controller, say Y. Otherwise, say N.
1523 To compile this driver as a module, choose M here: the
1524 module will be called wd33c93.
1527 tristate "A2091/A590 WD33C93A support"
1528 depends on ZORRO && SCSI
1530 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1533 To compile this driver as a module, choose M here: the
1534 module will be called wd33c93.
1537 tristate "GVP Series II WD33C93A support"
1538 depends on ZORRO && SCSI
1540 If you have a Great Valley Products Series II SCSI controller,
1541 answer Y. Also say Y if you have a later model of GVP SCSI
1542 controller (such as the GVP A4008 or a Combo board). Otherwise,
1543 answer N. This driver does NOT work for the T-Rex series of
1544 accelerators from TekMagic and GVP-M.
1546 To compile this driver as a module, choose M here: the
1547 module will be called gvp11.
1549 config CYBERSTORM_SCSI
1550 tristate "CyberStorm SCSI support"
1551 depends on ZORRO && SCSI
1553 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1554 accelerator board and the optional Cyberstorm SCSI controller,
1555 answer Y. Otherwise, say N.
1557 config CYBERSTORMII_SCSI
1558 tristate "CyberStorm Mk II SCSI support"
1559 depends on ZORRO && SCSI
1561 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1562 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1566 tristate "Blizzard 2060 SCSI support"
1567 depends on ZORRO && SCSI
1569 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1570 and want to use the onboard SCSI controller, say Y. Otherwise,
1574 tristate "Blizzard 1230IV/1260 SCSI support"
1575 depends on ZORRO && SCSI
1577 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1578 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1581 config FASTLANE_SCSI
1582 tristate "Fastlane SCSI support"
1583 depends on ZORRO && SCSI
1585 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1586 one in the near future, say Y to this question. Otherwise, say N.
1588 config SCSI_AMIGA7XX
1589 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1590 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1592 Support for various NCR53c710-based SCSI controllers on the Amiga.
1594 - the builtin SCSI controller on the Amiga 4000T,
1595 - the Amiga 4091 Zorro III SCSI-2 controller,
1596 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1598 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1599 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1600 accelerator card for the Amiga 1200,
1601 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1602 Note that all of the above SCSI controllers, except for the builtin
1603 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1604 bus, so you also have to enable Zorro bus support if you want to use
1608 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1609 depends on ZORRO && SCSI && EXPERIMENTAL
1611 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1612 Y to this question. If you're in doubt about whether you have one,
1614 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1617 tristate "Atari native SCSI support"
1618 depends on ATARI && SCSI && BROKEN
1620 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1621 Falcon, ...) say Y to get it supported. Of course also, if you have
1622 a compatible SCSI controller (e.g. for Medusa).
1624 To compile this driver as a module, choose M here: the
1625 module will be called atari_scsi.
1627 This driver supports both styles of NCR integration into the
1628 system: the TT style (separate DMA), and the Falcon style (via
1629 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1630 in the Hades (without DMA).
1632 config ATARI_SCSI_TOSHIBA_DELAY
1633 bool "Long delays for Toshiba CD-ROMs"
1634 depends on ATARI_SCSI
1636 This option increases the delay after a SCSI arbitration to
1637 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1638 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1639 would impact performance a bit, so say N.
1641 config ATARI_SCSI_RESET_BOOT
1642 bool "Reset SCSI-devices at boottime"
1643 depends on ATARI_SCSI
1645 Reset the devices on your Atari whenever it boots. This makes the
1646 boot process fractionally longer but may assist recovery from errors
1647 that leave the devices with SCSI operations partway completed.
1650 bool "Hades SCSI DMA emulator"
1651 depends on ATARI_SCSI && HADES
1653 This option enables code which emulates the TT SCSI DMA chip on the
1654 Hades. This increases the SCSI transfer rates at least ten times
1655 compared to PIO transfers.
1658 bool "Macintosh NCR5380 SCSI"
1659 depends on MAC && SCSI
1661 This is the NCR 5380 SCSI controller included on most of the 68030
1662 based Macintoshes. If you have one of these say Y and read the
1663 SCSI-HOWTO, available from
1664 <http://www.tldp.org/docs.html#howto>.
1667 tristate "Macintosh NCR53c9[46] SCSI"
1668 depends on MAC && SCSI
1670 This is the NCR 53c9x SCSI controller found on most of the 68040
1671 based Macintoshes. If you have one of these say Y and read the
1672 SCSI-HOWTO, available from
1673 <http://www.tldp.org/docs.html#howto>.
1675 To compile this driver as a module, choose M here: the
1676 module will be called mac_esp.
1679 bool "WD33C93 SCSI driver for MVME147"
1680 depends on MVME147 && SCSI
1682 Support for the on-board SCSI controller on the Motorola MVME147
1683 single-board computer.
1686 bool "NCR53C710 SCSI driver for MVME16x"
1687 depends on MVME16x && SCSI && BROKEN
1689 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1690 SCSI controller chip. Almost everyone using one of these boards
1691 will want to say Y to this question.
1693 config BVME6000_SCSI
1694 bool "NCR53C710 SCSI driver for BVME6000"
1695 depends on BVME6000 && SCSI && BROKEN
1697 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1698 SCSI controller chip. Almost everyone using one of these boards
1699 will want to say Y to this question.
1701 config SCSI_NCR53C7xx_FAST
1702 bool "allow FAST-SCSI [10MHz]"
1703 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1705 This will enable 10MHz FAST-SCSI transfers with your host
1706 adapter. Some systems have problems with that speed, so it's safest
1710 tristate "Sun3 NCR5380 SCSI"
1711 depends on SUN3 && SCSI
1713 This option will enable support for the OBIO (onboard io) NCR5380
1714 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1715 "Sun3" type VME scsi controllers also based on the NCR5380.
1716 General Linux information on the Sun 3 series (now discontinued)
1717 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1720 bool "Sun3x ESP SCSI"
1721 depends on SUN3X && SCSI
1723 The ESP was an on-board SCSI controller used on Sun 3/80
1724 machines. Say Y here to compile in support for it.
1727 tristate "Sparc ESP Scsi Driver"
1728 depends on SBUS && SCSI
1730 This is the driver for the Sun ESP SCSI host adapter. The ESP
1731 chipset is present in most SPARC SBUS-based computers.
1733 To compile this driver as a module, choose M here: the
1734 module will be called esp.
1736 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1739 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1740 depends on ARCH_S390 && SCSI
1741 select SCSI_FC_ATTRS
1743 If you want to access SCSI devices attached to your IBM eServer
1744 zSeries by means of Fibre Channel interfaces say Y.
1745 For details please refer to the documentation provided by IBM at
1746 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1748 This driver is also available as a module. This module will be
1749 called zfcp. If you want to compile it as a module, say M here
1750 and read Documentation/modules.txt.
1754 source "drivers/scsi/pcmcia/Kconfig"