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