]> git.proxmox.com Git - mirror_ubuntu-jammy-kernel.git/blob - drivers/scsi/Kconfig
Merge branch 'upstream'
[mirror_ubuntu-jammy-kernel.git] / drivers / scsi / Kconfig
1 menu "SCSI device support"
2
3 config RAID_ATTRS
4 tristate "RAID Transport Class"
5 default n
6 ---help---
7 Provides RAID
8
9 config SCSI
10 tristate "SCSI device support"
11 ---help---
12 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
13 any other SCSI device under Linux, say Y and make sure that you know
14 the name of your SCSI host adapter (the card inside your computer
15 that "speaks" the SCSI protocol, also called SCSI controller),
16 because you will be asked for it.
17
18 You also need to say Y here if you have a device which speaks
19 the SCSI protocol. Examples of this include the parallel port
20 version of the IOMEGA ZIP drive, USB storage devices, Fibre
21 Channel, FireWire storage and the IDE-SCSI emulation driver.
22
23 To compile this driver as a module, choose M here and read
24 <file:Documentation/scsi/scsi.txt>.
25 The module will be called scsi_mod.
26
27 However, do not compile this as a module if your root file system
28 (the one containing the directory /) is located on a SCSI device.
29
30 config SCSI_PROC_FS
31 bool "legacy /proc/scsi/ support"
32 depends on SCSI && PROC_FS
33 default y
34 ---help---
35 This option enables support for the various files in
36 /proc/scsi. In Linux 2.6 this has been superceeded by
37 files in sysfs but many legacy applications rely on this.
38
39 If unusure say Y.
40
41 comment "SCSI support type (disk, tape, CD-ROM)"
42 depends on SCSI
43
44 config BLK_DEV_SD
45 tristate "SCSI disk support"
46 depends on SCSI
47 ---help---
48 If you want to use SCSI hard disks, Fibre Channel disks,
49 USB storage or the SCSI or parallel port version of
50 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
51 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
52 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
53 CD-ROMs.
54
55 To compile this driver as a module, choose M here and read
56 <file:Documentation/scsi/scsi.txt>.
57 The module will be called sd_mod.
58
59 Do not compile this driver as a module if your root file system
60 (the one containing the directory /) is located on a SCSI disk.
61 In this case, do not compile the driver for your SCSI host adapter
62 (below) as a module either.
63
64 config CHR_DEV_ST
65 tristate "SCSI tape support"
66 depends on SCSI
67 ---help---
68 If you want to use a SCSI tape drive under Linux, say Y and read the
69 SCSI-HOWTO, available from
70 <http://www.tldp.org/docs.html#howto>, and
71 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
72 for SCSI CD-ROMs.
73
74 To compile this driver as a module, choose M here and read
75 <file:Documentation/scsi/scsi.txt>. The module will be called st.
76
77 config CHR_DEV_OSST
78 tristate "SCSI OnStream SC-x0 tape support"
79 depends on SCSI
80 ---help---
81 The OnStream SC-x0 SCSI tape drives can not be driven by the
82 standard st driver, but instead need this special osst driver and
83 use the /dev/osstX char device nodes (major 206). Via usb-storage
84 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
85 as well. Note that there is also a second generation of OnStream
86 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
87 tapes (QIC-157) and can be driven by the standard driver st.
88 For more information, you may have a look at the SCSI-HOWTO
89 <http://www.tldp.org/docs.html#howto> and
90 <file:Documentation/scsi/osst.txt> in the kernel source.
91 More info on the OnStream driver may be found on
92 <http://linux1.onstream.nl/test/>
93 Please also have a look at the standard st docu, as most of it
94 applies to osst as well.
95
96 To compile this driver as a module, choose M here and read
97 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
98
99 config BLK_DEV_SR
100 tristate "SCSI CDROM support"
101 depends on SCSI
102 ---help---
103 If you want to use a SCSI or FireWire CD-ROM under Linux,
104 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
105 <http://www.tldp.org/docs.html#howto>. Also make sure to say
106 Y or M to "ISO 9660 CD-ROM file system support" later.
107
108 To compile this driver as a module, choose M here and read
109 <file:Documentation/scsi/scsi.txt>.
110 The module will be called sr_mod.
111
112 config BLK_DEV_SR_VENDOR
113 bool "Enable vendor-specific extensions (for SCSI CDROM)"
114 depends on BLK_DEV_SR
115 help
116 This enables the usage of vendor specific SCSI commands. This is
117 required to support multisession CDs with old NEC/TOSHIBA cdrom
118 drives (and HP Writers). If you have such a drive and get the first
119 session only, try saying Y here; everybody else says N.
120
121 config CHR_DEV_SG
122 tristate "SCSI generic support"
123 depends on SCSI
124 ---help---
125 If you want to use SCSI scanners, synthesizers or CD-writers or just
126 about anything having "SCSI" in its name other than hard disks,
127 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
128 directly, so you need some additional software which knows how to
129 talk to these devices using the SCSI protocol:
130
131 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
132 writer software look at Cdrtools
133 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
134 and for burning a "disk at once": CDRDAO
135 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
136 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
137 For other devices, it's possible that you'll have to write the
138 driver software yourself. Please read the file
139 <file:Documentation/scsi/scsi-generic.txt> for more information.
140
141 To compile this driver as a module, choose M here and read
142 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
143
144 If unsure, say N.
145
146 config CHR_DEV_SCH
147 tristate "SCSI media changer support"
148 depends on SCSI
149 ---help---
150 This is a driver for SCSI media changers. Most common devices are
151 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
152 don't need this for those tiny 6-slot cdrom changers. Media
153 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
154 If you have such hardware and want to use it with linux, say Y
155 here. Check <file:Documentation/scsi-changer.txt> for details.
156
157 If you want to compile this as a module ( = code which can be
158 inserted in and removed from the running kernel whenever you want),
159 say M here and read <file:Documentation/modules.txt> and
160 <file:Documentation/scsi.txt>. The module will be called ch.o.
161 If unsure, say N.
162
163
164 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
165 depends on SCSI
166
167 config SCSI_MULTI_LUN
168 bool "Probe all LUNs on each SCSI device"
169 depends on SCSI
170 help
171 If you have a SCSI device that supports more than one LUN (Logical
172 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
173 can say Y here to force the SCSI driver to probe for multiple LUNs.
174 A SCSI device with multiple LUNs acts logically like multiple SCSI
175 devices. The vast majority of SCSI devices have only one LUN, and
176 so most people can say N here. The max_luns boot/module parameter
177 allows to override this setting.
178
179 config SCSI_CONSTANTS
180 bool "Verbose SCSI error reporting (kernel size +=12K)"
181 depends on SCSI
182 help
183 The error messages regarding your SCSI hardware will be easier to
184 understand if you say Y here; it will enlarge your kernel by about
185 12 KB. If in doubt, say Y.
186
187 config SCSI_LOGGING
188 bool "SCSI logging facility"
189 depends on SCSI
190 ---help---
191 This turns on a logging facility that can be used to debug a number
192 of SCSI related problems.
193
194 If you say Y here, no logging output will appear by default, but you
195 can enable logging by saying Y to "/proc file system support" and
196 "Sysctl support" below and executing the command
197
198 echo "scsi log token [level]" > /proc/scsi/scsi
199
200 at boot time after the /proc file system has been mounted.
201
202 There are a number of things that can be used for 'token' (you can
203 find them in the source: <file:drivers/scsi/scsi.c>), and this
204 allows you to select the types of information you want, and the
205 level allows you to select the level of verbosity.
206
207 If you say N here, it may be harder to track down some types of SCSI
208 problems. If you say Y here your kernel will be somewhat larger, but
209 there should be no noticeable performance impact as long as you have
210 logging turned off.
211
212 menu "SCSI Transport Attributes"
213 depends on SCSI
214
215 config SCSI_SPI_ATTRS
216 tristate "Parallel SCSI (SPI) Transport Attributes"
217 depends on SCSI
218 help
219 If you wish to export transport-specific information about
220 each attached SCSI device to sysfs, say Y. Otherwise, say N.
221
222 config SCSI_FC_ATTRS
223 tristate "FiberChannel Transport Attributes"
224 depends on SCSI
225 help
226 If you wish to export transport-specific information about
227 each attached FiberChannel device to sysfs, say Y.
228 Otherwise, say N.
229
230 config SCSI_ISCSI_ATTRS
231 tristate "iSCSI Transport Attributes"
232 depends on SCSI && NET
233 help
234 If you wish to export transport-specific information about
235 each attached iSCSI device to sysfs, say Y.
236 Otherwise, say N.
237
238 config SCSI_SAS_ATTRS
239 tristate "SAS Transport Attributes"
240 depends on SCSI
241 help
242 If you wish to export transport-specific information about
243 each attached SAS device to sysfs, say Y.
244
245 endmenu
246
247 menu "SCSI low-level drivers"
248 depends on SCSI!=n
249
250 config ISCSI_TCP
251 tristate "iSCSI Initiator over TCP/IP"
252 depends on SCSI && INET
253 select CRYPTO
254 select CRYPTO_MD5
255 select CRYPTO_CRC32C
256 select SCSI_ISCSI_ATTRS
257 help
258 The iSCSI Driver provides a host with the ability to access storage
259 through an IP network. The driver uses the iSCSI protocol to transport
260 SCSI requests and responses over a TCP/IP network between the host
261 (the "initiator") and "targets". Architecturally, the iSCSI driver
262 combines with the host's TCP/IP stack, network drivers, and Network
263 Interface Card (NIC) to provide the same functions as a SCSI or a
264 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
265
266 To compile this driver as a module, choose M here: the
267 module will be called iscsi_tcp.
268
269 The userspace component needed to initialize the driver, documentation,
270 and sample configuration files can be found here:
271
272 http://linux-iscsi.sf.net
273
274 config SGIWD93_SCSI
275 tristate "SGI WD93C93 SCSI Driver"
276 depends on SGI_IP22 && SCSI
277 help
278 If you have a Western Digital WD93 SCSI controller on
279 an SGI MIPS system, say Y. Otherwise, say N.
280
281 config SCSI_DECNCR
282 tristate "DEC NCR53C94 Scsi Driver"
283 depends on MACH_DECSTATION && SCSI && TC
284 help
285 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
286 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
287
288 config SCSI_DECSII
289 tristate "DEC SII Scsi Driver"
290 depends on MACH_DECSTATION && SCSI && 32BIT
291
292 config BLK_DEV_3W_XXXX_RAID
293 tristate "3ware 5/6/7/8xxx ATA-RAID support"
294 depends on PCI && SCSI
295 help
296 3ware is the only hardware ATA-Raid product in Linux to date.
297 This card is 2,4, or 8 channel master mode support only.
298 SCSI support required!!!
299
300 <http://www.3ware.com/>
301
302 Please read the comments at the top of
303 <file:drivers/scsi/3w-xxxx.c>.
304
305 config SCSI_3W_9XXX
306 tristate "3ware 9xxx SATA-RAID support"
307 depends on PCI && SCSI
308 help
309 This driver supports the 9000 series 3ware SATA-RAID cards.
310
311 <http://www.amcc.com>
312
313 Please read the comments at the top of
314 <file:drivers/scsi/3w-9xxx.c>.
315
316 config SCSI_7000FASST
317 tristate "7000FASST SCSI support"
318 depends on ISA && SCSI && ISA_DMA_API
319 help
320 This driver supports the Western Digital 7000 SCSI host adapter
321 family. Some information is in the source:
322 <file:drivers/scsi/wd7000.c>.
323
324 To compile this driver as a module, choose M here: the
325 module will be called wd7000.
326
327 config SCSI_ACARD
328 tristate "ACARD SCSI support"
329 depends on PCI && SCSI
330 help
331 This driver supports the ACARD SCSI host adapter.
332 Support Chip <ATP870 ATP876 ATP880 ATP885>
333 To compile this driver as a module, choose M here: the
334 module will be called atp870u.
335
336 config SCSI_AHA152X
337 tristate "Adaptec AHA152X/2825 support"
338 depends on ISA && SCSI && !64BIT
339 select SCSI_SPI_ATTRS
340 ---help---
341 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
342 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
343 must be manually specified in this case.
344
345 It is explained in section 3.3 of the SCSI-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>. You might also want to
347 read the file <file:Documentation/scsi/aha152x.txt>.
348
349 To compile this driver as a module, choose M here: the
350 module will be called aha152x.
351
352 config SCSI_AHA1542
353 tristate "Adaptec AHA1542 support"
354 depends on ISA && SCSI && ISA_DMA_API
355 ---help---
356 This is support for a SCSI host adapter. It is explained in section
357 3.4 of the SCSI-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
359 purchased by Adaptec, and some former Trantor products are being
360 sold under the Adaptec name. If it doesn't work out of the box, you
361 may have to change some settings in <file:drivers/scsi/aha1542.h>.
362
363 To compile this driver as a module, choose M here: the
364 module will be called aha1542.
365
366 config SCSI_AHA1740
367 tristate "Adaptec AHA1740 support"
368 depends on EISA && SCSI
369 ---help---
370 This is support for a SCSI host adapter. It is explained in section
371 3.5 of the SCSI-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
373 of the box, you may have to change some settings in
374 <file:drivers/scsi/aha1740.h>.
375
376 To compile this driver as a module, choose M here: the
377 module will be called aha1740.
378
379 config SCSI_AACRAID
380 tristate "Adaptec AACRAID support"
381 depends on SCSI && PCI
382 help
383 This driver supports a variety of Dell, HP, Adaptec, IBM and
384 ICP storage products. For a list of supported products, refer
385 to <file:Documentation/scsi/aacraid.txt>.
386
387 To compile this driver as a module, choose M here: the module
388 will be called aacraid.
389
390
391 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
392
393 config SCSI_AIC7XXX_OLD
394 tristate "Adaptec AIC7xxx support (old driver)"
395 depends on (ISA || EISA || PCI ) && SCSI
396 help
397 WARNING This driver is an older aic7xxx driver and is no longer
398 under active development. Adaptec, Inc. is writing a new driver to
399 take the place of this one, and it is recommended that whenever
400 possible, people should use the new Adaptec written driver instead
401 of this one. This driver will eventually be phased out entirely.
402
403 This is support for the various aic7xxx based Adaptec SCSI
404 controllers. These include the 274x EISA cards; 284x VLB cards;
405 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
406 motherboard based SCSI controllers from Adaptec. It does not support
407 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
408 support them. It does not support the 2920 cards from Adaptec that
409 use the Future Domain SCSI controller chip. For those cards, you
410 need the "Future Domain 16xx SCSI support" driver.
411
412 In general, if the controller is based on an Adaptec SCSI controller
413 chip from the aic777x series or the aic78xx series, this driver
414 should work. The only exception is the 7810 which is specifically
415 not supported (that's the RAID controller chip on the AAA-13x
416 cards).
417
418 Note that the AHA2920 SCSI host adapter is *not* supported by this
419 driver; choose "Future Domain 16xx SCSI support" instead if you have
420 one of those.
421
422 Information on the configuration options for this controller can be
423 found by checking the help file for each of the available
424 configuration options. You should read
425 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
426 contacting the maintainer with any questions. The SCSI-HOWTO,
427 available from <http://www.tldp.org/docs.html#howto>, can also
428 be of great help.
429
430 To compile this driver as a module, choose M here: the
431 module will be called aic7xxx_old.
432
433 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
434
435 # All the I2O code and drivers do not seem to be 64bit safe.
436 config SCSI_DPT_I2O
437 tristate "Adaptec I2O RAID support "
438 depends on !64BIT && SCSI && PCI
439 help
440 This driver supports all of Adaptec's I2O based RAID controllers as
441 well as the DPT SmartRaid V cards. This is an Adaptec maintained
442 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
443
444 To compile this driver as a module, choose M here: the
445 module will be called dpt_i2o.
446
447 config SCSI_ADVANSYS
448 tristate "AdvanSys SCSI support"
449 depends on (ISA || EISA || PCI) && SCSI && BROKEN
450 help
451 This is a driver for all SCSI host adapters manufactured by
452 AdvanSys. It is documented in the kernel source in
453 <file:drivers/scsi/advansys.c>.
454
455 To compile this driver as a module, choose M here: the
456 module will be called advansys.
457
458 config SCSI_IN2000
459 tristate "Always IN2000 SCSI support"
460 depends on ISA && SCSI
461 help
462 This is support for an ISA bus SCSI host adapter. You'll find more
463 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
464 out of the box, you may have to change the jumpers for IRQ or
465 address selection.
466
467 To compile this driver as a module, choose M here: the
468 module will be called in2000.
469
470 source "drivers/scsi/megaraid/Kconfig.megaraid"
471
472 config SCSI_SATA
473 tristate "Serial ATA (SATA) support"
474 depends on SCSI
475 help
476 This driver family supports Serial ATA host controllers
477 and devices.
478
479 If unsure, say N.
480
481 config SCSI_SATA_AHCI
482 tristate "AHCI SATA support"
483 depends on SCSI_SATA && PCI
484 help
485 This option enables support for AHCI Serial ATA.
486
487 If unsure, say N.
488
489 config SCSI_SATA_SVW
490 tristate "ServerWorks Frodo / Apple K2 SATA support"
491 depends on SCSI_SATA && PCI
492 help
493 This option enables support for Broadcom/Serverworks/Apple K2
494 SATA support.
495
496 If unsure, say N.
497
498 config SCSI_ATA_PIIX
499 tristate "Intel PIIX/ICH SATA support"
500 depends on SCSI_SATA && PCI
501 help
502 This option enables support for ICH5 Serial ATA.
503 If PATA support was enabled previously, this enables
504 support for select Intel PIIX/ICH PATA host controllers.
505
506 If unsure, say N.
507
508 config SCSI_SATA_MV
509 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
510 depends on SCSI_SATA && PCI && EXPERIMENTAL
511 help
512 This option enables support for the Marvell Serial ATA family.
513 Currently supports 88SX[56]0[48][01] chips.
514
515 If unsure, say N.
516
517 config SCSI_SATA_NV
518 tristate "NVIDIA SATA support"
519 depends on SCSI_SATA && PCI && EXPERIMENTAL
520 help
521 This option enables support for NVIDIA Serial ATA.
522
523 If unsure, say N.
524
525 config SCSI_PDC_ADMA
526 tristate "Pacific Digital ADMA support"
527 depends on SCSI_SATA && PCI
528 help
529 This option enables support for Pacific Digital ADMA controllers
530
531 If unsure, say N.
532
533 config SCSI_SATA_QSTOR
534 tristate "Pacific Digital SATA QStor support"
535 depends on SCSI_SATA && PCI
536 help
537 This option enables support for Pacific Digital Serial ATA QStor.
538
539 If unsure, say N.
540
541 config SCSI_SATA_PROMISE
542 tristate "Promise SATA TX2/TX4 support"
543 depends on SCSI_SATA && PCI
544 help
545 This option enables support for Promise Serial ATA TX2/TX4.
546
547 If unsure, say N.
548
549 config SCSI_SATA_SX4
550 tristate "Promise SATA SX4 support"
551 depends on SCSI_SATA && PCI && EXPERIMENTAL
552 help
553 This option enables support for Promise Serial ATA SX4.
554
555 If unsure, say N.
556
557 config SCSI_SATA_SIL
558 tristate "Silicon Image SATA support"
559 depends on SCSI_SATA && PCI && EXPERIMENTAL
560 help
561 This option enables support for Silicon Image Serial ATA.
562
563 If unsure, say N.
564
565 config SCSI_SATA_SIL24
566 tristate "Silicon Image 3124/3132 SATA support"
567 depends on SCSI_SATA && PCI && EXPERIMENTAL
568 help
569 This option enables support for Silicon Image 3124/3132 Serial ATA.
570
571 If unsure, say N.
572
573 config SCSI_SATA_SIS
574 tristate "SiS 964/180 SATA support"
575 depends on SCSI_SATA && PCI && EXPERIMENTAL
576 help
577 This option enables support for SiS Serial ATA 964/180.
578
579 If unsure, say N.
580
581 config SCSI_SATA_ULI
582 tristate "ULi Electronics SATA support"
583 depends on SCSI_SATA && PCI && EXPERIMENTAL
584 help
585 This option enables support for ULi Electronics SATA.
586
587 If unsure, say N.
588
589 config SCSI_SATA_VIA
590 tristate "VIA SATA support"
591 depends on SCSI_SATA && PCI
592 help
593 This option enables support for VIA Serial ATA.
594
595 If unsure, say N.
596
597 config SCSI_SATA_VITESSE
598 tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
599 depends on SCSI_SATA && PCI
600 help
601 This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
602
603 If unsure, say N.
604
605 config SCSI_SATA_INTEL_COMBINED
606 bool
607 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
608 default y
609
610 config SCSI_BUSLOGIC
611 tristate "BusLogic SCSI support"
612 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
613 ---help---
614 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
615 Adapters. Consult the SCSI-HOWTO, available from
616 <http://www.tldp.org/docs.html#howto>, and the files
617 <file:Documentation/scsi/BusLogic.txt> and
618 <file:Documentation/scsi/FlashPoint.txt> for more information.
619
620 To compile this driver as a module, choose M here: the
621 module will be called BusLogic.
622
623 config SCSI_OMIT_FLASHPOINT
624 bool "Omit FlashPoint support"
625 depends on SCSI_BUSLOGIC
626 help
627 This option allows you to omit the FlashPoint support from the
628 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
629 substantial, so users of MultiMaster Host Adapters may wish to omit
630 it.
631
632 config SCSI_DMX3191D
633 tristate "DMX3191D SCSI support"
634 depends on PCI && SCSI
635 select SCSI_SPI_ATTRS
636 help
637 This is support for Domex DMX3191D SCSI Host Adapters.
638
639 To compile this driver as a module, choose M here: the
640 module will be called dmx3191d.
641
642 config SCSI_DTC3280
643 tristate "DTC3180/3280 SCSI support"
644 depends on ISA && SCSI
645 select SCSI_SPI_ATTRS
646 help
647 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
648 the SCSI-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>, and the file
650 <file:Documentation/scsi/dtc3x80.txt>.
651
652 To compile this driver as a module, choose M here: the
653 module will be called dtc.
654
655 config SCSI_EATA
656 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
657 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
658 ---help---
659 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
660 ISA and all EISA I/O addresses are probed looking for the "EATA"
661 signature. The addresses of all the PCI SCSI controllers reported
662 by the PCI subsystem are probed as well.
663
664 You want to read the start of <file:drivers/scsi/eata.c> and the
665 SCSI-HOWTO, available from
666 <http://www.tldp.org/docs.html#howto>.
667
668 To compile this driver as a module, choose M here: the
669 module will be called eata.
670
671 config SCSI_EATA_TAGGED_QUEUE
672 bool "enable tagged command queueing"
673 depends on SCSI_EATA
674 help
675 This is a feature of SCSI-2 which improves performance: the host
676 adapter can send several SCSI commands to a device's queue even if
677 previous commands haven't finished yet.
678 This is equivalent to the "eata=tc:y" boot option.
679
680 config SCSI_EATA_LINKED_COMMANDS
681 bool "enable elevator sorting"
682 depends on SCSI_EATA
683 help
684 This option enables elevator sorting for all probed SCSI disks and
685 CD-ROMs. It definitely reduces the average seek distance when doing
686 random seeks, but this does not necessarily result in a noticeable
687 performance improvement: your mileage may vary...
688 This is equivalent to the "eata=lc:y" boot option.
689
690 config SCSI_EATA_MAX_TAGS
691 int "maximum number of queued commands"
692 depends on SCSI_EATA
693 default "16"
694 help
695 This specifies how many SCSI commands can be maximally queued for
696 each probed SCSI device. You should reduce the default value of 16
697 only if you have disks with buggy or limited tagged command support.
698 Minimum is 2 and maximum is 62. This value is also the window size
699 used by the elevator sorting option above. The effective value used
700 by the driver for each probed SCSI device is reported at boot time.
701 This is equivalent to the "eata=mq:8" boot option.
702
703 config SCSI_EATA_PIO
704 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
705 depends on (ISA || EISA || PCI) && SCSI && BROKEN
706 ---help---
707 This driver supports all EATA-PIO protocol compliant SCSI Host
708 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
709 host adapters could also use this driver but are discouraged from
710 doing so, since this driver only supports hard disks and lacks
711 numerous features. You might want to have a look at the SCSI-HOWTO,
712 available from <http://www.tldp.org/docs.html#howto>.
713
714 To compile this driver as a module, choose M here: the
715 module will be called eata_pio.
716
717 config SCSI_FUTURE_DOMAIN
718 tristate "Future Domain 16xx SCSI/AHA-2920A support"
719 depends on (ISA || PCI) && SCSI
720 ---help---
721 This is support for Future Domain's 16-bit SCSI host adapters
722 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
723 other adapters based on the Future Domain chipsets (Quantum
724 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
725 It is explained in section 3.7 of the SCSI-HOWTO, available from
726 <http://www.tldp.org/docs.html#howto>.
727
728 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
729 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
730 controller support"). This Future Domain driver works with the older
731 Adaptec AHA-2920A boards with a Future Domain chip on them.
732
733 To compile this driver as a module, choose M here: the
734 module will be called fdomain.
735
736 config SCSI_FD_MCS
737 tristate "Future Domain MCS-600/700 SCSI support"
738 depends on MCA_LEGACY && SCSI
739 ---help---
740 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
741 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
742 is identical to the MCS 700 and hence also supported by this driver.
743 This driver also supports the Reply SB16/SCSI card (the SCSI part).
744 It supports multiple adapters in the same system.
745
746 To compile this driver as a module, choose M here: the
747 module will be called fd_mcs.
748
749 config SCSI_GDTH
750 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
751 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
752 ---help---
753 Formerly called GDT SCSI Disk Array Controller Support.
754
755 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
756 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
757 in the kernel source in <file:drivers/scsi/gdth.c> and
758 <file:drivers/scsi/gdth.h.>
759
760 To compile this driver as a module, choose M here: the
761 module will be called gdth.
762
763 config SCSI_GENERIC_NCR5380
764 tristate "Generic NCR5380/53c400 SCSI PIO support"
765 depends on ISA && SCSI
766 select SCSI_SPI_ATTRS
767 ---help---
768 This is a driver for the old NCR 53c80 series of SCSI controllers
769 on boards using PIO. Most boards such as the Trantor T130 fit this
770 category, along with a large number of ISA 8bit controllers shipped
771 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
772 you should select the specific driver for that card rather than
773 generic 5380 support.
774
775 It is explained in section 3.8 of the SCSI-HOWTO, available from
776 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
777 of the box, you may have to change some settings in
778 <file:drivers/scsi/g_NCR5380.h>.
779
780 To compile this driver as a module, choose M here: the
781 module will be called g_NCR5380.
782
783 config SCSI_GENERIC_NCR5380_MMIO
784 tristate "Generic NCR5380/53c400 SCSI MMIO support"
785 depends on ISA && SCSI
786 select SCSI_SPI_ATTRS
787 ---help---
788 This is a driver for the old NCR 53c80 series of SCSI controllers
789 on boards using memory mapped I/O.
790 It is explained in section 3.8 of the SCSI-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
792 of the box, you may have to change some settings in
793 <file:drivers/scsi/g_NCR5380.h>.
794
795 To compile this driver as a module, choose M here: the
796 module will be called g_NCR5380_mmio.
797
798 config SCSI_GENERIC_NCR53C400
799 bool "Enable NCR53c400 extensions"
800 depends on SCSI_GENERIC_NCR5380
801 help
802 This enables certain optimizations for the NCR53c400 SCSI cards.
803 You might as well try it out. Note that this driver will only probe
804 for the Trantor T130B in its default configuration; you might have
805 to pass a command line option to the kernel at boot time if it does
806 not detect your card. See the file
807 <file:Documentation/scsi/g_NCR5380.txt> for details.
808
809 config SCSI_IBMMCA
810 tristate "IBMMCA SCSI support"
811 depends on MCA_LEGACY && SCSI
812 ---help---
813 This is support for the IBM SCSI adapter found in many of the PS/2
814 series computers. These machines have an MCA bus, so you need to
815 answer Y to "MCA support" as well and read
816 <file:Documentation/mca.txt>.
817
818 If the adapter isn't found during boot (a common problem for models
819 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
820 option, where <pun> is the id of the SCSI subsystem (usually 7, but
821 if that doesn't work check your reference diskette). Owners of
822 model 95 with a LED-matrix-display can in addition activate some
823 activity info like under OS/2, but more informative, by setting
824 'ibmmcascsi=display' as an additional kernel parameter. Try "man
825 bootparam" or see the documentation of your boot loader about how to
826 pass options to the kernel.
827
828 To compile this driver as a module, choose M here: the
829 module will be called ibmmca.
830
831 config IBMMCA_SCSI_ORDER_STANDARD
832 bool "Standard SCSI-order"
833 depends on SCSI_IBMMCA
834 ---help---
835 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
836 are assigned to the drive letters, starting with the lowest SCSI-id
837 (physical number -- pun) to be drive C:, as seen from DOS and
838 similar operating systems. When looking into papers describing the
839 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
840 The SCSI-standard follows a hardware-hierarchy which says that id 7
841 has the highest priority and id 0 the lowest. Therefore, the host
842 adapters are still today everywhere placed as SCSI-id 7 by default.
843 In the SCSI-standard, the drive letters express the priority of the
844 disk. C: should be the hard disk, or a partition on it, with the
845 highest priority. This must therefore be the disk with the highest
846 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
847 original definition of the SCSI-standard as also industrial- and
848 process-control-machines, like VME-CPUs running under realtime-OSes
849 (e.g. LynxOS, OS9) do.
850
851 If you like to run Linux on your MCA-machine with the same
852 assignment of hard disks as seen from e.g. DOS or OS/2 on your
853 machine, which is in addition conformant to the SCSI-standard, you
854 must say Y here. This is also necessary for MCA-Linux users who want
855 to keep downward compatibility to older releases of the
856 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
857 June 1997).
858
859 If you like to have the lowest SCSI-id assigned as drive C:, as
860 modern SCSI-BIOSes do, which does not conform to the standard, but
861 is widespread and common in the PC-world of today, you must say N
862 here. If unsure, say Y.
863
864 config IBMMCA_SCSI_DEV_RESET
865 bool "Reset SCSI-devices at boottime"
866 depends on SCSI_IBMMCA
867 ---help---
868 By default, SCSI-devices are reset when the machine is powered on.
869 However, some devices exist, like special-control-devices,
870 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
871 not reset when switched on. If you say Y here, each device connected
872 to your SCSI-bus will be issued a reset-command after it has been
873 probed, while the kernel is booting. This may cause problems with
874 more modern devices, like hard disks, which do not appreciate these
875 reset commands, and can cause your system to hang. So say Y only if
876 you know that one of your older devices needs it; N is the safe
877 answer.
878
879 config SCSI_IPS
880 tristate "IBM ServeRAID support"
881 depends on PCI && SCSI
882 ---help---
883 This is support for the IBM ServeRAID hardware RAID controllers.
884 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
885 for more information. If this driver does not work correctly
886 without modification please contact the author by email at
887 <ipslinux@adaptec.com>.
888
889 To compile this driver as a module, choose M here: the
890 module will be called ips.
891
892 config SCSI_IBMVSCSI
893 tristate "IBM Virtual SCSI support"
894 depends on PPC_PSERIES || PPC_ISERIES
895 help
896 This is the IBM POWER Virtual SCSI Client
897
898 To compile this driver as a module, choose M here: the
899 module will be called ibmvscsic.
900
901 config SCSI_INITIO
902 tristate "Initio 9100U(W) support"
903 depends on PCI && SCSI
904 help
905 This is support for the Initio 91XXU(W) SCSI host adapter. Please
906 read the SCSI-HOWTO, available from
907 <http://www.tldp.org/docs.html#howto>.
908
909 To compile this driver as a module, choose M here: the
910 module will be called initio.
911
912 config SCSI_INIA100
913 tristate "Initio INI-A100U2W support"
914 depends on PCI && SCSI
915 help
916 This is support for the Initio INI-A100U2W SCSI host adapter.
917 Please read the SCSI-HOWTO, available from
918 <http://www.tldp.org/docs.html#howto>.
919
920 To compile this driver as a module, choose M here: the
921 module will be called a100u2w.
922
923 config SCSI_PPA
924 tristate "IOMEGA parallel port (ppa - older drives)"
925 depends on SCSI && PARPORT_PC
926 ---help---
927 This driver supports older versions of IOMEGA's parallel port ZIP
928 drive (a 100 MB removable media device).
929
930 Note that you can say N here if you have the SCSI version of the ZIP
931 drive: it will be supported automatically if you said Y to the
932 generic "SCSI disk support", above.
933
934 If you have the ZIP Plus drive or a more recent parallel port ZIP
935 drive (if the supplied cable with the drive is labeled "AutoDetect")
936 then you should say N here and Y to "IOMEGA parallel port (imm -
937 newer drives)", below.
938
939 For more information about this driver and how to use it you should
940 read the file <file:Documentation/scsi/ppa.txt>. You should also read
941 the SCSI-HOWTO, which is available from
942 <http://www.tldp.org/docs.html#howto>. If you use this driver,
943 you will still be able to use the parallel port for other tasks,
944 such as a printer; it is safe to compile both drivers into the
945 kernel.
946
947 To compile this driver as a module, choose M here: the
948 module will be called ppa.
949
950 config SCSI_IMM
951 tristate "IOMEGA parallel port (imm - newer drives)"
952 depends on SCSI && PARPORT_PC
953 ---help---
954 This driver supports newer versions of IOMEGA's parallel port ZIP
955 drive (a 100 MB removable media device).
956
957 Note that you can say N here if you have the SCSI version of the ZIP
958 drive: it will be supported automatically if you said Y to the
959 generic "SCSI disk support", above.
960
961 If you have the ZIP Plus drive or a more recent parallel port ZIP
962 drive (if the supplied cable with the drive is labeled "AutoDetect")
963 then you should say Y here; if you have an older ZIP drive, say N
964 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
965
966 For more information about this driver and how to use it you should
967 read the file <file:Documentation/scsi/ppa.txt>. You should also read
968 the SCSI-HOWTO, which is available from
969 <http://www.tldp.org/docs.html#howto>. If you use this driver,
970 you will still be able to use the parallel port for other tasks,
971 such as a printer; it is safe to compile both drivers into the
972 kernel.
973
974 To compile this driver as a module, choose M here: the
975 module will be called imm.
976
977 config SCSI_IZIP_EPP16
978 bool "ppa/imm option - Use slow (but safe) EPP-16"
979 depends on SCSI_PPA || SCSI_IMM
980 ---help---
981 EPP (Enhanced Parallel Port) is a standard for parallel ports which
982 allows them to act as expansion buses that can handle up to 64
983 peripheral devices.
984
985 Some parallel port chipsets are slower than their motherboard, and
986 so we have to control the state of the chipset's FIFO queue every
987 now and then to avoid data loss. This will be done if you say Y
988 here.
989
990 Generally, saying Y is the safe option and slows things down a bit.
991
992 config SCSI_IZIP_SLOW_CTR
993 bool "ppa/imm option - Assume slow parport control register"
994 depends on SCSI_PPA || SCSI_IMM
995 help
996 Some parallel ports are known to have excessive delays between
997 changing the parallel port control register and good data being
998 available on the parallel port data/status register. This option
999 forces a small delay (1.0 usec to be exact) after changing the
1000 control register to let things settle out. Enabling this option may
1001 result in a big drop in performance but some very old parallel ports
1002 (found in 386 vintage machines) will not work properly.
1003
1004 Generally, saying N is fine.
1005
1006 config SCSI_NCR53C406A
1007 tristate "NCR53c406a SCSI support"
1008 depends on ISA && SCSI
1009 help
1010 This is support for the NCR53c406a SCSI host adapter. For user
1011 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1012 in the kernel source. Also read the SCSI-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
1014
1015 To compile this driver as a module, choose M here: the
1016 module will be called NCR53c406.
1017
1018 config SCSI_NCR_D700
1019 tristate "NCR Dual 700 MCA SCSI support"
1020 depends on MCA && SCSI
1021 select SCSI_SPI_ATTRS
1022 help
1023 This is a driver for the MicroChannel Dual 700 card produced by
1024 NCR and commonly used in 345x/35xx/4100 class machines. It always
1025 tries to negotiate sync and uses tag command queueing.
1026
1027 Unless you have an NCR manufactured machine, the chances are that
1028 you do not have this SCSI card, so say N.
1029
1030 config SCSI_LASI700
1031 tristate "HP Lasi SCSI support for 53c700/710"
1032 depends on GSC && SCSI
1033 select SCSI_SPI_ATTRS
1034 help
1035 This is a driver for the SCSI controller in the Lasi chip found in
1036 many PA-RISC workstations & servers. If you do not know whether you
1037 have a Lasi chip, it is safe to say "Y" here.
1038
1039 config 53C700_LE_ON_BE
1040 bool
1041 depends on SCSI_LASI700
1042 default y
1043
1044 config SCSI_SYM53C8XX_2
1045 tristate "SYM53C8XX Version 2 SCSI support"
1046 depends on PCI && SCSI
1047 select SCSI_SPI_ATTRS
1048 ---help---
1049 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1050 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1051 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1052 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1053 controllers; you need to use the Fusion MPT driver for that.
1054
1055 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1056 information.
1057
1058 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1059 int "DMA addressing mode"
1060 depends on SCSI_SYM53C8XX_2
1061 default "1"
1062 ---help---
1063 This option only applies to PCI-SCSI chips that are PCI DAC
1064 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1065
1066 When set to 0, the driver will program the chip to only perform
1067 32-bit DMA. When set to 1, the chip will be able to perform DMA
1068 to addresses up to 1TB. When set to 2, the driver supports the
1069 full 64-bit DMA address range, but can only address 16 segments
1070 of 4 GB each. This limits the total addressable range to 64 GB.
1071
1072 Most machines with less than 4GB of memory should use a setting
1073 of 0 for best performance. If your machine has 4GB of memory
1074 or more, you should set this option to 1 (the default).
1075
1076 The still experimental value 2 (64 bit DMA addressing with 16
1077 x 4GB segments limitation) can be used on systems that require
1078 PCI address bits past bit 39 to be set for the addressing of
1079 memory using PCI DAC cycles.
1080
1081 config SCSI_SYM53C8XX_DEFAULT_TAGS
1082 int "Default tagged command queue depth"
1083 depends on SCSI_SYM53C8XX_2
1084 default "16"
1085 help
1086 This is the default value of the command queue depth the
1087 driver will announce to the generic SCSI layer for devices
1088 that support tagged command queueing. This value can be changed
1089 from the boot command line. This is a soft limit that cannot
1090 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1091
1092 config SCSI_SYM53C8XX_MAX_TAGS
1093 int "Maximum number of queued commands"
1094 depends on SCSI_SYM53C8XX_2
1095 default "64"
1096 help
1097 This option allows you to specify the maximum number of commands
1098 that can be queued to any device, when tagged command queuing is
1099 possible. The driver supports up to 256 queued commands per device.
1100 This value is used as a compiled-in hard limit.
1101
1102 config SCSI_SYM53C8XX_MMIO
1103 bool "Use memory mapped IO"
1104 depends on SCSI_SYM53C8XX_2
1105 default y
1106 help
1107 Memory mapped IO is faster than Port IO. Most people should
1108 answer Y here, but some machines may have problems. If you have
1109 to answer N here, please report the problem to the maintainer.
1110
1111 config SCSI_IPR
1112 tristate "IBM Power Linux RAID adapter support"
1113 depends on PCI && SCSI
1114 select FW_LOADER
1115 ---help---
1116 This driver supports the IBM Power Linux family RAID adapters.
1117 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1118 as IBM iSeries 5702, 5703, 5709, and 570A.
1119
1120 config SCSI_IPR_TRACE
1121 bool "enable driver internal trace"
1122 depends on SCSI_IPR
1123 help
1124 If you say Y here, the driver will trace all commands issued
1125 to the adapter. Performance impact is minimal. Trace can be
1126 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1127
1128 config SCSI_IPR_DUMP
1129 bool "enable adapter dump support"
1130 depends on SCSI_IPR
1131 help
1132 If you say Y here, the driver will support adapter crash dump.
1133 If you enable this support, the iprdump daemon can be used
1134 to capture adapter failure analysis information.
1135
1136 config SCSI_ZALON
1137 tristate "Zalon SCSI support"
1138 depends on GSC && SCSI
1139 select SCSI_SPI_ATTRS
1140 help
1141 The Zalon is a GSC/HSC bus interface chip that sits between the
1142 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1143 C110, J200, J210 and some D, K & R-class machines. It's also
1144 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1145 Say Y here if you have one of these machines or cards.
1146
1147 config SCSI_NCR_Q720
1148 tristate "NCR Quad 720 MCA SCSI support"
1149 depends on MCA && SCSI
1150 select SCSI_SPI_ATTRS
1151 help
1152 This is a driver for the MicroChannel Quad 720 card produced by
1153 NCR and commonly used in 345x/35xx/4100 class machines. It always
1154 tries to negotiate sync and uses tag command queueing.
1155
1156 Unless you have an NCR manufactured machine, the chances are that
1157 you do not have this SCSI card, so say N.
1158
1159 config SCSI_NCR53C8XX_DEFAULT_TAGS
1160 int " default tagged command queue depth"
1161 depends on SCSI_ZALON || SCSI_NCR_Q720
1162 default "8"
1163 ---help---
1164 "Tagged command queuing" is a feature of SCSI-2 which improves
1165 performance: the host adapter can send several SCSI commands to a
1166 device's queue even if previous commands haven't finished yet.
1167 Because the device is intelligent, it can optimize its operations
1168 (like head positioning) based on its own request queue. Some SCSI
1169 devices don't implement this properly; if you want to disable this
1170 feature, enter 0 or 1 here (it doesn't matter which).
1171
1172 The default value is 8 and should be supported by most hard disks.
1173 This value can be overridden from the boot command line using the
1174 'tags' option as follows (example):
1175 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1176 4, set queue depth to 16 for target 2 and target 3 on controller 0
1177 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1178
1179 The normal answer therefore is to go with the default 8 and to use
1180 a boot command line option for devices that need to use a different
1181 command queue depth.
1182
1183 There is no safe option other than using good SCSI devices.
1184
1185 config SCSI_NCR53C8XX_MAX_TAGS
1186 int " maximum number of queued commands"
1187 depends on SCSI_ZALON || SCSI_NCR_Q720
1188 default "32"
1189 ---help---
1190 This option allows you to specify the maximum number of commands
1191 that can be queued to any device, when tagged command queuing is
1192 possible. The default value is 32. Minimum is 2, maximum is 64.
1193 Modern hard disks are able to support 64 tags and even more, but
1194 do not seem to be faster when more than 32 tags are being used.
1195
1196 So, the normal answer here is to go with the default value 32 unless
1197 you are using very large hard disks with large cache (>= 1 MB) that
1198 are able to take advantage of more than 32 tagged commands.
1199
1200 There is no safe option and the default answer is recommended.
1201
1202 config SCSI_NCR53C8XX_SYNC
1203 int " synchronous transfers frequency in MHz"
1204 depends on SCSI_ZALON || SCSI_NCR_Q720
1205 default "20"
1206 ---help---
1207 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1208 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1209 are respectively the maximum data transfer rates in mega-transfers
1210 per second for each class. For example, a FAST-20 Wide 16 device is
1211 able to transfer data at 20 million 16 bit packets per second for a
1212 total rate of 40 MB/s.
1213
1214 You may specify 0 if you want to only use asynchronous data
1215 transfers. This is the safest and slowest option. Otherwise, specify
1216 a value between 5 and 80, depending on the capability of your SCSI
1217 controller. The higher the number, the faster the data transfer.
1218 Note that 80 should normally be ok since the driver decreases the
1219 value automatically according to the controller's capabilities.
1220
1221 Your answer to this question is ignored for controllers with NVRAM,
1222 since the driver will get this information from the user set-up. It
1223 also can be overridden using a boot setup option, as follows
1224 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1225 for FAST-20 synchronous data transfer (20 mega-transfers per
1226 second).
1227
1228 The normal answer therefore is not to go with the default but to
1229 select the maximum value 80 allowing the driver to use the maximum
1230 value supported by each controller. If this causes problems with
1231 your SCSI devices, you should come back and decrease the value.
1232
1233 There is no safe option other than using good cabling, right
1234 terminations and SCSI conformant devices.
1235
1236 config SCSI_NCR53C8XX_PROFILE
1237 bool " enable profiling"
1238 depends on SCSI_ZALON || SCSI_NCR_Q720
1239 help
1240 This option allows you to enable profiling information gathering.
1241 These statistics are not very accurate due to the low frequency
1242 of the kernel clock (100 Hz on i386) and have performance impact
1243 on systems that use very fast devices.
1244
1245 The normal answer therefore is N.
1246
1247 config SCSI_NCR53C8XX_NO_DISCONNECT
1248 bool " not allow targets to disconnect"
1249 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1250 help
1251 This option is only provided for safety if you suspect some SCSI
1252 device of yours to not support properly the target-disconnect
1253 feature. In that case, you would say Y here. In general however, to
1254 not allow targets to disconnect is not reasonable if there is more
1255 than 1 device on a SCSI bus. The normal answer therefore is N.
1256
1257 config SCSI_MCA_53C9X
1258 tristate "NCR MCA 53C9x SCSI support"
1259 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1260 help
1261 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1262 controller based on the NCR 53C94. This driver will allow use of
1263 the controller on the 3550, and very possibly others.
1264
1265 To compile this driver as a module, choose M here: the
1266 module will be called mca_53c9x.
1267
1268 config SCSI_PAS16
1269 tristate "PAS16 SCSI support"
1270 depends on ISA && SCSI
1271 select SCSI_SPI_ATTRS
1272 ---help---
1273 This is support for a SCSI host adapter. It is explained in section
1274 3.10 of the SCSI-HOWTO, available from
1275 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1276 of the box, you may have to change some settings in
1277 <file:drivers/scsi/pas16.h>.
1278
1279 To compile this driver as a module, choose M here: the
1280 module will be called pas16.
1281
1282 config SCSI_PSI240I
1283 tristate "PSI240i support"
1284 depends on ISA && SCSI
1285 help
1286 This is support for the PSI240i EIDE interface card which acts as a
1287 SCSI host adapter. Please read the SCSI-HOWTO, available from
1288 <http://www.tldp.org/docs.html#howto>.
1289
1290 To compile this driver as a module, choose M here: the
1291 module will be called psi240i.
1292
1293 config SCSI_QLOGIC_FAS
1294 tristate "Qlogic FAS SCSI support"
1295 depends on ISA && SCSI
1296 ---help---
1297 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1298 FastSCSI! cards as well as any other card based on the FASXX chip
1299 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1300
1301 This driver does NOT support the PCI versions of these cards. The
1302 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1303 SCSI support"), below.
1304
1305 Information about this driver is contained in
1306 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1307 SCSI-HOWTO, available from
1308 <http://www.tldp.org/docs.html#howto>.
1309
1310 To compile this driver as a module, choose M here: the
1311 module will be called qlogicfas.
1312
1313 config SCSI_QLOGIC_FC_FIRMWARE
1314 bool "Include loadable firmware in driver"
1315 depends on SCSI_QLOGIC_FC
1316 help
1317 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1318 expanded LUN addressing and FcTape (FCP-2) support, in the
1319 qlogicfc driver. This is required on some platforms.
1320
1321 config SCSI_QLOGIC_1280
1322 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1323 depends on PCI && SCSI
1324 help
1325 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1326
1327 To compile this driver as a module, choose M here: the
1328 module will be called qla1280.
1329
1330 config SCSI_QLOGICPTI
1331 tristate "PTI Qlogic, ISP Driver"
1332 depends on SBUS && SCSI
1333 help
1334 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1335 controllers are known under Solaris as qpti and in the openprom as
1336 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1337 driven by a different driver.
1338
1339 To compile this driver as a module, choose M here: the
1340 module will be called qlogicpti.
1341
1342 source "drivers/scsi/qla2xxx/Kconfig"
1343
1344 config SCSI_LPFC
1345 tristate "Emulex LightPulse Fibre Channel Support"
1346 depends on PCI && SCSI
1347 select SCSI_FC_ATTRS
1348 help
1349 This lpfc driver supports the Emulex LightPulse
1350 Family of Fibre Channel PCI host adapters.
1351
1352 config SCSI_SEAGATE
1353 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1354 depends on X86 && ISA && SCSI && BROKEN
1355 ---help---
1356 These are 8-bit SCSI controllers; the ST-01 is also supported by
1357 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1358 available from <http://www.tldp.org/docs.html#howto>. If it
1359 doesn't work out of the box, you may have to change some settings in
1360 <file:drivers/scsi/seagate.h>.
1361
1362 To compile this driver as a module, choose M here: the
1363 module will be called seagate.
1364
1365 # definitely looks not 64bit safe:
1366 config SCSI_SIM710
1367 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1368 depends on (EISA || MCA) && SCSI
1369 select SCSI_SPI_ATTRS
1370 ---help---
1371 This driver for NCR53c710 based SCSI host adapters.
1372
1373 It currently supports Compaq EISA cards and NCR MCA cards
1374
1375 config 53C700_IO_MAPPED
1376 bool
1377 depends on SCSI_SIM710
1378 default y
1379
1380 config SCSI_SYM53C416
1381 tristate "Symbios 53c416 SCSI support"
1382 depends on ISA && SCSI
1383 ---help---
1384 This is support for the sym53c416 SCSI host adapter, the SCSI
1385 adapter that comes with some HP scanners. This driver requires that
1386 the sym53c416 is configured first using some sort of PnP
1387 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1388 are using isapnp then you need to compile this driver as a module
1389 and then load it using insmod after isapnp has run. The parameters
1390 of the configured card(s) should be passed to the driver. The format
1391 is:
1392
1393 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1394
1395 To compile this driver as a module, choose M here: the
1396 module will be called sym53c416.
1397
1398 config SCSI_DC395x
1399 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1400 depends on PCI && SCSI && EXPERIMENTAL
1401 ---help---
1402 This driver supports PCI SCSI host adapters based on the ASIC
1403 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1404
1405 This driver works, but is still in experimental status. So better
1406 have a bootable disk and a backup in case of emergency.
1407
1408 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1409
1410 To compile this driver as a module, choose M here: the
1411 module will be called dc395x.
1412
1413 config SCSI_DC390T
1414 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1415 depends on PCI && SCSI
1416 ---help---
1417 This driver supports PCI SCSI host adapters based on the Am53C974A
1418 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1419 PCscsi/PCnet (Am53/79C974) solutions.
1420
1421 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1422
1423 Note that this driver does NOT support Tekram DC390W/U/F, which are
1424 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1425
1426 To compile this driver as a module, choose M here: the
1427 module will be called tmscsim.
1428
1429 config SCSI_T128
1430 tristate "Trantor T128/T128F/T228 SCSI support"
1431 depends on ISA && SCSI
1432 select SCSI_SPI_ATTRS
1433 ---help---
1434 This is support for a SCSI host adapter. It is explained in section
1435 3.11 of the SCSI-HOWTO, available from
1436 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1437 of the box, you may have to change some settings in
1438 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1439 Adaptec, and some former Trantor products are being sold under the
1440 Adaptec name.
1441
1442 To compile this driver as a module, choose M here: the
1443 module will be called t128.
1444
1445 config SCSI_U14_34F
1446 tristate "UltraStor 14F/34F support"
1447 depends on ISA && SCSI && ISA_DMA_API
1448 ---help---
1449 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1450 The source at <file:drivers/scsi/u14-34f.c> contains some
1451 information about this hardware. If the driver doesn't work out of
1452 the box, you may have to change some settings in
1453 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1454 <http://www.tldp.org/docs.html#howto>. Note that there is also
1455 another driver for the same hardware: "UltraStor SCSI support",
1456 below. You should say Y to both only if you want 24F support as
1457 well.
1458
1459 To compile this driver as a module, choose M here: the
1460 module will be called u14-34f.
1461
1462 config SCSI_U14_34F_TAGGED_QUEUE
1463 bool "enable tagged command queueing"
1464 depends on SCSI_U14_34F
1465 help
1466 This is a feature of SCSI-2 which improves performance: the host
1467 adapter can send several SCSI commands to a device's queue even if
1468 previous commands haven't finished yet.
1469 This is equivalent to the "u14-34f=tc:y" boot option.
1470
1471 config SCSI_U14_34F_LINKED_COMMANDS
1472 bool "enable elevator sorting"
1473 depends on SCSI_U14_34F
1474 help
1475 This option enables elevator sorting for all probed SCSI disks and
1476 CD-ROMs. It definitely reduces the average seek distance when doing
1477 random seeks, but this does not necessarily result in a noticeable
1478 performance improvement: your mileage may vary...
1479 This is equivalent to the "u14-34f=lc:y" boot option.
1480
1481 config SCSI_U14_34F_MAX_TAGS
1482 int "maximum number of queued commands"
1483 depends on SCSI_U14_34F
1484 default "8"
1485 help
1486 This specifies how many SCSI commands can be maximally queued for
1487 each probed SCSI device. You should reduce the default value of 8
1488 only if you have disks with buggy or limited tagged command support.
1489 Minimum is 2 and maximum is 14. This value is also the window size
1490 used by the elevator sorting option above. The effective value used
1491 by the driver for each probed SCSI device is reported at boot time.
1492 This is equivalent to the "u14-34f=mq:8" boot option.
1493
1494 config SCSI_ULTRASTOR
1495 tristate "UltraStor SCSI support"
1496 depends on X86 && ISA && SCSI
1497 ---help---
1498 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1499 adapter family. This driver is explained in section 3.12 of the
1500 SCSI-HOWTO, available from
1501 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1502 of the box, you may have to change some settings in
1503 <file:drivers/scsi/ultrastor.h>.
1504
1505 Note that there is also another driver for the same hardware:
1506 "UltraStor 14F/34F support", above.
1507
1508 To compile this driver as a module, choose M here: the
1509 module will be called ultrastor.
1510
1511 config SCSI_NSP32
1512 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1513 depends on PCI && SCSI && !64BIT
1514 help
1515 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1516 SCSI host adapter. Please read the SCSI-HOWTO, available from
1517 <http://www.tldp.org/docs.html#howto>.
1518
1519 To compile this driver as a module, choose M here: the
1520 module will be called nsp32.
1521
1522 config SCSI_DEBUG
1523 tristate "SCSI debugging host simulator"
1524 depends on SCSI
1525 help
1526 This is a host adapter simulator that can simulate multiple hosts
1527 each with multiple dummy SCSI devices (disks). It defaults to one
1528 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1529 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1530 dummy disks are simulated, they share the same kernel RAM for
1531 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1532 information. This driver is primarily of use to those testing the
1533 SCSI and block subsystems. If unsure, say N.
1534
1535 config SCSI_MESH
1536 tristate "MESH (Power Mac internal SCSI) support"
1537 depends on PPC32 && PPC_PMAC && SCSI
1538 help
1539 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1540 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1541 other Power Macintoshes do). Say Y to include support for this SCSI
1542 adaptor.
1543
1544 To compile this driver as a module, choose M here: the
1545 module will be called mesh.
1546
1547 config SCSI_MESH_SYNC_RATE
1548 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1549 depends on SCSI_MESH
1550 default "5"
1551 help
1552 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1553 drives a bus which is entirely internal to the machine (such as the
1554 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1555 operation at up to 10 MB/s. On machines where the SCSI bus
1556 controlled by the MESH can have external devices connected, it is
1557 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1558 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1559 to disable synchronous operation.
1560
1561 config SCSI_MESH_RESET_DELAY_MS
1562 int "initial bus reset delay (ms) (0 = no reset)"
1563 depends on SCSI_MESH
1564 default "4000"
1565
1566 config SCSI_MAC53C94
1567 tristate "53C94 (Power Mac external SCSI) support"
1568 depends on PPC32 && PPC_PMAC && SCSI
1569 help
1570 On Power Macintoshes (and clones) with two SCSI buses, the external
1571 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1572 machines which only have one SCSI bus, such as the 7200, also use
1573 the 53C94. Say Y to include support for the 53C94.
1574
1575 To compile this driver as a module, choose M here: the
1576 module will be called mac53c94.
1577
1578 source "drivers/scsi/arm/Kconfig"
1579
1580 config JAZZ_ESP
1581 bool "MIPS JAZZ FAS216 SCSI support"
1582 depends on MACH_JAZZ && SCSI
1583 help
1584 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1585 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1586 systems.
1587
1588 config A3000_SCSI
1589 tristate "A3000 WD33C93A support"
1590 depends on AMIGA && SCSI
1591 help
1592 If you have an Amiga 3000 and have SCSI devices connected to the
1593 built-in SCSI controller, say Y. Otherwise, say N.
1594
1595 To compile this driver as a module, choose M here: the
1596 module will be called wd33c93.
1597
1598 config A2091_SCSI
1599 tristate "A2091/A590 WD33C93A support"
1600 depends on ZORRO && SCSI
1601 help
1602 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1603 say N.
1604
1605 To compile this driver as a module, choose M here: the
1606 module will be called wd33c93.
1607
1608 config GVP11_SCSI
1609 tristate "GVP Series II WD33C93A support"
1610 depends on ZORRO && SCSI
1611 ---help---
1612 If you have a Great Valley Products Series II SCSI controller,
1613 answer Y. Also say Y if you have a later model of GVP SCSI
1614 controller (such as the GVP A4008 or a Combo board). Otherwise,
1615 answer N. This driver does NOT work for the T-Rex series of
1616 accelerators from TekMagic and GVP-M.
1617
1618 To compile this driver as a module, choose M here: the
1619 module will be called gvp11.
1620
1621 config CYBERSTORM_SCSI
1622 tristate "CyberStorm SCSI support"
1623 depends on ZORRO && SCSI
1624 help
1625 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1626 accelerator board and the optional Cyberstorm SCSI controller,
1627 answer Y. Otherwise, say N.
1628
1629 config CYBERSTORMII_SCSI
1630 tristate "CyberStorm Mk II SCSI support"
1631 depends on ZORRO && SCSI
1632 help
1633 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1634 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1635 answer N.
1636
1637 config BLZ2060_SCSI
1638 tristate "Blizzard 2060 SCSI support"
1639 depends on ZORRO && SCSI
1640 help
1641 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1642 and want to use the onboard SCSI controller, say Y. Otherwise,
1643 answer N.
1644
1645 config BLZ1230_SCSI
1646 tristate "Blizzard 1230IV/1260 SCSI support"
1647 depends on ZORRO && SCSI
1648 help
1649 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1650 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1651 say N.
1652
1653 config FASTLANE_SCSI
1654 tristate "Fastlane SCSI support"
1655 depends on ZORRO && SCSI
1656 help
1657 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1658 one in the near future, say Y to this question. Otherwise, say N.
1659
1660 config SCSI_AMIGA7XX
1661 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1662 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1663 help
1664 Support for various NCR53c710-based SCSI controllers on the Amiga.
1665 This includes:
1666 - the builtin SCSI controller on the Amiga 4000T,
1667 - the Amiga 4091 Zorro III SCSI-2 controller,
1668 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1669 (info at
1670 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1671 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1672 accelerator card for the Amiga 1200,
1673 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1674 Note that all of the above SCSI controllers, except for the builtin
1675 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1676 bus, so you also have to enable Zorro bus support if you want to use
1677 them.
1678
1679 config OKTAGON_SCSI
1680 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1681 depends on ZORRO && SCSI && EXPERIMENTAL
1682 help
1683 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1684 Y to this question. If you're in doubt about whether you have one,
1685 see the picture at
1686 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1687
1688 config ATARI_SCSI
1689 tristate "Atari native SCSI support"
1690 depends on ATARI && SCSI && BROKEN
1691 select SCSI_SPI_ATTRS
1692 ---help---
1693 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1694 Falcon, ...) say Y to get it supported. Of course also, if you have
1695 a compatible SCSI controller (e.g. for Medusa).
1696
1697 To compile this driver as a module, choose M here: the
1698 module will be called atari_scsi.
1699
1700 This driver supports both styles of NCR integration into the
1701 system: the TT style (separate DMA), and the Falcon style (via
1702 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1703 in the Hades (without DMA).
1704
1705 config ATARI_SCSI_TOSHIBA_DELAY
1706 bool "Long delays for Toshiba CD-ROMs"
1707 depends on ATARI_SCSI
1708 help
1709 This option increases the delay after a SCSI arbitration to
1710 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1711 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1712 would impact performance a bit, so say N.
1713
1714 config ATARI_SCSI_RESET_BOOT
1715 bool "Reset SCSI-devices at boottime"
1716 depends on ATARI_SCSI
1717 help
1718 Reset the devices on your Atari whenever it boots. This makes the
1719 boot process fractionally longer but may assist recovery from errors
1720 that leave the devices with SCSI operations partway completed.
1721
1722 config TT_DMA_EMUL
1723 bool "Hades SCSI DMA emulator"
1724 depends on ATARI_SCSI && HADES
1725 help
1726 This option enables code which emulates the TT SCSI DMA chip on the
1727 Hades. This increases the SCSI transfer rates at least ten times
1728 compared to PIO transfers.
1729
1730 config MAC_SCSI
1731 bool "Macintosh NCR5380 SCSI"
1732 depends on MAC && SCSI=y
1733 select SCSI_SPI_ATTRS
1734 help
1735 This is the NCR 5380 SCSI controller included on most of the 68030
1736 based Macintoshes. If you have one of these say Y and read the
1737 SCSI-HOWTO, available from
1738 <http://www.tldp.org/docs.html#howto>.
1739
1740 config SCSI_MAC_ESP
1741 tristate "Macintosh NCR53c9[46] SCSI"
1742 depends on MAC && SCSI
1743 help
1744 This is the NCR 53c9x SCSI controller found on most of the 68040
1745 based Macintoshes. If you have one of these say Y and read the
1746 SCSI-HOWTO, available from
1747 <http://www.tldp.org/docs.html#howto>.
1748
1749 To compile this driver as a module, choose M here: the
1750 module will be called mac_esp.
1751
1752 config MVME147_SCSI
1753 bool "WD33C93 SCSI driver for MVME147"
1754 depends on MVME147 && SCSI=y
1755 select SCSI_SPI_ATTRS
1756 help
1757 Support for the on-board SCSI controller on the Motorola MVME147
1758 single-board computer.
1759
1760 config MVME16x_SCSI
1761 bool "NCR53C710 SCSI driver for MVME16x"
1762 depends on MVME16x && SCSI && BROKEN
1763 select SCSI_SPI_ATTRS
1764 help
1765 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1766 SCSI controller chip. Almost everyone using one of these boards
1767 will want to say Y to this question.
1768
1769 config BVME6000_SCSI
1770 bool "NCR53C710 SCSI driver for BVME6000"
1771 depends on BVME6000 && SCSI && BROKEN
1772 select SCSI_SPI_ATTRS
1773 help
1774 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1775 SCSI controller chip. Almost everyone using one of these boards
1776 will want to say Y to this question.
1777
1778 config SCSI_NCR53C7xx_FAST
1779 bool "allow FAST-SCSI [10MHz]"
1780 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1781 help
1782 This will enable 10MHz FAST-SCSI transfers with your host
1783 adapter. Some systems have problems with that speed, so it's safest
1784 to say N here.
1785
1786 config SUN3_SCSI
1787 tristate "Sun3 NCR5380 SCSI"
1788 depends on SUN3 && SCSI && BROKEN
1789 select SCSI_SPI_ATTRS
1790 help
1791 This option will enable support for the OBIO (onboard io) NCR5380
1792 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1793 "Sun3" type VME scsi controllers also based on the NCR5380.
1794 General Linux information on the Sun 3 series (now discontinued)
1795 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1796
1797 config SUN3X_ESP
1798 bool "Sun3x ESP SCSI"
1799 depends on SUN3X && SCSI=y
1800 help
1801 The ESP was an on-board SCSI controller used on Sun 3/80
1802 machines. Say Y here to compile in support for it.
1803
1804 config SCSI_SUNESP
1805 tristate "Sparc ESP Scsi Driver"
1806 depends on SBUS && SCSI
1807 help
1808 This is the driver for the Sun ESP SCSI host adapter. The ESP
1809 chipset is present in most SPARC SBUS-based computers.
1810
1811 To compile this driver as a module, choose M here: the
1812 module will be called esp.
1813
1814 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1815
1816 config ZFCP
1817 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1818 depends on S390 && QDIO && SCSI
1819 select SCSI_FC_ATTRS
1820 help
1821 If you want to access SCSI devices attached to your IBM eServer
1822 zSeries by means of Fibre Channel interfaces say Y.
1823 For details please refer to the documentation provided by IBM at
1824 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1825
1826 This driver is also available as a module. This module will be
1827 called zfcp. If you want to compile it as a module, say M here
1828 and read <file:Documentation/modules.txt>.
1829
1830 endmenu
1831
1832 source "drivers/scsi/pcmcia/Kconfig"
1833
1834 endmenu