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