1 menu "SCSI device support"
4 tristate "SCSI device support"
6 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
7 any other SCSI device under Linux, say Y and make sure that you know
8 the name of your SCSI host adapter (the card inside your computer
9 that "speaks" the SCSI protocol, also called SCSI controller),
10 because you will be asked for it.
12 You also need to say Y here if you have a device which speaks
13 the SCSI protocol. Examples of this include the parallel port
14 version of the IOMEGA ZIP drive, USB storage devices, Fibre
15 Channel, FireWire storage and the IDE-SCSI emulation driver.
17 To compile this driver as a module, choose M here and read
18 <file:Documentation/scsi/scsi.txt>.
19 The module will be called scsi_mod.
21 However, do not compile this as a module if your root file system
22 (the one containing the directory /) is located on a SCSI device.
25 bool "legacy /proc/scsi/ support"
26 depends on SCSI && PROC_FS
29 This option enables support for the various files in
30 /proc/scsi. In Linux 2.6 this has been superceeded by
31 files in sysfs but many legacy applications rely on this.
35 comment "SCSI support type (disk, tape, CD-ROM)"
39 tristate "SCSI disk support"
42 If you want to use SCSI hard disks, Fibre Channel disks,
43 USB storage or the SCSI or parallel port version of
44 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
45 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
46 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
49 To compile this driver as a module, choose M here and read
50 <file:Documentation/scsi/scsi.txt>.
51 The module will be called sd_mod.
53 Do not compile this driver as a module if your root file system
54 (the one containing the directory /) is located on a SCSI disk.
55 In this case, do not compile the driver for your SCSI host adapter
56 (below) as a module either.
59 tristate "SCSI tape support"
62 If you want to use a SCSI tape drive under Linux, say Y and read the
63 SCSI-HOWTO, available from
64 <http://www.tldp.org/docs.html#howto>, and
65 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
68 To compile this driver as a module, choose M here and read
69 <file:Documentation/scsi/scsi.txt>. The module will be called st.
72 tristate "SCSI OnStream SC-x0 tape support"
75 The OnStream SC-x0 SCSI tape drives can not be driven by the
76 standard st driver, but instead need this special osst driver and
77 use the /dev/osstX char device nodes (major 206). Via usb-storage
78 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
79 as well. Note that there is also a second generation of OnStream
80 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
81 tapes (QIC-157) and can be driven by the standard driver st.
82 For more information, you may have a look at the SCSI-HOWTO
83 <http://www.tldp.org/docs.html#howto> and
84 <file:Documentation/scsi/osst.txt> in the kernel source.
85 More info on the OnStream driver may be found on
86 <http://linux1.onstream.nl/test/>
87 Please also have a look at the standard st docu, as most of it
88 applies to osst as well.
90 To compile this driver as a module, choose M here and read
91 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
94 tristate "SCSI CDROM support"
97 If you want to use a SCSI or FireWire CD-ROM under Linux,
98 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
99 <http://www.tldp.org/docs.html#howto>. Also make sure to say
100 Y or M to "ISO 9660 CD-ROM file system support" later.
102 To compile this driver as a module, choose M here and read
103 <file:Documentation/scsi/scsi.txt>.
104 The module will be called sr_mod.
106 config BLK_DEV_SR_VENDOR
107 bool "Enable vendor-specific extensions (for SCSI CDROM)"
108 depends on BLK_DEV_SR
110 This enables the usage of vendor specific SCSI commands. This is
111 required to support multisession CDs with old NEC/TOSHIBA cdrom
112 drives (and HP Writers). If you have such a drive and get the first
113 session only, try saying Y here; everybody else says N.
116 tristate "SCSI generic support"
119 If you want to use SCSI scanners, synthesizers or CD-writers or just
120 about anything having "SCSI" in its name other than hard disks,
121 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
122 directly, so you need some additional software which knows how to
123 talk to these devices using the SCSI protocol:
125 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
126 writer software look at Cdrtools
127 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
128 and for burning a "disk at once": CDRDAO
129 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
130 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
131 For other devices, it's possible that you'll have to write the
132 driver software yourself. Please read the file
133 <file:Documentation/scsi/scsi-generic.txt> for more information.
135 To compile this driver as a module, choose M here and read
136 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
140 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
143 config SCSI_MULTI_LUN
144 bool "Probe all LUNs on each SCSI device"
147 If you have a SCSI device that supports more than one LUN (Logical
148 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
149 can say Y here to force the SCSI driver to probe for multiple LUNs.
150 A SCSI device with multiple LUNs acts logically like multiple SCSI
151 devices. The vast majority of SCSI devices have only one LUN, and
152 so most people can say N here. The max_luns boot/module parameter
153 allows to override this setting.
155 config SCSI_CONSTANTS
156 bool "Verbose SCSI error reporting (kernel size +=12K)"
159 The error messages regarding your SCSI hardware will be easier to
160 understand if you say Y here; it will enlarge your kernel by about
161 12 KB. If in doubt, say Y.
164 bool "SCSI logging facility"
167 This turns on a logging facility that can be used to debug a number
168 of SCSI related problems.
170 If you say Y here, no logging output will appear by default, but you
171 can enable logging by saying Y to "/proc file system support" and
172 "Sysctl support" below and executing the command
174 echo "scsi log token [level]" > /proc/scsi/scsi
176 at boot time after the /proc file system has been mounted.
178 There are a number of things that can be used for 'token' (you can
179 find them in the source: <file:drivers/scsi/scsi.c>), and this
180 allows you to select the types of information you want, and the
181 level allows you to select the level of verbosity.
183 If you say N here, it may be harder to track down some types of SCSI
184 problems. If you say Y here your kernel will be somewhat larger, but
185 there should be no noticeable performance impact as long as you have
188 menu "SCSI Transport Attributes"
191 config SCSI_SPI_ATTRS
192 tristate "Parallel SCSI (SPI) Transport Attributes"
195 If you wish to export transport-specific information about
196 each attached SCSI device to sysfs, say Y. Otherwise, say N.
199 tristate "FiberChannel Transport Attributes"
202 If you wish to export transport-specific information about
203 each attached FiberChannel device to sysfs, say Y.
208 menu "SCSI low-level drivers"
212 tristate "SGI WD93C93 SCSI Driver"
213 depends on SGI_IP22 && SCSI
215 If you have a Western Digital WD93 SCSI controller on
216 an SGI MIPS system, say Y. Otherwise, say N.
219 tristate "DEC NCR53C94 Scsi Driver"
220 depends on DECSTATION && TC && SCSI
222 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
223 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
226 tristate "DEC SII Scsi Driver"
227 depends on DECSTATION && SCSI
229 config BLK_DEV_3W_XXXX_RAID
230 tristate "3ware 5/6/7/8xxx ATA-RAID support"
231 depends on PCI && SCSI
233 3ware is the only hardware ATA-Raid product in Linux to date.
234 This card is 2,4, or 8 channel master mode support only.
235 SCSI support required!!!
237 <http://www.3ware.com/>
239 Please read the comments at the top of
240 <file:drivers/scsi/3w-xxxx.c>.
243 tristate "3ware 9xxx SATA-RAID support"
244 depends on PCI && SCSI
246 This driver supports the 9000 series 3ware SATA-RAID cards.
248 <http://www.amcc.com>
250 Please read the comments at the top of
251 <file:drivers/scsi/3w-9xxx.c>.
253 config SCSI_7000FASST
254 tristate "7000FASST SCSI support"
255 depends on ISA && SCSI
257 This driver supports the Western Digital 7000 SCSI host adapter
258 family. Some information is in the source:
259 <file:drivers/scsi/wd7000.c>.
261 To compile this driver as a module, choose M here: the
262 module will be called wd7000.
265 tristate "ACARD SCSI support"
266 depends on PCI && SCSI
268 This driver supports the ACARD 870U/W SCSI host adapter.
270 To compile this driver as a module, choose M here: the
271 module will be called atp870u.
274 tristate "Adaptec AHA152X/2825 support"
275 depends on ISA && SCSI && !64BIT
277 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
278 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
279 must be manually specified in this case.
281 It is explained in section 3.3 of the SCSI-HOWTO, available from
282 <http://www.tldp.org/docs.html#howto>. You might also want to
283 read the file <file:Documentation/scsi/aha152x.txt>.
285 To compile this driver as a module, choose M here: the
286 module will be called aha152x.
289 tristate "Adaptec AHA1542 support"
290 depends on ISA && SCSI
292 This is support for a SCSI host adapter. It is explained in section
293 3.4 of the SCSI-HOWTO, available from
294 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
295 purchased by Adaptec, and some former Trantor products are being
296 sold under the Adaptec name. If it doesn't work out of the box, you
297 may have to change some settings in <file:drivers/scsi/aha1542.h>.
299 To compile this driver as a module, choose M here: the
300 module will be called aha1542.
303 tristate "Adaptec AHA1740 support"
304 depends on EISA && SCSI
306 This is support for a SCSI host adapter. It is explained in section
307 3.5 of the SCSI-HOWTO, available from
308 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
309 of the box, you may have to change some settings in
310 <file:drivers/scsi/aha1740.h>.
312 To compile this driver as a module, choose M here: the
313 module will be called aha1740.
316 tristate "Adaptec AACRAID support (EXPERIMENTAL)"
317 depends on EXPERIMENTAL && SCSI && PCI
319 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
321 config SCSI_AIC7XXX_OLD
322 tristate "Adaptec AIC7xxx support (old driver)"
325 WARNING This driver is an older aic7xxx driver and is no longer
326 under active development. Adaptec, Inc. is writing a new driver to
327 take the place of this one, and it is recommended that whenever
328 possible, people should use the new Adaptec written driver instead
329 of this one. This driver will eventually be phased out entirely.
331 This is support for the various aic7xxx based Adaptec SCSI
332 controllers. These include the 274x EISA cards; 284x VLB cards;
333 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
334 motherboard based SCSI controllers from Adaptec. It does not support
335 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
336 support them. It does not support the 2920 cards from Adaptec that
337 use the Future Domain SCSI controller chip. For those cards, you
338 need the "Future Domain 16xx SCSI support" driver.
340 In general, if the controller is based on an Adaptec SCSI controller
341 chip from the aic777x series or the aic78xx series, this driver
342 should work. The only exception is the 7810 which is specifically
343 not supported (that's the RAID controller chip on the AAA-13x
346 Note that the AHA2920 SCSI host adapter is *not* supported by this
347 driver; choose "Future Domain 16xx SCSI support" instead if you have
350 Information on the configuration options for this controller can be
351 found by checking the help file for each of the available
352 configuration options. You should read
353 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
354 contacting the maintainer with any questions. The SCSI-HOWTO,
355 available from <http://www.tldp.org/docs.html#howto>, can also
358 To compile this driver as a module, choose M here: the
359 module will be called aic7xxx_old.
361 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
363 # All the I2O code and drivers do not seem to be 64bit safe.
365 tristate "Adaptec I2O RAID support "
366 depends on !64BIT && SCSI && PCI
368 This driver supports all of Adaptec's I2O based RAID controllers as
369 well as the DPT SmartRaid V cards. This is an Adaptec maintained
370 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
372 To compile this driver as a module, choose M here: the
373 module will be called dpt_i2o.
376 tristate "AdvanSys SCSI support"
377 depends on (ISA || EISA || PCI) && SCSI
379 This is a driver for all SCSI host adapters manufactured by
380 AdvanSys. It is documented in the kernel source in
381 <file:drivers/scsi/advansys.c>.
383 To compile this driver as a module, choose M here: the
384 module will be called advansys.
387 tristate "Always IN2000 SCSI support"
388 depends on ISA && SCSI
390 This is support for an ISA bus SCSI host adapter. You'll find more
391 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
392 out of the box, you may have to change the jumpers for IRQ or
395 To compile this driver as a module, choose M here: the
396 module will be called in2000.
399 tristate "AMI MegaRAID support"
400 depends on PCI && SCSI
402 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
403 and 467 SCSI host adapters.
405 To compile this driver as a module, choose M here: the
406 module will be called megaraid.
409 bool "Serial ATA (SATA) support"
410 depends on SCSI && EXPERIMENTAL
412 This driver family supports Serial ATA host controllers
418 tristate "ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL)"
419 depends on SCSI_SATA && PCI && EXPERIMENTAL
421 This option enables support for Broadcom/Serverworks/Apple K2
427 tristate "Intel PIIX/ICH SATA support"
428 depends on SCSI_SATA && PCI
430 This option enables support for ICH5 Serial ATA.
431 If PATA support was enabled previously, this enables
432 support for select Intel PIIX/ICH PATA host controllers.
436 config SCSI_SATA_PROMISE
437 tristate "Promise SATA TX2/TX4 support"
438 depends on SCSI_SATA && PCI
440 This option enables support for Promise Serial ATA TX2/TX4.
445 tristate "Promise SATA SX4 support"
446 depends on SCSI_SATA && PCI && EXPERIMENTAL
448 This option enables support for Promise Serial ATA SX4.
453 tristate "Silicon Image SATA support"
454 depends on SCSI_SATA && PCI && EXPERIMENTAL
456 This option enables support for Silicon Image Serial ATA.
461 tristate "SiS 964/180 SATA support"
462 depends on SCSI_SATA && PCI
464 This option enables support for SiS Serial ATA 964/180.
469 tristate "VIA SATA support"
470 depends on SCSI_SATA && PCI && EXPERIMENTAL
472 This option enables support for VIA Serial ATA.
476 config SCSI_SATA_VITESSE
477 tristate "VITESSE VSC-7174 SATA support"
478 depends on SCSI_SATA && PCI && EXPERIMENTAL
480 This option enables support for Vitesse VSC7174 Serial ATA.
485 tristate "BusLogic SCSI support"
486 depends on (PCI || ISA || MCA) && SCSI
488 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
489 Adapters. Consult the SCSI-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>, and the files
491 <file:Documentation/scsi/BusLogic.txt> and
492 <file:Documentation/scsi/FlashPoint.txt> for more information.
494 To compile this driver as a module, choose M here: the
495 module will be called BusLogic.
497 config SCSI_OMIT_FLASHPOINT
498 bool "Omit FlashPoint support"
499 depends on SCSI_BUSLOGIC
501 This option allows you to omit the FlashPoint support from the
502 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
503 substantial, so users of MultiMaster Host Adapters may wish to omit
507 # This is marked broken because it uses over 4kB of stack in
509 # 2076 CpqTsProcessIMQEntry
513 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
514 depends on PCI && SCSI && BROKEN
516 Say Y here to compile in support for the Compaq StorageWorks Fibre
517 Channel 64-bit/66Mhz Host Bus Adapter.
520 tristate "DMX3191D SCSI support"
521 depends on PCI && SCSI
523 This is support for Domex DMX3191D SCSI Host Adapters.
525 To compile this driver as a module, choose M here: the
526 module will be called dmx3191d.
529 tristate "DTC3180/3280 SCSI support"
530 depends on ISA && SCSI
532 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
533 the SCSI-HOWTO, available from
534 <http://www.tldp.org/docs.html#howto>, and the file
535 <file:Documentation/scsi/dtc3x80.txt>.
537 To compile this driver as a module, choose M here: the
538 module will be called dtc.
541 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
542 depends on (ISA || EISA || PCI) && SCSI
544 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
545 ISA and all EISA I/O addresses are probed looking for the "EATA"
546 signature. The addresses of all the PCI SCSI controllers reported
547 by the PCI subsystem are probed as well.
549 You want to read the start of <file:drivers/scsi/eata.c> and the
550 SCSI-HOWTO, available from
551 <http://www.tldp.org/docs.html#howto>.
553 To compile this driver as a module, choose M here: the
554 module will be called eata.
556 config SCSI_EATA_TAGGED_QUEUE
557 bool "enable tagged command queueing"
560 This is a feature of SCSI-2 which improves performance: the host
561 adapter can send several SCSI commands to a device's queue even if
562 previous commands haven't finished yet.
563 This is equivalent to the "eata=tc:y" boot option.
565 config SCSI_EATA_LINKED_COMMANDS
566 bool "enable elevator sorting"
569 This option enables elevator sorting for all probed SCSI disks and
570 CD-ROMs. It definitely reduces the average seek distance when doing
571 random seeks, but this does not necessarily result in a noticeable
572 performance improvement: your mileage may vary...
573 This is equivalent to the "eata=lc:y" boot option.
575 config SCSI_EATA_MAX_TAGS
576 int "maximum number of queued commands"
580 This specifies how many SCSI commands can be maximally queued for
581 each probed SCSI device. You should reduce the default value of 16
582 only if you have disks with buggy or limited tagged command support.
583 Minimum is 2 and maximum is 62. This value is also the window size
584 used by the elevator sorting option above. The effective value used
585 by the driver for each probed SCSI device is reported at boot time.
586 This is equivalent to the "eata=mq:8" boot option.
589 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
592 This driver supports all EATA-PIO protocol compliant SCSI Host
593 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
594 host adapters could also use this driver but are discouraged from
595 doing so, since this driver only supports hard disks and lacks
596 numerous features. You might want to have a look at the SCSI-HOWTO,
597 available from <http://www.tldp.org/docs.html#howto>.
599 To compile this driver as a module, choose M here: the
600 module will be called eata_pio.
602 config SCSI_FUTURE_DOMAIN
603 tristate "Future Domain 16xx SCSI/AHA-2920A support"
604 depends on (ISA || PCI) && SCSI
606 This is support for Future Domain's 16-bit SCSI host adapters
607 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
608 other adapters based on the Future Domain chipsets (Quantum
609 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
610 It is explained in section 3.7 of the SCSI-HOWTO, available from
611 <http://www.tldp.org/docs.html#howto>.
613 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
614 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
615 controller support"). This Future Domain driver works with the older
616 Adaptec AHA-2920A boards with a Future Domain chip on them.
618 To compile this driver as a module, choose M here: the
619 module will be called fdomain.
622 tristate "Future Domain MCS-600/700 SCSI support"
623 depends on MCA && SCSI
625 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
626 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
627 is identical to the MCS 700 and hence also supported by this driver.
628 This driver also supports the Reply SB16/SCSI card (the SCSI part).
629 It supports multiple adapters in the same system.
631 To compile this driver as a module, choose M here: the
632 module will be called fd_mcs.
635 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
636 depends on (ISA || EISA || PCI) && SCSI
638 Formerly called GDT SCSI Disk Array Controller Support.
640 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
641 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
642 in the kernel source in <file:drivers/scsi/gdth.c> and
643 <file:drivers/scsi/gdth.h.>
645 To compile this driver as a module, choose M here: the
646 module will be called gdth.
648 config SCSI_GENERIC_NCR5380
649 tristate "Generic NCR5380/53c400 SCSI PIO support"
650 depends on ISA && SCSI
652 This is a driver for the old NCR 53c80 series of SCSI controllers
653 on boards using PIO. Most boards such as the Trantor T130 fit this
654 category, along with a large number of ISA 8bit controllers shipped
655 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
656 you should select the specific driver for that card rather than
657 generic 5380 support.
659 It is explained in section 3.8 of the SCSI-HOWTO, available from
660 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
661 of the box, you may have to change some settings in
662 <file:drivers/scsi/g_NCR5380.h>.
664 To compile this driver as a module, choose M here: the
665 module will be called g_NCR5380.
667 config SCSI_GENERIC_NCR5380_MMIO
668 tristate "Generic NCR5380/53c400 SCSI MMIO support"
669 depends on ISA && SCSI
671 This is a driver for the old NCR 53c80 series of SCSI controllers
672 on boards using memory mapped I/O.
673 It is explained in section 3.8 of the SCSI-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
675 of the box, you may have to change some settings in
676 <file:drivers/scsi/g_NCR5380.h>.
678 To compile this driver as a module, choose M here: the
679 module will be called g_NCR5380_mmio.
681 config SCSI_GENERIC_NCR53C400
682 bool "Enable NCR53c400 extensions"
683 depends on SCSI_GENERIC_NCR5380
685 This enables certain optimizations for the NCR53c400 SCSI cards.
686 You might as well try it out. Note that this driver will only probe
687 for the Trantor T130B in its default configuration; you might have
688 to pass a command line option to the kernel at boot time if it does
689 not detect your card. See the file
690 <file:Documentation/scsi/g_NCR5380.txt> for details.
693 tristate "IBMMCA SCSI support"
694 depends on MCA && SCSI
696 This is support for the IBM SCSI adapter found in many of the PS/2
697 series computers. These machines have an MCA bus, so you need to
698 answer Y to "MCA support" as well and read
699 <file:Documentation/mca.txt>.
701 If the adapter isn't found during boot (a common problem for models
702 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
703 option, where <pun> is the id of the SCSI subsystem (usually 7, but
704 if that doesn't work check your reference diskette). Owners of
705 model 95 with a LED-matrix-display can in addition activate some
706 activity info like under OS/2, but more informative, by setting
707 'ibmmcascsi=display' as an additional kernel parameter. Try "man
708 bootparam" or see the documentation of your boot loader about how to
709 pass options to the kernel.
711 To compile this driver as a module, choose M here: the
712 module will be called ibmmca.
714 config IBMMCA_SCSI_ORDER_STANDARD
715 bool "Standard SCSI-order"
716 depends on SCSI_IBMMCA
718 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
719 are assigned to the drive letters, starting with the lowest SCSI-id
720 (physical number -- pun) to be drive C:, as seen from DOS and
721 similar operating systems. When looking into papers describing the
722 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
723 The SCSI-standard follows a hardware-hierarchy which says that id 7
724 has the highest priority and id 0 the lowest. Therefore, the host
725 adapters are still today everywhere placed as SCSI-id 7 by default.
726 In the SCSI-standard, the drive letters express the priority of the
727 disk. C: should be the hard disk, or a partition on it, with the
728 highest priority. This must therefore be the disk with the highest
729 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
730 original definition of the SCSI-standard as also industrial- and
731 process-control-machines, like VME-CPUs running under realtime-OSes
732 (e.g. LynxOS, OS9) do.
734 If you like to run Linux on your MCA-machine with the same
735 assignment of hard disks as seen from e.g. DOS or OS/2 on your
736 machine, which is in addition conformant to the SCSI-standard, you
737 must say Y here. This is also necessary for MCA-Linux users who want
738 to keep downward compatibility to older releases of the
739 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
742 If you like to have the lowest SCSI-id assigned as drive C:, as
743 modern SCSI-BIOSes do, which does not conform to the standard, but
744 is widespread and common in the PC-world of today, you must say N
745 here. If unsure, say Y.
747 config IBMMCA_SCSI_DEV_RESET
748 bool "Reset SCSI-devices at boottime"
749 depends on SCSI_IBMMCA
751 By default, SCSI-devices are reset when the machine is powered on.
752 However, some devices exist, like special-control-devices,
753 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
754 not reset when switched on. If you say Y here, each device connected
755 to your SCSI-bus will be issued a reset-command after it has been
756 probed, while the kernel is booting. This may cause problems with
757 more modern devices, like hard disks, which do not appreciate these
758 reset commands, and can cause your system to hang. So say Y only if
759 you know that one of your older devices needs it; N is the safe
763 tristate "IBM ServeRAID support"
764 depends on PCI && SCSI
766 This is support for the IBM ServeRAID hardware RAID controllers.
767 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
768 for more information. If this driver does not work correctly
769 without modification please contact the author by email at
770 ipslinux@adaptec.com.
772 To compile this driver as a module, choose M here: the
773 module will be called ips.
776 tristate "Initio 9100U(W) support"
777 depends on PCI && SCSI && BROKEN
779 This is support for the Initio 91XXU(W) SCSI host adapter. Please
780 read the SCSI-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 To compile this driver as a module, choose M here: the
784 module will be called initio.
787 tristate "Initio INI-A100U2W support"
788 depends on PCI && SCSI
790 This is support for the Initio INI-A100U2W SCSI host adapter.
791 Please read the SCSI-HOWTO, available from
792 <http://www.tldp.org/docs.html#howto>.
794 To compile this driver as a module, choose M here: the
795 module will be called a100u2w.
798 tristate "IOMEGA parallel port (ppa - older drives)"
799 depends on SCSI && PARPORT
801 This driver supports older versions of IOMEGA's parallel port ZIP
802 drive (a 100 MB removable media device).
804 Note that you can say N here if you have the SCSI version of the ZIP
805 drive: it will be supported automatically if you said Y to the
806 generic "SCSI disk support", above.
808 If you have the ZIP Plus drive or a more recent parallel port ZIP
809 drive (if the supplied cable with the drive is labeled "AutoDetect")
810 then you should say N here and Y to "IOMEGA parallel port (imm -
811 newer drives)", below.
813 For more information about this driver and how to use it you should
814 read the file <file:Documentation/scsi/ppa.txt>. You should also read
815 the SCSI-HOWTO, which is available from
816 <http://www.tldp.org/docs.html#howto>. If you use this driver,
817 you will still be able to use the parallel port for other tasks,
818 such as a printer; it is safe to compile both drivers into the
821 To compile this driver as a module, choose M here: the
822 module will be called ppa.
825 tristate "IOMEGA parallel port (imm - newer drives)"
826 depends on SCSI && PARPORT
828 This driver supports newer versions of IOMEGA's parallel port ZIP
829 drive (a 100 MB removable media device).
831 Note that you can say N here if you have the SCSI version of the ZIP
832 drive: it will be supported automatically if you said Y to the
833 generic "SCSI disk support", above.
835 If you have the ZIP Plus drive or a more recent parallel port ZIP
836 drive (if the supplied cable with the drive is labeled "AutoDetect")
837 then you should say Y here; if you have an older ZIP drive, say N
838 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
840 For more information about this driver and how to use it you should
841 read the file <file:Documentation/scsi/ppa.txt>. You should also read
842 the SCSI-HOWTO, which is available from
843 <http://www.tldp.org/docs.html#howto>. If you use this driver,
844 you will still be able to use the parallel port for other tasks,
845 such as a printer; it is safe to compile both drivers into the
848 To compile this driver as a module, choose M here: the
849 module will be called imm.
851 config SCSI_IZIP_EPP16
852 bool "ppa/imm option - Use slow (but safe) EPP-16"
853 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
855 EPP (Enhanced Parallel Port) is a standard for parallel ports which
856 allows them to act as expansion buses that can handle up to 64
859 Some parallel port chipsets are slower than their motherboard, and
860 so we have to control the state of the chipset's FIFO queue every
861 now and then to avoid data loss. This will be done if you say Y
864 Generally, saying Y is the safe option and slows things down a bit.
866 config SCSI_IZIP_SLOW_CTR
867 bool "ppa/imm option - Assume slow parport control register"
868 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
870 Some parallel ports are known to have excessive delays between
871 changing the parallel port control register and good data being
872 available on the parallel port data/status register. This option
873 forces a small delay (1.0 usec to be exact) after changing the
874 control register to let things settle out. Enabling this option may
875 result in a big drop in performance but some very old parallel ports
876 (found in 386 vintage machines) will not work properly.
878 Generally, saying N is fine.
880 config SCSI_NCR53C406A
881 tristate "NCR53c406a SCSI support"
882 depends on ISA && SCSI
884 This is support for the NCR53c406a SCSI host adapter. For user
885 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
886 in the kernel source. Also read the SCSI-HOWTO, available from
887 <http://www.tldp.org/docs.html#howto>.
889 To compile this driver as a module, choose M here: the
890 module will be called NCR53c406.
893 tristate "NCR Dual 700 MCA SCSI support"
894 depends on MCA && SCSI
895 select SCSI_SPI_ATTRS
897 This is a driver for the MicroChannel Dual 700 card produced by
898 NCR and commonly used in 345x/35xx/4100 class machines. It always
899 tries to negotiate sync and uses tag command queueing.
901 Unless you have an NCR manufactured machine, the chances are that
902 you do not have this SCSI card, so say N.
904 config 53C700_IO_MAPPED
906 depends on SCSI_NCR_D700
910 tristate "HP Lasi SCSI support for 53c700/710"
911 depends on GSC && SCSI
912 select SCSI_SPI_ATTRS
914 This is a driver for the SCSI controller in the Lasi chip found in
915 many PA-RISC workstations & servers. If you do not know whether you
916 have a Lasi chip, it is safe to say "Y" here.
918 config 53C700_MEM_MAPPED
920 depends on SCSI_LASI700
923 config 53C700_LE_ON_BE
925 depends on SCSI_LASI700
928 config SCSI_SYM53C8XX_2
929 tristate "SYM53C8XX Version 2 SCSI support"
930 depends on PCI && SCSI
931 select SCSI_SPI_ATTRS
933 This driver supports the whole NCR53C8XX/SYM53C8XX family of
934 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
935 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
936 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
937 controllers; you need to use the Fusion MPT driver for that.
939 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
942 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
943 int "DMA addressing mode"
944 depends on SCSI_SYM53C8XX_2
947 This option only applies to PCI-SCSI chips that are PCI DAC
948 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
950 When set to 0, the driver will program the chip to only perform
951 32-bit DMA. When set to 1, the chip will be able to perform DMA
952 to addresses up to 1TB. When set to 2, the driver supports the
953 full 64-bit DMA address range, but can only address 16 segments
954 of 4 GB each. This limits the total addressable range to 64 GB.
956 Most machines with less than 4GB of memory should use a setting
957 of 0 for best performance. If your machine has 4GB of memory
958 or more, you should set this option to 1 (the default).
960 The still experimental value 2 (64 bit DMA addressing with 16
961 x 4GB segments limitation) can be used on systems that require
962 PCI address bits past bit 39 to be set for the addressing of
963 memory using PCI DAC cycles.
965 config SCSI_SYM53C8XX_DEFAULT_TAGS
966 int "default tagged command queue depth"
967 depends on SCSI_SYM53C8XX_2
970 This is the default value of the command queue depth the
971 driver will announce to the generic SCSI layer for devices
972 that support tagged command queueing. This value can be changed
973 from the boot command line. This is a soft limit that cannot
974 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
976 config SCSI_SYM53C8XX_MAX_TAGS
977 int "maximum number of queued commands"
978 depends on SCSI_SYM53C8XX_2
981 This option allows you to specify the maximum number of commands
982 that can be queued to any device, when tagged command queuing is
983 possible. The driver supports up to 256 queued commands per device.
984 This value is used as a compiled-in hard limit.
986 config SCSI_SYM53C8XX_IOMAPPED
988 depends on SCSI_SYM53C8XX_2
990 If you say Y here, the driver will use port IO to access
991 the card. This is significantly slower then using memory
992 mapped IO. Most people should answer N.
995 tristate "IBM Power Linux RAID adapter support"
996 depends on PCI && SCSI
999 This driver supports the IBM Power Linux family RAID adapters.
1000 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1001 as IBM iSeries 5702, 5703, 5709, and 570A.
1003 config SCSI_IPR_TRACE
1004 bool "enable driver internal trace"
1007 If you say Y here, the driver will trace all commands issued
1008 to the adapter. Performance impact is minimal. Trace can be
1009 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1011 config SCSI_IPR_DUMP
1012 bool "enable adapter dump support"
1015 If you say Y here, the driver will support adapter crash dump.
1016 If you enable this support, the iprdump daemon can be used
1017 to capture adapter failure analysis information.
1020 tristate "Zalon SCSI support"
1021 depends on GSC && SCSI
1023 The Zalon is a GSC/HSC bus interface chip that sits between the
1024 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1025 C110, J200, J210 and some D, K & R-class machines. It's also
1026 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1027 Say Y here if you have one of these machines or cards.
1029 config SCSI_NCR_Q720
1030 tristate "NCR Quad 720 MCA SCSI support"
1031 depends on MCA && SCSI
1033 This is a driver for the MicroChannel Quad 720 card produced by
1034 NCR and commonly used in 345x/35xx/4100 class machines. It always
1035 tries to negotiate sync and uses tag command queueing.
1037 Unless you have an NCR manufactured machine, the chances are that
1038 you do not have this SCSI card, so say N.
1040 config SCSI_NCR53C8XX_DEFAULT_TAGS
1041 int " default tagged command queue depth"
1042 depends on SCSI_ZALON || SCSI_NCR_Q720
1045 "Tagged command queuing" is a feature of SCSI-2 which improves
1046 performance: the host adapter can send several SCSI commands to a
1047 device's queue even if previous commands haven't finished yet.
1048 Because the device is intelligent, it can optimize its operations
1049 (like head positioning) based on its own request queue. Some SCSI
1050 devices don't implement this properly; if you want to disable this
1051 feature, enter 0 or 1 here (it doesn't matter which).
1053 The default value is 8 and should be supported by most hard disks.
1054 This value can be overridden from the boot command line using the
1055 'tags' option as follows (example):
1056 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1057 4, set queue depth to 16 for target 2 and target 3 on controller 0
1058 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1060 The normal answer therefore is to go with the default 8 and to use
1061 a boot command line option for devices that need to use a different
1062 command queue depth.
1064 There is no safe option other than using good SCSI devices.
1066 config SCSI_NCR53C8XX_MAX_TAGS
1067 int " maximum number of queued commands"
1068 depends on SCSI_ZALON || SCSI_NCR_Q720
1071 This option allows you to specify the maximum number of commands
1072 that can be queued to any device, when tagged command queuing is
1073 possible. The default value is 32. Minimum is 2, maximum is 64.
1074 Modern hard disks are able to support 64 tags and even more, but
1075 do not seem to be faster when more than 32 tags are being used.
1077 So, the normal answer here is to go with the default value 32 unless
1078 you are using very large hard disks with large cache (>= 1 MB) that
1079 are able to take advantage of more than 32 tagged commands.
1081 There is no safe option and the default answer is recommended.
1083 config SCSI_NCR53C8XX_SYNC
1084 int " synchronous transfers frequency in MHz"
1085 depends on SCSI_ZALON || SCSI_NCR_Q720
1088 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1089 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1090 are respectively the maximum data transfer rates in mega-transfers
1091 per second for each class. For example, a FAST-20 Wide 16 device is
1092 able to transfer data at 20 million 16 bit packets per second for a
1093 total rate of 40 MB/s.
1095 You may specify 0 if you want to only use asynchronous data
1096 transfers. This is the safest and slowest option. Otherwise, specify
1097 a value between 5 and 80, depending on the capability of your SCSI
1098 controller. The higher the number, the faster the data transfer.
1099 Note that 80 should normally be ok since the driver decreases the
1100 value automatically according to the controller's capabilities.
1102 Your answer to this question is ignored for controllers with NVRAM,
1103 since the driver will get this information from the user set-up. It
1104 also can be overridden using a boot setup option, as follows
1105 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1106 for FAST-20 synchronous data transfer (20 mega-transfers per
1109 The normal answer therefore is not to go with the default but to
1110 select the maximum value 80 allowing the driver to use the maximum
1111 value supported by each controller. If this causes problems with
1112 your SCSI devices, you should come back and decrease the value.
1114 There is no safe option other than using good cabling, right
1115 terminations and SCSI conformant devices.
1117 config SCSI_NCR53C8XX_PROFILE
1118 bool " enable profiling"
1119 depends on SCSI_ZALON || SCSI_NCR_Q720
1121 This option allows you to enable profiling information gathering.
1122 These statistics are not very accurate due to the low frequency
1123 of the kernel clock (100 Hz on i386) and have performance impact
1124 on systems that use very fast devices.
1126 The normal answer therefore is N.
1128 config SCSI_NCR53C8XX_NO_DISCONNECT
1129 bool " not allow targets to disconnect"
1130 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1132 This option is only provided for safety if you suspect some SCSI
1133 device of yours to not support properly the target-disconnect
1134 feature. In that case, you would say Y here. In general however, to
1135 not allow targets to disconnect is not reasonable if there is more
1136 than 1 device on a SCSI bus. The normal answer therefore is N.
1138 config SCSI_MCA_53C9X
1139 tristate "NCR MCA 53C9x SCSI support"
1140 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1142 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1143 controller based on the NCR 53C94. This driver will allow use of
1144 the controller on the 3550, and very possibly others.
1146 To compile this driver as a module, choose M here: the
1147 module will be called mca_53c9x.
1150 tristate "PAS16 SCSI support"
1151 depends on ISA && SCSI
1153 This is support for a SCSI host adapter. It is explained in section
1154 3.10 of the SCSI-HOWTO, available from
1155 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1156 of the box, you may have to change some settings in
1157 <file:drivers/scsi/pas16.h>.
1159 To compile this driver as a module, choose M here: the
1160 module will be called pas16.
1163 tristate "PCI2000 support"
1164 depends on PCI && SCSI && BROKEN
1166 This is support for the PCI2000I EIDE interface card which acts as a
1167 SCSI host adapter. Please read the SCSI-HOWTO, available from
1168 <http://www.tldp.org/docs.html#howto>.
1170 To compile this driver as a module, choose M here: the
1171 module will be called pci2000.
1173 config SCSI_PCI2220I
1174 tristate "PCI2220i support"
1175 depends on PCI && SCSI && BROKEN
1177 This is support for the PCI2220i EIDE interface card which acts as a
1178 SCSI host adapter. Please read the SCSI-HOWTO, available from
1179 <http://www.tldp.org/docs.html#howto>.
1181 To compile this driver as a module, choose M here: the
1182 module will be called pci2220i.
1185 tristate "PSI240i support"
1186 depends on ISA && SCSI
1188 This is support for the PSI240i EIDE interface card which acts as a
1189 SCSI host adapter. Please read the SCSI-HOWTO, available from
1190 <http://www.tldp.org/docs.html#howto>.
1192 To compile this driver as a module, choose M here: the
1193 module will be called psi240i.
1195 config SCSI_QLOGIC_FAS
1196 tristate "Qlogic FAS SCSI support"
1197 depends on ISA && SCSI
1199 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1200 FastSCSI! cards as well as any other card based on the FASXX chip
1201 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1203 This driver does NOT support the PCI versions of these cards. The
1204 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1205 SCSI support"), below.
1207 Information about this driver is contained in
1208 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1209 SCSI-HOWTO, available from
1210 <http://www.tldp.org/docs.html#howto>.
1212 To compile this driver as a module, choose M here: the
1213 module will be called qlogicfas.
1215 config SCSI_QLOGIC_ISP
1216 tristate "Qlogic ISP SCSI support"
1217 depends on PCI && SCSI
1219 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1220 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1221 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1223 If you say Y here, make sure to choose "BIOS" at the question "PCI
1226 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1227 should also read the SCSI-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here: the
1231 module will be called qlogicisp.
1233 config SCSI_QLOGIC_FC
1234 tristate "Qlogic ISP FC SCSI support"
1235 depends on PCI && SCSI
1237 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1239 To compile this driver as a module, choose M here: the
1240 module will be called qlogicfc.
1242 config SCSI_QLOGIC_FC_FIRMWARE
1243 bool "Include loadable firmware in driver"
1244 depends on SCSI_QLOGIC_FC
1246 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1247 expanded LUN addressing and FcTape (FCP-2) support, in the
1248 qlogicfc driver. This is required on some platforms.
1250 config SCSI_QLOGIC_1280
1251 tristate "Qlogic QLA 1280 SCSI support"
1252 depends on PCI && SCSI
1254 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1256 To compile this driver as a module, choose M here: the
1257 module will be called qla1280.
1259 config SCSI_QLOGICPTI
1260 tristate "PTI Qlogic, ISP Driver"
1261 depends on SBUS && SCSI
1263 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1264 controllers are known under Solaris as qpti and in the openprom as
1265 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1266 driven by a different driver.
1268 To compile this driver as a module, choose M here: the
1269 module will be called qlogicpti.
1271 source "drivers/scsi/qla2xxx/Kconfig"
1274 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1275 depends on X86 && ISA && SCSI && BROKEN
1277 These are 8-bit SCSI controllers; the ST-01 is also supported by
1278 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1279 available from <http://www.tldp.org/docs.html#howto>. If it
1280 doesn't work out of the box, you may have to change some settings in
1281 <file:drivers/scsi/seagate.h>.
1283 To compile this driver as a module, choose M here: the
1284 module will be called seagate.
1286 # definitely looks not 64bit safe:
1288 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1289 depends on (EISA || MCA) && SCSI
1290 select SCSI_SPI_ATTRS
1292 This driver for NCR53c710 based SCSI host adapters.
1294 It currently supports Compaq EISA cards and NCR MCA cards
1296 config 53C700_IO_MAPPED
1298 depends on SCSI_SIM710
1301 config SCSI_SYM53C416
1302 tristate "Symbios 53c416 SCSI support"
1303 depends on ISA && SCSI
1305 This is support for the sym53c416 SCSI host adapter, the SCSI
1306 adapter that comes with some HP scanners. This driver requires that
1307 the sym53c416 is configured first using some sort of PnP
1308 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1309 are using isapnp then you need to compile this driver as a module
1310 and then load it using insmod after isapnp has run. The parameters
1311 of the configured card(s) should be passed to the driver. The format
1314 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1316 To compile this driver as a module, choose M here: the
1317 module will be called sym53c416.
1320 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1321 depends on PCI && SCSI && EXPERIMENTAL
1323 This driver supports PCI SCSI host adapters based on the ASIC
1324 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1326 This driver works, but is still in experimental status. So better
1327 have a bootable disk and a backup in case of emergency.
1329 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1331 To compile this driver as a module, choose M here: the
1332 module will be called dc395x.
1335 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1336 depends on PCI && SCSI
1338 This driver supports PCI SCSI host adapters based on the Am53C974A
1339 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1340 PCscsi/PCnet (Am53/79C974) solutions.
1342 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1344 Note that this driver does NOT support Tekram DC390W/U/F, which are
1345 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1347 To compile this driver as a module, choose M here: the
1348 module will be called tmscsim.
1351 tristate "Trantor T128/T128F/T228 SCSI support"
1352 depends on ISA && SCSI
1354 This is support for a SCSI host adapter. It is explained in section
1355 3.11 of the SCSI-HOWTO, available from
1356 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1357 of the box, you may have to change some settings in
1358 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1359 Adaptec, and some former Trantor products are being sold under the
1362 To compile this driver as a module, choose M here: the
1363 module will be called t128.
1366 tristate "UltraStor 14F/34F support"
1367 depends on ISA && SCSI
1369 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1370 The source at <file:drivers/scsi/u14-34f.c> contains some
1371 information about this hardware. If the driver doesn't work out of
1372 the box, you may have to change some settings in
1373 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1374 <http://www.tldp.org/docs.html#howto>. Note that there is also
1375 another driver for the same hardware: "UltraStor SCSI support",
1376 below. You should say Y to both only if you want 24F support as
1379 To compile this driver as a module, choose M here: the
1380 module will be called u14-34f.
1382 config SCSI_U14_34F_TAGGED_QUEUE
1383 bool "enable tagged command queueing"
1384 depends on SCSI_U14_34F
1386 This is a feature of SCSI-2 which improves performance: the host
1387 adapter can send several SCSI commands to a device's queue even if
1388 previous commands haven't finished yet.
1389 This is equivalent to the "u14-34f=tc:y" boot option.
1391 config SCSI_U14_34F_LINKED_COMMANDS
1392 bool "enable elevator sorting"
1393 depends on SCSI_U14_34F
1395 This option enables elevator sorting for all probed SCSI disks and
1396 CD-ROMs. It definitely reduces the average seek distance when doing
1397 random seeks, but this does not necessarily result in a noticeable
1398 performance improvement: your mileage may vary...
1399 This is equivalent to the "u14-34f=lc:y" boot option.
1401 config SCSI_U14_34F_MAX_TAGS
1402 int "maximum number of queued commands"
1403 depends on SCSI_U14_34F
1406 This specifies how many SCSI commands can be maximally queued for
1407 each probed SCSI device. You should reduce the default value of 8
1408 only if you have disks with buggy or limited tagged command support.
1409 Minimum is 2 and maximum is 14. This value is also the window size
1410 used by the elevator sorting option above. The effective value used
1411 by the driver for each probed SCSI device is reported at boot time.
1412 This is equivalent to the "u14-34f=mq:8" boot option.
1414 config SCSI_ULTRASTOR
1415 tristate "UltraStor SCSI support"
1416 depends on X86 && ISA && SCSI
1418 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1419 adapter family. This driver is explained in section 3.12 of the
1420 SCSI-HOWTO, available from
1421 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1422 of the box, you may have to change some settings in
1423 <file:drivers/scsi/ultrastor.h>.
1425 Note that there is also another driver for the same hardware:
1426 "UltraStor 14F/34F support", above.
1428 To compile this driver as a module, choose M here: the
1429 module will be called ultrastor.
1432 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1433 depends on PCI && SCSI && !64BIT
1435 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1436 SCSI host adapter. Please read the SCSI-HOWTO, available from
1437 <http://www.tldp.org/docs.html#howto>.
1439 To compile this driver as a module, choose M here: the
1440 module will be called nsp32.
1443 tristate "SCSI debugging host simulator"
1446 This is a host adapter simulator that can simulate multiple hosts
1447 each with multiple dummy SCSI devices (disks). It defaults to one
1448 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1449 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1450 dummy disks are simulated, they share the same kernel RAM for
1451 their storage. See http://www.torque.net/sg/sdebug.html for more
1452 information. This driver is primarily of use to those testing the
1453 SCSI and block subsystems. If unsure, say N.
1456 tristate "MESH (Power Mac internal SCSI) support"
1457 depends on PPC_PMAC && SCSI
1459 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1460 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1461 other Power Macintoshes do). Say Y to include support for this SCSI
1464 To compile this driver as a module, choose M here: the
1465 module will be called mesh.
1467 config SCSI_MESH_SYNC_RATE
1468 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1469 depends on SCSI_MESH
1472 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1473 drives a bus which is entirely internal to the machine (such as the
1474 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1475 operation at up to 10 MB/s. On machines where the SCSI bus
1476 controlled by the MESH can have external devices connected, it is
1477 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1478 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1479 to disable synchronous operation.
1481 config SCSI_MESH_RESET_DELAY_MS
1482 int "initial bus reset delay (ms) (0 = no reset)"
1483 depends on SCSI_MESH
1486 config SCSI_MAC53C94
1487 tristate "53C94 (Power Mac external SCSI) support"
1488 depends on PPC_PMAC && SCSI
1490 On Power Macintoshes (and clones) with two SCSI buses, the external
1491 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1492 machines which only have one SCSI bus, such as the 7200, also use
1493 the 53C94. Say Y to include support for the 53C94.
1495 To compile this driver as a module, choose M here: the
1496 module will be called mac53c94.
1498 source "drivers/scsi/arm/Kconfig"
1501 bool "MIPS JAZZ FAS216 SCSI support"
1502 depends on MIPS_JAZZ && SCSI
1504 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1505 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1509 tristate "A3000 WD33C93A support"
1510 depends on AMIGA && SCSI
1512 If you have an Amiga 3000 and have SCSI devices connected to the
1513 built-in SCSI controller, say Y. Otherwise, say N.
1515 To compile this driver as a module, choose M here: the
1516 module will be called wd33c93.
1519 tristate "A2091/A590 WD33C93A support"
1520 depends on ZORRO && SCSI
1522 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1525 To compile this driver as a module, choose M here: the
1526 module will be called wd33c93.
1529 tristate "GVP Series II WD33C93A support"
1530 depends on ZORRO && SCSI
1532 If you have a Great Valley Products Series II SCSI controller,
1533 answer Y. Also say Y if you have a later model of GVP SCSI
1534 controller (such as the GVP A4008 or a Combo board). Otherwise,
1535 answer N. This driver does NOT work for the T-Rex series of
1536 accelerators from TekMagic and GVP-M.
1538 To compile this driver as a module, choose M here: the
1539 module will be called gvp11.
1541 config CYBERSTORM_SCSI
1542 tristate "CyberStorm SCSI support"
1543 depends on ZORRO && SCSI
1545 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1546 accelerator board and the optional Cyberstorm SCSI controller,
1547 answer Y. Otherwise, say N.
1549 config CYBERSTORMII_SCSI
1550 tristate "CyberStorm Mk II SCSI support"
1551 depends on ZORRO && SCSI
1553 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1554 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1558 tristate "Blizzard 2060 SCSI support"
1559 depends on ZORRO && SCSI
1561 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1562 and want to use the onboard SCSI controller, say Y. Otherwise,
1566 tristate "Blizzard 1230IV/1260 SCSI support"
1567 depends on ZORRO && SCSI
1569 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1570 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1573 config FASTLANE_SCSI
1574 tristate "Fastlane SCSI support"
1575 depends on ZORRO && SCSI
1577 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1578 one in the near future, say Y to this question. Otherwise, say N.
1580 config SCSI_AMIGA7XX
1581 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1582 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1584 Support for various NCR53c710-based SCSI controllers on the Amiga.
1586 - the builtin SCSI controller on the Amiga 4000T,
1587 - the Amiga 4091 Zorro III SCSI-2 controller,
1588 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1590 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1591 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1592 accelerator card for the Amiga 1200,
1593 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1594 Note that all of the above SCSI controllers, except for the builtin
1595 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1596 bus, so you also have to enable Zorro bus support if you want to use
1600 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1601 depends on ZORRO && SCSI && EXPERIMENTAL
1603 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1604 Y to this question. If you're in doubt about whether you have one,
1606 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1609 tristate "Atari native SCSI support"
1610 depends on ATARI && SCSI && BROKEN
1612 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1613 Falcon, ...) say Y to get it supported. Of course also, if you have
1614 a compatible SCSI controller (e.g. for Medusa).
1616 To compile this driver as a module, choose M here: the
1617 module will be called atari_scsi.
1619 This driver supports both styles of NCR integration into the
1620 system: the TT style (separate DMA), and the Falcon style (via
1621 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1622 in the Hades (without DMA).
1624 config ATARI_SCSI_TOSHIBA_DELAY
1625 bool "Long delays for Toshiba CD-ROMs"
1626 depends on ATARI_SCSI
1628 This option increases the delay after a SCSI arbitration to
1629 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1630 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1631 would impact performance a bit, so say N.
1633 config ATARI_SCSI_RESET_BOOT
1634 bool "Reset SCSI-devices at boottime"
1635 depends on ATARI_SCSI
1637 Reset the devices on your Atari whenever it boots. This makes the
1638 boot process fractionally longer but may assist recovery from errors
1639 that leave the devices with SCSI operations partway completed.
1642 bool "Hades SCSI DMA emulator"
1643 depends on ATARI_SCSI && HADES
1645 This option enables code which emulates the TT SCSI DMA chip on the
1646 Hades. This increases the SCSI transfer rates at least ten times
1647 compared to PIO transfers.
1650 bool "Macintosh NCR5380 SCSI"
1651 depends on MAC && SCSI
1653 This is the NCR 5380 SCSI controller included on most of the 68030
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>.
1659 tristate "Macintosh NCR53c9[46] SCSI"
1660 depends on MAC && SCSI
1662 This is the NCR 53c9x SCSI controller found on most of the 68040
1663 based Macintoshes. If you have one of these say Y and read the
1664 SCSI-HOWTO, available from
1665 <http://www.tldp.org/docs.html#howto>.
1667 To compile this driver as a module, choose M here: the
1668 module will be called mac_esp.
1671 bool "WD33C93 SCSI driver for MVME147"
1672 depends on MVME147 && SCSI
1674 Support for the on-board SCSI controller on the Motorola MVME147
1675 single-board computer.
1678 bool "NCR53C710 SCSI driver for MVME16x"
1679 depends on MVME16x && SCSI && BROKEN
1681 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1682 SCSI controller chip. Almost everyone using one of these boards
1683 will want to say Y to this question.
1685 config BVME6000_SCSI
1686 bool "NCR53C710 SCSI driver for BVME6000"
1687 depends on BVME6000 && SCSI && BROKEN
1689 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1690 SCSI controller chip. Almost everyone using one of these boards
1691 will want to say Y to this question.
1693 config SCSI_NCR53C7xx_FAST
1694 bool "allow FAST-SCSI [10MHz]"
1695 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1697 This will enable 10MHz FAST-SCSI transfers with your host
1698 adapter. Some systems have problems with that speed, so it's safest
1702 tristate "Sun3 NCR5380 SCSI"
1703 depends on SUN3 && SCSI
1705 This option will enable support for the OBIO (onboard io) NCR5380
1706 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1707 "Sun3" type VME scsi controllers also based on the NCR5380.
1708 General Linux information on the Sun 3 series (now discontinued)
1709 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1712 bool "Sun3x ESP SCSI"
1713 depends on SUN3X && SCSI
1715 The ESP was an on-board SCSI controller used on Sun 3/80
1716 machines. Say Y here to compile in support for it.
1719 tristate "Sparc ESP Scsi Driver"
1720 depends on SBUS && SCSI
1722 This is the driver for the Sun ESP SCSI host adapter. The ESP
1723 chipset is present in most SPARC SBUS-based computers.
1725 To compile this driver as a module, choose M here: the
1726 module will be called esp.
1728 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1731 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1732 depends on ARCH_S390 && SCSI
1734 If you want to access SCSI devices attached to your IBM eServer
1735 zSeries by means of Fibre Channel interfaces say Y.
1736 For details please refer to the documentation provided by IBM at
1737 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1739 This driver is also available as a module. This module will be
1740 called zfcp. If you want to compile it as a module, say M here
1741 and read Documentation/modules.txt.
1745 source "drivers/scsi/pcmcia/Kconfig"