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