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 Hardware 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>.
242 config SCSI_7000FASST
243 tristate "7000FASST SCSI support"
244 depends on ISA && SCSI
246 This driver supports the Western Digital 7000 SCSI host adapter
247 family. Some information is in the source:
248 <file:drivers/scsi/wd7000.c>.
250 To compile this driver as a module, choose M here: the
251 module will be called wd7000.
254 tristate "ACARD SCSI support"
255 depends on PCI && SCSI
257 This driver supports the ACARD 870U/W SCSI host adapter.
259 To compile this driver as a module, choose M here: the
260 module will be called atp870u.
263 tristate "Adaptec AHA152X/2825 support"
264 depends on ISA && SCSI && !64BIT
266 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
267 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
268 must be manually specified in this case.
270 It is explained in section 3.3 of the SCSI-HOWTO, available from
271 <http://www.tldp.org/docs.html#howto>. You might also want to
272 read the file <file:Documentation/scsi/aha152x.txt>.
274 To compile this driver as a module, choose M here: the
275 module will be called aha152x.
278 tristate "Adaptec AHA1542 support"
279 depends on ISA && SCSI
281 This is support for a SCSI host adapter. It is explained in section
282 3.4 of the SCSI-HOWTO, available from
283 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
284 purchased by Adaptec, and some former Trantor products are being
285 sold under the Adaptec name. If it doesn't work out of the box, you
286 may have to change some settings in <file:drivers/scsi/aha1542.h>.
288 To compile this driver as a module, choose M here: the
289 module will be called aha1542.
292 tristate "Adaptec AHA1740 support"
293 depends on EISA && SCSI
295 This is support for a SCSI host adapter. It is explained in section
296 3.5 of the SCSI-HOWTO, available from
297 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
298 of the box, you may have to change some settings in
299 <file:drivers/scsi/aha1740.h>.
301 To compile this driver as a module, choose M here: the
302 module will be called aha1740.
305 tristate "Adaptec AACRAID support (EXPERIMENTAL)"
306 depends on EXPERIMENTAL && SCSI && PCI
308 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
310 config SCSI_AIC7XXX_OLD
311 tristate "Adaptec AIC7xxx support (old driver)"
314 WARNING This driver is an older aic7xxx driver and is no longer
315 under active development. Adaptec, Inc. is writing a new driver to
316 take the place of this one, and it is recommended that whenever
317 possible, people should use the new Adaptec written driver instead
318 of this one. This driver will eventually be phased out entirely.
320 This is support for the various aic7xxx based Adaptec SCSI
321 controllers. These include the 274x EISA cards; 284x VLB cards;
322 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
323 motherboard based SCSI controllers from Adaptec. It does not support
324 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
325 support them. It does not support the 2920 cards from Adaptec that
326 use the Future Domain SCSI controller chip. For those cards, you
327 need the "Future Domain 16xx SCSI support" driver.
329 In general, if the controller is based on an Adaptec SCSI controller
330 chip from the aic777x series or the aic78xx series, this driver
331 should work. The only exception is the 7810 which is specifically
332 not supported (that's the RAID controller chip on the AAA-13x
335 Note that the AHA2920 SCSI host adapter is *not* supported by this
336 driver; choose "Future Domain 16xx SCSI support" instead if you have
339 Information on the configuration options for this controller can be
340 found by checking the help file for each of the available
341 configuration options. You should read
342 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
343 contacting the maintainer with any questions. The SCSI-HOWTO,
344 available from <http://www.tldp.org/docs.html#howto>, can also
347 To compile this driver as a module, choose M here: the
348 module will be called aic7xxx_old.
350 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
352 # All the I2O code and drivers do not seem to be 64bit safe.
354 tristate "Adaptec I2O RAID support "
355 depends on !64BIT && SCSI && PCI
357 This driver supports all of Adaptec's I2O based RAID controllers as
358 well as the DPT SmartRaid V cards. This is an Adaptec maintained
359 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
361 To compile this driver as a module, choose M here: the
362 module will be called dpt_i2o.
365 tristate "AdvanSys SCSI support"
366 depends on (ISA || EISA || PCI) && SCSI
368 This is a driver for all SCSI host adapters manufactured by
369 AdvanSys. It is documented in the kernel source in
370 <file:drivers/scsi/advansys.c>.
372 To compile this driver as a module, choose M here: the
373 module will be called advansys.
376 tristate "Always IN2000 SCSI support"
377 depends on ISA && SCSI
379 This is support for an ISA bus SCSI host adapter. You'll find more
380 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
381 out of the box, you may have to change the jumpers for IRQ or
384 To compile this driver as a module, choose M here: the
385 module will be called in2000.
388 tristate "AMI MegaRAID support"
389 depends on PCI && SCSI
391 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
392 and 467 SCSI host adapters.
394 To compile this driver as a module, choose M here: the
395 module will be called megaraid.
398 bool "Serial ATA (SATA) support"
399 depends on SCSI && EXPERIMENTAL
401 This driver family supports Serial ATA host controllers
407 tristate "ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL)"
408 depends on SCSI_SATA && PCI && EXPERIMENTAL
410 This option enables support for Broadcom/Serverworks/Apple K2
416 tristate "Intel PIIX/ICH SATA support"
417 depends on SCSI_SATA && PCI
419 This option enables support for ICH5 Serial ATA.
420 If PATA support was enabled previously, this enables
421 support for select Intel PIIX/ICH PATA host controllers.
425 config SCSI_SATA_PROMISE
426 tristate "Promise SATA TX2/TX4 support"
427 depends on SCSI_SATA && PCI
429 This option enables support for Promise Serial ATA TX2/TX4.
434 tristate "Promise SATA SX4 support"
435 depends on SCSI_SATA && PCI && EXPERIMENTAL
437 This option enables support for Promise Serial ATA SX4.
442 tristate "Silicon Image SATA support"
443 depends on SCSI_SATA && PCI && EXPERIMENTAL
445 This option enables support for Silicon Image Serial ATA.
450 tristate "SiS 964/180 SATA support"
451 depends on SCSI_SATA && PCI
453 This option enables support for SiS Serial ATA 964/180.
458 tristate "VIA SATA support"
459 depends on SCSI_SATA && PCI && EXPERIMENTAL
461 This option enables support for VIA Serial ATA.
465 config SCSI_SATA_VITESSE
466 tristate "VITESSE VSC-7174 SATA support"
467 depends on SCSI_SATA && PCI && EXPERIMENTAL
469 This option enables support for Vitesse VSC7174 Serial ATA.
474 tristate "BusLogic SCSI support"
475 depends on (PCI || ISA || MCA) && SCSI
477 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
478 Adapters. Consult the SCSI-HOWTO, available from
479 <http://www.tldp.org/docs.html#howto>, and the files
480 <file:Documentation/scsi/BusLogic.txt> and
481 <file:Documentation/scsi/FlashPoint.txt> for more information. If this
482 driver does not work correctly without modification, please contact
483 the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
485 To compile this driver as a module, choose M here: the
486 module will be called BusLogic.
488 config SCSI_OMIT_FLASHPOINT
489 bool "Omit FlashPoint support"
490 depends on SCSI_BUSLOGIC
492 This option allows you to omit the FlashPoint support from the
493 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
494 substantial, so users of MultiMaster Host Adapters may wish to omit
498 # This is marked broken because it uses over 4kB of stack in
500 # 2076 CpqTsProcessIMQEntry
504 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
505 depends on PCI && SCSI && BROKEN
507 Say Y here to compile in support for the Compaq StorageWorks Fibre
508 Channel 64-bit/66Mhz Host Bus Adapter.
511 tristate "DMX3191D SCSI support"
512 depends on PCI && SCSI
514 This is support for Domex DMX3191D SCSI Host Adapters.
516 To compile this driver as a module, choose M here: the
517 module will be called dmx3191d.
520 tristate "DTC3180/3280 SCSI support"
521 depends on ISA && SCSI
523 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
524 the SCSI-HOWTO, available from
525 <http://www.tldp.org/docs.html#howto>, and the file
526 <file:Documentation/scsi/dtc3x80.txt>.
528 To compile this driver as a module, choose M here: the
529 module will be called dtc.
532 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
533 depends on (ISA || EISA || PCI) && SCSI
535 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
536 ISA and all EISA I/O addresses are probed looking for the "EATA"
537 signature. The addresses of all the PCI SCSI controllers reported
538 by the PCI subsystem are probed as well.
540 You want to read the start of <file:drivers/scsi/eata.c> and the
541 SCSI-HOWTO, available from
542 <http://www.tldp.org/docs.html#howto>.
544 To compile this driver as a module, choose M here: the
545 module will be called eata.
547 config SCSI_EATA_TAGGED_QUEUE
548 bool "enable tagged command queueing"
551 This is a feature of SCSI-2 which improves performance: the host
552 adapter can send several SCSI commands to a device's queue even if
553 previous commands haven't finished yet.
554 This is equivalent to the "eata=tc:y" boot option.
556 config SCSI_EATA_LINKED_COMMANDS
557 bool "enable elevator sorting"
560 This option enables elevator sorting for all probed SCSI disks and
561 CD-ROMs. It definitely reduces the average seek distance when doing
562 random seeks, but this does not necessarily result in a noticeable
563 performance improvement: your mileage may vary...
564 This is equivalent to the "eata=lc:y" boot option.
566 config SCSI_EATA_MAX_TAGS
567 int "maximum number of queued commands"
571 This specifies how many SCSI commands can be maximally queued for
572 each probed SCSI device. You should reduce the default value of 16
573 only if you have disks with buggy or limited tagged command support.
574 Minimum is 2 and maximum is 62. This value is also the window size
575 used by the elevator sorting option above. The effective value used
576 by the driver for each probed SCSI device is reported at boot time.
577 This is equivalent to the "eata=mq:8" boot option.
580 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
583 This driver supports all EATA-PIO protocol compliant SCSI Host
584 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
585 host adapters could also use this driver but are discouraged from
586 doing so, since this driver only supports hard disks and lacks
587 numerous features. You might want to have a look at the SCSI-HOWTO,
588 available from <http://www.tldp.org/docs.html#howto>.
590 To compile this driver as a module, choose M here: the
591 module will be called eata_pio.
593 config SCSI_FUTURE_DOMAIN
594 tristate "Future Domain 16xx SCSI/AHA-2920A support"
595 depends on (ISA || PCI) && SCSI
597 This is support for Future Domain's 16-bit SCSI host adapters
598 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
599 other adapters based on the Future Domain chipsets (Quantum
600 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
601 It is explained in section 3.7 of the SCSI-HOWTO, available from
602 <http://www.tldp.org/docs.html#howto>.
604 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
605 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
606 controller support"). This Future Domain driver works with the older
607 Adaptec AHA-2920A boards with a Future Domain chip on them.
609 To compile this driver as a module, choose M here: the
610 module will be called fdomain.
613 tristate "Future Domain MCS-600/700 SCSI support"
614 depends on MCA && SCSI
616 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
617 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
618 is identical to the MCS 700 and hence also supported by this driver.
619 This driver also supports the Reply SB16/SCSI card (the SCSI part).
620 It supports multiple adapters in the same system.
622 To compile this driver as a module, choose M here: the
623 module will be called fd_mcs.
626 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
627 depends on (ISA || EISA || PCI) && SCSI
629 Formerly called GDT SCSI Disk Array Controller Support.
631 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
632 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
633 in the kernel source in <file:drivers/scsi/gdth.c> and
634 <file:drivers/scsi/gdth.h.>
636 To compile this driver as a module, choose M here: the
637 module will be called gdth.
639 config SCSI_GENERIC_NCR5380
640 tristate "Generic NCR5380/53c400 SCSI PIO support"
641 depends on ISA && SCSI
643 This is a driver for the old NCR 53c80 series of SCSI controllers
644 on boards using PIO. Most boards such as the Trantor T130 fit this
645 category, along with a large number of ISA 8bit controllers shipped
646 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
647 you should select the specific driver for that card rather than
648 generic 5380 support.
650 It is explained in section 3.8 of the SCSI-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
652 of the box, you may have to change some settings in
653 <file:drivers/scsi/g_NCR5380.h>.
655 To compile this driver as a module, choose M here: the
656 module will be called g_NCR5380.
658 config SCSI_GENERIC_NCR5380_MMIO
659 tristate "Generic NCR5380/53c400 SCSI MMIO support"
660 depends on ISA && SCSI
662 This is a driver for the old NCR 53c80 series of SCSI controllers
663 on boards using memory mapped I/O.
664 It is explained in section 3.8 of the SCSI-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
666 of the box, you may have to change some settings in
667 <file:drivers/scsi/g_NCR5380.h>.
669 To compile this driver as a module, choose M here: the
670 module will be called g_NCR5380_mmio.
672 config SCSI_GENERIC_NCR53C400
673 bool "Enable NCR53c400 extensions"
674 depends on SCSI_GENERIC_NCR5380
676 This enables certain optimizations for the NCR53c400 SCSI cards.
677 You might as well try it out. Note that this driver will only probe
678 for the Trantor T130B in its default configuration; you might have
679 to pass a command line option to the kernel at boot time if it does
680 not detect your card. See the file
681 <file:Documentation/scsi/g_NCR5380.txt> for details.
684 tristate "IBMMCA SCSI support"
685 depends on MCA && SCSI
687 This is support for the IBM SCSI adapter found in many of the PS/2
688 series computers. These machines have an MCA bus, so you need to
689 answer Y to "MCA support" as well and read
690 <file:Documentation/mca.txt>.
692 If the adapter isn't found during boot (a common problem for models
693 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
694 option, where <pun> is the id of the SCSI subsystem (usually 7, but
695 if that doesn't work check your reference diskette). Owners of
696 model 95 with a LED-matrix-display can in addition activate some
697 activity info like under OS/2, but more informative, by setting
698 'ibmmcascsi=display' as an additional kernel parameter. Try "man
699 bootparam" or see the documentation of your boot loader about how to
700 pass options to the kernel.
702 To compile this driver as a module, choose M here: the
703 module will be called ibmmca.
705 config IBMMCA_SCSI_ORDER_STANDARD
706 bool "Standard SCSI-order"
707 depends on SCSI_IBMMCA
709 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
710 are assigned to the drive letters, starting with the lowest SCSI-id
711 (physical number -- pun) to be drive C:, as seen from DOS and
712 similar operating systems. When looking into papers describing the
713 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
714 The SCSI-standard follows a hardware-hierarchy which says that id 7
715 has the highest priority and id 0 the lowest. Therefore, the host
716 adapters are still today everywhere placed as SCSI-id 7 by default.
717 In the SCSI-standard, the drive letters express the priority of the
718 disk. C: should be the hard disk, or a partition on it, with the
719 highest priority. This must therefore be the disk with the highest
720 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
721 original definition of the SCSI-standard as also industrial- and
722 process-control-machines, like VME-CPUs running under realtime-OSes
723 (e.g. LynxOS, OS9) do.
725 If you like to run Linux on your MCA-machine with the same
726 assignment of hard disks as seen from e.g. DOS or OS/2 on your
727 machine, which is in addition conformant to the SCSI-standard, you
728 must say Y here. This is also necessary for MCA-Linux users who want
729 to keep downward compatibility to older releases of the
730 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
733 If you like to have the lowest SCSI-id assigned as drive C:, as
734 modern SCSI-BIOSes do, which does not conform to the standard, but
735 is widespread and common in the PC-world of today, you must say N
736 here. If unsure, say Y.
738 config IBMMCA_SCSI_DEV_RESET
739 bool "Reset SCSI-devices at boottime"
740 depends on SCSI_IBMMCA
742 By default, SCSI-devices are reset when the machine is powered on.
743 However, some devices exist, like special-control-devices,
744 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
745 not reset when switched on. If you say Y here, each device connected
746 to your SCSI-bus will be issued a reset-command after it has been
747 probed, while the kernel is booting. This may cause problems with
748 more modern devices, like hard disks, which do not appreciate these
749 reset commands, and can cause your system to hang. So say Y only if
750 you know that one of your older devices needs it; N is the safe
754 tristate "IBM ServeRAID support"
755 depends on PCI && SCSI
757 This is support for the IBM ServeRAID hardware RAID controllers.
758 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
759 for more information. If this driver does not work correctly
760 without modification please contact the author by email at
761 ipslinux@adaptec.com.
763 To compile this driver as a module, choose M here: the
764 module will be called ips.
767 tristate "Initio 9100U(W) support"
768 depends on PCI && SCSI && BROKEN
770 This is support for the Initio 91XXU(W) SCSI host adapter. Please
771 read the SCSI-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>.
774 To compile this driver as a module, choose M here: the
775 module will be called initio.
778 tristate "Initio INI-A100U2W support"
779 depends on PCI && SCSI
781 This is support for the Initio INI-A100U2W SCSI host adapter.
782 Please read the SCSI-HOWTO, available from
783 <http://www.tldp.org/docs.html#howto>.
785 To compile this driver as a module, choose M here: the
786 module will be called a100u2w.
789 tristate "IOMEGA parallel port (ppa - older drives)"
790 depends on SCSI && PARPORT
792 This driver supports older versions of IOMEGA's parallel port ZIP
793 drive (a 100 MB removable media device).
795 Note that you can say N here if you have the SCSI version of the ZIP
796 drive: it will be supported automatically if you said Y to the
797 generic "SCSI disk support", above.
799 If you have the ZIP Plus drive or a more recent parallel port ZIP
800 drive (if the supplied cable with the drive is labeled "AutoDetect")
801 then you should say N here and Y to "IOMEGA parallel port (imm -
802 newer drives)", below.
804 For more information about this driver and how to use it you should
805 read the file <file:Documentation/scsi/ppa.txt>. You should also read
806 the SCSI-HOWTO, which is available from
807 <http://www.tldp.org/docs.html#howto>. If you use this driver,
808 you will still be able to use the parallel port for other tasks,
809 such as a printer; it is safe to compile both drivers into the
812 To compile this driver as a module, choose M here: the
813 module will be called ppa.
816 tristate "IOMEGA parallel port (imm - newer drives)"
817 depends on SCSI && PARPORT
819 This driver supports newer versions of IOMEGA's parallel port ZIP
820 drive (a 100 MB removable media device).
822 Note that you can say N here if you have the SCSI version of the ZIP
823 drive: it will be supported automatically if you said Y to the
824 generic "SCSI disk support", above.
826 If you have the ZIP Plus drive or a more recent parallel port ZIP
827 drive (if the supplied cable with the drive is labeled "AutoDetect")
828 then you should say Y here; if you have an older ZIP drive, say N
829 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
831 For more information about this driver and how to use it you should
832 read the file <file:Documentation/scsi/ppa.txt>. You should also read
833 the SCSI-HOWTO, which is available from
834 <http://www.tldp.org/docs.html#howto>. If you use this driver,
835 you will still be able to use the parallel port for other tasks,
836 such as a printer; it is safe to compile both drivers into the
839 To compile this driver as a module, choose M here: the
840 module will be called imm.
842 config SCSI_IZIP_EPP16
843 bool "ppa/imm option - Use slow (but safe) EPP-16"
844 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
846 EPP (Enhanced Parallel Port) is a standard for parallel ports which
847 allows them to act as expansion buses that can handle up to 64
850 Some parallel port chipsets are slower than their motherboard, and
851 so we have to control the state of the chipset's FIFO queue every
852 now and then to avoid data loss. This will be done if you say Y
855 Generally, saying Y is the safe option and slows things down a bit.
857 config SCSI_IZIP_SLOW_CTR
858 bool "ppa/imm option - Assume slow parport control register"
859 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
861 Some parallel ports are known to have excessive delays between
862 changing the parallel port control register and good data being
863 available on the parallel port data/status register. This option
864 forces a small delay (1.0 usec to be exact) after changing the
865 control register to let things settle out. Enabling this option may
866 result in a big drop in performance but some very old parallel ports
867 (found in 386 vintage machines) will not work properly.
869 Generally, saying N is fine.
871 config SCSI_NCR53C406A
872 tristate "NCR53c406a SCSI support"
873 depends on ISA && SCSI
875 This is support for the NCR53c406a SCSI host adapter. For user
876 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
877 in the kernel source. Also read the SCSI-HOWTO, available from
878 <http://www.tldp.org/docs.html#howto>.
880 To compile this driver as a module, choose M here: the
881 module will be called NCR53c406.
884 tristate "NCR Dual 700 MCA SCSI support"
885 depends on MCA && SCSI
886 select SCSI_SPI_ATTRS
888 This is a driver for the MicroChannel Dual 700 card produced by
889 NCR and commonly used in 345x/35xx/4100 class machines. It always
890 tries to negotiate sync and uses tag command queueing.
892 Unless you have an NCR manufactured machine, the chances are that
893 you do not have this SCSI card, so say N.
895 config 53C700_IO_MAPPED
897 depends on SCSI_NCR_D700
901 tristate "HP Lasi SCSI support for 53c700/710"
902 depends on GSC && SCSI
903 select SCSI_SPI_ATTRS
905 This is a driver for the SCSI controller in the Lasi chip found in
906 many PA-RISC workstations & servers. If you do not know whether you
907 have a Lasi chip, it is safe to say "Y" here.
909 config 53C700_MEM_MAPPED
911 depends on SCSI_LASI700
914 config 53C700_LE_ON_BE
916 depends on SCSI_LASI700
919 config SCSI_SYM53C8XX_2
920 tristate "SYM53C8XX Version 2 SCSI support"
921 depends on PCI && SCSI
922 select SCSI_SPI_ATTRS
924 This driver supports the whole NCR53C8XX/SYM53C8XX family of
925 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
926 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
927 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
928 controllers; you need to use the Fusion MPT driver for that.
930 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
933 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
934 int "DMA addressing mode"
935 depends on SCSI_SYM53C8XX_2
938 This option only applies to PCI-SCSI chips that are PCI DAC
939 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
941 When set to 0, the driver will program the chip to only perform
942 32-bit DMA. When set to 1, the chip will be able to perform DMA
943 to addresses up to 1TB. When set to 2, the driver supports the
944 full 64-bit DMA address range, but can only address 16 segments
945 of 4 GB each. This limits the total addressable range to 64 GB.
947 Most machines with less than 4GB of memory should use a setting
948 of 0 for best performance. If your machine has 4GB of memory
949 or more, you should set this option to 1 (the default).
951 The still experimental value 2 (64 bit DMA addressing with 16
952 x 4GB segments limitation) can be used on systems that require
953 PCI address bits past bit 39 to be set for the addressing of
954 memory using PCI DAC cycles.
956 config SCSI_SYM53C8XX_DEFAULT_TAGS
957 int "default tagged command queue depth"
958 depends on SCSI_SYM53C8XX_2
961 This is the default value of the command queue depth the
962 driver will announce to the generic SCSI layer for devices
963 that support tagged command queueing. This value can be changed
964 from the boot command line. This is a soft limit that cannot
965 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
967 config SCSI_SYM53C8XX_MAX_TAGS
968 int "maximum number of queued commands"
969 depends on SCSI_SYM53C8XX_2
972 This option allows you to specify the maximum number of commands
973 that can be queued to any device, when tagged command queuing is
974 possible. The driver supports up to 256 queued commands per device.
975 This value is used as a compiled-in hard limit.
977 config SCSI_SYM53C8XX_IOMAPPED
979 depends on SCSI_SYM53C8XX_2
981 If you say Y here, the driver will use port IO to access
982 the card. This is significantly slower then using memory
983 mapped IO. Most people should answer N.
986 tristate "IBM Power Linux RAID adapter support"
987 depends on PCI && SCSI
990 This driver supports the IBM Power Linux family RAID adapters.
991 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
992 as IBM iSeries 5702, 5703, 5709, and 570A.
994 config SCSI_IPR_TRACE
995 bool "enable driver internal trace"
998 If you say Y here, the driver will trace all commands issued
999 to the adapter. Performance impact is minimal. Trace can be
1000 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1002 config SCSI_IPR_DUMP
1003 bool "enable adapter dump support"
1006 If you say Y here, the driver will support adapter crash dump.
1007 If you enable this support, the iprdump daemon can be used
1008 to capture adapter failure analysis information.
1011 tristate "Zalon SCSI support"
1012 depends on GSC && SCSI
1014 The Zalon is a GSC/HSC bus interface chip that sits between the
1015 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1016 C110, J200, J210 and some D, K & R-class machines. It's also
1017 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1018 Say Y here if you have one of these machines or cards.
1020 config SCSI_NCR_Q720
1021 tristate "NCR Quad 720 MCA SCSI support"
1022 depends on MCA && SCSI
1024 This is a driver for the MicroChannel Quad 720 card produced by
1025 NCR and commonly used in 345x/35xx/4100 class machines. It always
1026 tries to negotiate sync and uses tag command queueing.
1028 Unless you have an NCR manufactured machine, the chances are that
1029 you do not have this SCSI card, so say N.
1031 config SCSI_NCR53C8XX_DEFAULT_TAGS
1032 int " default tagged command queue depth"
1033 depends on SCSI_ZALON || SCSI_NCR_Q720
1036 "Tagged command queuing" is a feature of SCSI-2 which improves
1037 performance: the host adapter can send several SCSI commands to a
1038 device's queue even if previous commands haven't finished yet.
1039 Because the device is intelligent, it can optimize its operations
1040 (like head positioning) based on its own request queue. Some SCSI
1041 devices don't implement this properly; if you want to disable this
1042 feature, enter 0 or 1 here (it doesn't matter which).
1044 The default value is 8 and should be supported by most hard disks.
1045 This value can be overridden from the boot command line using the
1046 'tags' option as follows (example):
1047 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1048 4, set queue depth to 16 for target 2 and target 3 on controller 0
1049 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1051 The normal answer therefore is to go with the default 8 and to use
1052 a boot command line option for devices that need to use a different
1053 command queue depth.
1055 There is no safe option other than using good SCSI devices.
1057 config SCSI_NCR53C8XX_MAX_TAGS
1058 int " maximum number of queued commands"
1059 depends on SCSI_ZALON || SCSI_NCR_Q720
1062 This option allows you to specify the maximum number of commands
1063 that can be queued to any device, when tagged command queuing is
1064 possible. The default value is 32. Minimum is 2, maximum is 64.
1065 Modern hard disks are able to support 64 tags and even more, but
1066 do not seem to be faster when more than 32 tags are being used.
1068 So, the normal answer here is to go with the default value 32 unless
1069 you are using very large hard disks with large cache (>= 1 MB) that
1070 are able to take advantage of more than 32 tagged commands.
1072 There is no safe option and the default answer is recommended.
1074 config SCSI_NCR53C8XX_SYNC
1075 int " synchronous transfers frequency in MHz"
1076 depends on SCSI_ZALON || SCSI_NCR_Q720
1079 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1080 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1081 are respectively the maximum data transfer rates in mega-transfers
1082 per second for each class. For example, a FAST-20 Wide 16 device is
1083 able to transfer data at 20 million 16 bit packets per second for a
1084 total rate of 40 MB/s.
1086 You may specify 0 if you want to only use asynchronous data
1087 transfers. This is the safest and slowest option. Otherwise, specify
1088 a value between 5 and 80, depending on the capability of your SCSI
1089 controller. The higher the number, the faster the data transfer.
1090 Note that 80 should normally be ok since the driver decreases the
1091 value automatically according to the controller's capabilities.
1093 Your answer to this question is ignored for controllers with NVRAM,
1094 since the driver will get this information from the user set-up. It
1095 also can be overridden using a boot setup option, as follows
1096 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1097 for FAST-20 synchronous data transfer (20 mega-transfers per
1100 The normal answer therefore is not to go with the default but to
1101 select the maximum value 80 allowing the driver to use the maximum
1102 value supported by each controller. If this causes problems with
1103 your SCSI devices, you should come back and decrease the value.
1105 There is no safe option other than using good cabling, right
1106 terminations and SCSI conformant devices.
1108 config SCSI_NCR53C8XX_PROFILE
1109 bool " enable profiling"
1110 depends on SCSI_ZALON || SCSI_NCR_Q720
1112 This option allows you to enable profiling information gathering.
1113 These statistics are not very accurate due to the low frequency
1114 of the kernel clock (100 Hz on i386) and have performance impact
1115 on systems that use very fast devices.
1117 The normal answer therefore is N.
1119 config SCSI_NCR53C8XX_NO_DISCONNECT
1120 bool " not allow targets to disconnect"
1121 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1123 This option is only provided for safety if you suspect some SCSI
1124 device of yours to not support properly the target-disconnect
1125 feature. In that case, you would say Y here. In general however, to
1126 not allow targets to disconnect is not reasonable if there is more
1127 than 1 device on a SCSI bus. The normal answer therefore is N.
1129 config SCSI_MCA_53C9X
1130 tristate "NCR MCA 53C9x SCSI support"
1131 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1133 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1134 controller based on the NCR 53C94. This driver will allow use of
1135 the controller on the 3550, and very possibly others.
1137 To compile this driver as a module, choose M here: the
1138 module will be called mca_53c9x.
1141 tristate "PAS16 SCSI support"
1142 depends on ISA && SCSI
1144 This is support for a SCSI host adapter. It is explained in section
1145 3.10 of the SCSI-HOWTO, available from
1146 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1147 of the box, you may have to change some settings in
1148 <file:drivers/scsi/pas16.h>.
1150 To compile this driver as a module, choose M here: the
1151 module will be called pas16.
1154 tristate "PCI2000 support"
1155 depends on PCI && SCSI && BROKEN
1157 This is support for the PCI2000I EIDE interface card which acts as a
1158 SCSI host adapter. Please read the SCSI-HOWTO, available from
1159 <http://www.tldp.org/docs.html#howto>.
1161 To compile this driver as a module, choose M here: the
1162 module will be called pci2000.
1164 config SCSI_PCI2220I
1165 tristate "PCI2220i support"
1166 depends on PCI && SCSI && BROKEN
1168 This is support for the PCI2220i EIDE interface card which acts as a
1169 SCSI host adapter. Please read the SCSI-HOWTO, available from
1170 <http://www.tldp.org/docs.html#howto>.
1172 To compile this driver as a module, choose M here: the
1173 module will be called pci2220i.
1176 tristate "PSI240i support"
1177 depends on ISA && SCSI
1179 This is support for the PSI240i EIDE interface card which acts as a
1180 SCSI host adapter. Please read the SCSI-HOWTO, available from
1181 <http://www.tldp.org/docs.html#howto>.
1183 To compile this driver as a module, choose M here: the
1184 module will be called psi240i.
1186 config SCSI_QLOGIC_FAS
1187 tristate "Qlogic FAS SCSI support"
1188 depends on ISA && SCSI
1190 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1191 FastSCSI! cards as well as any other card based on the FASXX chip
1192 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1194 This driver does NOT support the PCI versions of these cards. The
1195 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1196 SCSI support"), below.
1198 Information about this driver is contained in
1199 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1200 SCSI-HOWTO, available from
1201 <http://www.tldp.org/docs.html#howto>.
1203 To compile this driver as a module, choose M here: the
1204 module will be called qlogicfas.
1206 config SCSI_QLOGIC_ISP
1207 tristate "Qlogic ISP SCSI support"
1208 depends on PCI && SCSI
1210 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1211 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1212 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1214 If you say Y here, make sure to choose "BIOS" at the question "PCI
1217 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1218 should also read the SCSI-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here: the
1222 module will be called qlogicisp.
1224 config SCSI_QLOGIC_FC
1225 tristate "Qlogic ISP FC SCSI support"
1226 depends on PCI && SCSI
1228 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1230 To compile this driver as a module, choose M here: the
1231 module will be called qlogicfc.
1233 config SCSI_QLOGIC_FC_FIRMWARE
1234 bool "Include loadable firmware in driver"
1235 depends on SCSI_QLOGIC_FC
1237 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1238 expanded LUN addressing and FcTape (FCP-2) support, in the
1239 qlogicfc driver. This is required on some platforms.
1241 config SCSI_QLOGIC_1280
1242 tristate "Qlogic QLA 1280 SCSI support"
1243 depends on PCI && SCSI
1245 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1247 To compile this driver as a module, choose M here: the
1248 module will be called qla1280.
1250 config SCSI_QLOGICPTI
1251 tristate "PTI Qlogic, ISP Driver"
1252 depends on SBUS && SCSI
1254 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1255 controllers are known under Solaris as qpti and in the openprom as
1256 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1257 driven by a different driver.
1259 To compile this driver as a module, choose M here: the
1260 module will be called qlogicpti.
1262 source "drivers/scsi/qla2xxx/Kconfig"
1265 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1266 depends on X86 && ISA && SCSI && BROKEN
1268 These are 8-bit SCSI controllers; the ST-01 is also supported by
1269 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1270 available from <http://www.tldp.org/docs.html#howto>. If it
1271 doesn't work out of the box, you may have to change some settings in
1272 <file:drivers/scsi/seagate.h>.
1274 To compile this driver as a module, choose M here: the
1275 module will be called seagate.
1277 # definitely looks not 64bit safe:
1279 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1280 depends on (EISA || MCA) && SCSI
1281 select SCSI_SPI_ATTRS
1283 This driver for NCR53c710 based SCSI host adapters.
1285 It currently supports Compaq EISA cards and NCR MCA cards
1287 config 53C700_IO_MAPPED
1289 depends on SCSI_SIM710
1292 config SCSI_SYM53C416
1293 tristate "Symbios 53c416 SCSI support"
1294 depends on ISA && SCSI
1296 This is support for the sym53c416 SCSI host adapter, the SCSI
1297 adapter that comes with some HP scanners. This driver requires that
1298 the sym53c416 is configured first using some sort of PnP
1299 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1300 are using isapnp then you need to compile this driver as a module
1301 and then load it using insmod after isapnp has run. The parameters
1302 of the configured card(s) should be passed to the driver. The format
1305 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1307 To compile this driver as a module, choose M here: the
1308 module will be called sym53c416.
1311 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1312 depends on PCI && SCSI && EXPERIMENTAL
1314 This driver supports PCI SCSI host adapters based on the ASIC
1315 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1317 This driver works, but is still in experimental status. So better
1318 have a bootable disk and a backup in case of emergency.
1320 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1322 To compile this driver as a module, choose M here: the
1323 module will be called dc395x.
1326 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1327 depends on PCI && SCSI
1329 This driver supports PCI SCSI host adapters based on the Am53C974A
1330 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1331 PCscsi/PCnet (Am53/79C974) solutions.
1333 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1335 Note that this driver does NOT support Tekram DC390W/U/F, which are
1336 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1338 To compile this driver as a module, choose M here: the
1339 module will be called tmscsim.
1342 tristate "Trantor T128/T128F/T228 SCSI support"
1343 depends on ISA && SCSI
1345 This is support for a SCSI host adapter. It is explained in section
1346 3.11 of the SCSI-HOWTO, available from
1347 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1348 of the box, you may have to change some settings in
1349 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1350 Adaptec, and some former Trantor products are being sold under the
1353 To compile this driver as a module, choose M here: the
1354 module will be called t128.
1357 tristate "UltraStor 14F/34F support"
1358 depends on ISA && SCSI
1360 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1361 The source at <file:drivers/scsi/u14-34f.c> contains some
1362 information about this hardware. If the driver doesn't work out of
1363 the box, you may have to change some settings in
1364 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1365 <http://www.tldp.org/docs.html#howto>. Note that there is also
1366 another driver for the same hardware: "UltraStor SCSI support",
1367 below. You should say Y to both only if you want 24F support as
1370 To compile this driver as a module, choose M here: the
1371 module will be called u14-34f.
1373 config SCSI_U14_34F_TAGGED_QUEUE
1374 bool "enable tagged command queueing"
1375 depends on SCSI_U14_34F
1377 This is a feature of SCSI-2 which improves performance: the host
1378 adapter can send several SCSI commands to a device's queue even if
1379 previous commands haven't finished yet.
1380 This is equivalent to the "u14-34f=tc:y" boot option.
1382 config SCSI_U14_34F_LINKED_COMMANDS
1383 bool "enable elevator sorting"
1384 depends on SCSI_U14_34F
1386 This option enables elevator sorting for all probed SCSI disks and
1387 CD-ROMs. It definitely reduces the average seek distance when doing
1388 random seeks, but this does not necessarily result in a noticeable
1389 performance improvement: your mileage may vary...
1390 This is equivalent to the "u14-34f=lc:y" boot option.
1392 config SCSI_U14_34F_MAX_TAGS
1393 int "maximum number of queued commands"
1394 depends on SCSI_U14_34F
1397 This specifies how many SCSI commands can be maximally queued for
1398 each probed SCSI device. You should reduce the default value of 8
1399 only if you have disks with buggy or limited tagged command support.
1400 Minimum is 2 and maximum is 14. This value is also the window size
1401 used by the elevator sorting option above. The effective value used
1402 by the driver for each probed SCSI device is reported at boot time.
1403 This is equivalent to the "u14-34f=mq:8" boot option.
1405 config SCSI_ULTRASTOR
1406 tristate "UltraStor SCSI support"
1407 depends on X86 && ISA && SCSI
1409 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1410 adapter family. This driver is explained in section 3.12 of the
1411 SCSI-HOWTO, available from
1412 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1413 of the box, you may have to change some settings in
1414 <file:drivers/scsi/ultrastor.h>.
1416 Note that there is also another driver for the same hardware:
1417 "UltraStor 14F/34F support", above.
1419 To compile this driver as a module, choose M here: the
1420 module will be called ultrastor.
1423 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1424 depends on PCI && SCSI && !64BIT
1426 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1427 SCSI host adapter. Please read the SCSI-HOWTO, available from
1428 <http://www.tldp.org/docs.html#howto>.
1430 To compile this driver as a module, choose M here: the
1431 module will be called nsp32.
1434 tristate "SCSI debugging host simulator"
1437 This is a host adapter simulator that can simulate multiple hosts
1438 each with multiple dummy SCSI devices (disks). It defaults to one
1439 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1440 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1441 dummy disks are simulated, they share the same kernel RAM for
1442 their storage. See http://www.torque.net/sg/sdebug.html for more
1443 information. This driver is primarily of use to those testing the
1444 SCSI and block subsystems. If unsure, say N.
1447 tristate "MESH (Power Mac internal SCSI) support"
1448 depends on PPC_PMAC && SCSI
1450 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1451 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1452 other Power Macintoshes do). Say Y to include support for this SCSI
1455 To compile this driver as a module, choose M here: the
1456 module will be called mesh.
1458 config SCSI_MESH_SYNC_RATE
1459 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1460 depends on SCSI_MESH
1463 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1464 drives a bus which is entirely internal to the machine (such as the
1465 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1466 operation at up to 10 MB/s. On machines where the SCSI bus
1467 controlled by the MESH can have external devices connected, it is
1468 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1469 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1470 to disable synchronous operation.
1472 config SCSI_MESH_RESET_DELAY_MS
1473 int "initial bus reset delay (ms) (0 = no reset)"
1474 depends on SCSI_MESH
1477 config SCSI_MAC53C94
1478 tristate "53C94 (Power Mac external SCSI) support"
1479 depends on PPC_PMAC && SCSI
1481 On Power Macintoshes (and clones) with two SCSI buses, the external
1482 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1483 machines which only have one SCSI bus, such as the 7200, also use
1484 the 53C94. Say Y to include support for the 53C94.
1486 To compile this driver as a module, choose M here: the
1487 module will be called mac53c94.
1489 source "drivers/scsi/arm/Kconfig"
1492 bool "MIPS JAZZ FAS216 SCSI support"
1493 depends on MIPS_JAZZ && SCSI
1495 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1496 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1500 tristate "A3000 WD33C93A support"
1501 depends on AMIGA && SCSI
1503 If you have an Amiga 3000 and have SCSI devices connected to the
1504 built-in SCSI controller, say Y. Otherwise, say N.
1506 To compile this driver as a module, choose M here: the
1507 module will be called wd33c93.
1510 tristate "A2091/A590 WD33C93A support"
1511 depends on ZORRO && SCSI
1513 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1516 To compile this driver as a module, choose M here: the
1517 module will be called wd33c93.
1520 tristate "GVP Series II WD33C93A support"
1521 depends on ZORRO && SCSI
1523 If you have a Great Valley Products Series II SCSI controller,
1524 answer Y. Also say Y if you have a later model of GVP SCSI
1525 controller (such as the GVP A4008 or a Combo board). Otherwise,
1526 answer N. This driver does NOT work for the T-Rex series of
1527 accelerators from TekMagic and GVP-M.
1529 To compile this driver as a module, choose M here: the
1530 module will be called gvp11.
1532 config CYBERSTORM_SCSI
1533 tristate "CyberStorm SCSI support"
1534 depends on ZORRO && SCSI
1536 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1537 accelerator board and the optional Cyberstorm SCSI controller,
1538 answer Y. Otherwise, say N.
1540 config CYBERSTORMII_SCSI
1541 tristate "CyberStorm Mk II SCSI support"
1542 depends on ZORRO && SCSI
1544 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1545 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1549 tristate "Blizzard 2060 SCSI support"
1550 depends on ZORRO && SCSI
1552 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1553 and want to use the onboard SCSI controller, say Y. Otherwise,
1557 tristate "Blizzard 1230IV/1260 SCSI support"
1558 depends on ZORRO && SCSI
1560 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1561 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1564 config FASTLANE_SCSI
1565 tristate "Fastlane SCSI support"
1566 depends on ZORRO && SCSI
1568 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1569 one in the near future, say Y to this question. Otherwise, say N.
1571 config SCSI_AMIGA7XX
1572 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1573 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1575 Support for various NCR53c710-based SCSI controllers on the Amiga.
1577 - the builtin SCSI controller on the Amiga 4000T,
1578 - the Amiga 4091 Zorro III SCSI-2 controller,
1579 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1581 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1582 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1583 accelerator card for the Amiga 1200,
1584 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1585 Note that all of the above SCSI controllers, except for the builtin
1586 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1587 bus, so you also have to enable Zorro bus support if you want to use
1591 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1592 depends on ZORRO && SCSI && EXPERIMENTAL
1594 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1595 Y to this question. If you're in doubt about whether you have one,
1597 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1600 tristate "Atari native SCSI support"
1601 depends on ATARI && SCSI && BROKEN
1603 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1604 Falcon, ...) say Y to get it supported. Of course also, if you have
1605 a compatible SCSI controller (e.g. for Medusa).
1607 To compile this driver as a module, choose M here: the
1608 module will be called atari_scsi.
1610 This driver supports both styles of NCR integration into the
1611 system: the TT style (separate DMA), and the Falcon style (via
1612 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1613 in the Hades (without DMA).
1615 config ATARI_SCSI_TOSHIBA_DELAY
1616 bool "Long delays for Toshiba CD-ROMs"
1617 depends on ATARI_SCSI
1619 This option increases the delay after a SCSI arbitration to
1620 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1621 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1622 would impact performance a bit, so say N.
1624 config ATARI_SCSI_RESET_BOOT
1625 bool "Reset SCSI-devices at boottime"
1626 depends on ATARI_SCSI
1628 Reset the devices on your Atari whenever it boots. This makes the
1629 boot process fractionally longer but may assist recovery from errors
1630 that leave the devices with SCSI operations partway completed.
1633 bool "Hades SCSI DMA emulator"
1634 depends on ATARI_SCSI && HADES
1636 This option enables code which emulates the TT SCSI DMA chip on the
1637 Hades. This increases the SCSI transfer rates at least ten times
1638 compared to PIO transfers.
1641 bool "Macintosh NCR5380 SCSI"
1642 depends on MAC && SCSI
1644 This is the NCR 5380 SCSI controller included on most of the 68030
1645 based Macintoshes. If you have one of these say Y and read the
1646 SCSI-HOWTO, available from
1647 <http://www.tldp.org/docs.html#howto>.
1650 tristate "Macintosh NCR53c9[46] SCSI"
1651 depends on MAC && SCSI
1653 This is the NCR 53c9x SCSI controller found on most of the 68040
1654 based Macintoshes. If you have one of these say Y and read the
1655 SCSI-HOWTO, available from
1656 <http://www.tldp.org/docs.html#howto>.
1658 To compile this driver as a module, choose M here: the
1659 module will be called mac_esp.
1662 bool "WD33C93 SCSI driver for MVME147"
1663 depends on MVME147 && SCSI
1665 Support for the on-board SCSI controller on the Motorola MVME147
1666 single-board computer.
1669 bool "NCR53C710 SCSI driver for MVME16x"
1670 depends on MVME16x && SCSI && BROKEN
1672 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1673 SCSI controller chip. Almost everyone using one of these boards
1674 will want to say Y to this question.
1676 config BVME6000_SCSI
1677 bool "NCR53C710 SCSI driver for BVME6000"
1678 depends on BVME6000 && SCSI && BROKEN
1680 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1681 SCSI controller chip. Almost everyone using one of these boards
1682 will want to say Y to this question.
1684 config SCSI_NCR53C7xx_FAST
1685 bool "allow FAST-SCSI [10MHz]"
1686 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1688 This will enable 10MHz FAST-SCSI transfers with your host
1689 adapter. Some systems have problems with that speed, so it's safest
1693 tristate "Sun3 NCR5380 SCSI"
1694 depends on SUN3 && SCSI
1696 This option will enable support for the OBIO (onboard io) NCR5380
1697 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1698 "Sun3" type VME scsi controllers also based on the NCR5380.
1699 General Linux information on the Sun 3 series (now discontinued)
1700 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1703 bool "Sun3x ESP SCSI"
1704 depends on SUN3X && SCSI
1706 The ESP was an on-board SCSI controller used on Sun 3/80
1707 machines. Say Y here to compile in support for it.
1710 tristate "Sparc ESP Scsi Driver"
1711 depends on SBUS && SCSI
1713 This is the driver for the Sun ESP SCSI host adapter. The ESP
1714 chipset is present in most SPARC SBUS-based computers.
1716 To compile this driver as a module, choose M here: the
1717 module will be called esp.
1719 config SCSI_PC980155
1720 tristate "NEC PC-9801-55 SCSI support"
1721 depends on X86_PC9800 && SCSI
1723 If you have the NEC PC-9801-55 SCSI interface card or compatibles
1724 for NEC PC-9801/PC-9821, say Y.
1728 depends on SCSI_PC980155
1731 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1734 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1735 depends on ARCH_S390 && SCSI
1737 If you want to access SCSI devices attached to your IBM eServer
1738 zSeries by means of Fibre Channel interfaces say Y.
1739 For details please refer to the documentation provided by IBM at
1740 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1742 This driver is also available as a module. This module will be
1743 called zfcp. If you want to compile it as a module, say M here
1744 and read Documentation/modules.txt.
1748 source "drivers/scsi/pcmcia/Kconfig"