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