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