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