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)"
323 depends on (ISA || EISA || PCI ) && SCSI
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.
398 source "drivers/scsi/megaraid/Kconfig.megaraid"
401 bool "Serial ATA (SATA) support"
402 depends on SCSI && EXPERIMENTAL
404 This driver family supports Serial ATA host controllers
409 config SCSI_SATA_AHCI
410 tristate "AHCI SATA support"
411 depends on SCSI_SATA && PCI && EXPERIMENTAL
413 This option enables support for AHCI Serial ATA.
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 && (BROKEN || !SPARC64)
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 && (BROKEN || !SPARC64)
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"
598 depends on (ISA || EISA || PCI) && SCSI
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.
611 tristate "Emulex LightPulse Fibre Channel Support"
612 depends on PCI && SCSI
614 This lpfc driver supports the Emulex LightPulse
615 family of Fibre Channel PCI host adapters.
617 config SCSI_FUTURE_DOMAIN
618 tristate "Future Domain 16xx SCSI/AHA-2920A support"
619 depends on (ISA || PCI) && SCSI
621 This is support for Future Domain's 16-bit SCSI host adapters
622 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
623 other adapters based on the Future Domain chipsets (Quantum
624 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
625 It is explained in section 3.7 of the SCSI-HOWTO, available from
626 <http://www.tldp.org/docs.html#howto>.
628 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
629 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
630 controller support"). This Future Domain driver works with the older
631 Adaptec AHA-2920A boards with a Future Domain chip on them.
633 To compile this driver as a module, choose M here: the
634 module will be called fdomain.
637 tristate "Future Domain MCS-600/700 SCSI support"
638 depends on MCA_LEGACY && SCSI
640 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
641 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
642 is identical to the MCS 700 and hence also supported by this driver.
643 This driver also supports the Reply SB16/SCSI card (the SCSI part).
644 It supports multiple adapters in the same system.
646 To compile this driver as a module, choose M here: the
647 module will be called fd_mcs.
650 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
651 depends on (ISA || EISA || PCI) && SCSI && (BROKEN || !SPARC64)
653 Formerly called GDT SCSI Disk Array Controller Support.
655 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
656 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
657 in the kernel source in <file:drivers/scsi/gdth.c> and
658 <file:drivers/scsi/gdth.h.>
660 To compile this driver as a module, choose M here: the
661 module will be called gdth.
663 config SCSI_GENERIC_NCR5380
664 tristate "Generic NCR5380/53c400 SCSI PIO support"
665 depends on ISA && SCSI
667 This is a driver for the old NCR 53c80 series of SCSI controllers
668 on boards using PIO. Most boards such as the Trantor T130 fit this
669 category, along with a large number of ISA 8bit controllers shipped
670 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
671 you should select the specific driver for that card rather than
672 generic 5380 support.
674 It is explained in section 3.8 of the SCSI-HOWTO, available from
675 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
676 of the box, you may have to change some settings in
677 <file:drivers/scsi/g_NCR5380.h>.
679 To compile this driver as a module, choose M here: the
680 module will be called g_NCR5380.
682 config SCSI_GENERIC_NCR5380_MMIO
683 tristate "Generic NCR5380/53c400 SCSI MMIO support"
684 depends on ISA && SCSI
686 This is a driver for the old NCR 53c80 series of SCSI controllers
687 on boards using memory mapped I/O.
688 It is explained in section 3.8 of the SCSI-HOWTO, available from
689 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
690 of the box, you may have to change some settings in
691 <file:drivers/scsi/g_NCR5380.h>.
693 To compile this driver as a module, choose M here: the
694 module will be called g_NCR5380_mmio.
696 config SCSI_GENERIC_NCR53C400
697 bool "Enable NCR53c400 extensions"
698 depends on SCSI_GENERIC_NCR5380
700 This enables certain optimizations for the NCR53c400 SCSI cards.
701 You might as well try it out. Note that this driver will only probe
702 for the Trantor T130B in its default configuration; you might have
703 to pass a command line option to the kernel at boot time if it does
704 not detect your card. See the file
705 <file:Documentation/scsi/g_NCR5380.txt> for details.
708 tristate "IBMMCA SCSI support"
709 depends on MCA_LEGACY && SCSI
711 This is support for the IBM SCSI adapter found in many of the PS/2
712 series computers. These machines have an MCA bus, so you need to
713 answer Y to "MCA support" as well and read
714 <file:Documentation/mca.txt>.
716 If the adapter isn't found during boot (a common problem for models
717 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
718 option, where <pun> is the id of the SCSI subsystem (usually 7, but
719 if that doesn't work check your reference diskette). Owners of
720 model 95 with a LED-matrix-display can in addition activate some
721 activity info like under OS/2, but more informative, by setting
722 'ibmmcascsi=display' as an additional kernel parameter. Try "man
723 bootparam" or see the documentation of your boot loader about how to
724 pass options to the kernel.
726 To compile this driver as a module, choose M here: the
727 module will be called ibmmca.
729 config IBMMCA_SCSI_ORDER_STANDARD
730 bool "Standard SCSI-order"
731 depends on SCSI_IBMMCA
733 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
734 are assigned to the drive letters, starting with the lowest SCSI-id
735 (physical number -- pun) to be drive C:, as seen from DOS and
736 similar operating systems. When looking into papers describing the
737 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
738 The SCSI-standard follows a hardware-hierarchy which says that id 7
739 has the highest priority and id 0 the lowest. Therefore, the host
740 adapters are still today everywhere placed as SCSI-id 7 by default.
741 In the SCSI-standard, the drive letters express the priority of the
742 disk. C: should be the hard disk, or a partition on it, with the
743 highest priority. This must therefore be the disk with the highest
744 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
745 original definition of the SCSI-standard as also industrial- and
746 process-control-machines, like VME-CPUs running under realtime-OSes
747 (e.g. LynxOS, OS9) do.
749 If you like to run Linux on your MCA-machine with the same
750 assignment of hard disks as seen from e.g. DOS or OS/2 on your
751 machine, which is in addition conformant to the SCSI-standard, you
752 must say Y here. This is also necessary for MCA-Linux users who want
753 to keep downward compatibility to older releases of the
754 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
757 If you like to have the lowest SCSI-id assigned as drive C:, as
758 modern SCSI-BIOSes do, which does not conform to the standard, but
759 is widespread and common in the PC-world of today, you must say N
760 here. If unsure, say Y.
762 config IBMMCA_SCSI_DEV_RESET
763 bool "Reset SCSI-devices at boottime"
764 depends on SCSI_IBMMCA
766 By default, SCSI-devices are reset when the machine is powered on.
767 However, some devices exist, like special-control-devices,
768 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
769 not reset when switched on. If you say Y here, each device connected
770 to your SCSI-bus will be issued a reset-command after it has been
771 probed, while the kernel is booting. This may cause problems with
772 more modern devices, like hard disks, which do not appreciate these
773 reset commands, and can cause your system to hang. So say Y only if
774 you know that one of your older devices needs it; N is the safe
778 tristate "IBM ServeRAID support"
779 depends on PCI && SCSI
781 This is support for the IBM ServeRAID hardware RAID controllers.
782 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
783 for more information. If this driver does not work correctly
784 without modification please contact the author by email at
785 ipslinux@adaptec.com.
787 To compile this driver as a module, choose M here: the
788 module will be called ips.
791 tristate "IBM Virtual SCSI support"
792 depends on PPC_PSERIES || PPC_ISERIES
794 This is the IBM POWER Virtual SCSI Client
796 To compile this driver as a module, choose M here: the
797 module will be called ibmvscsic.
800 tristate "Initio 9100U(W) support"
801 depends on PCI && SCSI
803 This is support for the Initio 91XXU(W) SCSI host adapter. Please
804 read the SCSI-HOWTO, available from
805 <http://www.tldp.org/docs.html#howto>.
807 To compile this driver as a module, choose M here: the
808 module will be called initio.
811 tristate "Initio INI-A100U2W support"
812 depends on PCI && SCSI
814 This is support for the Initio INI-A100U2W SCSI host adapter.
815 Please read the SCSI-HOWTO, available from
816 <http://www.tldp.org/docs.html#howto>.
818 To compile this driver as a module, choose M here: the
819 module will be called a100u2w.
822 tristate "IOMEGA parallel port (ppa - older drives)"
823 depends on SCSI && PARPORT
825 This driver supports older versions of IOMEGA's parallel port ZIP
826 drive (a 100 MB removable media device).
828 Note that you can say N here if you have the SCSI version of the ZIP
829 drive: it will be supported automatically if you said Y to the
830 generic "SCSI disk support", above.
832 If you have the ZIP Plus drive or a more recent parallel port ZIP
833 drive (if the supplied cable with the drive is labeled "AutoDetect")
834 then you should say N here and Y to "IOMEGA parallel port (imm -
835 newer drives)", below.
837 For more information about this driver and how to use it you should
838 read the file <file:Documentation/scsi/ppa.txt>. You should also read
839 the SCSI-HOWTO, which is available from
840 <http://www.tldp.org/docs.html#howto>. If you use this driver,
841 you will still be able to use the parallel port for other tasks,
842 such as a printer; it is safe to compile both drivers into the
845 To compile this driver as a module, choose M here: the
846 module will be called ppa.
849 tristate "IOMEGA parallel port (imm - newer drives)"
850 depends on SCSI && PARPORT
852 This driver supports newer versions of IOMEGA's parallel port ZIP
853 drive (a 100 MB removable media device).
855 Note that you can say N here if you have the SCSI version of the ZIP
856 drive: it will be supported automatically if you said Y to the
857 generic "SCSI disk support", above.
859 If you have the ZIP Plus drive or a more recent parallel port ZIP
860 drive (if the supplied cable with the drive is labeled "AutoDetect")
861 then you should say Y here; if you have an older ZIP drive, say N
862 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
864 For more information about this driver and how to use it you should
865 read the file <file:Documentation/scsi/ppa.txt>. You should also read
866 the SCSI-HOWTO, which is available from
867 <http://www.tldp.org/docs.html#howto>. If you use this driver,
868 you will still be able to use the parallel port for other tasks,
869 such as a printer; it is safe to compile both drivers into the
872 To compile this driver as a module, choose M here: the
873 module will be called imm.
875 config SCSI_IZIP_EPP16
876 bool "ppa/imm option - Use slow (but safe) EPP-16"
877 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
879 EPP (Enhanced Parallel Port) is a standard for parallel ports which
880 allows them to act as expansion buses that can handle up to 64
883 Some parallel port chipsets are slower than their motherboard, and
884 so we have to control the state of the chipset's FIFO queue every
885 now and then to avoid data loss. This will be done if you say Y
888 Generally, saying Y is the safe option and slows things down a bit.
890 config SCSI_IZIP_SLOW_CTR
891 bool "ppa/imm option - Assume slow parport control register"
892 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
894 Some parallel ports are known to have excessive delays between
895 changing the parallel port control register and good data being
896 available on the parallel port data/status register. This option
897 forces a small delay (1.0 usec to be exact) after changing the
898 control register to let things settle out. Enabling this option may
899 result in a big drop in performance but some very old parallel ports
900 (found in 386 vintage machines) will not work properly.
902 Generally, saying N is fine.
904 config SCSI_NCR53C406A
905 tristate "NCR53c406a SCSI support"
906 depends on ISA && SCSI
908 This is support for the NCR53c406a SCSI host adapter. For user
909 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
910 in the kernel source. Also read the SCSI-HOWTO, available from
911 <http://www.tldp.org/docs.html#howto>.
913 To compile this driver as a module, choose M here: the
914 module will be called NCR53c406.
917 tristate "NCR Dual 700 MCA SCSI support"
918 depends on MCA && SCSI
919 select SCSI_SPI_ATTRS
921 This is a driver for the MicroChannel Dual 700 card produced by
922 NCR and commonly used in 345x/35xx/4100 class machines. It always
923 tries to negotiate sync and uses tag command queueing.
925 Unless you have an NCR manufactured machine, the chances are that
926 you do not have this SCSI card, so say N.
928 config 53C700_IO_MAPPED
930 depends on SCSI_NCR_D700
934 tristate "HP Lasi SCSI support for 53c700/710"
935 depends on GSC && SCSI
936 select SCSI_SPI_ATTRS
938 This is a driver for the SCSI controller in the Lasi chip found in
939 many PA-RISC workstations & servers. If you do not know whether you
940 have a Lasi chip, it is safe to say "Y" here.
942 config 53C700_MEM_MAPPED
944 depends on SCSI_LASI700
947 config 53C700_LE_ON_BE
949 depends on SCSI_LASI700
952 config SCSI_SYM53C8XX_2
953 tristate "SYM53C8XX Version 2 SCSI support"
954 depends on PCI && SCSI
955 select SCSI_SPI_ATTRS
957 This driver supports the whole NCR53C8XX/SYM53C8XX family of
958 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
959 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
960 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
961 controllers; you need to use the Fusion MPT driver for that.
963 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
966 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
967 int "DMA addressing mode"
968 depends on SCSI_SYM53C8XX_2
971 This option only applies to PCI-SCSI chips that are PCI DAC
972 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
974 When set to 0, the driver will program the chip to only perform
975 32-bit DMA. When set to 1, the chip will be able to perform DMA
976 to addresses up to 1TB. When set to 2, the driver supports the
977 full 64-bit DMA address range, but can only address 16 segments
978 of 4 GB each. This limits the total addressable range to 64 GB.
980 Most machines with less than 4GB of memory should use a setting
981 of 0 for best performance. If your machine has 4GB of memory
982 or more, you should set this option to 1 (the default).
984 The still experimental value 2 (64 bit DMA addressing with 16
985 x 4GB segments limitation) can be used on systems that require
986 PCI address bits past bit 39 to be set for the addressing of
987 memory using PCI DAC cycles.
989 config SCSI_SYM53C8XX_DEFAULT_TAGS
990 int "default tagged command queue depth"
991 depends on SCSI_SYM53C8XX_2
994 This is the default value of the command queue depth the
995 driver will announce to the generic SCSI layer for devices
996 that support tagged command queueing. This value can be changed
997 from the boot command line. This is a soft limit that cannot
998 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1000 config SCSI_SYM53C8XX_MAX_TAGS
1001 int "maximum number of queued commands"
1002 depends on SCSI_SYM53C8XX_2
1005 This option allows you to specify the maximum number of commands
1006 that can be queued to any device, when tagged command queuing is
1007 possible. The driver supports up to 256 queued commands per device.
1008 This value is used as a compiled-in hard limit.
1010 config SCSI_SYM53C8XX_IOMAPPED
1012 depends on SCSI_SYM53C8XX_2
1014 If you say Y here, the driver will use port IO to access
1015 the card. This is significantly slower then using memory
1016 mapped IO. Most people should answer N.
1019 tristate "IBM Power Linux RAID adapter support"
1020 depends on PCI && SCSI
1023 This driver supports the IBM Power Linux family RAID adapters.
1024 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1025 as IBM iSeries 5702, 5703, 5709, and 570A.
1027 config SCSI_IPR_TRACE
1028 bool "enable driver internal trace"
1031 If you say Y here, the driver will trace all commands issued
1032 to the adapter. Performance impact is minimal. Trace can be
1033 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1035 config SCSI_IPR_DUMP
1036 bool "enable adapter dump support"
1039 If you say Y here, the driver will support adapter crash dump.
1040 If you enable this support, the iprdump daemon can be used
1041 to capture adapter failure analysis information.
1044 tristate "Zalon SCSI support"
1045 depends on GSC && SCSI
1047 The Zalon is a GSC/HSC bus interface chip that sits between the
1048 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1049 C110, J200, J210 and some D, K & R-class machines. It's also
1050 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1051 Say Y here if you have one of these machines or cards.
1053 config SCSI_NCR_Q720
1054 tristate "NCR Quad 720 MCA SCSI support"
1055 depends on MCA && SCSI
1057 This is a driver for the MicroChannel Quad 720 card produced by
1058 NCR and commonly used in 345x/35xx/4100 class machines. It always
1059 tries to negotiate sync and uses tag command queueing.
1061 Unless you have an NCR manufactured machine, the chances are that
1062 you do not have this SCSI card, so say N.
1064 config SCSI_NCR53C8XX_DEFAULT_TAGS
1065 int " default tagged command queue depth"
1066 depends on SCSI_ZALON || SCSI_NCR_Q720
1069 "Tagged command queuing" is a feature of SCSI-2 which improves
1070 performance: the host adapter can send several SCSI commands to a
1071 device's queue even if previous commands haven't finished yet.
1072 Because the device is intelligent, it can optimize its operations
1073 (like head positioning) based on its own request queue. Some SCSI
1074 devices don't implement this properly; if you want to disable this
1075 feature, enter 0 or 1 here (it doesn't matter which).
1077 The default value is 8 and should be supported by most hard disks.
1078 This value can be overridden from the boot command line using the
1079 'tags' option as follows (example):
1080 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1081 4, set queue depth to 16 for target 2 and target 3 on controller 0
1082 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1084 The normal answer therefore is to go with the default 8 and to use
1085 a boot command line option for devices that need to use a different
1086 command queue depth.
1088 There is no safe option other than using good SCSI devices.
1090 config SCSI_NCR53C8XX_MAX_TAGS
1091 int " maximum number of queued commands"
1092 depends on SCSI_ZALON || SCSI_NCR_Q720
1095 This option allows you to specify the maximum number of commands
1096 that can be queued to any device, when tagged command queuing is
1097 possible. The default value is 32. Minimum is 2, maximum is 64.
1098 Modern hard disks are able to support 64 tags and even more, but
1099 do not seem to be faster when more than 32 tags are being used.
1101 So, the normal answer here is to go with the default value 32 unless
1102 you are using very large hard disks with large cache (>= 1 MB) that
1103 are able to take advantage of more than 32 tagged commands.
1105 There is no safe option and the default answer is recommended.
1107 config SCSI_NCR53C8XX_SYNC
1108 int " synchronous transfers frequency in MHz"
1109 depends on SCSI_ZALON || SCSI_NCR_Q720
1112 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1113 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1114 are respectively the maximum data transfer rates in mega-transfers
1115 per second for each class. For example, a FAST-20 Wide 16 device is
1116 able to transfer data at 20 million 16 bit packets per second for a
1117 total rate of 40 MB/s.
1119 You may specify 0 if you want to only use asynchronous data
1120 transfers. This is the safest and slowest option. Otherwise, specify
1121 a value between 5 and 80, depending on the capability of your SCSI
1122 controller. The higher the number, the faster the data transfer.
1123 Note that 80 should normally be ok since the driver decreases the
1124 value automatically according to the controller's capabilities.
1126 Your answer to this question is ignored for controllers with NVRAM,
1127 since the driver will get this information from the user set-up. It
1128 also can be overridden using a boot setup option, as follows
1129 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1130 for FAST-20 synchronous data transfer (20 mega-transfers per
1133 The normal answer therefore is not to go with the default but to
1134 select the maximum value 80 allowing the driver to use the maximum
1135 value supported by each controller. If this causes problems with
1136 your SCSI devices, you should come back and decrease the value.
1138 There is no safe option other than using good cabling, right
1139 terminations and SCSI conformant devices.
1141 config SCSI_NCR53C8XX_PROFILE
1142 bool " enable profiling"
1143 depends on SCSI_ZALON || SCSI_NCR_Q720
1145 This option allows you to enable profiling information gathering.
1146 These statistics are not very accurate due to the low frequency
1147 of the kernel clock (100 Hz on i386) and have performance impact
1148 on systems that use very fast devices.
1150 The normal answer therefore is N.
1152 config SCSI_NCR53C8XX_NO_DISCONNECT
1153 bool " not allow targets to disconnect"
1154 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1156 This option is only provided for safety if you suspect some SCSI
1157 device of yours to not support properly the target-disconnect
1158 feature. In that case, you would say Y here. In general however, to
1159 not allow targets to disconnect is not reasonable if there is more
1160 than 1 device on a SCSI bus. The normal answer therefore is N.
1162 config SCSI_MCA_53C9X
1163 tristate "NCR MCA 53C9x SCSI support"
1164 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1166 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1167 controller based on the NCR 53C94. This driver will allow use of
1168 the controller on the 3550, and very possibly others.
1170 To compile this driver as a module, choose M here: the
1171 module will be called mca_53c9x.
1174 tristate "PAS16 SCSI support"
1175 depends on ISA && SCSI
1177 This is support for a SCSI host adapter. It is explained in section
1178 3.10 of the SCSI-HOWTO, available from
1179 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1180 of the box, you may have to change some settings in
1181 <file:drivers/scsi/pas16.h>.
1183 To compile this driver as a module, choose M here: the
1184 module will be called pas16.
1187 tristate "PCI2000 support"
1188 depends on PCI && SCSI && BROKEN
1190 This is support for the PCI2000I EIDE interface card which acts as a
1191 SCSI host adapter. Please read the SCSI-HOWTO, available from
1192 <http://www.tldp.org/docs.html#howto>.
1194 To compile this driver as a module, choose M here: the
1195 module will be called pci2000.
1197 config SCSI_PCI2220I
1198 tristate "PCI2220i support"
1199 depends on PCI && SCSI && BROKEN
1201 This is support for the PCI2220i EIDE interface card which acts as a
1202 SCSI host adapter. Please read the SCSI-HOWTO, available from
1203 <http://www.tldp.org/docs.html#howto>.
1205 To compile this driver as a module, choose M here: the
1206 module will be called pci2220i.
1209 tristate "PSI240i support"
1210 depends on ISA && SCSI
1212 This is support for the PSI240i EIDE interface card which acts as a
1213 SCSI host adapter. Please read the SCSI-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>.
1216 To compile this driver as a module, choose M here: the
1217 module will be called psi240i.
1219 config SCSI_QLOGIC_FAS
1220 tristate "Qlogic FAS SCSI support"
1221 depends on ISA && SCSI
1223 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1224 FastSCSI! cards as well as any other card based on the FASXX chip
1225 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1227 This driver does NOT support the PCI versions of these cards. The
1228 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1229 SCSI support"), below.
1231 Information about this driver is contained in
1232 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1233 SCSI-HOWTO, available from
1234 <http://www.tldp.org/docs.html#howto>.
1236 To compile this driver as a module, choose M here: the
1237 module will be called qlogicfas.
1239 config SCSI_QLOGIC_ISP
1240 tristate "Qlogic ISP SCSI support"
1241 depends on PCI && SCSI
1243 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1244 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1245 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1247 If you say Y here, make sure to choose "BIOS" at the question "PCI
1250 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1251 should also read the SCSI-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>.
1254 To compile this driver as a module, choose M here: the
1255 module will be called qlogicisp.
1257 config SCSI_QLOGIC_FC
1258 tristate "Qlogic ISP FC SCSI support"
1259 depends on PCI && SCSI
1261 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1263 To compile this driver as a module, choose M here: the
1264 module will be called qlogicfc.
1266 config SCSI_QLOGIC_FC_FIRMWARE
1267 bool "Include loadable firmware in driver"
1268 depends on SCSI_QLOGIC_FC
1270 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1271 expanded LUN addressing and FcTape (FCP-2) support, in the
1272 qlogicfc driver. This is required on some platforms.
1274 config SCSI_QLOGIC_1280
1275 tristate "Qlogic QLA 1280 SCSI support"
1276 depends on PCI && SCSI
1278 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1280 To compile this driver as a module, choose M here: the
1281 module will be called qla1280.
1283 config SCSI_QLOGICPTI
1284 tristate "PTI Qlogic, ISP Driver"
1285 depends on SBUS && SCSI
1287 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1288 controllers are known under Solaris as qpti and in the openprom as
1289 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1290 driven by a different driver.
1292 To compile this driver as a module, choose M here: the
1293 module will be called qlogicpti.
1295 source "drivers/scsi/qla2xxx/Kconfig"
1298 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1299 depends on X86 && ISA && SCSI && BROKEN
1301 These are 8-bit SCSI controllers; the ST-01 is also supported by
1302 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1303 available from <http://www.tldp.org/docs.html#howto>. If it
1304 doesn't work out of the box, you may have to change some settings in
1305 <file:drivers/scsi/seagate.h>.
1307 To compile this driver as a module, choose M here: the
1308 module will be called seagate.
1310 # definitely looks not 64bit safe:
1312 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1313 depends on (EISA || MCA) && SCSI
1314 select SCSI_SPI_ATTRS
1316 This driver for NCR53c710 based SCSI host adapters.
1318 It currently supports Compaq EISA cards and NCR MCA cards
1320 config 53C700_IO_MAPPED
1322 depends on SCSI_SIM710
1325 config SCSI_SYM53C416
1326 tristate "Symbios 53c416 SCSI support"
1327 depends on ISA && SCSI
1329 This is support for the sym53c416 SCSI host adapter, the SCSI
1330 adapter that comes with some HP scanners. This driver requires that
1331 the sym53c416 is configured first using some sort of PnP
1332 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1333 are using isapnp then you need to compile this driver as a module
1334 and then load it using insmod after isapnp has run. The parameters
1335 of the configured card(s) should be passed to the driver. The format
1338 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1340 To compile this driver as a module, choose M here: the
1341 module will be called sym53c416.
1344 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1345 depends on PCI && SCSI && EXPERIMENTAL
1347 This driver supports PCI SCSI host adapters based on the ASIC
1348 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1350 This driver works, but is still in experimental status. So better
1351 have a bootable disk and a backup in case of emergency.
1353 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1355 To compile this driver as a module, choose M here: the
1356 module will be called dc395x.
1359 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1360 depends on PCI && SCSI
1362 This driver supports PCI SCSI host adapters based on the Am53C974A
1363 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1364 PCscsi/PCnet (Am53/79C974) solutions.
1366 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1368 Note that this driver does NOT support Tekram DC390W/U/F, which are
1369 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1371 To compile this driver as a module, choose M here: the
1372 module will be called tmscsim.
1375 tristate "Trantor T128/T128F/T228 SCSI support"
1376 depends on ISA && SCSI
1378 This is support for a SCSI host adapter. It is explained in section
1379 3.11 of the SCSI-HOWTO, available from
1380 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1381 of the box, you may have to change some settings in
1382 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1383 Adaptec, and some former Trantor products are being sold under the
1386 To compile this driver as a module, choose M here: the
1387 module will be called t128.
1390 tristate "UltraStor 14F/34F support"
1391 depends on ISA && SCSI
1393 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1394 The source at <file:drivers/scsi/u14-34f.c> contains some
1395 information about this hardware. If the driver doesn't work out of
1396 the box, you may have to change some settings in
1397 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>. Note that there is also
1399 another driver for the same hardware: "UltraStor SCSI support",
1400 below. You should say Y to both only if you want 24F support as
1403 To compile this driver as a module, choose M here: the
1404 module will be called u14-34f.
1406 config SCSI_U14_34F_TAGGED_QUEUE
1407 bool "enable tagged command queueing"
1408 depends on SCSI_U14_34F
1410 This is a feature of SCSI-2 which improves performance: the host
1411 adapter can send several SCSI commands to a device's queue even if
1412 previous commands haven't finished yet.
1413 This is equivalent to the "u14-34f=tc:y" boot option.
1415 config SCSI_U14_34F_LINKED_COMMANDS
1416 bool "enable elevator sorting"
1417 depends on SCSI_U14_34F
1419 This option enables elevator sorting for all probed SCSI disks and
1420 CD-ROMs. It definitely reduces the average seek distance when doing
1421 random seeks, but this does not necessarily result in a noticeable
1422 performance improvement: your mileage may vary...
1423 This is equivalent to the "u14-34f=lc:y" boot option.
1425 config SCSI_U14_34F_MAX_TAGS
1426 int "maximum number of queued commands"
1427 depends on SCSI_U14_34F
1430 This specifies how many SCSI commands can be maximally queued for
1431 each probed SCSI device. You should reduce the default value of 8
1432 only if you have disks with buggy or limited tagged command support.
1433 Minimum is 2 and maximum is 14. This value is also the window size
1434 used by the elevator sorting option above. The effective value used
1435 by the driver for each probed SCSI device is reported at boot time.
1436 This is equivalent to the "u14-34f=mq:8" boot option.
1438 config SCSI_ULTRASTOR
1439 tristate "UltraStor SCSI support"
1440 depends on X86 && ISA && SCSI
1442 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1443 adapter family. This driver is explained in section 3.12 of the
1444 SCSI-HOWTO, available from
1445 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1446 of the box, you may have to change some settings in
1447 <file:drivers/scsi/ultrastor.h>.
1449 Note that there is also another driver for the same hardware:
1450 "UltraStor 14F/34F support", above.
1452 To compile this driver as a module, choose M here: the
1453 module will be called ultrastor.
1456 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1457 depends on PCI && SCSI && !64BIT
1459 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1460 SCSI host adapter. Please read the SCSI-HOWTO, available from
1461 <http://www.tldp.org/docs.html#howto>.
1463 To compile this driver as a module, choose M here: the
1464 module will be called nsp32.
1467 tristate "SCSI debugging host simulator"
1470 This is a host adapter simulator that can simulate multiple hosts
1471 each with multiple dummy SCSI devices (disks). It defaults to one
1472 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1473 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1474 dummy disks are simulated, they share the same kernel RAM for
1475 their storage. See http://www.torque.net/sg/sdebug.html for more
1476 information. This driver is primarily of use to those testing the
1477 SCSI and block subsystems. If unsure, say N.
1480 tristate "MESH (Power Mac internal SCSI) support"
1481 depends on PPC32 && PPC_PMAC && SCSI
1483 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1484 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1485 other Power Macintoshes do). Say Y to include support for this SCSI
1488 To compile this driver as a module, choose M here: the
1489 module will be called mesh.
1491 config SCSI_MESH_SYNC_RATE
1492 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1493 depends on SCSI_MESH
1496 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1497 drives a bus which is entirely internal to the machine (such as the
1498 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1499 operation at up to 10 MB/s. On machines where the SCSI bus
1500 controlled by the MESH can have external devices connected, it is
1501 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1502 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1503 to disable synchronous operation.
1505 config SCSI_MESH_RESET_DELAY_MS
1506 int "initial bus reset delay (ms) (0 = no reset)"
1507 depends on SCSI_MESH
1510 config SCSI_MAC53C94
1511 tristate "53C94 (Power Mac external SCSI) support"
1512 depends on PPC_PMAC && SCSI
1514 On Power Macintoshes (and clones) with two SCSI buses, the external
1515 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1516 machines which only have one SCSI bus, such as the 7200, also use
1517 the 53C94. Say Y to include support for the 53C94.
1519 To compile this driver as a module, choose M here: the
1520 module will be called mac53c94.
1522 source "drivers/scsi/arm/Kconfig"
1525 bool "MIPS JAZZ FAS216 SCSI support"
1526 depends on MACH_JAZZ && SCSI
1528 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1529 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1533 tristate "A3000 WD33C93A support"
1534 depends on AMIGA && SCSI
1536 If you have an Amiga 3000 and have SCSI devices connected to the
1537 built-in SCSI controller, say Y. Otherwise, say N.
1539 To compile this driver as a module, choose M here: the
1540 module will be called wd33c93.
1543 tristate "A2091/A590 WD33C93A support"
1544 depends on ZORRO && SCSI
1546 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1549 To compile this driver as a module, choose M here: the
1550 module will be called wd33c93.
1553 tristate "GVP Series II WD33C93A support"
1554 depends on ZORRO && SCSI
1556 If you have a Great Valley Products Series II SCSI controller,
1557 answer Y. Also say Y if you have a later model of GVP SCSI
1558 controller (such as the GVP A4008 or a Combo board). Otherwise,
1559 answer N. This driver does NOT work for the T-Rex series of
1560 accelerators from TekMagic and GVP-M.
1562 To compile this driver as a module, choose M here: the
1563 module will be called gvp11.
1565 config CYBERSTORM_SCSI
1566 tristate "CyberStorm SCSI support"
1567 depends on ZORRO && SCSI
1569 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1570 accelerator board and the optional Cyberstorm SCSI controller,
1571 answer Y. Otherwise, say N.
1573 config CYBERSTORMII_SCSI
1574 tristate "CyberStorm Mk II SCSI support"
1575 depends on ZORRO && SCSI
1577 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1578 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1582 tristate "Blizzard 2060 SCSI support"
1583 depends on ZORRO && SCSI
1585 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1586 and want to use the onboard SCSI controller, say Y. Otherwise,
1590 tristate "Blizzard 1230IV/1260 SCSI support"
1591 depends on ZORRO && SCSI
1593 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1594 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1597 config FASTLANE_SCSI
1598 tristate "Fastlane SCSI support"
1599 depends on ZORRO && SCSI
1601 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1602 one in the near future, say Y to this question. Otherwise, say N.
1604 config SCSI_AMIGA7XX
1605 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1606 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1608 Support for various NCR53c710-based SCSI controllers on the Amiga.
1610 - the builtin SCSI controller on the Amiga 4000T,
1611 - the Amiga 4091 Zorro III SCSI-2 controller,
1612 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1614 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1615 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1616 accelerator card for the Amiga 1200,
1617 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1618 Note that all of the above SCSI controllers, except for the builtin
1619 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1620 bus, so you also have to enable Zorro bus support if you want to use
1624 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1625 depends on ZORRO && SCSI && EXPERIMENTAL
1627 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1628 Y to this question. If you're in doubt about whether you have one,
1630 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1633 tristate "Atari native SCSI support"
1634 depends on ATARI && SCSI && BROKEN
1636 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1637 Falcon, ...) say Y to get it supported. Of course also, if you have
1638 a compatible SCSI controller (e.g. for Medusa).
1640 To compile this driver as a module, choose M here: the
1641 module will be called atari_scsi.
1643 This driver supports both styles of NCR integration into the
1644 system: the TT style (separate DMA), and the Falcon style (via
1645 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1646 in the Hades (without DMA).
1648 config ATARI_SCSI_TOSHIBA_DELAY
1649 bool "Long delays for Toshiba CD-ROMs"
1650 depends on ATARI_SCSI
1652 This option increases the delay after a SCSI arbitration to
1653 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1654 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1655 would impact performance a bit, so say N.
1657 config ATARI_SCSI_RESET_BOOT
1658 bool "Reset SCSI-devices at boottime"
1659 depends on ATARI_SCSI
1661 Reset the devices on your Atari whenever it boots. This makes the
1662 boot process fractionally longer but may assist recovery from errors
1663 that leave the devices with SCSI operations partway completed.
1666 bool "Hades SCSI DMA emulator"
1667 depends on ATARI_SCSI && HADES
1669 This option enables code which emulates the TT SCSI DMA chip on the
1670 Hades. This increases the SCSI transfer rates at least ten times
1671 compared to PIO transfers.
1674 bool "Macintosh NCR5380 SCSI"
1675 depends on MAC && SCSI
1677 This is the NCR 5380 SCSI controller included on most of the 68030
1678 based Macintoshes. If you have one of these say Y and read the
1679 SCSI-HOWTO, available from
1680 <http://www.tldp.org/docs.html#howto>.
1683 tristate "Macintosh NCR53c9[46] SCSI"
1684 depends on MAC && SCSI
1686 This is the NCR 53c9x SCSI controller found on most of the 68040
1687 based Macintoshes. If you have one of these say Y and read the
1688 SCSI-HOWTO, available from
1689 <http://www.tldp.org/docs.html#howto>.
1691 To compile this driver as a module, choose M here: the
1692 module will be called mac_esp.
1695 bool "WD33C93 SCSI driver for MVME147"
1696 depends on MVME147 && SCSI
1698 Support for the on-board SCSI controller on the Motorola MVME147
1699 single-board computer.
1702 bool "NCR53C710 SCSI driver for MVME16x"
1703 depends on MVME16x && SCSI && BROKEN
1705 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1706 SCSI controller chip. Almost everyone using one of these boards
1707 will want to say Y to this question.
1709 config BVME6000_SCSI
1710 bool "NCR53C710 SCSI driver for BVME6000"
1711 depends on BVME6000 && SCSI && BROKEN
1713 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1714 SCSI controller chip. Almost everyone using one of these boards
1715 will want to say Y to this question.
1717 config SCSI_NCR53C7xx_FAST
1718 bool "allow FAST-SCSI [10MHz]"
1719 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1721 This will enable 10MHz FAST-SCSI transfers with your host
1722 adapter. Some systems have problems with that speed, so it's safest
1726 tristate "Sun3 NCR5380 SCSI"
1727 depends on SUN3 && SCSI
1729 This option will enable support for the OBIO (onboard io) NCR5380
1730 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1731 "Sun3" type VME scsi controllers also based on the NCR5380.
1732 General Linux information on the Sun 3 series (now discontinued)
1733 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1736 bool "Sun3x ESP SCSI"
1737 depends on SUN3X && SCSI
1739 The ESP was an on-board SCSI controller used on Sun 3/80
1740 machines. Say Y here to compile in support for it.
1743 tristate "Sparc ESP Scsi Driver"
1744 depends on SBUS && SCSI
1746 This is the driver for the Sun ESP SCSI host adapter. The ESP
1747 chipset is present in most SPARC SBUS-based computers.
1749 To compile this driver as a module, choose M here: the
1750 module will be called esp.
1752 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1755 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1756 depends on ARCH_S390 && SCSI
1757 select SCSI_FC_ATTRS
1759 If you want to access SCSI devices attached to your IBM eServer
1760 zSeries by means of Fibre Channel interfaces say Y.
1761 For details please refer to the documentation provided by IBM at
1762 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1764 This driver is also available as a module. This module will be
1765 called zfcp. If you want to compile it as a module, say M here
1766 and read Documentation/modules.txt.
1770 source "drivers/scsi/pcmcia/Kconfig"