Version:  2.6.34 2.6.35 2.6.36 2.6.37 2.6.38 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14

Linux/drivers/scsi/Kconfig

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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us