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