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