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