| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | menu "SCSI device support" |
| 3 | |
| 4 | config SCSI_MOD |
| 5 | tristate |
| 6 | default y if SCSI=n || SCSI=y |
| 7 | default m if SCSI=m |
| 8 | depends on BLOCK |
| 9 | |
| 10 | config RAID_ATTRS |
| 11 | tristate "RAID Transport Class" |
| 12 | default n |
| 13 | depends on BLOCK |
| 14 | depends on SCSI_MOD |
| 15 | help |
| 16 | Provides RAID |
| 17 | |
| 18 | config SCSI_COMMON |
| 19 | tristate |
| 20 | |
| 21 | config SCSI |
| 22 | tristate "SCSI device support" |
| 23 | depends on BLOCK |
| 24 | select SCSI_DMA if HAS_DMA |
| 25 | select SG_POOL |
| 26 | select SCSI_COMMON |
| 27 | select BLK_DEV_BSG_COMMON if BLK_DEV_BSG |
| 28 | help |
| 29 | If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or |
| 30 | any other SCSI device under Linux, say Y and make sure that you know |
| 31 | the name of your SCSI host adapter (the card inside your computer |
| 32 | that "speaks" the SCSI protocol, also called SCSI controller), |
| 33 | because you will be asked for it. |
| 34 | |
| 35 | You also need to say Y here if you have a device which speaks |
| 36 | the SCSI protocol. Examples of this include the parallel port |
| 37 | version of the IOMEGA ZIP drive, USB storage devices, Fibre |
| 38 | Channel, and FireWire storage. |
| 39 | |
| 40 | To compile this driver as a module, choose M here and read |
| 41 | <file:Documentation/scsi/scsi.rst>. |
| 42 | The module will be called scsi_mod. |
| 43 | |
| 44 | However, do not compile this as a module if your root file system |
| 45 | (the one containing the directory /) is located on a SCSI device. |
| 46 | |
| 47 | config SCSI_DMA |
| 48 | bool |
| 49 | default n |
| 50 | |
| 51 | config SCSI_ESP_PIO |
| 52 | bool |
| 53 | |
| 54 | config SCSI_NETLINK |
| 55 | bool |
| 56 | default n |
| 57 | depends on NET |
| 58 | |
| 59 | config SCSI_PROC_FS |
| 60 | bool "legacy /proc/scsi/ support" |
| 61 | depends on SCSI && PROC_FS |
| 62 | default y |
| 63 | help |
| 64 | This option enables support for the various files in |
| 65 | /proc/scsi. In Linux 2.6 this has been superseded by |
| 66 | files in sysfs but many legacy applications rely on this. |
| 67 | |
| 68 | If unsure say Y. |
| 69 | |
| 70 | config SCSI_LIB_KUNIT_TEST |
| 71 | tristate "KUnit tests for SCSI Mid Layer's scsi_lib" if !KUNIT_ALL_TESTS |
| 72 | depends on KUNIT |
| 73 | default KUNIT_ALL_TESTS |
| 74 | help |
| 75 | Run SCSI Mid Layer's KUnit tests for scsi_lib. |
| 76 | |
| 77 | If unsure say N. |
| 78 | |
| 79 | comment "SCSI support type (disk, tape, CD-ROM)" |
| 80 | depends on SCSI |
| 81 | |
| 82 | config BLK_DEV_SD |
| 83 | tristate "SCSI disk support" |
| 84 | depends on SCSI |
| 85 | help |
| 86 | If you want to use SCSI hard disks, Fibre Channel disks, |
| 87 | Serial ATA (SATA) or Parallel ATA (PATA) hard disks, |
| 88 | USB storage or the SCSI or parallel port version of |
| 89 | the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO, |
| 90 | the Disk-HOWTO and the Multi-Disk-HOWTO, available from |
| 91 | <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI |
| 92 | CD-ROMs. |
| 93 | |
| 94 | To compile this driver as a module, choose M here and read |
| 95 | <file:Documentation/scsi/scsi.rst>. |
| 96 | The module will be called sd_mod. |
| 97 | |
| 98 | Do not compile this driver as a module if your root file system |
| 99 | (the one containing the directory /) is located on a SCSI disk. |
| 100 | In this case, do not compile the driver for your SCSI host adapter |
| 101 | (below) as a module either. |
| 102 | |
| 103 | config CHR_DEV_ST |
| 104 | tristate "SCSI tape support" |
| 105 | depends on SCSI |
| 106 | help |
| 107 | If you want to use a SCSI tape drive under Linux, say Y and read the |
| 108 | SCSI-HOWTO, available from |
| 109 | <http://www.tldp.org/docs.html#howto>, and |
| 110 | <file:Documentation/scsi/st.rst> in the kernel source. This is NOT |
| 111 | for SCSI CD-ROMs. |
| 112 | |
| 113 | To compile this driver as a module, choose M here and read |
| 114 | <file:Documentation/scsi/scsi.rst>. The module will be called st. |
| 115 | |
| 116 | config BLK_DEV_SR |
| 117 | tristate "SCSI CDROM support" |
| 118 | depends on SCSI && BLK_DEV |
| 119 | select CDROM |
| 120 | help |
| 121 | If you want to use a CD or DVD drive attached to your computer |
| 122 | by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO |
| 123 | and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>. |
| 124 | |
| 125 | Make sure to say Y or M to "ISO 9660 CD-ROM file system support". |
| 126 | |
| 127 | To compile this driver as a module, choose M here and read |
| 128 | <file:Documentation/scsi/scsi.rst>. |
| 129 | The module will be called sr_mod. |
| 130 | |
| 131 | config CHR_DEV_SG |
| 132 | tristate "SCSI generic support" |
| 133 | depends on SCSI |
| 134 | help |
| 135 | If you want to use SCSI scanners, synthesizers or CD-writers or just |
| 136 | about anything having "SCSI" in its name other than hard disks, |
| 137 | CD-ROMs or tapes, say Y here. These won't be supported by the kernel |
| 138 | directly, so you need some additional software which knows how to |
| 139 | talk to these devices using the SCSI protocol: |
| 140 | |
| 141 | For scanners, look at SANE (<http://www.sane-project.org/>). For CD |
| 142 | writer software look at Cdrtools |
| 143 | (<http://cdrtools.sourceforge.net/>) |
| 144 | and for burning a "disk at once": CDRDAO |
| 145 | (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high |
| 146 | quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>). |
| 147 | For other devices, it's possible that you'll have to write the |
| 148 | driver software yourself. Please read the file |
| 149 | <file:Documentation/scsi/scsi-generic.rst> for more information. |
| 150 | |
| 151 | To compile this driver as a module, choose M here and read |
| 152 | <file:Documentation/scsi/scsi.rst>. The module will be called sg. |
| 153 | |
| 154 | If unsure, say N. |
| 155 | |
| 156 | config BLK_DEV_BSG |
| 157 | bool "/dev/bsg support (SG v4)" |
| 158 | depends on SCSI |
| 159 | default y |
| 160 | help |
| 161 | Saying Y here will enable generic SG (SCSI generic) v4 support |
| 162 | for any SCSI device. |
| 163 | |
| 164 | This option is required by UDEV to access device serial numbers, etc. |
| 165 | |
| 166 | If unsure, say Y. |
| 167 | |
| 168 | config CHR_DEV_SCH |
| 169 | tristate "SCSI media changer support" |
| 170 | depends on SCSI |
| 171 | help |
| 172 | This is a driver for SCSI media changers. Most common devices are |
| 173 | tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you |
| 174 | don't need this for those tiny 6-slot cdrom changers. Media |
| 175 | changers are listed as "Type: Medium Changer" in /proc/scsi/scsi. |
| 176 | If you have such hardware and want to use it with linux, say Y |
| 177 | here. Check <file:Documentation/scsi/scsi-changer.rst> for details. |
| 178 | |
| 179 | If you want to compile this as a module ( = code which can be |
| 180 | inserted in and removed from the running kernel whenever you want), |
| 181 | say M here and read <file:Documentation/kbuild/modules.rst> and |
| 182 | <file:Documentation/scsi/scsi.rst>. The module will be called ch.o. |
| 183 | If unsure, say N. |
| 184 | |
| 185 | config SCSI_ENCLOSURE |
| 186 | tristate "SCSI Enclosure Support" |
| 187 | depends on SCSI && ENCLOSURE_SERVICES |
| 188 | depends on m || SCSI_SAS_ATTRS != m |
| 189 | help |
| 190 | Enclosures are devices sitting on or in SCSI backplanes that |
| 191 | manage devices. If you have a disk cage, the chances are that |
| 192 | it has an enclosure device. Selecting this option will just allow |
| 193 | certain enclosure conditions to be reported and is not required. |
| 194 | |
| 195 | config SCSI_CONSTANTS |
| 196 | bool "Verbose SCSI error reporting (kernel size += 36K)" |
| 197 | depends on SCSI |
| 198 | help |
| 199 | The error messages regarding your SCSI hardware will be easier to |
| 200 | understand if you say Y here; it will enlarge your kernel by about |
| 201 | 36 KB. If in doubt, say Y. |
| 202 | |
| 203 | config SCSI_LOGGING |
| 204 | bool "SCSI logging facility" |
| 205 | depends on SCSI |
| 206 | help |
| 207 | This turns on a logging facility that can be used to debug a number |
| 208 | of SCSI related problems. |
| 209 | |
| 210 | If you say Y here, no logging output will appear by default, but you |
| 211 | can enable logging by saying Y to "/proc file system support" and |
| 212 | "Sysctl support" below and executing the command |
| 213 | |
| 214 | echo <bitmask> > /proc/sys/dev/scsi/logging_level |
| 215 | |
| 216 | where <bitmask> is a four byte value representing the logging type |
| 217 | and logging level for each type of logging selected. |
| 218 | |
| 219 | There are a number of logging types and you can find them in the |
| 220 | source at <file:drivers/scsi/scsi_logging.h>. The logging levels |
| 221 | are also described in that file and they determine the verbosity of |
| 222 | the logging for each logging type. |
| 223 | |
| 224 | If you say N here, it may be harder to track down some types of SCSI |
| 225 | problems. If you say Y here your kernel will be somewhat larger, but |
| 226 | there should be no noticeable performance impact as long as you have |
| 227 | logging turned off. |
| 228 | |
| 229 | config SCSI_SCAN_ASYNC |
| 230 | bool "Asynchronous SCSI scanning" |
| 231 | depends on SCSI |
| 232 | help |
| 233 | The SCSI subsystem can probe for devices while the rest of the |
| 234 | system continues booting, and even probe devices on different |
| 235 | busses in parallel, leading to a significant speed-up. |
| 236 | |
| 237 | You can override this choice by specifying "scsi_mod.scan=sync" |
| 238 | or async on the kernel's command line. |
| 239 | |
| 240 | Note that this setting also affects whether resuming from |
| 241 | system suspend will be performed asynchronously. |
| 242 | |
| 243 | config SCSI_PROTO_TEST |
| 244 | tristate "scsi_proto.h unit tests" if !KUNIT_ALL_TESTS |
| 245 | depends on SCSI && KUNIT |
| 246 | default KUNIT_ALL_TESTS |
| 247 | |
| 248 | menu "SCSI Transports" |
| 249 | depends on SCSI |
| 250 | |
| 251 | config SCSI_SPI_ATTRS |
| 252 | tristate "Parallel SCSI (SPI) Transport Attributes" |
| 253 | depends on SCSI |
| 254 | help |
| 255 | If you wish to export transport-specific information about |
| 256 | each attached SCSI device to sysfs, say Y. Otherwise, say N. |
| 257 | |
| 258 | config SCSI_FC_ATTRS |
| 259 | tristate "FiberChannel Transport Attributes" |
| 260 | depends on SCSI && NET |
| 261 | select BLK_DEV_BSGLIB |
| 262 | select SCSI_NETLINK |
| 263 | help |
| 264 | If you wish to export transport-specific information about |
| 265 | each attached FiberChannel device to sysfs, say Y. |
| 266 | Otherwise, say N. |
| 267 | |
| 268 | config SCSI_ISCSI_ATTRS |
| 269 | tristate "iSCSI Transport Attributes" |
| 270 | depends on SCSI && NET |
| 271 | select BLK_DEV_BSGLIB |
| 272 | help |
| 273 | If you wish to export transport-specific information about |
| 274 | each attached iSCSI device to sysfs, say Y. |
| 275 | Otherwise, say N. |
| 276 | |
| 277 | config SCSI_SAS_ATTRS |
| 278 | tristate "SAS Transport Attributes" |
| 279 | depends on SCSI |
| 280 | select BLK_DEV_BSGLIB |
| 281 | help |
| 282 | If you wish to export transport-specific information about |
| 283 | each attached SAS device to sysfs, say Y. |
| 284 | |
| 285 | source "drivers/scsi/libsas/Kconfig" |
| 286 | |
| 287 | config SCSI_SRP_ATTRS |
| 288 | tristate "SRP Transport Attributes" |
| 289 | depends on SCSI |
| 290 | help |
| 291 | If you wish to export transport-specific information about |
| 292 | each attached SRP device to sysfs, say Y. |
| 293 | |
| 294 | endmenu |
| 295 | |
| 296 | menuconfig SCSI_LOWLEVEL |
| 297 | bool "SCSI low-level drivers" |
| 298 | depends on SCSI!=n |
| 299 | default y |
| 300 | |
| 301 | if SCSI_LOWLEVEL && SCSI |
| 302 | |
| 303 | config ISCSI_TCP |
| 304 | tristate "iSCSI Initiator over TCP/IP" |
| 305 | depends on SCSI && INET |
| 306 | select CRC32 |
| 307 | select SCSI_ISCSI_ATTRS |
| 308 | help |
| 309 | The iSCSI Driver provides a host with the ability to access storage |
| 310 | through an IP network. The driver uses the iSCSI protocol to transport |
| 311 | SCSI requests and responses over a TCP/IP network between the host |
| 312 | (the "initiator") and "targets". Architecturally, the iSCSI driver |
| 313 | combines with the host's TCP/IP stack, network drivers, and Network |
| 314 | Interface Card (NIC) to provide the same functions as a SCSI or a |
| 315 | Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA). |
| 316 | |
| 317 | To compile this driver as a module, choose M here: the |
| 318 | module will be called iscsi_tcp. |
| 319 | |
| 320 | The userspace component needed to initialize the driver, documentation, |
| 321 | and sample configuration files can be found here: |
| 322 | |
| 323 | http://open-iscsi.org |
| 324 | |
| 325 | config ISCSI_BOOT_SYSFS |
| 326 | tristate "iSCSI Boot Sysfs Interface" |
| 327 | default n |
| 328 | help |
| 329 | This option enables support for exposing iSCSI boot information |
| 330 | via sysfs to userspace. If you wish to export this information, |
| 331 | say Y. Otherwise, say N. |
| 332 | |
| 333 | source "drivers/scsi/cxgbi/Kconfig" |
| 334 | source "drivers/scsi/bnx2i/Kconfig" |
| 335 | source "drivers/scsi/bnx2fc/Kconfig" |
| 336 | source "drivers/scsi/be2iscsi/Kconfig" |
| 337 | |
| 338 | config SGIWD93_SCSI |
| 339 | tristate "SGI WD93C93 SCSI Driver" |
| 340 | depends on SGI_HAS_WD93 && SCSI |
| 341 | help |
| 342 | If you have a Western Digital WD93 SCSI controller on |
| 343 | an SGI MIPS system, say Y. Otherwise, say N. |
| 344 | |
| 345 | config BLK_DEV_3W_XXXX_RAID |
| 346 | tristate "3ware 5/6/7/8xxx ATA-RAID support" |
| 347 | depends on PCI && HAS_IOPORT && SCSI |
| 348 | help |
| 349 | 3ware is the only hardware ATA-Raid product in Linux to date. |
| 350 | This card is 2,4, or 8 channel master mode support only. |
| 351 | SCSI support required!!! |
| 352 | |
| 353 | <http://www.3ware.com/> |
| 354 | |
| 355 | Please read the comments at the top of |
| 356 | <file:drivers/scsi/3w-xxxx.c>. |
| 357 | |
| 358 | config SCSI_HPSA |
| 359 | tristate "HP Smart Array SCSI driver" |
| 360 | depends on PCI && SCSI |
| 361 | select CHECK_SIGNATURE |
| 362 | select SCSI_SAS_ATTRS |
| 363 | help |
| 364 | This driver supports HP Smart Array Controllers (circa 2009). |
| 365 | It is a SCSI alternative to the cciss driver, which is a block |
| 366 | driver. Anyone wishing to use HP Smart Array controllers who |
| 367 | would prefer the devices be presented to linux as SCSI devices, |
| 368 | rather than as generic block devices should say Y here. |
| 369 | |
| 370 | config SCSI_3W_9XXX |
| 371 | tristate "3ware 9xxx SATA-RAID support" |
| 372 | depends on PCI && SCSI |
| 373 | help |
| 374 | This driver supports the 9000 series 3ware SATA-RAID cards. |
| 375 | |
| 376 | <http://www.amcc.com> |
| 377 | |
| 378 | Please read the comments at the top of |
| 379 | <file:drivers/scsi/3w-9xxx.c>. |
| 380 | |
| 381 | config SCSI_3W_SAS |
| 382 | tristate "3ware 97xx SAS/SATA-RAID support" |
| 383 | depends on PCI && SCSI |
| 384 | help |
| 385 | This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards. |
| 386 | |
| 387 | <http://www.lsi.com> |
| 388 | |
| 389 | Please read the comments at the top of |
| 390 | <file:drivers/scsi/3w-sas.c>. |
| 391 | |
| 392 | config SCSI_ACARD |
| 393 | tristate "ACARD SCSI support" |
| 394 | depends on PCI && HAS_IOPORT && SCSI |
| 395 | help |
| 396 | This driver supports the ACARD SCSI host adapter. |
| 397 | Support Chip <ATP870 ATP876 ATP880 ATP885> |
| 398 | To compile this driver as a module, choose M here: the |
| 399 | module will be called atp870u. |
| 400 | |
| 401 | config SCSI_AHA152X |
| 402 | tristate "Adaptec AHA152X/2825 support" |
| 403 | depends on ISA && SCSI |
| 404 | depends on !HIGHMEM |
| 405 | select SCSI_SPI_ATTRS |
| 406 | select CHECK_SIGNATURE |
| 407 | help |
| 408 | This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825 |
| 409 | SCSI host adapters. It also works for the AVA-1505, but the IRQ etc. |
| 410 | must be manually specified in this case. |
| 411 | |
| 412 | It is explained in section 3.3 of the SCSI-HOWTO, available from |
| 413 | <http://www.tldp.org/docs.html#howto>. You might also want to |
| 414 | read the file <file:Documentation/scsi/aha152x.rst>. |
| 415 | |
| 416 | To compile this driver as a module, choose M here: the |
| 417 | module will be called aha152x. |
| 418 | |
| 419 | config SCSI_AHA1542 |
| 420 | tristate "Adaptec AHA1542 support" |
| 421 | depends on ISA && SCSI && ISA_DMA_API |
| 422 | help |
| 423 | This is support for a SCSI host adapter. It is explained in section |
| 424 | 3.4 of the SCSI-HOWTO, available from |
| 425 | <http://www.tldp.org/docs.html#howto>. Note that Trantor was |
| 426 | purchased by Adaptec, and some former Trantor products are being |
| 427 | sold under the Adaptec name. If it doesn't work out of the box, you |
| 428 | may have to change some settings in <file:drivers/scsi/aha1542.h>. |
| 429 | |
| 430 | To compile this driver as a module, choose M here: the |
| 431 | module will be called aha1542. |
| 432 | |
| 433 | config SCSI_AHA1740 |
| 434 | tristate "Adaptec AHA1740 support" |
| 435 | depends on EISA && SCSI |
| 436 | help |
| 437 | This is support for a SCSI host adapter. It is explained in section |
| 438 | 3.5 of the SCSI-HOWTO, available from |
| 439 | <http://www.tldp.org/docs.html#howto>. If it doesn't work out |
| 440 | of the box, you may have to change some settings in |
| 441 | <file:drivers/scsi/aha1740.h>. |
| 442 | |
| 443 | To compile this driver as a module, choose M here: the |
| 444 | module will be called aha1740. |
| 445 | |
| 446 | config SCSI_AACRAID |
| 447 | tristate "Adaptec AACRAID support" |
| 448 | depends on SCSI && PCI |
| 449 | help |
| 450 | This driver supports a variety of Dell, HP, Adaptec, IBM and |
| 451 | ICP storage products. For a list of supported products, refer |
| 452 | to <file:Documentation/scsi/aacraid.rst>. |
| 453 | |
| 454 | To compile this driver as a module, choose M here: the module |
| 455 | will be called aacraid. |
| 456 | |
| 457 | |
| 458 | source "drivers/scsi/aic7xxx/Kconfig.aic7xxx" |
| 459 | source "drivers/scsi/aic7xxx/Kconfig.aic79xx" |
| 460 | source "drivers/scsi/aic94xx/Kconfig" |
| 461 | source "drivers/scsi/hisi_sas/Kconfig" |
| 462 | source "drivers/scsi/mvsas/Kconfig" |
| 463 | |
| 464 | config SCSI_MVUMI |
| 465 | tristate "Marvell UMI driver" |
| 466 | depends on SCSI && PCI |
| 467 | help |
| 468 | Module for Marvell Universal Message Interface(UMI) driver |
| 469 | |
| 470 | To compile this driver as a module, choose M here: the |
| 471 | module will be called mvumi. |
| 472 | |
| 473 | config SCSI_ADVANSYS |
| 474 | tristate "AdvanSys SCSI support" |
| 475 | depends on SCSI |
| 476 | depends on (ISA || EISA || PCI) && HAS_IOPORT |
| 477 | help |
| 478 | This is a driver for all SCSI host adapters manufactured by |
| 479 | AdvanSys. It is documented in the kernel source in |
| 480 | <file:drivers/scsi/advansys.c>. |
| 481 | |
| 482 | To compile this driver as a module, choose M here: the |
| 483 | module will be called advansys. |
| 484 | |
| 485 | config SCSI_ARCMSR |
| 486 | tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter" |
| 487 | depends on PCI && SCSI |
| 488 | help |
| 489 | This driver supports all of ARECA's SATA/SAS RAID controller cards. |
| 490 | This is an ARECA-maintained driver by Erich Chen. |
| 491 | If you have any problems, please mail to: <[email protected]>. |
| 492 | Areca supports Linux RAID config tools. |
| 493 | Please link <http://www.areca.com.tw> |
| 494 | |
| 495 | To compile this driver as a module, choose M here: the |
| 496 | module will be called arcmsr (modprobe arcmsr). |
| 497 | |
| 498 | source "drivers/scsi/esas2r/Kconfig" |
| 499 | source "drivers/scsi/megaraid/Kconfig.megaraid" |
| 500 | source "drivers/scsi/mpt3sas/Kconfig" |
| 501 | source "drivers/scsi/mpi3mr/Kconfig" |
| 502 | source "drivers/scsi/leapraid/Kconfig" |
| 503 | source "drivers/scsi/smartpqi/Kconfig" |
| 504 | |
| 505 | config SCSI_HPTIOP |
| 506 | tristate "HighPoint RocketRAID 3xxx/4xxx Controller support" |
| 507 | depends on SCSI && PCI |
| 508 | help |
| 509 | This option enables support for HighPoint RocketRAID 3xxx/4xxx |
| 510 | controllers. |
| 511 | |
| 512 | To compile this driver as a module, choose M here; the module |
| 513 | will be called hptiop. If unsure, say N. |
| 514 | |
| 515 | config SCSI_BUSLOGIC |
| 516 | tristate "BusLogic SCSI support" |
| 517 | depends on SCSI && PCI && HAS_IOPORT |
| 518 | help |
| 519 | This is support for BusLogic MultiMaster and FlashPoint SCSI Host |
| 520 | Adapters. Consult the SCSI-HOWTO, available from |
| 521 | <http://www.tldp.org/docs.html#howto>, and the files |
| 522 | <file:Documentation/scsi/BusLogic.rst> and |
| 523 | <file:Documentation/scsi/FlashPoint.rst> for more information. |
| 524 | Note that support for FlashPoint is only available for 32-bit |
| 525 | x86 configurations. |
| 526 | |
| 527 | To compile this driver as a module, choose M here: the |
| 528 | module will be called BusLogic. |
| 529 | |
| 530 | config SCSI_FLASHPOINT |
| 531 | bool "FlashPoint support" |
| 532 | depends on SCSI_BUSLOGIC && PCI && HAS_IOPORT |
| 533 | help |
| 534 | This option allows you to add FlashPoint support to the |
| 535 | BusLogic SCSI driver. The FlashPoint SCCB Manager code is |
| 536 | substantial, so users of MultiMaster Host Adapters may not |
| 537 | wish to include it. |
| 538 | |
| 539 | config SCSI_MYRB |
| 540 | tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)" |
| 541 | depends on PCI |
| 542 | select RAID_ATTRS |
| 543 | help |
| 544 | This driver adds support for the Mylex DAC960, AcceleRAID, and |
| 545 | eXtremeRAID PCI RAID controllers. This driver supports the |
| 546 | older, block based interface. |
| 547 | This driver is a reimplementation of the original DAC960 |
| 548 | driver. If you have used the DAC960 driver you should enable |
| 549 | this module. |
| 550 | |
| 551 | To compile this driver as a module, choose M here: the |
| 552 | module will be called myrb. |
| 553 | |
| 554 | config SCSI_MYRS |
| 555 | tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)" |
| 556 | depends on PCI |
| 557 | depends on !CPU_BIG_ENDIAN || COMPILE_TEST |
| 558 | select RAID_ATTRS |
| 559 | help |
| 560 | This driver adds support for the Mylex DAC960, AcceleRAID, and |
| 561 | eXtremeRAID PCI RAID controllers. This driver supports the |
| 562 | newer, SCSI-based interface only. |
| 563 | This driver is a reimplementation of the original DAC960 |
| 564 | driver. If you have used the DAC960 driver you should enable |
| 565 | this module. |
| 566 | |
| 567 | To compile this driver as a module, choose M here: the |
| 568 | module will be called myrs. |
| 569 | |
| 570 | config VMWARE_PVSCSI |
| 571 | tristate "VMware PVSCSI driver support" |
| 572 | depends on PCI && SCSI && X86 |
| 573 | help |
| 574 | This driver supports VMware's para virtualized SCSI HBA. |
| 575 | To compile this driver as a module, choose M here: the |
| 576 | module will be called vmw_pvscsi. |
| 577 | |
| 578 | config XEN_SCSI_FRONTEND |
| 579 | tristate "XEN SCSI frontend driver" |
| 580 | depends on SCSI && XEN |
| 581 | select XEN_XENBUS_FRONTEND |
| 582 | help |
| 583 | The XEN SCSI frontend driver allows the kernel to access SCSI Devices |
| 584 | within another guest OS (usually Dom0). |
| 585 | Only needed if the kernel is running in a XEN guest and generic |
| 586 | SCSI access to a device is needed. |
| 587 | |
| 588 | config HYPERV_STORAGE |
| 589 | tristate "Microsoft Hyper-V virtual storage driver" |
| 590 | depends on SCSI && HYPERV_VMBUS |
| 591 | depends on m || SCSI_FC_ATTRS != m |
| 592 | default HYPERV |
| 593 | help |
| 594 | Select this option to enable the Hyper-V virtual storage driver. |
| 595 | |
| 596 | config LIBFC |
| 597 | tristate "LibFC module" |
| 598 | depends on SCSI_FC_ATTRS |
| 599 | select CRC32 |
| 600 | help |
| 601 | Fibre Channel library module |
| 602 | |
| 603 | config LIBFCOE |
| 604 | tristate "LibFCoE module" |
| 605 | depends on LIBFC |
| 606 | help |
| 607 | Library for Fibre Channel over Ethernet module |
| 608 | |
| 609 | config FCOE |
| 610 | tristate "FCoE module" |
| 611 | depends on PCI |
| 612 | depends on LIBFCOE |
| 613 | help |
| 614 | Fibre Channel over Ethernet module |
| 615 | |
| 616 | config FCOE_FNIC |
| 617 | tristate "Cisco FNIC Driver" |
| 618 | depends on PCI && X86 |
| 619 | depends on LIBFCOE |
| 620 | help |
| 621 | This is support for the Cisco PCI-Express FCoE HBA. |
| 622 | |
| 623 | To compile this driver as a module, choose M here and read |
| 624 | <file:Documentation/scsi/scsi.rst>. |
| 625 | The module will be called fnic. |
| 626 | |
| 627 | config SCSI_SNIC |
| 628 | tristate "Cisco SNIC Driver" |
| 629 | depends on PCI && SCSI |
| 630 | help |
| 631 | This is support for the Cisco PCI-Express SCSI HBA. |
| 632 | |
| 633 | To compile this driver as a module, choose M here and read |
| 634 | <file:Documentation/scsi/scsi.rst>. |
| 635 | The module will be called snic. |
| 636 | |
| 637 | config SCSI_SNIC_DEBUG_FS |
| 638 | bool "Cisco SNIC Driver Debugfs Support" |
| 639 | depends on SCSI_SNIC && DEBUG_FS |
| 640 | help |
| 641 | This enables to list debugging information from SNIC Driver |
| 642 | available via debugfs file system |
| 643 | |
| 644 | config SCSI_DMX3191D |
| 645 | tristate "DMX3191D SCSI support" |
| 646 | depends on PCI && HAS_IOPORT && SCSI |
| 647 | select SCSI_SPI_ATTRS |
| 648 | help |
| 649 | This is support for Domex DMX3191D SCSI Host Adapters. |
| 650 | |
| 651 | To compile this driver as a module, choose M here: the |
| 652 | module will be called dmx3191d. |
| 653 | |
| 654 | config SCSI_FDOMAIN |
| 655 | tristate |
| 656 | depends on SCSI |
| 657 | |
| 658 | config SCSI_FDOMAIN_PCI |
| 659 | tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support" |
| 660 | depends on PCI && HAS_IOPORT && SCSI |
| 661 | select SCSI_FDOMAIN |
| 662 | help |
| 663 | This is support for Future Domain's PCI SCSI host adapters (TMC-3260) |
| 664 | and other adapters with PCI bus based on the Future Domain chipsets |
| 665 | (Adaptec AHA-2920A). |
| 666 | |
| 667 | NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip |
| 668 | and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI |
| 669 | controller support"). This Future Domain driver works with the older |
| 670 | Adaptec AHA-2920A boards with a Future Domain chip on them. |
| 671 | |
| 672 | To compile this driver as a module, choose M here: the |
| 673 | module will be called fdomain_pci. |
| 674 | |
| 675 | config SCSI_FDOMAIN_ISA |
| 676 | tristate "Future Domain 16xx ISA SCSI support" |
| 677 | depends on ISA && SCSI |
| 678 | select CHECK_SIGNATURE |
| 679 | select SCSI_FDOMAIN |
| 680 | help |
| 681 | This is support for Future Domain's 16-bit SCSI host adapters |
| 682 | (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters |
| 683 | with ISA bus based on the Future Domain chipsets (Quantum ISA-200S, |
| 684 | ISA-250MG; and at least one IBM board). |
| 685 | |
| 686 | To compile this driver as a module, choose M here: the |
| 687 | module will be called fdomain_isa. |
| 688 | |
| 689 | config SCSI_ISCI |
| 690 | tristate "Intel(R) C600 Series Chipset SAS Controller" |
| 691 | depends on PCI && SCSI |
| 692 | depends on X86 |
| 693 | select SCSI_SAS_LIBSAS |
| 694 | help |
| 695 | This driver supports the 6Gb/s SAS capabilities of the storage |
| 696 | control unit found in the Intel(R) C600 series chipset. |
| 697 | |
| 698 | config SCSI_GENERIC_NCR5380 |
| 699 | tristate "Generic NCR5380/53c400 SCSI ISA card support" |
| 700 | depends on ISA && SCSI && HAS_IOPORT_MAP |
| 701 | select SCSI_SPI_ATTRS |
| 702 | help |
| 703 | This is a driver for old ISA card SCSI controllers based on a |
| 704 | NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device. |
| 705 | Most boards such as the Trantor T130 fit this category, as do |
| 706 | various 8-bit and 16-bit ISA cards bundled with SCSI scanners. |
| 707 | |
| 708 | To compile this driver as a module, choose M here: the |
| 709 | module will be called g_NCR5380. |
| 710 | |
| 711 | config SCSI_IPS |
| 712 | tristate "IBM ServeRAID support" |
| 713 | depends on PCI && HAS_IOPORT && SCSI |
| 714 | help |
| 715 | This is support for the IBM ServeRAID hardware RAID controllers. |
| 716 | See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html> |
| 717 | and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID> |
| 718 | for more information. If this driver does not work correctly |
| 719 | without modification please contact the author by email at |
| 720 | <[email protected]>. |
| 721 | |
| 722 | To compile this driver as a module, choose M here: the |
| 723 | module will be called ips. |
| 724 | |
| 725 | config SCSI_IBMVSCSI |
| 726 | tristate "IBM Virtual SCSI support" |
| 727 | depends on PPC_PSERIES |
| 728 | select SCSI_SRP_ATTRS |
| 729 | help |
| 730 | This is the IBM POWER Virtual SCSI Client |
| 731 | |
| 732 | To compile this driver as a module, choose M here: the |
| 733 | module will be called ibmvscsi. |
| 734 | |
| 735 | config SCSI_IBMVSCSIS |
| 736 | tristate "IBM Virtual SCSI Server support" |
| 737 | depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI |
| 738 | help |
| 739 | This is the IBM POWER Virtual SCSI Target Server |
| 740 | This driver uses the SRP protocol for communication between servers |
| 741 | guest and/or the host that run on the same server. |
| 742 | More information on VSCSI protocol can be found at www.power.org |
| 743 | |
| 744 | The userspace configuration needed to initialize the driver can be |
| 745 | be found here: |
| 746 | |
| 747 | https://github.com/powervm/ibmvscsis/wiki/Configuration |
| 748 | |
| 749 | To compile this driver as a module, choose M here: the |
| 750 | module will be called ibmvscsis. |
| 751 | |
| 752 | config SCSI_IBMVFC |
| 753 | tristate "IBM Virtual FC support" |
| 754 | depends on PPC_PSERIES && SCSI |
| 755 | depends on SCSI_FC_ATTRS |
| 756 | depends on NVME_FC || NVME_FC=n |
| 757 | help |
| 758 | This is the IBM POWER Virtual FC Client |
| 759 | |
| 760 | To compile this driver as a module, choose M here: the |
| 761 | module will be called ibmvfc. |
| 762 | |
| 763 | config SCSI_IBMVFC_TRACE |
| 764 | bool "enable driver internal trace" |
| 765 | depends on SCSI_IBMVFC |
| 766 | default y |
| 767 | help |
| 768 | If you say Y here, the driver will trace all commands issued |
| 769 | to the adapter. Performance impact is minimal. Trace can be |
| 770 | dumped using /sys/class/scsi_host/hostXX/trace. |
| 771 | |
| 772 | config SCSI_INITIO |
| 773 | tristate "Initio 9100U(W) support" |
| 774 | depends on PCI && HAS_IOPORT && SCSI |
| 775 | help |
| 776 | This is support for the Initio 91XXU(W) SCSI host adapter. Please |
| 777 | read the SCSI-HOWTO, available from |
| 778 | <http://www.tldp.org/docs.html#howto>. |
| 779 | |
| 780 | To compile this driver as a module, choose M here: the |
| 781 | module will be called initio. |
| 782 | |
| 783 | config SCSI_INIA100 |
| 784 | tristate "Initio INI-A100U2W support" |
| 785 | depends on PCI && HAS_IOPORT && SCSI |
| 786 | help |
| 787 | This is support for the Initio INI-A100U2W SCSI host adapter. |
| 788 | Please read the SCSI-HOWTO, available from |
| 789 | <http://www.tldp.org/docs.html#howto>. |
| 790 | |
| 791 | To compile this driver as a module, choose M here: the |
| 792 | module will be called a100u2w. |
| 793 | |
| 794 | config SCSI_PPA |
| 795 | tristate "IOMEGA parallel port (ppa - older drives)" |
| 796 | depends on SCSI && PARPORT_PC |
| 797 | depends on HAS_IOPORT |
| 798 | depends on !HIGHMEM |
| 799 | help |
| 800 | This driver supports older versions of IOMEGA's parallel port ZIP |
| 801 | drive (a 100 MB removable media device). |
| 802 | |
| 803 | Note that you can say N here if you have the SCSI version of the ZIP |
| 804 | drive: it will be supported automatically if you said Y to the |
| 805 | generic "SCSI disk support", above. |
| 806 | |
| 807 | If you have the ZIP Plus drive or a more recent parallel port ZIP |
| 808 | drive (if the supplied cable with the drive is labeled "AutoDetect") |
| 809 | then you should say N here and Y to "IOMEGA parallel port (imm - |
| 810 | newer drives)", below. |
| 811 | |
| 812 | For more information about this driver and how to use it you should |
| 813 | read the file <file:Documentation/scsi/ppa.rst>. You should also read |
| 814 | the SCSI-HOWTO, which is available from |
| 815 | <http://www.tldp.org/docs.html#howto>. If you use this driver, |
| 816 | you will still be able to use the parallel port for other tasks, |
| 817 | such as a printer; it is safe to compile both drivers into the |
| 818 | kernel. |
| 819 | |
| 820 | To compile this driver as a module, choose M here: the |
| 821 | module will be called ppa. |
| 822 | |
| 823 | config SCSI_IMM |
| 824 | tristate "IOMEGA parallel port (imm - newer drives)" |
| 825 | depends on SCSI && PARPORT_PC |
| 826 | depends on !HIGHMEM |
| 827 | help |
| 828 | This driver supports newer versions of IOMEGA's parallel port ZIP |
| 829 | drive (a 100 MB removable media device). |
| 830 | |
| 831 | Note that you can say N here if you have the SCSI version of the ZIP |
| 832 | drive: it will be supported automatically if you said Y to the |
| 833 | generic "SCSI disk support", above. |
| 834 | |
| 835 | If you have the ZIP Plus drive or a more recent parallel port ZIP |
| 836 | drive (if the supplied cable with the drive is labeled "AutoDetect") |
| 837 | then you should say Y here; if you have an older ZIP drive, say N |
| 838 | here and Y to "IOMEGA Parallel Port (ppa - older drives)", above. |
| 839 | |
| 840 | For more information about this driver and how to use it you should |
| 841 | read the file <file:Documentation/scsi/ppa.rst>. You should also read |
| 842 | the SCSI-HOWTO, which is available from |
| 843 | <http://www.tldp.org/docs.html#howto>. If you use this driver, |
| 844 | you will still be able to use the parallel port for other tasks, |
| 845 | such as a printer; it is safe to compile both drivers into the |
| 846 | kernel. |
| 847 | |
| 848 | To compile this driver as a module, choose M here: the |
| 849 | module will be called imm. |
| 850 | |
| 851 | config SCSI_IZIP_SLOW_CTR |
| 852 | bool "ppa/imm option - Assume slow parport control register" |
| 853 | depends on SCSI_PPA || SCSI_IMM |
| 854 | help |
| 855 | Some parallel ports are known to have excessive delays between |
| 856 | changing the parallel port control register and good data being |
| 857 | available on the parallel port data/status register. This option |
| 858 | forces a small delay (1.0 usec to be exact) after changing the |
| 859 | control register to let things settle out. Enabling this option may |
| 860 | result in a big drop in performance but some very old parallel ports |
| 861 | (found in 386 vintage machines) will not work properly. |
| 862 | |
| 863 | Generally, saying N is fine. |
| 864 | |
| 865 | config SCSI_LASI700 |
| 866 | tristate "HP Lasi SCSI support for 53c700/710" |
| 867 | depends on GSC && SCSI |
| 868 | select SCSI_SPI_ATTRS |
| 869 | help |
| 870 | This is a driver for the SCSI controller in the Lasi chip found in |
| 871 | many PA-RISC workstations & servers. If you do not know whether you |
| 872 | have a Lasi chip, it is safe to say "Y" here. |
| 873 | |
| 874 | config SCSI_SNI_53C710 |
| 875 | tristate "SNI RM SCSI support for 53c710" |
| 876 | depends on SNI_RM && SCSI |
| 877 | select SCSI_SPI_ATTRS |
| 878 | select 53C700_LE_ON_BE |
| 879 | help |
| 880 | This is a driver for the onboard SCSI controller found in older |
| 881 | SNI RM workstations & servers. |
| 882 | |
| 883 | config 53C700_LE_ON_BE |
| 884 | bool |
| 885 | depends on SCSI_LASI700 || SCSI_SNI_53C710 |
| 886 | default y |
| 887 | |
| 888 | config SCSI_STEX |
| 889 | tristate "Promise SuperTrak EX Series support" |
| 890 | depends on PCI && SCSI |
| 891 | help |
| 892 | This driver supports Promise SuperTrak EX series storage controllers. |
| 893 | |
| 894 | Promise provides Linux RAID configuration utility for these |
| 895 | controllers. Please visit <http://www.promise.com> to download. |
| 896 | |
| 897 | To compile this driver as a module, choose M here: the |
| 898 | module will be called stex. |
| 899 | |
| 900 | config 53C700_BE_BUS |
| 901 | bool |
| 902 | depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI |
| 903 | default y |
| 904 | |
| 905 | config SCSI_SYM53C8XX_2 |
| 906 | tristate "SYM53C8XX Version 2 SCSI support" |
| 907 | depends on PCI && SCSI |
| 908 | select SCSI_SPI_ATTRS |
| 909 | help |
| 910 | This driver supports the whole NCR53C8XX/SYM53C8XX family of |
| 911 | PCI-SCSI controllers. It also supports the subset of LSI53C10XX |
| 912 | Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS |
| 913 | language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI |
| 914 | controllers; you need to use the Fusion MPT driver for that. |
| 915 | |
| 916 | Please read <file:Documentation/scsi/sym53c8xx_2.rst> for more |
| 917 | information. |
| 918 | |
| 919 | config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE |
| 920 | int "DMA addressing mode" |
| 921 | depends on SCSI_SYM53C8XX_2 |
| 922 | default "1" |
| 923 | help |
| 924 | This option only applies to PCI-SCSI chips that are PCI DAC |
| 925 | capable (875A, 895A, 896, 1010-33, 1010-66, 1000). |
| 926 | |
| 927 | When set to 0, the driver will program the chip to only perform |
| 928 | 32-bit DMA. When set to 1, the chip will be able to perform DMA |
| 929 | to addresses up to 1TB. When set to 2, the driver supports the |
| 930 | full 64-bit DMA address range, but can only address 16 segments |
| 931 | of 4 GB each. This limits the total addressable range to 64 GB. |
| 932 | |
| 933 | Most machines with less than 4GB of memory should use a setting |
| 934 | of 0 for best performance. If your machine has 4GB of memory |
| 935 | or more, you should set this option to 1 (the default). |
| 936 | |
| 937 | The still experimental value 2 (64 bit DMA addressing with 16 |
| 938 | x 4GB segments limitation) can be used on systems that require |
| 939 | PCI address bits past bit 39 to be set for the addressing of |
| 940 | memory using PCI DAC cycles. |
| 941 | |
| 942 | config SCSI_SYM53C8XX_DEFAULT_TAGS |
| 943 | int "Default tagged command queue depth" |
| 944 | depends on SCSI_SYM53C8XX_2 |
| 945 | default "16" |
| 946 | help |
| 947 | This is the default value of the command queue depth the |
| 948 | driver will announce to the generic SCSI layer for devices |
| 949 | that support tagged command queueing. This value can be changed |
| 950 | from the boot command line. This is a soft limit that cannot |
| 951 | exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS. |
| 952 | |
| 953 | config SCSI_SYM53C8XX_MAX_TAGS |
| 954 | int "Maximum number of queued commands" |
| 955 | depends on SCSI_SYM53C8XX_2 |
| 956 | default "64" |
| 957 | help |
| 958 | This option allows you to specify the maximum number of commands |
| 959 | that can be queued to any device, when tagged command queuing is |
| 960 | possible. The driver supports up to 256 queued commands per device. |
| 961 | This value is used as a compiled-in hard limit. |
| 962 | |
| 963 | config SCSI_SYM53C8XX_MMIO |
| 964 | bool "Use memory mapped IO" |
| 965 | depends on SCSI_SYM53C8XX_2 |
| 966 | default y |
| 967 | help |
| 968 | Memory mapped IO is faster than Port IO. Most people should |
| 969 | answer Y here, but some machines may have problems. If you have |
| 970 | to answer N here, please report the problem to the maintainer. |
| 971 | |
| 972 | config SCSI_IPR |
| 973 | tristate "IBM Power Linux RAID adapter support" |
| 974 | depends on PCI && SCSI |
| 975 | select FW_LOADER |
| 976 | select IRQ_POLL |
| 977 | select SGL_ALLOC |
| 978 | help |
| 979 | This driver supports the IBM Power Linux family RAID adapters. |
| 980 | This includes IBM pSeries 5712, 5703, 5709, and 570A, as well |
| 981 | as IBM iSeries 5702, 5703, 5709, and 570A. |
| 982 | |
| 983 | config SCSI_IPR_TRACE |
| 984 | bool "enable driver internal trace" |
| 985 | depends on SCSI_IPR |
| 986 | default y |
| 987 | help |
| 988 | If you say Y here, the driver will trace all commands issued |
| 989 | to the adapter. Performance impact is minimal. Trace can be |
| 990 | dumped using /sys/bus/class/scsi_host/hostXX/trace. |
| 991 | |
| 992 | config SCSI_IPR_DUMP |
| 993 | bool "enable adapter dump support" |
| 994 | depends on SCSI_IPR |
| 995 | default y |
| 996 | help |
| 997 | If you say Y here, the driver will support adapter crash dump. |
| 998 | If you enable this support, the iprdump daemon can be used |
| 999 | to capture adapter failure analysis information. |
| 1000 | |
| 1001 | config SCSI_ZALON |
| 1002 | tristate "Zalon SCSI support" |
| 1003 | depends on GSC && SCSI |
| 1004 | select SCSI_SPI_ATTRS |
| 1005 | help |
| 1006 | The Zalon is a GSC/HSC bus interface chip that sits between the |
| 1007 | PA-RISC processor and the NCR 53c720 SCSI controller on C100, |
| 1008 | C110, J200, J210 and some D, K & R-class machines. It's also |
| 1009 | used on the add-in Bluefish, Barracuda & Shrike SCSI cards. |
| 1010 | Say Y here if you have one of these machines or cards. |
| 1011 | |
| 1012 | config SCSI_NCR53C8XX_DEFAULT_TAGS |
| 1013 | int "default tagged command queue depth" |
| 1014 | depends on SCSI_ZALON |
| 1015 | default "8" |
| 1016 | help |
| 1017 | "Tagged command queuing" is a feature of SCSI-2 which improves |
| 1018 | performance: the host adapter can send several SCSI commands to a |
| 1019 | device's queue even if previous commands haven't finished yet. |
| 1020 | Because the device is intelligent, it can optimize its operations |
| 1021 | (like head positioning) based on its own request queue. Some SCSI |
| 1022 | devices don't implement this properly; if you want to disable this |
| 1023 | feature, enter 0 or 1 here (it doesn't matter which). |
| 1024 | |
| 1025 | The default value is 8 and should be supported by most hard disks. |
| 1026 | This value can be overridden from the boot command line using the |
| 1027 | 'tags' option as follows (example): |
| 1028 | 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to |
| 1029 | 4, set queue depth to 16 for target 2 and target 3 on controller 0 |
| 1030 | and set queue depth to 10 for target 0 / lun 2 on controller 1. |
| 1031 | |
| 1032 | The normal answer therefore is to go with the default 8 and to use |
| 1033 | a boot command line option for devices that need to use a different |
| 1034 | command queue depth. |
| 1035 | |
| 1036 | There is no safe option other than using good SCSI devices. |
| 1037 | |
| 1038 | config SCSI_NCR53C8XX_MAX_TAGS |
| 1039 | int "maximum number of queued commands" |
| 1040 | depends on SCSI_ZALON |
| 1041 | default "32" |
| 1042 | help |
| 1043 | This option allows you to specify the maximum number of commands |
| 1044 | that can be queued to any device, when tagged command queuing is |
| 1045 | possible. The default value is 32. Minimum is 2, maximum is 64. |
| 1046 | Modern hard disks are able to support 64 tags and even more, but |
| 1047 | do not seem to be faster when more than 32 tags are being used. |
| 1048 | |
| 1049 | So, the normal answer here is to go with the default value 32 unless |
| 1050 | you are using very large hard disks with large cache (>= 1 MB) that |
| 1051 | are able to take advantage of more than 32 tagged commands. |
| 1052 | |
| 1053 | There is no safe option and the default answer is recommended. |
| 1054 | |
| 1055 | config SCSI_NCR53C8XX_SYNC |
| 1056 | int "synchronous transfers frequency in MHz" |
| 1057 | depends on SCSI_ZALON |
| 1058 | default "20" |
| 1059 | help |
| 1060 | The SCSI Parallel Interface-2 Standard defines 5 classes of transfer |
| 1061 | rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers |
| 1062 | are respectively the maximum data transfer rates in mega-transfers |
| 1063 | per second for each class. For example, a FAST-20 Wide 16 device is |
| 1064 | able to transfer data at 20 million 16 bit packets per second for a |
| 1065 | total rate of 40 MB/s. |
| 1066 | |
| 1067 | You may specify 0 if you want to only use asynchronous data |
| 1068 | transfers. This is the safest and slowest option. Otherwise, specify |
| 1069 | a value between 5 and 80, depending on the capability of your SCSI |
| 1070 | controller. The higher the number, the faster the data transfer. |
| 1071 | Note that 80 should normally be ok since the driver decreases the |
| 1072 | value automatically according to the controller's capabilities. |
| 1073 | |
| 1074 | Your answer to this question is ignored for controllers with NVRAM, |
| 1075 | since the driver will get this information from the user set-up. It |
| 1076 | also can be overridden using a boot setup option, as follows |
| 1077 | (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate |
| 1078 | for FAST-20 synchronous data transfer (20 mega-transfers per |
| 1079 | second). |
| 1080 | |
| 1081 | The normal answer therefore is not to go with the default but to |
| 1082 | select the maximum value 80 allowing the driver to use the maximum |
| 1083 | value supported by each controller. If this causes problems with |
| 1084 | your SCSI devices, you should come back and decrease the value. |
| 1085 | |
| 1086 | There is no safe option other than using good cabling, right |
| 1087 | terminations and SCSI conformant devices. |
| 1088 | |
| 1089 | config SCSI_NCR53C8XX_NO_DISCONNECT |
| 1090 | bool "not allow targets to disconnect" |
| 1091 | depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0 |
| 1092 | help |
| 1093 | This option is only provided for safety if you suspect some SCSI |
| 1094 | device of yours to not support properly the target-disconnect |
| 1095 | feature. In that case, you would say Y here. In general however, to |
| 1096 | not allow targets to disconnect is not reasonable if there is more |
| 1097 | than 1 device on a SCSI bus. The normal answer therefore is N. |
| 1098 | |
| 1099 | config SCSI_QLOGIC_FAS |
| 1100 | tristate "Qlogic FAS SCSI support" |
| 1101 | depends on ISA && SCSI |
| 1102 | help |
| 1103 | This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic |
| 1104 | FastSCSI! cards as well as any other card based on the FASXX chip |
| 1105 | (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards). |
| 1106 | |
| 1107 | This driver does NOT support the PCI versions of these cards. The |
| 1108 | PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP |
| 1109 | SCSI support"), below. |
| 1110 | |
| 1111 | Information about this driver is contained in |
| 1112 | <file:Documentation/scsi/qlogicfas.rst>. You should also read the |
| 1113 | SCSI-HOWTO, available from |
| 1114 | <http://www.tldp.org/docs.html#howto>. |
| 1115 | |
| 1116 | To compile this driver as a module, choose M here: the |
| 1117 | module will be called qlogicfas. |
| 1118 | |
| 1119 | config SCSI_QLOGIC_1280 |
| 1120 | tristate "Qlogic QLA 1240/1x80/1x160 SCSI support" |
| 1121 | depends on PCI && SCSI |
| 1122 | help |
| 1123 | Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter. |
| 1124 | |
| 1125 | To compile this driver as a module, choose M here: the |
| 1126 | module will be called qla1280. |
| 1127 | |
| 1128 | config SCSI_QLOGICPTI |
| 1129 | tristate "PTI Qlogic, ISP Driver" |
| 1130 | depends on SBUS && SCSI |
| 1131 | help |
| 1132 | This driver supports SBUS SCSI controllers from PTI or QLogic. These |
| 1133 | controllers are known under Solaris as qpti and in the openprom as |
| 1134 | PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are |
| 1135 | driven by a different driver. |
| 1136 | |
| 1137 | To compile this driver as a module, choose M here: the |
| 1138 | module will be called qlogicpti. |
| 1139 | |
| 1140 | source "drivers/scsi/qla2xxx/Kconfig" |
| 1141 | source "drivers/scsi/qla4xxx/Kconfig" |
| 1142 | source "drivers/scsi/qedi/Kconfig" |
| 1143 | source "drivers/scsi/qedf/Kconfig" |
| 1144 | |
| 1145 | config SCSI_LPFC |
| 1146 | tristate "Emulex LightPulse Fibre Channel Support" |
| 1147 | depends on PCI && SCSI |
| 1148 | depends on CPU_FREQ |
| 1149 | depends on SCSI_FC_ATTRS |
| 1150 | depends on NVME_TARGET_FC || NVME_TARGET_FC=n |
| 1151 | depends on NVME_FC || NVME_FC=n |
| 1152 | select CRC_T10DIF |
| 1153 | select CRC32 |
| 1154 | select IRQ_POLL |
| 1155 | help |
| 1156 | This lpfc driver supports the Emulex LightPulse |
| 1157 | Family of Fibre Channel PCI host adapters. |
| 1158 | |
| 1159 | config SCSI_LPFC_DEBUG_FS |
| 1160 | bool "Emulex LightPulse Fibre Channel debugfs Support" |
| 1161 | depends on SCSI_LPFC && DEBUG_FS |
| 1162 | help |
| 1163 | This makes debugging information from the lpfc driver |
| 1164 | available via the debugfs filesystem. |
| 1165 | |
| 1166 | source "drivers/scsi/elx/Kconfig" |
| 1167 | |
| 1168 | config SCSI_SIM710 |
| 1169 | tristate "Simple 53c710 SCSI support (Compaq, NCR machines)" |
| 1170 | depends on EISA && SCSI |
| 1171 | select SCSI_SPI_ATTRS |
| 1172 | help |
| 1173 | This driver is for NCR53c710 based SCSI host adapters. |
| 1174 | |
| 1175 | It currently supports Compaq EISA cards. |
| 1176 | |
| 1177 | config SCSI_DC395x |
| 1178 | tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support" |
| 1179 | depends on PCI && HAS_IOPORT && SCSI |
| 1180 | select SCSI_SPI_ATTRS |
| 1181 | help |
| 1182 | This driver supports PCI SCSI host adapters based on the ASIC |
| 1183 | TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants. |
| 1184 | |
| 1185 | This driver works, but is still in experimental status. So better |
| 1186 | have a bootable disk and a backup in case of emergency. |
| 1187 | |
| 1188 | Documentation can be found in <file:Documentation/scsi/dc395x.rst>. |
| 1189 | |
| 1190 | To compile this driver as a module, choose M here: the |
| 1191 | module will be called dc395x. |
| 1192 | |
| 1193 | config SCSI_AM53C974 |
| 1194 | tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)" |
| 1195 | depends on PCI && SCSI |
| 1196 | select SCSI_SPI_ATTRS |
| 1197 | help |
| 1198 | This driver supports PCI SCSI host adapters based on the Am53C974A |
| 1199 | chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard |
| 1200 | PCscsi/PCnet (Am53/79C974) solutions. |
| 1201 | This is a new implementation base on the generic esp_scsi driver. |
| 1202 | |
| 1203 | Note that this driver does NOT support Tekram DC390W/U/F, which are |
| 1204 | based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those. |
| 1205 | |
| 1206 | To compile this driver as a module, choose M here: the |
| 1207 | module will be called am53c974. |
| 1208 | |
| 1209 | config SCSI_NSP32 |
| 1210 | tristate "Workbit NinjaSCSI-32Bi/UDE support" |
| 1211 | depends on PCI && SCSI && !64BIT && HAS_IOPORT |
| 1212 | help |
| 1213 | This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus |
| 1214 | SCSI host adapter. Please read the SCSI-HOWTO, available from |
| 1215 | <http://www.tldp.org/docs.html#howto>. |
| 1216 | |
| 1217 | To compile this driver as a module, choose M here: the |
| 1218 | module will be called nsp32. |
| 1219 | |
| 1220 | config SCSI_WD719X |
| 1221 | tristate "Western Digital WD7193/7197/7296 support" |
| 1222 | depends on PCI && SCSI |
| 1223 | select EEPROM_93CX6 |
| 1224 | help |
| 1225 | This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI |
| 1226 | SCSI controllers (based on WD33C296A chip). |
| 1227 | |
| 1228 | config SCSI_DEBUG |
| 1229 | tristate "SCSI debugging host and device simulator" |
| 1230 | depends on SCSI |
| 1231 | select CRC_T10DIF |
| 1232 | help |
| 1233 | This pseudo driver simulates one or more hosts (SCSI initiators), |
| 1234 | each with one or more targets, each with one or more logical units. |
| 1235 | Defaults to one of each, creating a small RAM disk device. Many |
| 1236 | parameters found in the /sys/bus/pseudo/drivers/scsi_debug |
| 1237 | directory can be tweaked at run time. |
| 1238 | See <http://sg.danny.cz/sg/sdebug26.html> for more information. |
| 1239 | Mainly used for testing and best as a module. If unsure, say N. |
| 1240 | |
| 1241 | config SCSI_MESH |
| 1242 | tristate "MESH (Power Mac internal SCSI) support" |
| 1243 | depends on PPC32 && PPC_PMAC && SCSI |
| 1244 | help |
| 1245 | Many Power Macintoshes and clones have a MESH (Macintosh Enhanced |
| 1246 | SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the |
| 1247 | other Power Macintoshes do). Say Y to include support for this SCSI |
| 1248 | adaptor. |
| 1249 | |
| 1250 | To compile this driver as a module, choose M here: the |
| 1251 | module will be called mesh. |
| 1252 | |
| 1253 | config SCSI_MESH_SYNC_RATE |
| 1254 | int "maximum synchronous transfer rate (MB/s) (0 = async)" |
| 1255 | depends on SCSI_MESH |
| 1256 | default "5" |
| 1257 | help |
| 1258 | On Power Macintoshes (and clones) where the MESH SCSI bus adaptor |
| 1259 | drives a bus which is entirely internal to the machine (such as the |
| 1260 | 7500, 7600, 8500, etc.), the MESH is capable of synchronous |
| 1261 | operation at up to 10 MB/s. On machines where the SCSI bus |
| 1262 | controlled by the MESH can have external devices connected, it is |
| 1263 | usually rated at 5 MB/s. 5 is a safe value here unless you know the |
| 1264 | MESH SCSI bus is internal only; in that case you can say 10. Say 0 |
| 1265 | to disable synchronous operation. |
| 1266 | |
| 1267 | config SCSI_MESH_RESET_DELAY_MS |
| 1268 | int "initial bus reset delay (ms) (0 = no reset)" |
| 1269 | depends on SCSI_MESH |
| 1270 | default "4000" |
| 1271 | |
| 1272 | config SCSI_MAC53C94 |
| 1273 | tristate "53C94 (Power Mac external SCSI) support" |
| 1274 | depends on PPC32 && PPC_PMAC && SCSI |
| 1275 | help |
| 1276 | On Power Macintoshes (and clones) with two SCSI buses, the external |
| 1277 | SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older |
| 1278 | machines which only have one SCSI bus, such as the 7200, also use |
| 1279 | the 53C94. Say Y to include support for the 53C94. |
| 1280 | |
| 1281 | To compile this driver as a module, choose M here: the |
| 1282 | module will be called mac53c94. |
| 1283 | |
| 1284 | source "drivers/scsi/arm/Kconfig" |
| 1285 | |
| 1286 | config JAZZ_ESP |
| 1287 | bool "MIPS JAZZ FAS216 SCSI support" |
| 1288 | depends on MACH_JAZZ && SCSI=y |
| 1289 | select SCSI_SPI_ATTRS |
| 1290 | help |
| 1291 | This is the driver for the onboard SCSI host adapter of MIPS Magnum |
| 1292 | 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM |
| 1293 | systems. |
| 1294 | |
| 1295 | config A3000_SCSI |
| 1296 | tristate "A3000 WD33C93A support" |
| 1297 | depends on AMIGA && SCSI |
| 1298 | help |
| 1299 | If you have an Amiga 3000 and have SCSI devices connected to the |
| 1300 | built-in SCSI controller, say Y. Otherwise, say N. |
| 1301 | |
| 1302 | To compile this driver as a module, choose M here: the |
| 1303 | module will be called a3000. |
| 1304 | |
| 1305 | config A2091_SCSI |
| 1306 | tristate "A2091/A590 WD33C93A support" |
| 1307 | depends on ZORRO && SCSI |
| 1308 | help |
| 1309 | If you have a Commodore A2091 SCSI controller, say Y. Otherwise, |
| 1310 | say N. |
| 1311 | |
| 1312 | To compile this driver as a module, choose M here: the |
| 1313 | module will be called a2091. |
| 1314 | |
| 1315 | config GVP11_SCSI |
| 1316 | tristate "GVP Series II WD33C93A support" |
| 1317 | depends on ZORRO && SCSI |
| 1318 | help |
| 1319 | If you have a Great Valley Products Series II SCSI controller, |
| 1320 | answer Y. Also say Y if you have a later model of GVP SCSI |
| 1321 | controller (such as the GVP A4008 or a Combo board). Otherwise, |
| 1322 | answer N. This driver does NOT work for the T-Rex series of |
| 1323 | accelerators from TekMagic and GVP-M. |
| 1324 | |
| 1325 | To compile this driver as a module, choose M here: the |
| 1326 | module will be called gvp11. |
| 1327 | |
| 1328 | config SCSI_A4000T |
| 1329 | tristate "A4000T NCR53c710 SCSI support" |
| 1330 | depends on AMIGA && SCSI |
| 1331 | select SCSI_SPI_ATTRS |
| 1332 | help |
| 1333 | If you have an Amiga 4000T and have SCSI devices connected to the |
| 1334 | built-in SCSI controller, say Y. Otherwise, say N. |
| 1335 | |
| 1336 | To compile this driver as a module, choose M here: the |
| 1337 | module will be called a4000t. |
| 1338 | |
| 1339 | config SCSI_ZORRO7XX |
| 1340 | tristate "Zorro NCR53c710 SCSI support" |
| 1341 | depends on ZORRO && SCSI |
| 1342 | select SCSI_SPI_ATTRS |
| 1343 | help |
| 1344 | Support for various NCR53c710-based SCSI controllers on Zorro |
| 1345 | expansion boards for the Amiga. |
| 1346 | This includes: |
| 1347 | - the Amiga 4091 Zorro III SCSI-2 controller, |
| 1348 | - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller |
| 1349 | (info at |
| 1350 | <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>), |
| 1351 | - the SCSI controller on the Phase5 Blizzard PowerUP 603e+ |
| 1352 | accelerator card for the Amiga 1200, |
| 1353 | - the SCSI controller on the GVP Turbo 040/060 accelerator. |
| 1354 | |
| 1355 | config SCSI_ZORRO_ESP |
| 1356 | tristate "Zorro ESP SCSI support" |
| 1357 | depends on ZORRO && SCSI |
| 1358 | select SCSI_SPI_ATTRS |
| 1359 | select SCSI_ESP_PIO |
| 1360 | help |
| 1361 | Support for various NCR53C9x (ESP) based SCSI controllers on Zorro |
| 1362 | expansion boards for the Amiga. |
| 1363 | This includes: |
| 1364 | - the Phase5 Blizzard 1230 II and IV SCSI controllers, |
| 1365 | - the Phase5 Blizzard 2060 SCSI controller, |
| 1366 | - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI |
| 1367 | controllers, |
| 1368 | - the Fastlane Zorro III SCSI controller. |
| 1369 | |
| 1370 | config ATARI_SCSI |
| 1371 | tristate "Atari native SCSI support" |
| 1372 | depends on ATARI && SCSI |
| 1373 | select SCSI_SPI_ATTRS |
| 1374 | help |
| 1375 | If you have an Atari with built-in NCR5380 SCSI controller (TT, |
| 1376 | Falcon, ...) say Y to get it supported. Of course also, if you have |
| 1377 | a compatible SCSI controller (e.g. for Medusa). |
| 1378 | |
| 1379 | To compile this driver as a module, choose M here: the module will |
| 1380 | be called atari_scsi. If you also enable NVRAM support, the SCSI |
| 1381 | host's ID is taken from the setting in TT RTC NVRAM. |
| 1382 | |
| 1383 | This driver supports both styles of NCR integration into the |
| 1384 | system: the TT style (separate DMA), and the Falcon style (via |
| 1385 | ST-DMA, replacing ACSI). It does NOT support other schemes, like |
| 1386 | in the Hades (without DMA). |
| 1387 | |
| 1388 | config MAC_SCSI |
| 1389 | tristate "Macintosh NCR5380 SCSI" |
| 1390 | depends on MAC && SCSI |
| 1391 | select SCSI_SPI_ATTRS |
| 1392 | help |
| 1393 | This is the NCR 5380 SCSI controller included on most of the 68030 |
| 1394 | based Macintoshes. If you have one of these say Y and read the |
| 1395 | SCSI-HOWTO, available from |
| 1396 | <http://www.tldp.org/docs.html#howto>. |
| 1397 | |
| 1398 | config SCSI_MAC_ESP |
| 1399 | tristate "Macintosh NCR53c9[46] SCSI" |
| 1400 | depends on MAC && SCSI |
| 1401 | select SCSI_SPI_ATTRS |
| 1402 | select SCSI_ESP_PIO |
| 1403 | help |
| 1404 | This is the NCR 53c9x SCSI controller found on most of the 68040 |
| 1405 | based Macintoshes. |
| 1406 | |
| 1407 | To compile this driver as a module, choose M here: the module |
| 1408 | will be called mac_esp. |
| 1409 | |
| 1410 | config MVME147_SCSI |
| 1411 | bool "WD33C93 SCSI driver for MVME147" |
| 1412 | depends on MVME147 && SCSI=y |
| 1413 | select SCSI_SPI_ATTRS |
| 1414 | help |
| 1415 | Support for the on-board SCSI controller on the Motorola MVME147 |
| 1416 | single-board computer. |
| 1417 | |
| 1418 | config MVME16x_SCSI |
| 1419 | tristate "NCR53C710 SCSI driver for MVME16x" |
| 1420 | depends on MVME16x && SCSI |
| 1421 | select SCSI_SPI_ATTRS |
| 1422 | help |
| 1423 | The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710 |
| 1424 | SCSI controller chip. Almost everyone using one of these boards |
| 1425 | will want to say Y to this question. |
| 1426 | |
| 1427 | config BVME6000_SCSI |
| 1428 | tristate "NCR53C710 SCSI driver for BVME6000" |
| 1429 | depends on BVME6000 && SCSI |
| 1430 | select SCSI_SPI_ATTRS |
| 1431 | help |
| 1432 | The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710 |
| 1433 | SCSI controller chip. Almost everyone using one of these boards |
| 1434 | will want to say Y to this question. |
| 1435 | |
| 1436 | config SUN3_SCSI |
| 1437 | tristate "Sun3 NCR5380 SCSI" |
| 1438 | depends on SUN3 && SCSI |
| 1439 | select SCSI_SPI_ATTRS |
| 1440 | help |
| 1441 | This option will enable support for the OBIO (onboard io) NCR5380 |
| 1442 | SCSI controller found in the Sun 3/50 and 3/60, as well as for |
| 1443 | "Sun3" type VME scsi controllers also based on the NCR5380. |
| 1444 | General Linux information on the Sun 3 series (now discontinued) |
| 1445 | is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. |
| 1446 | |
| 1447 | config SUN3X_ESP |
| 1448 | bool "Sun3x ESP SCSI" |
| 1449 | depends on SUN3X && SCSI=y |
| 1450 | select SCSI_SPI_ATTRS |
| 1451 | help |
| 1452 | The ESP was an on-board SCSI controller used on Sun 3/80 |
| 1453 | machines. Say Y here to compile in support for it. |
| 1454 | |
| 1455 | config SCSI_SUNESP |
| 1456 | tristate "Sparc ESP Scsi Driver" |
| 1457 | depends on SBUS && SCSI |
| 1458 | select SCSI_SPI_ATTRS |
| 1459 | help |
| 1460 | This is the driver for the Sun ESP SCSI host adapter. The ESP |
| 1461 | chipset is present in most SPARC SBUS-based computers and |
| 1462 | supports the Emulex family of ESP SCSI chips (esp100, esp100A, |
| 1463 | esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip. |
| 1464 | |
| 1465 | To compile this driver as a module, choose M here: the |
| 1466 | module will be called sun_esp. |
| 1467 | |
| 1468 | config ZFCP |
| 1469 | tristate "FCP host bus adapter driver for IBM mainframes" |
| 1470 | depends on S390 && QDIO && SCSI |
| 1471 | depends on SCSI_FC_ATTRS |
| 1472 | help |
| 1473 | If you want to access SCSI devices attached to your IBM mainframe by |
| 1474 | means of Fibre Channel Protocol host bus adapters say Y. |
| 1475 | |
| 1476 | Supported HBAs include different models of the FICON Express and FCP |
| 1477 | Express I/O cards. |
| 1478 | |
| 1479 | For a more complete list, and for more details about setup and |
| 1480 | operation refer to the IBM publication "Device Drivers, Features, and |
| 1481 | Commands", SC33-8411. |
| 1482 | |
| 1483 | This driver is also available as a module. This module will be |
| 1484 | called zfcp. If you want to compile it as a module, say M here |
| 1485 | and read <file:Documentation/kbuild/modules.rst>. |
| 1486 | |
| 1487 | config SCSI_PMCRAID |
| 1488 | tristate "PMC SIERRA Linux MaxRAID adapter support" |
| 1489 | depends on PCI && SCSI && NET |
| 1490 | select SGL_ALLOC |
| 1491 | help |
| 1492 | This driver supports the PMC SIERRA MaxRAID adapters. |
| 1493 | |
| 1494 | config SCSI_PM8001 |
| 1495 | tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver" |
| 1496 | depends on PCI && SCSI |
| 1497 | select SCSI_SAS_LIBSAS |
| 1498 | help |
| 1499 | This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip |
| 1500 | based host adapters. |
| 1501 | |
| 1502 | config SCSI_BFA_FC |
| 1503 | tristate "Brocade BFA Fibre Channel Support" |
| 1504 | depends on PCI && SCSI |
| 1505 | depends on SCSI_FC_ATTRS |
| 1506 | help |
| 1507 | This bfa driver supports all Brocade PCIe FC/FCOE host adapters. |
| 1508 | |
| 1509 | To compile this driver as a module, choose M here. The module will |
| 1510 | be called bfa. |
| 1511 | |
| 1512 | config SCSI_VIRTIO |
| 1513 | tristate "virtio-scsi support" |
| 1514 | depends on VIRTIO |
| 1515 | help |
| 1516 | This is the virtual HBA driver for virtio. If the kernel will |
| 1517 | be used in a virtual machine, say Y or M. |
| 1518 | |
| 1519 | source "drivers/scsi/csiostor/Kconfig" |
| 1520 | |
| 1521 | source "drivers/scsi/pcmcia/Kconfig" |
| 1522 | |
| 1523 | endif # SCSI_LOWLEVEL |
| 1524 | |
| 1525 | source "drivers/scsi/device_handler/Kconfig" |
| 1526 | |
| 1527 | endmenu |