1 comment "SCSI support type (disk, tape, CD-ROM)"
5 tristate "SCSI disk support"
8 If you want to use a SCSI hard disk or the SCSI or parallel port
9 version of the IOMEGA ZIP drive under Linux, say Y and read the
10 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
11 <http://www.linuxdoc.org/docs.html#howto>. This is NOT for SCSI
14 This driver is also available as a module ( = code which can be
15 inserted in and removed from the running kernel whenever you want).
16 The module will be called sd_mod.o. If you want to compile it as a
17 module, say M here and read <file:Documentation/modules.txt> and
18 <file:Documentation/scsi/scsi.txt>. Do not compile this driver as a
19 module if your root file system (the one containing the directory /)
20 is located on a SCSI disk. In this case, do not compile the driver
21 for your SCSI host adapter (below) as a module either.
24 tristate "SCSI tape support"
27 If you want to use a SCSI tape drive under Linux, say Y and read the
28 SCSI-HOWTO, available from
29 <http://www.linuxdoc.org/docs.html#howto>, and
30 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT for
33 This driver is also available as a module ( = code which can be
34 inserted in and removed from the running kernel whenever you want).
35 The module will be called st.o. If you want to compile it as a
36 module, say M here and read <file:Documentation/modules.txt> and
37 <file:Documentation/scsi/scsi.txt>.
40 tristate "SCSI OnStream SC-x0 tape support"
43 The OnStream SC-x0 SCSI tape drives can not be driven by the
44 standard st driver, but instead need this special osst driver and
45 use the /dev/osstX char device nodes (major 206). Via usb-storage
46 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
47 as well. Note that there is also a second generation of OnStream
48 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
49 tapes (QIC-157) and can be driven by the standard driver st.
50 For more information, you may have a look at the SCSI-HOWTO
51 <http://www.linuxdoc.org/docs.html#howto> and
52 <file:Documentation/scsi/osst.txt> in the kernel source.
53 More info on the OnStream driver may be found on
54 <http://linux1.onstream.nl/test/>
55 Please also have a look at the standard st docu, as most of it
56 applies to osst as well.
58 This driver is also available as a module ( = code which can be
59 inserted in and removed from the running kernel whenever you want).
60 The module will be called osst.o. If you want to compile it as a
61 module, say M here and read <file:Documentation/modules.txt> and
62 <file:Documentation/scsi/scsi.txt>.
65 tristate "SCSI CDROM support"
68 If you want to use a SCSI CD-ROM under Linux, say Y and read the
69 SCSI-HOWTO and the CD-ROM-HOWTO at
70 <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
71 or M to "ISO 9660 CD-ROM file system support" later.
73 This driver is also available as a module ( = code which can be
74 inserted in and removed from the running kernel whenever you want).
75 The module will be called sr_mod.o. If you want to compile it as a
76 module, say M here and read <file:Documentation/modules.txt> and
77 <file:Documentation/scsi/scsi.txt>.
79 config BLK_DEV_SR_VENDOR
80 bool "Enable vendor-specific extensions (for SCSI CDROM)"
83 This enables the usage of vendor specific SCSI commands. This is
84 required to support multisession CDs with old NEC/TOSHIBA cdrom
85 drives (and HP Writers). If you have such a drive and get the first
86 session only, try saying Y here; everybody else says N.
89 tristate "SCSI generic support"
92 If you want to use SCSI scanners, synthesizers or CD-writers or just
93 about anything having "SCSI" in its name other than hard disks,
94 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
95 directly, so you need some additional software which knows how to
96 talk to these devices using the SCSI protocol:
98 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
99 writer software look at Cdrtools
100 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
101 and for burning a "disk at once": CDRDAO
102 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
103 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
104 For other devices, it's possible that you'll have to write the
105 driver software yourself. Please read the file
106 <file:Documentation/scsi/scsi-generic.txt> for more information.
108 If you want to compile this as a module ( = code which can be
109 inserted in and removed from the running kernel whenever you want),
110 say M here and read <file:Documentation/modules.txt> and
111 <file:Documentation/scsi/scsi.txt>. The module will be called sg.o.
114 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
117 config SCSI_MULTI_LUN
118 bool "Probe all LUNs on each SCSI device"
121 If you have a SCSI device that supports more than one LUN (Logical
122 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
123 can say Y here to force the SCSI driver to probe for multiple LUNs.
124 A SCSI device with multiple LUNs acts logically like multiple SCSI
125 devices. The vast majority of SCSI devices have only one LUN, and
126 so most people can say N here and should in fact do so, because it
129 config SCSI_REPORT_LUNS
130 bool "Build with SCSI REPORT LUNS support"
133 If you want to build with SCSI REPORT LUNS support in the kernel, say Y here.
134 The REPORT LUNS command is useful for devices (such as disk arrays) with
135 large numbers of LUNs where the LUN values are not contiguous (sparse LUN).
136 REPORT LUNS scanning is done only for SCSI-3 devices. Most users can safely
139 config SCSI_CONSTANTS
140 bool "Verbose SCSI error reporting (kernel size +=12K)"
143 The error messages regarding your SCSI hardware will be easier to
144 understand if you say Y here; it will enlarge your kernel by about
145 12 KB. If in doubt, say Y.
148 bool "SCSI logging facility"
151 This turns on a logging facility that can be used to debug a number
152 of SCSI related problems.
154 If you say Y here, no logging output will appear by default, but you
155 can enable logging by saying Y to "/proc file system support" and
156 "Sysctl support" below and executing the command
158 echo "scsi log token [level]" > /proc/scsi/scsi
160 at boot time after the /proc file system has been mounted.
162 There are a number of things that can be used for 'token' (you can
163 find them in the source: <file:drivers/scsi/scsi.c>), and this
164 allows you to select the types of information you want, and the
165 level allows you to select the level of verbosity.
167 If you say N here, it may be harder to track down some types of SCSI
168 problems. If you say Y here your kernel will be somewhat larger, but
169 there should be no noticeable performance impact as long as you have
173 menu "SCSI low-level drivers"
177 tristate "SGI WD93C93 SCSI Driver"
178 depends on SGI_IP22 && SCSI
181 tristate "DEC NCR53C94 Scsi Driver"
182 depends on DECSTATION && SCSI && TC
184 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
185 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
188 tristate "DEC SII Scsi Driver"
189 depends on DECSTATION && SCSI && MIPS32
191 config BLK_DEV_3W_XXXX_RAID
192 tristate "3ware Hardware ATA-RAID support"
193 depends on PCI && SCSI
195 3ware is the only hardware ATA-Raid product in Linux to date.
196 This card is 2,4, or 8 channel master mode support only.
197 SCSI support required!!!
199 <http://www.3ware.com/>
201 Please read the comments at the top of
202 <file:drivers/scsi/3w-xxxx.c>.
204 config SCSI_7000FASST
205 tristate "7000FASST SCSI support"
206 depends on SCSI && ISA
208 This driver supports the Western Digital 7000 SCSI host adapter
209 family. Some information is in the source:
210 <file:drivers/scsi/wd7000.c>.
212 This driver is also available as a module ( = code which can be
213 inserted in and removed from the running kernel whenever you want).
214 The module will be called wd7000.o. If you want to compile it as a
215 module, say M here and read <file:Documentation/modules.txt>.
218 tristate "ACARD SCSI support"
221 This driver supports the ACARD 870U/W SCSI host adapter.
223 This driver is also available as a module ( = code which can be
224 inserted in and removed from the running kernel whenever you want).
225 The module will be called atp870u.o. If you want to compile it as a
226 module, say M here and read <file:Documentation/modules.txt>.
229 tristate "Adaptec AHA152X/2825 support"
230 depends on ISA && SCSI
232 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
233 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
234 must be manually specified in this case.
236 It is explained in section 3.3 of the SCSI-HOWTO, available from
237 <http://www.linuxdoc.org/docs.html#howto>. You might also want to
238 read the file <file:Documentation/scsi/aha152x.txt>.
240 This driver is also available as a module ( = code which can be
241 inserted in and removed from the running kernel whenever you want).
242 The module will be called aha152x.o. If you want to compile it as a
243 module, say M here and read <file:Documentation/modules.txt>.
246 tristate "Adaptec AHA1542 support"
247 depends on ISA && SCSI
249 This is support for a SCSI host adapter. It is explained in section
250 3.4 of the SCSI-HOWTO, available from
251 <http://www.linuxdoc.org/docs.html#howto>. Note that Trantor was
252 purchased by Adaptec, and some former Trantor products are being
253 sold under the Adaptec name. If it doesn't work out of the box, you
254 may have to change some settings in <file:drivers/scsi/aha1542.h>.
256 If you want to compile this as a module ( = code which can be
257 inserted in and removed from the running kernel whenever you want),
258 say M here and read <file:Documentation/modules.txt>. The module
259 will be called aha1542.o.
262 tristate "Adaptec AHA1740 support"
263 depends on EISA && SCSI
265 This is support for a SCSI host adapter. It is explained in section
266 3.5 of the SCSI-HOWTO, available from
267 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
268 of the box, you may have to change some settings in
269 <file:drivers/scsi/aha1740.h>.
271 This driver is also available as a module ( = code which can be
272 inserted in and removed from the running kernel whenever you want).
273 The module will be called aha1740.o. If you want to compile it as a
274 module, say M here and read <file:Documentation/modules.txt>.
277 tristate "Adaptec AACRAID support (EXPERIMENTAL)"
278 depends on EXPERIMENTAL && SCSI && PCI
281 prompt "Adaptec AIC7xxx support"
285 source "drivers/scsi/aic7xxx/Kconfig"
287 config SCSI_AIC7XXX_OLD
288 tristate "Old driver"
290 WARNING This driver is an older aic7xxx driver and is no longer
291 under active development. Adaptec, Inc. is writing a new driver to
292 take the place of this one, and it is recommended that whenever
293 possible, people should use the new Adaptec written driver instead
294 of this one. This driver will eventually be phased out entirely.
296 This is support for the various aic7xxx based Adaptec SCSI
297 controllers. These include the 274x EISA cards; 284x VLB cards;
298 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
299 motherboard based SCSI controllers from Adaptec. It does not support
300 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
301 support them. It does not support the 2920 cards from Adaptec that
302 use the Future Domain SCSI controller chip. For those cards, you
303 need the "Future Domain 16xx SCSI support" driver.
305 In general, if the controller is based on an Adaptec SCSI controller
306 chip from the aic777x series or the aic78xx series, this driver
307 should work. The only exception is the 7810 which is specifically
308 not supported (that's the RAID controller chip on the AAA-13x
311 Note that the AHA2920 SCSI host adapter is *not* supported by this
312 driver; choose "Future Domain 16xx SCSI support" instead if you have
315 Information on the configuration options for this controller can be
316 found by checking the help file for each of the available
317 configuration options. You should read
318 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
319 contacting the maintainer with any questions. The SCSI-HOWTO,
320 available from <http://www.linuxdoc.org/docs.html#howto>, can also
323 If you want to compile this driver as a module ( = code which can be
324 inserted in and removed from the running kernel whenever you want),
325 say M here and read <file:Documentation/modules.txt>. The module
326 will be called aic7xxx_old.o.
331 # All the I2O code and drivers do not seem to be 64bit safe.
333 tristate "Adaptec I2O RAID support "
334 depends on !X86_64 && SCSI
336 This driver supports all of Adaptec's I2O based RAID controllers as
337 well as the DPT SmartRaid V cards. This is an Adaptec maintained
338 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
340 This driver is also available as a module ( = code which can be
341 inserted in and removed from the running kernel whenever you want).
342 If you want to compile it as a module, say M here and read
343 <file:Documentation/modules.txt>. The module will be called
347 tristate "AdvanSys SCSI support"
350 This is a driver for all SCSI host adapters manufactured by
351 AdvanSys. It is documented in the kernel source in
352 <file:drivers/scsi/advansys.c>.
354 This driver is also available as a module ( = code which can be
355 inserted in and removed from the running kernel whenever you want).
356 If you want to compile it as a module, say M here and read
357 <file:Documentation/modules.txt>. The module will be called
361 tristate "Always IN2000 SCSI support"
364 This is support for an ISA bus SCSI host adapter. You'll find more
365 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
366 out of the box, you may have to change the jumpers for IRQ or
369 If you want to compile this as a module ( = code which can be
370 inserted in and removed from the running kernel whenever you want),
371 say M here and read <file:Documentation/modules.txt>. The module
372 will be called in2000.o.
374 # does not use pci dma and seems to be isa/onboard only for old machines
376 tristate "AM53/79C974 PCI SCSI support"
377 depends on !X86_64 && SCSI && PCI
379 This is support for the AM53/79C974 SCSI host adapters. Please read
380 <file:Documentation/scsi/AM53C974.txt> for details. Also, the
381 SCSI-HOWTO, available from
382 <http://www.linuxdoc.org/docs.html#howto>, is for you.
384 Note that there is another driver for AM53C974 based adapters:
385 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
388 If you want to compile this driver as a module ( = code which can be
389 inserted in and removed from the running kernel whenever you want),
390 say M here and read <file:Documentation/modules.txt>. The module
391 will be called AM53C974.o.
394 tristate "AMI MegaRAID support"
397 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
398 and 467 SCSI host adapters.
400 If you want to compile this driver as a module ( = code which can be
401 inserted in and removed from the running kernel whenever you want),
402 say M here and read <file:Documentation/modules.txt>. The module
403 will be called megaraid.o.
406 tristate "BusLogic SCSI support"
409 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
410 Adapters. Consult the SCSI-HOWTO, available from
411 <http://www.linuxdoc.org/docs.html#howto>, and the files
412 <file:Documentation/scsi/BusLogic.txt> and
413 <file:Documentation/scsi/FlashPoint.txt> for more information. If this
414 driver does not work correctly without modification, please contact
415 the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
417 You can also build this driver as a module ( = code which can be
418 inserted in and removed from the running kernel whenever you want),
419 but only a single instance may be loaded. If you want to compile it
420 as a module, say M here and read <file:Documentation/modules.txt>.
421 The module will be called BusLogic.o.
423 config SCSI_OMIT_FLASHPOINT
424 bool "Omit FlashPoint support"
425 depends on SCSI_BUSLOGIC
427 This option allows you to omit the FlashPoint support from the
428 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
429 substantial, so users of MultiMaster Host Adapters may wish to omit
433 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
434 depends on PCI && SCSI
436 Say Y here to compile in support for the Compaq StorageWorks Fibre
437 Channel 64-bit/66Mhz Host Bus Adapter.
440 tristate "DMX3191D SCSI support"
441 depends on SCSI && PCI
443 This is support for Domex DMX3191D SCSI Host Adapters.
445 This driver is also available as a module ( = code which can be
446 inserted in and removed from the running kernel whenever you want).
447 The module will be called dmx3191d.o. If you want to compile it as
448 a module, say M here and read <file:Documentation/modules.txt>.
451 tristate "DTC3180/3280 SCSI support"
452 depends on SCSI && ISA
454 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
455 the SCSI-HOWTO, available from
456 <http://www.linuxdoc.org/docs.html#howto>, and the file
457 <file:Documentation/scsi/dtc3x80.txt>.
459 This driver is also available as a module ( = code which can be
460 inserted in and removed from the running kernel whenever you want).
461 The module will be called dtc.o. If you want to compile it as a
462 module, say M here and read <file:Documentation/modules.txt>.
465 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
468 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
469 ISA and all EISA I/O addresses are probed looking for the "EATA"
470 signature. If you chose "BIOS" at the question "PCI access mode",
471 the addresses of all the PCI SCSI controllers reported by the PCI
472 subsystem are probed as well.
474 You want to read the start of <file:drivers/scsi/eata.c> and the
475 SCSI-HOWTO, available from
476 <http://www.linuxdoc.org/docs.html#howto>.
478 Note that there is also another driver for the same hardware
479 available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
480 Alphatronix) support". You should say Y to only one of them.
482 If you want to compile this as a module ( = code which can be
483 inserted in and removed from the running kernel whenever you want),
484 say M here and read <file:Documentation/modules.txt>. The module
485 will be called eata.o.
487 config SCSI_EATA_TAGGED_QUEUE
488 bool "enable tagged command queueing"
491 This is a feature of SCSI-2 which improves performance: the host
492 adapter can send several SCSI commands to a device's queue even if
493 previous commands haven't finished yet. Most EATA adapters negotiate
494 this feature automatically with the device, even if your answer is
495 N. The safe answer is N.
497 config SCSI_EATA_LINKED_COMMANDS
498 bool "enable elevator sorting"
501 This option enables elevator sorting for all probed SCSI disks and
502 CD-ROMs. It definitely reduces the average seek distance when doing
503 random seeks, but this does not necessarily result in a noticeable
504 performance improvement: your mileage may vary...
505 The safe answer is N.
507 config SCSI_EATA_MAX_TAGS
508 int "maximum number of queued commands"
512 This specifies how many SCSI commands can be maximally queued for
513 each probed SCSI device. You should reduce the default value of 16
514 only if you have disks with buggy or limited tagged command support.
515 Minimum is 2 and maximum is 62. This value is also the window size
516 used by the elevator sorting option above. The effective value used
517 by the driver for each probed SCSI device is reported at boot time.
520 tristate "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support"
523 This is support for the EATA-DMA protocol compliant SCSI Host
524 Adapters like the SmartCache III/IV, SmartRAID controller families
525 and the DPT PM2011B and PM2012B controllers.
527 Note that this driver is obsolete; if you have one of the above
528 SCSI Host Adapters, you should normally say N here and Y to "EATA
529 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
530 from <http://www.linuxdoc.org/docs.html#howto>.
532 This driver is also available as a module ( = code which can be
533 inserted in and removed from the running kernel whenever you want).
534 The module will be called eata_dma.o. If you want to compile it as
535 a module, say M here and read <file:Documentation/modules.txt>.
538 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
541 This driver supports all EATA-PIO protocol compliant SCSI Host
542 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
543 host adapters could also use this driver but are discouraged from
544 doing so, since this driver only supports hard disks and lacks
545 numerous features. You might want to have a look at the SCSI-HOWTO,
546 available from <http://www.linuxdoc.org/docs.html#howto>.
548 If you want to compile this as a module ( = code which can be
549 inserted in and removed from the running kernel whenever you want),
550 say M here and read <file:Documentation/modules.txt>. The module
551 will be called eata_pio.o.
553 config SCSI_FUTURE_DOMAIN
554 tristate "Future Domain 16xx SCSI/AHA-2920A support"
557 This is support for Future Domain's 16-bit SCSI host adapters
558 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
559 other adapters based on the Future Domain chipsets (Quantum
560 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
561 It is explained in section 3.7 of the SCSI-HOWTO, available from
562 <http://www.linuxdoc.org/docs.html#howto>.
564 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
565 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
566 controller support"). This Future Domain driver works with the older
567 Adaptec AHA-2920A boards with a Future Domain chip on them.
569 This driver is also available as a module ( = code which can be
570 inserted in and removed from the running kernel whenever you want).
571 The module will be called fdomain.o. If you want to compile it as a
572 module, say M here and read <file:Documentation/modules.txt>.
575 tristate "Future Domain MCS-600/700 SCSI support"
576 depends on MCA && SCSI
578 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
579 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
580 is identical to the MCS 700 and hence also supported by this driver.
581 This driver also supports the Reply SB16/SCSI card (the SCSI part).
582 It supports multiple adapters in the same system.
584 This driver is also available as a module ( = code which can be
585 inserted in and removed from the running kernel whenever you want).
586 The module will be called fd_mcs.o. If you want to compile it as a
587 module, say M here and read <file:Documentation/modules.txt>.
590 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
593 Formerly called GDT SCSI Disk Array Controller Support.
595 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
596 manufactured by Intel/ICP vortex (an Intel Company). It is documented
597 in the kernel source in <file:drivers/scsi/gdth.c> and
598 <file:drivers/scsi/gdth.h.>
600 This driver is also available as a module ( = code which can be
601 inserted in and removed from the running kernel whenever you want).
602 If you want to compile it as a module, say M here and read
603 <file:Documentation/modules.txt>.
605 config SCSI_GENERIC_NCR5380
606 tristate "Generic NCR5380/53c400 SCSI PIO support"
609 This is a driver for the old NCR 53c80 series of SCSI controllers
610 on boards using PIO. Most boards such as the Trantor T130 fit this
611 category, along with a large number of ISA 8bit controllers shipped
612 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
613 you should select the specific driver for that card rather than
614 generic 5380 support.
616 It is explained in section 3.8 of the SCSI-HOWTO, available from
617 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
618 of the box, you may have to change some settings in
619 <file:drivers/scsi/g_NCR5380.h>.
621 This driver is also available as a module ( = code which can be
622 inserted in and removed from the running kernel whenever you want).
623 The module will be called g_NCR5380.o. If you want to compile it as
624 a module, say M here and read <file:Documentation/modules.txt>.
626 config SCSI_GENERIC_NCR5380_MMIO
627 tristate "Generic NCR5380/53c400 SCSI MMIO support"
630 This is a driver for the old NCR 53c80 series of SCSI controllers
631 on boards using memory mapped I/O.
632 It is explained in section 3.8 of the SCSI-HOWTO, available from
633 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
634 of the box, you may have to change some settings in
635 <file:drivers/scsi/g_NCR5380.h>.
637 This driver is also available as a module ( = code which can be
638 inserted in and removed from the running kernel whenever you want).
639 The module will be called g_NCR5380.o. If you want to compile it as
640 a module, say M here and read <file:Documentation/modules.txt>.
642 config SCSI_GENERIC_NCR53C400
643 bool "Enable NCR53c400 extensions"
644 depends on SCSI_GENERIC_NCR5380
646 This enables certain optimizations for the NCR53c400 SCSI cards.
647 You might as well try it out. Note that this driver will only probe
648 for the Trantor T130B in its default configuration; you might have
649 to pass a command line option to the kernel at boot time if it does
650 not detect your card. See the file
651 <file:Documentation/scsi/g_NCR5380.txt> for details.
654 tristate "IBMMCA SCSI support"
655 depends on MCA && SCSI
657 This is support for the IBM SCSI adapter found in many of the PS/2
658 series computers. These machines have an MCA bus, so you need to
659 answer Y to "MCA support" as well and read
660 <file:Documentation/mca.txt>.
662 If the adapter isn't found during boot (a common problem for models
663 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
664 option, where <pun> is the id of the SCSI subsystem (usually 7, but
665 if that doesn't work check your reference diskette). Owners of
666 model 95 with a LED-matrix-display can in addition activate some
667 activity info like under OS/2, but more informative, by setting
668 'ibmmcascsi=display' as an additional kernel parameter. Try "man
669 bootparam" or see the documentation of your boot loader about how to
670 pass options to the kernel.
672 If you want to compile this driver as a module ( = code which can be
673 inserted in and removed from the running kernel whenever you want),
674 say M here and read <file:Documentation/modules.txt>. The module
675 will be called ibmmca.o.
677 config IBMMCA_SCSI_ORDER_STANDARD
678 bool "Standard SCSI-order"
679 depends on SCSI_IBMMCA
681 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
682 are assigned to the drive letters, starting with the lowest SCSI-id
683 (physical number -- pun) to be drive C:, as seen from DOS and
684 similar operating systems. When looking into papers describing the
685 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
686 The SCSI-standard follows a hardware-hierarchy which says that id 7
687 has the highest priority and id 0 the lowest. Therefore, the host
688 adapters are still today everywhere placed as SCSI-id 7 by default.
689 In the SCSI-standard, the drive letters express the priority of the
690 disk. C: should be the hard disk, or a partition on it, with the
691 highest priority. This must therefore be the disk with the highest
692 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
693 original definition of the SCSI-standard as also industrial- and
694 process-control-machines, like VME-CPUs running under realtime-OSes
695 (e.g. LynxOS, OS9) do.
697 If you like to run Linux on your MCA-machine with the same
698 assignment of hard disks as seen from e.g. DOS or OS/2 on your
699 machine, which is in addition conformant to the SCSI-standard, you
700 must say Y here. This is also necessary for MCA-Linux users who want
701 to keep downward compatibility to older releases of the
702 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
705 If you like to have the lowest SCSI-id assigned as drive C:, as
706 modern SCSI-BIOSes do, which does not conform to the standard, but
707 is widespread and common in the PC-world of today, you must say N
708 here. If unsure, say Y.
710 config IBMMCA_SCSI_DEV_RESET
711 bool "Reset SCSI-devices at boottime"
712 depends on SCSI_IBMMCA
714 By default, SCSI-devices are reset when the machine is powered on.
715 However, some devices exist, like special-control-devices,
716 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
717 not reset when switched on. If you say Y here, each device connected
718 to your SCSI-bus will be issued a reset-command after it has been
719 probed, while the kernel is booting. This may cause problems with
720 more modern devices, like hard disks, which do not appreciate these
721 reset commands, and can cause your system to hang. So say Y only if
722 you know that one of your older devices needs it; N is the safe
726 tristate "IBM ServeRAID support"
727 depends on X86 && SCSI && PCI
729 This is support for the IBM ServeRAID hardware RAID controllers.
730 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
731 for more information. If this driver does not work correctly
732 without modification please contact the author by email at
735 You can build this driver as a module ( = code which can be
736 inserted in and removed from the running kernel whenever you want),
737 but only a single instance may be loaded. If you want to compile it
738 as a module, say M here and read <file:Documentation/modules.txt>.
739 The module will be called ips.o.
742 tristate "Initio 9100U(W) support"
743 depends on SCSI && PCI
745 This is support for the Initio 91XXU(W) SCSI host adapter. Please
746 read the SCSI-HOWTO, available from
747 <http://www.linuxdoc.org/docs.html#howto>.
749 If you want to compile this as a module ( = code which can be
750 inserted in and removed from the running kernel whenever you want),
751 say M here and read <file:Documentation/modules.txt>. The module
752 will be called initio.o.
755 tristate "Initio INI-A100U2W support"
756 depends on SCSI && PCI
758 This is support for the Initio INI-A100U2W SCSI host adapter.
759 Please read the SCSI-HOWTO, available from
760 <http://www.linuxdoc.org/docs.html#howto>.
762 If you want to compile this as a module ( = code which can be
763 inserted in and removed from the running kernel whenever you want),
764 say M here and read <file:Documentation/modules.txt>. The module
765 will be called a100u2w.o.
768 tristate "IOMEGA parallel port (ppa - older drives)"
769 depends on SCSI && PARPORT
771 This driver supports older versions of IOMEGA's parallel port ZIP
772 drive (a 100 MB removable media device).
774 Note that you can say N here if you have the SCSI version of the ZIP
775 drive: it will be supported automatically if you said Y to the
776 generic "SCSI disk support", above.
778 If you have the ZIP Plus drive or a more recent parallel port ZIP
779 drive (if the supplied cable with the drive is labeled "AutoDetect")
780 then you should say N here and Y to "IOMEGA parallel port (imm -
781 newer drives)", below.
783 For more information about this driver and how to use it you should
784 read the file <file:Documentation/scsi/ppa.txt>. You should also read
785 the SCSI-HOWTO, which is available from
786 <http://www.linuxdoc.org/docs.html#howto>. If you use this driver,
787 you will still be able to use the parallel port for other tasks,
788 such as a printer; it is safe to compile both drivers into the
791 This driver is also available as a module which can be inserted in
792 and removed from the running kernel whenever you want. To compile
793 this driver as a module, say M here and read
794 <file:Documentation/modules.txt>. The module will be called ppa.o.
797 tristate "IOMEGA parallel port (imm - newer drives)"
798 depends on SCSI && PARPORT
800 This driver supports newer versions of IOMEGA's parallel port ZIP
801 drive (a 100 MB removable media device).
803 Note that you can say N here if you have the SCSI version of the ZIP
804 drive: it will be supported automatically if you said Y to the
805 generic "SCSI disk support", above.
807 If you have the ZIP Plus drive or a more recent parallel port ZIP
808 drive (if the supplied cable with the drive is labeled "AutoDetect")
809 then you should say Y here; if you have an older ZIP drive, say N
810 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
812 For more information about this driver and how to use it you should
813 read the file <file:Documentation/scsi/ppa.txt>. You should also read
814 the SCSI-HOWTO, which is available from
815 <http://www.linuxdoc.org/docs.html#howto>. If you use this driver,
816 you will still be able to use the parallel port for other tasks,
817 such as a printer; it is safe to compile both drivers into the
820 This driver is also available as a module which can be inserted in
821 and removed from the running kernel whenever you want. To compile
822 this driver as a module, say M here and read
823 <file:Documentation/modules.txt>. The module will be called imm.o.
825 config SCSI_IZIP_EPP16
826 bool "ppa/imm option - Use slow (but safe) EPP-16"
827 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
829 EPP (Enhanced Parallel Port) is a standard for parallel ports which
830 allows them to act as expansion buses that can handle up to 64
833 Some parallel port chipsets are slower than their motherboard, and
834 so we have to control the state of the chipset's FIFO queue every
835 now and then to avoid data loss. This will be done if you say Y
838 Generally, saying Y is the safe option and slows things down a bit.
840 config SCSI_IZIP_SLOW_CTR
841 bool "ppa/imm option - Assume slow parport control register"
842 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
844 Some parallel ports are known to have excessive delays between
845 changing the parallel port control register and good data being
846 available on the parallel port data/status register. This option
847 forces a small delay (1.0 usec to be exact) after changing the
848 control register to let things settle out. Enabling this option may
849 result in a big drop in performance but some very old parallel ports
850 (found in 386 vintage machines) will not work properly.
852 Generally, saying N is fine.
854 config SCSI_NCR53C406A
855 tristate "NCR53c406a SCSI support"
856 depends on SCSI && ISA
858 This is support for the NCR53c406a SCSI host adapter. For user
859 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
860 in the kernel source. Also read the SCSI-HOWTO, available from
861 <http://www.linuxdoc.org/docs.html#howto>.
863 If you want to compile this driver as a module ( = code which can be
864 inserted in and removed from the running kernel whenever you want),
865 say M here and read <file:Documentation/modules.txt>. The module
866 will be called NCR53c406.o.
869 tristate "NCR Dual 700 MCA SCSI support"
870 depends on MCA && SCSI
872 This is a driver for the MicroChannel Dual 700 card produced by
873 NCR and commonly used in 345x/35xx/4100 class machines. It always
874 tries to negotiate sync and uses tag command queueing.
876 Unless you have an NCR manufactured machine, the chances are that
877 you do not have this SCSI card, so say N.
879 config 53C700_IO_MAPPED
881 depends on SCSI_NCR_D700
885 tristate "HP LASI SCSI support for 53c700/710"
886 depends on PARISC && SCSI
888 This is a driver for the lasi baseboard in some parisc machines
889 which is based on the 53c700 chip. Will also support LASI subsystems
890 based on the 710 chip using 700 emulation mode.
892 Unless you know you have a 53c700 or 53c710 based lasi, say N here
894 config 53C700_MEM_MAPPED
896 depends on SCSI_LASI700
899 config 53C700_LE_ON_BE
901 depends on SCSI_LASI700
904 config 53C700_USE_CONSISTENT
906 depends on SCSI_LASI700
909 config SCSI_NCR53C7xx
910 tristate "NCR53c7,8xx SCSI support"
911 depends on SCSI && PCI
913 This is a driver for the 53c7 and 8xx NCR family of SCSI
914 controllers, not to be confused with the NCR 5380 controllers. It
915 is explained in section 3.8 of the SCSI-HOWTO, available from
916 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
917 of the box, you may have to change some settings in
918 <file:drivers/scsi/53c7,8xx.h>. Please read
919 <file:Documentation/scsi/ncr53c7xx.txt> for the available boot time
920 command line options.
922 Note: there is another driver for the 53c8xx family of controllers
923 ("NCR53C8XX SCSI support" below). If you want to use them both, you
924 need to say M to both and build them as modules, but only one may be
925 active at a time. If you have a 53c8xx board, it's better to use the
928 This driver is also available as a module ( = code which can be
929 inserted in and removed from the running kernel whenever you want).
930 The module will be called 53c7,8xx.o. If you want to compile it as
931 a module, say M here and read <file:Documentation/modules.txt>.
933 config SCSI_NCR53C7xx_sync
934 bool "always negotiate synchronous transfers"
935 depends on SCSI_NCR53C7xx
937 In general, this is good; however, it is a bit dangerous since there
938 are some broken SCSI devices out there. Take your chances. Safe bet
941 config SCSI_NCR53C7xx_FAST
942 bool "allow FAST-SCSI [10MHz]"
943 depends on SCSI_NCR53C7xx
945 This will enable 10MHz FAST-SCSI transfers with your host
946 adapter. Some systems have problems with that speed, so it's safest
949 config SCSI_NCR53C7xx_DISCONNECT
950 bool "allow DISCONNECT"
951 depends on SCSI_NCR53C7xx
953 This enables the disconnect/reconnect feature of the NCR SCSI
954 controller. When you say Y here, a slow SCSI device will not lock
955 the SCSI bus while processing a request, allowing simultaneous use
956 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
957 providing much better performance when using slow and fast SCSI
958 devices at the same time. Some devices, however, do not operate
959 properly with this option enabled, and will cause your SCSI system
960 to hang, which might cause a system crash. The safe answer
961 therefore is to say N.
963 config SCSI_SYM53C8XX_2
964 tristate "SYM53C8XX Version 2 SCSI support"
965 depends on PCI && SCSI
967 This driver supports the whole NCR53C8XX/SYM53C8XX family of
968 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
969 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
970 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
973 If your system has problems using this new major version of the
974 SYM53C8XX driver, you may switch back to driver version 1.
976 Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
979 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
980 int "DMA addressing mode"
981 depends on SCSI_SYM53C8XX_2
984 This option only applies to PCI-SCSI chip that are PCI DAC capable
985 (875A, 895A, 896, 1010-33, 1010-66, 1000).
987 When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
988 When set to 1, 40 bit DMA addressing (with upper 24 bits of address
989 set to zero) is supported. The addressable range is here 1 TB.
990 When set to 2, full 64 bits of address for DMA are supported, but only
991 16 segments of 4 GB can be addressed. The addressable range is so
994 The safest value is 0 (32 bit DMA addressing) that is guessed to still
995 fit most of real machines.
997 The preferred value 1 (40 bit DMA addressing) should make happy
998 properly engineered PCI DAC capable host bridges. You may configure
999 this option for Intel platforms with more than 4 GB of memory.
1001 The still experimental value 2 (64 bit DMA addressing with 16 x 4GB
1002 segments limitation) can be used on systems that require PCI address
1003 bits past bit 39 to be set for the addressing of memory using PCI
1006 config SCSI_SYM53C8XX_DEFAULT_TAGS
1007 int "default tagged command queue depth"
1008 depends on SCSI_SYM53C8XX_2
1011 This is the default value of the command queue depth the driver will
1012 announce to the generic SCSI layer for devices that support tagged
1013 command queueing. This value can be changed from the boot command line.
1014 This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1016 config SCSI_SYM53C8XX_MAX_TAGS
1017 int "maximum number of queued commands"
1018 depends on SCSI_SYM53C8XX_2
1021 This option allows you to specify the maximum number of commands
1022 that can be queued to any device, when tagged command queuing is
1023 possible. The driver supports up to 256 queued commands per device.
1024 This value is used as a compiled-in hard limit.
1026 config SCSI_SYM53C8XX_IOMAPPED
1027 bool "use normal IO"
1028 depends on SCSI_SYM53C8XX_2
1030 If you say Y here, the driver will preferently use normal IO rather than
1033 config SCSI_NCR53C8XX
1034 tristate "NCR53C8XX SCSI support"
1035 depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
1037 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
1038 of PCI-SCSI controllers. This driver supports parity checking,
1039 tagged command queuing and fast synchronous data transfers up to 80
1040 MB/s with wide FAST-40 LVD devices and controllers.
1042 Recent versions of the 53C8XX chips are better supported by the
1043 option "SYM53C8XX SCSI support", below.
1045 Note: there is yet another driver for the 53c8xx family of
1046 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
1047 them both, you need to say M to both and build them as modules, but
1048 only one may be active at a time. If you have a 53c8xx board, you
1049 probably do not want to use the "NCR53c7,8xx SCSI support".
1051 Please read <file:Documentation/scsi/ncr53c8xx.txt> for more
1054 config SCSI_SYM53C8XX
1055 tristate "SYM53C8XX SCSI support"
1056 depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
1058 This driver supports all the features of recent 53C8XX chips (used
1059 in PCI SCSI controllers), notably the hardware phase mismatch
1060 feature of the SYM53C896.
1062 Older versions of the 53C8XX chips are not supported by this
1063 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
1064 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
1065 driver ("NCR53C8XX SCSI support" above) or configure both the
1066 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
1069 When both drivers are linked into the kernel, the SYM53C8XX driver
1070 is called first at initialization and you can use the 'excl=ioaddr'
1071 driver boot option to exclude attachment of adapters by the
1072 SYM53C8XX driver. For example, entering
1073 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
1074 adapters at io address 0xb400 and 0xc000 from being attached by the
1075 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
1076 The 'excl' option is also supported by the NCR53C8XX driver.
1078 Please read <file:Documentation/scsi/ncr53c8xx.txt> for more
1081 config SCSI_NCR53C8XX_DEFAULT_TAGS
1082 int "default tagged command queue depth"
1083 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
1086 "Tagged command queuing" is a feature of SCSI-2 which improves
1087 performance: the host adapter can send several SCSI commands to a
1088 device's queue even if previous commands haven't finished yet.
1089 Because the device is intelligent, it can optimize its operations
1090 (like head positioning) based on its own request queue. Some SCSI
1091 devices don't implement this properly; if you want to disable this
1092 feature, enter 0 or 1 here (it doesn't matter which).
1094 The default value is 8 and should be supported by most hard disks.
1095 This value can be overridden from the boot command line using the
1096 'tags' option as follows (example):
1097 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1098 4, set queue depth to 16 for target 2 and target 3 on controller 0
1099 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1101 The normal answer therefore is to go with the default 8 and to use
1102 a boot command line option for devices that need to use a different
1103 command queue depth.
1105 There is no safe option other than using good SCSI devices.
1107 config SCSI_NCR53C8XX_MAX_TAGS
1108 int "maximum number of queued commands"
1109 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
1112 This option allows you to specify the maximum number of commands
1113 that can be queued to any device, when tagged command queuing is
1114 possible. The default value is 32. Minimum is 2, maximum is 64.
1115 Modern hard disks are able to support 64 tags and even more, but
1116 do not seem to be faster when more than 32 tags are being used.
1118 So, the normal answer here is to go with the default value 32 unless
1119 you are using very large hard disks with large cache (>= 1 MB) that
1120 are able to take advantage of more than 32 tagged commands.
1122 There is no safe option and the default answer is recommended.
1124 config SCSI_NCR53C8XX_SYNC
1125 int "synchronous transfers frequency in MHz"
1126 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
1129 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1130 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1131 are respectively the maximum data transfer rates in mega-transfers
1132 per second for each class. For example, a FAST-20 Wide 16 device is
1133 able to transfer data at 20 million 16 bit packets per second for a
1134 total rate of 40 MB/s.
1136 You may specify 0 if you want to only use asynchronous data
1137 transfers. This is the safest and slowest option. Otherwise, specify
1138 a value between 5 and 80, depending on the capability of your SCSI
1139 controller. The higher the number, the faster the data transfer.
1140 Note that 80 should normally be ok since the driver decreases the
1141 value automatically according to the controller's capabilities.
1143 Your answer to this question is ignored for controllers with NVRAM,
1144 since the driver will get this information from the user set-up. It
1145 also can be overridden using a boot setup option, as follows
1146 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1147 for FAST-20 synchronous data transfer (20 mega-transfers per
1150 The normal answer therefore is not to go with the default but to
1151 select the maximum value 80 allowing the driver to use the maximum
1152 value supported by each controller. If this causes problems with
1153 your SCSI devices, you should come back and decrease the value.
1155 There is no safe option other than using good cabling, right
1156 terminations and SCSI conformant devices.
1158 config SCSI_NCR53C8XX_PROFILE
1159 bool "enable profiling"
1160 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
1162 This option allows you to enable profiling information gathering.
1163 These statistics are not very accurate due to the low frequency
1164 of the kernel clock (100 Hz on i386) and have performance impact
1165 on systems that use very fast devices.
1167 The normal answer therefore is N.
1169 config SCSI_NCR53C8XX_IOMAPPED
1170 bool "use normal IO"
1171 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
1173 If you say Y here, the driver will use normal IO, as opposed to
1174 memory mapped IO. Memory mapped IO has less latency than normal IO
1175 and works for most Intel-based hardware. Under Linux/Alpha only
1176 normal IO is currently supported by the driver and so, this option
1177 has no effect on those systems.
1179 The normal answer therefore is N; try Y only if you encounter SCSI
1182 config SCSI_NCR53C8XX_PQS_PDS
1183 bool "include support for the NCR PQS/PDS SCSI card"
1184 depends on (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && SCSI_SYM53C8XX
1186 Say Y here if you have a special SCSI adapter produced by NCR
1187 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
1188 this if you do not have one of these adapters. However, since this
1189 device is detected as a specific PCI device, this option is quite
1192 The common answer here is N, but answering Y is safe.
1194 config SCSI_NCR53C8XX_NO_DISCONNECT
1195 bool "not allow targets to disconnect"
1196 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1198 This option is only provided for safety if you suspect some SCSI
1199 device of yours to not support properly the target-disconnect
1200 feature. In that case, you would say Y here. In general however, to
1201 not allow targets to disconnect is not reasonable if there is more
1202 than 1 device on a SCSI bus. The normal answer therefore is N.
1204 config SCSI_NCR53C8XX_SYMBIOS_COMPAT
1205 bool "assume boards are SYMBIOS compatible (EXPERIMENTAL)"
1206 depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && EXPERIMENTAL
1208 This option allows you to enable some features depending on GPIO
1209 wiring. These General Purpose Input/Output pins can be used for
1210 vendor specific features or implementation of the standard SYMBIOS
1211 features. Genuine SYMBIOS controllers use GPIO0 in output for
1212 controller LED and GPIO3 bit as a flag indicating
1213 singled-ended/differential interface. The Tekram DC-390U/F boards
1214 uses a different GPIO wiring.
1216 Your answer to this question is ignored if all your controllers have
1217 NVRAM, since the driver is able to detect the board type from the
1220 If all the controllers in your system are genuine SYMBIOS boards or
1221 use BIOS and drivers from SYMBIOS, you would want to say Y here,
1222 otherwise N. N is the safe answer.
1224 config SCSI_MCA_53C9X
1225 tristate "NCR MCA 53C9x SCSI support"
1226 depends on MCA && SCSI
1228 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1229 controller based on the NCR 53C94. This driver will allow use of
1230 the controller on the 3550, and very possibly others.
1232 If you want to compile this as a module (= code which can be
1233 inserted and removed from the running kernel whenever you want), say
1234 M here and read <file:Documentation/modules.txt>. The module will
1235 be called mca_53c9x.o.
1238 tristate "PAS16 SCSI support"
1239 depends on SCSI && ISA
1241 This is support for a SCSI host adapter. It is explained in section
1242 3.10 of the SCSI-HOWTO, available from
1243 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
1244 of the box, you may have to change some settings in
1245 <file:drivers/scsi/pas16.h>.
1247 This driver is also available as a module ( = code which can be
1248 inserted in and removed from the running kernel whenever you want).
1249 The module will be called pas16.o. If you want to compile it as a
1250 module, say M here and read <file:Documentation/modules.txt>.
1253 tristate "PCI2000 support"
1256 This is support for the PCI2000I EIDE interface card which acts as a
1257 SCSI host adapter. Please read the SCSI-HOWTO, available from
1258 <http://www.linuxdoc.org/docs.html#howto>.
1260 This driver is also available as a module called pci2000.o ( = code
1261 which can be inserted in and removed from the running kernel
1262 whenever you want). If you want to compile it as a module, say M
1263 here and read <file:Documentation/modules.txt>.
1265 config SCSI_PCI2220I
1266 tristate "PCI2220i support"
1269 This is support for the PCI2220i EIDE interface card which acts as a
1270 SCSI host adapter. Please read the SCSI-HOWTO, available from
1271 <http://www.linuxdoc.org/docs.html#howto>.
1273 This driver is also available as a module called pci2220i.o ( = code
1274 which can be inserted in and removed from the running kernel
1275 whenever you want). If you want to compile it as a module, say M
1276 here and read <file:Documentation/modules.txt>.
1279 tristate "PSI240i support"
1280 depends on SCSI && ISA
1282 This is support for the PSI240i EIDE interface card which acts as a
1283 SCSI host adapter. Please read the SCSI-HOWTO, available from
1284 <http://www.linuxdoc.org/docs.html#howto>.
1286 This driver is also available as a module called psi240i.o ( = code
1287 which can be inserted in and removed from the running kernel
1288 whenever you want). If you want to compile it as a module, say M
1289 here and read <file:Documentation/modules.txt>.
1291 config SCSI_QLOGIC_FAS
1292 tristate "Qlogic FAS SCSI support"
1293 depends on SCSI && ISA
1295 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1296 FastSCSI! cards as well as any other card based on the FASXX chip
1297 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1299 This driver does NOT support the PCI versions of these cards. The
1300 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1301 SCSI support"), below.
1303 Information about this driver is contained in
1304 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1305 SCSI-HOWTO, available from
1306 <http://www.linuxdoc.org/docs.html#howto>.
1308 This driver is also available as a module ( = code which can be
1309 inserted in and removed from the running kernel whenever you want).
1310 The module will be called qlogicfas.o. If you want to compile it as
1311 a module, say M here and read <file:Documentation/modules.txt>.
1313 config SCSI_QLOGIC_ISP
1314 tristate "Qlogic ISP SCSI support"
1315 depends on PCI && SCSI
1317 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1318 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1319 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1321 If you say Y here, make sure to choose "BIOS" at the question "PCI
1324 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1325 should also read the SCSI-HOWTO, available from
1326 <http://www.linuxdoc.org/docs.html#howto>.
1328 This driver is also available as a module ( = code which can be
1329 inserted in and removed from the running kernel whenever you want).
1330 The module will be called qlogicisp.o. If you want to compile it as
1331 a module, say M here and read <file:Documentation/modules.txt>.
1333 config SCSI_QLOGIC_FC
1334 tristate "Qlogic ISP FC SCSI support"
1335 depends on PCI && SCSI
1337 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1339 This driver is also available as a module ( = code which can be
1340 inserted in and removed from the running kernel whenever you want).
1341 The module will be called qlogicfc.o. If you want to compile it as
1342 a module, say M here and read <file:Documentation/modules.txt>.
1344 config SCSI_QLOGIC_FC_FIRMWARE
1345 bool "Include loadable firmware in driver"
1346 depends on SCSI_QLOGIC_FC
1348 config SCSI_QLOGIC_1280
1349 tristate "Qlogic QLA 1280 SCSI support"
1350 depends on PCI && SCSI
1352 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1354 This driver is also available as a module ( = code which can be
1355 inserted in and removed from the running kernel whenever you want).
1356 The module will be called qla1280.o. If you want to compile it as
1357 a module, say M here and read <file:Documentation/modules.txt>.
1360 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1361 depends on X86 && ISA && SCSI
1363 These are 8-bit SCSI controllers; the ST-01 is also supported by
1364 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1365 available from <http://www.linuxdoc.org/docs.html#howto>. If it
1366 doesn't work out of the box, you may have to change some settings in
1367 <file:drivers/scsi/seagate.h>.
1369 This driver is also available as a module ( = code which can be
1370 inserted in and removed from the running kernel whenever you want).
1371 The module will be called seagate.o. If you want to compile it as a
1372 module, say M here and read <file:Documentation/modules.txt>.
1374 # definitely looks note 64bit safe:
1376 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1377 depends on (ISA || MCA && !X86_64) && SCSI
1379 This is a simple driver for NCR53c710 based SCSI host adapters.
1381 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
1382 support", above), but they require that the scsi chip be able to do
1383 DMA block moves between memory and on-chip registers, which can
1384 cause problems under certain conditions. This driver is designed to
1385 avoid these problems and is intended to work with any Intel machines
1386 using 53c710 chips, including various Compaq and NCR machines.
1388 Please read the comments at the top of the file
1389 <file:drivers/scsi/sim710.c> for more information.
1391 If you want to compile this driver as a module ( = code which can be
1392 inserted in and removed from the running kernel whenever you want),
1393 say M here and read <file:Documentation/modules.txt>. The module
1394 will be called sim710.o.
1396 config SCSI_SYM53C416
1397 tristate "Symbios 53c416 SCSI support"
1398 depends on SCSI && ISA
1400 This is support for the sym53c416 SCSI host adapter, the SCSI
1401 adapter that comes with some HP scanners. This driver requires that
1402 the sym53c416 is configured first using some sort of PnP
1403 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1404 are using isapnp then you need to compile this driver as a module
1405 and then load it using insmod after isapnp has run. The parameters
1406 of the configured card(s) should be passed to the driver. The format
1409 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1411 There is support for up to four adapters. If you want to compile
1412 this driver as a module ( = code which can be inserted in and
1413 removed from the running kernel whenever you want), say M here and
1414 read <file:Documentation/modules.txt>. The module will be called
1418 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1419 depends on PCI && SCSI
1421 This driver supports PCI SCSI host adapters based on the Am53C974A
1422 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1423 PCscsi/PCnet (Am53/79C974) solutions.
1425 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1427 Note that this driver does NOT support Tekram DC390W/U/F, which are
1428 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1429 Also note that there is another generic Am53C974 driver,
1430 "AM53/79C974 PCI SCSI support" below. You can pick either one.
1432 If you want to compile this driver as a module ( = code which can be
1433 inserted in and removed from the running kernel whenever you want),
1434 say M here and read <file:Documentation/modules.txt>. The module
1435 will be called tmscsim.o.
1437 config SCSI_DC390T_NOGENSUPP
1438 bool "_omit_ support for non-DC390 adapters"
1439 depends on SCSI_DC390T
1441 If you say N here, the DC390(T) SCSI driver relies on the DC390
1442 EEPROM to get initial values for its settings, such as speed,
1443 termination, etc. If it can't find this EEPROM, it will use
1444 defaults or the user supplied boot/module parameters. For details
1445 on driver configuration see <file:Documentation/scsi/tmscsim.txt>.
1447 If you say Y here and if no EEPROM is found, the driver gives up and
1448 thus only supports Tekram DC390(T) adapters. This can be useful if
1449 you have a DC390(T) and another Am53C974 based adapter, which, for
1450 some reason, you want to drive with the other AM53C974 driver.
1455 tristate "Trantor T128/T128F/T228 SCSI support"
1456 depends on SCSI && ISA
1458 This is support for a SCSI host adapter. It is explained in section
1459 3.11 of the SCSI-HOWTO, available from
1460 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
1461 of the box, you may have to change some settings in
1462 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1463 Adaptec, and some former Trantor products are being sold under the
1466 This driver is also available as a module ( = code which can be
1467 inserted in and removed from the running kernel whenever you want).
1468 The module will be called t128.o. If you want to compile it as a
1469 module, say M here and read <file:Documentation/modules.txt>.
1472 tristate "UltraStor 14F/34F support"
1475 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1476 The source at <file:drivers/scsi/u14-34f.c> contains some
1477 information about this hardware. If the driver doesn't work out of
1478 the box, you may have to change some settings in
1479 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1480 <http://www.linuxdoc.org/docs.html#howto>. Note that there is also
1481 another driver for the same hardware: "UltraStor SCSI support",
1482 below. You should say Y to both only if you want 24F support as
1485 This driver is also available as a module ( = code which can be
1486 inserted in and removed from the running kernel whenever you want).
1487 The module will be called u14-34f.o. If you want to compile it as a
1488 module, say M here and read <file:Documentation/modules.txt>.
1490 config SCSI_U14_34F_LINKED_COMMANDS
1491 bool "enable elevator sorting"
1492 depends on SCSI_U14_34F
1494 This option enables elevator sorting for all probed SCSI disks and
1495 CD-ROMs. It definitely reduces the average seek distance when doing
1496 random seeks, but this does not necessarily result in a noticeable
1497 performance improvement: your mileage may vary...
1499 The safe answer is N.
1501 config SCSI_U14_34F_MAX_TAGS
1502 int "maximum number of queued commands"
1503 depends on SCSI_U14_34F
1506 This specifies how many SCSI commands can be maximally queued for
1507 each probed SCSI device. You should reduce the default value of 8
1508 only if you have disks with buggy or limited tagged command support.
1509 Minimum is 2 and maximum is 14. This value is also the window size
1510 used by the elevator sorting option above. The effective value used
1511 by the driver for each probed SCSI device is reported at boot time.
1513 config SCSI_ULTRASTOR
1514 tristate "UltraStor SCSI support"
1515 depends on X86 && ISA && SCSI
1517 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1518 adapter family. This driver is explained in section 3.12 of the
1519 SCSI-HOWTO, available from
1520 <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
1521 of the box, you may have to change some settings in
1522 <file:drivers/scsi/ultrastor.h>.
1524 Note that there is also another driver for the same hardware:
1525 "UltraStor 14F/34F support", above.
1527 If you want to compile this as a module ( = code which can be
1528 inserted in and removed from the running kernel whenever you want),
1529 say M here and read <file:Documentation/modules.txt>. The module
1530 will be called ultrastor.o.
1533 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1536 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1537 SCSI host adapter. Please read the SCSI-HOWTO, available from
1538 <http://www.linuxdoc.org/docs.html#howto>.
1540 If you want to compile this as a module ( = code which can be
1541 inserted in and removed from the running kernel whenever you want),
1542 say M here and read <file:Documentation/modules.txt>. The module
1543 will be called nsp32.o.
1546 # Note - this is a very special 'host' adapter that simulates the presence of some disks.
1547 # It can come in very handy for troubleshooting. Anyone else is welcome to use it - all
1548 # you do is hack it to simulate the condition you want to test for, and then use it.
1550 # The actual configuration in any kernel release could change at any time as I hack it to
1551 # simulate various conditions that I am testing.
1554 tristate "SCSI debugging host simulator (EXPERIMENTAL)"
1555 depends on EXPERIMENTAL && SCSI
1557 This is a host adapter simulator that can be programmed to simulate
1558 a large number of conditions that could occur on a real bus. The
1559 advantage is that many hard to reproduce problems can be tested in a
1560 controlled environment where there is reduced risk of losing
1561 important data. This is primarily of use to people trying to debug
1562 the middle and upper layers of the SCSI subsystem. If unsure, say N.
1565 tristate "MESH (Power Mac internal SCSI) support"
1566 depends on ALL_PPC && SCSI
1568 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1569 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1570 other Power Macintoshes do). Say Y to include support for this SCSI
1571 adaptor. This driver is also available as a module called mesh.o
1572 ( = code which can be inserted in and removed from the running
1573 kernel whenever you want). If you want to compile it as a module,
1574 say M here and read <file:Documentation/modules.txt>.
1576 config SCSI_MESH_SYNC_RATE
1577 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1578 depends on SCSI_MESH
1581 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1582 drives a bus which is entirely internal to the machine (such as the
1583 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1584 operation at up to 10 MB/s. On machines where the SCSI bus
1585 controlled by the MESH can have external devices connected, it is
1586 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1587 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1588 to disable synchronous operation.
1590 config SCSI_MESH_RESET_DELAY_MS
1591 int "initial bus reset delay (ms) (0 = no reset)"
1592 depends on SCSI_MESH
1595 config SCSI_MAC53C94
1596 tristate "53C94 (Power Mac external SCSI) support"
1597 depends on ALL_PPC && SCSI
1599 On Power Macintoshes (and clones) with two SCSI buses, the external
1600 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1601 machines which only have one SCSI bus, such as the 7200, also use
1602 the 53C94. Say Y to include support for the 53C94.
1604 This driver is also available as a module called mac53c94.o ( = code
1605 which can be inserted in and removed from the running kernel
1606 whenever you want). If you want to compile it as a module, say M
1607 here and read <file:Documentation/modules.txt>.
1609 source "drivers/acorn/scsi/Kconfig"
1612 bool "MIPS JAZZ FAS216 SCSI support"
1613 depends on MIPS_JAZZ
1615 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1616 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1620 tristate "A3000 WD33C93A support"
1621 depends on AMIGA && SCSI
1623 If you have an Amiga 3000 and have SCSI devices connected to the
1624 built-in SCSI controller, say Y. Otherwise, say N. This driver is
1625 also available as a module ( = code which can be inserted in and
1626 removed from the running kernel whenever you want). The module is
1627 called wd33c93.o. If you want to compile it as a module, say M here
1628 and read <file:Documentation/modules.txt>.
1631 bool "A4000T SCSI support (EXPERIMENTAL)"
1632 depends on AMIGA && EXPERIMENTAL
1634 Support for the NCR53C710 SCSI controller on the Amiga 4000T.
1637 tristate "A2091/A590 WD33C93A support"
1638 depends on ZORRO && SCSI
1640 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1641 say N. This driver is also available as a module ( = code which can
1642 be inserted in and removed from the running kernel whenever you
1643 want). The module is called wd33c93.o. If you want to compile it as
1644 a module, say M here and read <file:Documentation/modules.txt>.
1647 tristate "GVP Series II WD33C93A support"
1648 depends on ZORRO && SCSI
1650 If you have a Great Valley Products Series II SCSI controller,
1651 answer Y. Also say Y if you have a later model of GVP SCSI
1652 controller (such as the GVP A4008 or a Combo board). Otherwise,
1653 answer N. This driver does NOT work for the T-Rex series of
1654 accelerators from TekMagic and GVP-M.
1656 This driver is also available as a module ( = code which can be
1657 inserted in and removed from the running kernel whenever you
1658 want). The module will be called gvp11.o. If you want to compile it
1659 as a module, say M here and read <file:Documentation/modules.txt>.
1661 config CYBERSTORM_SCSI
1662 tristate "CyberStorm SCSI support"
1663 depends on ZORRO && SCSI
1665 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1666 accelerator board and the optional Cyberstorm SCSI controller,
1667 answer Y. Otherwise, say N.
1669 config CYBERSTORMII_SCSI
1670 tristate "CyberStorm Mk II SCSI support"
1671 depends on ZORRO && SCSI
1673 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1674 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1678 tristate "Blizzard 2060 SCSI support"
1679 depends on ZORRO && SCSI
1681 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1682 and want to use the onboard SCSI controller, say Y. Otherwise,
1686 tristate "Blizzard 1230IV/1260 SCSI support"
1687 depends on ZORRO && SCSI
1689 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1690 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1693 config FASTLANE_SCSI
1694 tristate "Fastlane SCSI support"
1695 depends on ZORRO && SCSI
1697 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1698 one in the near future, say Y to this question. Otherwise, say N.
1701 bool "A4091 SCSI support (EXPERIMENTAL)"
1702 depends on ZORRO && EXPERIMENTAL
1704 Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller
1705 (1993). Very obscure -- the 4091 was part of an Amiga 4000 upgrade
1706 plan at the time the Amiga business was sold to DKB.
1708 config WARPENGINE_SCSI
1709 bool "WarpEngine SCSI support (EXPERIMENTAL)"
1710 depends on ZORRO && EXPERIMENTAL
1712 Support for MacroSystem Development's WarpEngine Amiga SCSI-2
1714 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
1716 config BLZ603EPLUS_SCSI
1717 bool "Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)"
1718 depends on ZORRO && EXPERIMENTAL
1720 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
1721 accelerator, say Y. Otherwise, say N.
1724 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1725 depends on ZORRO && EXPERIMENTAL && SCSI
1727 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1728 Y to this question. If you're in doubt about whether you have one,
1730 <http://amiga.multigraph.com/photos/oktagon.html>.
1732 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1733 # bool 'GVP Turbo 040/060 SCSI support (EXPERIMENTAL)' CONFIG_GVP_TURBO_SCSI
1736 source "drivers/scsi/pcmcia/Kconfig"