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