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