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