blob: 8616496ffc026ef24cadc8e943dc6e23e4010722 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "SCSI device support"
2
James Bottomleyfac829f2010-03-03 11:06:56 +05303config SCSI_MOD
4 tristate
5 default y if SCSI=n || SCSI=y
6 default m if SCSI=m
7
James Bottomley61a7afa2005-08-16 18:27:34 -05008config RAID_ATTRS
9 tristate "RAID Transport Class"
10 default n
David Howells93614012006-09-30 20:45:40 +020011 depends on BLOCK
James Bottomleyfac829f2010-03-03 11:06:56 +053012 depends on SCSI_MOD
James Bottomley61a7afa2005-08-16 18:27:34 -050013 ---help---
14 Provides RAID
15
Linus Torvalds1da177e2005-04-16 15:20:36 -070016config SCSI
17 tristate "SCSI device support"
David Howells93614012006-09-30 20:45:40 +020018 depends on BLOCK
Cornelia Huck7689e822007-07-09 11:59:59 -070019 select SCSI_DMA if HAS_DMA
Linus Torvalds1da177e2005-04-16 15:20:36 -070020 ---help---
21 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
22 any other SCSI device under Linux, say Y and make sure that you know
23 the name of your SCSI host adapter (the card inside your computer
24 that "speaks" the SCSI protocol, also called SCSI controller),
25 because you will be asked for it.
26
27 You also need to say Y here if you have a device which speaks
28 the SCSI protocol. Examples of this include the parallel port
29 version of the IOMEGA ZIP drive, USB storage devices, Fibre
FUJITA Tomonori93c164a2009-01-02 16:12:51 +010030 Channel, and FireWire storage.
Linus Torvalds1da177e2005-04-16 15:20:36 -070031
32 To compile this driver as a module, choose M here and read
33 <file:Documentation/scsi/scsi.txt>.
34 The module will be called scsi_mod.
35
36 However, do not compile this as a module if your root file system
37 (the one containing the directory /) is located on a SCSI device.
38
Cornelia Huck7689e822007-07-09 11:59:59 -070039config SCSI_DMA
40 bool
41 default n
42
FUJITA Tomonori0d2db302006-11-16 19:24:18 +090043config SCSI_TGT
44 tristate "SCSI target support"
45 depends on SCSI && EXPERIMENTAL
46 ---help---
47 If you want to use SCSI target mode drivers enable this option.
48 If you choose M, the module will be called scsi_tgt.
49
James Smart84314fd2006-08-18 17:30:09 -040050config SCSI_NETLINK
James Bottomley2b7cbe22006-09-07 15:14:46 -050051 bool
James Smart84314fd2006-08-18 17:30:09 -040052 default n
53 select NET
54
Linus Torvalds1da177e2005-04-16 15:20:36 -070055config SCSI_PROC_FS
56 bool "legacy /proc/scsi/ support"
57 depends on SCSI && PROC_FS
58 default y
59 ---help---
60 This option enables support for the various files in
Matt LaPlante09509602006-10-03 22:31:37 +020061 /proc/scsi. In Linux 2.6 this has been superseded by
Linus Torvalds1da177e2005-04-16 15:20:36 -070062 files in sysfs but many legacy applications rely on this.
63
Matt LaPlante09509602006-10-03 22:31:37 +020064 If unsure say Y.
Linus Torvalds1da177e2005-04-16 15:20:36 -070065
66comment "SCSI support type (disk, tape, CD-ROM)"
67 depends on SCSI
68
69config BLK_DEV_SD
70 tristate "SCSI disk support"
71 depends on SCSI
Stefan Richterbfad9ce2008-08-02 19:49:40 +020072 select CRC_T10DIF if BLK_DEV_INTEGRITY
Linus Torvalds1da177e2005-04-16 15:20:36 -070073 ---help---
74 If you want to use SCSI hard disks, Fibre Channel disks,
Randy Dunlapabcdceb2007-06-11 11:59:34 -070075 Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
Linus Torvalds1da177e2005-04-16 15:20:36 -070076 USB storage or the SCSI or parallel port version of
77 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
78 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
79 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
80 CD-ROMs.
81
82 To compile this driver as a module, choose M here and read
83 <file:Documentation/scsi/scsi.txt>.
84 The module will be called sd_mod.
85
86 Do not compile this driver as a module if your root file system
87 (the one containing the directory /) is located on a SCSI disk.
88 In this case, do not compile the driver for your SCSI host adapter
89 (below) as a module either.
90
91config CHR_DEV_ST
92 tristate "SCSI tape support"
93 depends on SCSI
94 ---help---
95 If you want to use a SCSI tape drive under Linux, say Y and read the
96 SCSI-HOWTO, available from
97 <http://www.tldp.org/docs.html#howto>, and
98 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT
99 for SCSI CD-ROMs.
100
101 To compile this driver as a module, choose M here and read
102 <file:Documentation/scsi/scsi.txt>. The module will be called st.
103
104config CHR_DEV_OSST
105 tristate "SCSI OnStream SC-x0 tape support"
106 depends on SCSI
107 ---help---
Matt LaPlante84eb8d02006-10-03 22:53:09 +0200108 The OnStream SC-x0 SCSI tape drives cannot be driven by the
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 standard st driver, but instead need this special osst driver and
FUJITA Tomonori93c164a2009-01-02 16:12:51 +0100110 use the /dev/osstX char device nodes (major 206). Via usb-storage,
111 you may be able to drive the USB-x0 and DI-x0 drives as well.
112 Note that there is also a second generation of OnStream
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
114 tapes (QIC-157) and can be driven by the standard driver st.
115 For more information, you may have a look at the SCSI-HOWTO
116 <http://www.tldp.org/docs.html#howto> and
117 <file:Documentation/scsi/osst.txt> in the kernel source.
118 More info on the OnStream driver may be found on
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200119 <http://sourceforge.net/projects/osst/>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700120 Please also have a look at the standard st docu, as most of it
121 applies to osst as well.
122
123 To compile this driver as a module, choose M here and read
124 <file:Documentation/scsi/scsi.txt>. The module will be called osst.
125
126config BLK_DEV_SR
127 tristate "SCSI CDROM support"
128 depends on SCSI
129 ---help---
Alan Coxe7fb6d22009-04-01 15:00:18 +0100130 If you want to use a CD or DVD drive attached to your computer
131 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
132 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
133
134 Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
Linus Torvalds1da177e2005-04-16 15:20:36 -0700135
136 To compile this driver as a module, choose M here and read
137 <file:Documentation/scsi/scsi.txt>.
138 The module will be called sr_mod.
139
140config BLK_DEV_SR_VENDOR
141 bool "Enable vendor-specific extensions (for SCSI CDROM)"
142 depends on BLK_DEV_SR
143 help
144 This enables the usage of vendor specific SCSI commands. This is
145 required to support multisession CDs with old NEC/TOSHIBA cdrom
146 drives (and HP Writers). If you have such a drive and get the first
147 session only, try saying Y here; everybody else says N.
148
149config CHR_DEV_SG
150 tristate "SCSI generic support"
151 depends on SCSI
152 ---help---
153 If you want to use SCSI scanners, synthesizers or CD-writers or just
154 about anything having "SCSI" in its name other than hard disks,
155 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
156 directly, so you need some additional software which knows how to
157 talk to these devices using the SCSI protocol:
158
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200159 For scanners, look at SANE (<http://www.sane-project.org/>). For CD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700160 writer software look at Cdrtools
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200161 (<http://cdrecord.berlios.de/private/cdrecord.html>)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700162 and for burning a "disk at once": CDRDAO
163 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
164 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
165 For other devices, it's possible that you'll have to write the
166 driver software yourself. Please read the file
167 <file:Documentation/scsi/scsi-generic.txt> for more information.
168
169 To compile this driver as a module, choose M here and read
170 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
171
172 If unsure, say N.
173
Gerd Knorr daa6eda2005-05-10 10:59:13 +0200174config CHR_DEV_SCH
175 tristate "SCSI media changer support"
176 depends on SCSI
177 ---help---
178 This is a driver for SCSI media changers. Most common devices are
179 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
180 don't need this for those tiny 6-slot cdrom changers. Media
181 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
182 If you have such hardware and want to use it with linux, say Y
Dirk Hohndele4031492007-10-30 13:37:19 -0700183 here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
Gerd Knorr daa6eda2005-05-10 10:59:13 +0200184
185 If you want to compile this as a module ( = code which can be
186 inserted in and removed from the running kernel whenever you want),
Alexander E. Patrakov39f5fb32007-03-16 18:28:43 +0500187 say M here and read <file:Documentation/kbuild/modules.txt> and
Dirk Hohndele4031492007-10-30 13:37:19 -0700188 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
Gerd Knorr daa6eda2005-05-10 10:59:13 +0200189 If unsure, say N.
James Bottomley9927c682008-02-03 15:48:56 -0600190
191config SCSI_ENCLOSURE
192 tristate "SCSI Enclosure Support"
193 depends on SCSI && ENCLOSURE_SERVICES
194 help
195 Enclosures are devices sitting on or in SCSI backplanes that
196 manage devices. If you have a disk cage, the chances are that
197 it has an enclosure device. Selecting this option will just allow
198 certain enclosure conditions to be reported and is not required.
Gerd Knorr daa6eda2005-05-10 10:59:13 +0200199
Linus Torvalds1da177e2005-04-16 15:20:36 -0700200config SCSI_MULTI_LUN
201 bool "Probe all LUNs on each SCSI device"
202 depends on SCSI
203 help
Eric Piela3ec7232009-05-04 12:43:02 +0200204 Some devices support more than one LUN (Logical Unit Number) in order
205 to allow access to several media, e.g. CD jukebox, USB card reader,
206 mobile phone in mass storage mode. This option forces the kernel to
207 probe for all LUNs by default. This setting can be overriden by
208 max_luns boot/module parameter. Note that this option does not affect
209 devices conforming to SCSI-3 or higher as they can explicitely report
210 their number of LUNs. It is safe to say Y here unless you have one of
211 those rare devices which reacts in an unexpected way when probed for
212 multiple LUNs.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700213
214config SCSI_CONSTANTS
215 bool "Verbose SCSI error reporting (kernel size +=12K)"
216 depends on SCSI
217 help
218 The error messages regarding your SCSI hardware will be easier to
219 understand if you say Y here; it will enlarge your kernel by about
220 12 KB. If in doubt, say Y.
221
222config SCSI_LOGGING
223 bool "SCSI logging facility"
224 depends on SCSI
225 ---help---
226 This turns on a logging facility that can be used to debug a number
227 of SCSI related problems.
228
229 If you say Y here, no logging output will appear by default, but you
230 can enable logging by saying Y to "/proc file system support" and
231 "Sysctl support" below and executing the command
232
Robert Love5ef07412009-01-14 11:14:32 -0800233 echo <bitmask> > /proc/sys/dev/scsi/logging_level
Linus Torvalds1da177e2005-04-16 15:20:36 -0700234
Robert Love5ef07412009-01-14 11:14:32 -0800235 where <bitmask> is a four byte value representing the logging type
236 and logging level for each type of logging selected.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700237
Robert Love5ef07412009-01-14 11:14:32 -0800238 There are a number of logging types and you can find them in the
239 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
240 are also described in that file and they determine the verbosity of
241 the logging for each logging type.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700242
243 If you say N here, it may be harder to track down some types of SCSI
244 problems. If you say Y here your kernel will be somewhat larger, but
245 there should be no noticeable performance impact as long as you have
246 logging turned off.
247
Matthew Wilcox21db1882006-11-22 13:24:52 -0700248config SCSI_SCAN_ASYNC
249 bool "Asynchronous SCSI scanning"
250 depends on SCSI
251 help
252 The SCSI subsystem can probe for devices while the rest of the
253 system continues booting, and even probe devices on different
254 busses in parallel, leading to a significant speed-up.
Matthew Wilcox082f6f92007-02-17 19:36:33 +0100255
Matthew Wilcox21db1882006-11-22 13:24:52 -0700256 If you have built SCSI as modules, enabling this option can
257 be a problem as the devices may not have been found by the
258 time your system expects them to have been. You can load the
259 scsi_wait_scan module to ensure that all scans have completed.
260 If you build your SCSI drivers into the kernel, then everything
261 will work fine if you say Y here.
262
Matthew Wilcox082f6f92007-02-17 19:36:33 +0100263 You can override this choice by specifying "scsi_mod.scan=sync"
264 or async on the kernel's command line.
Matthew Wilcox21db1882006-11-22 13:24:52 -0700265
James Bottomley840c2832007-03-11 14:16:43 -0500266config SCSI_WAIT_SCAN
Stefan Richter5e2fb912009-06-18 21:03:23 +0200267 tristate # No prompt here, this is an invisible symbol.
James Bottomley840c2832007-03-11 14:16:43 -0500268 default m
269 depends on SCSI
270 depends on MODULES
Stefan Richter5e2fb912009-06-18 21:03:23 +0200271# scsi_wait_scan is a loadable module which waits until all the async scans are
272# complete. The idea is to use it in initrd/ initramfs scripts. You modprobe
273# it after all the modprobes of the root SCSI drivers and it will wait until
274# they have all finished scanning their buses before allowing the boot to
275# proceed. (This method is not applicable if targets boot independently in
276# parallel with the initiator, or with transports with non-deterministic target
277# discovery schemes, or if a transport driver does not support scsi_wait_scan.)
278#
279# This symbol is not exposed as a prompt because little is to be gained by
280# disabling it, whereas people who accidentally switch it off may wonder why
281# their mkinitrd gets into trouble.
James Bottomley840c2832007-03-11 14:16:43 -0500282
James Bottomley2908d772006-08-29 09:22:51 -0500283menu "SCSI Transports"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700284 depends on SCSI
285
286config SCSI_SPI_ATTRS
287 tristate "Parallel SCSI (SPI) Transport Attributes"
288 depends on SCSI
289 help
290 If you wish to export transport-specific information about
291 each attached SCSI device to sysfs, say Y. Otherwise, say N.
292
293config SCSI_FC_ATTRS
294 tristate "FiberChannel Transport Attributes"
295 depends on SCSI
James Smart84314fd2006-08-18 17:30:09 -0400296 select SCSI_NETLINK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700297 help
298 If you wish to export transport-specific information about
299 each attached FiberChannel device to sysfs, say Y.
300 Otherwise, say N.
301
FUJITA Tomonori75252362007-09-01 02:02:27 +0900302config SCSI_FC_TGT_ATTRS
303 bool "SCSI target support for FiberChannel Transport Attributes"
304 depends on SCSI_FC_ATTRS
305 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS
306 help
307 If you want to use SCSI target mode drivers enable this option.
308
Linus Torvalds1da177e2005-04-16 15:20:36 -0700309config SCSI_ISCSI_ATTRS
310 tristate "iSCSI Transport Attributes"
Alex Aizmanc899e4e2005-08-04 19:33:15 -0700311 depends on SCSI && NET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700312 help
313 If you wish to export transport-specific information about
314 each attached iSCSI device to sysfs, say Y.
315 Otherwise, say N.
316
Christoph Hellwigc7ebbbc2005-09-09 16:22:50 +0200317config SCSI_SAS_ATTRS
318 tristate "SAS Transport Attributes"
Randy Dunlap47259652010-08-18 09:28:43 -0700319 depends on SCSI
320 select BLK_DEV_BSG
Christoph Hellwigc7ebbbc2005-09-09 16:22:50 +0200321 help
322 If you wish to export transport-specific information about
323 each attached SAS device to sysfs, say Y.
324
James Bottomley2908d772006-08-29 09:22:51 -0500325source "drivers/scsi/libsas/Kconfig"
326
FUJITA Tomonori09345f62007-06-27 16:32:39 +0900327config SCSI_SRP_ATTRS
328 tristate "SRP Transport Attributes"
FUJITA Tomonori0012fdf2007-08-02 00:20:34 +0900329 depends on SCSI
FUJITA Tomonori09345f62007-06-27 16:32:39 +0900330 help
331 If you wish to export transport-specific information about
332 each attached SRP device to sysfs, say Y.
333
FUJITA Tomonori0012fdf2007-08-02 00:20:34 +0900334config SCSI_SRP_TGT_ATTRS
335 bool "SCSI target support for SRP Transport Attributes"
336 depends on SCSI_SRP_ATTRS
337 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS
338 help
339 If you want to use SCSI target mode drivers enable this option.
340
Linus Torvalds1da177e2005-04-16 15:20:36 -0700341endmenu
342
Jan Engelhardtfc6e7402007-07-09 12:00:08 -0700343menuconfig SCSI_LOWLEVEL
344 bool "SCSI low-level drivers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 depends on SCSI!=n
Jan Engelhardtfc6e7402007-07-09 12:00:08 -0700346 default y
347
James Bottomley67951f62008-03-06 15:32:06 -0600348if SCSI_LOWLEVEL && SCSI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700349
Alex Aizmanc899e4e2005-08-04 19:33:15 -0700350config ISCSI_TCP
351 tristate "iSCSI Initiator over TCP/IP"
James Bottomley96bad872005-09-08 09:56:18 -0500352 depends on SCSI && INET
Alex Aizmanc899e4e2005-08-04 19:33:15 -0700353 select CRYPTO
354 select CRYPTO_MD5
355 select CRYPTO_CRC32C
James Bottomley96bad872005-09-08 09:56:18 -0500356 select SCSI_ISCSI_ATTRS
Alex Aizmanc899e4e2005-08-04 19:33:15 -0700357 help
358 The iSCSI Driver provides a host with the ability to access storage
359 through an IP network. The driver uses the iSCSI protocol to transport
360 SCSI requests and responses over a TCP/IP network between the host
361 (the "initiator") and "targets". Architecturally, the iSCSI driver
362 combines with the host's TCP/IP stack, network drivers, and Network
363 Interface Card (NIC) to provide the same functions as a SCSI or a
364 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
365
366 To compile this driver as a module, choose M here: the
367 module will be called iscsi_tcp.
368
369 The userspace component needed to initialize the driver, documentation,
370 and sample configuration files can be found here:
371
FUJITA Tomonoribca10882007-12-13 12:43:31 -0600372 http://open-iscsi.org
Alex Aizmanc899e4e2005-08-04 19:33:15 -0700373
Mike Christieaab7a8f2010-08-02 12:46:12 -0500374config ISCSI_BOOT_SYSFS
375 tristate "iSCSI Boot Sysfs Interface"
376 default n
377 help
378 This option enables support for exposing iSCSI boot information
379 via sysfs to userspace. If you wish to export this information,
380 say Y. Otherwise, say N.
381
kxie@chelsio.com7b36b6e2010-08-16 20:55:53 -0700382source "drivers/scsi/cxgbi/Kconfig"
Michael Chancf4e6362009-06-08 18:14:44 -0700383source "drivers/scsi/bnx2i/Kconfig"
Jayamohan Kallickal6733b392009-09-05 07:36:35 +0530384source "drivers/scsi/be2iscsi/Kconfig"
Karen Xiec3673462008-12-09 14:15:32 -0800385
Linus Torvalds1da177e2005-04-16 15:20:36 -0700386config SGIWD93_SCSI
387 tristate "SGI WD93C93 SCSI Driver"
Thomas Bogendoerfer2adbfa32008-01-27 00:25:53 +0100388 depends on SGI_HAS_WD93 && SCSI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389 help
390 If you have a Western Digital WD93 SCSI controller on
391 an SGI MIPS system, say Y. Otherwise, say N.
392
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393config BLK_DEV_3W_XXXX_RAID
394 tristate "3ware 5/6/7/8xxx ATA-RAID support"
395 depends on PCI && SCSI
396 help
397 3ware is the only hardware ATA-Raid product in Linux to date.
398 This card is 2,4, or 8 channel master mode support only.
399 SCSI support required!!!
400
401 <http://www.3ware.com/>
402
403 Please read the comments at the top of
404 <file:drivers/scsi/3w-xxxx.c>.
405
Stephen M. Cameronedd16362009-12-08 14:09:11 -0800406config SCSI_HPSA
407 tristate "HP Smart Array SCSI driver"
408 depends on PCI && SCSI
409 help
410 This driver supports HP Smart Array Controllers (circa 2009).
411 It is a SCSI alternative to the cciss driver, which is a block
412 driver. Anyone wishing to use HP Smart Array controllers who
413 would prefer the devices be presented to linux as SCSI devices,
414 rather than as generic block devices should say Y here.
415
Linus Torvalds1da177e2005-04-16 15:20:36 -0700416config SCSI_3W_9XXX
417 tristate "3ware 9xxx SATA-RAID support"
418 depends on PCI && SCSI
419 help
420 This driver supports the 9000 series 3ware SATA-RAID cards.
421
422 <http://www.amcc.com>
423
424 Please read the comments at the top of
425 <file:drivers/scsi/3w-9xxx.c>.
426
adam radfordf6191062009-10-23 14:52:33 -0700427config SCSI_3W_SAS
428 tristate "3ware 97xx SAS/SATA-RAID support"
429 depends on PCI && SCSI
430 help
431 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
432
433 <http://www.lsi.com>
434
435 Please read the comments at the top of
436 <file:drivers/scsi/3w-sas.c>.
437
Linus Torvalds1da177e2005-04-16 15:20:36 -0700438config SCSI_7000FASST
439 tristate "7000FASST SCSI support"
Al Viroa5532602005-05-04 05:39:42 +0100440 depends on ISA && SCSI && ISA_DMA_API
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700441 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700442 help
443 This driver supports the Western Digital 7000 SCSI host adapter
444 family. Some information is in the source:
445 <file:drivers/scsi/wd7000.c>.
446
447 To compile this driver as a module, choose M here: the
448 module will be called wd7000.
449
450config SCSI_ACARD
451 tristate "ACARD SCSI support"
452 depends on PCI && SCSI
453 help
454 This driver supports the ACARD SCSI host adapter.
455 Support Chip <ATP870 ATP876 ATP880 ATP885>
456 To compile this driver as a module, choose M here: the
457 module will be called atp870u.
458
459config SCSI_AHA152X
460 tristate "Adaptec AHA152X/2825 support"
461 depends on ISA && SCSI && !64BIT
Matthew Wilcox410ca5c2005-12-15 16:22:01 -0500462 select SCSI_SPI_ATTRS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700463 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700464 ---help---
465 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
466 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
467 must be manually specified in this case.
468
469 It is explained in section 3.3 of the SCSI-HOWTO, available from
470 <http://www.tldp.org/docs.html#howto>. You might also want to
471 read the file <file:Documentation/scsi/aha152x.txt>.
472
473 To compile this driver as a module, choose M here: the
474 module will be called aha152x.
475
476config SCSI_AHA1542
477 tristate "Adaptec AHA1542 support"
Al Viroa5532602005-05-04 05:39:42 +0100478 depends on ISA && SCSI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700479 ---help---
480 This is support for a SCSI host adapter. It is explained in section
481 3.4 of the SCSI-HOWTO, available from
482 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
483 purchased by Adaptec, and some former Trantor products are being
484 sold under the Adaptec name. If it doesn't work out of the box, you
485 may have to change some settings in <file:drivers/scsi/aha1542.h>.
486
487 To compile this driver as a module, choose M here: the
488 module will be called aha1542.
489
490config SCSI_AHA1740
491 tristate "Adaptec AHA1740 support"
492 depends on EISA && SCSI
493 ---help---
494 This is support for a SCSI host adapter. It is explained in section
495 3.5 of the SCSI-HOWTO, available from
496 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
497 of the box, you may have to change some settings in
498 <file:drivers/scsi/aha1740.h>.
499
500 To compile this driver as a module, choose M here: the
501 module will be called aha1740.
502
503config SCSI_AACRAID
504 tristate "Adaptec AACRAID support"
505 depends on SCSI && PCI
Adrian Bunk8075f212006-03-20 20:21:24 +0100506 help
507 This driver supports a variety of Dell, HP, Adaptec, IBM and
508 ICP storage products. For a list of supported products, refer
509 to <file:Documentation/scsi/aacraid.txt>.
510
511 To compile this driver as a module, choose M here: the module
512 will be called aacraid.
513
Linus Torvalds1da177e2005-04-16 15:20:36 -0700514
515source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
516
517config SCSI_AIC7XXX_OLD
518 tristate "Adaptec AIC7xxx support (old driver)"
519 depends on (ISA || EISA || PCI ) && SCSI
520 help
521 WARNING This driver is an older aic7xxx driver and is no longer
522 under active development. Adaptec, Inc. is writing a new driver to
523 take the place of this one, and it is recommended that whenever
524 possible, people should use the new Adaptec written driver instead
525 of this one. This driver will eventually be phased out entirely.
526
527 This is support for the various aic7xxx based Adaptec SCSI
528 controllers. These include the 274x EISA cards; 284x VLB cards;
529 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
530 motherboard based SCSI controllers from Adaptec. It does not support
531 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
532 support them. It does not support the 2920 cards from Adaptec that
533 use the Future Domain SCSI controller chip. For those cards, you
534 need the "Future Domain 16xx SCSI support" driver.
535
536 In general, if the controller is based on an Adaptec SCSI controller
537 chip from the aic777x series or the aic78xx series, this driver
538 should work. The only exception is the 7810 which is specifically
539 not supported (that's the RAID controller chip on the AAA-13x
540 cards).
541
542 Note that the AHA2920 SCSI host adapter is *not* supported by this
543 driver; choose "Future Domain 16xx SCSI support" instead if you have
544 one of those.
545
546 Information on the configuration options for this controller can be
547 found by checking the help file for each of the available
548 configuration options. You should read
549 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
550 contacting the maintainer with any questions. The SCSI-HOWTO,
551 available from <http://www.tldp.org/docs.html#howto>, can also
552 be of great help.
553
554 To compile this driver as a module, choose M here: the
555 module will be called aic7xxx_old.
556
557source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
James Bottomley2908d772006-08-29 09:22:51 -0500558source "drivers/scsi/aic94xx/Kconfig"
Jeff Garzik2ad52f42009-05-08 16:35:37 -0400559source "drivers/scsi/mvsas/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700560
Linus Torvalds1da177e2005-04-16 15:20:36 -0700561config SCSI_DPT_I2O
562 tristate "Adaptec I2O RAID support "
Miquel van Smoorenburg62ac5ae2008-05-02 01:07:27 +0200563 depends on SCSI && PCI && VIRT_TO_BUS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700564 help
565 This driver supports all of Adaptec's I2O based RAID controllers as
566 well as the DPT SmartRaid V cards. This is an Adaptec maintained
567 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
568
569 To compile this driver as a module, choose M here: the
570 module will be called dpt_i2o.
571
572config SCSI_ADVANSYS
573 tristate "AdvanSys SCSI support"
Andrew Morton50899562007-10-18 23:39:10 -0700574 depends on SCSI && VIRT_TO_BUS
Linus Torvalds4661e3e2006-04-29 14:27:13 -0700575 depends on ISA || EISA || PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700576 help
577 This is a driver for all SCSI host adapters manufactured by
578 AdvanSys. It is documented in the kernel source in
579 <file:drivers/scsi/advansys.c>.
580
581 To compile this driver as a module, choose M here: the
582 module will be called advansys.
583
584config SCSI_IN2000
585 tristate "Always IN2000 SCSI support"
586 depends on ISA && SCSI
587 help
588 This is support for an ISA bus SCSI host adapter. You'll find more
589 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
590 out of the box, you may have to change the jumpers for IRQ or
591 address selection.
592
593 To compile this driver as a module, choose M here: the
594 module will be called in2000.
595
Erich Chen1c57e862006-07-12 08:59:32 -0700596config SCSI_ARCMSR
Nick Cheng1a4f5502007-09-13 17:26:40 +0800597 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
Erich Chen1c57e862006-07-12 08:59:32 -0700598 depends on PCI && SCSI
599 help
Nick Cheng1a4f5502007-09-13 17:26:40 +0800600 This driver supports all of ARECA's SATA/SAS RAID controller cards.
Erich Chen1c57e862006-07-12 08:59:32 -0700601 This is an ARECA-maintained driver by Erich Chen.
Nick Cheng1a4f5502007-09-13 17:26:40 +0800602 If you have any problems, please mail to: <erich@areca.com.tw>.
Erich Chen1c57e862006-07-12 08:59:32 -0700603 Areca supports Linux RAID config tools.
Nick Cheng1a4f5502007-09-13 17:26:40 +0800604 Please link <http://www.areca.com.tw>
Erich Chen1c57e862006-07-12 08:59:32 -0700605
606 To compile this driver as a module, choose M here: the
607 module will be called arcmsr (modprobe arcmsr).
608
Nick Cheng1a4f5502007-09-13 17:26:40 +0800609config SCSI_ARCMSR_AER
610 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)"
611 depends on SCSI_ARCMSR && PCIEAER
612 default n
613 help
614 The advanced error reporting(AER) capability is "NOT" provided by
615 ARC1200/1201/1202 SATA RAID controllers cards.
616 If your card is one of ARC1200/1201/1202, please use the default setting, n.
617 If your card is other models, you could pick it
618 on condition that the kernel version is greater than 2.6.19.
619 This function is maintained driver by Nick Cheng. If you have any
620 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>.
621 To enable this function, choose Y here.
622
Linus Torvalds1da177e2005-04-16 15:20:36 -0700623source "drivers/scsi/megaraid/Kconfig.megaraid"
Eric Moore635374e2009-03-09 01:21:12 -0600624source "drivers/scsi/mpt2sas/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700625
HighPoint Linux Teamede1e6f2006-05-16 14:38:09 +0800626config SCSI_HPTIOP
HighPoint Linux Team00f59702007-12-13 16:14:26 -0800627 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
HighPoint Linux Teamede1e6f2006-05-16 14:38:09 +0800628 depends on SCSI && PCI
629 help
HighPoint Linux Team00f59702007-12-13 16:14:26 -0800630 This option enables support for HighPoint RocketRAID 3xxx/4xxx
HighPoint Linux Teamede1e6f2006-05-16 14:38:09 +0800631 controllers.
632
633 To compile this driver as a module, choose M here; the module
634 will be called hptiop. If unsure, say N.
635
Linus Torvalds1da177e2005-04-16 15:20:36 -0700636config SCSI_BUSLOGIC
637 tristate "BusLogic SCSI support"
Stephen Rothwellf057eac2007-07-15 23:40:05 -0700638 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700639 ---help---
640 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
641 Adapters. Consult the SCSI-HOWTO, available from
642 <http://www.tldp.org/docs.html#howto>, and the files
643 <file:Documentation/scsi/BusLogic.txt> and
644 <file:Documentation/scsi/FlashPoint.txt> for more information.
Matthew Wilcox78b4b052008-03-13 06:55:08 -0600645 Note that support for FlashPoint is only available for 32-bit
646 x86 configurations.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700647
648 To compile this driver as a module, choose M here: the
649 module will be called BusLogic.
650
Matthew Wilcox78b4b052008-03-13 06:55:08 -0600651config SCSI_FLASHPOINT
652 bool "FlashPoint support"
653 depends on SCSI_BUSLOGIC && PCI && X86_32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700654 help
Matthew Wilcox78b4b052008-03-13 06:55:08 -0600655 This option allows you to add FlashPoint support to the
Linus Torvalds1da177e2005-04-16 15:20:36 -0700656 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
Matthew Wilcox78b4b052008-03-13 06:55:08 -0600657 substantial, so users of MultiMaster Host Adapters may not
658 wish to include it.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700659
Alok Kataria851b1642009-10-13 14:51:05 -0700660config VMWARE_PVSCSI
661 tristate "VMware PVSCSI driver support"
662 depends on PCI && SCSI && X86
663 help
664 This driver supports VMware's para virtualized SCSI HBA.
665 To compile this driver as a module, choose M here: the
666 module will be called vmw_pvscsi.
667
Robert Love42e9a922008-12-09 15:10:17 -0800668config LIBFC
669 tristate "LibFC module"
James Bottomleyfb5edd02008-12-30 09:44:29 -0600670 select SCSI_FC_ATTRS
Randy Dunlapd943aee2009-01-12 10:50:58 -0800671 select CRC32
Robert Love42e9a922008-12-09 15:10:17 -0800672 ---help---
673 Fibre Channel library module
674
Vasu Dev9b34ecf2009-03-17 11:42:13 -0700675config LIBFCOE
676 tristate "LibFCoE module"
677 select LIBFC
678 ---help---
679 Library for Fibre Channel over Ethernet module
680
Robert Love85b4aa42008-12-09 15:10:24 -0800681config FCOE
682 tristate "FCoE module"
James Bottomleyfb5edd02008-12-30 09:44:29 -0600683 depends on PCI
Vasu Dev9b34ecf2009-03-17 11:42:13 -0700684 select LIBFCOE
Robert Love85b4aa42008-12-09 15:10:24 -0800685 ---help---
686 Fibre Channel over Ethernet module
687
Abhijeet Joglekar5df6d732009-04-17 18:33:26 -0700688config FCOE_FNIC
689 tristate "Cisco FNIC Driver"
690 depends on PCI && X86
Joe Eykholt78112e52009-11-03 11:49:22 -0800691 select LIBFCOE
Abhijeet Joglekar5df6d732009-04-17 18:33:26 -0700692 help
693 This is support for the Cisco PCI-Express FCoE HBA.
694
695 To compile this driver as a module, choose M here and read
696 <file:Documentation/scsi/scsi.txt>.
697 The module will be called fnic.
698
Linus Torvalds1da177e2005-04-16 15:20:36 -0700699config SCSI_DMX3191D
700 tristate "DMX3191D SCSI support"
701 depends on PCI && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -0500702 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700703 help
704 This is support for Domex DMX3191D SCSI Host Adapters.
705
706 To compile this driver as a module, choose M here: the
707 module will be called dmx3191d.
708
709config SCSI_DTC3280
710 tristate "DTC3180/3280 SCSI support"
711 depends on ISA && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -0500712 select SCSI_SPI_ATTRS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700713 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700714 help
715 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
716 the SCSI-HOWTO, available from
717 <http://www.tldp.org/docs.html#howto>, and the file
718 <file:Documentation/scsi/dtc3x80.txt>.
719
720 To compile this driver as a module, choose M here: the
721 module will be called dtc.
722
723config SCSI_EATA
724 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
Al Viroa5532602005-05-04 05:39:42 +0100725 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700726 ---help---
727 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
728 ISA and all EISA I/O addresses are probed looking for the "EATA"
729 signature. The addresses of all the PCI SCSI controllers reported
730 by the PCI subsystem are probed as well.
731
732 You want to read the start of <file:drivers/scsi/eata.c> and the
733 SCSI-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
735
736 To compile this driver as a module, choose M here: the
737 module will be called eata.
738
739config SCSI_EATA_TAGGED_QUEUE
740 bool "enable tagged command queueing"
741 depends on SCSI_EATA
742 help
743 This is a feature of SCSI-2 which improves performance: the host
744 adapter can send several SCSI commands to a device's queue even if
745 previous commands haven't finished yet.
746 This is equivalent to the "eata=tc:y" boot option.
747
748config SCSI_EATA_LINKED_COMMANDS
749 bool "enable elevator sorting"
750 depends on SCSI_EATA
751 help
752 This option enables elevator sorting for all probed SCSI disks and
753 CD-ROMs. It definitely reduces the average seek distance when doing
754 random seeks, but this does not necessarily result in a noticeable
755 performance improvement: your mileage may vary...
756 This is equivalent to the "eata=lc:y" boot option.
757
758config SCSI_EATA_MAX_TAGS
759 int "maximum number of queued commands"
760 depends on SCSI_EATA
761 default "16"
762 help
763 This specifies how many SCSI commands can be maximally queued for
764 each probed SCSI device. You should reduce the default value of 16
765 only if you have disks with buggy or limited tagged command support.
766 Minimum is 2 and maximum is 62. This value is also the window size
767 used by the elevator sorting option above. The effective value used
768 by the driver for each probed SCSI device is reported at boot time.
769 This is equivalent to the "eata=mq:8" boot option.
770
771config SCSI_EATA_PIO
772 tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
773 depends on (ISA || EISA || PCI) && SCSI && BROKEN
774 ---help---
775 This driver supports all EATA-PIO protocol compliant SCSI Host
776 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
777 host adapters could also use this driver but are discouraged from
778 doing so, since this driver only supports hard disks and lacks
779 numerous features. You might want to have a look at the SCSI-HOWTO,
780 available from <http://www.tldp.org/docs.html#howto>.
781
782 To compile this driver as a module, choose M here: the
783 module will be called eata_pio.
784
785config SCSI_FUTURE_DOMAIN
786 tristate "Future Domain 16xx SCSI/AHA-2920A support"
787 depends on (ISA || PCI) && SCSI
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700788 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700789 ---help---
790 This is support for Future Domain's 16-bit SCSI host adapters
791 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
792 other adapters based on the Future Domain chipsets (Quantum
793 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
794 It is explained in section 3.7 of the SCSI-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
796
797 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
798 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
799 controller support"). This Future Domain driver works with the older
800 Adaptec AHA-2920A boards with a Future Domain chip on them.
801
802 To compile this driver as a module, choose M here: the
803 module will be called fdomain.
804
805config SCSI_FD_MCS
806 tristate "Future Domain MCS-600/700 SCSI support"
807 depends on MCA_LEGACY && SCSI
808 ---help---
809 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
810 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
811 is identical to the MCS 700 and hence also supported by this driver.
812 This driver also supports the Reply SB16/SCSI card (the SCSI part).
813 It supports multiple adapters in the same system.
814
815 To compile this driver as a module, choose M here: the
816 module will be called fd_mcs.
817
818config SCSI_GDTH
819 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
Sergio Luis99109302008-02-12 20:48:03 -0300820 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700821 ---help---
822 Formerly called GDT SCSI Disk Array Controller Support.
823
824 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
825 manufactured by Intel Corporation/ICP vortex GmbH. It is documented
826 in the kernel source in <file:drivers/scsi/gdth.c> and
Johann Felix Soden889c94a2008-01-20 14:41:18 +0100827 <file:drivers/scsi/gdth.h>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700828
829 To compile this driver as a module, choose M here: the
830 module will be called gdth.
831
832config SCSI_GENERIC_NCR5380
833 tristate "Generic NCR5380/53c400 SCSI PIO support"
834 depends on ISA && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -0500835 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700836 ---help---
837 This is a driver for the old NCR 53c80 series of SCSI controllers
838 on boards using PIO. Most boards such as the Trantor T130 fit this
839 category, along with a large number of ISA 8bit controllers shipped
840 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
841 you should select the specific driver for that card rather than
842 generic 5380 support.
843
844 It is explained in section 3.8 of the SCSI-HOWTO, available from
845 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
846 of the box, you may have to change some settings in
847 <file:drivers/scsi/g_NCR5380.h>.
848
849 To compile this driver as a module, choose M here: the
850 module will be called g_NCR5380.
851
852config SCSI_GENERIC_NCR5380_MMIO
853 tristate "Generic NCR5380/53c400 SCSI MMIO support"
854 depends on ISA && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -0500855 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700856 ---help---
857 This is a driver for the old NCR 53c80 series of SCSI controllers
858 on boards using memory mapped I/O.
859 It is explained in section 3.8 of the SCSI-HOWTO, available from
860 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
861 of the box, you may have to change some settings in
862 <file:drivers/scsi/g_NCR5380.h>.
863
864 To compile this driver as a module, choose M here: the
865 module will be called g_NCR5380_mmio.
866
867config SCSI_GENERIC_NCR53C400
868 bool "Enable NCR53c400 extensions"
869 depends on SCSI_GENERIC_NCR5380
870 help
871 This enables certain optimizations for the NCR53c400 SCSI cards.
872 You might as well try it out. Note that this driver will only probe
873 for the Trantor T130B in its default configuration; you might have
874 to pass a command line option to the kernel at boot time if it does
875 not detect your card. See the file
876 <file:Documentation/scsi/g_NCR5380.txt> for details.
877
878config SCSI_IBMMCA
879 tristate "IBMMCA SCSI support"
James Bottomley67b20092007-05-03 11:13:08 -0500880 depends on MCA && SCSI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700881 ---help---
882 This is support for the IBM SCSI adapter found in many of the PS/2
883 series computers. These machines have an MCA bus, so you need to
884 answer Y to "MCA support" as well and read
885 <file:Documentation/mca.txt>.
886
887 If the adapter isn't found during boot (a common problem for models
888 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
889 option, where <pun> is the id of the SCSI subsystem (usually 7, but
890 if that doesn't work check your reference diskette). Owners of
891 model 95 with a LED-matrix-display can in addition activate some
892 activity info like under OS/2, but more informative, by setting
893 'ibmmcascsi=display' as an additional kernel parameter. Try "man
894 bootparam" or see the documentation of your boot loader about how to
895 pass options to the kernel.
896
897 To compile this driver as a module, choose M here: the
898 module will be called ibmmca.
899
900config IBMMCA_SCSI_ORDER_STANDARD
901 bool "Standard SCSI-order"
902 depends on SCSI_IBMMCA
903 ---help---
904 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
905 are assigned to the drive letters, starting with the lowest SCSI-id
906 (physical number -- pun) to be drive C:, as seen from DOS and
907 similar operating systems. When looking into papers describing the
908 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
909 The SCSI-standard follows a hardware-hierarchy which says that id 7
910 has the highest priority and id 0 the lowest. Therefore, the host
911 adapters are still today everywhere placed as SCSI-id 7 by default.
912 In the SCSI-standard, the drive letters express the priority of the
913 disk. C: should be the hard disk, or a partition on it, with the
914 highest priority. This must therefore be the disk with the highest
915 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
916 original definition of the SCSI-standard as also industrial- and
917 process-control-machines, like VME-CPUs running under realtime-OSes
918 (e.g. LynxOS, OS9) do.
919
920 If you like to run Linux on your MCA-machine with the same
921 assignment of hard disks as seen from e.g. DOS or OS/2 on your
922 machine, which is in addition conformant to the SCSI-standard, you
923 must say Y here. This is also necessary for MCA-Linux users who want
924 to keep downward compatibility to older releases of the
925 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
926 June 1997).
927
928 If you like to have the lowest SCSI-id assigned as drive C:, as
929 modern SCSI-BIOSes do, which does not conform to the standard, but
930 is widespread and common in the PC-world of today, you must say N
931 here. If unsure, say Y.
932
933config IBMMCA_SCSI_DEV_RESET
934 bool "Reset SCSI-devices at boottime"
935 depends on SCSI_IBMMCA
936 ---help---
937 By default, SCSI-devices are reset when the machine is powered on.
938 However, some devices exist, like special-control-devices,
939 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
940 not reset when switched on. If you say Y here, each device connected
941 to your SCSI-bus will be issued a reset-command after it has been
942 probed, while the kernel is booting. This may cause problems with
943 more modern devices, like hard disks, which do not appreciate these
944 reset commands, and can cause your system to hang. So say Y only if
945 you know that one of your older devices needs it; N is the safe
946 answer.
947
948config SCSI_IPS
949 tristate "IBM ServeRAID support"
950 depends on PCI && SCSI
951 ---help---
952 This is support for the IBM ServeRAID hardware RAID controllers.
953 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200954 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700955 for more information. If this driver does not work correctly
956 without modification please contact the author by email at
957 <ipslinux@adaptec.com>.
958
959 To compile this driver as a module, choose M here: the
960 module will be called ips.
961
962config SCSI_IBMVSCSI
963 tristate "IBM Virtual SCSI support"
964 depends on PPC_PSERIES || PPC_ISERIES
FUJITA Tomonori4d680412007-06-27 16:32:50 +0900965 select SCSI_SRP_ATTRS
Kamalesh Babulald2b43972009-01-06 05:57:24 +0000966 select VIOPATH if PPC_ISERIES
Linus Torvalds1da177e2005-04-16 15:20:36 -0700967 help
968 This is the IBM POWER Virtual SCSI Client
969
970 To compile this driver as a module, choose M here: the
971 module will be called ibmvscsic.
972
FUJITA Tomonori0e5d0302006-12-01 03:00:54 +0900973config SCSI_IBMVSCSIS
974 tristate "IBM Virtual SCSI Server support"
FUJITA Tomonori0012fdf2007-08-02 00:20:34 +0900975 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS
FUJITA Tomonori0e5d0302006-12-01 03:00:54 +0900976 help
977 This is the SRP target driver for IBM pSeries virtual environments.
978
979 The userspace component needed to initialize the driver and
980 documentation can be found:
981
982 http://stgt.berlios.de/
983
984 To compile this driver as a module, choose M here: the
985 module will be called ibmvstgt.
986
Brian King072b91f2008-07-01 13:14:30 -0500987config SCSI_IBMVFC
988 tristate "IBM Virtual FC support"
989 depends on PPC_PSERIES && SCSI
990 select SCSI_FC_ATTRS
991 help
992 This is the IBM POWER Virtual FC Client
993
994 To compile this driver as a module, choose M here: the
995 module will be called ibmvfc.
996
997config SCSI_IBMVFC_TRACE
998 bool "enable driver internal trace"
999 depends on SCSI_IBMVFC
1000 default y
1001 help
1002 If you say Y here, the driver will trace all commands issued
1003 to the adapter. Performance impact is minimal. Trace can be
1004 dumped using /sys/class/scsi_host/hostXX/trace.
1005
Linus Torvalds1da177e2005-04-16 15:20:36 -07001006config SCSI_INITIO
1007 tristate "Initio 9100U(W) support"
1008 depends on PCI && SCSI
1009 help
1010 This is support for the Initio 91XXU(W) SCSI host adapter. Please
1011 read the SCSI-HOWTO, available from
1012 <http://www.tldp.org/docs.html#howto>.
1013
1014 To compile this driver as a module, choose M here: the
1015 module will be called initio.
1016
1017config SCSI_INIA100
1018 tristate "Initio INI-A100U2W support"
1019 depends on PCI && SCSI
1020 help
1021 This is support for the Initio INI-A100U2W SCSI host adapter.
1022 Please read the SCSI-HOWTO, available from
1023 <http://www.tldp.org/docs.html#howto>.
1024
1025 To compile this driver as a module, choose M here: the
1026 module will be called a100u2w.
1027
1028config SCSI_PPA
1029 tristate "IOMEGA parallel port (ppa - older drives)"
Marko Kohtala6a19b412006-01-06 00:19:49 -08001030 depends on SCSI && PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -07001031 ---help---
1032 This driver supports older versions of IOMEGA's parallel port ZIP
1033 drive (a 100 MB removable media device).
1034
1035 Note that you can say N here if you have the SCSI version of the ZIP
1036 drive: it will be supported automatically if you said Y to the
1037 generic "SCSI disk support", above.
1038
1039 If you have the ZIP Plus drive or a more recent parallel port ZIP
1040 drive (if the supplied cable with the drive is labeled "AutoDetect")
1041 then you should say N here and Y to "IOMEGA parallel port (imm -
1042 newer drives)", below.
1043
1044 For more information about this driver and how to use it you should
1045 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1046 the SCSI-HOWTO, which is available from
1047 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1048 you will still be able to use the parallel port for other tasks,
1049 such as a printer; it is safe to compile both drivers into the
1050 kernel.
1051
1052 To compile this driver as a module, choose M here: the
1053 module will be called ppa.
1054
1055config SCSI_IMM
1056 tristate "IOMEGA parallel port (imm - newer drives)"
Marko Kohtala6a19b412006-01-06 00:19:49 -08001057 depends on SCSI && PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -07001058 ---help---
1059 This driver supports newer versions of IOMEGA's parallel port ZIP
1060 drive (a 100 MB removable media device).
1061
1062 Note that you can say N here if you have the SCSI version of the ZIP
1063 drive: it will be supported automatically if you said Y to the
1064 generic "SCSI disk support", above.
1065
1066 If you have the ZIP Plus drive or a more recent parallel port ZIP
1067 drive (if the supplied cable with the drive is labeled "AutoDetect")
1068 then you should say Y here; if you have an older ZIP drive, say N
1069 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
1070
1071 For more information about this driver and how to use it you should
1072 read the file <file:Documentation/scsi/ppa.txt>. You should also read
1073 the SCSI-HOWTO, which is available from
1074 <http://www.tldp.org/docs.html#howto>. If you use this driver,
1075 you will still be able to use the parallel port for other tasks,
1076 such as a printer; it is safe to compile both drivers into the
1077 kernel.
1078
1079 To compile this driver as a module, choose M here: the
1080 module will be called imm.
1081
1082config SCSI_IZIP_EPP16
1083 bool "ppa/imm option - Use slow (but safe) EPP-16"
Marko Kohtala6a19b412006-01-06 00:19:49 -08001084 depends on SCSI_PPA || SCSI_IMM
Linus Torvalds1da177e2005-04-16 15:20:36 -07001085 ---help---
1086 EPP (Enhanced Parallel Port) is a standard for parallel ports which
1087 allows them to act as expansion buses that can handle up to 64
1088 peripheral devices.
1089
1090 Some parallel port chipsets are slower than their motherboard, and
1091 so we have to control the state of the chipset's FIFO queue every
1092 now and then to avoid data loss. This will be done if you say Y
1093 here.
1094
1095 Generally, saying Y is the safe option and slows things down a bit.
1096
1097config SCSI_IZIP_SLOW_CTR
1098 bool "ppa/imm option - Assume slow parport control register"
Marko Kohtala6a19b412006-01-06 00:19:49 -08001099 depends on SCSI_PPA || SCSI_IMM
Linus Torvalds1da177e2005-04-16 15:20:36 -07001100 help
1101 Some parallel ports are known to have excessive delays between
1102 changing the parallel port control register and good data being
1103 available on the parallel port data/status register. This option
1104 forces a small delay (1.0 usec to be exact) after changing the
1105 control register to let things settle out. Enabling this option may
1106 result in a big drop in performance but some very old parallel ports
1107 (found in 386 vintage machines) will not work properly.
1108
1109 Generally, saying N is fine.
1110
1111config SCSI_NCR53C406A
1112 tristate "NCR53c406a SCSI support"
1113 depends on ISA && SCSI
1114 help
1115 This is support for the NCR53c406a SCSI host adapter. For user
1116 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
1117 in the kernel source. Also read the SCSI-HOWTO, available from
1118 <http://www.tldp.org/docs.html#howto>.
1119
1120 To compile this driver as a module, choose M here: the
1121 module will be called NCR53c406.
1122
1123config SCSI_NCR_D700
1124 tristate "NCR Dual 700 MCA SCSI support"
1125 depends on MCA && SCSI
1126 select SCSI_SPI_ATTRS
1127 help
1128 This is a driver for the MicroChannel Dual 700 card produced by
1129 NCR and commonly used in 345x/35xx/4100 class machines. It always
1130 tries to negotiate sync and uses tag command queueing.
1131
1132 Unless you have an NCR manufactured machine, the chances are that
1133 you do not have this SCSI card, so say N.
1134
Linus Torvalds1da177e2005-04-16 15:20:36 -07001135config SCSI_LASI700
1136 tristate "HP Lasi SCSI support for 53c700/710"
1137 depends on GSC && SCSI
1138 select SCSI_SPI_ATTRS
1139 help
1140 This is a driver for the SCSI controller in the Lasi chip found in
1141 many PA-RISC workstations & servers. If you do not know whether you
1142 have a Lasi chip, it is safe to say "Y" here.
1143
Thomas Bogendoerferc27d85f2006-12-25 21:32:04 +01001144config SCSI_SNI_53C710
1145 tristate "SNI RM SCSI support for 53c710"
1146 depends on SNI_RM && SCSI
1147 select SCSI_SPI_ATTRS
1148 select 53C700_LE_ON_BE
1149 help
1150 This is a driver for the onboard SCSI controller found in older
1151 SNI RM workstations & servers.
1152
Linus Torvalds1da177e2005-04-16 15:20:36 -07001153config 53C700_LE_ON_BE
1154 bool
1155 depends on SCSI_LASI700
1156 default y
1157
Jeff Garzik5a25ba12006-09-01 03:12:19 -04001158config SCSI_STEX
1159 tristate "Promise SuperTrak EX Series support"
1160 depends on PCI && SCSI
1161 ---help---
Ed Linee926b22006-12-04 17:49:36 -08001162 This driver supports Promise SuperTrak EX series storage controllers.
1163
1164 Promise provides Linux RAID configuration utility for these
1165 controllers. Please visit <http://www.promise.com> to download.
1166
1167 To compile this driver as a module, choose M here: the
1168 module will be called stex.
Jeff Garzik5a25ba12006-09-01 03:12:19 -04001169
Kars de Jong63273132007-06-17 14:47:05 +02001170config 53C700_BE_BUS
1171 bool
Kars de Jong45804fb2007-06-17 14:47:09 +02001172 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
Kars de Jong63273132007-06-17 14:47:05 +02001173 default y
1174
Linus Torvalds1da177e2005-04-16 15:20:36 -07001175config SCSI_SYM53C8XX_2
1176 tristate "SYM53C8XX Version 2 SCSI support"
1177 depends on PCI && SCSI
1178 select SCSI_SPI_ATTRS
1179 ---help---
1180 This driver supports the whole NCR53C8XX/SYM53C8XX family of
1181 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
1182 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1183 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1184 controllers; you need to use the Fusion MPT driver for that.
1185
1186 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1187 information.
1188
1189config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1190 int "DMA addressing mode"
1191 depends on SCSI_SYM53C8XX_2
1192 default "1"
1193 ---help---
1194 This option only applies to PCI-SCSI chips that are PCI DAC
1195 capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1196
1197 When set to 0, the driver will program the chip to only perform
1198 32-bit DMA. When set to 1, the chip will be able to perform DMA
1199 to addresses up to 1TB. When set to 2, the driver supports the
1200 full 64-bit DMA address range, but can only address 16 segments
1201 of 4 GB each. This limits the total addressable range to 64 GB.
1202
1203 Most machines with less than 4GB of memory should use a setting
1204 of 0 for best performance. If your machine has 4GB of memory
1205 or more, you should set this option to 1 (the default).
1206
1207 The still experimental value 2 (64 bit DMA addressing with 16
1208 x 4GB segments limitation) can be used on systems that require
1209 PCI address bits past bit 39 to be set for the addressing of
1210 memory using PCI DAC cycles.
1211
1212config SCSI_SYM53C8XX_DEFAULT_TAGS
Matthew Wilcox1f61d822006-03-28 11:03:43 -05001213 int "Default tagged command queue depth"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001214 depends on SCSI_SYM53C8XX_2
1215 default "16"
1216 help
1217 This is the default value of the command queue depth the
1218 driver will announce to the generic SCSI layer for devices
1219 that support tagged command queueing. This value can be changed
1220 from the boot command line. This is a soft limit that cannot
1221 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1222
1223config SCSI_SYM53C8XX_MAX_TAGS
Matthew Wilcox1f61d822006-03-28 11:03:43 -05001224 int "Maximum number of queued commands"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001225 depends on SCSI_SYM53C8XX_2
1226 default "64"
1227 help
1228 This option allows you to specify the maximum number of commands
1229 that can be queued to any device, when tagged command queuing is
1230 possible. The driver supports up to 256 queued commands per device.
1231 This value is used as a compiled-in hard limit.
1232
Matthew Wilcox1f61d822006-03-28 11:03:43 -05001233config SCSI_SYM53C8XX_MMIO
1234 bool "Use memory mapped IO"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001235 depends on SCSI_SYM53C8XX_2
Matthew Wilcox1f61d822006-03-28 11:03:43 -05001236 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001237 help
Matthew Wilcox1f61d822006-03-28 11:03:43 -05001238 Memory mapped IO is faster than Port IO. Most people should
1239 answer Y here, but some machines may have problems. If you have
1240 to answer N here, please report the problem to the maintainer.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001241
1242config SCSI_IPR
1243 tristate "IBM Power Linux RAID adapter support"
Brian King35a39692006-09-25 12:39:20 -05001244 depends on PCI && SCSI && ATA
Linus Torvalds1da177e2005-04-16 15:20:36 -07001245 select FW_LOADER
1246 ---help---
1247 This driver supports the IBM Power Linux family RAID adapters.
1248 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1249 as IBM iSeries 5702, 5703, 5709, and 570A.
1250
1251config SCSI_IPR_TRACE
1252 bool "enable driver internal trace"
1253 depends on SCSI_IPR
Brian Kingefbbdd82006-11-21 10:28:16 -06001254 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001255 help
1256 If you say Y here, the driver will trace all commands issued
1257 to the adapter. Performance impact is minimal. Trace can be
1258 dumped using /sys/bus/class/scsi_host/hostXX/trace.
1259
1260config SCSI_IPR_DUMP
1261 bool "enable adapter dump support"
1262 depends on SCSI_IPR
Brian Kingefbbdd82006-11-21 10:28:16 -06001263 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001264 help
1265 If you say Y here, the driver will support adapter crash dump.
1266 If you enable this support, the iprdump daemon can be used
1267 to capture adapter failure analysis information.
1268
1269config SCSI_ZALON
1270 tristate "Zalon SCSI support"
1271 depends on GSC && SCSI
1272 select SCSI_SPI_ATTRS
1273 help
1274 The Zalon is a GSC/HSC bus interface chip that sits between the
1275 PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1276 C110, J200, J210 and some D, K & R-class machines. It's also
1277 used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1278 Say Y here if you have one of these machines or cards.
1279
1280config SCSI_NCR_Q720
1281 tristate "NCR Quad 720 MCA SCSI support"
1282 depends on MCA && SCSI
1283 select SCSI_SPI_ATTRS
1284 help
1285 This is a driver for the MicroChannel Quad 720 card produced by
1286 NCR and commonly used in 345x/35xx/4100 class machines. It always
1287 tries to negotiate sync and uses tag command queueing.
1288
1289 Unless you have an NCR manufactured machine, the chances are that
1290 you do not have this SCSI card, so say N.
1291
1292config SCSI_NCR53C8XX_DEFAULT_TAGS
Roman Zippele55a3e82006-06-08 22:12:49 -07001293 int "default tagged command queue depth"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001294 depends on SCSI_ZALON || SCSI_NCR_Q720
1295 default "8"
1296 ---help---
1297 "Tagged command queuing" is a feature of SCSI-2 which improves
1298 performance: the host adapter can send several SCSI commands to a
1299 device's queue even if previous commands haven't finished yet.
1300 Because the device is intelligent, it can optimize its operations
1301 (like head positioning) based on its own request queue. Some SCSI
1302 devices don't implement this properly; if you want to disable this
1303 feature, enter 0 or 1 here (it doesn't matter which).
1304
1305 The default value is 8 and should be supported by most hard disks.
1306 This value can be overridden from the boot command line using the
1307 'tags' option as follows (example):
1308 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1309 4, set queue depth to 16 for target 2 and target 3 on controller 0
1310 and set queue depth to 10 for target 0 / lun 2 on controller 1.
1311
1312 The normal answer therefore is to go with the default 8 and to use
1313 a boot command line option for devices that need to use a different
1314 command queue depth.
1315
1316 There is no safe option other than using good SCSI devices.
1317
1318config SCSI_NCR53C8XX_MAX_TAGS
Roman Zippele55a3e82006-06-08 22:12:49 -07001319 int "maximum number of queued commands"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001320 depends on SCSI_ZALON || SCSI_NCR_Q720
1321 default "32"
1322 ---help---
1323 This option allows you to specify the maximum number of commands
1324 that can be queued to any device, when tagged command queuing is
1325 possible. The default value is 32. Minimum is 2, maximum is 64.
1326 Modern hard disks are able to support 64 tags and even more, but
1327 do not seem to be faster when more than 32 tags are being used.
1328
1329 So, the normal answer here is to go with the default value 32 unless
1330 you are using very large hard disks with large cache (>= 1 MB) that
1331 are able to take advantage of more than 32 tagged commands.
1332
1333 There is no safe option and the default answer is recommended.
1334
1335config SCSI_NCR53C8XX_SYNC
Roman Zippele55a3e82006-06-08 22:12:49 -07001336 int "synchronous transfers frequency in MHz"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001337 depends on SCSI_ZALON || SCSI_NCR_Q720
1338 default "20"
1339 ---help---
1340 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1341 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
1342 are respectively the maximum data transfer rates in mega-transfers
1343 per second for each class. For example, a FAST-20 Wide 16 device is
1344 able to transfer data at 20 million 16 bit packets per second for a
1345 total rate of 40 MB/s.
1346
1347 You may specify 0 if you want to only use asynchronous data
1348 transfers. This is the safest and slowest option. Otherwise, specify
1349 a value between 5 and 80, depending on the capability of your SCSI
1350 controller. The higher the number, the faster the data transfer.
1351 Note that 80 should normally be ok since the driver decreases the
1352 value automatically according to the controller's capabilities.
1353
1354 Your answer to this question is ignored for controllers with NVRAM,
1355 since the driver will get this information from the user set-up. It
1356 also can be overridden using a boot setup option, as follows
1357 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1358 for FAST-20 synchronous data transfer (20 mega-transfers per
1359 second).
1360
1361 The normal answer therefore is not to go with the default but to
1362 select the maximum value 80 allowing the driver to use the maximum
1363 value supported by each controller. If this causes problems with
1364 your SCSI devices, you should come back and decrease the value.
1365
1366 There is no safe option other than using good cabling, right
1367 terminations and SCSI conformant devices.
1368
Linus Torvalds1da177e2005-04-16 15:20:36 -07001369config SCSI_NCR53C8XX_NO_DISCONNECT
Roman Zippele55a3e82006-06-08 22:12:49 -07001370 bool "not allow targets to disconnect"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001371 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1372 help
1373 This option is only provided for safety if you suspect some SCSI
1374 device of yours to not support properly the target-disconnect
1375 feature. In that case, you would say Y here. In general however, to
1376 not allow targets to disconnect is not reasonable if there is more
1377 than 1 device on a SCSI bus. The normal answer therefore is N.
1378
Linus Torvalds1da177e2005-04-16 15:20:36 -07001379config SCSI_PAS16
1380 tristate "PAS16 SCSI support"
1381 depends on ISA && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001382 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001383 ---help---
1384 This is support for a SCSI host adapter. It is explained in section
1385 3.10 of the SCSI-HOWTO, available from
1386 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1387 of the box, you may have to change some settings in
1388 <file:drivers/scsi/pas16.h>.
1389
1390 To compile this driver as a module, choose M here: the
1391 module will be called pas16.
1392
Linus Torvalds1da177e2005-04-16 15:20:36 -07001393config SCSI_QLOGIC_FAS
1394 tristate "Qlogic FAS SCSI support"
1395 depends on ISA && SCSI
1396 ---help---
1397 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1398 FastSCSI! cards as well as any other card based on the FASXX chip
1399 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1400
1401 This driver does NOT support the PCI versions of these cards. The
1402 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1403 SCSI support"), below.
1404
1405 Information about this driver is contained in
1406 <file:Documentation/scsi/qlogicfas.txt>. You should also read the
1407 SCSI-HOWTO, available from
1408 <http://www.tldp.org/docs.html#howto>.
1409
1410 To compile this driver as a module, choose M here: the
1411 module will be called qlogicfas.
1412
Linus Torvalds1da177e2005-04-16 15:20:36 -07001413config SCSI_QLOGIC_1280
1414 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1415 depends on PCI && SCSI
1416 help
1417 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1418
1419 To compile this driver as a module, choose M here: the
1420 module will be called qla1280.
1421
Linus Torvalds1da177e2005-04-16 15:20:36 -07001422config SCSI_QLOGICPTI
1423 tristate "PTI Qlogic, ISP Driver"
1424 depends on SBUS && SCSI
1425 help
1426 This driver supports SBUS SCSI controllers from PTI or QLogic. These
1427 controllers are known under Solaris as qpti and in the openprom as
1428 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1429 driven by a different driver.
1430
1431 To compile this driver as a module, choose M here: the
1432 module will be called qlogicpti.
1433
1434source "drivers/scsi/qla2xxx/Kconfig"
David Somayajuluafaf5a22006-09-19 10:28:00 -07001435source "drivers/scsi/qla4xxx/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001436
dea31012005-04-17 16:05:31 -05001437config SCSI_LPFC
1438 tristate "Emulex LightPulse Fibre Channel Support"
1439 depends on PCI && SCSI
1440 select SCSI_FC_ATTRS
1441 help
1442 This lpfc driver supports the Emulex LightPulse
1443 Family of Fibre Channel PCI host adapters.
1444
James Smart923e4b62008-12-04 22:40:07 -05001445config SCSI_LPFC_DEBUG_FS
1446 bool "Emulex LightPulse Fibre Channel debugfs Support"
1447 depends on SCSI_LPFC && DEBUG_FS
1448 help
Matt LaPlante692105b2009-01-26 11:12:25 +01001449 This makes debugging information from the lpfc driver
James Smart923e4b62008-12-04 22:40:07 -05001450 available via the debugfs filesystem.
1451
Linus Torvalds1da177e2005-04-16 15:20:36 -07001452config SCSI_SIM710
1453 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1454 depends on (EISA || MCA) && SCSI
1455 select SCSI_SPI_ATTRS
1456 ---help---
Matt LaPlante692105b2009-01-26 11:12:25 +01001457 This driver is for NCR53c710 based SCSI host adapters.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001458
1459 It currently supports Compaq EISA cards and NCR MCA cards
1460
Linus Torvalds1da177e2005-04-16 15:20:36 -07001461config SCSI_SYM53C416
1462 tristate "Symbios 53c416 SCSI support"
1463 depends on ISA && SCSI
1464 ---help---
1465 This is support for the sym53c416 SCSI host adapter, the SCSI
1466 adapter that comes with some HP scanners. This driver requires that
1467 the sym53c416 is configured first using some sort of PnP
1468 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1469 are using isapnp then you need to compile this driver as a module
1470 and then load it using insmod after isapnp has run. The parameters
1471 of the configured card(s) should be passed to the driver. The format
1472 is:
1473
1474 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1475
1476 To compile this driver as a module, choose M here: the
1477 module will be called sym53c416.
1478
1479config SCSI_DC395x
1480 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1481 depends on PCI && SCSI && EXPERIMENTAL
1482 ---help---
1483 This driver supports PCI SCSI host adapters based on the ASIC
1484 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1485
1486 This driver works, but is still in experimental status. So better
1487 have a bootable disk and a backup in case of emergency.
1488
1489 Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1490
1491 To compile this driver as a module, choose M here: the
1492 module will be called dc395x.
1493
1494config SCSI_DC390T
1495 tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
1496 depends on PCI && SCSI
1497 ---help---
1498 This driver supports PCI SCSI host adapters based on the Am53C974A
1499 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1500 PCscsi/PCnet (Am53/79C974) solutions.
1501
1502 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1503
1504 Note that this driver does NOT support Tekram DC390W/U/F, which are
1505 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1506
1507 To compile this driver as a module, choose M here: the
1508 module will be called tmscsim.
1509
1510config SCSI_T128
1511 tristate "Trantor T128/T128F/T228 SCSI support"
1512 depends on ISA && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001513 select SCSI_SPI_ATTRS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -07001514 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -07001515 ---help---
1516 This is support for a SCSI host adapter. It is explained in section
1517 3.11 of the SCSI-HOWTO, available from
1518 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1519 of the box, you may have to change some settings in
1520 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
1521 Adaptec, and some former Trantor products are being sold under the
1522 Adaptec name.
1523
1524 To compile this driver as a module, choose M here: the
1525 module will be called t128.
1526
1527config SCSI_U14_34F
1528 tristate "UltraStor 14F/34F support"
Al Viroa5532602005-05-04 05:39:42 +01001529 depends on ISA && SCSI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -07001530 ---help---
1531 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1532 The source at <file:drivers/scsi/u14-34f.c> contains some
1533 information about this hardware. If the driver doesn't work out of
1534 the box, you may have to change some settings in
1535 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
1536 <http://www.tldp.org/docs.html#howto>. Note that there is also
1537 another driver for the same hardware: "UltraStor SCSI support",
1538 below. You should say Y to both only if you want 24F support as
1539 well.
1540
1541 To compile this driver as a module, choose M here: the
1542 module will be called u14-34f.
1543
1544config SCSI_U14_34F_TAGGED_QUEUE
1545 bool "enable tagged command queueing"
1546 depends on SCSI_U14_34F
1547 help
1548 This is a feature of SCSI-2 which improves performance: the host
1549 adapter can send several SCSI commands to a device's queue even if
1550 previous commands haven't finished yet.
1551 This is equivalent to the "u14-34f=tc:y" boot option.
1552
1553config SCSI_U14_34F_LINKED_COMMANDS
1554 bool "enable elevator sorting"
1555 depends on SCSI_U14_34F
1556 help
1557 This option enables elevator sorting for all probed SCSI disks and
1558 CD-ROMs. It definitely reduces the average seek distance when doing
1559 random seeks, but this does not necessarily result in a noticeable
1560 performance improvement: your mileage may vary...
1561 This is equivalent to the "u14-34f=lc:y" boot option.
1562
1563config SCSI_U14_34F_MAX_TAGS
1564 int "maximum number of queued commands"
1565 depends on SCSI_U14_34F
1566 default "8"
1567 help
1568 This specifies how many SCSI commands can be maximally queued for
1569 each probed SCSI device. You should reduce the default value of 8
1570 only if you have disks with buggy or limited tagged command support.
1571 Minimum is 2 and maximum is 14. This value is also the window size
1572 used by the elevator sorting option above. The effective value used
1573 by the driver for each probed SCSI device is reported at boot time.
1574 This is equivalent to the "u14-34f=mq:8" boot option.
1575
1576config SCSI_ULTRASTOR
1577 tristate "UltraStor SCSI support"
1578 depends on X86 && ISA && SCSI
1579 ---help---
1580 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1581 adapter family. This driver is explained in section 3.12 of the
1582 SCSI-HOWTO, available from
1583 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
1584 of the box, you may have to change some settings in
1585 <file:drivers/scsi/ultrastor.h>.
1586
1587 Note that there is also another driver for the same hardware:
1588 "UltraStor 14F/34F support", above.
1589
1590 To compile this driver as a module, choose M here: the
1591 module will be called ultrastor.
1592
1593config SCSI_NSP32
1594 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1595 depends on PCI && SCSI && !64BIT
1596 help
1597 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1598 SCSI host adapter. Please read the SCSI-HOWTO, available from
1599 <http://www.tldp.org/docs.html#howto>.
1600
1601 To compile this driver as a module, choose M here: the
1602 module will be called nsp32.
1603
1604config SCSI_DEBUG
1605 tristate "SCSI debugging host simulator"
1606 depends on SCSI
Randy Dunlapd0ace3c2009-01-12 10:53:04 -08001607 select CRC_T10DIF
Linus Torvalds1da177e2005-04-16 15:20:36 -07001608 help
1609 This is a host adapter simulator that can simulate multiple hosts
1610 each with multiple dummy SCSI devices (disks). It defaults to one
1611 host adapter with one dummy SCSI disk. Each dummy disk uses kernel
1612 RAM as storage (i.e. it is a ramdisk). To save space when multiple
1613 dummy disks are simulated, they share the same kernel RAM for
Justin P. Mattock631dd1a2010-10-18 11:03:14 +02001614 their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
Linus Torvalds1da177e2005-04-16 15:20:36 -07001615 information. This driver is primarily of use to those testing the
1616 SCSI and block subsystems. If unsure, say N.
1617
1618config SCSI_MESH
1619 tristate "MESH (Power Mac internal SCSI) support"
1620 depends on PPC32 && PPC_PMAC && SCSI
1621 help
1622 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1623 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1624 other Power Macintoshes do). Say Y to include support for this SCSI
1625 adaptor.
1626
1627 To compile this driver as a module, choose M here: the
1628 module will be called mesh.
1629
1630config SCSI_MESH_SYNC_RATE
1631 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1632 depends on SCSI_MESH
1633 default "5"
1634 help
1635 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1636 drives a bus which is entirely internal to the machine (such as the
1637 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1638 operation at up to 10 MB/s. On machines where the SCSI bus
1639 controlled by the MESH can have external devices connected, it is
1640 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1641 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1642 to disable synchronous operation.
1643
1644config SCSI_MESH_RESET_DELAY_MS
1645 int "initial bus reset delay (ms) (0 = no reset)"
1646 depends on SCSI_MESH
1647 default "4000"
1648
1649config SCSI_MAC53C94
1650 tristate "53C94 (Power Mac external SCSI) support"
1651 depends on PPC32 && PPC_PMAC && SCSI
1652 help
1653 On Power Macintoshes (and clones) with two SCSI buses, the external
1654 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1655 machines which only have one SCSI bus, such as the 7200, also use
1656 the 53C94. Say Y to include support for the 53C94.
1657
1658 To compile this driver as a module, choose M here: the
1659 module will be called mac53c94.
1660
1661source "drivers/scsi/arm/Kconfig"
1662
1663config JAZZ_ESP
1664 bool "MIPS JAZZ FAS216 SCSI support"
1665 depends on MACH_JAZZ && SCSI
David S. Miller3a243072007-06-03 17:56:04 -07001666 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001667 help
1668 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1669 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1670 systems.
1671
1672config A3000_SCSI
1673 tristate "A3000 WD33C93A support"
1674 depends on AMIGA && SCSI
1675 help
1676 If you have an Amiga 3000 and have SCSI devices connected to the
1677 built-in SCSI controller, say Y. Otherwise, say N.
1678
1679 To compile this driver as a module, choose M here: the
Geert Uytterhoeven90638f92007-08-22 14:01:34 -07001680 module will be called a3000.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001681
1682config A2091_SCSI
1683 tristate "A2091/A590 WD33C93A support"
1684 depends on ZORRO && SCSI
1685 help
1686 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1687 say N.
1688
1689 To compile this driver as a module, choose M here: the
Geert Uytterhoeven90638f92007-08-22 14:01:34 -07001690 module will be called a2091.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001691
1692config GVP11_SCSI
1693 tristate "GVP Series II WD33C93A support"
1694 depends on ZORRO && SCSI
1695 ---help---
1696 If you have a Great Valley Products Series II SCSI controller,
1697 answer Y. Also say Y if you have a later model of GVP SCSI
1698 controller (such as the GVP A4008 or a Combo board). Otherwise,
1699 answer N. This driver does NOT work for the T-Rex series of
1700 accelerators from TekMagic and GVP-M.
1701
1702 To compile this driver as a module, choose M here: the
1703 module will be called gvp11.
1704
Kars de Jonga16efc12007-06-17 14:47:08 +02001705config SCSI_A4000T
1706 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
1707 depends on AMIGA && SCSI && EXPERIMENTAL
1708 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001709 help
Kars de Jonga16efc12007-06-17 14:47:08 +02001710 If you have an Amiga 4000T and have SCSI devices connected to the
1711 built-in SCSI controller, say Y. Otherwise, say N.
1712
1713 To compile this driver as a module, choose M here: the
1714 module will be called a4000t.
1715
Kars de Jong45804fb2007-06-17 14:47:09 +02001716config SCSI_ZORRO7XX
1717 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
1718 depends on ZORRO && SCSI && EXPERIMENTAL
1719 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001720 help
Kars de Jong45804fb2007-06-17 14:47:09 +02001721 Support for various NCR53c710-based SCSI controllers on Zorro
1722 expansion boards for the Amiga.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001723 This includes:
Linus Torvalds1da177e2005-04-16 15:20:36 -07001724 - the Amiga 4091 Zorro III SCSI-2 controller,
1725 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1726 (info at
1727 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1728 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1729 accelerator card for the Amiga 1200,
1730 - the SCSI controller on the GVP Turbo 040/060 accelerator.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001731
Linus Torvalds1da177e2005-04-16 15:20:36 -07001732config ATARI_SCSI
1733 tristate "Atari native SCSI support"
Michael Schmitzfb810d12007-05-01 22:32:35 +02001734 depends on ATARI && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001735 select SCSI_SPI_ATTRS
Geert Uytterhoevenfff11c02008-10-13 21:59:02 +02001736 select NVRAM
Linus Torvalds1da177e2005-04-16 15:20:36 -07001737 ---help---
1738 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1739 Falcon, ...) say Y to get it supported. Of course also, if you have
1740 a compatible SCSI controller (e.g. for Medusa).
1741
1742 To compile this driver as a module, choose M here: the
1743 module will be called atari_scsi.
1744
1745 This driver supports both styles of NCR integration into the
1746 system: the TT style (separate DMA), and the Falcon style (via
1747 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1748 in the Hades (without DMA).
1749
1750config ATARI_SCSI_TOSHIBA_DELAY
1751 bool "Long delays for Toshiba CD-ROMs"
1752 depends on ATARI_SCSI
1753 help
1754 This option increases the delay after a SCSI arbitration to
1755 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1756 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1757 would impact performance a bit, so say N.
1758
1759config ATARI_SCSI_RESET_BOOT
1760 bool "Reset SCSI-devices at boottime"
1761 depends on ATARI_SCSI
1762 help
1763 Reset the devices on your Atari whenever it boots. This makes the
1764 boot process fractionally longer but may assist recovery from errors
1765 that leave the devices with SCSI operations partway completed.
1766
Linus Torvalds1da177e2005-04-16 15:20:36 -07001767config MAC_SCSI
1768 bool "Macintosh NCR5380 SCSI"
Al Virofa53bb62005-08-23 22:48:07 +01001769 depends on MAC && SCSI=y
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001770 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001771 help
1772 This is the NCR 5380 SCSI controller included on most of the 68030
1773 based Macintoshes. If you have one of these say Y and read the
1774 SCSI-HOWTO, available from
1775 <http://www.tldp.org/docs.html#howto>.
1776
Finn Thain6fe07aa2008-04-25 10:06:05 -05001777config SCSI_MAC_ESP
1778 tristate "Macintosh NCR53c9[46] SCSI"
1779 depends on MAC && SCSI
Geert Uytterhoeven48fc8de2008-05-05 21:27:21 +02001780 select SCSI_SPI_ATTRS
Finn Thain6fe07aa2008-04-25 10:06:05 -05001781 help
1782 This is the NCR 53c9x SCSI controller found on most of the 68040
1783 based Macintoshes.
1784
1785 To compile this driver as a module, choose M here: the module
1786 will be called mac_esp.
1787
Linus Torvalds1da177e2005-04-16 15:20:36 -07001788config MVME147_SCSI
1789 bool "WD33C93 SCSI driver for MVME147"
Al Virofa53bb62005-08-23 22:48:07 +01001790 depends on MVME147 && SCSI=y
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001791 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001792 help
1793 Support for the on-board SCSI controller on the Motorola MVME147
1794 single-board computer.
1795
1796config MVME16x_SCSI
Kars de Jong506c7bb2007-06-17 14:47:07 +02001797 tristate "NCR53C710 SCSI driver for MVME16x"
1798 depends on MVME16x && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001799 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001800 help
1801 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1802 SCSI controller chip. Almost everyone using one of these boards
1803 will want to say Y to this question.
1804
1805config BVME6000_SCSI
Kars de Jong8276b582007-06-17 14:47:06 +02001806 tristate "NCR53C710 SCSI driver for BVME6000"
1807 depends on BVME6000 && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001808 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001809 help
1810 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1811 SCSI controller chip. Almost everyone using one of these boards
1812 will want to say Y to this question.
1813
Linus Torvalds1da177e2005-04-16 15:20:36 -07001814config SUN3_SCSI
1815 tristate "Sun3 NCR5380 SCSI"
Sam Creaseyc39e7ee2006-12-09 10:37:05 +01001816 depends on SUN3 && SCSI
Matthew Wilcox410ca5c2005-12-15 16:22:01 -05001817 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001818 help
1819 This option will enable support for the OBIO (onboard io) NCR5380
1820 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1821 "Sun3" type VME scsi controllers also based on the NCR5380.
1822 General Linux information on the Sun 3 series (now discontinued)
1823 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1824
1825config SUN3X_ESP
1826 bool "Sun3x ESP SCSI"
Al Virofa53bb62005-08-23 22:48:07 +01001827 depends on SUN3X && SCSI=y
Thomas Bogendoerfer0bb67f12008-02-01 00:13:34 +01001828 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001829 help
1830 The ESP was an on-board SCSI controller used on Sun 3/80
1831 machines. Say Y here to compile in support for it.
1832
1833config SCSI_SUNESP
1834 tristate "Sparc ESP Scsi Driver"
1835 depends on SBUS && SCSI
David S. Miller3a243072007-06-03 17:56:04 -07001836 select SCSI_SPI_ATTRS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001837 help
1838 This is the driver for the Sun ESP SCSI host adapter. The ESP
Frans Popdbfe54a2008-06-19 20:20:12 -07001839 chipset is present in most SPARC SBUS-based computers and
1840 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1841 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001842
1843 To compile this driver as a module, choose M here: the
Frans Popdbfe54a2008-06-19 20:20:12 -07001844 module will be called sun_esp.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001845
Linus Torvalds1da177e2005-04-16 15:20:36 -07001846config ZFCP
1847 tristate "FCP host bus adapter driver for IBM eServer zSeries"
Martin Schwidefsky347a8dc2006-01-06 00:19:28 -08001848 depends on S390 && QDIO && SCSI
Linus Torvalds1da177e2005-04-16 15:20:36 -07001849 select SCSI_FC_ATTRS
1850 help
1851 If you want to access SCSI devices attached to your IBM eServer
1852 zSeries by means of Fibre Channel interfaces say Y.
1853 For details please refer to the documentation provided by IBM at
1854 <http://oss.software.ibm.com/developerworks/opensource/linux390>
1855
1856 This driver is also available as a module. This module will be
1857 called zfcp. If you want to compile it as a module, say M here
Alexander E. Patrakov39f5fb32007-03-16 18:28:43 +05001858 and read <file:Documentation/kbuild/modules.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001859
Felix Beckef3eb712010-07-16 15:37:42 +02001860config ZFCP_DIF
1861 tristate "T10 DIF/DIX support for the zfcp driver (EXPERIMENTAL)"
1862 depends on ZFCP && EXPERIMENTAL
1863
Anil Ravindranath89a36812009-08-25 17:35:18 -07001864config SCSI_PMCRAID
1865 tristate "PMC SIERRA Linux MaxRAID adapter support"
Randy Dunlapb2045242010-08-10 18:01:24 -07001866 depends on PCI && SCSI && NET
Anil Ravindranath89a36812009-08-25 17:35:18 -07001867 ---help---
1868 This driver supports the PMC SIERRA MaxRAID adapters.
1869
jack wangdbf9bfe2009-10-14 16:19:21 +08001870config SCSI_PM8001
1871 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1872 depends on PCI && SCSI
1873 select SCSI_SAS_LIBSAS
1874 help
1875 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1876 based host adapters.
1877
FUJITA Tomonori26b14822006-12-01 03:00:50 +09001878config SCSI_SRP
1879 tristate "SCSI RDMA Protocol helper library"
1880 depends on SCSI && PCI
1881 select SCSI_TGT
1882 help
1883 If you wish to use SRP target drivers, say Y.
1884
1885 To compile this driver as a module, choose M here: the
1886 module will be called libsrp.
1887
Jing Huang7725ccf2009-09-23 17:46:15 -07001888config SCSI_BFA_FC
1889 tristate "Brocade BFA Fibre Channel Support"
1890 depends on PCI && SCSI
1891 select SCSI_FC_ATTRS
1892 help
1893 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1894
1895 To compile this driver as a module, choose M here. The module will
1896 be called bfa.
1897
Jan Engelhardtfc6e7402007-07-09 12:00:08 -07001898endif # SCSI_LOWLEVEL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001899
1900source "drivers/scsi/pcmcia/Kconfig"
1901
Chandra Seetharamana6a8d9f2008-05-01 14:49:46 -07001902source "drivers/scsi/device_handler/Kconfig"
1903
Boaz Harrosh68274792009-01-25 17:24:14 +02001904source "drivers/scsi/osd/Kconfig"
1905
Linus Torvalds1da177e2005-04-16 15:20:36 -07001906endmenu