1 menu "SCSI device support"
4 tristate "RAID Transport Class"
11 tristate "SCSI device support"
14 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
15 any other SCSI device under Linux, say Y and make sure that you know
16 the name of your SCSI host adapter (the card inside your computer
17 that "speaks" the SCSI protocol, also called SCSI controller),
18 because you will be asked for it.
20 You also need to say Y here if you have a device which speaks
21 the SCSI protocol. Examples of this include the parallel port
22 version of the IOMEGA ZIP drive, USB storage devices, Fibre
23 Channel, FireWire storage and the IDE-SCSI emulation driver.
25 To compile this driver as a module, choose M here and read
26 <file:Documentation/scsi/scsi.txt>.
27 The module will be called scsi_mod.
29 However, do not compile this as a module if your root file system
30 (the one containing the directory /) is located on a SCSI device.
33 tristate "SCSI target support"
34 depends on SCSI && EXPERIMENTAL
36 If you want to use SCSI target mode drivers enable this option.
37 If you choose M, the module will be called scsi_tgt.
45 bool "legacy /proc/scsi/ support"
46 depends on SCSI && PROC_FS
49 This option enables support for the various files in
50 /proc/scsi. In Linux 2.6 this has been superseded by
51 files in sysfs but many legacy applications rely on this.
55 comment "SCSI support type (disk, tape, CD-ROM)"
59 tristate "SCSI disk support"
62 If you want to use SCSI hard disks, Fibre Channel disks,
63 USB storage or the SCSI or parallel port version of
64 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
65 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
66 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
69 To compile this driver as a module, choose M here and read
70 <file:Documentation/scsi/scsi.txt>.
71 The module will be called sd_mod.
73 Do not compile this driver as a module if your root file system
74 (the one containing the directory /) is located on a SCSI disk.
75 In this case, do not compile the driver for your SCSI host adapter
76 (below) as a module either.
79 tristate "SCSI tape support"
82 If you want to use a SCSI tape drive under Linux, say Y and read the
83 SCSI-HOWTO, available from
84 <http://www.tldp.org/docs.html#howto>, and
85 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
88 To compile this driver as a module, choose M here and read
89 <file:Documentation/scsi/scsi.txt>. The module will be called st.
92 tristate "SCSI OnStream SC-x0 tape support"
95 The OnStream SC-x0 SCSI tape drives cannot be driven by the
96 standard st driver, but instead need this special osst driver and
97 use the /dev/osstX char device nodes (major 206). Via usb-storage
98 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
99 as well. Note that there is also a second generation of OnStream
100 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
101 tapes (QIC-157) and can be driven by the standard driver st.
102 For more information, you may have a look at the SCSI-HOWTO
103 <http://www.tldp.org/docs.html#howto> and
104 <file:Documentation/scsi/osst.txt> in the kernel source.
105 More info on the OnStream driver may be found on
106 <http://linux1.onstream.nl/test/>
107 Please also have a look at the standard st docu, as most of it
108 applies to osst as well.
110 To compile this driver as a module, choose M here and read
111 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
114 tristate "SCSI CDROM support"
117 If you want to use a SCSI or FireWire CD-ROM under Linux,
118 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
119 <http://www.tldp.org/docs.html#howto>. Also make sure to say
120 Y or M to "ISO 9660 CD-ROM file system support" later.
122 To compile this driver as a module, choose M here and read
123 <file:Documentation/scsi/scsi.txt>.
124 The module will be called sr_mod.
126 config BLK_DEV_SR_VENDOR
127 bool "Enable vendor-specific extensions (for SCSI CDROM)"
128 depends on BLK_DEV_SR
130 This enables the usage of vendor specific SCSI commands. This is
131 required to support multisession CDs with old NEC/TOSHIBA cdrom
132 drives (and HP Writers). If you have such a drive and get the first
133 session only, try saying Y here; everybody else says N.
136 tristate "SCSI generic support"
139 If you want to use SCSI scanners, synthesizers or CD-writers or just
140 about anything having "SCSI" in its name other than hard disks,
141 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
142 directly, so you need some additional software which knows how to
143 talk to these devices using the SCSI protocol:
145 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
146 writer software look at Cdrtools
147 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
148 and for burning a "disk at once": CDRDAO
149 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
150 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
151 For other devices, it's possible that you'll have to write the
152 driver software yourself. Please read the file
153 <file:Documentation/scsi/scsi-generic.txt> for more information.
155 To compile this driver as a module, choose M here and read
156 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
161 tristate "SCSI media changer support"
164 This is a driver for SCSI media changers. Most common devices are
165 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
166 don't need this for those tiny 6-slot cdrom changers. Media
167 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
168 If you have such hardware and want to use it with linux, say Y
169 here. Check <file:Documentation/scsi-changer.txt> for details.
171 If you want to compile this as a module ( = code which can be
172 inserted in and removed from the running kernel whenever you want),
173 say M here and read <file:Documentation/modules.txt> and
174 <file:Documentation/scsi.txt>. The module will be called ch.o.
178 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
181 config SCSI_MULTI_LUN
182 bool "Probe all LUNs on each SCSI device"
185 If you have a SCSI device that supports more than one LUN (Logical
186 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
187 can say Y here to force the SCSI driver to probe for multiple LUNs.
188 A SCSI device with multiple LUNs acts logically like multiple SCSI
189 devices. The vast majority of SCSI devices have only one LUN, and
190 so most people can say N here. The max_luns boot/module parameter
191 allows to override this setting.
193 config SCSI_CONSTANTS
194 bool "Verbose SCSI error reporting (kernel size +=12K)"
197 The error messages regarding your SCSI hardware will be easier to
198 understand if you say Y here; it will enlarge your kernel by about
199 12 KB. If in doubt, say Y.
202 bool "SCSI logging facility"
205 This turns on a logging facility that can be used to debug a number
206 of SCSI related problems.
208 If you say Y here, no logging output will appear by default, but you
209 can enable logging by saying Y to "/proc file system support" and
210 "Sysctl support" below and executing the command
212 echo "scsi log token [level]" > /proc/scsi/scsi
214 at boot time after the /proc file system has been mounted.
216 There are a number of things that can be used for 'token' (you can
217 find them in the source: <file:drivers/scsi/scsi.c>), and this
218 allows you to select the types of information you want, and the
219 level allows you to select the level of verbosity.
221 If you say N here, it may be harder to track down some types of SCSI
222 problems. If you say Y here your kernel will be somewhat larger, but
223 there should be no noticeable performance impact as long as you have
226 config SCSI_SCAN_ASYNC
227 bool "Asynchronous SCSI scanning"
230 The SCSI subsystem can probe for devices while the rest of the
231 system continues booting, and even probe devices on different
232 busses in parallel, leading to a significant speed-up.
233 If you have built SCSI as modules, enabling this option can
234 be a problem as the devices may not have been found by the
235 time your system expects them to have been. You can load the
236 scsi_wait_scan module to ensure that all scans have completed.
237 If you build your SCSI drivers into the kernel, then everything
238 will work fine if you say Y here.
240 You can override this choice by specifying scsi_mod.scan="sync"
241 or "async" on the kernel's command line.
243 menu "SCSI Transports"
246 config SCSI_SPI_ATTRS
247 tristate "Parallel SCSI (SPI) Transport Attributes"
250 If you wish to export transport-specific information about
251 each attached SCSI device to sysfs, say Y. Otherwise, say N.
254 tristate "FiberChannel Transport Attributes"
258 If you wish to export transport-specific information about
259 each attached FiberChannel device to sysfs, say Y.
262 config SCSI_ISCSI_ATTRS
263 tristate "iSCSI Transport Attributes"
264 depends on SCSI && NET
266 If you wish to export transport-specific information about
267 each attached iSCSI device to sysfs, say Y.
270 config SCSI_SAS_ATTRS
271 tristate "SAS Transport Attributes"
274 If you wish to export transport-specific information about
275 each attached SAS device to sysfs, say Y.
277 source "drivers/scsi/libsas/Kconfig"
281 menu "SCSI low-level drivers"
285 tristate "iSCSI Initiator over TCP/IP"
286 depends on SCSI && INET
290 select SCSI_ISCSI_ATTRS
292 The iSCSI Driver provides a host with the ability to access storage
293 through an IP network. The driver uses the iSCSI protocol to transport
294 SCSI requests and responses over a TCP/IP network between the host
295 (the "initiator") and "targets". Architecturally, the iSCSI driver
296 combines with the host's TCP/IP stack, network drivers, and Network
297 Interface Card (NIC) to provide the same functions as a SCSI or a
298 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
300 To compile this driver as a module, choose M here: the
301 module will be called iscsi_tcp.
303 The userspace component needed to initialize the driver, documentation,
304 and sample configuration files can be found here:
306 http://linux-iscsi.sf.net
309 tristate "SGI WD93C93 SCSI Driver"
310 depends on SGI_IP22 && SCSI
312 If you have a Western Digital WD93 SCSI controller on
313 an SGI MIPS system, say Y. Otherwise, say N.
316 tristate "DEC NCR53C94 Scsi Driver"
317 depends on MACH_DECSTATION && SCSI && TC
319 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
320 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
323 tristate "DEC SII Scsi Driver"
324 depends on MACH_DECSTATION && SCSI && 32BIT
326 config BLK_DEV_3W_XXXX_RAID
327 tristate "3ware 5/6/7/8xxx ATA-RAID support"
328 depends on PCI && SCSI
330 3ware is the only hardware ATA-Raid product in Linux to date.
331 This card is 2,4, or 8 channel master mode support only.
332 SCSI support required!!!
334 <http://www.3ware.com/>
336 Please read the comments at the top of
337 <file:drivers/scsi/3w-xxxx.c>.
340 tristate "3ware 9xxx SATA-RAID support"
341 depends on PCI && SCSI
343 This driver supports the 9000 series 3ware SATA-RAID cards.
345 <http://www.amcc.com>
347 Please read the comments at the top of
348 <file:drivers/scsi/3w-9xxx.c>.
350 config SCSI_7000FASST
351 tristate "7000FASST SCSI support"
352 depends on ISA && SCSI && ISA_DMA_API
354 This driver supports the Western Digital 7000 SCSI host adapter
355 family. Some information is in the source:
356 <file:drivers/scsi/wd7000.c>.
358 To compile this driver as a module, choose M here: the
359 module will be called wd7000.
362 tristate "ACARD SCSI support"
363 depends on PCI && SCSI
365 This driver supports the ACARD SCSI host adapter.
366 Support Chip <ATP870 ATP876 ATP880 ATP885>
367 To compile this driver as a module, choose M here: the
368 module will be called atp870u.
371 tristate "Adaptec AHA152X/2825 support"
372 depends on ISA && SCSI && !64BIT
373 select SCSI_SPI_ATTRS
375 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
376 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
377 must be manually specified in this case.
379 It is explained in section 3.3 of the SCSI-HOWTO, available from
380 <http://www.tldp.org/docs.html#howto>. You might also want to
381 read the file <file:Documentation/scsi/aha152x.txt>.
383 To compile this driver as a module, choose M here: the
384 module will be called aha152x.
387 tristate "Adaptec AHA1542 support"
388 depends on ISA && SCSI && ISA_DMA_API
390 This is support for a SCSI host adapter. It is explained in section
391 3.4 of the SCSI-HOWTO, available from
392 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
393 purchased by Adaptec, and some former Trantor products are being
394 sold under the Adaptec name. If it doesn't work out of the box, you
395 may have to change some settings in <file:drivers/scsi/aha1542.h>.
397 To compile this driver as a module, choose M here: the
398 module will be called aha1542.
401 tristate "Adaptec AHA1740 support"
402 depends on EISA && SCSI
404 This is support for a SCSI host adapter. It is explained in section
405 3.5 of the SCSI-HOWTO, available from
406 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
407 of the box, you may have to change some settings in
408 <file:drivers/scsi/aha1740.h>.
410 To compile this driver as a module, choose M here: the
411 module will be called aha1740.
414 tristate "Adaptec AACRAID support"
415 depends on SCSI && PCI
417 This driver supports a variety of Dell, HP, Adaptec, IBM and
418 ICP storage products. For a list of supported products, refer
419 to <file:Documentation/scsi/aacraid.txt>.
421 To compile this driver as a module, choose M here: the module
422 will be called aacraid.
425 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
427 config SCSI_AIC7XXX_OLD
428 tristate "Adaptec AIC7xxx support (old driver)"
429 depends on (ISA || EISA || PCI ) && SCSI
431 WARNING This driver is an older aic7xxx driver and is no longer
432 under active development. Adaptec, Inc. is writing a new driver to
433 take the place of this one, and it is recommended that whenever
434 possible, people should use the new Adaptec written driver instead
435 of this one. This driver will eventually be phased out entirely.
437 This is support for the various aic7xxx based Adaptec SCSI
438 controllers. These include the 274x EISA cards; 284x VLB cards;
439 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
440 motherboard based SCSI controllers from Adaptec. It does not support
441 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
442 support them. It does not support the 2920 cards from Adaptec that
443 use the Future Domain SCSI controller chip. For those cards, you
444 need the "Future Domain 16xx SCSI support" driver.
446 In general, if the controller is based on an Adaptec SCSI controller
447 chip from the aic777x series or the aic78xx series, this driver
448 should work. The only exception is the 7810 which is specifically
449 not supported (that's the RAID controller chip on the AAA-13x
452 Note that the AHA2920 SCSI host adapter is *not* supported by this
453 driver; choose "Future Domain 16xx SCSI support" instead if you have
456 Information on the configuration options for this controller can be
457 found by checking the help file for each of the available
458 configuration options. You should read
459 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
460 contacting the maintainer with any questions. The SCSI-HOWTO,
461 available from <http://www.tldp.org/docs.html#howto>, can also
464 To compile this driver as a module, choose M here: the
465 module will be called aic7xxx_old.
467 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
468 source "drivers/scsi/aic94xx/Kconfig"
470 # All the I2O code and drivers do not seem to be 64bit safe.
472 tristate "Adaptec I2O RAID support "
473 depends on !64BIT && SCSI && PCI
475 This driver supports all of Adaptec's I2O based RAID controllers as
476 well as the DPT SmartRaid V cards. This is an Adaptec maintained
477 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
479 To compile this driver as a module, choose M here: the
480 module will be called dpt_i2o.
483 tristate "AdvanSys SCSI support"
485 depends on ISA || EISA || PCI
486 depends on BROKEN || X86_32
488 This is a driver for all SCSI host adapters manufactured by
489 AdvanSys. It is documented in the kernel source in
490 <file:drivers/scsi/advansys.c>.
492 To compile this driver as a module, choose M here: the
493 module will be called advansys.
496 tristate "Always IN2000 SCSI support"
497 depends on ISA && SCSI
499 This is support for an ISA bus SCSI host adapter. You'll find more
500 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
501 out of the box, you may have to change the jumpers for IRQ or
504 To compile this driver as a module, choose M here: the
505 module will be called in2000.
508 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
509 depends on PCI && SCSI
511 This driver supports all of ARECA's SATA RAID controller cards.
512 This is an ARECA-maintained driver by Erich Chen.
513 If you have any problems, please mail to: < erich@areca.com.tw >
514 Areca supports Linux RAID config tools.
516 < http://www.areca.com.tw >
518 To compile this driver as a module, choose M here: the
519 module will be called arcmsr (modprobe arcmsr).
521 source "drivers/scsi/megaraid/Kconfig.megaraid"
524 tristate "HighPoint RocketRAID 3xxx Controller support"
525 depends on SCSI && PCI
527 This option enables support for HighPoint RocketRAID 3xxx
530 To compile this driver as a module, choose M here; the module
531 will be called hptiop. If unsure, say N.
534 tristate "BusLogic SCSI support"
535 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
537 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
538 Adapters. Consult the SCSI-HOWTO, available from
539 <http://www.tldp.org/docs.html#howto>, and the files
540 <file:Documentation/scsi/BusLogic.txt> and
541 <file:Documentation/scsi/FlashPoint.txt> for more information.
543 To compile this driver as a module, choose M here: the
544 module will be called BusLogic.
546 config SCSI_OMIT_FLASHPOINT
547 bool "Omit FlashPoint support"
548 depends on SCSI_BUSLOGIC
550 This option allows you to omit the FlashPoint support from the
551 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
552 substantial, so users of MultiMaster Host Adapters may wish to omit
556 tristate "DMX3191D SCSI support"
557 depends on PCI && SCSI
558 select SCSI_SPI_ATTRS
560 This is support for Domex DMX3191D SCSI Host Adapters.
562 To compile this driver as a module, choose M here: the
563 module will be called dmx3191d.
566 tristate "DTC3180/3280 SCSI support"
567 depends on ISA && SCSI
568 select SCSI_SPI_ATTRS
570 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
571 the SCSI-HOWTO, available from
572 <http://www.tldp.org/docs.html#howto>, and the file
573 <file:Documentation/scsi/dtc3x80.txt>.
575 To compile this driver as a module, choose M here: the
576 module will be called dtc.
579 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
580 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
582 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
583 ISA and all EISA I/O addresses are probed looking for the "EATA"
584 signature. The addresses of all the PCI SCSI controllers reported
585 by the PCI subsystem are probed as well.
587 You want to read the start of <file:drivers/scsi/eata.c> and the
588 SCSI-HOWTO, available from
589 <http://www.tldp.org/docs.html#howto>.
591 To compile this driver as a module, choose M here: the
592 module will be called eata.
594 config SCSI_EATA_TAGGED_QUEUE
595 bool "enable tagged command queueing"
598 This is a feature of SCSI-2 which improves performance: the host
599 adapter can send several SCSI commands to a device's queue even if
600 previous commands haven't finished yet.
601 This is equivalent to the "eata=tc:y" boot option.
603 config SCSI_EATA_LINKED_COMMANDS
604 bool "enable elevator sorting"
607 This option enables elevator sorting for all probed SCSI disks and
608 CD-ROMs. It definitely reduces the average seek distance when doing
609 random seeks, but this does not necessarily result in a noticeable
610 performance improvement: your mileage may vary...
611 This is equivalent to the "eata=lc:y" boot option.
613 config SCSI_EATA_MAX_TAGS
614 int "maximum number of queued commands"
618 This specifies how many SCSI commands can be maximally queued for
619 each probed SCSI device. You should reduce the default value of 16
620 only if you have disks with buggy or limited tagged command support.
621 Minimum is 2 and maximum is 62. This value is also the window size
622 used by the elevator sorting option above. The effective value used
623 by the driver for each probed SCSI device is reported at boot time.
624 This is equivalent to the "eata=mq:8" boot option.
627 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
628 depends on (ISA || EISA || PCI) && SCSI && BROKEN
630 This driver supports all EATA-PIO protocol compliant SCSI Host
631 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
632 host adapters could also use this driver but are discouraged from
633 doing so, since this driver only supports hard disks and lacks
634 numerous features. You might want to have a look at the SCSI-HOWTO,
635 available from <http://www.tldp.org/docs.html#howto>.
637 To compile this driver as a module, choose M here: the
638 module will be called eata_pio.
640 config SCSI_FUTURE_DOMAIN
641 tristate "Future Domain 16xx SCSI/AHA-2920A support"
642 depends on (ISA || PCI) && SCSI
644 This is support for Future Domain's 16-bit SCSI host adapters
645 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
646 other adapters based on the Future Domain chipsets (Quantum
647 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
648 It is explained in section 3.7 of the SCSI-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>.
651 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
652 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
653 controller support"). This Future Domain driver works with the older
654 Adaptec AHA-2920A boards with a Future Domain chip on them.
656 To compile this driver as a module, choose M here: the
657 module will be called fdomain.
660 tristate "Future Domain MCS-600/700 SCSI support"
661 depends on MCA_LEGACY && SCSI
663 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
664 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
665 is identical to the MCS 700 and hence also supported by this driver.
666 This driver also supports the Reply SB16/SCSI card (the SCSI part).
667 It supports multiple adapters in the same system.
669 To compile this driver as a module, choose M here: the
670 module will be called fd_mcs.
673 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
674 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
676 Formerly called GDT SCSI Disk Array Controller Support.
678 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
679 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
680 in the kernel source in <file:drivers/scsi/gdth.c> and
681 <file:drivers/scsi/gdth.h.>
683 To compile this driver as a module, choose M here: the
684 module will be called gdth.
686 config SCSI_GENERIC_NCR5380
687 tristate "Generic NCR5380/53c400 SCSI PIO support"
688 depends on ISA && SCSI
689 select SCSI_SPI_ATTRS
691 This is a driver for the old NCR 53c80 series of SCSI controllers
692 on boards using PIO. Most boards such as the Trantor T130 fit this
693 category, along with a large number of ISA 8bit controllers shipped
694 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
695 you should select the specific driver for that card rather than
696 generic 5380 support.
698 It is explained in section 3.8 of the SCSI-HOWTO, available from
699 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
700 of the box, you may have to change some settings in
701 <file:drivers/scsi/g_NCR5380.h>.
703 To compile this driver as a module, choose M here: the
704 module will be called g_NCR5380.
706 config SCSI_GENERIC_NCR5380_MMIO
707 tristate "Generic NCR5380/53c400 SCSI MMIO support"
708 depends on ISA && SCSI
709 select SCSI_SPI_ATTRS
711 This is a driver for the old NCR 53c80 series of SCSI controllers
712 on boards using memory mapped I/O.
713 It is explained in section 3.8 of the SCSI-HOWTO, available from
714 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
715 of the box, you may have to change some settings in
716 <file:drivers/scsi/g_NCR5380.h>.
718 To compile this driver as a module, choose M here: the
719 module will be called g_NCR5380_mmio.
721 config SCSI_GENERIC_NCR53C400
722 bool "Enable NCR53c400 extensions"
723 depends on SCSI_GENERIC_NCR5380
725 This enables certain optimizations for the NCR53c400 SCSI cards.
726 You might as well try it out. Note that this driver will only probe
727 for the Trantor T130B in its default configuration; you might have
728 to pass a command line option to the kernel at boot time if it does
729 not detect your card. See the file
730 <file:Documentation/scsi/g_NCR5380.txt> for details.
733 tristate "IBMMCA SCSI support"
734 depends on MCA_LEGACY && SCSI
736 This is support for the IBM SCSI adapter found in many of the PS/2
737 series computers. These machines have an MCA bus, so you need to
738 answer Y to "MCA support" as well and read
739 <file:Documentation/mca.txt>.
741 If the adapter isn't found during boot (a common problem for models
742 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
743 option, where <pun> is the id of the SCSI subsystem (usually 7, but
744 if that doesn't work check your reference diskette). Owners of
745 model 95 with a LED-matrix-display can in addition activate some
746 activity info like under OS/2, but more informative, by setting
747 'ibmmcascsi=display' as an additional kernel parameter. Try "man
748 bootparam" or see the documentation of your boot loader about how to
749 pass options to the kernel.
751 To compile this driver as a module, choose M here: the
752 module will be called ibmmca.
754 config IBMMCA_SCSI_ORDER_STANDARD
755 bool "Standard SCSI-order"
756 depends on SCSI_IBMMCA
758 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
759 are assigned to the drive letters, starting with the lowest SCSI-id
760 (physical number -- pun) to be drive C:, as seen from DOS and
761 similar operating systems. When looking into papers describing the
762 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
763 The SCSI-standard follows a hardware-hierarchy which says that id 7
764 has the highest priority and id 0 the lowest. Therefore, the host
765 adapters are still today everywhere placed as SCSI-id 7 by default.
766 In the SCSI-standard, the drive letters express the priority of the
767 disk. C: should be the hard disk, or a partition on it, with the
768 highest priority. This must therefore be the disk with the highest
769 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
770 original definition of the SCSI-standard as also industrial- and
771 process-control-machines, like VME-CPUs running under realtime-OSes
772 (e.g. LynxOS, OS9) do.
774 If you like to run Linux on your MCA-machine with the same
775 assignment of hard disks as seen from e.g. DOS or OS/2 on your
776 machine, which is in addition conformant to the SCSI-standard, you
777 must say Y here. This is also necessary for MCA-Linux users who want
778 to keep downward compatibility to older releases of the
779 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
782 If you like to have the lowest SCSI-id assigned as drive C:, as
783 modern SCSI-BIOSes do, which does not conform to the standard, but
784 is widespread and common in the PC-world of today, you must say N
785 here. If unsure, say Y.
787 config IBMMCA_SCSI_DEV_RESET
788 bool "Reset SCSI-devices at boottime"
789 depends on SCSI_IBMMCA
791 By default, SCSI-devices are reset when the machine is powered on.
792 However, some devices exist, like special-control-devices,
793 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
794 not reset when switched on. If you say Y here, each device connected
795 to your SCSI-bus will be issued a reset-command after it has been
796 probed, while the kernel is booting. This may cause problems with
797 more modern devices, like hard disks, which do not appreciate these
798 reset commands, and can cause your system to hang. So say Y only if
799 you know that one of your older devices needs it; N is the safe
803 tristate "IBM ServeRAID support"
804 depends on PCI && SCSI
806 This is support for the IBM ServeRAID hardware RAID controllers.
807 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
808 for more information. If this driver does not work correctly
809 without modification please contact the author by email at
810 <ipslinux@adaptec.com>.
812 To compile this driver as a module, choose M here: the
813 module will be called ips.
816 tristate "IBM Virtual SCSI support"
817 depends on PPC_PSERIES || PPC_ISERIES
819 This is the IBM POWER Virtual SCSI Client
821 To compile this driver as a module, choose M here: the
822 module will be called ibmvscsic.
824 config SCSI_IBMVSCSIS
825 tristate "IBM Virtual SCSI Server support"
826 depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
828 This is the SRP target driver for IBM pSeries virtual environments.
830 The userspace component needed to initialize the driver and
831 documentation can be found:
833 http://stgt.berlios.de/
835 To compile this driver as a module, choose M here: the
836 module will be called ibmvstgt.
839 tristate "Initio 9100U(W) support"
840 depends on PCI && SCSI
842 This is support for the Initio 91XXU(W) SCSI host adapter. Please
843 read the SCSI-HOWTO, available from
844 <http://www.tldp.org/docs.html#howto>.
846 To compile this driver as a module, choose M here: the
847 module will be called initio.
850 tristate "Initio INI-A100U2W support"
851 depends on PCI && SCSI
853 This is support for the Initio INI-A100U2W SCSI host adapter.
854 Please read the SCSI-HOWTO, available from
855 <http://www.tldp.org/docs.html#howto>.
857 To compile this driver as a module, choose M here: the
858 module will be called a100u2w.
861 tristate "IOMEGA parallel port (ppa - older drives)"
862 depends on SCSI && PARPORT_PC
864 This driver supports older versions of IOMEGA's parallel port ZIP
865 drive (a 100 MB removable media device).
867 Note that you can say N here if you have the SCSI version of the ZIP
868 drive: it will be supported automatically if you said Y to the
869 generic "SCSI disk support", above.
871 If you have the ZIP Plus drive or a more recent parallel port ZIP
872 drive (if the supplied cable with the drive is labeled "AutoDetect")
873 then you should say N here and Y to "IOMEGA parallel port (imm -
874 newer drives)", below.
876 For more information about this driver and how to use it you should
877 read the file <file:Documentation/scsi/ppa.txt>. You should also read
878 the SCSI-HOWTO, which is available from
879 <http://www.tldp.org/docs.html#howto>. If you use this driver,
880 you will still be able to use the parallel port for other tasks,
881 such as a printer; it is safe to compile both drivers into the
884 To compile this driver as a module, choose M here: the
885 module will be called ppa.
888 tristate "IOMEGA parallel port (imm - newer drives)"
889 depends on SCSI && PARPORT_PC
891 This driver supports newer versions of IOMEGA's parallel port ZIP
892 drive (a 100 MB removable media device).
894 Note that you can say N here if you have the SCSI version of the ZIP
895 drive: it will be supported automatically if you said Y to the
896 generic "SCSI disk support", above.
898 If you have the ZIP Plus drive or a more recent parallel port ZIP
899 drive (if the supplied cable with the drive is labeled "AutoDetect")
900 then you should say Y here; if you have an older ZIP drive, say N
901 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
903 For more information about this driver and how to use it you should
904 read the file <file:Documentation/scsi/ppa.txt>. You should also read
905 the SCSI-HOWTO, which is available from
906 <http://www.tldp.org/docs.html#howto>. If you use this driver,
907 you will still be able to use the parallel port for other tasks,
908 such as a printer; it is safe to compile both drivers into the
911 To compile this driver as a module, choose M here: the
912 module will be called imm.
914 config SCSI_IZIP_EPP16
915 bool "ppa/imm option - Use slow (but safe) EPP-16"
916 depends on SCSI_PPA || SCSI_IMM
918 EPP (Enhanced Parallel Port) is a standard for parallel ports which
919 allows them to act as expansion buses that can handle up to 64
922 Some parallel port chipsets are slower than their motherboard, and
923 so we have to control the state of the chipset's FIFO queue every
924 now and then to avoid data loss. This will be done if you say Y
927 Generally, saying Y is the safe option and slows things down a bit.
929 config SCSI_IZIP_SLOW_CTR
930 bool "ppa/imm option - Assume slow parport control register"
931 depends on SCSI_PPA || SCSI_IMM
933 Some parallel ports are known to have excessive delays between
934 changing the parallel port control register and good data being
935 available on the parallel port data/status register. This option
936 forces a small delay (1.0 usec to be exact) after changing the
937 control register to let things settle out. Enabling this option may
938 result in a big drop in performance but some very old parallel ports
939 (found in 386 vintage machines) will not work properly.
941 Generally, saying N is fine.
943 config SCSI_NCR53C406A
944 tristate "NCR53c406a SCSI support"
945 depends on ISA && SCSI
947 This is support for the NCR53c406a SCSI host adapter. For user
948 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
949 in the kernel source. Also read the SCSI-HOWTO, available from
950 <http://www.tldp.org/docs.html#howto>.
952 To compile this driver as a module, choose M here: the
953 module will be called NCR53c406.
956 tristate "NCR Dual 700 MCA SCSI support"
957 depends on MCA && SCSI
958 select SCSI_SPI_ATTRS
960 This is a driver for the MicroChannel Dual 700 card produced by
961 NCR and commonly used in 345x/35xx/4100 class machines. It always
962 tries to negotiate sync and uses tag command queueing.
964 Unless you have an NCR manufactured machine, the chances are that
965 you do not have this SCSI card, so say N.
968 tristate "HP Lasi SCSI support for 53c700/710"
969 depends on GSC && SCSI
970 select SCSI_SPI_ATTRS
972 This is a driver for the SCSI controller in the Lasi chip found in
973 many PA-RISC workstations & servers. If you do not know whether you
974 have a Lasi chip, it is safe to say "Y" here.
976 config 53C700_LE_ON_BE
978 depends on SCSI_LASI700
982 tristate "Promise SuperTrak EX Series support"
983 depends on PCI && SCSI
985 This driver supports Promise SuperTrak EX8350/8300/16350/16300
988 config SCSI_SYM53C8XX_2
989 tristate "SYM53C8XX Version 2 SCSI support"
990 depends on PCI && SCSI
991 select SCSI_SPI_ATTRS
993 This driver supports the whole NCR53C8XX/SYM53C8XX family of
994 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
995 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
996 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
997 controllers; you need to use the Fusion MPT driver for that.
999 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1002 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1003 int "DMA addressing mode"
1004 depends on SCSI_SYM53C8XX_2
1007 This option only applies to PCI-SCSI chips that are PCI DAC
1008 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1010 When set to 0, the driver will program the chip to only perform
1011 32-bit DMA. When set to 1, the chip will be able to perform DMA
1012 to addresses up to 1TB. When set to 2, the driver supports the
1013 full 64-bit DMA address range, but can only address 16 segments
1014 of 4 GB each. This limits the total addressable range to 64 GB.
1016 Most machines with less than 4GB of memory should use a setting
1017 of 0 for best performance. If your machine has 4GB of memory
1018 or more, you should set this option to 1 (the default).
1020 The still experimental value 2 (64 bit DMA addressing with 16
1021 x 4GB segments limitation) can be used on systems that require
1022 PCI address bits past bit 39 to be set for the addressing of
1023 memory using PCI DAC cycles.
1025 config SCSI_SYM53C8XX_DEFAULT_TAGS
1026 int "Default tagged command queue depth"
1027 depends on SCSI_SYM53C8XX_2
1030 This is the default value of the command queue depth the
1031 driver will announce to the generic SCSI layer for devices
1032 that support tagged command queueing. This value can be changed
1033 from the boot command line. This is a soft limit that cannot
1034 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1036 config SCSI_SYM53C8XX_MAX_TAGS
1037 int "Maximum number of queued commands"
1038 depends on SCSI_SYM53C8XX_2
1041 This option allows you to specify the maximum number of commands
1042 that can be queued to any device, when tagged command queuing is
1043 possible. The driver supports up to 256 queued commands per device.
1044 This value is used as a compiled-in hard limit.
1046 config SCSI_SYM53C8XX_MMIO
1047 bool "Use memory mapped IO"
1048 depends on SCSI_SYM53C8XX_2
1051 Memory mapped IO is faster than Port IO. Most people should
1052 answer Y here, but some machines may have problems. If you have
1053 to answer N here, please report the problem to the maintainer.
1056 tristate "IBM Power Linux RAID adapter support"
1057 depends on PCI && SCSI && ATA
1060 This driver supports the IBM Power Linux family RAID adapters.
1061 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1062 as IBM iSeries 5702, 5703, 5709, and 570A.
1064 config SCSI_IPR_TRACE
1065 bool "enable driver internal trace"
1069 If you say Y here, the driver will trace all commands issued
1070 to the adapter. Performance impact is minimal. Trace can be
1071 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1073 config SCSI_IPR_DUMP
1074 bool "enable adapter dump support"
1078 If you say Y here, the driver will support adapter crash dump.
1079 If you enable this support, the iprdump daemon can be used
1080 to capture adapter failure analysis information.
1083 tristate "Zalon SCSI support"
1084 depends on GSC && SCSI
1085 select SCSI_SPI_ATTRS
1087 The Zalon is a GSC/HSC bus interface chip that sits between the
1088 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1089 C110, J200, J210 and some D, K & R-class machines. It's also
1090 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1091 Say Y here if you have one of these machines or cards.
1093 config SCSI_NCR_Q720
1094 tristate "NCR Quad 720 MCA SCSI support"
1095 depends on MCA && SCSI
1096 select SCSI_SPI_ATTRS
1098 This is a driver for the MicroChannel Quad 720 card produced by
1099 NCR and commonly used in 345x/35xx/4100 class machines. It always
1100 tries to negotiate sync and uses tag command queueing.
1102 Unless you have an NCR manufactured machine, the chances are that
1103 you do not have this SCSI card, so say N.
1105 config SCSI_NCR53C8XX_DEFAULT_TAGS
1106 int "default tagged command queue depth"
1107 depends on SCSI_ZALON || SCSI_NCR_Q720
1110 "Tagged command queuing" is a feature of SCSI-2 which improves
1111 performance: the host adapter can send several SCSI commands to a
1112 device's queue even if previous commands haven't finished yet.
1113 Because the device is intelligent, it can optimize its operations
1114 (like head positioning) based on its own request queue. Some SCSI
1115 devices don't implement this properly; if you want to disable this
1116 feature, enter 0 or 1 here (it doesn't matter which).
1118 The default value is 8 and should be supported by most hard disks.
1119 This value can be overridden from the boot command line using the
1120 'tags' option as follows (example):
1121 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1122 4, set queue depth to 16 for target 2 and target 3 on controller 0
1123 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1125 The normal answer therefore is to go with the default 8 and to use
1126 a boot command line option for devices that need to use a different
1127 command queue depth.
1129 There is no safe option other than using good SCSI devices.
1131 config SCSI_NCR53C8XX_MAX_TAGS
1132 int "maximum number of queued commands"
1133 depends on SCSI_ZALON || SCSI_NCR_Q720
1136 This option allows you to specify the maximum number of commands
1137 that can be queued to any device, when tagged command queuing is
1138 possible. The default value is 32. Minimum is 2, maximum is 64.
1139 Modern hard disks are able to support 64 tags and even more, but
1140 do not seem to be faster when more than 32 tags are being used.
1142 So, the normal answer here is to go with the default value 32 unless
1143 you are using very large hard disks with large cache (>= 1 MB) that
1144 are able to take advantage of more than 32 tagged commands.
1146 There is no safe option and the default answer is recommended.
1148 config SCSI_NCR53C8XX_SYNC
1149 int "synchronous transfers frequency in MHz"
1150 depends on SCSI_ZALON || SCSI_NCR_Q720
1153 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1154 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1155 are respectively the maximum data transfer rates in mega-transfers
1156 per second for each class. For example, a FAST-20 Wide 16 device is
1157 able to transfer data at 20 million 16 bit packets per second for a
1158 total rate of 40 MB/s.
1160 You may specify 0 if you want to only use asynchronous data
1161 transfers. This is the safest and slowest option. Otherwise, specify
1162 a value between 5 and 80, depending on the capability of your SCSI
1163 controller. The higher the number, the faster the data transfer.
1164 Note that 80 should normally be ok since the driver decreases the
1165 value automatically according to the controller's capabilities.
1167 Your answer to this question is ignored for controllers with NVRAM,
1168 since the driver will get this information from the user set-up. It
1169 also can be overridden using a boot setup option, as follows
1170 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1171 for FAST-20 synchronous data transfer (20 mega-transfers per
1174 The normal answer therefore is not to go with the default but to
1175 select the maximum value 80 allowing the driver to use the maximum
1176 value supported by each controller. If this causes problems with
1177 your SCSI devices, you should come back and decrease the value.
1179 There is no safe option other than using good cabling, right
1180 terminations and SCSI conformant devices.
1182 config SCSI_NCR53C8XX_PROFILE
1183 bool "enable profiling"
1184 depends on SCSI_ZALON || SCSI_NCR_Q720
1186 This option allows you to enable profiling information gathering.
1187 These statistics are not very accurate due to the low frequency
1188 of the kernel clock (100 Hz on i386) and have performance impact
1189 on systems that use very fast devices.
1191 The normal answer therefore is N.
1193 config SCSI_NCR53C8XX_NO_DISCONNECT
1194 bool "not allow targets to disconnect"
1195 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1197 This option is only provided for safety if you suspect some SCSI
1198 device of yours to not support properly the target-disconnect
1199 feature. In that case, you would say Y here. In general however, to
1200 not allow targets to disconnect is not reasonable if there is more
1201 than 1 device on a SCSI bus. The normal answer therefore is N.
1203 config SCSI_MCA_53C9X
1204 tristate "NCR MCA 53C9x SCSI support"
1205 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1207 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1208 controller based on the NCR 53C94. This driver will allow use of
1209 the controller on the 3550, and very possibly others.
1211 To compile this driver as a module, choose M here: the
1212 module will be called mca_53c9x.
1215 tristate "PAS16 SCSI support"
1216 depends on ISA && SCSI
1217 select SCSI_SPI_ATTRS
1219 This is support for a SCSI host adapter. It is explained in section
1220 3.10 of the SCSI-HOWTO, available from
1221 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1222 of the box, you may have to change some settings in
1223 <file:drivers/scsi/pas16.h>.
1225 To compile this driver as a module, choose M here: the
1226 module will be called pas16.
1229 tristate "PSI240i support"
1230 depends on ISA && SCSI
1232 This is support for the PSI240i EIDE interface card which acts as a
1233 SCSI host adapter. Please read the SCSI-HOWTO, available from
1234 <http://www.tldp.org/docs.html#howto>.
1236 To compile this driver as a module, choose M here: the
1237 module will be called psi240i.
1239 config SCSI_QLOGIC_FAS
1240 tristate "Qlogic FAS SCSI support"
1241 depends on ISA && SCSI
1243 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1244 FastSCSI! cards as well as any other card based on the FASXX chip
1245 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1247 This driver does NOT support the PCI versions of these cards. The
1248 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1249 SCSI support"), below.
1251 Information about this driver is contained in
1252 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1253 SCSI-HOWTO, available from
1254 <http://www.tldp.org/docs.html#howto>.
1256 To compile this driver as a module, choose M here: the
1257 module will be called qlogicfas.
1259 config SCSI_QLOGIC_FC_FIRMWARE
1260 bool "Include loadable firmware in driver"
1261 depends on SCSI_QLOGIC_FC
1263 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1264 expanded LUN addressing and FcTape (FCP-2) support, in the
1265 qlogicfc driver. This is required on some platforms.
1267 config SCSI_QLOGIC_1280
1268 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1269 depends on PCI && SCSI
1271 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1273 To compile this driver as a module, choose M here: the
1274 module will be called qla1280.
1276 config SCSI_QLOGICPTI
1277 tristate "PTI Qlogic, ISP Driver"
1278 depends on SBUS && SCSI
1280 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1281 controllers are known under Solaris as qpti and in the openprom as
1282 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1283 driven by a different driver.
1285 To compile this driver as a module, choose M here: the
1286 module will be called qlogicpti.
1288 source "drivers/scsi/qla2xxx/Kconfig"
1289 source "drivers/scsi/qla4xxx/Kconfig"
1292 tristate "Emulex LightPulse Fibre Channel Support"
1293 depends on PCI && SCSI
1294 select SCSI_FC_ATTRS
1296 This lpfc driver supports the Emulex LightPulse
1297 Family of Fibre Channel PCI host adapters.
1300 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1301 depends on X86 && ISA && SCSI && BROKEN
1303 These are 8-bit SCSI controllers; the ST-01 is also supported by
1304 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1305 available from <http://www.tldp.org/docs.html#howto>. If it
1306 doesn't work out of the box, you may have to change some macros at
1307 compiletime, which are described in <file:drivers/scsi/seagate.c>.
1309 To compile this driver as a module, choose M here: the
1310 module will be called seagate.
1312 # definitely looks not 64bit safe:
1314 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1315 depends on (EISA || MCA) && SCSI
1316 select SCSI_SPI_ATTRS
1318 This driver for NCR53c710 based SCSI host adapters.
1320 It currently supports Compaq EISA cards and NCR MCA cards
1322 config 53C700_IO_MAPPED
1324 depends on SCSI_SIM710
1327 config SCSI_SYM53C416
1328 tristate "Symbios 53c416 SCSI support"
1329 depends on ISA && SCSI
1331 This is support for the sym53c416 SCSI host adapter, the SCSI
1332 adapter that comes with some HP scanners. This driver requires that
1333 the sym53c416 is configured first using some sort of PnP
1334 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1335 are using isapnp then you need to compile this driver as a module
1336 and then load it using insmod after isapnp has run. The parameters
1337 of the configured card(s) should be passed to the driver. The format
1340 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1342 To compile this driver as a module, choose M here: the
1343 module will be called sym53c416.
1346 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1347 depends on PCI && SCSI && EXPERIMENTAL
1349 This driver supports PCI SCSI host adapters based on the ASIC
1350 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1352 This driver works, but is still in experimental status. So better
1353 have a bootable disk and a backup in case of emergency.
1355 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1357 To compile this driver as a module, choose M here: the
1358 module will be called dc395x.
1361 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1362 depends on PCI && SCSI
1364 This driver supports PCI SCSI host adapters based on the Am53C974A
1365 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1366 PCscsi/PCnet (Am53/79C974) solutions.
1368 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1370 Note that this driver does NOT support Tekram DC390W/U/F, which are
1371 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1373 To compile this driver as a module, choose M here: the
1374 module will be called tmscsim.
1377 tristate "Trantor T128/T128F/T228 SCSI support"
1378 depends on ISA && SCSI
1379 select SCSI_SPI_ATTRS
1381 This is support for a SCSI host adapter. It is explained in section
1382 3.11 of the SCSI-HOWTO, available from
1383 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1384 of the box, you may have to change some settings in
1385 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1386 Adaptec, and some former Trantor products are being sold under the
1389 To compile this driver as a module, choose M here: the
1390 module will be called t128.
1393 tristate "UltraStor 14F/34F support"
1394 depends on ISA && SCSI && ISA_DMA_API
1396 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1397 The source at <file:drivers/scsi/u14-34f.c> contains some
1398 information about this hardware. If the driver doesn't work out of
1399 the box, you may have to change some settings in
1400 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1401 <http://www.tldp.org/docs.html#howto>. Note that there is also
1402 another driver for the same hardware: "UltraStor SCSI support",
1403 below. You should say Y to both only if you want 24F support as
1406 To compile this driver as a module, choose M here: the
1407 module will be called u14-34f.
1409 config SCSI_U14_34F_TAGGED_QUEUE
1410 bool "enable tagged command queueing"
1411 depends on SCSI_U14_34F
1413 This is a feature of SCSI-2 which improves performance: the host
1414 adapter can send several SCSI commands to a device's queue even if
1415 previous commands haven't finished yet.
1416 This is equivalent to the "u14-34f=tc:y" boot option.
1418 config SCSI_U14_34F_LINKED_COMMANDS
1419 bool "enable elevator sorting"
1420 depends on SCSI_U14_34F
1422 This option enables elevator sorting for all probed SCSI disks and
1423 CD-ROMs. It definitely reduces the average seek distance when doing
1424 random seeks, but this does not necessarily result in a noticeable
1425 performance improvement: your mileage may vary...
1426 This is equivalent to the "u14-34f=lc:y" boot option.
1428 config SCSI_U14_34F_MAX_TAGS
1429 int "maximum number of queued commands"
1430 depends on SCSI_U14_34F
1433 This specifies how many SCSI commands can be maximally queued for
1434 each probed SCSI device. You should reduce the default value of 8
1435 only if you have disks with buggy or limited tagged command support.
1436 Minimum is 2 and maximum is 14. This value is also the window size
1437 used by the elevator sorting option above. The effective value used
1438 by the driver for each probed SCSI device is reported at boot time.
1439 This is equivalent to the "u14-34f=mq:8" boot option.
1441 config SCSI_ULTRASTOR
1442 tristate "UltraStor SCSI support"
1443 depends on X86 && ISA && SCSI
1445 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1446 adapter family. This driver is explained in section 3.12 of the
1447 SCSI-HOWTO, available from
1448 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1449 of the box, you may have to change some settings in
1450 <file:drivers/scsi/ultrastor.h>.
1452 Note that there is also another driver for the same hardware:
1453 "UltraStor 14F/34F support", above.
1455 To compile this driver as a module, choose M here: the
1456 module will be called ultrastor.
1459 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1460 depends on PCI && SCSI && !64BIT
1462 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1463 SCSI host adapter. Please read the SCSI-HOWTO, available from
1464 <http://www.tldp.org/docs.html#howto>.
1466 To compile this driver as a module, choose M here: the
1467 module will be called nsp32.
1470 tristate "SCSI debugging host simulator"
1473 This is a host adapter simulator that can simulate multiple hosts
1474 each with multiple dummy SCSI devices (disks). It defaults to one
1475 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1476 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1477 dummy disks are simulated, they share the same kernel RAM for
1478 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1479 information. This driver is primarily of use to those testing the
1480 SCSI and block subsystems. If unsure, say N.
1483 tristate "MESH (Power Mac internal SCSI) support"
1484 depends on PPC32 && PPC_PMAC && SCSI
1486 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1487 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1488 other Power Macintoshes do). Say Y to include support for this SCSI
1491 To compile this driver as a module, choose M here: the
1492 module will be called mesh.
1494 config SCSI_MESH_SYNC_RATE
1495 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1496 depends on SCSI_MESH
1499 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1500 drives a bus which is entirely internal to the machine (such as the
1501 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1502 operation at up to 10 MB/s. On machines where the SCSI bus
1503 controlled by the MESH can have external devices connected, it is
1504 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1505 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1506 to disable synchronous operation.
1508 config SCSI_MESH_RESET_DELAY_MS
1509 int "initial bus reset delay (ms) (0 = no reset)"
1510 depends on SCSI_MESH
1513 config SCSI_MAC53C94
1514 tristate "53C94 (Power Mac external SCSI) support"
1515 depends on PPC32 && PPC_PMAC && SCSI
1517 On Power Macintoshes (and clones) with two SCSI buses, the external
1518 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1519 machines which only have one SCSI bus, such as the 7200, also use
1520 the 53C94. Say Y to include support for the 53C94.
1522 To compile this driver as a module, choose M here: the
1523 module will be called mac53c94.
1525 source "drivers/scsi/arm/Kconfig"
1528 bool "MIPS JAZZ FAS216 SCSI support"
1529 depends on MACH_JAZZ && SCSI
1531 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1532 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1536 tristate "A3000 WD33C93A support"
1537 depends on AMIGA && SCSI
1539 If you have an Amiga 3000 and have SCSI devices connected to the
1540 built-in SCSI controller, say Y. Otherwise, say N.
1542 To compile this driver as a module, choose M here: the
1543 module will be called wd33c93.
1546 tristate "A2091/A590 WD33C93A support"
1547 depends on ZORRO && SCSI
1549 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1552 To compile this driver as a module, choose M here: the
1553 module will be called wd33c93.
1556 tristate "GVP Series II WD33C93A support"
1557 depends on ZORRO && SCSI
1559 If you have a Great Valley Products Series II SCSI controller,
1560 answer Y. Also say Y if you have a later model of GVP SCSI
1561 controller (such as the GVP A4008 or a Combo board). Otherwise,
1562 answer N. This driver does NOT work for the T-Rex series of
1563 accelerators from TekMagic and GVP-M.
1565 To compile this driver as a module, choose M here: the
1566 module will be called gvp11.
1568 config CYBERSTORM_SCSI
1569 tristate "CyberStorm SCSI support"
1570 depends on ZORRO && SCSI
1572 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1573 accelerator board and the optional Cyberstorm SCSI controller,
1574 answer Y. Otherwise, say N.
1576 config CYBERSTORMII_SCSI
1577 tristate "CyberStorm Mk II SCSI support"
1578 depends on ZORRO && SCSI
1580 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1581 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1585 tristate "Blizzard 2060 SCSI support"
1586 depends on ZORRO && SCSI
1588 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1589 and want to use the onboard SCSI controller, say Y. Otherwise,
1593 tristate "Blizzard 1230IV/1260 SCSI support"
1594 depends on ZORRO && SCSI
1596 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1597 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1600 config FASTLANE_SCSI
1601 tristate "Fastlane SCSI support"
1602 depends on ZORRO && SCSI
1604 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1605 one in the near future, say Y to this question. Otherwise, say N.
1607 config SCSI_AMIGA7XX
1608 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1609 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1611 Support for various NCR53c710-based SCSI controllers on the Amiga.
1613 - the builtin SCSI controller on the Amiga 4000T,
1614 - the Amiga 4091 Zorro III SCSI-2 controller,
1615 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1617 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1618 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1619 accelerator card for the Amiga 1200,
1620 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1621 Note that all of the above SCSI controllers, except for the builtin
1622 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1623 bus, so you also have to enable Zorro bus support if you want to use
1627 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1628 depends on ZORRO && SCSI && EXPERIMENTAL
1630 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1631 Y to this question. If you're in doubt about whether you have one,
1633 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1636 tristate "Atari native SCSI support"
1637 depends on ATARI && SCSI && BROKEN
1638 select SCSI_SPI_ATTRS
1640 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1641 Falcon, ...) say Y to get it supported. Of course also, if you have
1642 a compatible SCSI controller (e.g. for Medusa).
1644 To compile this driver as a module, choose M here: the
1645 module will be called atari_scsi.
1647 This driver supports both styles of NCR integration into the
1648 system: the TT style (separate DMA), and the Falcon style (via
1649 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1650 in the Hades (without DMA).
1652 config ATARI_SCSI_TOSHIBA_DELAY
1653 bool "Long delays for Toshiba CD-ROMs"
1654 depends on ATARI_SCSI
1656 This option increases the delay after a SCSI arbitration to
1657 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1658 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1659 would impact performance a bit, so say N.
1661 config ATARI_SCSI_RESET_BOOT
1662 bool "Reset SCSI-devices at boottime"
1663 depends on ATARI_SCSI
1665 Reset the devices on your Atari whenever it boots. This makes the
1666 boot process fractionally longer but may assist recovery from errors
1667 that leave the devices with SCSI operations partway completed.
1670 bool "Hades SCSI DMA emulator"
1671 depends on ATARI_SCSI && HADES
1673 This option enables code which emulates the TT SCSI DMA chip on the
1674 Hades. This increases the SCSI transfer rates at least ten times
1675 compared to PIO transfers.
1678 bool "Macintosh NCR5380 SCSI"
1679 depends on MAC && SCSI=y
1680 select SCSI_SPI_ATTRS
1682 This is the NCR 5380 SCSI controller included on most of the 68030
1683 based Macintoshes. If you have one of these say Y and read the
1684 SCSI-HOWTO, available from
1685 <http://www.tldp.org/docs.html#howto>.
1688 tristate "Macintosh NCR53c9[46] SCSI"
1689 depends on MAC && SCSI
1691 This is the NCR 53c9x SCSI controller found on most of the 68040
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>.
1696 To compile this driver as a module, choose M here: the
1697 module will be called mac_esp.
1700 bool "WD33C93 SCSI driver for MVME147"
1701 depends on MVME147 && SCSI=y
1702 select SCSI_SPI_ATTRS
1704 Support for the on-board SCSI controller on the Motorola MVME147
1705 single-board computer.
1708 bool "NCR53C710 SCSI driver for MVME16x"
1709 depends on MVME16x && SCSI && BROKEN
1710 select SCSI_SPI_ATTRS
1712 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1713 SCSI controller chip. Almost everyone using one of these boards
1714 will want to say Y to this question.
1716 config BVME6000_SCSI
1717 bool "NCR53C710 SCSI driver for BVME6000"
1718 depends on BVME6000 && SCSI && BROKEN
1719 select SCSI_SPI_ATTRS
1721 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1722 SCSI controller chip. Almost everyone using one of these boards
1723 will want to say Y to this question.
1725 config SCSI_NCR53C7xx_FAST
1726 bool "allow FAST-SCSI [10MHz]"
1727 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1729 This will enable 10MHz FAST-SCSI transfers with your host
1730 adapter. Some systems have problems with that speed, so it's safest
1734 tristate "Sun3 NCR5380 SCSI"
1735 depends on SUN3 && SCSI && BROKEN
1736 select SCSI_SPI_ATTRS
1738 This option will enable support for the OBIO (onboard io) NCR5380
1739 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1740 "Sun3" type VME scsi controllers also based on the NCR5380.
1741 General Linux information on the Sun 3 series (now discontinued)
1742 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1745 bool "Sun3x ESP SCSI"
1746 depends on SUN3X && SCSI=y
1748 The ESP was an on-board SCSI controller used on Sun 3/80
1749 machines. Say Y here to compile in support for it.
1752 tristate "Sparc ESP Scsi Driver"
1753 depends on SBUS && SCSI
1755 This is the driver for the Sun ESP SCSI host adapter. The ESP
1756 chipset is present in most SPARC SBUS-based computers.
1758 To compile this driver as a module, choose M here: the
1759 module will be called esp.
1761 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1764 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1765 depends on S390 && QDIO && SCSI
1766 select SCSI_FC_ATTRS
1768 If you want to access SCSI devices attached to your IBM eServer
1769 zSeries by means of Fibre Channel interfaces say Y.
1770 For details please refer to the documentation provided by IBM at
1771 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1773 This driver is also available as a module. This module will be
1774 called zfcp. If you want to compile it as a module, say M here
1775 and read <file:Documentation/modules.txt>.
1778 tristate "SCSI RDMA Protocol helper library"
1779 depends on SCSI && PCI
1782 If you wish to use SRP target drivers, say Y.
1784 To compile this driver as a module, choose M here: the
1785 module will be called libsrp.
1789 source "drivers/scsi/pcmcia/Kconfig"