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