1 menu "SCSI device support"
4 tristate "RAID Transport Class"
10 tristate "SCSI device support"
12 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
13 any other SCSI device under Linux, say Y and make sure that you know
14 the name of your SCSI host adapter (the card inside your computer
15 that "speaks" the SCSI protocol, also called SCSI controller),
16 because you will be asked for it.
18 You also need to say Y here if you have a device which speaks
19 the SCSI protocol. Examples of this include the parallel port
20 version of the IOMEGA ZIP drive, USB storage devices, Fibre
21 Channel, FireWire storage and the IDE-SCSI emulation driver.
23 To compile this driver as a module, choose M here and read
24 <file:Documentation/scsi/scsi.txt>.
25 The module will be called scsi_mod.
27 However, do not compile this as a module if your root file system
28 (the one containing the directory /) is located on a SCSI device.
31 bool "legacy /proc/scsi/ support"
32 depends on SCSI && PROC_FS
35 This option enables support for the various files in
36 /proc/scsi. In Linux 2.6 this has been superceeded by
37 files in sysfs but many legacy applications rely on this.
41 comment "SCSI support type (disk, tape, CD-ROM)"
45 tristate "SCSI disk support"
48 If you want to use SCSI hard disks, Fibre Channel disks,
49 USB storage or the SCSI or parallel port version of
50 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
51 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
52 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
55 To compile this driver as a module, choose M here and read
56 <file:Documentation/scsi/scsi.txt>.
57 The module will be called sd_mod.
59 Do not compile this driver as a module if your root file system
60 (the one containing the directory /) is located on a SCSI disk.
61 In this case, do not compile the driver for your SCSI host adapter
62 (below) as a module either.
65 tristate "SCSI tape support"
68 If you want to use a SCSI tape drive under Linux, say Y and read the
69 SCSI-HOWTO, available from
70 <http://www.tldp.org/docs.html#howto>, and
71 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
74 To compile this driver as a module, choose M here and read
75 <file:Documentation/scsi/scsi.txt>. The module will be called st.
78 tristate "SCSI OnStream SC-x0 tape support"
81 The OnStream SC-x0 SCSI tape drives can not be driven by the
82 standard st driver, but instead need this special osst driver and
83 use the /dev/osstX char device nodes (major 206). Via usb-storage
84 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
85 as well. Note that there is also a second generation of OnStream
86 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
87 tapes (QIC-157) and can be driven by the standard driver st.
88 For more information, you may have a look at the SCSI-HOWTO
89 <http://www.tldp.org/docs.html#howto> and
90 <file:Documentation/scsi/osst.txt> in the kernel source.
91 More info on the OnStream driver may be found on
92 <http://linux1.onstream.nl/test/>
93 Please also have a look at the standard st docu, as most of it
94 applies to osst as well.
96 To compile this driver as a module, choose M here and read
97 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
100 tristate "SCSI CDROM support"
103 If you want to use a SCSI or FireWire CD-ROM under Linux,
104 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
105 <http://www.tldp.org/docs.html#howto>. Also make sure to say
106 Y or M to "ISO 9660 CD-ROM file system support" later.
108 To compile this driver as a module, choose M here and read
109 <file:Documentation/scsi/scsi.txt>.
110 The module will be called sr_mod.
112 config BLK_DEV_SR_VENDOR
113 bool "Enable vendor-specific extensions (for SCSI CDROM)"
114 depends on BLK_DEV_SR
116 This enables the usage of vendor specific SCSI commands. This is
117 required to support multisession CDs with old NEC/TOSHIBA cdrom
118 drives (and HP Writers). If you have such a drive and get the first
119 session only, try saying Y here; everybody else says N.
122 tristate "SCSI generic support"
125 If you want to use SCSI scanners, synthesizers or CD-writers or just
126 about anything having "SCSI" in its name other than hard disks,
127 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
128 directly, so you need some additional software which knows how to
129 talk to these devices using the SCSI protocol:
131 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
132 writer software look at Cdrtools
133 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
134 and for burning a "disk at once": CDRDAO
135 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
136 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
137 For other devices, it's possible that you'll have to write the
138 driver software yourself. Please read the file
139 <file:Documentation/scsi/scsi-generic.txt> for more information.
141 To compile this driver as a module, choose M here and read
142 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
147 tristate "SCSI media changer support"
150 This is a driver for SCSI media changers. Most common devices are
151 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
152 don't need this for those tiny 6-slot cdrom changers. Media
153 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
154 If you have such hardware and want to use it with linux, say Y
155 here. Check <file:Documentation/scsi-changer.txt> for details.
157 If you want to compile this as a module ( = code which can be
158 inserted in and removed from the running kernel whenever you want),
159 say M here and read <file:Documentation/modules.txt> and
160 <file:Documentation/scsi.txt>. The module will be called ch.o.
164 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
167 config SCSI_MULTI_LUN
168 bool "Probe all LUNs on each SCSI device"
171 If you have a SCSI device that supports more than one LUN (Logical
172 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
173 can say Y here to force the SCSI driver to probe for multiple LUNs.
174 A SCSI device with multiple LUNs acts logically like multiple SCSI
175 devices. The vast majority of SCSI devices have only one LUN, and
176 so most people can say N here. The max_luns boot/module parameter
177 allows to override this setting.
179 config SCSI_CONSTANTS
180 bool "Verbose SCSI error reporting (kernel size +=12K)"
183 The error messages regarding your SCSI hardware will be easier to
184 understand if you say Y here; it will enlarge your kernel by about
185 12 KB. If in doubt, say Y.
188 bool "SCSI logging facility"
191 This turns on a logging facility that can be used to debug a number
192 of SCSI related problems.
194 If you say Y here, no logging output will appear by default, but you
195 can enable logging by saying Y to "/proc file system support" and
196 "Sysctl support" below and executing the command
198 echo "scsi log token [level]" > /proc/scsi/scsi
200 at boot time after the /proc file system has been mounted.
202 There are a number of things that can be used for 'token' (you can
203 find them in the source: <file:drivers/scsi/scsi.c>), and this
204 allows you to select the types of information you want, and the
205 level allows you to select the level of verbosity.
207 If you say N here, it may be harder to track down some types of SCSI
208 problems. If you say Y here your kernel will be somewhat larger, but
209 there should be no noticeable performance impact as long as you have
212 menu "SCSI Transport Attributes"
215 config SCSI_SPI_ATTRS
216 tristate "Parallel SCSI (SPI) Transport Attributes"
219 If you wish to export transport-specific information about
220 each attached SCSI device to sysfs, say Y. Otherwise, say N.
223 tristate "FiberChannel Transport Attributes"
226 If you wish to export transport-specific information about
227 each attached FiberChannel device to sysfs, say Y.
230 config SCSI_ISCSI_ATTRS
231 tristate "iSCSI Transport Attributes"
232 depends on SCSI && NET
234 If you wish to export transport-specific information about
235 each attached iSCSI device to sysfs, say Y.
238 config SCSI_SAS_ATTRS
239 tristate "SAS Transport Attributes"
242 If you wish to export transport-specific information about
243 each attached SAS device to sysfs, say Y.
247 menu "SCSI low-level drivers"
251 tristate "iSCSI Initiator over TCP/IP"
252 depends on SCSI && INET
256 select SCSI_ISCSI_ATTRS
258 The iSCSI Driver provides a host with the ability to access storage
259 through an IP network. The driver uses the iSCSI protocol to transport
260 SCSI requests and responses over a TCP/IP network between the host
261 (the "initiator") and "targets". Architecturally, the iSCSI driver
262 combines with the host's TCP/IP stack, network drivers, and Network
263 Interface Card (NIC) to provide the same functions as a SCSI or a
264 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
266 To compile this driver as a module, choose M here: the
267 module will be called iscsi_tcp.
269 The userspace component needed to initialize the driver, documentation,
270 and sample configuration files can be found here:
272 http://linux-iscsi.sf.net
275 tristate "SGI WD93C93 SCSI Driver"
276 depends on SGI_IP22 && SCSI
278 If you have a Western Digital WD93 SCSI controller on
279 an SGI MIPS system, say Y. Otherwise, say N.
282 tristate "DEC NCR53C94 Scsi Driver"
283 depends on MACH_DECSTATION && SCSI && TC
285 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
286 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
289 tristate "DEC SII Scsi Driver"
290 depends on MACH_DECSTATION && SCSI && 32BIT
292 config BLK_DEV_3W_XXXX_RAID
293 tristate "3ware 5/6/7/8xxx ATA-RAID support"
294 depends on PCI && SCSI
296 3ware is the only hardware ATA-Raid product in Linux to date.
297 This card is 2,4, or 8 channel master mode support only.
298 SCSI support required!!!
300 <http://www.3ware.com/>
302 Please read the comments at the top of
303 <file:drivers/scsi/3w-xxxx.c>.
306 tristate "3ware 9xxx SATA-RAID support"
307 depends on PCI && SCSI
309 This driver supports the 9000 series 3ware SATA-RAID cards.
311 <http://www.amcc.com>
313 Please read the comments at the top of
314 <file:drivers/scsi/3w-9xxx.c>.
316 config SCSI_7000FASST
317 tristate "7000FASST SCSI support"
318 depends on ISA && SCSI && ISA_DMA_API
320 This driver supports the Western Digital 7000 SCSI host adapter
321 family. Some information is in the source:
322 <file:drivers/scsi/wd7000.c>.
324 To compile this driver as a module, choose M here: the
325 module will be called wd7000.
328 tristate "ACARD SCSI support"
329 depends on PCI && SCSI
331 This driver supports the ACARD SCSI host adapter.
332 Support Chip <ATP870 ATP876 ATP880 ATP885>
333 To compile this driver as a module, choose M here: the
334 module will be called atp870u.
337 tristate "Adaptec AHA152X/2825 support"
338 depends on ISA && SCSI && !64BIT
339 select SCSI_SPI_ATTRS
341 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
342 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
343 must be manually specified in this case.
345 It is explained in section 3.3 of the SCSI-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>. You might also want to
347 read the file <file:Documentation/scsi/aha152x.txt>.
349 To compile this driver as a module, choose M here: the
350 module will be called aha152x.
353 tristate "Adaptec AHA1542 support"
354 depends on ISA && SCSI && ISA_DMA_API
356 This is support for a SCSI host adapter. It is explained in section
357 3.4 of the SCSI-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
359 purchased by Adaptec, and some former Trantor products are being
360 sold under the Adaptec name. If it doesn't work out of the box, you
361 may have to change some settings in <file:drivers/scsi/aha1542.h>.
363 To compile this driver as a module, choose M here: the
364 module will be called aha1542.
367 tristate "Adaptec AHA1740 support"
368 depends on EISA && SCSI
370 This is support for a SCSI host adapter. It is explained in section
371 3.5 of the SCSI-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
373 of the box, you may have to change some settings in
374 <file:drivers/scsi/aha1740.h>.
376 To compile this driver as a module, choose M here: the
377 module will be called aha1740.
380 tristate "Adaptec AACRAID support"
381 depends on SCSI && PCI
383 This driver supports a variety of Dell, HP, Adaptec, IBM and
384 ICP storage products. For a list of supported products, refer
385 to <file:Documentation/scsi/aacraid.txt>.
387 To compile this driver as a module, choose M here: the module
388 will be called aacraid.
391 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
393 config SCSI_AIC7XXX_OLD
394 tristate "Adaptec AIC7xxx support (old driver)"
395 depends on (ISA || EISA || PCI ) && SCSI
397 WARNING This driver is an older aic7xxx driver and is no longer
398 under active development. Adaptec, Inc. is writing a new driver to
399 take the place of this one, and it is recommended that whenever
400 possible, people should use the new Adaptec written driver instead
401 of this one. This driver will eventually be phased out entirely.
403 This is support for the various aic7xxx based Adaptec SCSI
404 controllers. These include the 274x EISA cards; 284x VLB cards;
405 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
406 motherboard based SCSI controllers from Adaptec. It does not support
407 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
408 support them. It does not support the 2920 cards from Adaptec that
409 use the Future Domain SCSI controller chip. For those cards, you
410 need the "Future Domain 16xx SCSI support" driver.
412 In general, if the controller is based on an Adaptec SCSI controller
413 chip from the aic777x series or the aic78xx series, this driver
414 should work. The only exception is the 7810 which is specifically
415 not supported (that's the RAID controller chip on the AAA-13x
418 Note that the AHA2920 SCSI host adapter is *not* supported by this
419 driver; choose "Future Domain 16xx SCSI support" instead if you have
422 Information on the configuration options for this controller can be
423 found by checking the help file for each of the available
424 configuration options. You should read
425 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
426 contacting the maintainer with any questions. The SCSI-HOWTO,
427 available from <http://www.tldp.org/docs.html#howto>, can also
430 To compile this driver as a module, choose M here: the
431 module will be called aic7xxx_old.
433 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
435 # All the I2O code and drivers do not seem to be 64bit safe.
437 tristate "Adaptec I2O RAID support "
438 depends on !64BIT && SCSI && PCI
440 This driver supports all of Adaptec's I2O based RAID controllers as
441 well as the DPT SmartRaid V cards. This is an Adaptec maintained
442 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
444 To compile this driver as a module, choose M here: the
445 module will be called dpt_i2o.
448 tristate "AdvanSys SCSI support"
450 depends on ISA || EISA || PCI
451 depends on BROKEN || X86_32
453 This is a driver for all SCSI host adapters manufactured by
454 AdvanSys. It is documented in the kernel source in
455 <file:drivers/scsi/advansys.c>.
457 To compile this driver as a module, choose M here: the
458 module will be called advansys.
461 tristate "Always IN2000 SCSI support"
462 depends on ISA && SCSI
464 This is support for an ISA bus SCSI host adapter. You'll find more
465 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
466 out of the box, you may have to change the jumpers for IRQ or
469 To compile this driver as a module, choose M here: the
470 module will be called in2000.
472 source "drivers/scsi/megaraid/Kconfig.megaraid"
475 tristate "HighPoint RocketRAID 3xxx Controller support"
476 depends on SCSI && PCI
478 This option enables support for HighPoint RocketRAID 3xxx
481 To compile this driver as a module, choose M here; the module
482 will be called hptiop. If unsure, say N.
485 tristate "BusLogic SCSI support"
486 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
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 tristate "DMX3191D SCSI support"
508 depends on PCI && SCSI
509 select SCSI_SPI_ATTRS
511 This is support for Domex DMX3191D SCSI Host Adapters.
513 To compile this driver as a module, choose M here: the
514 module will be called dmx3191d.
517 tristate "DTC3180/3280 SCSI support"
518 depends on ISA && SCSI
519 select SCSI_SPI_ATTRS
521 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
522 the SCSI-HOWTO, available from
523 <http://www.tldp.org/docs.html#howto>, and the file
524 <file:Documentation/scsi/dtc3x80.txt>.
526 To compile this driver as a module, choose M here: the
527 module will be called dtc.
530 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
531 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
533 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
534 ISA and all EISA I/O addresses are probed looking for the "EATA"
535 signature. The addresses of all the PCI SCSI controllers reported
536 by the PCI subsystem are probed as well.
538 You want to read the start of <file:drivers/scsi/eata.c> and the
539 SCSI-HOWTO, available from
540 <http://www.tldp.org/docs.html#howto>.
542 To compile this driver as a module, choose M here: the
543 module will be called eata.
545 config SCSI_EATA_TAGGED_QUEUE
546 bool "enable tagged command queueing"
549 This is a feature of SCSI-2 which improves performance: the host
550 adapter can send several SCSI commands to a device's queue even if
551 previous commands haven't finished yet.
552 This is equivalent to the "eata=tc:y" boot option.
554 config SCSI_EATA_LINKED_COMMANDS
555 bool "enable elevator sorting"
558 This option enables elevator sorting for all probed SCSI disks and
559 CD-ROMs. It definitely reduces the average seek distance when doing
560 random seeks, but this does not necessarily result in a noticeable
561 performance improvement: your mileage may vary...
562 This is equivalent to the "eata=lc:y" boot option.
564 config SCSI_EATA_MAX_TAGS
565 int "maximum number of queued commands"
569 This specifies how many SCSI commands can be maximally queued for
570 each probed SCSI device. You should reduce the default value of 16
571 only if you have disks with buggy or limited tagged command support.
572 Minimum is 2 and maximum is 62. This value is also the window size
573 used by the elevator sorting option above. The effective value used
574 by the driver for each probed SCSI device is reported at boot time.
575 This is equivalent to the "eata=mq:8" boot option.
578 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
579 depends on (ISA || EISA || PCI) && SCSI && BROKEN
581 This driver supports all EATA-PIO protocol compliant SCSI Host
582 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
583 host adapters could also use this driver but are discouraged from
584 doing so, since this driver only supports hard disks and lacks
585 numerous features. You might want to have a look at the SCSI-HOWTO,
586 available from <http://www.tldp.org/docs.html#howto>.
588 To compile this driver as a module, choose M here: the
589 module will be called eata_pio.
591 config SCSI_FUTURE_DOMAIN
592 tristate "Future Domain 16xx SCSI/AHA-2920A support"
593 depends on (ISA || PCI) && SCSI
595 This is support for Future Domain's 16-bit SCSI host adapters
596 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
597 other adapters based on the Future Domain chipsets (Quantum
598 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
599 It is explained in section 3.7 of the SCSI-HOWTO, available from
600 <http://www.tldp.org/docs.html#howto>.
602 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
603 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
604 controller support"). This Future Domain driver works with the older
605 Adaptec AHA-2920A boards with a Future Domain chip on them.
607 To compile this driver as a module, choose M here: the
608 module will be called fdomain.
611 tristate "Future Domain MCS-600/700 SCSI support"
612 depends on MCA_LEGACY && SCSI
614 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
615 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
616 is identical to the MCS 700 and hence also supported by this driver.
617 This driver also supports the Reply SB16/SCSI card (the SCSI part).
618 It supports multiple adapters in the same system.
620 To compile this driver as a module, choose M here: the
621 module will be called fd_mcs.
624 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
625 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
627 Formerly called GDT SCSI Disk Array Controller Support.
629 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
630 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
631 in the kernel source in <file:drivers/scsi/gdth.c> and
632 <file:drivers/scsi/gdth.h.>
634 To compile this driver as a module, choose M here: the
635 module will be called gdth.
637 config SCSI_GENERIC_NCR5380
638 tristate "Generic NCR5380/53c400 SCSI PIO support"
639 depends on ISA && SCSI
640 select SCSI_SPI_ATTRS
642 This is a driver for the old NCR 53c80 series of SCSI controllers
643 on boards using PIO. Most boards such as the Trantor T130 fit this
644 category, along with a large number of ISA 8bit controllers shipped
645 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
646 you should select the specific driver for that card rather than
647 generic 5380 support.
649 It is explained in section 3.8 of the SCSI-HOWTO, available from
650 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
651 of the box, you may have to change some settings in
652 <file:drivers/scsi/g_NCR5380.h>.
654 To compile this driver as a module, choose M here: the
655 module will be called g_NCR5380.
657 config SCSI_GENERIC_NCR5380_MMIO
658 tristate "Generic NCR5380/53c400 SCSI MMIO support"
659 depends on ISA && SCSI
660 select SCSI_SPI_ATTRS
662 This is a driver for the old NCR 53c80 series of SCSI controllers
663 on boards using memory mapped I/O.
664 It is explained in section 3.8 of the SCSI-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
666 of the box, you may have to change some settings in
667 <file:drivers/scsi/g_NCR5380.h>.
669 To compile this driver as a module, choose M here: the
670 module will be called g_NCR5380_mmio.
672 config SCSI_GENERIC_NCR53C400
673 bool "Enable NCR53c400 extensions"
674 depends on SCSI_GENERIC_NCR5380
676 This enables certain optimizations for the NCR53c400 SCSI cards.
677 You might as well try it out. Note that this driver will only probe
678 for the Trantor T130B in its default configuration; you might have
679 to pass a command line option to the kernel at boot time if it does
680 not detect your card. See the file
681 <file:Documentation/scsi/g_NCR5380.txt> for details.
684 tristate "IBMMCA SCSI support"
685 depends on MCA_LEGACY && SCSI
687 This is support for the IBM SCSI adapter found in many of the PS/2
688 series computers. These machines have an MCA bus, so you need to
689 answer Y to "MCA support" as well and read
690 <file:Documentation/mca.txt>.
692 If the adapter isn't found during boot (a common problem for models
693 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
694 option, where <pun> is the id of the SCSI subsystem (usually 7, but
695 if that doesn't work check your reference diskette). Owners of
696 model 95 with a LED-matrix-display can in addition activate some
697 activity info like under OS/2, but more informative, by setting
698 'ibmmcascsi=display' as an additional kernel parameter. Try "man
699 bootparam" or see the documentation of your boot loader about how to
700 pass options to the kernel.
702 To compile this driver as a module, choose M here: the
703 module will be called ibmmca.
705 config IBMMCA_SCSI_ORDER_STANDARD
706 bool "Standard SCSI-order"
707 depends on SCSI_IBMMCA
709 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
710 are assigned to the drive letters, starting with the lowest SCSI-id
711 (physical number -- pun) to be drive C:, as seen from DOS and
712 similar operating systems. When looking into papers describing the
713 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
714 The SCSI-standard follows a hardware-hierarchy which says that id 7
715 has the highest priority and id 0 the lowest. Therefore, the host
716 adapters are still today everywhere placed as SCSI-id 7 by default.
717 In the SCSI-standard, the drive letters express the priority of the
718 disk. C: should be the hard disk, or a partition on it, with the
719 highest priority. This must therefore be the disk with the highest
720 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
721 original definition of the SCSI-standard as also industrial- and
722 process-control-machines, like VME-CPUs running under realtime-OSes
723 (e.g. LynxOS, OS9) do.
725 If you like to run Linux on your MCA-machine with the same
726 assignment of hard disks as seen from e.g. DOS or OS/2 on your
727 machine, which is in addition conformant to the SCSI-standard, you
728 must say Y here. This is also necessary for MCA-Linux users who want
729 to keep downward compatibility to older releases of the
730 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
733 If you like to have the lowest SCSI-id assigned as drive C:, as
734 modern SCSI-BIOSes do, which does not conform to the standard, but
735 is widespread and common in the PC-world of today, you must say N
736 here. If unsure, say Y.
738 config IBMMCA_SCSI_DEV_RESET
739 bool "Reset SCSI-devices at boottime"
740 depends on SCSI_IBMMCA
742 By default, SCSI-devices are reset when the machine is powered on.
743 However, some devices exist, like special-control-devices,
744 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
745 not reset when switched on. If you say Y here, each device connected
746 to your SCSI-bus will be issued a reset-command after it has been
747 probed, while the kernel is booting. This may cause problems with
748 more modern devices, like hard disks, which do not appreciate these
749 reset commands, and can cause your system to hang. So say Y only if
750 you know that one of your older devices needs it; N is the safe
754 tristate "IBM ServeRAID support"
755 depends on PCI && SCSI
757 This is support for the IBM ServeRAID hardware RAID controllers.
758 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
759 for more information. If this driver does not work correctly
760 without modification please contact the author by email at
761 <ipslinux@adaptec.com>.
763 To compile this driver as a module, choose M here: the
764 module will be called ips.
767 tristate "IBM Virtual SCSI support"
768 depends on PPC_PSERIES || PPC_ISERIES
770 This is the IBM POWER Virtual SCSI Client
772 To compile this driver as a module, choose M here: the
773 module will be called ibmvscsic.
776 tristate "Initio 9100U(W) support"
777 depends on PCI && SCSI
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_PC
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_PC
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 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 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.
905 tristate "HP Lasi SCSI support for 53c700/710"
906 depends on GSC && SCSI
907 select SCSI_SPI_ATTRS
909 This is a driver for the SCSI controller in the Lasi chip found in
910 many PA-RISC workstations & servers. If you do not know whether you
911 have a Lasi chip, it is safe to say "Y" here.
913 config 53C700_LE_ON_BE
915 depends on SCSI_LASI700
918 config SCSI_SYM53C8XX_2
919 tristate "SYM53C8XX Version 2 SCSI support"
920 depends on PCI && SCSI
921 select SCSI_SPI_ATTRS
923 This driver supports the whole NCR53C8XX/SYM53C8XX family of
924 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
925 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
926 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
927 controllers; you need to use the Fusion MPT driver for that.
929 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
932 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
933 int "DMA addressing mode"
934 depends on SCSI_SYM53C8XX_2
937 This option only applies to PCI-SCSI chips that are PCI DAC
938 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
940 When set to 0, the driver will program the chip to only perform
941 32-bit DMA. When set to 1, the chip will be able to perform DMA
942 to addresses up to 1TB. When set to 2, the driver supports the
943 full 64-bit DMA address range, but can only address 16 segments
944 of 4 GB each. This limits the total addressable range to 64 GB.
946 Most machines with less than 4GB of memory should use a setting
947 of 0 for best performance. If your machine has 4GB of memory
948 or more, you should set this option to 1 (the default).
950 The still experimental value 2 (64 bit DMA addressing with 16
951 x 4GB segments limitation) can be used on systems that require
952 PCI address bits past bit 39 to be set for the addressing of
953 memory using PCI DAC cycles.
955 config SCSI_SYM53C8XX_DEFAULT_TAGS
956 int "Default tagged command queue depth"
957 depends on SCSI_SYM53C8XX_2
960 This is the default value of the command queue depth the
961 driver will announce to the generic SCSI layer for devices
962 that support tagged command queueing. This value can be changed
963 from the boot command line. This is a soft limit that cannot
964 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
966 config SCSI_SYM53C8XX_MAX_TAGS
967 int "Maximum number of queued commands"
968 depends on SCSI_SYM53C8XX_2
971 This option allows you to specify the maximum number of commands
972 that can be queued to any device, when tagged command queuing is
973 possible. The driver supports up to 256 queued commands per device.
974 This value is used as a compiled-in hard limit.
976 config SCSI_SYM53C8XX_MMIO
977 bool "Use memory mapped IO"
978 depends on SCSI_SYM53C8XX_2
981 Memory mapped IO is faster than Port IO. Most people should
982 answer Y here, but some machines may have problems. If you have
983 to answer N here, please report the problem to the maintainer.
986 tristate "IBM Power Linux RAID adapter support"
987 depends on PCI && SCSI
990 This driver supports the IBM Power Linux family RAID adapters.
991 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
992 as IBM iSeries 5702, 5703, 5709, and 570A.
994 config SCSI_IPR_TRACE
995 bool "enable driver internal trace"
998 If you say Y here, the driver will trace all commands issued
999 to the adapter. Performance impact is minimal. Trace can be
1000 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1002 config SCSI_IPR_DUMP
1003 bool "enable adapter dump support"
1006 If you say Y here, the driver will support adapter crash dump.
1007 If you enable this support, the iprdump daemon can be used
1008 to capture adapter failure analysis information.
1011 tristate "Zalon SCSI support"
1012 depends on GSC && SCSI
1013 select SCSI_SPI_ATTRS
1015 The Zalon is a GSC/HSC bus interface chip that sits between the
1016 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1017 C110, J200, J210 and some D, K & R-class machines. It's also
1018 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1019 Say Y here if you have one of these machines or cards.
1021 config SCSI_NCR_Q720
1022 tristate "NCR Quad 720 MCA SCSI support"
1023 depends on MCA && SCSI
1024 select SCSI_SPI_ATTRS
1026 This is a driver for the MicroChannel Quad 720 card produced by
1027 NCR and commonly used in 345x/35xx/4100 class machines. It always
1028 tries to negotiate sync and uses tag command queueing.
1030 Unless you have an NCR manufactured machine, the chances are that
1031 you do not have this SCSI card, so say N.
1033 config SCSI_NCR53C8XX_DEFAULT_TAGS
1034 int "default tagged command queue depth"
1035 depends on SCSI_ZALON || SCSI_NCR_Q720
1038 "Tagged command queuing" is a feature of SCSI-2 which improves
1039 performance: the host adapter can send several SCSI commands to a
1040 device's queue even if previous commands haven't finished yet.
1041 Because the device is intelligent, it can optimize its operations
1042 (like head positioning) based on its own request queue. Some SCSI
1043 devices don't implement this properly; if you want to disable this
1044 feature, enter 0 or 1 here (it doesn't matter which).
1046 The default value is 8 and should be supported by most hard disks.
1047 This value can be overridden from the boot command line using the
1048 'tags' option as follows (example):
1049 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1050 4, set queue depth to 16 for target 2 and target 3 on controller 0
1051 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1053 The normal answer therefore is to go with the default 8 and to use
1054 a boot command line option for devices that need to use a different
1055 command queue depth.
1057 There is no safe option other than using good SCSI devices.
1059 config SCSI_NCR53C8XX_MAX_TAGS
1060 int "maximum number of queued commands"
1061 depends on SCSI_ZALON || SCSI_NCR_Q720
1064 This option allows you to specify the maximum number of commands
1065 that can be queued to any device, when tagged command queuing is
1066 possible. The default value is 32. Minimum is 2, maximum is 64.
1067 Modern hard disks are able to support 64 tags and even more, but
1068 do not seem to be faster when more than 32 tags are being used.
1070 So, the normal answer here is to go with the default value 32 unless
1071 you are using very large hard disks with large cache (>= 1 MB) that
1072 are able to take advantage of more than 32 tagged commands.
1074 There is no safe option and the default answer is recommended.
1076 config SCSI_NCR53C8XX_SYNC
1077 int "synchronous transfers frequency in MHz"
1078 depends on SCSI_ZALON || SCSI_NCR_Q720
1081 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1082 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1083 are respectively the maximum data transfer rates in mega-transfers
1084 per second for each class. For example, a FAST-20 Wide 16 device is
1085 able to transfer data at 20 million 16 bit packets per second for a
1086 total rate of 40 MB/s.
1088 You may specify 0 if you want to only use asynchronous data
1089 transfers. This is the safest and slowest option. Otherwise, specify
1090 a value between 5 and 80, depending on the capability of your SCSI
1091 controller. The higher the number, the faster the data transfer.
1092 Note that 80 should normally be ok since the driver decreases the
1093 value automatically according to the controller's capabilities.
1095 Your answer to this question is ignored for controllers with NVRAM,
1096 since the driver will get this information from the user set-up. It
1097 also can be overridden using a boot setup option, as follows
1098 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1099 for FAST-20 synchronous data transfer (20 mega-transfers per
1102 The normal answer therefore is not to go with the default but to
1103 select the maximum value 80 allowing the driver to use the maximum
1104 value supported by each controller. If this causes problems with
1105 your SCSI devices, you should come back and decrease the value.
1107 There is no safe option other than using good cabling, right
1108 terminations and SCSI conformant devices.
1110 config SCSI_NCR53C8XX_PROFILE
1111 bool "enable profiling"
1112 depends on SCSI_ZALON || SCSI_NCR_Q720
1114 This option allows you to enable profiling information gathering.
1115 These statistics are not very accurate due to the low frequency
1116 of the kernel clock (100 Hz on i386) and have performance impact
1117 on systems that use very fast devices.
1119 The normal answer therefore is N.
1121 config SCSI_NCR53C8XX_NO_DISCONNECT
1122 bool "not allow targets to disconnect"
1123 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1125 This option is only provided for safety if you suspect some SCSI
1126 device of yours to not support properly the target-disconnect
1127 feature. In that case, you would say Y here. In general however, to
1128 not allow targets to disconnect is not reasonable if there is more
1129 than 1 device on a SCSI bus. The normal answer therefore is N.
1131 config SCSI_MCA_53C9X
1132 tristate "NCR MCA 53C9x SCSI support"
1133 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1135 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1136 controller based on the NCR 53C94. This driver will allow use of
1137 the controller on the 3550, and very possibly others.
1139 To compile this driver as a module, choose M here: the
1140 module will be called mca_53c9x.
1143 tristate "PAS16 SCSI support"
1144 depends on ISA && SCSI
1145 select SCSI_SPI_ATTRS
1147 This is support for a SCSI host adapter. It is explained in section
1148 3.10 of the SCSI-HOWTO, available from
1149 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1150 of the box, you may have to change some settings in
1151 <file:drivers/scsi/pas16.h>.
1153 To compile this driver as a module, choose M here: the
1154 module will be called pas16.
1157 tristate "PSI240i support"
1158 depends on ISA && SCSI
1160 This is support for the PSI240i EIDE interface card which acts as a
1161 SCSI host adapter. Please read the SCSI-HOWTO, available from
1162 <http://www.tldp.org/docs.html#howto>.
1164 To compile this driver as a module, choose M here: the
1165 module will be called psi240i.
1167 config SCSI_QLOGIC_FAS
1168 tristate "Qlogic FAS SCSI support"
1169 depends on ISA && SCSI
1171 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1172 FastSCSI! cards as well as any other card based on the FASXX chip
1173 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1175 This driver does NOT support the PCI versions of these cards. The
1176 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1177 SCSI support"), below.
1179 Information about this driver is contained in
1180 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1181 SCSI-HOWTO, available from
1182 <http://www.tldp.org/docs.html#howto>.
1184 To compile this driver as a module, choose M here: the
1185 module will be called qlogicfas.
1187 config SCSI_QLOGIC_FC_FIRMWARE
1188 bool "Include loadable firmware in driver"
1189 depends on SCSI_QLOGIC_FC
1191 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1192 expanded LUN addressing and FcTape (FCP-2) support, in the
1193 qlogicfc driver. This is required on some platforms.
1195 config SCSI_QLOGIC_1280
1196 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1197 depends on PCI && SCSI
1199 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1201 To compile this driver as a module, choose M here: the
1202 module will be called qla1280.
1204 config SCSI_QLOGICPTI
1205 tristate "PTI Qlogic, ISP Driver"
1206 depends on SBUS && SCSI
1208 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1209 controllers are known under Solaris as qpti and in the openprom as
1210 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1211 driven by a different driver.
1213 To compile this driver as a module, choose M here: the
1214 module will be called qlogicpti.
1216 source "drivers/scsi/qla2xxx/Kconfig"
1219 tristate "Emulex LightPulse Fibre Channel Support"
1220 depends on PCI && SCSI
1221 select SCSI_FC_ATTRS
1223 This lpfc driver supports the Emulex LightPulse
1224 Family of Fibre Channel PCI host adapters.
1227 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1228 depends on X86 && ISA && SCSI && BROKEN
1230 These are 8-bit SCSI controllers; the ST-01 is also supported by
1231 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1232 available from <http://www.tldp.org/docs.html#howto>. If it
1233 doesn't work out of the box, you may have to change some settings in
1234 <file:drivers/scsi/seagate.h>.
1236 To compile this driver as a module, choose M here: the
1237 module will be called seagate.
1239 # definitely looks not 64bit safe:
1241 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1242 depends on (EISA || MCA) && SCSI
1243 select SCSI_SPI_ATTRS
1245 This driver for NCR53c710 based SCSI host adapters.
1247 It currently supports Compaq EISA cards and NCR MCA cards
1249 config 53C700_IO_MAPPED
1251 depends on SCSI_SIM710
1254 config SCSI_SYM53C416
1255 tristate "Symbios 53c416 SCSI support"
1256 depends on ISA && SCSI
1258 This is support for the sym53c416 SCSI host adapter, the SCSI
1259 adapter that comes with some HP scanners. This driver requires that
1260 the sym53c416 is configured first using some sort of PnP
1261 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1262 are using isapnp then you need to compile this driver as a module
1263 and then load it using insmod after isapnp has run. The parameters
1264 of the configured card(s) should be passed to the driver. The format
1267 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1269 To compile this driver as a module, choose M here: the
1270 module will be called sym53c416.
1273 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1274 depends on PCI && SCSI && EXPERIMENTAL
1276 This driver supports PCI SCSI host adapters based on the ASIC
1277 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1279 This driver works, but is still in experimental status. So better
1280 have a bootable disk and a backup in case of emergency.
1282 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1284 To compile this driver as a module, choose M here: the
1285 module will be called dc395x.
1288 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1289 depends on PCI && SCSI
1291 This driver supports PCI SCSI host adapters based on the Am53C974A
1292 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1293 PCscsi/PCnet (Am53/79C974) solutions.
1295 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1297 Note that this driver does NOT support Tekram DC390W/U/F, which are
1298 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1300 To compile this driver as a module, choose M here: the
1301 module will be called tmscsim.
1304 tristate "Trantor T128/T128F/T228 SCSI support"
1305 depends on ISA && SCSI
1306 select SCSI_SPI_ATTRS
1308 This is support for a SCSI host adapter. It is explained in section
1309 3.11 of the SCSI-HOWTO, available from
1310 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1311 of the box, you may have to change some settings in
1312 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1313 Adaptec, and some former Trantor products are being sold under the
1316 To compile this driver as a module, choose M here: the
1317 module will be called t128.
1320 tristate "UltraStor 14F/34F support"
1321 depends on ISA && SCSI && ISA_DMA_API
1323 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1324 The source at <file:drivers/scsi/u14-34f.c> contains some
1325 information about this hardware. If the driver doesn't work out of
1326 the box, you may have to change some settings in
1327 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1328 <http://www.tldp.org/docs.html#howto>. Note that there is also
1329 another driver for the same hardware: "UltraStor SCSI support",
1330 below. You should say Y to both only if you want 24F support as
1333 To compile this driver as a module, choose M here: the
1334 module will be called u14-34f.
1336 config SCSI_U14_34F_TAGGED_QUEUE
1337 bool "enable tagged command queueing"
1338 depends on SCSI_U14_34F
1340 This is a feature of SCSI-2 which improves performance: the host
1341 adapter can send several SCSI commands to a device's queue even if
1342 previous commands haven't finished yet.
1343 This is equivalent to the "u14-34f=tc:y" boot option.
1345 config SCSI_U14_34F_LINKED_COMMANDS
1346 bool "enable elevator sorting"
1347 depends on SCSI_U14_34F
1349 This option enables elevator sorting for all probed SCSI disks and
1350 CD-ROMs. It definitely reduces the average seek distance when doing
1351 random seeks, but this does not necessarily result in a noticeable
1352 performance improvement: your mileage may vary...
1353 This is equivalent to the "u14-34f=lc:y" boot option.
1355 config SCSI_U14_34F_MAX_TAGS
1356 int "maximum number of queued commands"
1357 depends on SCSI_U14_34F
1360 This specifies how many SCSI commands can be maximally queued for
1361 each probed SCSI device. You should reduce the default value of 8
1362 only if you have disks with buggy or limited tagged command support.
1363 Minimum is 2 and maximum is 14. This value is also the window size
1364 used by the elevator sorting option above. The effective value used
1365 by the driver for each probed SCSI device is reported at boot time.
1366 This is equivalent to the "u14-34f=mq:8" boot option.
1368 config SCSI_ULTRASTOR
1369 tristate "UltraStor SCSI support"
1370 depends on X86 && ISA && SCSI
1372 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1373 adapter family. This driver is explained in section 3.12 of the
1374 SCSI-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1376 of the box, you may have to change some settings in
1377 <file:drivers/scsi/ultrastor.h>.
1379 Note that there is also another driver for the same hardware:
1380 "UltraStor 14F/34F support", above.
1382 To compile this driver as a module, choose M here: the
1383 module will be called ultrastor.
1386 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1387 depends on PCI && SCSI && !64BIT
1389 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1390 SCSI host adapter. Please read the SCSI-HOWTO, available from
1391 <http://www.tldp.org/docs.html#howto>.
1393 To compile this driver as a module, choose M here: the
1394 module will be called nsp32.
1397 tristate "SCSI debugging host simulator"
1400 This is a host adapter simulator that can simulate multiple hosts
1401 each with multiple dummy SCSI devices (disks). It defaults to one
1402 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1403 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1404 dummy disks are simulated, they share the same kernel RAM for
1405 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1406 information. This driver is primarily of use to those testing the
1407 SCSI and block subsystems. If unsure, say N.
1410 tristate "MESH (Power Mac internal SCSI) support"
1411 depends on PPC32 && PPC_PMAC && SCSI
1413 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1414 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1415 other Power Macintoshes do). Say Y to include support for this SCSI
1418 To compile this driver as a module, choose M here: the
1419 module will be called mesh.
1421 config SCSI_MESH_SYNC_RATE
1422 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1423 depends on SCSI_MESH
1426 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1427 drives a bus which is entirely internal to the machine (such as the
1428 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1429 operation at up to 10 MB/s. On machines where the SCSI bus
1430 controlled by the MESH can have external devices connected, it is
1431 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1432 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1433 to disable synchronous operation.
1435 config SCSI_MESH_RESET_DELAY_MS
1436 int "initial bus reset delay (ms) (0 = no reset)"
1437 depends on SCSI_MESH
1440 config SCSI_MAC53C94
1441 tristate "53C94 (Power Mac external SCSI) support"
1442 depends on PPC32 && PPC_PMAC && SCSI
1444 On Power Macintoshes (and clones) with two SCSI buses, the external
1445 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1446 machines which only have one SCSI bus, such as the 7200, also use
1447 the 53C94. Say Y to include support for the 53C94.
1449 To compile this driver as a module, choose M here: the
1450 module will be called mac53c94.
1452 source "drivers/scsi/arm/Kconfig"
1455 bool "MIPS JAZZ FAS216 SCSI support"
1456 depends on MACH_JAZZ && SCSI
1458 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1459 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1463 tristate "A3000 WD33C93A support"
1464 depends on AMIGA && SCSI
1466 If you have an Amiga 3000 and have SCSI devices connected to the
1467 built-in SCSI controller, say Y. Otherwise, say N.
1469 To compile this driver as a module, choose M here: the
1470 module will be called wd33c93.
1473 tristate "A2091/A590 WD33C93A support"
1474 depends on ZORRO && SCSI
1476 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1479 To compile this driver as a module, choose M here: the
1480 module will be called wd33c93.
1483 tristate "GVP Series II WD33C93A support"
1484 depends on ZORRO && SCSI
1486 If you have a Great Valley Products Series II SCSI controller,
1487 answer Y. Also say Y if you have a later model of GVP SCSI
1488 controller (such as the GVP A4008 or a Combo board). Otherwise,
1489 answer N. This driver does NOT work for the T-Rex series of
1490 accelerators from TekMagic and GVP-M.
1492 To compile this driver as a module, choose M here: the
1493 module will be called gvp11.
1495 config CYBERSTORM_SCSI
1496 tristate "CyberStorm SCSI support"
1497 depends on ZORRO && SCSI
1499 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1500 accelerator board and the optional Cyberstorm SCSI controller,
1501 answer Y. Otherwise, say N.
1503 config CYBERSTORMII_SCSI
1504 tristate "CyberStorm Mk II SCSI support"
1505 depends on ZORRO && SCSI
1507 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1508 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1512 tristate "Blizzard 2060 SCSI support"
1513 depends on ZORRO && SCSI
1515 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1516 and want to use the onboard SCSI controller, say Y. Otherwise,
1520 tristate "Blizzard 1230IV/1260 SCSI support"
1521 depends on ZORRO && SCSI
1523 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1524 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1527 config FASTLANE_SCSI
1528 tristate "Fastlane SCSI support"
1529 depends on ZORRO && SCSI
1531 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1532 one in the near future, say Y to this question. Otherwise, say N.
1534 config SCSI_AMIGA7XX
1535 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1536 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1538 Support for various NCR53c710-based SCSI controllers on the Amiga.
1540 - the builtin SCSI controller on the Amiga 4000T,
1541 - the Amiga 4091 Zorro III SCSI-2 controller,
1542 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1544 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1545 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1546 accelerator card for the Amiga 1200,
1547 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1548 Note that all of the above SCSI controllers, except for the builtin
1549 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1550 bus, so you also have to enable Zorro bus support if you want to use
1554 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1555 depends on ZORRO && SCSI && EXPERIMENTAL
1557 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1558 Y to this question. If you're in doubt about whether you have one,
1560 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1563 tristate "Atari native SCSI support"
1564 depends on ATARI && SCSI && BROKEN
1565 select SCSI_SPI_ATTRS
1567 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1568 Falcon, ...) say Y to get it supported. Of course also, if you have
1569 a compatible SCSI controller (e.g. for Medusa).
1571 To compile this driver as a module, choose M here: the
1572 module will be called atari_scsi.
1574 This driver supports both styles of NCR integration into the
1575 system: the TT style (separate DMA), and the Falcon style (via
1576 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1577 in the Hades (without DMA).
1579 config ATARI_SCSI_TOSHIBA_DELAY
1580 bool "Long delays for Toshiba CD-ROMs"
1581 depends on ATARI_SCSI
1583 This option increases the delay after a SCSI arbitration to
1584 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1585 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1586 would impact performance a bit, so say N.
1588 config ATARI_SCSI_RESET_BOOT
1589 bool "Reset SCSI-devices at boottime"
1590 depends on ATARI_SCSI
1592 Reset the devices on your Atari whenever it boots. This makes the
1593 boot process fractionally longer but may assist recovery from errors
1594 that leave the devices with SCSI operations partway completed.
1597 bool "Hades SCSI DMA emulator"
1598 depends on ATARI_SCSI && HADES
1600 This option enables code which emulates the TT SCSI DMA chip on the
1601 Hades. This increases the SCSI transfer rates at least ten times
1602 compared to PIO transfers.
1605 bool "Macintosh NCR5380 SCSI"
1606 depends on MAC && SCSI=y
1607 select SCSI_SPI_ATTRS
1609 This is the NCR 5380 SCSI controller included on most of the 68030
1610 based Macintoshes. If you have one of these say Y and read the
1611 SCSI-HOWTO, available from
1612 <http://www.tldp.org/docs.html#howto>.
1615 tristate "Macintosh NCR53c9[46] SCSI"
1616 depends on MAC && SCSI
1618 This is the NCR 53c9x SCSI controller found on most of the 68040
1619 based Macintoshes. If you have one of these say Y and read the
1620 SCSI-HOWTO, available from
1621 <http://www.tldp.org/docs.html#howto>.
1623 To compile this driver as a module, choose M here: the
1624 module will be called mac_esp.
1627 bool "WD33C93 SCSI driver for MVME147"
1628 depends on MVME147 && SCSI=y
1629 select SCSI_SPI_ATTRS
1631 Support for the on-board SCSI controller on the Motorola MVME147
1632 single-board computer.
1635 bool "NCR53C710 SCSI driver for MVME16x"
1636 depends on MVME16x && SCSI && BROKEN
1637 select SCSI_SPI_ATTRS
1639 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1640 SCSI controller chip. Almost everyone using one of these boards
1641 will want to say Y to this question.
1643 config BVME6000_SCSI
1644 bool "NCR53C710 SCSI driver for BVME6000"
1645 depends on BVME6000 && SCSI && BROKEN
1646 select SCSI_SPI_ATTRS
1648 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1649 SCSI controller chip. Almost everyone using one of these boards
1650 will want to say Y to this question.
1652 config SCSI_NCR53C7xx_FAST
1653 bool "allow FAST-SCSI [10MHz]"
1654 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1656 This will enable 10MHz FAST-SCSI transfers with your host
1657 adapter. Some systems have problems with that speed, so it's safest
1661 tristate "Sun3 NCR5380 SCSI"
1662 depends on SUN3 && SCSI && BROKEN
1663 select SCSI_SPI_ATTRS
1665 This option will enable support for the OBIO (onboard io) NCR5380
1666 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1667 "Sun3" type VME scsi controllers also based on the NCR5380.
1668 General Linux information on the Sun 3 series (now discontinued)
1669 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1672 bool "Sun3x ESP SCSI"
1673 depends on SUN3X && SCSI=y
1675 The ESP was an on-board SCSI controller used on Sun 3/80
1676 machines. Say Y here to compile in support for it.
1679 tristate "Sparc ESP Scsi Driver"
1680 depends on SBUS && SCSI
1682 This is the driver for the Sun ESP SCSI host adapter. The ESP
1683 chipset is present in most SPARC SBUS-based computers.
1685 To compile this driver as a module, choose M here: the
1686 module will be called esp.
1688 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1691 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1692 depends on S390 && QDIO && SCSI
1693 select SCSI_FC_ATTRS
1695 If you want to access SCSI devices attached to your IBM eServer
1696 zSeries by means of Fibre Channel interfaces say Y.
1697 For details please refer to the documentation provided by IBM at
1698 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1700 This driver is also available as a module. This module will be
1701 called zfcp. If you want to compile it as a module, say M here
1702 and read <file:Documentation/modules.txt>.
1706 source "drivers/scsi/pcmcia/Kconfig"