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 SCSI host adapter.
269 Support Chip <ATP870 ATP876 ATP880 ATP885>
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"
317 depends on SCSI && PCI
319 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
321 config SCSI_AIC7XXX_OLD
322 tristate "Adaptec AIC7xxx support (old driver)"
323 depends on (ISA || EISA || PCI ) && SCSI
325 WARNING This driver is an older aic7xxx driver and is no longer
326 under active development. Adaptec, Inc. is writing a new driver to
327 take the place of this one, and it is recommended that whenever
328 possible, people should use the new Adaptec written driver instead
329 of this one. This driver will eventually be phased out entirely.
331 This is support for the various aic7xxx based Adaptec SCSI
332 controllers. These include the 274x EISA cards; 284x VLB cards;
333 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
334 motherboard based SCSI controllers from Adaptec. It does not support
335 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
336 support them. It does not support the 2920 cards from Adaptec that
337 use the Future Domain SCSI controller chip. For those cards, you
338 need the "Future Domain 16xx SCSI support" driver.
340 In general, if the controller is based on an Adaptec SCSI controller
341 chip from the aic777x series or the aic78xx series, this driver
342 should work. The only exception is the 7810 which is specifically
343 not supported (that's the RAID controller chip on the AAA-13x
346 Note that the AHA2920 SCSI host adapter is *not* supported by this
347 driver; choose "Future Domain 16xx SCSI support" instead if you have
350 Information on the configuration options for this controller can be
351 found by checking the help file for each of the available
352 configuration options. You should read
353 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
354 contacting the maintainer with any questions. The SCSI-HOWTO,
355 available from <http://www.tldp.org/docs.html#howto>, can also
358 To compile this driver as a module, choose M here: the
359 module will be called aic7xxx_old.
361 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
363 # All the I2O code and drivers do not seem to be 64bit safe.
365 tristate "Adaptec I2O RAID support "
366 depends on !64BIT && SCSI && PCI
368 This driver supports all of Adaptec's I2O based RAID controllers as
369 well as the DPT SmartRaid V cards. This is an Adaptec maintained
370 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
372 To compile this driver as a module, choose M here: the
373 module will be called dpt_i2o.
376 tristate "AdvanSys SCSI support"
377 depends on (ISA || EISA || PCI) && SCSI
379 This is a driver for all SCSI host adapters manufactured by
380 AdvanSys. It is documented in the kernel source in
381 <file:drivers/scsi/advansys.c>.
383 To compile this driver as a module, choose M here: the
384 module will be called advansys.
387 tristate "Always IN2000 SCSI support"
388 depends on ISA && SCSI
390 This is support for an ISA bus SCSI host adapter. You'll find more
391 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
392 out of the box, you may have to change the jumpers for IRQ or
395 To compile this driver as a module, choose M here: the
396 module will be called in2000.
398 source "drivers/scsi/megaraid/Kconfig.megaraid"
401 bool "Serial ATA (SATA) support"
404 This driver family supports Serial ATA host controllers
409 config SCSI_SATA_AHCI
410 tristate "AHCI SATA support"
411 depends on SCSI_SATA && PCI
413 This option enables support for AHCI Serial ATA.
418 tristate "ServerWorks Frodo / Apple K2 SATA support"
419 depends on SCSI_SATA && PCI
421 This option enables support for Broadcom/Serverworks/Apple K2
427 tristate "Intel PIIX/ICH SATA support"
428 depends on SCSI_SATA && PCI
430 This option enables support for ICH5 Serial ATA.
431 If PATA support was enabled previously, this enables
432 support for select Intel PIIX/ICH PATA host controllers.
437 tristate "NVIDIA SATA support"
438 depends on SCSI_SATA && PCI && EXPERIMENTAL
440 This option enables support for NVIDIA Serial ATA.
444 config SCSI_SATA_PROMISE
445 tristate "Promise SATA TX2/TX4 support"
446 depends on SCSI_SATA && PCI
448 This option enables support for Promise Serial ATA TX2/TX4.
453 tristate "Promise SATA SX4 support"
454 depends on SCSI_SATA && PCI && EXPERIMENTAL
456 This option enables support for Promise Serial ATA SX4.
461 tristate "Silicon Image SATA support"
462 depends on SCSI_SATA && PCI && EXPERIMENTAL
464 This option enables support for Silicon Image Serial ATA.
469 tristate "SiS 964/180 SATA support"
470 depends on SCSI_SATA && PCI && EXPERIMENTAL
472 This option enables support for SiS Serial ATA 964/180.
477 tristate "ULi Electronics SATA support"
478 depends on SCSI_SATA && PCI && EXPERIMENTAL
480 This option enables support for ULi Electronics SATA.
485 tristate "VIA SATA support"
486 depends on SCSI_SATA && PCI
488 This option enables support for VIA Serial ATA.
492 config SCSI_SATA_VITESSE
493 tristate "VITESSE VSC-7174 SATA support"
494 depends on SCSI_SATA && PCI
496 This option enables support for Vitesse VSC7174 Serial ATA.
501 tristate "BusLogic SCSI support"
502 depends on (PCI || ISA || MCA) && SCSI && (BROKEN || !SPARC64)
504 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
505 Adapters. Consult the SCSI-HOWTO, available from
506 <http://www.tldp.org/docs.html#howto>, and the files
507 <file:Documentation/scsi/BusLogic.txt> and
508 <file:Documentation/scsi/FlashPoint.txt> for more information.
510 To compile this driver as a module, choose M here: the
511 module will be called BusLogic.
513 config SCSI_OMIT_FLASHPOINT
514 bool "Omit FlashPoint support"
515 depends on SCSI_BUSLOGIC
517 This option allows you to omit the FlashPoint support from the
518 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
519 substantial, so users of MultiMaster Host Adapters may wish to omit
523 # This is marked broken because it uses over 4kB of stack in
525 # 2076 CpqTsProcessIMQEntry
529 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
530 depends on PCI && SCSI && BROKEN
532 Say Y here to compile in support for the Compaq StorageWorks Fibre
533 Channel 64-bit/66Mhz Host Bus Adapter.
536 tristate "DMX3191D SCSI support"
537 depends on PCI && SCSI
539 This is support for Domex DMX3191D SCSI Host Adapters.
541 To compile this driver as a module, choose M here: the
542 module will be called dmx3191d.
545 tristate "DTC3180/3280 SCSI support"
546 depends on ISA && SCSI
548 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
549 the SCSI-HOWTO, available from
550 <http://www.tldp.org/docs.html#howto>, and the file
551 <file:Documentation/scsi/dtc3x80.txt>.
553 To compile this driver as a module, choose M here: the
554 module will be called dtc.
557 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
558 depends on (ISA || EISA || PCI) && SCSI && (BROKEN || !SPARC64)
560 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
561 ISA and all EISA I/O addresses are probed looking for the "EATA"
562 signature. The addresses of all the PCI SCSI controllers reported
563 by the PCI subsystem are probed as well.
565 You want to read the start of <file:drivers/scsi/eata.c> and the
566 SCSI-HOWTO, available from
567 <http://www.tldp.org/docs.html#howto>.
569 To compile this driver as a module, choose M here: the
570 module will be called eata.
572 config SCSI_EATA_TAGGED_QUEUE
573 bool "enable tagged command queueing"
576 This is a feature of SCSI-2 which improves performance: the host
577 adapter can send several SCSI commands to a device's queue even if
578 previous commands haven't finished yet.
579 This is equivalent to the "eata=tc:y" boot option.
581 config SCSI_EATA_LINKED_COMMANDS
582 bool "enable elevator sorting"
585 This option enables elevator sorting for all probed SCSI disks and
586 CD-ROMs. It definitely reduces the average seek distance when doing
587 random seeks, but this does not necessarily result in a noticeable
588 performance improvement: your mileage may vary...
589 This is equivalent to the "eata=lc:y" boot option.
591 config SCSI_EATA_MAX_TAGS
592 int "maximum number of queued commands"
596 This specifies how many SCSI commands can be maximally queued for
597 each probed SCSI device. You should reduce the default value of 16
598 only if you have disks with buggy or limited tagged command support.
599 Minimum is 2 and maximum is 62. This value is also the window size
600 used by the elevator sorting option above. The effective value used
601 by the driver for each probed SCSI device is reported at boot time.
602 This is equivalent to the "eata=mq:8" boot option.
605 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
606 depends on (ISA || EISA || PCI) && SCSI
608 This driver supports all EATA-PIO protocol compliant SCSI Host
609 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
610 host adapters could also use this driver but are discouraged from
611 doing so, since this driver only supports hard disks and lacks
612 numerous features. You might want to have a look at the SCSI-HOWTO,
613 available from <http://www.tldp.org/docs.html#howto>.
615 To compile this driver as a module, choose M here: the
616 module will be called eata_pio.
618 config SCSI_FUTURE_DOMAIN
619 tristate "Future Domain 16xx SCSI/AHA-2920A support"
620 depends on (ISA || PCI) && SCSI
622 This is support for Future Domain's 16-bit SCSI host adapters
623 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
624 other adapters based on the Future Domain chipsets (Quantum
625 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
626 It is explained in section 3.7 of the SCSI-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>.
629 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
630 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
631 controller support"). This Future Domain driver works with the older
632 Adaptec AHA-2920A boards with a Future Domain chip on them.
634 To compile this driver as a module, choose M here: the
635 module will be called fdomain.
638 tristate "Future Domain MCS-600/700 SCSI support"
639 depends on MCA_LEGACY && SCSI
641 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
642 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
643 is identical to the MCS 700 and hence also supported by this driver.
644 This driver also supports the Reply SB16/SCSI card (the SCSI part).
645 It supports multiple adapters in the same system.
647 To compile this driver as a module, choose M here: the
648 module will be called fd_mcs.
651 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
652 depends on (ISA || EISA || PCI) && SCSI && (BROKEN || !SPARC64)
654 Formerly called GDT SCSI Disk Array Controller Support.
656 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
657 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
658 in the kernel source in <file:drivers/scsi/gdth.c> and
659 <file:drivers/scsi/gdth.h.>
661 To compile this driver as a module, choose M here: the
662 module will be called gdth.
664 config SCSI_GENERIC_NCR5380
665 tristate "Generic NCR5380/53c400 SCSI PIO support"
666 depends on ISA && SCSI
668 This is a driver for the old NCR 53c80 series of SCSI controllers
669 on boards using PIO. Most boards such as the Trantor T130 fit this
670 category, along with a large number of ISA 8bit controllers shipped
671 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
672 you should select the specific driver for that card rather than
673 generic 5380 support.
675 It is explained in section 3.8 of the SCSI-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
677 of the box, you may have to change some settings in
678 <file:drivers/scsi/g_NCR5380.h>.
680 To compile this driver as a module, choose M here: the
681 module will be called g_NCR5380.
683 config SCSI_GENERIC_NCR5380_MMIO
684 tristate "Generic NCR5380/53c400 SCSI MMIO support"
685 depends on ISA && SCSI
687 This is a driver for the old NCR 53c80 series of SCSI controllers
688 on boards using memory mapped I/O.
689 It is explained in section 3.8 of the SCSI-HOWTO, available from
690 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
691 of the box, you may have to change some settings in
692 <file:drivers/scsi/g_NCR5380.h>.
694 To compile this driver as a module, choose M here: the
695 module will be called g_NCR5380_mmio.
697 config SCSI_GENERIC_NCR53C400
698 bool "Enable NCR53c400 extensions"
699 depends on SCSI_GENERIC_NCR5380
701 This enables certain optimizations for the NCR53c400 SCSI cards.
702 You might as well try it out. Note that this driver will only probe
703 for the Trantor T130B in its default configuration; you might have
704 to pass a command line option to the kernel at boot time if it does
705 not detect your card. See the file
706 <file:Documentation/scsi/g_NCR5380.txt> for details.
709 tristate "IBMMCA SCSI support"
710 depends on MCA_LEGACY && SCSI
712 This is support for the IBM SCSI adapter found in many of the PS/2
713 series computers. These machines have an MCA bus, so you need to
714 answer Y to "MCA support" as well and read
715 <file:Documentation/mca.txt>.
717 If the adapter isn't found during boot (a common problem for models
718 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
719 option, where <pun> is the id of the SCSI subsystem (usually 7, but
720 if that doesn't work check your reference diskette). Owners of
721 model 95 with a LED-matrix-display can in addition activate some
722 activity info like under OS/2, but more informative, by setting
723 'ibmmcascsi=display' as an additional kernel parameter. Try "man
724 bootparam" or see the documentation of your boot loader about how to
725 pass options to the kernel.
727 To compile this driver as a module, choose M here: the
728 module will be called ibmmca.
730 config IBMMCA_SCSI_ORDER_STANDARD
731 bool "Standard SCSI-order"
732 depends on SCSI_IBMMCA
734 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
735 are assigned to the drive letters, starting with the lowest SCSI-id
736 (physical number -- pun) to be drive C:, as seen from DOS and
737 similar operating systems. When looking into papers describing the
738 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
739 The SCSI-standard follows a hardware-hierarchy which says that id 7
740 has the highest priority and id 0 the lowest. Therefore, the host
741 adapters are still today everywhere placed as SCSI-id 7 by default.
742 In the SCSI-standard, the drive letters express the priority of the
743 disk. C: should be the hard disk, or a partition on it, with the
744 highest priority. This must therefore be the disk with the highest
745 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
746 original definition of the SCSI-standard as also industrial- and
747 process-control-machines, like VME-CPUs running under realtime-OSes
748 (e.g. LynxOS, OS9) do.
750 If you like to run Linux on your MCA-machine with the same
751 assignment of hard disks as seen from e.g. DOS or OS/2 on your
752 machine, which is in addition conformant to the SCSI-standard, you
753 must say Y here. This is also necessary for MCA-Linux users who want
754 to keep downward compatibility to older releases of the
755 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
758 If you like to have the lowest SCSI-id assigned as drive C:, as
759 modern SCSI-BIOSes do, which does not conform to the standard, but
760 is widespread and common in the PC-world of today, you must say N
761 here. If unsure, say Y.
763 config IBMMCA_SCSI_DEV_RESET
764 bool "Reset SCSI-devices at boottime"
765 depends on SCSI_IBMMCA
767 By default, SCSI-devices are reset when the machine is powered on.
768 However, some devices exist, like special-control-devices,
769 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
770 not reset when switched on. If you say Y here, each device connected
771 to your SCSI-bus will be issued a reset-command after it has been
772 probed, while the kernel is booting. This may cause problems with
773 more modern devices, like hard disks, which do not appreciate these
774 reset commands, and can cause your system to hang. So say Y only if
775 you know that one of your older devices needs it; N is the safe
779 tristate "IBM ServeRAID support"
780 depends on PCI && SCSI
782 This is support for the IBM ServeRAID hardware RAID controllers.
783 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
784 for more information. If this driver does not work correctly
785 without modification please contact the author by email at
786 ipslinux@adaptec.com.
788 To compile this driver as a module, choose M here: the
789 module will be called ips.
792 tristate "IBM Virtual SCSI support"
793 depends on PPC_PSERIES || PPC_ISERIES
795 This is the IBM POWER Virtual SCSI Client
797 To compile this driver as a module, choose M here: the
798 module will be called ibmvscsic.
801 tristate "Initio 9100U(W) support"
802 depends on PCI && SCSI
804 This is support for the Initio 91XXU(W) SCSI host adapter. Please
805 read the SCSI-HOWTO, available from
806 <http://www.tldp.org/docs.html#howto>.
808 To compile this driver as a module, choose M here: the
809 module will be called initio.
812 tristate "Initio INI-A100U2W support"
813 depends on PCI && SCSI
815 This is support for the Initio INI-A100U2W SCSI host adapter.
816 Please read the SCSI-HOWTO, available from
817 <http://www.tldp.org/docs.html#howto>.
819 To compile this driver as a module, choose M here: the
820 module will be called a100u2w.
823 tristate "IOMEGA parallel port (ppa - older drives)"
824 depends on SCSI && PARPORT
826 This driver supports older versions of IOMEGA's parallel port ZIP
827 drive (a 100 MB removable media device).
829 Note that you can say N here if you have the SCSI version of the ZIP
830 drive: it will be supported automatically if you said Y to the
831 generic "SCSI disk support", above.
833 If you have the ZIP Plus drive or a more recent parallel port ZIP
834 drive (if the supplied cable with the drive is labeled "AutoDetect")
835 then you should say N here and Y to "IOMEGA parallel port (imm -
836 newer drives)", below.
838 For more information about this driver and how to use it you should
839 read the file <file:Documentation/scsi/ppa.txt>. You should also read
840 the SCSI-HOWTO, which is available from
841 <http://www.tldp.org/docs.html#howto>. If you use this driver,
842 you will still be able to use the parallel port for other tasks,
843 such as a printer; it is safe to compile both drivers into the
846 To compile this driver as a module, choose M here: the
847 module will be called ppa.
850 tristate "IOMEGA parallel port (imm - newer drives)"
851 depends on SCSI && PARPORT
853 This driver supports newer versions of IOMEGA's parallel port ZIP
854 drive (a 100 MB removable media device).
856 Note that you can say N here if you have the SCSI version of the ZIP
857 drive: it will be supported automatically if you said Y to the
858 generic "SCSI disk support", above.
860 If you have the ZIP Plus drive or a more recent parallel port ZIP
861 drive (if the supplied cable with the drive is labeled "AutoDetect")
862 then you should say Y here; if you have an older ZIP drive, say N
863 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
865 For more information about this driver and how to use it you should
866 read the file <file:Documentation/scsi/ppa.txt>. You should also read
867 the SCSI-HOWTO, which is available from
868 <http://www.tldp.org/docs.html#howto>. If you use this driver,
869 you will still be able to use the parallel port for other tasks,
870 such as a printer; it is safe to compile both drivers into the
873 To compile this driver as a module, choose M here: the
874 module will be called imm.
876 config SCSI_IZIP_EPP16
877 bool "ppa/imm option - Use slow (but safe) EPP-16"
878 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
880 EPP (Enhanced Parallel Port) is a standard for parallel ports which
881 allows them to act as expansion buses that can handle up to 64
884 Some parallel port chipsets are slower than their motherboard, and
885 so we have to control the state of the chipset's FIFO queue every
886 now and then to avoid data loss. This will be done if you say Y
889 Generally, saying Y is the safe option and slows things down a bit.
891 config SCSI_IZIP_SLOW_CTR
892 bool "ppa/imm option - Assume slow parport control register"
893 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
895 Some parallel ports are known to have excessive delays between
896 changing the parallel port control register and good data being
897 available on the parallel port data/status register. This option
898 forces a small delay (1.0 usec to be exact) after changing the
899 control register to let things settle out. Enabling this option may
900 result in a big drop in performance but some very old parallel ports
901 (found in 386 vintage machines) will not work properly.
903 Generally, saying N is fine.
905 config SCSI_NCR53C406A
906 tristate "NCR53c406a SCSI support"
907 depends on ISA && SCSI
909 This is support for the NCR53c406a SCSI host adapter. For user
910 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
911 in the kernel source. Also read the SCSI-HOWTO, available from
912 <http://www.tldp.org/docs.html#howto>.
914 To compile this driver as a module, choose M here: the
915 module will be called NCR53c406.
918 tristate "NCR Dual 700 MCA SCSI support"
919 depends on MCA && SCSI
920 select SCSI_SPI_ATTRS
922 This is a driver for the MicroChannel Dual 700 card produced by
923 NCR and commonly used in 345x/35xx/4100 class machines. It always
924 tries to negotiate sync and uses tag command queueing.
926 Unless you have an NCR manufactured machine, the chances are that
927 you do not have this SCSI card, so say N.
929 config 53C700_IO_MAPPED
931 depends on SCSI_NCR_D700
935 tristate "HP Lasi SCSI support for 53c700/710"
936 depends on GSC && SCSI
937 select SCSI_SPI_ATTRS
939 This is a driver for the SCSI controller in the Lasi chip found in
940 many PA-RISC workstations & servers. If you do not know whether you
941 have a Lasi chip, it is safe to say "Y" here.
943 config 53C700_MEM_MAPPED
945 depends on SCSI_LASI700
948 config 53C700_LE_ON_BE
950 depends on SCSI_LASI700
953 config SCSI_SYM53C8XX_2
954 tristate "SYM53C8XX Version 2 SCSI support"
955 depends on PCI && SCSI
956 select SCSI_SPI_ATTRS
958 This driver supports the whole NCR53C8XX/SYM53C8XX family of
959 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
960 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
961 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
962 controllers; you need to use the Fusion MPT driver for that.
964 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
967 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
968 int "DMA addressing mode"
969 depends on SCSI_SYM53C8XX_2
972 This option only applies to PCI-SCSI chips that are PCI DAC
973 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
975 When set to 0, the driver will program the chip to only perform
976 32-bit DMA. When set to 1, the chip will be able to perform DMA
977 to addresses up to 1TB. When set to 2, the driver supports the
978 full 64-bit DMA address range, but can only address 16 segments
979 of 4 GB each. This limits the total addressable range to 64 GB.
981 Most machines with less than 4GB of memory should use a setting
982 of 0 for best performance. If your machine has 4GB of memory
983 or more, you should set this option to 1 (the default).
985 The still experimental value 2 (64 bit DMA addressing with 16
986 x 4GB segments limitation) can be used on systems that require
987 PCI address bits past bit 39 to be set for the addressing of
988 memory using PCI DAC cycles.
990 config SCSI_SYM53C8XX_DEFAULT_TAGS
991 int "default tagged command queue depth"
992 depends on SCSI_SYM53C8XX_2
995 This is the default value of the command queue depth the
996 driver will announce to the generic SCSI layer for devices
997 that support tagged command queueing. This value can be changed
998 from the boot command line. This is a soft limit that cannot
999 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1001 config SCSI_SYM53C8XX_MAX_TAGS
1002 int "maximum number of queued commands"
1003 depends on SCSI_SYM53C8XX_2
1006 This option allows you to specify the maximum number of commands
1007 that can be queued to any device, when tagged command queuing is
1008 possible. The driver supports up to 256 queued commands per device.
1009 This value is used as a compiled-in hard limit.
1011 config SCSI_SYM53C8XX_IOMAPPED
1013 depends on SCSI_SYM53C8XX_2
1015 If you say Y here, the driver will use port IO to access
1016 the card. This is significantly slower then using memory
1017 mapped IO. Most people should answer N.
1020 tristate "IBM Power Linux RAID adapter support"
1021 depends on PCI && SCSI
1024 This driver supports the IBM Power Linux family RAID adapters.
1025 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1026 as IBM iSeries 5702, 5703, 5709, and 570A.
1028 config SCSI_IPR_TRACE
1029 bool "enable driver internal trace"
1032 If you say Y here, the driver will trace all commands issued
1033 to the adapter. Performance impact is minimal. Trace can be
1034 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1036 config SCSI_IPR_DUMP
1037 bool "enable adapter dump support"
1040 If you say Y here, the driver will support adapter crash dump.
1041 If you enable this support, the iprdump daemon can be used
1042 to capture adapter failure analysis information.
1045 tristate "Zalon SCSI support"
1046 depends on GSC && SCSI
1047 select SCSI_SPI_ATTRS
1049 The Zalon is a GSC/HSC bus interface chip that sits between the
1050 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1051 C110, J200, J210 and some D, K & R-class machines. It's also
1052 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1053 Say Y here if you have one of these machines or cards.
1055 config SCSI_NCR_Q720
1056 tristate "NCR Quad 720 MCA SCSI support"
1057 depends on MCA && SCSI
1058 select SCSI_SPI_ATTRS
1060 This is a driver for the MicroChannel Quad 720 card produced by
1061 NCR and commonly used in 345x/35xx/4100 class machines. It always
1062 tries to negotiate sync and uses tag command queueing.
1064 Unless you have an NCR manufactured machine, the chances are that
1065 you do not have this SCSI card, so say N.
1067 config SCSI_NCR53C8XX_DEFAULT_TAGS
1068 int " default tagged command queue depth"
1069 depends on SCSI_ZALON || SCSI_NCR_Q720
1072 "Tagged command queuing" is a feature of SCSI-2 which improves
1073 performance: the host adapter can send several SCSI commands to a
1074 device's queue even if previous commands haven't finished yet.
1075 Because the device is intelligent, it can optimize its operations
1076 (like head positioning) based on its own request queue. Some SCSI
1077 devices don't implement this properly; if you want to disable this
1078 feature, enter 0 or 1 here (it doesn't matter which).
1080 The default value is 8 and should be supported by most hard disks.
1081 This value can be overridden from the boot command line using the
1082 'tags' option as follows (example):
1083 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1084 4, set queue depth to 16 for target 2 and target 3 on controller 0
1085 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1087 The normal answer therefore is to go with the default 8 and to use
1088 a boot command line option for devices that need to use a different
1089 command queue depth.
1091 There is no safe option other than using good SCSI devices.
1093 config SCSI_NCR53C8XX_MAX_TAGS
1094 int " maximum number of queued commands"
1095 depends on SCSI_ZALON || SCSI_NCR_Q720
1098 This option allows you to specify the maximum number of commands
1099 that can be queued to any device, when tagged command queuing is
1100 possible. The default value is 32. Minimum is 2, maximum is 64.
1101 Modern hard disks are able to support 64 tags and even more, but
1102 do not seem to be faster when more than 32 tags are being used.
1104 So, the normal answer here is to go with the default value 32 unless
1105 you are using very large hard disks with large cache (>= 1 MB) that
1106 are able to take advantage of more than 32 tagged commands.
1108 There is no safe option and the default answer is recommended.
1110 config SCSI_NCR53C8XX_SYNC
1111 int " synchronous transfers frequency in MHz"
1112 depends on SCSI_ZALON || SCSI_NCR_Q720
1115 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1116 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1117 are respectively the maximum data transfer rates in mega-transfers
1118 per second for each class. For example, a FAST-20 Wide 16 device is
1119 able to transfer data at 20 million 16 bit packets per second for a
1120 total rate of 40 MB/s.
1122 You may specify 0 if you want to only use asynchronous data
1123 transfers. This is the safest and slowest option. Otherwise, specify
1124 a value between 5 and 80, depending on the capability of your SCSI
1125 controller. The higher the number, the faster the data transfer.
1126 Note that 80 should normally be ok since the driver decreases the
1127 value automatically according to the controller's capabilities.
1129 Your answer to this question is ignored for controllers with NVRAM,
1130 since the driver will get this information from the user set-up. It
1131 also can be overridden using a boot setup option, as follows
1132 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1133 for FAST-20 synchronous data transfer (20 mega-transfers per
1136 The normal answer therefore is not to go with the default but to
1137 select the maximum value 80 allowing the driver to use the maximum
1138 value supported by each controller. If this causes problems with
1139 your SCSI devices, you should come back and decrease the value.
1141 There is no safe option other than using good cabling, right
1142 terminations and SCSI conformant devices.
1144 config SCSI_NCR53C8XX_PROFILE
1145 bool " enable profiling"
1146 depends on SCSI_ZALON || SCSI_NCR_Q720
1148 This option allows you to enable profiling information gathering.
1149 These statistics are not very accurate due to the low frequency
1150 of the kernel clock (100 Hz on i386) and have performance impact
1151 on systems that use very fast devices.
1153 The normal answer therefore is N.
1155 config SCSI_NCR53C8XX_NO_DISCONNECT
1156 bool " not allow targets to disconnect"
1157 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1159 This option is only provided for safety if you suspect some SCSI
1160 device of yours to not support properly the target-disconnect
1161 feature. In that case, you would say Y here. In general however, to
1162 not allow targets to disconnect is not reasonable if there is more
1163 than 1 device on a SCSI bus. The normal answer therefore is N.
1165 config SCSI_MCA_53C9X
1166 tristate "NCR MCA 53C9x SCSI support"
1167 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1169 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1170 controller based on the NCR 53C94. This driver will allow use of
1171 the controller on the 3550, and very possibly others.
1173 To compile this driver as a module, choose M here: the
1174 module will be called mca_53c9x.
1177 tristate "PAS16 SCSI support"
1178 depends on ISA && SCSI
1180 This is support for a SCSI host adapter. It is explained in section
1181 3.10 of the SCSI-HOWTO, available from
1182 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1183 of the box, you may have to change some settings in
1184 <file:drivers/scsi/pas16.h>.
1186 To compile this driver as a module, choose M here: the
1187 module will be called pas16.
1190 tristate "PCI2000 support"
1191 depends on PCI && SCSI && BROKEN
1193 This is support for the PCI2000I EIDE interface card which acts as a
1194 SCSI host adapter. Please read the SCSI-HOWTO, available from
1195 <http://www.tldp.org/docs.html#howto>.
1197 To compile this driver as a module, choose M here: the
1198 module will be called pci2000.
1200 config SCSI_PCI2220I
1201 tristate "PCI2220i support"
1202 depends on PCI && SCSI && BROKEN
1204 This is support for the PCI2220i EIDE interface card which acts as a
1205 SCSI host adapter. Please read the SCSI-HOWTO, available from
1206 <http://www.tldp.org/docs.html#howto>.
1208 To compile this driver as a module, choose M here: the
1209 module will be called pci2220i.
1212 tristate "PSI240i support"
1213 depends on ISA && SCSI
1215 This is support for the PSI240i EIDE interface card which acts as a
1216 SCSI host adapter. Please read the SCSI-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here: the
1220 module will be called psi240i.
1222 config SCSI_QLOGIC_FAS
1223 tristate "Qlogic FAS SCSI support"
1224 depends on ISA && SCSI
1226 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1227 FastSCSI! cards as well as any other card based on the FASXX chip
1228 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1230 This driver does NOT support the PCI versions of these cards. The
1231 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1232 SCSI support"), below.
1234 Information about this driver is contained in
1235 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1236 SCSI-HOWTO, available from
1237 <http://www.tldp.org/docs.html#howto>.
1239 To compile this driver as a module, choose M here: the
1240 module will be called qlogicfas.
1242 config SCSI_QLOGIC_ISP
1243 tristate "Qlogic ISP SCSI support (old driver)"
1244 depends on PCI && SCSI
1246 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1247 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1248 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1250 If you say Y here, make sure to choose "BIOS" at the question "PCI
1253 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1254 should also read the SCSI-HOWTO, available from
1255 <http://www.tldp.org/docs.html#howto>.
1257 To compile this driver as a module, choose M here: the
1258 module will be called qlogicisp.
1260 These days the hardware is also supported by the more modern qla1280
1261 driver. In doubt use that one instead of qlogicisp.
1263 config SCSI_QLOGIC_FC
1264 tristate "Qlogic ISP FC SCSI support"
1265 depends on PCI && SCSI
1267 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1269 To compile this driver as a module, choose M here: the
1270 module will be called qlogicfc.
1272 config SCSI_QLOGIC_FC_FIRMWARE
1273 bool "Include loadable firmware in driver"
1274 depends on SCSI_QLOGIC_FC
1276 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1277 expanded LUN addressing and FcTape (FCP-2) support, in the
1278 qlogicfc driver. This is required on some platforms.
1280 config SCSI_QLOGIC_1280
1281 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1282 depends on PCI && SCSI
1284 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1286 To compile this driver as a module, choose M here: the
1287 module will be called qla1280.
1289 config SCSI_QLOGIC_1280_1040
1290 bool "Qlogic QLA 1020/1040 SCSI support"
1291 depends on SCSI_QLOGIC_1280 && SCSI_QLOGIC_ISP!=y
1293 Say Y here if you have a QLogic ISP1020/1040 SCSI host adapter and
1294 do not want to use the old driver. This option enables support in
1295 the qla1280 driver for those host adapters.
1297 config SCSI_QLOGICPTI
1298 tristate "PTI Qlogic, ISP Driver"
1299 depends on SBUS && SCSI
1301 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1302 controllers are known under Solaris as qpti and in the openprom as
1303 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1304 driven by a different driver.
1306 To compile this driver as a module, choose M here: the
1307 module will be called qlogicpti.
1309 source "drivers/scsi/qla2xxx/Kconfig"
1312 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1313 depends on X86 && ISA && SCSI && BROKEN
1315 These are 8-bit SCSI controllers; the ST-01 is also supported by
1316 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1317 available from <http://www.tldp.org/docs.html#howto>. If it
1318 doesn't work out of the box, you may have to change some settings in
1319 <file:drivers/scsi/seagate.h>.
1321 To compile this driver as a module, choose M here: the
1322 module will be called seagate.
1324 # definitely looks not 64bit safe:
1326 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1327 depends on (EISA || MCA) && SCSI
1328 select SCSI_SPI_ATTRS
1330 This driver for NCR53c710 based SCSI host adapters.
1332 It currently supports Compaq EISA cards and NCR MCA cards
1334 config 53C700_IO_MAPPED
1336 depends on SCSI_SIM710
1339 config SCSI_SYM53C416
1340 tristate "Symbios 53c416 SCSI support"
1341 depends on ISA && SCSI
1343 This is support for the sym53c416 SCSI host adapter, the SCSI
1344 adapter that comes with some HP scanners. This driver requires that
1345 the sym53c416 is configured first using some sort of PnP
1346 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1347 are using isapnp then you need to compile this driver as a module
1348 and then load it using insmod after isapnp has run. The parameters
1349 of the configured card(s) should be passed to the driver. The format
1352 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1354 To compile this driver as a module, choose M here: the
1355 module will be called sym53c416.
1358 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1359 depends on PCI && SCSI && EXPERIMENTAL
1361 This driver supports PCI SCSI host adapters based on the ASIC
1362 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1364 This driver works, but is still in experimental status. So better
1365 have a bootable disk and a backup in case of emergency.
1367 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1369 To compile this driver as a module, choose M here: the
1370 module will be called dc395x.
1373 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1374 depends on PCI && SCSI
1376 This driver supports PCI SCSI host adapters based on the Am53C974A
1377 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1378 PCscsi/PCnet (Am53/79C974) solutions.
1380 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1382 Note that this driver does NOT support Tekram DC390W/U/F, which are
1383 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1385 To compile this driver as a module, choose M here: the
1386 module will be called tmscsim.
1389 tristate "Trantor T128/T128F/T228 SCSI support"
1390 depends on ISA && SCSI
1392 This is support for a SCSI host adapter. It is explained in section
1393 3.11 of the SCSI-HOWTO, available from
1394 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1395 of the box, you may have to change some settings in
1396 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1397 Adaptec, and some former Trantor products are being sold under the
1400 To compile this driver as a module, choose M here: the
1401 module will be called t128.
1404 tristate "UltraStor 14F/34F support"
1405 depends on ISA && SCSI
1407 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1408 The source at <file:drivers/scsi/u14-34f.c> contains some
1409 information about this hardware. If the driver doesn't work out of
1410 the box, you may have to change some settings in
1411 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1412 <http://www.tldp.org/docs.html#howto>. Note that there is also
1413 another driver for the same hardware: "UltraStor SCSI support",
1414 below. You should say Y to both only if you want 24F support as
1417 To compile this driver as a module, choose M here: the
1418 module will be called u14-34f.
1420 config SCSI_U14_34F_TAGGED_QUEUE
1421 bool "enable tagged command queueing"
1422 depends on SCSI_U14_34F
1424 This is a feature of SCSI-2 which improves performance: the host
1425 adapter can send several SCSI commands to a device's queue even if
1426 previous commands haven't finished yet.
1427 This is equivalent to the "u14-34f=tc:y" boot option.
1429 config SCSI_U14_34F_LINKED_COMMANDS
1430 bool "enable elevator sorting"
1431 depends on SCSI_U14_34F
1433 This option enables elevator sorting for all probed SCSI disks and
1434 CD-ROMs. It definitely reduces the average seek distance when doing
1435 random seeks, but this does not necessarily result in a noticeable
1436 performance improvement: your mileage may vary...
1437 This is equivalent to the "u14-34f=lc:y" boot option.
1439 config SCSI_U14_34F_MAX_TAGS
1440 int "maximum number of queued commands"
1441 depends on SCSI_U14_34F
1444 This specifies how many SCSI commands can be maximally queued for
1445 each probed SCSI device. You should reduce the default value of 8
1446 only if you have disks with buggy or limited tagged command support.
1447 Minimum is 2 and maximum is 14. This value is also the window size
1448 used by the elevator sorting option above. The effective value used
1449 by the driver for each probed SCSI device is reported at boot time.
1450 This is equivalent to the "u14-34f=mq:8" boot option.
1452 config SCSI_ULTRASTOR
1453 tristate "UltraStor SCSI support"
1454 depends on X86 && ISA && SCSI
1456 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1457 adapter family. This driver is explained in section 3.12 of the
1458 SCSI-HOWTO, available from
1459 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1460 of the box, you may have to change some settings in
1461 <file:drivers/scsi/ultrastor.h>.
1463 Note that there is also another driver for the same hardware:
1464 "UltraStor 14F/34F support", above.
1466 To compile this driver as a module, choose M here: the
1467 module will be called ultrastor.
1470 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1471 depends on PCI && SCSI && !64BIT
1473 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1474 SCSI host adapter. Please read the SCSI-HOWTO, available from
1475 <http://www.tldp.org/docs.html#howto>.
1477 To compile this driver as a module, choose M here: the
1478 module will be called nsp32.
1481 tristate "SCSI debugging host simulator"
1484 This is a host adapter simulator that can simulate multiple hosts
1485 each with multiple dummy SCSI devices (disks). It defaults to one
1486 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1487 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1488 dummy disks are simulated, they share the same kernel RAM for
1489 their storage. See http://www.torque.net/sg/sdebug.html for more
1490 information. This driver is primarily of use to those testing the
1491 SCSI and block subsystems. If unsure, say N.
1494 tristate "MESH (Power Mac internal SCSI) support"
1495 depends on PPC32 && PPC_PMAC && SCSI
1497 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1498 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1499 other Power Macintoshes do). Say Y to include support for this SCSI
1502 To compile this driver as a module, choose M here: the
1503 module will be called mesh.
1505 config SCSI_MESH_SYNC_RATE
1506 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1507 depends on SCSI_MESH
1510 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1511 drives a bus which is entirely internal to the machine (such as the
1512 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1513 operation at up to 10 MB/s. On machines where the SCSI bus
1514 controlled by the MESH can have external devices connected, it is
1515 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1516 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1517 to disable synchronous operation.
1519 config SCSI_MESH_RESET_DELAY_MS
1520 int "initial bus reset delay (ms) (0 = no reset)"
1521 depends on SCSI_MESH
1524 config SCSI_MAC53C94
1525 tristate "53C94 (Power Mac external SCSI) support"
1526 depends on PPC32 && PPC_PMAC && SCSI
1528 On Power Macintoshes (and clones) with two SCSI buses, the external
1529 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1530 machines which only have one SCSI bus, such as the 7200, also use
1531 the 53C94. Say Y to include support for the 53C94.
1533 To compile this driver as a module, choose M here: the
1534 module will be called mac53c94.
1536 source "drivers/scsi/arm/Kconfig"
1539 bool "MIPS JAZZ FAS216 SCSI support"
1540 depends on MACH_JAZZ && SCSI
1542 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1543 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1547 tristate "A3000 WD33C93A support"
1548 depends on AMIGA && SCSI
1550 If you have an Amiga 3000 and have SCSI devices connected to the
1551 built-in SCSI controller, say Y. Otherwise, say N.
1553 To compile this driver as a module, choose M here: the
1554 module will be called wd33c93.
1557 tristate "A2091/A590 WD33C93A support"
1558 depends on ZORRO && SCSI
1560 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1563 To compile this driver as a module, choose M here: the
1564 module will be called wd33c93.
1567 tristate "GVP Series II WD33C93A support"
1568 depends on ZORRO && SCSI
1570 If you have a Great Valley Products Series II SCSI controller,
1571 answer Y. Also say Y if you have a later model of GVP SCSI
1572 controller (such as the GVP A4008 or a Combo board). Otherwise,
1573 answer N. This driver does NOT work for the T-Rex series of
1574 accelerators from TekMagic and GVP-M.
1576 To compile this driver as a module, choose M here: the
1577 module will be called gvp11.
1579 config CYBERSTORM_SCSI
1580 tristate "CyberStorm SCSI support"
1581 depends on ZORRO && SCSI
1583 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1584 accelerator board and the optional Cyberstorm SCSI controller,
1585 answer Y. Otherwise, say N.
1587 config CYBERSTORMII_SCSI
1588 tristate "CyberStorm Mk II SCSI support"
1589 depends on ZORRO && SCSI
1591 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1592 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1596 tristate "Blizzard 2060 SCSI support"
1597 depends on ZORRO && SCSI
1599 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1600 and want to use the onboard SCSI controller, say Y. Otherwise,
1604 tristate "Blizzard 1230IV/1260 SCSI support"
1605 depends on ZORRO && SCSI
1607 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1608 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1611 config FASTLANE_SCSI
1612 tristate "Fastlane SCSI support"
1613 depends on ZORRO && SCSI
1615 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1616 one in the near future, say Y to this question. Otherwise, say N.
1618 config SCSI_AMIGA7XX
1619 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1620 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1622 Support for various NCR53c710-based SCSI controllers on the Amiga.
1624 - the builtin SCSI controller on the Amiga 4000T,
1625 - the Amiga 4091 Zorro III SCSI-2 controller,
1626 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1628 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1629 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1630 accelerator card for the Amiga 1200,
1631 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1632 Note that all of the above SCSI controllers, except for the builtin
1633 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1634 bus, so you also have to enable Zorro bus support if you want to use
1638 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1639 depends on ZORRO && SCSI && EXPERIMENTAL
1641 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1642 Y to this question. If you're in doubt about whether you have one,
1644 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1647 tristate "Atari native SCSI support"
1648 depends on ATARI && SCSI && BROKEN
1650 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1651 Falcon, ...) say Y to get it supported. Of course also, if you have
1652 a compatible SCSI controller (e.g. for Medusa).
1654 To compile this driver as a module, choose M here: the
1655 module will be called atari_scsi.
1657 This driver supports both styles of NCR integration into the
1658 system: the TT style (separate DMA), and the Falcon style (via
1659 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1660 in the Hades (without DMA).
1662 config ATARI_SCSI_TOSHIBA_DELAY
1663 bool "Long delays for Toshiba CD-ROMs"
1664 depends on ATARI_SCSI
1666 This option increases the delay after a SCSI arbitration to
1667 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1668 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1669 would impact performance a bit, so say N.
1671 config ATARI_SCSI_RESET_BOOT
1672 bool "Reset SCSI-devices at boottime"
1673 depends on ATARI_SCSI
1675 Reset the devices on your Atari whenever it boots. This makes the
1676 boot process fractionally longer but may assist recovery from errors
1677 that leave the devices with SCSI operations partway completed.
1680 bool "Hades SCSI DMA emulator"
1681 depends on ATARI_SCSI && HADES
1683 This option enables code which emulates the TT SCSI DMA chip on the
1684 Hades. This increases the SCSI transfer rates at least ten times
1685 compared to PIO transfers.
1688 bool "Macintosh NCR5380 SCSI"
1689 depends on MAC && SCSI
1691 This is the NCR 5380 SCSI controller included on most of the 68030
1692 based Macintoshes. If you have one of these say Y and read the
1693 SCSI-HOWTO, available from
1694 <http://www.tldp.org/docs.html#howto>.
1697 tristate "Macintosh NCR53c9[46] SCSI"
1698 depends on MAC && SCSI
1700 This is the NCR 53c9x SCSI controller found on most of the 68040
1701 based Macintoshes. If you have one of these say Y and read the
1702 SCSI-HOWTO, available from
1703 <http://www.tldp.org/docs.html#howto>.
1705 To compile this driver as a module, choose M here: the
1706 module will be called mac_esp.
1709 bool "WD33C93 SCSI driver for MVME147"
1710 depends on MVME147 && SCSI
1712 Support for the on-board SCSI controller on the Motorola MVME147
1713 single-board computer.
1716 bool "NCR53C710 SCSI driver for MVME16x"
1717 depends on MVME16x && SCSI && BROKEN
1719 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1720 SCSI controller chip. Almost everyone using one of these boards
1721 will want to say Y to this question.
1723 config BVME6000_SCSI
1724 bool "NCR53C710 SCSI driver for BVME6000"
1725 depends on BVME6000 && SCSI && BROKEN
1727 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1728 SCSI controller chip. Almost everyone using one of these boards
1729 will want to say Y to this question.
1731 config SCSI_NCR53C7xx_FAST
1732 bool "allow FAST-SCSI [10MHz]"
1733 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1735 This will enable 10MHz FAST-SCSI transfers with your host
1736 adapter. Some systems have problems with that speed, so it's safest
1740 tristate "Sun3 NCR5380 SCSI"
1741 depends on SUN3 && SCSI
1743 This option will enable support for the OBIO (onboard io) NCR5380
1744 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1745 "Sun3" type VME scsi controllers also based on the NCR5380.
1746 General Linux information on the Sun 3 series (now discontinued)
1747 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1750 bool "Sun3x ESP SCSI"
1751 depends on SUN3X && SCSI
1753 The ESP was an on-board SCSI controller used on Sun 3/80
1754 machines. Say Y here to compile in support for it.
1757 tristate "Sparc ESP Scsi Driver"
1758 depends on SBUS && SCSI
1760 This is the driver for the Sun ESP SCSI host adapter. The ESP
1761 chipset is present in most SPARC SBUS-based computers.
1763 To compile this driver as a module, choose M here: the
1764 module will be called esp.
1766 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1769 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1770 depends on ARCH_S390 && QDIO && SCSI
1771 select SCSI_FC_ATTRS
1773 If you want to access SCSI devices attached to your IBM eServer
1774 zSeries by means of Fibre Channel interfaces say Y.
1775 For details please refer to the documentation provided by IBM at
1776 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1778 This driver is also available as a module. This module will be
1779 called zfcp. If you want to compile it as a module, say M here
1780 and read Documentation/modules.txt.
1784 source "drivers/scsi/pcmcia/Kconfig"