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