| blob | d61662c1a0ee950770b8dc0a6c5f54ce7d0d8d6b |
1 menu "SCSI device support"
3 config RAID_ATTRS
4 tristate "RAID Transport Class"
5 default n
6 ---help---
7 Provides RAID
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.
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.
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.
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.
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.
39 If unusure say Y.
41 comment "SCSI support type (disk, tape, CD-ROM)"
42 depends on SCSI
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
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.
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.
144 If unsure, say N.
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.
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.
164 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
165 depends on SCSI
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.
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.
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.
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
198 echo "scsi log token [level]" > /proc/scsi/scsi
200 at boot time after the /proc file system has been mounted.
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.
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.
212 menu "SCSI Transport Attributes"
213 depends on SCSI
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.
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.
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.
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.
245 endmenu
247 menu "SCSI low-level drivers"
248 depends on SCSI!=n
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).
266 To compile this driver as a module, choose M here: the
267 module will be called iscsi_tcp.
269 The userspace component needed to initialize the driver, documentation,
270 and sample configuration files can be found here:
272 http://linux-iscsi.sf.net
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.
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.
288 config SCSI_DECSII
289 tristate "DEC SII Scsi Driver"
290 depends on MACH_DECSTATION && SCSI && 32BIT
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!!!
300 <http://www.3ware.com/>
302 Please read the comments at the top of
303 <file:drivers/scsi/3w-xxxx.c>.
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.
311 <http://www.amcc.com>
313 Please read the comments at the top of
314 <file:drivers/scsi/3w-9xxx.c>.
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>.
324 To compile this driver as a module, choose M here: the
325 module will be called wd7000.
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.
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.
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>.
349 To compile this driver as a module, choose M here: the
350 module will be called aha152x.
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>.
363 To compile this driver as a module, choose M here: the
364 module will be called aha1542.
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>.
376 To compile this driver as a module, choose M here: the
377 module will be called aha1740.
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>.
387 To compile this driver as a module, choose M here: the module
388 will be called aacraid.
391 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
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.
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.
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).
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.
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.
430 To compile this driver as a module, choose M here: the
431 module will be called aic7xxx_old.
433 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
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>.
444 To compile this driver as a module, choose M here: the
445 module will be called dpt_i2o.
447 config SCSI_ADVANSYS
448 tristate "AdvanSys SCSI support"
449 depends on SCSI
450 depends on ISA || EISA || PCI
451 depends on BROKEN || X86_32
452 help
453 This is a driver for all SCSI host adapters manufactured by
454 AdvanSys. It is documented in the kernel source in
455 <file:drivers/scsi/advansys.c>.
457 To compile this driver as a module, choose M here: the
458 module will be called advansys.
460 config SCSI_IN2000
461 tristate "Always IN2000 SCSI support"
462 depends on ISA && SCSI
463 help
464 This is support for an ISA bus SCSI host adapter. You'll find more
465 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
466 out of the box, you may have to change the jumpers for IRQ or
467 address selection.
469 To compile this driver as a module, choose M here: the
470 module will be called in2000.
472 config SCSI_ARCMSR
473 tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
474 depends on PCI && SCSI
475 help
476 This driver supports all of ARECA's SATA RAID controller cards.
477 This is an ARECA-maintained driver by Erich Chen.
478 If you have any problems, please mail to: < erich@areca.com.tw >
479 Areca supports Linux RAID config tools.
481 < http://www.areca.com.tw >
483 To compile this driver as a module, choose M here: the
484 module will be called arcmsr (modprobe arcmsr).
486 source "drivers/scsi/megaraid/Kconfig.megaraid"
488 config SCSI_SATA
489 tristate "Serial ATA (SATA) support"
490 depends on SCSI
491 help
492 This driver family supports Serial ATA host controllers
493 and devices.
495 If unsure, say N.
497 config SCSI_SATA_AHCI
498 tristate "AHCI SATA support"
499 depends on SCSI_SATA && PCI
500 help
501 This option enables support for AHCI Serial ATA.
503 If unsure, say N.
505 config SCSI_SATA_SVW
506 tristate "ServerWorks Frodo / Apple K2 SATA support"
507 depends on SCSI_SATA && PCI
508 help
509 This option enables support for Broadcom/Serverworks/Apple K2
510 SATA support.
512 If unsure, say N.
514 config SCSI_ATA_PIIX
515 tristate "Intel PIIX/ICH SATA support"
516 depends on SCSI_SATA && PCI
517 help
518 This option enables support for ICH5/6/7/8 Serial ATA.
519 If PATA support was enabled previously, this enables
520 support for select Intel PIIX/ICH PATA host controllers.
522 If unsure, say N.
524 config SCSI_SATA_MV
525 tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
526 depends on SCSI_SATA && PCI && EXPERIMENTAL
527 help
528 This option enables support for the Marvell Serial ATA family.
529 Currently supports 88SX[56]0[48][01] chips.
531 If unsure, say N.
533 config SCSI_SATA_NV
534 tristate "NVIDIA SATA support"
535 depends on SCSI_SATA && PCI && EXPERIMENTAL
536 help
537 This option enables support for NVIDIA Serial ATA.
539 If unsure, say N.
541 config SCSI_PDC_ADMA
542 tristate "Pacific Digital ADMA support"
543 depends on SCSI_SATA && PCI
544 help
545 This option enables support for Pacific Digital ADMA controllers
547 If unsure, say N.
549 config SCSI_HPTIOP
550 tristate "HighPoint RocketRAID 3xxx Controller support"
551 depends on SCSI && PCI
552 help
553 This option enables support for HighPoint RocketRAID 3xxx
554 controllers.
556 To compile this driver as a module, choose M here; the module
557 will be called hptiop. If unsure, say N.
559 config SCSI_SATA_QSTOR
560 tristate "Pacific Digital SATA QStor support"
561 depends on SCSI_SATA && PCI
562 help
563 This option enables support for Pacific Digital Serial ATA QStor.
565 If unsure, say N.
567 config SCSI_SATA_PROMISE
568 tristate "Promise SATA TX2/TX4 support"
569 depends on SCSI_SATA && PCI
570 help
571 This option enables support for Promise Serial ATA TX2/TX4.
573 If unsure, say N.
575 config SCSI_SATA_SX4
576 tristate "Promise SATA SX4 support"
577 depends on SCSI_SATA && PCI && EXPERIMENTAL
578 help
579 This option enables support for Promise Serial ATA SX4.
581 If unsure, say N.
583 config SCSI_SATA_SIL
584 tristate "Silicon Image SATA support"
585 depends on SCSI_SATA && PCI && EXPERIMENTAL
586 help
587 This option enables support for Silicon Image Serial ATA.
589 If unsure, say N.
591 config SCSI_SATA_SIL24
592 tristate "Silicon Image 3124/3132 SATA support"
593 depends on SCSI_SATA && PCI && EXPERIMENTAL
594 help
595 This option enables support for Silicon Image 3124/3132 Serial ATA.
597 If unsure, say N.
599 config SCSI_SATA_SIS
600 tristate "SiS 964/180 SATA support"
601 depends on SCSI_SATA && PCI && EXPERIMENTAL
602 help
603 This option enables support for SiS Serial ATA 964/180.
605 If unsure, say N.
607 config SCSI_SATA_ULI
608 tristate "ULi Electronics SATA support"
609 depends on SCSI_SATA && PCI && EXPERIMENTAL
610 help
611 This option enables support for ULi Electronics SATA.
613 If unsure, say N.
615 config SCSI_SATA_VIA
616 tristate "VIA SATA support"
617 depends on SCSI_SATA && PCI
618 help
619 This option enables support for VIA Serial ATA.
621 If unsure, say N.
623 config SCSI_SATA_VITESSE
624 tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
625 depends on SCSI_SATA && PCI
626 help
627 This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
629 If unsure, say N.
631 config SCSI_SATA_INTEL_COMBINED
632 bool
633 depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
634 default y
636 config SCSI_BUSLOGIC
637 tristate "BusLogic SCSI support"
638 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API
639 ---help---
640 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
641 Adapters. Consult the SCSI-HOWTO, available from
642 <http://www.tldp.org/docs.html#howto>, and the files
643 <file:Documentation/scsi/BusLogic.txt> and
644 <file:Documentation/scsi/FlashPoint.txt> for more information.
646 To compile this driver as a module, choose M here: the
647 module will be called BusLogic.
649 config SCSI_OMIT_FLASHPOINT
650 bool "Omit FlashPoint support"
651 depends on SCSI_BUSLOGIC
652 help
653 This option allows you to omit the FlashPoint support from the
654 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
655 substantial, so users of MultiMaster Host Adapters may wish to omit
656 it.
658 config SCSI_DMX3191D
659 tristate "DMX3191D SCSI support"
660 depends on PCI && SCSI
661 select SCSI_SPI_ATTRS
662 help
663 This is support for Domex DMX3191D SCSI Host Adapters.
665 To compile this driver as a module, choose M here: the
666 module will be called dmx3191d.
668 config SCSI_DTC3280
669 tristate "DTC3180/3280 SCSI support"
670 depends on ISA && SCSI
671 select SCSI_SPI_ATTRS
672 help
673 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
674 the SCSI-HOWTO, available from
675 <http://www.tldp.org/docs.html#howto>, and the file
676 <file:Documentation/scsi/dtc3x80.txt>.
678 To compile this driver as a module, choose M here: the
679 module will be called dtc.
681 config SCSI_EATA
682 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
683 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
684 ---help---
685 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
686 ISA and all EISA I/O addresses are probed looking for the "EATA"
687 signature. The addresses of all the PCI SCSI controllers reported
688 by the PCI subsystem are probed as well.
690 You want to read the start of <file:drivers/scsi/eata.c> and the
691 SCSI-HOWTO, available from
692 <http://www.tldp.org/docs.html#howto>.
694 To compile this driver as a module, choose M here: the
695 module will be called eata.
697 config SCSI_EATA_TAGGED_QUEUE
698 bool "enable tagged command queueing"
699 depends on SCSI_EATA
700 help
701 This is a feature of SCSI-2 which improves performance: the host
702 adapter can send several SCSI commands to a device's queue even if
703 previous commands haven't finished yet.
704 This is equivalent to the "eata=tc:y" boot option.
706 config SCSI_EATA_LINKED_COMMANDS
707 bool "enable elevator sorting"
708 depends on SCSI_EATA
709 help
710 This option enables elevator sorting for all probed SCSI disks and
711 CD-ROMs. It definitely reduces the average seek distance when doing
712 random seeks, but this does not necessarily result in a noticeable
713 performance improvement: your mileage may vary...
714 This is equivalent to the "eata=lc:y" boot option.
716 config SCSI_EATA_MAX_TAGS
717 int "maximum number of queued commands"
718 depends on SCSI_EATA
719 default "16"
720 help
721 This specifies how many SCSI commands can be maximally queued for
722 each probed SCSI device. You should reduce the default value of 16
723 only if you have disks with buggy or limited tagged command support.
724 Minimum is 2 and maximum is 62. This value is also the window size
725 used by the elevator sorting option above. The effective value used
726 by the driver for each probed SCSI device is reported at boot time.
727 This is equivalent to the "eata=mq:8" boot option.
729 config SCSI_EATA_PIO
730 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
731 depends on (ISA || EISA || PCI) && SCSI && BROKEN
732 ---help---
733 This driver supports all EATA-PIO protocol compliant SCSI Host
734 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
735 host adapters could also use this driver but are discouraged from
736 doing so, since this driver only supports hard disks and lacks
737 numerous features. You might want to have a look at the SCSI-HOWTO,
738 available from <http://www.tldp.org/docs.html#howto>.
740 To compile this driver as a module, choose M here: the
741 module will be called eata_pio.
743 config SCSI_FUTURE_DOMAIN
744 tristate "Future Domain 16xx SCSI/AHA-2920A support"
745 depends on (ISA || PCI) && SCSI
746 ---help---
747 This is support for Future Domain's 16-bit SCSI host adapters
748 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
749 other adapters based on the Future Domain chipsets (Quantum
750 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
751 It is explained in section 3.7 of the SCSI-HOWTO, available from
752 <http://www.tldp.org/docs.html#howto>.
754 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
755 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
756 controller support"). This Future Domain driver works with the older
757 Adaptec AHA-2920A boards with a Future Domain chip on them.
759 To compile this driver as a module, choose M here: the
760 module will be called fdomain.
762 config SCSI_FD_MCS
763 tristate "Future Domain MCS-600/700 SCSI support"
764 depends on MCA_LEGACY && SCSI
765 ---help---
766 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
767 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
768 is identical to the MCS 700 and hence also supported by this driver.
769 This driver also supports the Reply SB16/SCSI card (the SCSI part).
770 It supports multiple adapters in the same system.
772 To compile this driver as a module, choose M here: the
773 module will be called fd_mcs.
775 config SCSI_GDTH
776 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
777 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
778 ---help---
779 Formerly called GDT SCSI Disk Array Controller Support.
781 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
782 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
783 in the kernel source in <file:drivers/scsi/gdth.c> and
784 <file:drivers/scsi/gdth.h.>
786 To compile this driver as a module, choose M here: the
787 module will be called gdth.
789 config SCSI_GENERIC_NCR5380
790 tristate "Generic NCR5380/53c400 SCSI PIO support"
791 depends on ISA && SCSI
792 select SCSI_SPI_ATTRS
793 ---help---
794 This is a driver for the old NCR 53c80 series of SCSI controllers
795 on boards using PIO. Most boards such as the Trantor T130 fit this
796 category, along with a large number of ISA 8bit controllers shipped
797 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
798 you should select the specific driver for that card rather than
799 generic 5380 support.
801 It is explained in section 3.8 of the SCSI-HOWTO, available from
802 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
803 of the box, you may have to change some settings in
804 <file:drivers/scsi/g_NCR5380.h>.
806 To compile this driver as a module, choose M here: the
807 module will be called g_NCR5380.
809 config SCSI_GENERIC_NCR5380_MMIO
810 tristate "Generic NCR5380/53c400 SCSI MMIO support"
811 depends on ISA && SCSI
812 select SCSI_SPI_ATTRS
813 ---help---
814 This is a driver for the old NCR 53c80 series of SCSI controllers
815 on boards using memory mapped I/O.
816 It is explained in section 3.8 of the SCSI-HOWTO, available from
817 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
818 of the box, you may have to change some settings in
819 <file:drivers/scsi/g_NCR5380.h>.
821 To compile this driver as a module, choose M here: the
822 module will be called g_NCR5380_mmio.
824 config SCSI_GENERIC_NCR53C400
825 bool "Enable NCR53c400 extensions"
826 depends on SCSI_GENERIC_NCR5380
827 help
828 This enables certain optimizations for the NCR53c400 SCSI cards.
829 You might as well try it out. Note that this driver will only probe
830 for the Trantor T130B in its default configuration; you might have
831 to pass a command line option to the kernel at boot time if it does
832 not detect your card. See the file
833 <file:Documentation/scsi/g_NCR5380.txt> for details.
835 config SCSI_IBMMCA
836 tristate "IBMMCA SCSI support"
837 depends on MCA_LEGACY && SCSI
838 ---help---
839 This is support for the IBM SCSI adapter found in many of the PS/2
840 series computers. These machines have an MCA bus, so you need to
841 answer Y to "MCA support" as well and read
842 <file:Documentation/mca.txt>.
844 If the adapter isn't found during boot (a common problem for models
845 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
846 option, where <pun> is the id of the SCSI subsystem (usually 7, but
847 if that doesn't work check your reference diskette). Owners of
848 model 95 with a LED-matrix-display can in addition activate some
849 activity info like under OS/2, but more informative, by setting
850 'ibmmcascsi=display' as an additional kernel parameter. Try "man
851 bootparam" or see the documentation of your boot loader about how to
852 pass options to the kernel.
854 To compile this driver as a module, choose M here: the
855 module will be called ibmmca.
857 config IBMMCA_SCSI_ORDER_STANDARD
858 bool "Standard SCSI-order"
859 depends on SCSI_IBMMCA
860 ---help---
861 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
862 are assigned to the drive letters, starting with the lowest SCSI-id
863 (physical number -- pun) to be drive C:, as seen from DOS and
864 similar operating systems. When looking into papers describing the
865 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
866 The SCSI-standard follows a hardware-hierarchy which says that id 7
867 has the highest priority and id 0 the lowest. Therefore, the host
868 adapters are still today everywhere placed as SCSI-id 7 by default.
869 In the SCSI-standard, the drive letters express the priority of the
870 disk. C: should be the hard disk, or a partition on it, with the
871 highest priority. This must therefore be the disk with the highest
872 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
873 original definition of the SCSI-standard as also industrial- and
874 process-control-machines, like VME-CPUs running under realtime-OSes
875 (e.g. LynxOS, OS9) do.
877 If you like to run Linux on your MCA-machine with the same
878 assignment of hard disks as seen from e.g. DOS or OS/2 on your
879 machine, which is in addition conformant to the SCSI-standard, you
880 must say Y here. This is also necessary for MCA-Linux users who want
881 to keep downward compatibility to older releases of the
882 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
883 June 1997).
885 If you like to have the lowest SCSI-id assigned as drive C:, as
886 modern SCSI-BIOSes do, which does not conform to the standard, but
887 is widespread and common in the PC-world of today, you must say N
888 here. If unsure, say Y.
890 config IBMMCA_SCSI_DEV_RESET
891 bool "Reset SCSI-devices at boottime"
892 depends on SCSI_IBMMCA
893 ---help---
894 By default, SCSI-devices are reset when the machine is powered on.
895 However, some devices exist, like special-control-devices,
896 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
897 not reset when switched on. If you say Y here, each device connected
898 to your SCSI-bus will be issued a reset-command after it has been
899 probed, while the kernel is booting. This may cause problems with
900 more modern devices, like hard disks, which do not appreciate these
901 reset commands, and can cause your system to hang. So say Y only if
902 you know that one of your older devices needs it; N is the safe
903 answer.
905 config SCSI_IPS
906 tristate "IBM ServeRAID support"
907 depends on PCI && SCSI
908 ---help---
909 This is support for the IBM ServeRAID hardware RAID controllers.
910 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
911 for more information. If this driver does not work correctly
912 without modification please contact the author by email at
913 <ipslinux@adaptec.com>.
915 To compile this driver as a module, choose M here: the
916 module will be called ips.
918 config SCSI_IBMVSCSI
919 tristate "IBM Virtual SCSI support"
920 depends on PPC_PSERIES || PPC_ISERIES
921 help
922 This is the IBM POWER Virtual SCSI Client
924 To compile this driver as a module, choose M here: the
925 module will be called ibmvscsic.
927 config SCSI_INITIO
928 tristate "Initio 9100U(W) support"
929 depends on PCI && SCSI
930 help
931 This is support for the Initio 91XXU(W) SCSI host adapter. Please
932 read the SCSI-HOWTO, available from
933 <http://www.tldp.org/docs.html#howto>.
935 To compile this driver as a module, choose M here: the
936 module will be called initio.
938 config SCSI_INIA100
939 tristate "Initio INI-A100U2W support"
940 depends on PCI && SCSI
941 help
942 This is support for the Initio INI-A100U2W SCSI host adapter.
943 Please read the SCSI-HOWTO, available from
944 <http://www.tldp.org/docs.html#howto>.
946 To compile this driver as a module, choose M here: the
947 module will be called a100u2w.
949 config SCSI_PPA
950 tristate "IOMEGA parallel port (ppa - older drives)"
951 depends on SCSI && PARPORT_PC
952 ---help---
953 This driver supports older versions of IOMEGA's parallel port ZIP
954 drive (a 100 MB removable media device).
956 Note that you can say N here if you have the SCSI version of the ZIP
957 drive: it will be supported automatically if you said Y to the
958 generic "SCSI disk support", above.
960 If you have the ZIP Plus drive or a more recent parallel port ZIP
961 drive (if the supplied cable with the drive is labeled "AutoDetect")
962 then you should say N here and Y to "IOMEGA parallel port (imm -
963 newer drives)", below.
965 For more information about this driver and how to use it you should
966 read the file <file:Documentation/scsi/ppa.txt>. You should also read
967 the SCSI-HOWTO, which is available from
968 <http://www.tldp.org/docs.html#howto>. If you use this driver,
969 you will still be able to use the parallel port for other tasks,
970 such as a printer; it is safe to compile both drivers into the
971 kernel.
973 To compile this driver as a module, choose M here: the
974 module will be called ppa.
976 config SCSI_IMM
977 tristate "IOMEGA parallel port (imm - newer drives)"
978 depends on SCSI && PARPORT_PC
979 ---help---
980 This driver supports newer versions of IOMEGA's parallel port ZIP
981 drive (a 100 MB removable media device).
983 Note that you can say N here if you have the SCSI version of the ZIP
984 drive: it will be supported automatically if you said Y to the
985 generic "SCSI disk support", above.
987 If you have the ZIP Plus drive or a more recent parallel port ZIP
988 drive (if the supplied cable with the drive is labeled "AutoDetect")
989 then you should say Y here; if you have an older ZIP drive, say N
990 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
992 For more information about this driver and how to use it you should
993 read the file <file:Documentation/scsi/ppa.txt>. You should also read
994 the SCSI-HOWTO, which is available from
995 <http://www.tldp.org/docs.html#howto>. If you use this driver,
996 you will still be able to use the parallel port for other tasks,
997 such as a printer; it is safe to compile both drivers into the
998 kernel.
1000 To compile this driver as a module, choose M here: the
1001 module will be called imm.
1003 config SCSI_IZIP_EPP16
1004 bool "ppa/imm option - Use slow (but safe) EPP-16"
1005 depends on SCSI_PPA || SCSI_IMM
1006 ---help---
1007 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1008 allows them to act as expansion buses that can handle up to 64
1009 peripheral devices.
1011 Some parallel port chipsets are slower than their motherboard, and
1012 so we have to control the state of the chipset's FIFO queue every
1013 now and then to avoid data loss. This will be done if you say Y
1014 here.
1016 Generally, saying Y is the safe option and slows things down a bit.
1018 config SCSI_IZIP_SLOW_CTR
1019 bool "ppa/imm option - Assume slow parport control register"
1020 depends on SCSI_PPA || SCSI_IMM
1021 help
1022 Some parallel ports are known to have excessive delays between
1023 changing the parallel port control register and good data being
1024 available on the parallel port data/status register. This option
1025 forces a small delay (1.0 usec to be exact) after changing the
1026 control register to let things settle out. Enabling this option may
1027 result in a big drop in performance but some very old parallel ports
1028 (found in 386 vintage machines) will not work properly.
1030 Generally, saying N is fine.
1032 config SCSI_NCR53C406A
1033 tristate "NCR53c406a SCSI support"
1034 depends on ISA && SCSI
1035 help
1036 This is support for the NCR53c406a SCSI host adapter. For user
1037 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1038 in the kernel source. Also read the SCSI-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here: the
1042 module will be called NCR53c406.
1044 config SCSI_NCR_D700
1045 tristate "NCR Dual 700 MCA SCSI support"
1046 depends on MCA && SCSI
1047 select SCSI_SPI_ATTRS
1048 help
1049 This is a driver for the MicroChannel Dual 700 card produced by
1050 NCR and commonly used in 345x/35xx/4100 class machines. It always
1051 tries to negotiate sync and uses tag command queueing.
1053 Unless you have an NCR manufactured machine, the chances are that
1054 you do not have this SCSI card, so say N.
1056 config SCSI_LASI700
1057 tristate "HP Lasi SCSI support for 53c700/710"
1058 depends on GSC && SCSI
1059 select SCSI_SPI_ATTRS
1060 help
1061 This is a driver for the SCSI controller in the Lasi chip found in
1062 many PA-RISC workstations & servers. If you do not know whether you
1063 have a Lasi chip, it is safe to say "Y" here.
1065 config 53C700_LE_ON_BE
1066 bool
1067 depends on SCSI_LASI700
1068 default y
1070 config SCSI_SYM53C8XX_2
1071 tristate "SYM53C8XX Version 2 SCSI support"
1072 depends on PCI && SCSI
1073 select SCSI_SPI_ATTRS
1074 ---help---
1075 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1076 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1077 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1078 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1079 controllers; you need to use the Fusion MPT driver for that.
1081 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1082 information.
1084 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1085 int "DMA addressing mode"
1086 depends on SCSI_SYM53C8XX_2
1087 default "1"
1088 ---help---
1089 This option only applies to PCI-SCSI chips that are PCI DAC
1090 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1092 When set to 0, the driver will program the chip to only perform
1093 32-bit DMA. When set to 1, the chip will be able to perform DMA
1094 to addresses up to 1TB. When set to 2, the driver supports the
1095 full 64-bit DMA address range, but can only address 16 segments
1096 of 4 GB each. This limits the total addressable range to 64 GB.
1098 Most machines with less than 4GB of memory should use a setting
1099 of 0 for best performance. If your machine has 4GB of memory
1100 or more, you should set this option to 1 (the default).
1102 The still experimental value 2 (64 bit DMA addressing with 16
1103 x 4GB segments limitation) can be used on systems that require
1104 PCI address bits past bit 39 to be set for the addressing of
1105 memory using PCI DAC cycles.
1107 config SCSI_SYM53C8XX_DEFAULT_TAGS
1108 int "Default tagged command queue depth"
1109 depends on SCSI_SYM53C8XX_2
1110 default "16"
1111 help
1112 This is the default value of the command queue depth the
1113 driver will announce to the generic SCSI layer for devices
1114 that support tagged command queueing. This value can be changed
1115 from the boot command line. This is a soft limit that cannot
1116 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1118 config SCSI_SYM53C8XX_MAX_TAGS
1119 int "Maximum number of queued commands"
1120 depends on SCSI_SYM53C8XX_2
1121 default "64"
1122 help
1123 This option allows you to specify the maximum number of commands
1124 that can be queued to any device, when tagged command queuing is
1125 possible. The driver supports up to 256 queued commands per device.
1126 This value is used as a compiled-in hard limit.
1128 config SCSI_SYM53C8XX_MMIO
1129 bool "Use memory mapped IO"
1130 depends on SCSI_SYM53C8XX_2
1131 default y
1132 help
1133 Memory mapped IO is faster than Port IO. Most people should
1134 answer Y here, but some machines may have problems. If you have
1135 to answer N here, please report the problem to the maintainer.
1137 config SCSI_IPR
1138 tristate "IBM Power Linux RAID adapter support"
1139 depends on PCI && SCSI
1140 select FW_LOADER
1141 ---help---
1142 This driver supports the IBM Power Linux family RAID adapters.
1143 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1144 as IBM iSeries 5702, 5703, 5709, and 570A.
1146 config SCSI_IPR_TRACE
1147 bool "enable driver internal trace"
1148 depends on SCSI_IPR
1149 help
1150 If you say Y here, the driver will trace all commands issued
1151 to the adapter. Performance impact is minimal. Trace can be
1152 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1154 config SCSI_IPR_DUMP
1155 bool "enable adapter dump support"
1156 depends on SCSI_IPR
1157 help
1158 If you say Y here, the driver will support adapter crash dump.
1159 If you enable this support, the iprdump daemon can be used
1160 to capture adapter failure analysis information.
1162 config SCSI_ZALON
1163 tristate "Zalon SCSI support"
1164 depends on GSC && SCSI
1165 select SCSI_SPI_ATTRS
1166 help
1167 The Zalon is a GSC/HSC bus interface chip that sits between the
1168 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1169 C110, J200, J210 and some D, K & R-class machines. It's also
1170 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1171 Say Y here if you have one of these machines or cards.
1173 config SCSI_NCR_Q720
1174 tristate "NCR Quad 720 MCA SCSI support"
1175 depends on MCA && SCSI
1176 select SCSI_SPI_ATTRS
1177 help
1178 This is a driver for the MicroChannel Quad 720 card produced by
1179 NCR and commonly used in 345x/35xx/4100 class machines. It always
1180 tries to negotiate sync and uses tag command queueing.
1182 Unless you have an NCR manufactured machine, the chances are that
1183 you do not have this SCSI card, so say N.
1185 config SCSI_NCR53C8XX_DEFAULT_TAGS
1186 int "default tagged command queue depth"
1187 depends on SCSI_ZALON || SCSI_NCR_Q720
1188 default "8"
1189 ---help---
1190 "Tagged command queuing" is a feature of SCSI-2 which improves
1191 performance: the host adapter can send several SCSI commands to a
1192 device's queue even if previous commands haven't finished yet.
1193 Because the device is intelligent, it can optimize its operations
1194 (like head positioning) based on its own request queue. Some SCSI
1195 devices don't implement this properly; if you want to disable this
1196 feature, enter 0 or 1 here (it doesn't matter which).
1198 The default value is 8 and should be supported by most hard disks.
1199 This value can be overridden from the boot command line using the
1200 'tags' option as follows (example):
1201 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1202 4, set queue depth to 16 for target 2 and target 3 on controller 0
1203 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1205 The normal answer therefore is to go with the default 8 and to use
1206 a boot command line option for devices that need to use a different
1207 command queue depth.
1209 There is no safe option other than using good SCSI devices.
1211 config SCSI_NCR53C8XX_MAX_TAGS
1212 int "maximum number of queued commands"
1213 depends on SCSI_ZALON || SCSI_NCR_Q720
1214 default "32"
1215 ---help---
1216 This option allows you to specify the maximum number of commands
1217 that can be queued to any device, when tagged command queuing is
1218 possible. The default value is 32. Minimum is 2, maximum is 64.
1219 Modern hard disks are able to support 64 tags and even more, but
1220 do not seem to be faster when more than 32 tags are being used.
1222 So, the normal answer here is to go with the default value 32 unless
1223 you are using very large hard disks with large cache (>= 1 MB) that
1224 are able to take advantage of more than 32 tagged commands.
1226 There is no safe option and the default answer is recommended.
1228 config SCSI_NCR53C8XX_SYNC
1229 int "synchronous transfers frequency in MHz"
1230 depends on SCSI_ZALON || SCSI_NCR_Q720
1231 default "20"
1232 ---help---
1233 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1234 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1235 are respectively the maximum data transfer rates in mega-transfers
1236 per second for each class. For example, a FAST-20 Wide 16 device is
1237 able to transfer data at 20 million 16 bit packets per second for a
1238 total rate of 40 MB/s.
1240 You may specify 0 if you want to only use asynchronous data
1241 transfers. This is the safest and slowest option. Otherwise, specify
1242 a value between 5 and 80, depending on the capability of your SCSI
1243 controller. The higher the number, the faster the data transfer.
1244 Note that 80 should normally be ok since the driver decreases the
1245 value automatically according to the controller's capabilities.
1247 Your answer to this question is ignored for controllers with NVRAM,
1248 since the driver will get this information from the user set-up. It
1249 also can be overridden using a boot setup option, as follows
1250 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1251 for FAST-20 synchronous data transfer (20 mega-transfers per
1252 second).
1254 The normal answer therefore is not to go with the default but to
1255 select the maximum value 80 allowing the driver to use the maximum
1256 value supported by each controller. If this causes problems with
1257 your SCSI devices, you should come back and decrease the value.
1259 There is no safe option other than using good cabling, right
1260 terminations and SCSI conformant devices.
1262 config SCSI_NCR53C8XX_PROFILE
1263 bool "enable profiling"
1264 depends on SCSI_ZALON || SCSI_NCR_Q720
1265 help
1266 This option allows you to enable profiling information gathering.
1267 These statistics are not very accurate due to the low frequency
1268 of the kernel clock (100 Hz on i386) and have performance impact
1269 on systems that use very fast devices.
1271 The normal answer therefore is N.
1273 config SCSI_NCR53C8XX_NO_DISCONNECT
1274 bool "not allow targets to disconnect"
1275 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1276 help
1277 This option is only provided for safety if you suspect some SCSI
1278 device of yours to not support properly the target-disconnect
1279 feature. In that case, you would say Y here. In general however, to
1280 not allow targets to disconnect is not reasonable if there is more
1281 than 1 device on a SCSI bus. The normal answer therefore is N.
1283 config SCSI_MCA_53C9X
1284 tristate "NCR MCA 53C9x SCSI support"
1285 depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
1286 help
1287 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
1288 controller based on the NCR 53C94. This driver will allow use of
1289 the controller on the 3550, and very possibly others.
1291 To compile this driver as a module, choose M here: the
1292 module will be called mca_53c9x.
1294 config SCSI_PAS16
1295 tristate "PAS16 SCSI support"
1296 depends on ISA && SCSI
1297 select SCSI_SPI_ATTRS
1298 ---help---
1299 This is support for a SCSI host adapter. It is explained in section
1300 3.10 of the SCSI-HOWTO, available from
1301 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1302 of the box, you may have to change some settings in
1303 <file:drivers/scsi/pas16.h>.
1305 To compile this driver as a module, choose M here: the
1306 module will be called pas16.
1308 config SCSI_PSI240I
1309 tristate "PSI240i support"
1310 depends on ISA && SCSI
1311 help
1312 This is support for the PSI240i EIDE interface card which acts as a
1313 SCSI host adapter. Please read the SCSI-HOWTO, available from
1314 <http://www.tldp.org/docs.html#howto>.
1316 To compile this driver as a module, choose M here: the
1317 module will be called psi240i.
1319 config SCSI_QLOGIC_FAS
1320 tristate "Qlogic FAS SCSI support"
1321 depends on ISA && SCSI
1322 ---help---
1323 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1324 FastSCSI! cards as well as any other card based on the FASXX chip
1325 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1327 This driver does NOT support the PCI versions of these cards. The
1328 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1329 SCSI support"), below.
1331 Information about this driver is contained in
1332 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1333 SCSI-HOWTO, available from
1334 <http://www.tldp.org/docs.html#howto>.
1336 To compile this driver as a module, choose M here: the
1337 module will be called qlogicfas.
1339 config SCSI_QLOGIC_FC_FIRMWARE
1340 bool "Include loadable firmware in driver"
1341 depends on SCSI_QLOGIC_FC
1342 help
1343 Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
1344 expanded LUN addressing and FcTape (FCP-2) support, in the
1345 qlogicfc driver. This is required on some platforms.
1347 config SCSI_QLOGIC_1280
1348 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1349 depends on PCI && SCSI
1350 help
1351 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1353 To compile this driver as a module, choose M here: the
1354 module will be called qla1280.
1356 config SCSI_QLOGICPTI
1357 tristate "PTI Qlogic, ISP Driver"
1358 depends on SBUS && SCSI
1359 help
1360 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1361 controllers are known under Solaris as qpti and in the openprom as
1362 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1363 driven by a different driver.
1365 To compile this driver as a module, choose M here: the
1366 module will be called qlogicpti.
1368 source "drivers/scsi/qla2xxx/Kconfig"
1370 config SCSI_LPFC
1371 tristate "Emulex LightPulse Fibre Channel Support"
1372 depends on PCI && SCSI
1373 select SCSI_FC_ATTRS
1374 help
1375 This lpfc driver supports the Emulex LightPulse
1376 Family of Fibre Channel PCI host adapters.
1378 config SCSI_SEAGATE
1379 tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1380 depends on X86 && ISA && SCSI && BROKEN
1381 ---help---
1382 These are 8-bit SCSI controllers; the ST-01 is also supported by
1383 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
1384 available from <http://www.tldp.org/docs.html#howto>. If it
1385 doesn't work out of the box, you may have to change some settings in
1386 <file:drivers/scsi/seagate.h>.
1388 To compile this driver as a module, choose M here: the
1389 module will be called seagate.
1391 # definitely looks not 64bit safe:
1392 config SCSI_SIM710
1393 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1394 depends on (EISA || MCA) && SCSI
1395 select SCSI_SPI_ATTRS
1396 ---help---
1397 This driver for NCR53c710 based SCSI host adapters.
1399 It currently supports Compaq EISA cards and NCR MCA cards
1401 config 53C700_IO_MAPPED
1402 bool
1403 depends on SCSI_SIM710
1404 default y
1406 config SCSI_SYM53C416
1407 tristate "Symbios 53c416 SCSI support"
1408 depends on ISA && SCSI
1409 ---help---
1410 This is support for the sym53c416 SCSI host adapter, the SCSI
1411 adapter that comes with some HP scanners. This driver requires that
1412 the sym53c416 is configured first using some sort of PnP
1413 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1414 are using isapnp then you need to compile this driver as a module
1415 and then load it using insmod after isapnp has run. The parameters
1416 of the configured card(s) should be passed to the driver. The format
1417 is:
1419 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1421 To compile this driver as a module, choose M here: the
1422 module will be called sym53c416.
1424 config SCSI_DC395x
1425 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1426 depends on PCI && SCSI && EXPERIMENTAL
1427 ---help---
1428 This driver supports PCI SCSI host adapters based on the ASIC
1429 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1431 This driver works, but is still in experimental status. So better
1432 have a bootable disk and a backup in case of emergency.
1434 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1436 To compile this driver as a module, choose M here: the
1437 module will be called dc395x.
1439 config SCSI_DC390T
1440 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1441 depends on PCI && SCSI
1442 ---help---
1443 This driver supports PCI SCSI host adapters based on the Am53C974A
1444 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1445 PCscsi/PCnet (Am53/79C974) solutions.
1447 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1449 Note that this driver does NOT support Tekram DC390W/U/F, which are
1450 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1452 To compile this driver as a module, choose M here: the
1453 module will be called tmscsim.
1455 config SCSI_T128
1456 tristate "Trantor T128/T128F/T228 SCSI support"
1457 depends on ISA && SCSI
1458 select SCSI_SPI_ATTRS
1459 ---help---
1460 This is support for a SCSI host adapter. It is explained in section
1461 3.11 of the SCSI-HOWTO, available from
1462 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1463 of the box, you may have to change some settings in
1464 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1465 Adaptec, and some former Trantor products are being sold under the
1466 Adaptec name.
1468 To compile this driver as a module, choose M here: the
1469 module will be called t128.
1471 config SCSI_U14_34F
1472 tristate "UltraStor 14F/34F support"
1473 depends on ISA && SCSI && ISA_DMA_API
1474 ---help---
1475 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1476 The source at <file:drivers/scsi/u14-34f.c> contains some
1477 information about this hardware. If the driver doesn't work out of
1478 the box, you may have to change some settings in
1479 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1480 <http://www.tldp.org/docs.html#howto>. Note that there is also
1481 another driver for the same hardware: "UltraStor SCSI support",
1482 below. You should say Y to both only if you want 24F support as
1483 well.
1485 To compile this driver as a module, choose M here: the
1486 module will be called u14-34f.
1488 config SCSI_U14_34F_TAGGED_QUEUE
1489 bool "enable tagged command queueing"
1490 depends on SCSI_U14_34F
1491 help
1492 This is a feature of SCSI-2 which improves performance: the host
1493 adapter can send several SCSI commands to a device's queue even if
1494 previous commands haven't finished yet.
1495 This is equivalent to the "u14-34f=tc:y" boot option.
1497 config SCSI_U14_34F_LINKED_COMMANDS
1498 bool "enable elevator sorting"
1499 depends on SCSI_U14_34F
1500 help
1501 This option enables elevator sorting for all probed SCSI disks and
1502 CD-ROMs. It definitely reduces the average seek distance when doing
1503 random seeks, but this does not necessarily result in a noticeable
1504 performance improvement: your mileage may vary...
1505 This is equivalent to the "u14-34f=lc:y" boot option.
1507 config SCSI_U14_34F_MAX_TAGS
1508 int "maximum number of queued commands"
1509 depends on SCSI_U14_34F
1510 default "8"
1511 help
1512 This specifies how many SCSI commands can be maximally queued for
1513 each probed SCSI device. You should reduce the default value of 8
1514 only if you have disks with buggy or limited tagged command support.
1515 Minimum is 2 and maximum is 14. This value is also the window size
1516 used by the elevator sorting option above. The effective value used
1517 by the driver for each probed SCSI device is reported at boot time.
1518 This is equivalent to the "u14-34f=mq:8" boot option.
1520 config SCSI_ULTRASTOR
1521 tristate "UltraStor SCSI support"
1522 depends on X86 && ISA && SCSI
1523 ---help---
1524 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1525 adapter family. This driver is explained in section 3.12 of the
1526 SCSI-HOWTO, available from
1527 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1528 of the box, you may have to change some settings in
1529 <file:drivers/scsi/ultrastor.h>.
1531 Note that there is also another driver for the same hardware:
1532 "UltraStor 14F/34F support", above.
1534 To compile this driver as a module, choose M here: the
1535 module will be called ultrastor.
1537 config SCSI_NSP32
1538 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1539 depends on PCI && SCSI && !64BIT
1540 help
1541 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1542 SCSI host adapter. Please read the SCSI-HOWTO, available from
1543 <http://www.tldp.org/docs.html#howto>.
1545 To compile this driver as a module, choose M here: the
1546 module will be called nsp32.
1548 config SCSI_DEBUG
1549 tristate "SCSI debugging host simulator"
1550 depends on SCSI
1551 help
1552 This is a host adapter simulator that can simulate multiple hosts
1553 each with multiple dummy SCSI devices (disks). It defaults to one
1554 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1555 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1556 dummy disks are simulated, they share the same kernel RAM for
1557 their storage. See <http://www.torque.net/sg/sdebug.html> for more
1558 information. This driver is primarily of use to those testing the
1559 SCSI and block subsystems. If unsure, say N.
1561 config SCSI_MESH
1562 tristate "MESH (Power Mac internal SCSI) support"
1563 depends on PPC32 && PPC_PMAC && SCSI
1564 help
1565 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1566 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1567 other Power Macintoshes do). Say Y to include support for this SCSI
1568 adaptor.
1570 To compile this driver as a module, choose M here: the
1571 module will be called mesh.
1573 config SCSI_MESH_SYNC_RATE
1574 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1575 depends on SCSI_MESH
1576 default "5"
1577 help
1578 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1579 drives a bus which is entirely internal to the machine (such as the
1580 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1581 operation at up to 10 MB/s. On machines where the SCSI bus
1582 controlled by the MESH can have external devices connected, it is
1583 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1584 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1585 to disable synchronous operation.
1587 config SCSI_MESH_RESET_DELAY_MS
1588 int "initial bus reset delay (ms) (0 = no reset)"
1589 depends on SCSI_MESH
1590 default "4000"
1592 config SCSI_MAC53C94
1593 tristate "53C94 (Power Mac external SCSI) support"
1594 depends on PPC32 && PPC_PMAC && SCSI
1595 help
1596 On Power Macintoshes (and clones) with two SCSI buses, the external
1597 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1598 machines which only have one SCSI bus, such as the 7200, also use
1599 the 53C94. Say Y to include support for the 53C94.
1601 To compile this driver as a module, choose M here: the
1602 module will be called mac53c94.
1604 source "drivers/scsi/arm/Kconfig"
1606 config JAZZ_ESP
1607 bool "MIPS JAZZ FAS216 SCSI support"
1608 depends on MACH_JAZZ && SCSI
1609 help
1610 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1611 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1612 systems.
1614 config A3000_SCSI
1615 tristate "A3000 WD33C93A support"
1616 depends on AMIGA && SCSI
1617 help
1618 If you have an Amiga 3000 and have SCSI devices connected to the
1619 built-in SCSI controller, say Y. Otherwise, say N.
1621 To compile this driver as a module, choose M here: the
1622 module will be called wd33c93.
1624 config A2091_SCSI
1625 tristate "A2091/A590 WD33C93A support"
1626 depends on ZORRO && SCSI
1627 help
1628 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1629 say N.
1631 To compile this driver as a module, choose M here: the
1632 module will be called wd33c93.
1634 config GVP11_SCSI
1635 tristate "GVP Series II WD33C93A support"
1636 depends on ZORRO && SCSI
1637 ---help---
1638 If you have a Great Valley Products Series II SCSI controller,
1639 answer Y. Also say Y if you have a later model of GVP SCSI
1640 controller (such as the GVP A4008 or a Combo board). Otherwise,
1641 answer N. This driver does NOT work for the T-Rex series of
1642 accelerators from TekMagic and GVP-M.
1644 To compile this driver as a module, choose M here: the
1645 module will be called gvp11.
1647 config CYBERSTORM_SCSI
1648 tristate "CyberStorm SCSI support"
1649 depends on ZORRO && SCSI
1650 help
1651 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
1652 accelerator board and the optional Cyberstorm SCSI controller,
1653 answer Y. Otherwise, say N.
1655 config CYBERSTORMII_SCSI
1656 tristate "CyberStorm Mk II SCSI support"
1657 depends on ZORRO && SCSI
1658 help
1659 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
1660 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
1661 answer N.
1663 config BLZ2060_SCSI
1664 tristate "Blizzard 2060 SCSI support"
1665 depends on ZORRO && SCSI
1666 help
1667 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
1668 and want to use the onboard SCSI controller, say Y. Otherwise,
1669 answer N.
1671 config BLZ1230_SCSI
1672 tristate "Blizzard 1230IV/1260 SCSI support"
1673 depends on ZORRO && SCSI
1674 help
1675 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
1676 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1677 say N.
1679 config FASTLANE_SCSI
1680 tristate "Fastlane SCSI support"
1681 depends on ZORRO && SCSI
1682 help
1683 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1684 one in the near future, say Y to this question. Otherwise, say N.
1686 config SCSI_AMIGA7XX
1687 bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
1688 depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1689 help
1690 Support for various NCR53c710-based SCSI controllers on the Amiga.
1691 This includes:
1692 - the builtin SCSI controller on the Amiga 4000T,
1693 - the Amiga 4091 Zorro III SCSI-2 controller,
1694 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1695 (info at
1696 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1697 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1698 accelerator card for the Amiga 1200,
1699 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1700 Note that all of the above SCSI controllers, except for the builtin
1701 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
1702 bus, so you also have to enable Zorro bus support if you want to use
1703 them.
1705 config OKTAGON_SCSI
1706 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1707 depends on ZORRO && SCSI && EXPERIMENTAL
1708 help
1709 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1710 Y to this question. If you're in doubt about whether you have one,
1711 see the picture at
1712 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1714 config ATARI_SCSI
1715 tristate "Atari native SCSI support"
1716 depends on ATARI && SCSI && BROKEN
1717 select SCSI_SPI_ATTRS
1718 ---help---
1719 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1720 Falcon, ...) say Y to get it supported. Of course also, if you have
1721 a compatible SCSI controller (e.g. for Medusa).
1723 To compile this driver as a module, choose M here: the
1724 module will be called atari_scsi.
1726 This driver supports both styles of NCR integration into the
1727 system: the TT style (separate DMA), and the Falcon style (via
1728 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1729 in the Hades (without DMA).
1731 config ATARI_SCSI_TOSHIBA_DELAY
1732 bool "Long delays for Toshiba CD-ROMs"
1733 depends on ATARI_SCSI
1734 help
1735 This option increases the delay after a SCSI arbitration to
1736 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1737 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1738 would impact performance a bit, so say N.
1740 config ATARI_SCSI_RESET_BOOT
1741 bool "Reset SCSI-devices at boottime"
1742 depends on ATARI_SCSI
1743 help
1744 Reset the devices on your Atari whenever it boots. This makes the
1745 boot process fractionally longer but may assist recovery from errors
1746 that leave the devices with SCSI operations partway completed.
1748 config TT_DMA_EMUL
1749 bool "Hades SCSI DMA emulator"
1750 depends on ATARI_SCSI && HADES
1751 help
1752 This option enables code which emulates the TT SCSI DMA chip on the
1753 Hades. This increases the SCSI transfer rates at least ten times
1754 compared to PIO transfers.
1756 config MAC_SCSI
1757 bool "Macintosh NCR5380 SCSI"
1758 depends on MAC && SCSI=y
1759 select SCSI_SPI_ATTRS
1760 help
1761 This is the NCR 5380 SCSI controller included on most of the 68030
1762 based Macintoshes. If you have one of these say Y and read the
1763 SCSI-HOWTO, available from
1764 <http://www.tldp.org/docs.html#howto>.
1766 config SCSI_MAC_ESP
1767 tristate "Macintosh NCR53c9[46] SCSI"
1768 depends on MAC && SCSI
1769 help
1770 This is the NCR 53c9x SCSI controller found on most of the 68040
1771 based Macintoshes. If you have one of these say Y and read the
1772 SCSI-HOWTO, available from
1773 <http://www.tldp.org/docs.html#howto>.
1775 To compile this driver as a module, choose M here: the
1776 module will be called mac_esp.
1778 config MVME147_SCSI
1779 bool "WD33C93 SCSI driver for MVME147"
1780 depends on MVME147 && SCSI=y
1781 select SCSI_SPI_ATTRS
1782 help
1783 Support for the on-board SCSI controller on the Motorola MVME147
1784 single-board computer.
1786 config MVME16x_SCSI
1787 bool "NCR53C710 SCSI driver for MVME16x"
1788 depends on MVME16x && SCSI && BROKEN
1789 select SCSI_SPI_ATTRS
1790 help
1791 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1792 SCSI controller chip. Almost everyone using one of these boards
1793 will want to say Y to this question.
1795 config BVME6000_SCSI
1796 bool "NCR53C710 SCSI driver for BVME6000"
1797 depends on BVME6000 && SCSI && BROKEN
1798 select SCSI_SPI_ATTRS
1799 help
1800 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1801 SCSI controller chip. Almost everyone using one of these boards
1802 will want to say Y to this question.
1804 config SCSI_NCR53C7xx_FAST
1805 bool "allow FAST-SCSI [10MHz]"
1806 depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1807 help
1808 This will enable 10MHz FAST-SCSI transfers with your host
1809 adapter. Some systems have problems with that speed, so it's safest
1810 to say N here.
1812 config SUN3_SCSI
1813 tristate "Sun3 NCR5380 SCSI"
1814 depends on SUN3 && SCSI && BROKEN
1815 select SCSI_SPI_ATTRS
1816 help
1817 This option will enable support for the OBIO (onboard io) NCR5380
1818 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1819 "Sun3" type VME scsi controllers also based on the NCR5380.
1820 General Linux information on the Sun 3 series (now discontinued)
1821 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1823 config SUN3X_ESP
1824 bool "Sun3x ESP SCSI"
1825 depends on SUN3X && SCSI=y
1826 help
1827 The ESP was an on-board SCSI controller used on Sun 3/80
1828 machines. Say Y here to compile in support for it.
1830 config SCSI_SUNESP
1831 tristate "Sparc ESP Scsi Driver"
1832 depends on SBUS && SCSI
1833 help
1834 This is the driver for the Sun ESP SCSI host adapter. The ESP
1835 chipset is present in most SPARC SBUS-based computers.
1837 To compile this driver as a module, choose M here: the
1838 module will be called esp.
1840 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1842 config ZFCP
1843 tristate "FCP host bus adapter driver for IBM eServer zSeries"
1844 depends on S390 && QDIO && SCSI
1845 select SCSI_FC_ATTRS
1846 help
1847 If you want to access SCSI devices attached to your IBM eServer
1848 zSeries by means of Fibre Channel interfaces say Y.
1849 For details please refer to the documentation provided by IBM at
1850 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1852 This driver is also available as a module. This module will be
1853 called zfcp. If you want to compile it as a module, say M here
1854 and read <file:Documentation/modules.txt>.
1856 endmenu
1858 source "drivers/scsi/pcmcia/Kconfig"
1860 endmenu