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