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