| blob | 60015656c1f28fb5ccc9ffb697e15a0924d7e678 |
1 menu "SCSI device support"
3 config SCSI
4 tristate "SCSI device support"
5 ---help---
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.
24 config SCSI_PROC_FS
25 bool "legacy /proc/scsi/ support"
26 depends on SCSI && PROC_FS
27 default y
28 ---help---
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.
33 If unusure say Y.
35 comment "SCSI support type (disk, tape, CD-ROM)"
36 depends on SCSI
38 config BLK_DEV_SD
39 tristate "SCSI disk support"
40 depends on SCSI
41 ---help---
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
47 CD-ROMs.
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.
58 config CHR_DEV_ST
59 tristate "SCSI tape support"
60 depends on SCSI
61 ---help---
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
66 for SCSI CD-ROMs.
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.
71 config CHR_DEV_OSST
72 tristate "SCSI OnStream SC-x0 tape support"
73 depends on SCSI
74 ---help---
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.
93 config BLK_DEV_SR
94 tristate "SCSI CDROM support"
95 depends on SCSI
96 ---help---
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
109 help
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.
115 config CHR_DEV_SG
116 tristate "SCSI generic support"
117 depends on SCSI
118 ---help---
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.
138 If unsure, say N.
140 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
141 depends on SCSI
143 config SCSI_MULTI_LUN
144 bool "Probe all LUNs on each SCSI device"
145 depends on SCSI
146 help
147 If you have a SCSI device that supports more than one LUN (Logical
148 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
149 can say Y here to force the SCSI driver to probe for multiple LUNs.
150 A SCSI device with multiple LUNs acts logically like multiple SCSI
151 devices. The vast majority of SCSI devices have only one LUN, and
152 so most people can say N here. The max_luns boot/module parameter
153 allows to override this setting.
155 config SCSI_CONSTANTS
156 bool "Verbose SCSI error reporting (kernel size +=12K)"
157 depends on SCSI
158 help
159 The error messages regarding your SCSI hardware will be easier to
160 understand if you say Y here; it will enlarge your kernel by about
161 12 KB. If in doubt, say Y.
163 config SCSI_LOGGING
164 bool "SCSI logging facility"
165 depends on SCSI
166 ---help---
167 This turns on a logging facility that can be used to debug a number
168 of SCSI related problems.
170 If you say Y here, no logging output will appear by default, but you
171 can enable logging by saying Y to "/proc file system support" and
172 "Sysctl support" below and executing the command
174 echo "scsi log token [level]" > /proc/scsi/scsi
176 at boot time after the /proc file system has been mounted.
178 There are a number of things that can be used for 'token' (you can
179 find them in the source: <file:drivers/scsi/scsi.c>), and this
180 allows you to select the types of information you want, and the
181 level allows you to select the level of verbosity.
183 If you say N here, it may be harder to track down some types of SCSI
184 problems. If you say Y here your kernel will be somewhat larger, but
185 there should be no noticeable performance impact as long as you have
186 logging turned off.
188 menu "SCSI Transport Attributes"
189 depends on SCSI
191 config SCSI_SPI_ATTRS
192 tristate "Parallel SCSI (SPI) Transport Attributes"
193 depends on SCSI
194 help
195 If you wish to export transport-specific information about
196 each attached SCSI device to sysfs, say Y. Otherwise, say N.
198 config SCSI_FC_ATTRS
199 tristate "FiberChannel Transport Attributes"
200 depends on SCSI
201 help
202 If you wish to export transport-specific information about
203 each attached FiberChannel device to sysfs, say Y.
204 Otherwise, say N.
206 endmenu
208 menu "SCSI low-level drivers"
209 depends on SCSI!=n
211 config SGIWD93_SCSI
212 tristate "SGI WD93C93 SCSI Driver"
213 depends on SGI_IP22 && SCSI
214 help
215 If you have a Western Digital WD93 SCSI controller on
216 an SGI MIPS system, say Y. Otherwise, say N.
218 config SCSI_DECNCR
219 tristate "DEC NCR53C94 Scsi Driver"
220 depends on DECSTATION && TC && SCSI
221 help
222 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
223 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
225 config SCSI_DECSII
226 tristate "DEC SII Scsi Driver"
227 depends on DECSTATION && SCSI
229 config BLK_DEV_3W_XXXX_RAID
230 tristate "3ware 5/6/7/8xxx ATA-RAID support"
231 depends on PCI && SCSI
232 help
233 3ware is the only hardware ATA-Raid product in Linux to date.
234 This card is 2,4, or 8 channel master mode support only.
235 SCSI support required!!!
237 <http://www.3ware.com/>
239 Please read the comments at the top of
240 <file:drivers/scsi/3w-xxxx.c>.
242 config SCSI_3W_9XXX
243 tristate "3ware 9xxx SATA-RAID support"
244 depends on PCI && SCSI
245 help
246 This driver supports the 9000 series 3ware SATA-RAID cards.
248 <http://www.amcc.com>
250 Please read the comments at the top of
251 <file:drivers/scsi/3w-9xxx.c>.
253 config SCSI_7000FASST
254 tristate "7000FASST SCSI support"
255 depends on ISA && SCSI
256 help
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.
264 config SCSI_ACARD
265 tristate "ACARD SCSI support"
266 depends on PCI && SCSI
267 help
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.
273 config SCSI_AHA152X
274 tristate "Adaptec AHA152X/2825 support"
275 depends on ISA && SCSI && !64BIT
276 ---help---
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.
288 config SCSI_AHA1542
289 tristate "Adaptec AHA1542 support"
290 depends on ISA && SCSI
291 ---help---
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.
302 config SCSI_AHA1740
303 tristate "Adaptec AHA1740 support"
304 depends on EISA && SCSI
305 ---help---
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.
315 config SCSI_AACRAID
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)"
323 depends on (ISA || EISA || PCI ) && SCSI
324 help
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
344 cards).
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
348 one of those.
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
356 be of great help.
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.
364 config SCSI_DPT_I2O
365 tristate "Adaptec I2O RAID support "
366 depends on !64BIT && SCSI && PCI
367 help
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.
375 config SCSI_ADVANSYS
376 tristate "AdvanSys SCSI support"
377 depends on (ISA || EISA || PCI) && SCSI && BROKEN
378 help
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.
386 config SCSI_IN2000
387 tristate "Always IN2000 SCSI support"
388 depends on ISA && SCSI
389 help
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
393 address selection.
395 To compile this driver as a module, choose M here: the
396 module will be called in2000.
398 source "drivers/scsi/megaraid/Kconfig.megaraid"
400 config SCSI_SATA
401 bool "Serial ATA (SATA) support"
402 depends on SCSI && EXPERIMENTAL
403 help
404 This driver family supports Serial ATA host controllers
405 and devices.
407 If unsure, say N.
409 config SCSI_SATA_SVW
410 tristate "ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL)"
411 depends on SCSI_SATA && PCI && EXPERIMENTAL
412 help
413 This option enables support for Broadcom/Serverworks/Apple K2
414 SATA support.
416 If unsure, say N.
418 config SCSI_ATA_PIIX
419 tristate "Intel PIIX/ICH SATA support"
420 depends on SCSI_SATA && PCI
421 help
422 This option enables support for ICH5 Serial ATA.
423 If PATA support was enabled previously, this enables
424 support for select Intel PIIX/ICH PATA host controllers.
426 If unsure, say N.
428 config SCSI_SATA_NV
429 tristate "NVIDIA SATA support"
430 depends on SCSI_SATA && PCI && EXPERIMENTAL
431 help
432 This option enables support for NVIDIA Serial ATA.
434 If unsure, say N.
436 config SCSI_SATA_PROMISE
437 tristate "Promise SATA TX2/TX4 support"
438 depends on SCSI_SATA && PCI
439 help
440 This option enables support for Promise Serial ATA TX2/TX4.
442 If unsure, say N.
444 config SCSI_SATA_SX4
445 tristate "Promise SATA SX4 support"
446 depends on SCSI_SATA && PCI && EXPERIMENTAL
447 help
448 This option enables support for Promise Serial ATA SX4.
450 If unsure, say N.
452 config SCSI_SATA_SIL
453 tristate "Silicon Image SATA support"
454 depends on SCSI_SATA && PCI && EXPERIMENTAL
455 help
456 This option enables support for Silicon Image Serial ATA.
458 If unsure, say N.
460 config SCSI_SATA_SIS
461 tristate "SiS 964/180 SATA support"
462 depends on SCSI_SATA && PCI
463 help
464 This option enables support for SiS Serial ATA 964/180.
466 If unsure, say N.
468 config SCSI_SATA_VIA
469 tristate "VIA SATA support"
470 depends on SCSI_SATA && PCI && EXPERIMENTAL
471 help
472 This option enables support for VIA Serial ATA.
474 If unsure, say N.
476 config SCSI_SATA_VITESSE
477 tristate "VITESSE VSC-7174 SATA support"
478 depends on SCSI_SATA && PCI && EXPERIMENTAL
479 help
480 This option enables support for Vitesse VSC7174 Serial ATA.
482 If unsure, say N.
484 config SCSI_BUSLOGIC
485 tristate "BusLogic SCSI support"
486 depends on (PCI || ISA || MCA) && SCSI && (BROKEN || !SPARC64)
487 ---help---
488 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
489 Adapters. Consult the SCSI-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>, and the files
491 <file:Documentation/scsi/BusLogic.txt> and
492 <file:Documentation/scsi/FlashPoint.txt> for more information.
494 To compile this driver as a module, choose M here: the
495 module will be called BusLogic.
497 config SCSI_OMIT_FLASHPOINT
498 bool "Omit FlashPoint support"
499 depends on SCSI_BUSLOGIC
500 help
501 This option allows you to omit the FlashPoint support from the
502 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
503 substantial, so users of MultiMaster Host Adapters may wish to omit
504 it.
506 #
507 # This is marked broken because it uses over 4kB of stack in
508 # just two routines:
509 # 2076 CpqTsProcessIMQEntry
510 # 2052 PeekIMQEntry
511 #
512 config SCSI_CPQFCTS
513 tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
514 depends on PCI && SCSI && BROKEN
515 help
516 Say Y here to compile in support for the Compaq StorageWorks Fibre
517 Channel 64-bit/66Mhz Host Bus Adapter.
519 config SCSI_DMX3191D
520 tristate "DMX3191D SCSI support"
521 depends on PCI && SCSI
522 help
523 This is support for Domex DMX3191D SCSI Host Adapters.
525 To compile this driver as a module, choose M here: the
526 module will be called dmx3191d.
528 config SCSI_DTC3280
529 tristate "DTC3180/3280 SCSI support"
530 depends on ISA && SCSI
531 help
532 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
533 the SCSI-HOWTO, available from
534 <http://www.tldp.org/docs.html#howto>, and the file
535 <file:Documentation/scsi/dtc3x80.txt>.
537 To compile this driver as a module, choose M here: the
538 module will be called dtc.
540 config SCSI_EATA
541 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
542 depends on (ISA || EISA || PCI) && SCSI && (BROKEN || !SPARC64)
543 ---help---
544 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
545 ISA and all EISA I/O addresses are probed looking for the "EATA"
546 signature. The addresses of all the PCI SCSI controllers reported
547 by the PCI subsystem are probed as well.
549 You want to read the start of <file:drivers/scsi/eata.c> and the
550 SCSI-HOWTO, available from
551 <http://www.tldp.org/docs.html#howto>.
553 To compile this driver as a module, choose M here: the
554 module will be called eata.
556 config SCSI_EATA_TAGGED_QUEUE
557 bool "enable tagged command queueing"
558 depends on SCSI_EATA
559 help
560 This is a feature of SCSI-2 which improves performance: the host
561 adapter can send several SCSI commands to a device's queue even if
562 previous commands haven't finished yet.
563 This is equivalent to the "eata=tc:y" boot option.
565 config SCSI_EATA_LINKED_COMMANDS
566 bool "enable elevator sorting"
567 depends on SCSI_EATA
568 help
569 This option enables elevator sorting for all probed SCSI disks and
570 CD-ROMs. It definitely reduces the average seek distance when doing
571 random seeks, but this does not necessarily result in a noticeable
572 performance improvement: your mileage may vary...
573 This is equivalent to the "eata=lc:y" boot option.
575 config SCSI_EATA_MAX_TAGS
576 int "maximum number of queued commands"
577 depends on SCSI_EATA
578 default "16"
579 help
580 This specifies how many SCSI commands can be maximally queued for
581 each probed SCSI device. You should reduce the default value of 16
582 only if you have disks with buggy or limited tagged command support.
583 Minimum is 2 and maximum is 62. This value is also the window size
584 used by the elevator sorting option above. The effective value used
585 by the driver for each probed SCSI device is reported at boot time.
586 This is equivalent to the "eata=mq:8" boot option.
588 config SCSI_EATA_PIO
589 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
590 depends on (ISA || EISA || PCI) && SCSI
591 ---help---
592 This driver supports all EATA-PIO protocol compliant SCSI Host
593 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
594 host adapters could also use this driver but are discouraged from
595 doing so, since this driver only supports hard disks and lacks
596 numerous features. You might want to have a look at the SCSI-HOWTO,
597 available from <http://www.tldp.org/docs.html#howto>.
599 To compile this driver as a module, choose M here: the
600 module will be called eata_pio.
602 config SCSI_FUTURE_DOMAIN
603 tristate "Future Domain 16xx SCSI/AHA-2920A support"
604 depends on (ISA || PCI) && SCSI
605 ---help---
606 This is support for Future Domain's 16-bit SCSI host adapters
607 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
608 other adapters based on the Future Domain chipsets (Quantum
609 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
610 It is explained in section 3.7 of the SCSI-HOWTO, available from
611 <http://www.tldp.org/docs.html#howto>.
613 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
614 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
615 controller support"). This Future Domain driver works with the older
616 Adaptec AHA-2920A boards with a Future Domain chip on them.
618 To compile this driver as a module, choose M here: the
619 module will be called fdomain.
621 config SCSI_FD_MCS
622 tristate "Future Domain MCS-600/700 SCSI support"
623 depends on MCA_LEGACY && SCSI
624 ---help---
625 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
626 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
627 is identical to the MCS 700 and hence also supported by this driver.
628 This driver also supports the Reply SB16/SCSI card (the SCSI part).
629 It supports multiple adapters in the same system.
631 To compile this driver as a module, choose M here: the
632 module will be called fd_mcs.
634 config SCSI_GDTH
635 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
636 depends on (ISA || EISA || PCI) && SCSI && (BROKEN || !SPARC64)
637 ---help---
638 Formerly called GDT SCSI Disk Array Controller Support.
640 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
641 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
642 in the kernel source in <file:drivers/scsi/gdth.c> and
643 <file:drivers/scsi/gdth.h.>
645 To compile this driver as a module, choose M here: the
646 module will be called gdth.
648 config SCSI_GENERIC_NCR5380
649 tristate "Generic NCR5380/53c400 SCSI PIO support"
650 depends on ISA && SCSI
651 ---help---
652 This is a driver for the old NCR 53c80 series of SCSI controllers
653 on boards using PIO. Most boards such as the Trantor T130 fit this
654 category, along with a large number of ISA 8bit controllers shipped
655 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
656 you should select the specific driver for that card rather than
657 generic 5380 support.
659 It is explained in section 3.8 of the SCSI-HOWTO, available from
660 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
661 of the box, you may have to change some settings in
662 <file:drivers/scsi/g_NCR5380.h>.
664 To compile this driver as a module, choose M here: the
665 module will be called g_NCR5380.
667 config SCSI_GENERIC_NCR5380_MMIO
668 tristate "Generic NCR5380/53c400 SCSI MMIO support"
669 depends on ISA && SCSI
670 ---help---
671 This is a driver for the old NCR 53c80 series of SCSI controllers
672 on boards using memory mapped I/O.
673 It is explained in section 3.8 of the SCSI-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
675 of the box, you may have to change some settings in
676 <file:drivers/scsi/g_NCR5380.h>.
678 To compile this driver as a module, choose M here: the
679 module will be called g_NCR5380_mmio.
681 config SCSI_GENERIC_NCR53C400
682 bool "Enable NCR53c400 extensions"
683 depends on SCSI_GENERIC_NCR5380
684 help
685 This enables certain optimizations for the NCR53c400 SCSI cards.
686 You might as well try it out. Note that this driver will only probe
687 for the Trantor T130B in its default configuration; you might have
688 to pass a command line option to the kernel at boot time if it does
689 not detect your card. See the file
690 <file:Documentation/scsi/g_NCR5380.txt> for details.
692 config SCSI_IBMMCA
693 tristate "IBMMCA SCSI support"
694 depends on MCA_LEGACY && SCSI
695 ---help---
696 This is support for the IBM SCSI adapter found in many of the PS/2
697 series computers. These machines have an MCA bus, so you need to
698 answer Y to "MCA support" as well and read
699 <file:Documentation/mca.txt>.
701 If the adapter isn't found during boot (a common problem for models
702 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
703 option, where <pun> is the id of the SCSI subsystem (usually 7, but
704 if that doesn't work check your reference diskette). Owners of
705 model 95 with a LED-matrix-display can in addition activate some
706 activity info like under OS/2, but more informative, by setting
707 'ibmmcascsi=display' as an additional kernel parameter. Try "man
708 bootparam" or see the documentation of your boot loader about how to
709 pass options to the kernel.
711 To compile this driver as a module, choose M here: the
712 module will be called ibmmca.
714 config IBMMCA_SCSI_ORDER_STANDARD
715 bool "Standard SCSI-order"
716 depends on SCSI_IBMMCA
717 ---help---
718 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
719 are assigned to the drive letters, starting with the lowest SCSI-id
720 (physical number -- pun) to be drive C:, as seen from DOS and
721 similar operating systems. When looking into papers describing the
722 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
723 The SCSI-standard follows a hardware-hierarchy which says that id 7
724 has the highest priority and id 0 the lowest. Therefore, the host
725 adapters are still today everywhere placed as SCSI-id 7 by default.
726 In the SCSI-standard, the drive letters express the priority of the
727 disk. C: should be the hard disk, or a partition on it, with the
728 highest priority. This must therefore be the disk with the highest
729 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
730 original definition of the SCSI-standard as also industrial- and
731 process-control-machines, like VME-CPUs running under realtime-OSes
732 (e.g. LynxOS, OS9) do.
734 If you like to run Linux on your MCA-machine with the same
735 assignment of hard disks as seen from e.g. DOS or OS/2 on your
736 machine, which is in addition conformant to the SCSI-standard, you
737 must say Y here. This is also necessary for MCA-Linux users who want
738 to keep downward compatibility to older releases of the
739 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
740 June 1997).
742 If you like to have the lowest SCSI-id assigned as drive C:, as
743 modern SCSI-BIOSes do, which does not conform to the standard, but
744 is widespread and common in the PC-world of today, you must say N
745 here. If unsure, say Y.
747 config IBMMCA_SCSI_DEV_RESET
748 bool "Reset SCSI-devices at boottime"
749 depends on SCSI_IBMMCA
750 ---help---
751 By default, SCSI-devices are reset when the machine is powered on.
752 However, some devices exist, like special-control-devices,
753 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
754 not reset when switched on. If you say Y here, each device connected
755 to your SCSI-bus will be issued a reset-command after it has been
756 probed, while the kernel is booting. This may cause problems with
757 more modern devices, like hard disks, which do not appreciate these
758 reset commands, and can cause your system to hang. So say Y only if
759 you know that one of your older devices needs it; N is the safe
760 answer.
762 config SCSI_IPS
763 tristate "IBM ServeRAID support"
764 depends on PCI && SCSI
765 ---help---
766 This is support for the IBM ServeRAID hardware RAID controllers.
767 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
768 for more information. If this driver does not work correctly
769 without modification please contact the author by email at
770 ipslinux@adaptec.com.
772 To compile this driver as a module, choose M here: the
773 module will be called ips.
775 config SCSI_IBMVSCSI
776 tristate "IBM Virtual SCSI support"
777 depends on PPC_PSERIES || PPC_ISERIES
778 help
779 This is the IBM POWER Virtual SCSI Client
781 To compile this driver as a module, choose M here: the
782 module will be called ibmvscsic.
784 config SCSI_INITIO
785 tristate "Initio 9100U(W) support"
786 depends on PCI && SCSI && BROKEN
787 help
788 This is support for the Initio 91XXU(W) SCSI host adapter. Please
789 read the SCSI-HOWTO, available from
790 <http://www.tldp.org/docs.html#howto>.
792 To compile this driver as a module, choose M here: the
793 module will be called initio.
795 config SCSI_INIA100
796 tristate "Initio INI-A100U2W support"
797 depends on PCI && SCSI
798 help
799 This is support for the Initio INI-A100U2W SCSI host adapter.
800 Please read the SCSI-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>.
803 To compile this driver as a module, choose M here: the
804 module will be called a100u2w.
806 config SCSI_PPA
807 tristate "IOMEGA parallel port (ppa - older drives)"
808 depends on SCSI && PARPORT
809 ---help---
810 This driver supports older versions of IOMEGA's parallel port ZIP
811 drive (a 100 MB removable media device).
813 Note that you can say N here if you have the SCSI version of the ZIP
814 drive: it will be supported automatically if you said Y to the
815 generic "SCSI disk support", above.
817 If you have the ZIP Plus drive or a more recent parallel port ZIP
818 drive (if the supplied cable with the drive is labeled "AutoDetect")
819 then you should say N here and Y to "IOMEGA parallel port (imm -
820 newer drives)", below.
822 For more information about this driver and how to use it you should
823 read the file <file:Documentation/scsi/ppa.txt>. You should also read
824 the SCSI-HOWTO, which is available from
825 <http://www.tldp.org/docs.html#howto>. If you use this driver,
826 you will still be able to use the parallel port for other tasks,
827 such as a printer; it is safe to compile both drivers into the
828 kernel.
830 To compile this driver as a module, choose M here: the
831 module will be called ppa.
833 config SCSI_IMM
834 tristate "IOMEGA parallel port (imm - newer drives)"
835 depends on SCSI && PARPORT
836 ---help---
837 This driver supports newer versions of IOMEGA's parallel port ZIP
838 drive (a 100 MB removable media device).
840 Note that you can say N here if you have the SCSI version of the ZIP
841 drive: it will be supported automatically if you said Y to the
842 generic "SCSI disk support", above.
844 If you have the ZIP Plus drive or a more recent parallel port ZIP
845 drive (if the supplied cable with the drive is labeled "AutoDetect")
846 then you should say Y here; if you have an older ZIP drive, say N
847 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
849 For more information about this driver and how to use it you should
850 read the file <file:Documentation/scsi/ppa.txt>. You should also read
851 the SCSI-HOWTO, which is available from
852 <http://www.tldp.org/docs.html#howto>. If you use this driver,
853 you will still be able to use the parallel port for other tasks,
854 such as a printer; it is safe to compile both drivers into the
855 kernel.
857 To compile this driver as a module, choose M here: the
858 module will be called imm.
860 config SCSI_IZIP_EPP16
861 bool "ppa/imm option - Use slow (but safe) EPP-16"
862 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
863 ---help---
864 EPP (Enhanced Parallel Port) is a standard for parallel ports which
865 allows them to act as expansion buses that can handle up to 64
866 peripheral devices.
868 Some parallel port chipsets are slower than their motherboard, and
869 so we have to control the state of the chipset's FIFO queue every
870 now and then to avoid data loss. This will be done if you say Y
871 here.
873 Generally, saying Y is the safe option and slows things down a bit.
875 config SCSI_IZIP_SLOW_CTR
876 bool "ppa/imm option - Assume slow parport control register"
877 depends on PARPORT && (SCSI_PPA || SCSI_IMM)
878 help
879 Some parallel ports are known to have excessive delays between
880 changing the parallel port control register and good data being
881 available on the parallel port data/status register. This option
882 forces a small delay (1.0 usec to be exact) after changing the
883 control register to let things settle out. Enabling this option may
884 result in a big drop in performance but some very old parallel ports
885 (found in 386 vintage machines) will not work properly.
887 Generally, saying N is fine.
889 config SCSI_NCR53C406A
890 tristate "NCR53c406a SCSI support"
891 depends on ISA && SCSI
892 help
893 This is support for the NCR53c406a SCSI host adapter. For user
894 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
895 in the kernel source. Also read the SCSI-HOWTO, available from
896 <http://www.tldp.org/docs.html#howto>.
898 To compile this driver as a module, choose M here: the
899 module will be called NCR53c406.
901 config SCSI_NCR_D700
902 tristate "NCR Dual 700 MCA SCSI support"
903 depends on MCA && SCSI
904 select SCSI_SPI_ATTRS
905 help
906 This is a driver for the MicroChannel Dual 700 card produced by
907 NCR and commonly used in 345x/35xx/4100 class machines. It always
908 tries to negotiate sync and uses tag command queueing.
910 Unless you have an NCR manufactured machine, the chances are that
911 you do not have this SCSI card, so say N.
913 config 53C700_IO_MAPPED
914 bool
915 depends on SCSI_NCR_D700
916 default y
918 config SCSI_LASI700
919 tristate "HP Lasi SCSI support for 53c700/710"
920 depends on GSC && SCSI
921 select SCSI_SPI_ATTRS
922 help
923 This is a driver for the SCSI controller in the Lasi chip found in
924 many PA-RISC workstations & servers. If you do not know whether you
925 have a Lasi chip, it is safe to say "Y" here.
927 config 53C700_MEM_MAPPED
928 bool
929 depends on SCSI_LASI700
930 default y
932 config 53C700_LE_ON_BE
933 bool
934 depends on SCSI_LASI700
935 default y
937 config SCSI_SYM53C8XX_2
938 tristate "SYM53C8XX Version 2 SCSI support"
939 depends on PCI && SCSI
940 select SCSI_SPI_ATTRS
941 ---help---
942 This driver supports the whole NCR53C8XX/SYM53C8XX family of
943 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
944 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
945 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
946 controllers; you need to use the Fusion MPT driver for that.
948 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
949 information.
951 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
952 int "DMA addressing mode"
953 depends on SCSI_SYM53C8XX_2
954 default "1"
955 ---help---
956 This option only applies to PCI-SCSI chips that are PCI DAC
957 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
959 When set to 0, the driver will program the chip to only perform
960 32-bit DMA. When set to 1, the chip will be able to perform DMA
961 to addresses up to 1TB. When set to 2, the driver supports the
962 full 64-bit DMA address range, but can only address 16 segments
963 of 4 GB each. This limits the total addressable range to 64 GB.
965 Most machines with less than 4GB of memory should use a setting
966 of 0 for best performance. If your machine has 4GB of memory
967 or more, you should set this option to 1 (the default).
969 The still experimental value 2 (64 bit DMA addressing with 16
970 x 4GB segments limitation) can be used on systems that require
971 PCI address bits past bit 39 to be set for the addressing of
972 memory using PCI DAC cycles.
974 config SCSI_SYM53C8XX_DEFAULT_TAGS
975 int "default tagged command queue depth"
976 depends on SCSI_SYM53C8XX_2
977 default "16"
978 help
979 This is the default value of the command queue depth the
980 driver will announce to the generic SCSI layer for devices
981 that support tagged command queueing. This value can be changed
982 from the boot command line. This is a soft limit that cannot
983 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
985 config SCSI_SYM53C8XX_MAX_TAGS
986 int "maximum number of queued commands"
987 depends on SCSI_SYM53C8XX_2
988 default "64"
989 help
990 This option allows you to specify the maximum number of commands
991 that can be queued to any device, when tagged command queuing is
992 possible. The driver supports up to 256 queued commands per device.
993 This value is used as a compiled-in hard limit.
995 config SCSI_SYM53C8XX_IOMAPPED
996 bool "use port IO"
997 depends on SCSI_SYM53C8XX_2
998 help
999 If you say Y here, the driver will use port IO to access
1000 the card. This is significantly slower then using memory
1001 mapped IO. Most people should answer N.
1003 config SCSI_IPR
1004 tristate "IBM Power Linux RAID adapter support"
1005 depends on PCI && SCSI
1006 select FW_LOADER
1007 ---help---
1008 This driver supports the IBM Power Linux family RAID adapters.
1009 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1010 as IBM iSeries 5702, 5703, 5709, and 570A.
1012 config SCSI_IPR_TRACE
1013 bool "enable driver internal trace"
1014 depends on SCSI_IPR
1015 help
1016 If you say Y here, the driver will trace all commands issued
1017 to the adapter. Performance impact is minimal. Trace can be
1018 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1020 config SCSI_IPR_DUMP
1021 bool "enable adapter dump support"
1022 depends on SCSI_IPR
1023 help
1024 If you say Y here, the driver will support adapter crash dump.
1025 If you enable this support, the iprdump daemon can be used
1026 to capture adapter failure analysis information.
1028 config SCSI_ZALON
1029 tristate "Zalon SCSI support"
1030 depends on GSC && SCSI
1031 help
1032 The Zalon is a GSC/HSC bus interface chip that sits between the
1033 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1034 C110, J200, J210 and some D, K & R-class machines. It's also
1035 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1036 Say Y here if you have one of these machines or cards.
1038 config SCSI_NCR_Q720
1039 tristate "NCR Quad 720 MCA SCSI support"
1040 depends on MCA && SCSI
1041 help
1042 This is a driver for the MicroChannel Quad 720 card produced by
1043 NCR and commonly used in 345x/35xx/4100 class machines. It always
1044 tries to negotiate sync and uses tag command queueing.
1046 Unless you have an NCR manufactured machine, the chances are that
1047 you do not have this SCSI card, so say N.
1049 config SCSI_NCR53C8XX_DEFAULT_TAGS
1050 int " default tagged command queue depth"
1051 depends on SCSI_ZALON || SCSI_NCR_Q720
1052 default "8"
1053 ---help---
1054 "Tagged command queuing" is a feature of SCSI-2 which improves
1055 performance: the host adapter can send several SCSI commands to a
1056 device's queue even if previous commands haven't finished yet.
1057 Because the device is intelligent, it can optimize its operations
1058 (like head positioning) based on its own request queue. Some SCSI
1059 devices don't implement this properly; if you want to disable this
1060 feature, enter 0 or 1 here (it doesn't matter which).
1062 The default value is 8 and should be supported by most hard disks.
1063 This value can be overridden from the boot command line using the
1064 'tags' option as follows (example):
1065 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1066 4, set queue depth to 16 for target 2 and target 3 on controller 0
1067 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1069 The normal answer therefore is to go with the default 8 and to use
1070 a boot command line option for devices that need to use a different
1071 command queue depth.
1073 There is no safe option other than using good SCSI devices.
1075 config SCSI_NCR53C8XX_MAX_TAGS
1076 int " maximum number of queued commands"
1077 depends on SCSI_ZALON || SCSI_NCR_Q720
1078 default "32"
1079 ---help---
1080 This option allows you to specify the maximum number of commands
1081 that can be queued to any device, when tagged command queuing is
1082 possible. The default value is 32. Minimum is 2, maximum is 64.
1083 Modern hard disks are able to support 64 tags and even more, but
1084 do not seem to be faster when more than 32 tags are being used.
1086 So, the normal answer here is to go with the default value 32 unless
1087 you are using very large hard disks with large cache (>= 1 MB) that
1088 are able to take advantage of more than 32 tagged commands.
1090 There is no safe option and the default answer is recommended.
1092 config SCSI_NCR53C8XX_SYNC
1093 int " synchronous transfers frequency in MHz"
1094 depends on SCSI_ZALON || SCSI_NCR_Q720
1095 default "20"
1096 ---help---
1097 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1098 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1099 are respectively the maximum data transfer rates in mega-transfers
1100 per second for each class. For example, a FAST-20 Wide 16 device is
1101 able to transfer data at 20 million 16 bit packets per second for a
1102 total rate of 40 MB/s.
1104 You may specify 0 if you want to only use asynchronous data
1105 transfers. This is the safest and slowest option. Otherwise, specify
1106 a value between 5 and 80, depending on the capability of your SCSI
1107 controller. The higher the number, the faster the data transfer.
1108 Note that 80 should normally be ok since the driver decreases the
1109 value automatically according to the controller's capabilities.
1111 Your answer to this question is ignored for controllers with NVRAM,
1112 since the driver will get this information from the user set-up. It
1113 also can be overridden using a boot setup option, as follows
1114 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1115 for FAST-20 synchronous data transfer (20 mega-transfers per
1116 second).
1118 The normal answer therefore is not to go with the default but to
1119 select the maximum value 80 allowing the driver to use the maximum
1120 value supported by each controller. If this causes problems with
1121 your SCSI devices, you should come back and decrease the value.
1123 There is no safe option other than using good cabling, right
1124 terminations and SCSI conformant devices.
1126 config SCSI_NCR53C8XX_PROFILE
1127 bool " enable profiling"
1128 depends on SCSI_ZALON || SCSI_NCR_Q720
1129 help
1130 This option allows you to enable profiling information gathering.
1131 These statistics are not very accurate due to the low frequency
1132 of the kernel clock (100 Hz on i386) and have performance impact
1133 on systems that use very fast devices.
1135 The normal answer therefore is N.
1137 config SCSI_NCR53C8XX_NO_DISCONNECT
1138 bool " not allow targets to disconnect"
1139 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1140 help
1141 This option is only provided for safety if you suspect some SCSI
1142 device of yours to not support properly the target-disconnect
1143 feature. In that case, you would say Y here. In general however, to
1144 not allow targets to disconnect is not reasonable if there is more
1145 than 1 device on a SCSI bus. The normal answer therefore is N.
1147 config SCSI_MCA_53C9X
1148 tristate "NCR MCA 53C9x SCSI support"
1149 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1150 help
1151 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1152 controller based on the NCR 53C94. This driver will allow use of
1153 the controller on the 3550, and very possibly others.
1155 To compile this driver as a module, choose M here: the
1156 module will be called mca_53c9x.
1158 config SCSI_PAS16
1159 tristate "PAS16 SCSI support"
1160 depends on ISA && SCSI
1161 ---help---
1162 This is support for a SCSI host adapter. It is explained in section
1163 3.10 of the SCSI-HOWTO, available from
1164 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1165 of the box, you may have to change some settings in
1166 <file:drivers/scsi/pas16.h>.
1168 To compile this driver as a module, choose M here: the
1169 module will be called pas16.
1171 config SCSI_PCI2000
1172 tristate "PCI2000 support"
1173 depends on PCI && SCSI && BROKEN
1174 help
1175 This is support for the PCI2000I EIDE interface card which acts as a
1176 SCSI host adapter. Please read the SCSI-HOWTO, available from
1177 <http://www.tldp.org/docs.html#howto>.
1179 To compile this driver as a module, choose M here: the
1180 module will be called pci2000.
1182 config SCSI_PCI2220I
1183 tristate "PCI2220i support"
1184 depends on PCI && SCSI && BROKEN
1185 help
1186 This is support for the PCI2220i EIDE interface card which acts as a
1187 SCSI host adapter. Please read the SCSI-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>.
1190 To compile this driver as a module, choose M here: the
1191 module will be called pci2220i.
1193 config SCSI_PSI240I
1194 tristate "PSI240i support"
1195 depends on ISA && SCSI
1196 help
1197 This is support for the PSI240i EIDE interface card which acts as a
1198 SCSI host adapter. Please read the SCSI-HOWTO, available from
1199 <http://www.tldp.org/docs.html#howto>.
1201 To compile this driver as a module, choose M here: the
1202 module will be called psi240i.
1204 config SCSI_QLOGIC_FAS
1205 tristate "Qlogic FAS SCSI support"
1206 depends on ISA && SCSI
1207 ---help---
1208 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1209 FastSCSI! cards as well as any other card based on the FASXX chip
1210 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1212 This driver does NOT support the PCI versions of these cards. The
1213 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1214 SCSI support"), below.
1216 Information about this driver is contained in
1217 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1218 SCSI-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here: the
1222 module will be called qlogicfas.
1224 config SCSI_QLOGIC_ISP
1225 tristate "Qlogic ISP SCSI support"
1226 depends on PCI && SCSI
1227 ---help---
1228 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
1229 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
1230 card is supported by the "AM53/79C974 PCI SCSI" driver.)
1232 If you say Y here, make sure to choose "BIOS" at the question "PCI
1233 access mode".
1235 Please read the file <file:Documentation/scsi/qlogicisp.txt>. You
1236 should also read the SCSI-HOWTO, available from
1237 <http://www.tldp.org/docs.html#howto>.
1239 To compile this driver as a module, choose M here: the
1240 module will be called qlogicisp.
1242 config SCSI_QLOGIC_FC
1243 tristate "Qlogic ISP FC SCSI support"
1244 depends on PCI && SCSI
1245 help
1246 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
1248 To compile this driver as a module, choose M here: the
1249 module will be called qlogicfc.
1251 config SCSI_QLOGIC_FC_FIRMWARE
1252 bool "Include loadable firmware in driver"
1253 depends on SCSI_QLOGIC_FC
1254 help
1255 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1256 expanded LUN addressing and FcTape (FCP-2) support, in the
1257 qlogicfc driver. This is required on some platforms.
1259 config SCSI_QLOGIC_1280
1260 tristate "Qlogic QLA 1280 SCSI support"
1261 depends on PCI && SCSI
1262 help
1263 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
1265 To compile this driver as a module, choose M here: the
1266 module will be called qla1280.
1268 config SCSI_QLOGICPTI
1269 tristate "PTI Qlogic, ISP Driver"
1270 depends on SBUS && SCSI
1271 help
1272 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1273 controllers are known under Solaris as qpti and in the openprom as
1274 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1275 driven by a different driver.
1277 To compile this driver as a module, choose M here: the
1278 module will be called qlogicpti.
1280 source "drivers/scsi/qla2xxx/Kconfig"
1282 config SCSI_SEAGATE
1283 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1284 depends on X86 && ISA && SCSI && BROKEN
1285 ---help---
1286 These are 8-bit SCSI controllers; the ST-01 is also supported by
1287 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1288 available from <http://www.tldp.org/docs.html#howto>. If it
1289 doesn't work out of the box, you may have to change some settings in
1290 <file:drivers/scsi/seagate.h>.
1292 To compile this driver as a module, choose M here: the
1293 module will be called seagate.
1295 # definitely looks not 64bit safe:
1296 config SCSI_SIM710
1297 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1298 depends on (EISA || MCA) && SCSI
1299 select SCSI_SPI_ATTRS
1300 ---help---
1301 This driver for NCR53c710 based SCSI host adapters.
1303 It currently supports Compaq EISA cards and NCR MCA cards
1305 config 53C700_IO_MAPPED
1306 bool
1307 depends on SCSI_SIM710
1308 default y
1310 config SCSI_SYM53C416
1311 tristate "Symbios 53c416 SCSI support"
1312 depends on ISA && SCSI
1313 ---help---
1314 This is support for the sym53c416 SCSI host adapter, the SCSI
1315 adapter that comes with some HP scanners. This driver requires that
1316 the sym53c416 is configured first using some sort of PnP
1317 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1318 are using isapnp then you need to compile this driver as a module
1319 and then load it using insmod after isapnp has run. The parameters
1320 of the configured card(s) should be passed to the driver. The format
1321 is:
1323 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1325 To compile this driver as a module, choose M here: the
1326 module will be called sym53c416.
1328 config SCSI_DC395x
1329 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1330 depends on PCI && SCSI && EXPERIMENTAL
1331 ---help---
1332 This driver supports PCI SCSI host adapters based on the ASIC
1333 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1335 This driver works, but is still in experimental status. So better
1336 have a bootable disk and a backup in case of emergency.
1338 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1340 To compile this driver as a module, choose M here: the
1341 module will be called dc395x.
1343 config SCSI_DC390T
1344 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1345 depends on PCI && SCSI
1346 ---help---
1347 This driver supports PCI SCSI host adapters based on the Am53C974A
1348 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1349 PCscsi/PCnet (Am53/79C974) solutions.
1351 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1353 Note that this driver does NOT support Tekram DC390W/U/F, which are
1354 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1356 To compile this driver as a module, choose M here: the
1357 module will be called tmscsim.
1359 config SCSI_T128
1360 tristate "Trantor T128/T128F/T228 SCSI support"
1361 depends on ISA && SCSI
1362 ---help---
1363 This is support for a SCSI host adapter. It is explained in section
1364 3.11 of the SCSI-HOWTO, available from
1365 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1366 of the box, you may have to change some settings in
1367 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1368 Adaptec, and some former Trantor products are being sold under the
1369 Adaptec name.
1371 To compile this driver as a module, choose M here: the
1372 module will be called t128.
1374 config SCSI_U14_34F
1375 tristate "UltraStor 14F/34F support"
1376 depends on ISA && SCSI
1377 ---help---
1378 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1379 The source at <file:drivers/scsi/u14-34f.c> contains some
1380 information about this hardware. If the driver doesn't work out of
1381 the box, you may have to change some settings in
1382 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1383 <http://www.tldp.org/docs.html#howto>. Note that there is also
1384 another driver for the same hardware: "UltraStor SCSI support",
1385 below. You should say Y to both only if you want 24F support as
1386 well.
1388 To compile this driver as a module, choose M here: the
1389 module will be called u14-34f.
1391 config SCSI_U14_34F_TAGGED_QUEUE
1392 bool "enable tagged command queueing"
1393 depends on SCSI_U14_34F
1394 help
1395 This is a feature of SCSI-2 which improves performance: the host
1396 adapter can send several SCSI commands to a device's queue even if
1397 previous commands haven't finished yet.
1398 This is equivalent to the "u14-34f=tc:y" boot option.
1400 config SCSI_U14_34F_LINKED_COMMANDS
1401 bool "enable elevator sorting"
1402 depends on SCSI_U14_34F
1403 help
1404 This option enables elevator sorting for all probed SCSI disks and
1405 CD-ROMs. It definitely reduces the average seek distance when doing
1406 random seeks, but this does not necessarily result in a noticeable
1407 performance improvement: your mileage may vary...
1408 This is equivalent to the "u14-34f=lc:y" boot option.
1410 config SCSI_U14_34F_MAX_TAGS
1411 int "maximum number of queued commands"
1412 depends on SCSI_U14_34F
1413 default "8"
1414 help
1415 This specifies how many SCSI commands can be maximally queued for
1416 each probed SCSI device. You should reduce the default value of 8
1417 only if you have disks with buggy or limited tagged command support.
1418 Minimum is 2 and maximum is 14. This value is also the window size
1419 used by the elevator sorting option above. The effective value used
1420 by the driver for each probed SCSI device is reported at boot time.
1421 This is equivalent to the "u14-34f=mq:8" boot option.
1423 config SCSI_ULTRASTOR
1424 tristate "UltraStor SCSI support"
1425 depends on X86 && ISA && SCSI
1426 ---help---
1427 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1428 adapter family. This driver is explained in section 3.12 of the
1429 SCSI-HOWTO, available from
1430 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1431 of the box, you may have to change some settings in
1432 <file:drivers/scsi/ultrastor.h>.
1434 Note that there is also another driver for the same hardware:
1435 "UltraStor 14F/34F support", above.
1437 To compile this driver as a module, choose M here: the
1438 module will be called ultrastor.
1440 config SCSI_NSP32
1441 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1442 depends on PCI && SCSI && !64BIT
1443 help
1444 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1445 SCSI host adapter. Please read the SCSI-HOWTO, available from
1446 <http://www.tldp.org/docs.html#howto>.
1448 To compile this driver as a module, choose M here: the
1449 module will be called nsp32.
1451 config SCSI_DEBUG
1452 tristate "SCSI debugging host simulator"
1453 depends on SCSI
1454 help
1455 This is a host adapter simulator that can simulate multiple hosts
1456 each with multiple dummy SCSI devices (disks). It defaults to one
1457 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1458 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1459 dummy disks are simulated, they share the same kernel RAM for
1460 their storage. See http://www.torque.net/sg/sdebug.html for more
1461 information. This driver is primarily of use to those testing the
1462 SCSI and block subsystems. If unsure, say N.
1464 config SCSI_MESH
1465 tristate "MESH (Power Mac internal SCSI) support"
1466 depends on PPC32 && PPC_PMAC && SCSI
1467 help
1468 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1469 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1470 other Power Macintoshes do). Say Y to include support for this SCSI
1471 adaptor.
1473 To compile this driver as a module, choose M here: the
1474 module will be called mesh.
1476 config SCSI_MESH_SYNC_RATE
1477 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1478 depends on SCSI_MESH
1479 default "5"
1480 help
1481 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1482 drives a bus which is entirely internal to the machine (such as the
1483 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1484 operation at up to 10 MB/s. On machines where the SCSI bus
1485 controlled by the MESH can have external devices connected, it is
1486 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1487 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1488 to disable synchronous operation.
1490 config SCSI_MESH_RESET_DELAY_MS
1491 int "initial bus reset delay (ms) (0 = no reset)"
1492 depends on SCSI_MESH
1493 default "4000"
1495 config SCSI_MAC53C94
1496 tristate "53C94 (Power Mac external SCSI) support"
1497 depends on PPC_PMAC && SCSI
1498 help
1499 On Power Macintoshes (and clones) with two SCSI buses, the external
1500 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1501 machines which only have one SCSI bus, such as the 7200, also use
1502 the 53C94. Say Y to include support for the 53C94.
1504 To compile this driver as a module, choose M here: the
1505 module will be called mac53c94.
1507 source "drivers/scsi/arm/Kconfig"
1509 config JAZZ_ESP
1510 bool "MIPS JAZZ FAS216 SCSI support"
1511 depends on MACH_JAZZ && SCSI
1512 help
1513 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1514 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1515 systems.
1517 config A3000_SCSI
1518 tristate "A3000 WD33C93A support"
1519 depends on AMIGA && SCSI
1520 help
1521 If you have an Amiga 3000 and have SCSI devices connected to the
1522 built-in SCSI controller, say Y. Otherwise, say N.
1524 To compile this driver as a module, choose M here: the
1525 module will be called wd33c93.
1527 config A2091_SCSI
1528 tristate "A2091/A590 WD33C93A support"
1529 depends on ZORRO && SCSI
1530 help
1531 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1532 say N.
1534 To compile this driver as a module, choose M here: the
1535 module will be called wd33c93.
1537 config GVP11_SCSI
1538 tristate "GVP Series II WD33C93A support"
1539 depends on ZORRO && SCSI
1540 ---help---
1541 If you have a Great Valley Products Series II SCSI controller,
1542 answer Y. Also say Y if you have a later model of GVP SCSI
1543 controller (such as the GVP A4008 or a Combo board). Otherwise,
1544 answer N. This driver does NOT work for the T-Rex series of
1545 accelerators from TekMagic and GVP-M.
1547 To compile this driver as a module, choose M here: the
1548 module will be called gvp11.
1550 config CYBERSTORM_SCSI
1551 tristate "CyberStorm SCSI support"
1552 depends on ZORRO && SCSI
1553 help
1554 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1555 accelerator board and the optional Cyberstorm SCSI controller,
1556 answer Y. Otherwise, say N.
1558 config CYBERSTORMII_SCSI
1559 tristate "CyberStorm Mk II SCSI support"
1560 depends on ZORRO && SCSI
1561 help
1562 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1563 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1564 answer N.
1566 config BLZ2060_SCSI
1567 tristate "Blizzard 2060 SCSI support"
1568 depends on ZORRO && SCSI
1569 help
1570 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1571 and want to use the onboard SCSI controller, say Y. Otherwise,
1572 answer N.
1574 config BLZ1230_SCSI
1575 tristate "Blizzard 1230IV/1260 SCSI support"
1576 depends on ZORRO && SCSI
1577 help
1578 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1579 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1580 say N.
1582 config FASTLANE_SCSI
1583 tristate "Fastlane SCSI support"
1584 depends on ZORRO && SCSI
1585 help
1586 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1587 one in the near future, say Y to this question. Otherwise, say N.
1589 config SCSI_AMIGA7XX
1590 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1591 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1592 help
1593 Support for various NCR53c710-based SCSI controllers on the Amiga.
1594 This includes:
1595 - the builtin SCSI controller on the Amiga 4000T,
1596 - the Amiga 4091 Zorro III SCSI-2 controller,
1597 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1598 (info at
1599 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1600 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1601 accelerator card for the Amiga 1200,
1602 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1603 Note that all of the above SCSI controllers, except for the builtin
1604 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1605 bus, so you also have to enable Zorro bus support if you want to use
1606 them.
1608 config OKTAGON_SCSI
1609 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1610 depends on ZORRO && SCSI && EXPERIMENTAL
1611 help
1612 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1613 Y to this question. If you're in doubt about whether you have one,
1614 see the picture at
1615 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1617 config ATARI_SCSI
1618 tristate "Atari native SCSI support"
1619 depends on ATARI && SCSI && BROKEN
1620 ---help---
1621 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1622 Falcon, ...) say Y to get it supported. Of course also, if you have
1623 a compatible SCSI controller (e.g. for Medusa).
1625 To compile this driver as a module, choose M here: the
1626 module will be called atari_scsi.
1628 This driver supports both styles of NCR integration into the
1629 system: the TT style (separate DMA), and the Falcon style (via
1630 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1631 in the Hades (without DMA).
1633 config ATARI_SCSI_TOSHIBA_DELAY
1634 bool "Long delays for Toshiba CD-ROMs"
1635 depends on ATARI_SCSI
1636 help
1637 This option increases the delay after a SCSI arbitration to
1638 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1639 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1640 would impact performance a bit, so say N.
1642 config ATARI_SCSI_RESET_BOOT
1643 bool "Reset SCSI-devices at boottime"
1644 depends on ATARI_SCSI
1645 help
1646 Reset the devices on your Atari whenever it boots. This makes the
1647 boot process fractionally longer but may assist recovery from errors
1648 that leave the devices with SCSI operations partway completed.
1650 config TT_DMA_EMUL
1651 bool "Hades SCSI DMA emulator"
1652 depends on ATARI_SCSI && HADES
1653 help
1654 This option enables code which emulates the TT SCSI DMA chip on the
1655 Hades. This increases the SCSI transfer rates at least ten times
1656 compared to PIO transfers.
1658 config MAC_SCSI
1659 bool "Macintosh NCR5380 SCSI"
1660 depends on MAC && SCSI
1661 help
1662 This is the NCR 5380 SCSI controller included on most of the 68030
1663 based Macintoshes. If you have one of these say Y and read the
1664 SCSI-HOWTO, available from
1665 <http://www.tldp.org/docs.html#howto>.
1667 config SCSI_MAC_ESP
1668 tristate "Macintosh NCR53c9[46] SCSI"
1669 depends on MAC && SCSI
1670 help
1671 This is the NCR 53c9x SCSI controller found on most of the 68040
1672 based Macintoshes. If you have one of these say Y and read the
1673 SCSI-HOWTO, available from
1674 <http://www.tldp.org/docs.html#howto>.
1676 To compile this driver as a module, choose M here: the
1677 module will be called mac_esp.
1679 config MVME147_SCSI
1680 bool "WD33C93 SCSI driver for MVME147"
1681 depends on MVME147 && SCSI
1682 help
1683 Support for the on-board SCSI controller on the Motorola MVME147
1684 single-board computer.
1686 config MVME16x_SCSI
1687 bool "NCR53C710 SCSI driver for MVME16x"
1688 depends on MVME16x && SCSI && BROKEN
1689 help
1690 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1691 SCSI controller chip. Almost everyone using one of these boards
1692 will want to say Y to this question.
1694 config BVME6000_SCSI
1695 bool "NCR53C710 SCSI driver for BVME6000"
1696 depends on BVME6000 && SCSI && BROKEN
1697 help
1698 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1699 SCSI controller chip. Almost everyone using one of these boards
1700 will want to say Y to this question.
1702 config SCSI_NCR53C7xx_FAST
1703 bool "allow FAST-SCSI [10MHz]"
1704 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1705 help
1706 This will enable 10MHz FAST-SCSI transfers with your host
1707 adapter. Some systems have problems with that speed, so it's safest
1708 to say N here.
1710 config SUN3_SCSI
1711 tristate "Sun3 NCR5380 SCSI"
1712 depends on SUN3 && SCSI
1713 help
1714 This option will enable support for the OBIO (onboard io) NCR5380
1715 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1716 "Sun3" type VME scsi controllers also based on the NCR5380.
1717 General Linux information on the Sun 3 series (now discontinued)
1718 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1720 config SUN3X_ESP
1721 bool "Sun3x ESP SCSI"
1722 depends on SUN3X && SCSI
1723 help
1724 The ESP was an on-board SCSI controller used on Sun 3/80
1725 machines. Say Y here to compile in support for it.
1727 config SCSI_SUNESP
1728 tristate "Sparc ESP Scsi Driver"
1729 depends on SBUS && SCSI
1730 help
1731 This is the driver for the Sun ESP SCSI host adapter. The ESP
1732 chipset is present in most SPARC SBUS-based computers.
1734 To compile this driver as a module, choose M here: the
1735 module will be called esp.
1737 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1739 config ZFCP
1740 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1741 depends on ARCH_S390 && SCSI
1742 select SCSI_FC_ATTRS
1743 help
1744 If you want to access SCSI devices attached to your IBM eServer
1745 zSeries by means of Fibre Channel interfaces say Y.
1746 For details please refer to the documentation provided by IBM at
1747 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1749 This driver is also available as a module. This module will be
1750 called zfcp. If you want to compile it as a module, say M here
1751 and read Documentation/modules.txt.
1753 endmenu
1755 source "drivers/scsi/pcmcia/Kconfig"
1757 endmenu