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