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