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