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