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