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