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