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