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