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