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