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