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