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