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