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