Kconfig 71.5 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
comment "SCSI support type (disk, tape, CD-ROM)"
	depends on SCSI

config BLK_DEV_SD
	tristate "SCSI disk support"
	depends on SCSI
	---help---
	  If you want to use a SCSI hard disk or the SCSI or parallel port
	  version of the IOMEGA ZIP drive under Linux, say Y and read the
	  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>. This is NOT for SCSI
	  CD-ROMs.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
16
	  The module will be called sd_mod.  If you want to compile it as a
17
	  module, say M here and read <file:Documentation/modules.txt> and
18
	  <file:Documentation/scsi/scsi.txt>.  Do not compile this driver as a
19 20 21 22 23 24 25 26 27 28 29
	  module if your root file system (the one containing the directory /)
	  is located on a SCSI disk. In this case, do not compile the driver
	  for your SCSI host adapter (below) as a module either.

config CHR_DEV_ST
	tristate "SCSI tape support"
	depends on SCSI
	---help---
	  If you want to use a SCSI tape drive under Linux, say Y and read the
	  SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>, and
30
	  <file:Documentation/scsi/st.txt> in the kernel source.  This is NOT for
31 32 33 34
	  SCSI CD-ROMs.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
35
	  The module will be called st. If you want to compile it as a
36
	  module, say M here and read <file:Documentation/modules.txt> and
37
	  <file:Documentation/scsi/scsi.txt>.
38 39 40 41 42 43 44 45 46 47 48 49 50 51

config CHR_DEV_OSST
	tristate "SCSI OnStream SC-x0 tape support"
	depends on SCSI
	---help---
	  The OnStream SC-x0 SCSI tape drives can not be driven by the
	  standard st driver, but instead need this special osst driver and
	  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
	  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
	  as well.  Note that there is also a second generation of OnStream
	  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
	  tapes (QIC-157) and can be driven by the standard driver st.
	  For more information, you may have a look at the SCSI-HOWTO
	  <http://www.linuxdoc.org/docs.html#howto>  and
52
	  <file:Documentation/scsi/osst.txt>  in the kernel source.
53 54 55 56 57 58 59
	  More info on the OnStream driver may be found on
	  <http://linux1.onstream.nl/test/>
	  Please also have a look at the standard st docu, as most of it
	  applies to osst as well.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
60
	  The module will be called osst. If you want to compile it as a
61
	  module, say M here and read <file:Documentation/modules.txt> and
62
	  <file:Documentation/scsi/scsi.txt>.
63 64 65 66 67 68 69 70 71 72 73 74

config BLK_DEV_SR
	tristate "SCSI CDROM support"
	depends on SCSI
	---help---
	  If you want to use a SCSI CD-ROM under Linux, say Y and read the
	  SCSI-HOWTO and the CD-ROM-HOWTO at
	  <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
	  or M to "ISO 9660 CD-ROM file system support" later.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
75
	  The module will be called sr_mod. If you want to compile it as a
76
	  module, say M here and read <file:Documentation/modules.txt> and
77
	  <file:Documentation/scsi/scsi.txt>.
78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105

config BLK_DEV_SR_VENDOR
	bool "Enable vendor-specific extensions (for SCSI CDROM)"
	depends on BLK_DEV_SR
	help
	  This enables the usage of vendor specific SCSI commands. This is
	  required to support multisession CDs with old NEC/TOSHIBA cdrom
	  drives (and HP Writers). If you have such a drive and get the first
	  session only, try saying Y here; everybody else says N.

config CHR_DEV_SG
	tristate "SCSI generic support"
	depends on SCSI
	---help---
	  If you want to use SCSI scanners, synthesizers or CD-writers or just
	  about anything having "SCSI" in its name other than hard disks,
	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
	  directly, so you need some additional software which knows how to
	  talk to these devices using the SCSI protocol:

	  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
	  writer software look at Cdrtools
	  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
	  and for burning a "disk at once": CDRDAO
	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
	  For other devices, it's possible that you'll have to write the
	  driver software yourself. Please read the file
106
	  <file:Documentation/scsi/scsi-generic.txt> for more information.
107 108 109 110

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt> and
111
	  <file:Documentation/scsi/scsi.txt>. The module will be called sg.
112
	  If unsure, say N.
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178

comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
	depends on SCSI

config SCSI_MULTI_LUN
	bool "Probe all LUNs on each SCSI device"
	depends on SCSI
	help
	  If you have a SCSI device that supports more than one LUN (Logical
	  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
	  can say Y here to force the SCSI driver to probe for multiple LUNs.
	  A SCSI device with multiple LUNs acts logically like multiple SCSI
	  devices. The vast majority of SCSI devices have only one LUN, and
	  so most people can say N here and should in fact do so, because it
	  is safer.

config SCSI_REPORT_LUNS
	bool "Build with SCSI REPORT LUNS support"
	depends on SCSI
	help
	  If you want to build with SCSI REPORT LUNS support in the kernel, say Y here.
	  The REPORT LUNS command is useful for devices (such as disk arrays) with
	  large numbers of LUNs where the LUN values are not contiguous (sparse LUN).
	  REPORT LUNS scanning is done only for SCSI-3 devices. Most users can safely
	  answer N here.

config SCSI_CONSTANTS
	bool "Verbose SCSI error reporting (kernel size +=12K)"
	depends on SCSI
	help
	  The error messages regarding your SCSI hardware will be easier to
	  understand if you say Y here; it will enlarge your kernel by about
	  12 KB. If in doubt, say Y.

config SCSI_LOGGING
	bool "SCSI logging facility"
	depends on SCSI
	---help---
	  This turns on a logging facility that can be used to debug a number
	  of SCSI related problems.

	  If you say Y here, no logging output will appear by default, but you
	  can enable logging by saying Y to "/proc file system support" and
	  "Sysctl support" below and executing the command

	  echo "scsi log token [level]" > /proc/scsi/scsi

	  at boot time after the /proc file system has been mounted.

	  There are a number of things that can be used for 'token' (you can
	  find them in the source: <file:drivers/scsi/scsi.c>), and this
	  allows you to select the types of information you want, and the
	  level allows you to select the level of verbosity.

	  If you say N here, it may be harder to track down some types of SCSI
	  problems. If you say Y here your kernel will be somewhat larger, but
	  there should be no noticeable performance impact as long as you have
	  logging turned off.


menu "SCSI low-level drivers"
	depends on SCSI!=n

config SGIWD93_SCSI
	tristate "SGI WD93C93 SCSI Driver"
	depends on SGI_IP22 && SCSI
179 180 181
  	help
	  If you have a Western Digital WD93 SCSI controller on
	  an SGI MIPS system, say Y.  Otherwise, say N.
182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216

config SCSI_DECNCR
	tristate "DEC NCR53C94 Scsi Driver"
	depends on DECSTATION && TC && SCSI
	help
	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.

config SCSI_DECSII
	tristate "DEC SII Scsi Driver"
	depends on DECSTATION && SCSI

config BLK_DEV_3W_XXXX_RAID
	tristate "3ware Hardware ATA-RAID support"
	depends on PCI && SCSI
	help
	  3ware is the only hardware ATA-Raid product in Linux to date.
	  This card is 2,4, or 8 channel master mode support only.
	  SCSI support required!!!

	  <http://www.3ware.com/>

	  Please read the comments at the top of
	  <file:drivers/scsi/3w-xxxx.c>.

config SCSI_7000FASST
	tristate "7000FASST SCSI support"
	depends on SCSI && ISA
	help
	  This driver supports the Western Digital 7000 SCSI host adapter
	  family.  Some information is in the source:
	  <file:drivers/scsi/wd7000.c>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
217
	  The module will be called wd7000.  If you want to compile it as a
218 219 220 221 222 223 224 225 226 227
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_ACARD
	tristate "ACARD SCSI support"
	depends on SCSI
	help
	  This driver supports the ACARD 870U/W SCSI host adapter.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
228
	  The module will be called atp870u. If you want to compile it as a
229 230 231 232 233 234 235 236 237 238 239 240
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_AHA152X
	tristate "Adaptec AHA152X/2825 support"
	depends on ISA && SCSI
	---help---
	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
	  must be manually specified in this case.

	  It is explained in section 3.3 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>. You might also want to
241
	  read the file <file:Documentation/scsi/aha152x.txt>.
242 243 244

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
245
	  The module will be called aha152x. If you want to compile it as a
246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_AHA1542
	tristate "Adaptec AHA1542 support"
	depends on ISA && SCSI
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.4 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  Note that Trantor was
	  purchased by Adaptec, and some former Trantor products are being
	  sold under the Adaptec name.  If it doesn't work out of the box, you
	  may have to change some settings in <file:drivers/scsi/aha1542.h>.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
262
	  will be called aha1542.
263 264 265 266 267 268 269 270 271 272 273 274 275

config SCSI_AHA1740
	tristate "Adaptec AHA1740 support"
	depends on EISA && SCSI
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.5 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/aha1740.h>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
276
	  The module will be called aha1740.  If you want to compile it as a
277 278 279 280 281 282
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_AACRAID
	tristate "Adaptec AACRAID support (EXPERIMENTAL)"
	depends on EXPERIMENTAL && SCSI && PCI

283
source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
284 285

config SCSI_AIC7XXX_OLD
286
	tristate "Adaptec AIC7xxx support (old driver)"
287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315
	help
	  WARNING This driver is an older aic7xxx driver and is no longer
	  under active development.  Adaptec, Inc. is writing a new driver to
	  take the place of this one, and it is recommended that whenever
	  possible, people should use the new Adaptec written driver instead
	  of this one.  This driver will eventually be phased out entirely.

	  This is support for the various aic7xxx based Adaptec SCSI
	  controllers. These include the 274x EISA cards; 284x VLB cards;
	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
	  motherboard based SCSI controllers from Adaptec. It does not support
	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
	  support them. It does not support the 2920 cards from Adaptec that
	  use the Future Domain SCSI controller chip. For those cards, you
	  need the "Future Domain 16xx SCSI support" driver.

	  In general, if the controller is based on an Adaptec SCSI controller
	  chip from the aic777x series or the aic78xx series, this driver
	  should work. The only exception is the 7810 which is specifically
	  not supported (that's the RAID controller chip on the AAA-13x
	  cards).

	  Note that the AHA2920 SCSI host adapter is *not* supported by this
	  driver; choose "Future Domain 16xx SCSI support" instead if you have
	  one of those.

	  Information on the configuration options for this controller can be
	  found by checking the help file for each of the available
	  configuration options. You should read
316
	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
317 318 319 320 321 322 323
	  contacting the maintainer with any questions.  The SCSI-HOWTO,
	  available from <http://www.linuxdoc.org/docs.html#howto>, can also
	  be of great help.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
324
	  will be called aic7xxx_old.
325

326
source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
327 328 329 330 331 332 333 334

# All the I2O code and drivers do not seem to be 64bit safe.
config SCSI_DPT_I2O
	tristate "Adaptec I2O RAID support "
	depends on !X86_64 && SCSI
	help
	  This driver supports all of Adaptec's I2O based RAID controllers as 
	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
335
	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
336 337 338 339 340

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  If you want to compile it as a module, say M here and read
	  <file:Documentation/modules.txt>.  The module will be called
341
	  dpt_i2o.
342 343 344 345 346 347 348 349 350 351 352 353 354

config SCSI_ADVANSYS
	tristate "AdvanSys SCSI support"
	depends on SCSI
	help
	  This is a driver for all SCSI host adapters manufactured by
	  AdvanSys. It is documented in the kernel source in
	  <file:drivers/scsi/advansys.c>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  If you want to compile it as a module, say M here and read
	  <file:Documentation/modules.txt>.  The module will be called
355
	  advansys.
356 357 358 359 360 361

config SCSI_IN2000
	tristate "Always IN2000 SCSI support"
	depends on SCSI
	help
	  This is support for an ISA bus SCSI host adapter.  You'll find more
362
	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
363 364 365 366 367 368
	  out of the box, you may have to change the jumpers for IRQ or
	  address selection.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
369
	  will be called in2000.
370 371 372 373 374 375 376

# does not use pci dma and seems to be isa/onboard only for old machines
config SCSI_AM53C974
	tristate "AM53/79C974 PCI SCSI support"
	depends on !X86_64 && SCSI && PCI
	---help---
	  This is support for the AM53/79C974 SCSI host adapters.  Please read
377
	  <file:Documentation/scsi/AM53C974.txt> for details.  Also, the
378 379 380 381 382 383 384 385 386 387
	  SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>, is for you.

	  Note that there is another driver for AM53C974 based adapters:
	  "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above.  You
	  can pick either one.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
388
	  will be called AM53C974.
389 390 391 392 393 394 395 396 397 398 399

config SCSI_MEGARAID
	tristate "AMI MegaRAID support"
	depends on SCSI
	help
	  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
	  and 467 SCSI host adapters.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
400
	  will be called megaraid.
401 402 403 404 405 406 407 408

config SCSI_BUSLOGIC
	tristate "BusLogic SCSI support"
	depends on SCSI
	---help---
	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
	  Adapters. Consult the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>, and the files
409 410
	  <file:Documentation/scsi/BusLogic.txt> and
	  <file:Documentation/scsi/FlashPoint.txt> for more information. If this
411 412 413 414 415 416 417
	  driver does not work correctly without modification, please contact
	  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.

	  You can also build this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  but only a single instance may be loaded. If you want to compile it
	  as a module, say M here and read <file:Documentation/modules.txt>.
418
	  The module will be called BusLogic.
419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443

config SCSI_OMIT_FLASHPOINT
	bool "Omit FlashPoint support"
	depends on SCSI_BUSLOGIC
	help
	  This option allows you to omit the FlashPoint support from the
	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
	  substantial, so users of MultiMaster Host Adapters may wish to omit
	  it.

config SCSI_CPQFCTS
	tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
	depends on PCI && SCSI
	help
	  Say Y here to compile in support for the Compaq StorageWorks Fibre
	  Channel 64-bit/66Mhz Host Bus Adapter.

config SCSI_DMX3191D
	tristate "DMX3191D SCSI support"
	depends on SCSI && PCI
	help
	  This is support for Domex DMX3191D SCSI Host Adapters.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
444
	  The module will be called dmx3191d.  If you want to compile it as
445 446 447 448 449 450 451 452 453
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_DTC3280
	tristate "DTC3180/3280 SCSI support"
	depends on SCSI && ISA
	help
	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
	  the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>, and the file
454
	  <file:Documentation/scsi/dtc3x80.txt>.
455 456 457

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
458
	  The module will be called dtc.  If you want to compile it as a
459 460 461 462 463 464 465 466
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_EATA
	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
	depends on SCSI
	---help---
	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
	  ISA and all EISA I/O addresses are probed looking for the "EATA"
467 468
	  signature. The addresses of all the PCI SCSI controllers reported
          by the PCI subsystem are probed as well.
469 470 471 472 473 474 475 476 477 478 479 480

	  You want to read the start of <file:drivers/scsi/eata.c> and the
	  SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  Note that there is also another driver for the same hardware
	  available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
	  Alphatronix) support". You should say Y to only one of them.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
481
	  will be called eata.
482 483 484 485 486 487 488

config SCSI_EATA_TAGGED_QUEUE
	bool "enable tagged command queueing"
	depends on SCSI_EATA
	help
	  This is a feature of SCSI-2 which improves performance: the host
	  adapter can send several SCSI commands to a device's queue even if
489 490
	  previous commands haven't finished yet.
	  This is equivalent to the "eata=tc:y" boot option.
491 492 493 494 495 496 497 498 499

config SCSI_EATA_LINKED_COMMANDS
	bool "enable elevator sorting"
	depends on SCSI_EATA
	help
	  This option enables elevator sorting for all probed SCSI disks and
	  CD-ROMs. It definitely reduces the average seek distance when doing
	  random seeks, but this does not necessarily result in a noticeable
	  performance improvement: your mileage may vary...
500
	  This is equivalent to the "eata=lc:y" boot option.
501 502 503 504 505 506 507 508 509 510 511 512

config SCSI_EATA_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_EATA
	default "16"
	help
	  This specifies how many SCSI commands can be maximally queued for
	  each probed SCSI device. You should reduce the default value of 16
	  only if you have disks with buggy or limited tagged command support.
	  Minimum is 2 and maximum is 62. This value is also the window size
	  used by the elevator sorting option above. The effective value used
	  by the driver for each probed SCSI device is reported at boot time.
513
	  This is equivalent to the "eata=mq:8" boot option.
514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529

config SCSI_EATA_DMA
	tristate "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support"
	depends on SCSI
	---help---
	  This is support for the EATA-DMA protocol compliant SCSI Host
	  Adapters like the SmartCache III/IV, SmartRAID controller families
	  and the DPT PM2011B and PM2012B controllers.

	  Note that this driver is obsolete; if you have one of the above
	  SCSI Host Adapters, you should normally say N here and Y to "EATA
	  ISA/EISA/PCI support", below.  Please read the SCSI-HOWTO, available
	  from <http://www.linuxdoc.org/docs.html#howto>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
530
	  The module will be called eata_dma.  If you want to compile it as
531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_EATA_PIO
	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
	depends on SCSI
	---help---
	  This driver supports all EATA-PIO protocol compliant SCSI Host
	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
	  host adapters could also use this driver but are discouraged from
	  doing so, since this driver only supports hard disks and lacks
	  numerous features.  You might want to have a look at the SCSI-HOWTO,
	  available from <http://www.linuxdoc.org/docs.html#howto>.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
547
	  will be called eata_pio.
548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566

config SCSI_FUTURE_DOMAIN
	tristate "Future Domain 16xx SCSI/AHA-2920A support"
	depends on SCSI
	---help---
	  This is support for Future Domain's 16-bit SCSI host adapters
	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
	  other adapters based on the Future Domain chipsets (Quantum
	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
	  It is explained in section 3.7 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
	  controller support"). This Future Domain driver works with the older
	  Adaptec AHA-2920A boards with a Future Domain chip on them.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
567
	  The module will be called fdomain. If you want to compile it as a
568 569 570 571 572 573 574 575 576 577 578 579 580 581
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_FD_MCS
	tristate "Future Domain MCS-600/700 SCSI support"
	depends on MCA && SCSI
	---help---
	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
	  is identical to the MCS 700 and hence also supported by this driver.
	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
	  It supports multiple adapters in the same system.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
582
	  The module will be called fd_mcs. If you want to compile it as a
583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_GDTH
	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
	depends on SCSI
	---help---
	  Formerly called GDT SCSI Disk Array Controller Support.

	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
	  manufactured by Intel/ICP vortex (an Intel Company). It is documented
	  in the kernel source in <file:drivers/scsi/gdth.c> and
	  <file:drivers/scsi/gdth.h.>

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  If you want to compile it as a module, say M here and read
	  <file:Documentation/modules.txt>.

config SCSI_GENERIC_NCR5380
	tristate "Generic NCR5380/53c400 SCSI PIO support"
	depends on SCSI
	---help---
	  This is a driver for the old NCR 53c80 series of SCSI controllers
	  on boards using PIO. Most boards such as the Trantor T130 fit this
	  category, along with a large number of ISA 8bit controllers shipped
	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
	  you should select the specific driver for that card rather than
	  generic 5380 support.

	  It is explained in section 3.8 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/g_NCR5380.h>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
619
	  The module will be called g_NCR5380.  If you want to compile it as
620 621 622 623 624 625 626 627 628 629 630 631 632 633 634
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_GENERIC_NCR5380_MMIO
	tristate "Generic NCR5380/53c400 SCSI MMIO support"
	depends on SCSI
	---help---
	  This is a driver for the old NCR 53c80 series of SCSI controllers
	  on boards using memory mapped I/O. 
	  It is explained in section 3.8 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/g_NCR5380.h>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
635
	  The module will be called g_NCR5380.  If you want to compile it as
636 637 638 639 640 641 642 643 644 645 646
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_GENERIC_NCR53C400
	bool "Enable NCR53c400 extensions"
	depends on SCSI_GENERIC_NCR5380
	help
	  This enables certain optimizations for the NCR53c400 SCSI cards.
	  You might as well try it out.  Note that this driver will only probe
	  for the Trantor T130B in its default configuration; you might have
	  to pass a command line option to the kernel at boot time if it does
	  not detect your card.  See the file
647
	  <file:Documentation/scsi/g_NCR5380.txt> for details.
648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670

config SCSI_IBMMCA
	tristate "IBMMCA SCSI support"
	depends on MCA && SCSI
	---help---
	  This is support for the IBM SCSI adapter found in many of the PS/2
	  series computers.  These machines have an MCA bus, so you need to
	  answer Y to "MCA support" as well and read
	  <file:Documentation/mca.txt>.

	  If the adapter isn't found during boot (a common problem for models
	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
	  if that doesn't work check your reference diskette).  Owners of
	  model 95 with a LED-matrix-display can in addition activate some
	  activity info like under OS/2, but more informative, by setting
	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
	  bootparam" or see the documentation of your boot loader about how to
	  pass options to the kernel.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
671
	  will be called ibmmca.
672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734

config IBMMCA_SCSI_ORDER_STANDARD
	bool "Standard SCSI-order"
	depends on SCSI_IBMMCA
	---help---
	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
	  are assigned to the drive letters, starting with the lowest SCSI-id
	  (physical number -- pun) to be drive C:, as seen from DOS and
	  similar operating systems. When looking into papers describing the
	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
	  The SCSI-standard follows a hardware-hierarchy which says that id 7
	  has the highest priority and id 0 the lowest. Therefore, the host
	  adapters are still today everywhere placed as SCSI-id 7 by default.
	  In the SCSI-standard, the drive letters express the priority of the
	  disk. C: should be the hard disk, or a partition on it, with the
	  highest priority. This must therefore be the disk with the highest
	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
	  original definition of the SCSI-standard as also industrial- and
	  process-control-machines, like VME-CPUs running under realtime-OSes
	  (e.g. LynxOS, OS9) do.

	  If you like to run Linux on your MCA-machine with the same
	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
	  machine, which is in addition conformant to the SCSI-standard, you
	  must say Y here. This is also necessary for MCA-Linux users who want
	  to keep downward compatibility to older releases of the
	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
	  June 1997).

	  If you like to have the lowest SCSI-id assigned as drive C:, as
	  modern SCSI-BIOSes do, which does not conform to the standard, but
	  is widespread and common in the PC-world of today, you must say N
	  here. If unsure, say Y.

config IBMMCA_SCSI_DEV_RESET
	bool "Reset SCSI-devices at boottime"
	depends on SCSI_IBMMCA
	---help---
	  By default, SCSI-devices are reset when the machine is powered on.
	  However, some devices exist, like special-control-devices,
	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
	  not reset when switched on. If you say Y here, each device connected
	  to your SCSI-bus will be issued a reset-command after it has been
	  probed, while the kernel is booting. This may cause problems with
	  more modern devices, like hard disks, which do not appreciate these
	  reset commands, and can cause your system to hang. So say Y only if
	  you know that one of your older devices needs it; N is the safe
	  answer.

config SCSI_IPS
	tristate "IBM ServeRAID support"
	depends on X86 && SCSI && PCI
	---help---
	  This is support for the IBM ServeRAID hardware RAID controllers.
	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
	  for more information.  If this driver does not work correctly
	  without modification please contact the author by email at
	  ipslinux@us.ibm.com.

	  You can build this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  but only a single instance may be loaded. If you want to compile it
	  as a module, say M here and read <file:Documentation/modules.txt>.
735
	  The module will be called ips.
736 737 738 739 740 741 742 743 744 745 746 747

config SCSI_INITIO
	tristate "Initio 9100U(W) support"
	depends on SCSI && PCI
	help
	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
	  read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
748
	  will be called initio.
749 750 751 752 753 754 755 756 757 758 759 760

config SCSI_INIA100
	tristate "Initio INI-A100U2W support"
	depends on SCSI && PCI
	help
	  This is support for the Initio INI-A100U2W SCSI host adapter.
	  Please read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
761
	  will be called a100u2w.
762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779

config SCSI_PPA
	tristate "IOMEGA parallel port (ppa - older drives)"
	depends on SCSI && PARPORT
	---help---
	  This driver supports older versions of IOMEGA's parallel port ZIP
	  drive (a 100 MB removable media device).

	  Note that you can say N here if you have the SCSI version of the ZIP
	  drive: it will be supported automatically if you said Y to the
	  generic "SCSI disk support", above.

	  If you have the ZIP Plus drive or a more recent parallel port ZIP
	  drive (if the supplied cable with the drive is labeled "AutoDetect")
	  then you should say N here and Y to "IOMEGA parallel port (imm -
	  newer drives)", below.

	  For more information about this driver and how to use it you should
780
	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
781 782 783 784 785 786 787 788 789
	  the SCSI-HOWTO, which is available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If you use this driver,
	  you will still be able to use the parallel port for other tasks,
	  such as a printer; it is safe to compile both drivers into the
	  kernel.

	  This driver is also available as a module which can be inserted in
	  and removed from the running kernel whenever you want.  To compile
	  this driver as a module, say M here and read
790
	  <file:Documentation/modules.txt>.  The module will be called ppa.
791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808

config SCSI_IMM
	tristate "IOMEGA parallel port (imm - newer drives)"
	depends on SCSI && PARPORT
	---help---
	  This driver supports newer versions of IOMEGA's parallel port ZIP
	  drive (a 100 MB removable media device).

	  Note that you can say N here if you have the SCSI version of the ZIP
	  drive: it will be supported automatically if you said Y to the
	  generic "SCSI disk support", above.

	  If you have the ZIP Plus drive or a more recent parallel port ZIP
	  drive (if the supplied cable with the drive is labeled "AutoDetect")
	  then you should say Y here; if you have an older ZIP drive, say N
	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.

	  For more information about this driver and how to use it you should
809
	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
810 811 812 813 814 815 816 817 818
	  the SCSI-HOWTO, which is available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If you use this driver,
	  you will still be able to use the parallel port for other tasks,
	  such as a printer; it is safe to compile both drivers into the
	  kernel.

	  This driver is also available as a module which can be inserted in
	  and removed from the running kernel whenever you want.  To compile
	  this driver as a module, say M here and read
819
	  <file:Documentation/modules.txt>.  The module will be called imm.
820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861

config SCSI_IZIP_EPP16
	bool "ppa/imm option - Use slow (but safe) EPP-16"
	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
	---help---
	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
	  allows them to act as expansion buses that can handle up to 64
	  peripheral devices.

	  Some parallel port chipsets are slower than their motherboard, and
	  so we have to control the state of the chipset's FIFO queue every
	  now and then to avoid data loss. This will be done if you say Y
	  here.

	  Generally, saying Y is the safe option and slows things down a bit.

config SCSI_IZIP_SLOW_CTR
	bool "ppa/imm option - Assume slow parport control register"
	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
	help
	  Some parallel ports are known to have excessive delays between
	  changing the parallel port control register and good data being
	  available on the parallel port data/status register. This option
	  forces a small delay (1.0 usec to be exact) after changing the
	  control register to let things settle out. Enabling this option may
	  result in a big drop in performance but some very old parallel ports
	  (found in 386 vintage machines) will not work properly.

	  Generally, saying N is fine.

config SCSI_NCR53C406A
	tristate "NCR53c406a SCSI support"
	depends on SCSI && ISA
	help
	  This is support for the NCR53c406a SCSI host adapter.  For user
	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
	  in the kernel source.  Also read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
862
	  will be called NCR53c406.
863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909

config SCSI_NCR_D700
	tristate "NCR Dual 700 MCA SCSI support"
	depends on MCA && SCSI
	help
	  This is a driver for the MicroChannel Dual 700 card produced by
	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
	  tries to negotiate sync and uses tag command queueing.

	  Unless you have an NCR manufactured machine, the chances are that
	  you do not have this SCSI card, so say N.

config 53C700_IO_MAPPED
	bool
	depends on SCSI_NCR_D700
	default y

config SCSI_LASI700
	tristate "HP LASI SCSI support for 53c700/710"
	depends on PARISC && SCSI
	help
	  This is a driver for the lasi baseboard in some parisc machines
	  which is based on the 53c700 chip.  Will also support LASI subsystems
	  based on the 710 chip using 700 emulation mode.

	  Unless you know you have a 53c700 or 53c710 based lasi, say N here

config 53C700_MEM_MAPPED
	bool
	depends on SCSI_LASI700
	default y

config 53C700_LE_ON_BE
	bool
	depends on SCSI_LASI700
	default y

config SCSI_NCR53C7xx
	tristate "NCR53c7,8xx SCSI support"
	depends on SCSI && PCI
	---help---
	  This is a driver for the 53c7 and 8xx NCR family of SCSI
	  controllers, not to be confused with the NCR 5380 controllers.  It
	  is explained in section 3.8 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/53c7,8xx.h>.  Please read
910
	  <file:Documentation/scsi/ncr53c7xx.txt> for the available boot time
911 912 913 914 915 916 917 918 919 920
	  command line options.

	  Note: there is another driver for the 53c8xx family of controllers
	  ("NCR53C8XX SCSI support" below).  If you want to use them both, you
	  need to say M to both and build them as modules, but only one may be
	  active at a time. If you have a 53c8xx board, it's better to use the
	  other driver.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
921
	  The module will be called 53c7,8xx.  If you want to compile it as
922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_NCR53C7xx_sync
	bool "always negotiate synchronous transfers"
	depends on SCSI_NCR53C7xx
	help
	  In general, this is good; however, it is a bit dangerous since there
	  are some broken SCSI devices out there. Take your chances. Safe bet
	  is N.

config SCSI_NCR53C7xx_FAST
	bool "allow FAST-SCSI [10MHz]"
	depends on SCSI_NCR53C7xx
	help
	  This will enable 10MHz FAST-SCSI transfers with your host
	  adapter. Some systems have problems with that speed, so it's safest
	  to say N here.

config SCSI_NCR53C7xx_DISCONNECT
	bool "allow DISCONNECT"
	depends on SCSI_NCR53C7xx
	help
	  This enables the disconnect/reconnect feature of the NCR SCSI
	  controller. When you say Y here, a slow SCSI device will not lock
	  the SCSI bus while processing a request, allowing simultaneous use
	  of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
	  providing much better performance when using slow and fast SCSI
	  devices at the same time. Some devices, however, do not operate
	  properly with this option enabled, and will cause your SCSI system
	  to hang, which might cause a system crash. The safe answer
	  therefore is to say N.

config SCSI_SYM53C8XX_2
	tristate "SYM53C8XX Version 2 SCSI support"
	depends on PCI && SCSI
	---help---
	  This driver supports the whole NCR53C8XX/SYM53C8XX family of 
	  PCI-SCSI controllers. It also supports the subset of LSI53C10XX 
	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS 
	  language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI 
	  controllers.

	  If your system has problems using this new major version of the
	  SYM53C8XX driver, you may switch back to driver version 1.

	  Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
	  information.

Richard Hirst's avatar
Richard Hirst committed
970 971 972 973 974 975 976 977 978 979
config SCSI_ZALON
	tristate "Zalon SCSI support"
	depends on GSC && SCSI
	help
	  The Zalon is a GSC/HSC bus interface chip that sits between the
	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
	  C110, J200, J210 and some D, K & R-class machines.  It's also
	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
	  Say Y here if you have one of these machines or cards.

980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051
config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
	int "DMA addressing mode"
	depends on SCSI_SYM53C8XX_2
	default "1"
	---help---
	  This option only applies to PCI-SCSI chip that are PCI DAC capable 
	  (875A, 895A, 896, 1010-33, 1010-66, 1000).

	  When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
	  When set to 1, 40 bit DMA addressing (with upper 24 bits of address 
	  set to zero) is supported. The addressable range is here 1 TB.
	  When set to 2, full 64 bits of address for DMA are supported, but only
	  16 segments of 4 GB can be addressed. The addressable range is so 
	  limited to 64 GB.

	  The safest value is 0 (32 bit DMA addressing) that is guessed to still 
	  fit most of real machines.

	  The preferred value 1 (40 bit DMA addressing) should make happy 
	  properly engineered PCI DAC capable host bridges. You may configure
	  this option for Intel platforms with more than 4 GB of memory.

	  The still experimental value 2 (64 bit DMA addressing with 16 x 4GB 
	  segments limitation) can be used on systems that require PCI address 
	  bits past bit 39 to be set for the addressing of memory using PCI 
	  DAC cycles.

config SCSI_SYM53C8XX_DEFAULT_TAGS
	int "default tagged command queue depth"
	depends on SCSI_SYM53C8XX_2
	default "16"
	help
	  This is the default value of the command queue depth the driver will 
	  announce to the generic SCSI layer for devices that support tagged 
	  command queueing. This value can be changed from the boot command line.
	  This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.

config SCSI_SYM53C8XX_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_SYM53C8XX_2
	default "64"
	help
	  This option allows you to specify the maximum number of commands
	  that can be queued to any device, when tagged command queuing is
	  possible. The driver supports up to 256 queued commands per device.
	  This value is used as a compiled-in hard limit.

config SCSI_SYM53C8XX_IOMAPPED
	bool "use normal IO"
	depends on SCSI_SYM53C8XX_2
	help
	  If you say Y here, the driver will preferently use normal IO rather than 
	  memory mapped IO.

config SCSI_NCR53C8XX
	tristate "NCR53C8XX SCSI support"
	depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
	---help---
	  This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
	  of PCI-SCSI controllers.  This driver supports parity checking,
	  tagged command queuing and fast synchronous data transfers up to 80
	  MB/s with wide FAST-40 LVD devices and controllers.

	  Recent versions of the 53C8XX chips are better supported by the
	  option "SYM53C8XX SCSI support", below.

	  Note: there is yet another driver for the 53c8xx family of
	  controllers ("NCR53c7,8xx SCSI support" above).  If you want to use
	  them both, you need to say M to both and build them as modules, but
	  only one may be active at a time.  If you have a 53c8xx board, you
	  probably do not want to use the "NCR53c7,8xx SCSI support".

1052
	  Please read <file:Documentation/scsi/ncr53c8xx.txt> for more
1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078
	  information.

config SCSI_SYM53C8XX
	tristate "SYM53C8XX SCSI support"
	depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
	---help---
	  This driver supports all the features of recent 53C8XX chips (used
	  in PCI SCSI controllers), notably the hardware phase mismatch
	  feature of the SYM53C896.

	  Older versions of the 53C8XX chips are not supported by this
	  driver.  If your system uses either a 810 rev. < 16, a 815, or a 825
	  rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
	  driver ("NCR53C8XX SCSI support" above) or configure both the
	  NCR53C8XX and this SYM53C8XX drivers either as module or linked to
	  the kernel image.

	  When both drivers are linked into the kernel, the SYM53C8XX driver
	  is called first at initialization and you can use the 'excl=ioaddr'
	  driver boot option to exclude attachment of adapters by the
	  SYM53C8XX driver.  For example, entering
	  'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
	  adapters at io address 0xb400 and 0xc000 from being attached by the
	  SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
	  The 'excl' option is also supported by the NCR53C8XX driver.

1079
	  Please read <file:Documentation/scsi/ncr53c8xx.txt> for more
1080 1081 1082 1083
	  information.

config SCSI_NCR53C8XX_DEFAULT_TAGS
	int "default tagged command queue depth"
Richard Hirst's avatar
Richard Hirst committed
1084
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON)
1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109
	default "8"
	---help---
	  "Tagged command queuing" is a feature of SCSI-2 which improves
	  performance: the host adapter can send several SCSI commands to a
	  device's queue even if previous commands haven't finished yet.
	  Because the device is intelligent, it can optimize its operations
	  (like head positioning) based on its own request queue. Some SCSI
	  devices don't implement this properly; if you want to disable this
	  feature, enter 0 or 1 here (it doesn't matter which).

	  The default value is 8 and should be supported by most hard disks.
	  This value can be overridden from the boot command line using the
	  'tags' option as follows (example):
	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
	  4, set queue depth to 16 for target 2 and target 3 on controller 0
	  and set queue depth to 10 for target 0 / lun 2 on controller 1.

	  The normal answer therefore is to go with the default 8 and to use
	  a boot command line option for devices that need to use a different
	  command queue depth.

	  There is no safe option other than using good SCSI devices.

config SCSI_NCR53C8XX_MAX_TAGS
	int "maximum number of queued commands"
Richard Hirst's avatar
Richard Hirst committed
1110
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON)
1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126
	default "32"
	---help---
	  This option allows you to specify the maximum number of commands
	  that can be queued to any device, when tagged command queuing is
	  possible. The default value is 32. Minimum is 2, maximum is 64.
	  Modern hard disks are able to support 64 tags and even more, but
	  do not seem to be faster when more than 32 tags are being used.

	  So, the normal answer here is to go with the default value 32 unless
	  you are using very large hard disks with large cache (>= 1 MB) that
	  are able to take advantage of more than 32 tagged commands.

	  There is no safe option and the default answer is recommended.

config SCSI_NCR53C8XX_SYNC
	int "synchronous transfers frequency in MHz"
Richard Hirst's avatar
Richard Hirst committed
1127
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON)
1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160
	default "20"
	---help---
	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
	  are respectively the maximum data transfer rates in mega-transfers
	  per second for each class.  For example, a FAST-20 Wide 16 device is
	  able to transfer data at 20 million 16 bit packets per second for a
	  total rate of 40 MB/s.

	  You may specify 0 if you want to only use asynchronous data
	  transfers. This is the safest and slowest option. Otherwise, specify
	  a value between 5 and 80, depending on the capability of your SCSI
	  controller.  The higher the number, the faster the data transfer.
	  Note that 80 should normally be ok since the driver decreases the
	  value automatically according to the controller's capabilities.

	  Your answer to this question is ignored for controllers with NVRAM,
	  since the driver will get this information from the user set-up.  It
	  also can be overridden using a boot setup option, as follows
	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
	  for FAST-20 synchronous data transfer (20 mega-transfers per
	  second).

	  The normal answer therefore is not to go with the default but to
	  select the maximum value 80 allowing the driver to use the maximum
	  value supported by each controller. If this causes problems with
	  your SCSI devices, you should come back and decrease the value.

	  There is no safe option other than using good cabling, right
	  terminations and SCSI conformant devices.

config SCSI_NCR53C8XX_PROFILE
	bool "enable profiling"
Richard Hirst's avatar
Richard Hirst committed
1161
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON)
1162 1163 1164 1165 1166 1167 1168 1169 1170 1171
	help
	  This option allows you to enable profiling information gathering.
	  These statistics are not very accurate due to the low frequency
	  of the kernel clock (100 Hz on i386) and have performance impact
	  on systems that use very fast devices.

	  The normal answer therefore is N.

config SCSI_NCR53C8XX_IOMAPPED
	bool "use normal IO"
Richard Hirst's avatar
Richard Hirst committed
1172
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && !SCSI_ZALON
1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196
	help
	  If you say Y here, the driver will use normal IO, as opposed to
	  memory mapped IO. Memory mapped IO has less latency than normal IO
	  and works for most Intel-based hardware. Under Linux/Alpha only
	  normal IO is currently supported by the driver and so, this option
	  has no effect on those systems.

	  The normal answer therefore is N; try Y only if you encounter SCSI
	  related problems.

config SCSI_NCR53C8XX_PQS_PDS
	bool "include support for the NCR PQS/PDS SCSI card"
	depends on (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && SCSI_SYM53C8XX
	help
	  Say Y here if you have a special SCSI adapter produced by NCR
	  corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
	  this if you do not have one of these adapters. However, since this
	  device is detected as a specific PCI device, this option is quite
	  safe.

	  The common answer here is N, but answering Y is safe.

config SCSI_NCR53C8XX_NO_DISCONNECT
	bool "not allow targets to disconnect"
Richard Hirst's avatar
Richard Hirst committed
1197
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1198 1199 1200 1201 1202 1203 1204 1205 1206
	help
	  This option is only provided for safety if you suspect some SCSI
	  device of yours to not support properly the target-disconnect
	  feature. In that case, you would say Y here. In general however, to
	  not allow targets to disconnect is not reasonable if there is more
	  than 1 device on a SCSI bus. The normal answer therefore is N.

config SCSI_NCR53C8XX_SYMBIOS_COMPAT
	bool "assume boards are SYMBIOS compatible (EXPERIMENTAL)"
Richard Hirst's avatar
Richard Hirst committed
1207
	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX || SCSI_ZALON) && EXPERIMENTAL
1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235
	---help---
	  This option allows you to enable some features depending on GPIO
	  wiring. These General Purpose Input/Output pins can be used for
	  vendor specific features or implementation of the standard SYMBIOS
	  features. Genuine SYMBIOS controllers use GPIO0 in output for
	  controller LED and GPIO3 bit as a flag indicating
	  singled-ended/differential interface. The Tekram DC-390U/F boards
	  uses a different GPIO wiring.

	  Your answer to this question is ignored if all your controllers have
	  NVRAM, since the driver is able to detect the board type from the
	  NVRAM format.

	  If all the controllers in your system are genuine SYMBIOS boards or
	  use BIOS and drivers from SYMBIOS, you would want to say Y here,
	  otherwise N. N is the safe answer.

config SCSI_MCA_53C9X
	tristate "NCR MCA 53C9x SCSI support"
	depends on MCA && SCSI
	help
	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
	  controller based on the NCR 53C94.  This driver will allow use of
	  the controller on the 3550, and very possibly others.

	  If you want to compile this as a module (= code which can be
	  inserted and removed from the running kernel whenever you want), say
	  M here and read <file:Documentation/modules.txt>.  The module will
1236
	  be called mca_53c9x.
1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249

config SCSI_PAS16
	tristate "PAS16 SCSI support"
	depends on SCSI && ISA
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.10 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/pas16.h>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1250
	  The module will be called pas16.  If you want to compile it as a
1251 1252 1253 1254 1255 1256 1257 1258 1259 1260
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_PCI2000
	tristate "PCI2000 support"
	depends on SCSI
	help
	  This is support for the PCI2000I EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

1261
	  This driver is also available as a module called pci2000 ( = code
1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273
	  which can be inserted in and removed from the running kernel
	  whenever you want).  If you want to compile it as a module, say M
	  here and read <file:Documentation/modules.txt>.

config SCSI_PCI2220I
	tristate "PCI2220i support"
	depends on SCSI
	help
	  This is support for the PCI2220i EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

1274
	  This driver is also available as a module called pci2220i ( = code
1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286
	  which can be inserted in and removed from the running kernel
	  whenever you want).  If you want to compile it as a module, say M
	  here and read <file:Documentation/modules.txt>.

config SCSI_PSI240I
	tristate "PSI240i support"
	depends on SCSI && ISA
	help
	  This is support for the PSI240i EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

1287
	  This driver is also available as a module called psi240i ( = code
1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304
	  which can be inserted in and removed from the running kernel
	  whenever you want).  If you want to compile it as a module, say M
	  here and read <file:Documentation/modules.txt>.

config SCSI_QLOGIC_FAS
	tristate "Qlogic FAS SCSI support"
	depends on SCSI && ISA
	---help---
	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
	  FastSCSI! cards as well as any other card based on the FASXX chip
	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).

	  This driver does NOT support the PCI versions of these cards. The
	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
	  SCSI support"), below.

	  Information about this driver is contained in
1305
	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
1306 1307 1308 1309 1310
	  SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1311
	  The module will be called qlogicfas. If you want to compile it as
1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_QLOGIC_ISP
	tristate "Qlogic ISP SCSI support"
	depends on PCI && SCSI
	---help---
	  This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
	  IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card.  (This latter
	  card is supported by the "AM53/79C974 PCI SCSI" driver.)

	  If you say Y here, make sure to choose "BIOS" at the question "PCI
	  access mode".

1325
	  Please read the file <file:Documentation/scsi/qlogicisp.txt>.  You
1326 1327 1328 1329 1330
	  should also read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1331
	  The module will be called qlogicisp.  If you want to compile it as
1332 1333 1334 1335 1336 1337 1338 1339 1340 1341
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_QLOGIC_FC
	tristate "Qlogic ISP FC SCSI support"
	depends on PCI && SCSI
	help
	  This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1342
	  The module will be called qlogicfc.  If you want to compile it as
1343 1344 1345 1346 1347
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_QLOGIC_FC_FIRMWARE
	bool "Include loadable firmware in driver"
	depends on SCSI_QLOGIC_FC
1348 1349 1350 1351
  	help
	  Say Y to include ISP2100 Fabric Initiator/Target Firmware, with
	  expanded LUN addressing and FcTape (FCP-2) support, in the
	  Qlogic QLA 1280 driver. This is required on some platforms.
1352 1353 1354 1355 1356 1357 1358 1359 1360

config SCSI_QLOGIC_1280
	tristate "Qlogic QLA 1280 SCSI support"
	depends on PCI && SCSI
	help
	  Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1361
	  The module will be called qla1280. If you want to compile it as
1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375
	  a module, say M here and read <file:Documentation/modules.txt>.

config SCSI_SEAGATE
	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
	depends on X86 && ISA && SCSI
	---help---
	  These are 8-bit SCSI controllers; the ST-01 is also supported by
	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
	  available from <http://www.linuxdoc.org/docs.html#howto>.  If it
	  doesn't work out of the box, you may have to change some settings in
	  <file:drivers/scsi/seagate.h>.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1376
	  The module will be called seagate.  If you want to compile it as a
1377 1378 1379 1380 1381
	  module, say M here and read <file:Documentation/modules.txt>.

# definitely looks note 64bit safe:
config SCSI_SIM710
	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1382
	depends on (EISA || MCA && !X86_64) && SCSI
1383
	---help---
1384
	  This driver for NCR53c710 based SCSI host adapters.
1385

1386
	  It currently supports Compaq EISA cards and NCR MCA cards
1387

1388 1389 1390 1391
config 53C700_IO_MAPPED
	bool
	depends on SCSI_SIM710
	default y
1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411

config SCSI_SYM53C416
	tristate "Symbios 53c416 SCSI support"
	depends on SCSI && ISA
	---help---
	  This is support for the sym53c416 SCSI host adapter, the SCSI
	  adapter that comes with some HP scanners. This driver requires that
	  the sym53c416 is configured first using some sort of PnP
	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
	  are using isapnp then you need to compile this driver as a module
	  and then load it using insmod after isapnp has run. The parameters
	  of the configured card(s) should be passed to the driver. The format
	  is:

	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]

	  There is support for up to four adapters. If you want to compile
	  this driver as a module ( = code which can be inserted in and
	  removed from the running kernel whenever you want), say M here and
	  read <file:Documentation/modules.txt>. The module will be called
1412
	  sym53c416.
1413 1414 1415 1416 1417 1418 1419 1420 1421

config SCSI_DC390T
	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
	depends on PCI && SCSI
	---help---
	  This driver supports PCI SCSI host adapters based on the Am53C974A
	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
	  PCscsi/PCnet (Am53/79C974) solutions.

1422
	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1423 1424 1425 1426 1427 1428 1429 1430 1431

	  Note that this driver does NOT support Tekram DC390W/U/F, which are
	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
	  Also note that there is another generic Am53C974 driver,
	  "AM53/79C974 PCI SCSI support" below.  You can pick either one.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
1432
	  will be called tmscsim.
1433 1434 1435 1436 1437 1438 1439 1440 1441

config SCSI_DC390T_NOGENSUPP
	bool "_omit_ support for non-DC390 adapters"
	depends on SCSI_DC390T
	---help---
	  If you say N here, the DC390(T) SCSI driver relies on the DC390
	  EEPROM to get initial values for its settings, such as speed,
	  termination, etc.  If it can't find this EEPROM, it will use
	  defaults or the user supplied boot/module parameters.  For details
1442
	  on driver configuration see <file:Documentation/scsi/tmscsim.txt>.
1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464

	  If you say Y here and if no EEPROM is found, the driver gives up and
	  thus only supports Tekram DC390(T) adapters.  This can be useful if
	  you have a DC390(T) and another Am53C974 based adapter, which, for
	  some reason, you want to drive with the other AM53C974 driver.

	  If unsure, say N.

config SCSI_T128
	tristate "Trantor T128/T128F/T228 SCSI support"
	depends on SCSI && ISA
	---help---
	  This is support for a SCSI host adapter. It is explained in section
	  3.11 of the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
	  Adaptec, and some former Trantor products are being sold under the
	  Adaptec name.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1465
	  The module will be called t128.  If you want to compile it as a
1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483
	  module, say M here and read <file:Documentation/modules.txt>.

config SCSI_U14_34F
	tristate "UltraStor 14F/34F support"
	depends on SCSI
	---help---
	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
	  The source at <file:drivers/scsi/u14-34f.c> contains some
	  information about this hardware.  If the driver doesn't work out of
	  the box, you may have to change some settings in
	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  Note that there is also
	  another driver for the same hardware: "UltraStor SCSI support",
	  below.  You should say Y to both only if you want 24F support as
	  well.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
1484
	  The module will be called u14-34f.  If you want to compile it as a
1485 1486
	  module, say M here and read <file:Documentation/modules.txt>.

1487 1488 1489 1490 1491 1492 1493 1494 1495
config SCSI_U14_34F_TAGGED_QUEUE
	bool "enable tagged command queueing"
	depends on SCSI_U14_34F
	help
	  This is a feature of SCSI-2 which improves performance: the host
	  adapter can send several SCSI commands to a device's queue even if
	  previous commands haven't finished yet.
	  This is equivalent to the "u14-34f=tc:y" boot option.

1496 1497 1498 1499 1500 1501 1502 1503
config SCSI_U14_34F_LINKED_COMMANDS
	bool "enable elevator sorting"
	depends on SCSI_U14_34F
	help
	  This option enables elevator sorting for all probed SCSI disks and
	  CD-ROMs. It definitely reduces the average seek distance when doing
	  random seeks, but this does not necessarily result in a noticeable
	  performance improvement: your mileage may vary...
1504
	  This is equivalent to the "u14-34f=lc:y" boot option.
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516

config SCSI_U14_34F_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_U14_34F
	default "8"
	help
	  This specifies how many SCSI commands can be maximally queued for
	  each probed SCSI device. You should reduce the default value of 8
	  only if you have disks with buggy or limited tagged command support.
	  Minimum is 2 and maximum is 14. This value is also the window size
	  used by the elevator sorting option above. The effective value used
	  by the driver for each probed SCSI device is reported at boot time.
1517
	  This is equivalent to the "u14-34f=mq:8" boot option.
1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535

config SCSI_ULTRASTOR
	tristate "UltraStor SCSI support"
	depends on X86 && ISA && SCSI
	---help---
	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
	  adapter family.  This driver is explained in section 3.12 of the
	  SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/ultrastor.h>.

	  Note that there is also another driver for the same hardware:
	  "UltraStor 14F/34F support", above.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
1536
	  will be called ultrastor.
1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548

config SCSI_NSP32
	tristate "Workbit NinjaSCSI-32Bi/UDE support"
	depends on SCSI
	help
	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
	  SCSI host adapter. Please read the SCSI-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
1549
	  will be called nsp32.
1550 1551

config SCSI_DEBUG
1552 1553
	tristate "SCSI debugging host simulator"
	depends on SCSI
1554
	help
1555 1556 1557 1558 1559 1560 1561 1562
	  This is a host adapter simulator that can simulate multiple hosts
	  each with multiple dummy SCSI devices (disks). It defaults to one
	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
	  dummy disks are simulated, they share the same kernel RAM for 
	  their storage. See http://www.torque.net/sg/sdebug.html for more
	  information. This driver is primarily of use to those testing the
	  SCSI and block subsystems. If unsure, say N.
1563 1564 1565 1566 1567 1568 1569 1570

config SCSI_MESH
	tristate "MESH (Power Mac internal SCSI) support"
	depends on ALL_PPC && SCSI
	help
	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
	  other Power Macintoshes do). Say Y to include support for this SCSI
1571
	  adaptor. This driver is also available as a module called mesh
1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603
	  ( = code which can be inserted in and removed from the running
	  kernel whenever you want). If you want to compile it as a module,
	  say M here and read <file:Documentation/modules.txt>.

config SCSI_MESH_SYNC_RATE
	int "maximum synchronous transfer rate (MB/s) (0 = async)"
	depends on SCSI_MESH
	default "5"
	help
	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
	  drives a bus which is entirely internal to the machine (such as the
	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
	  operation at up to 10 MB/s. On machines where the SCSI bus
	  controlled by the MESH can have external devices connected, it is
	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
	  to disable synchronous operation.

config SCSI_MESH_RESET_DELAY_MS
	int "initial bus reset delay (ms) (0 = no reset)"
	depends on SCSI_MESH
	default "4000"

config SCSI_MAC53C94
	tristate "53C94 (Power Mac external SCSI) support"
	depends on ALL_PPC && SCSI
	help
	  On Power Macintoshes (and clones) with two SCSI buses, the external
	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
	  machines which only have one SCSI bus, such as the 7200, also use
	  the 53C94. Say Y to include support for the 53C94.

1604
	  This driver is also available as a module called mac53c94 ( = code
1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626
	  which can be inserted in and removed from the running kernel
	  whenever you want). If you want to compile it as a module, say M
	  here and read <file:Documentation/modules.txt>.

source "drivers/acorn/scsi/Kconfig"

config JAZZ_ESP
	bool "MIPS JAZZ FAS216 SCSI support"
	depends on MIPS_JAZZ
	help
	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
	  systems.

config A3000_SCSI
	tristate "A3000 WD33C93A support"
	depends on AMIGA && SCSI
	help
	  If you have an Amiga 3000 and have SCSI devices connected to the
	  built-in SCSI controller, say Y. Otherwise, say N. This driver is
	  also available as a module ( = code which can be inserted in and
	  removed from the running kernel whenever you want). The module is
1627
	  called wd33c93. If you want to compile it as a module, say M here
1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642
	  and read <file:Documentation/modules.txt>.

config A4000T_SCSI
	bool "A4000T SCSI support (EXPERIMENTAL)"
	depends on AMIGA && EXPERIMENTAL
	help
	  Support for the NCR53C710 SCSI controller on the Amiga 4000T.

config A2091_SCSI
	tristate "A2091/A590 WD33C93A support"
	depends on ZORRO && SCSI
	help
	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
	  say N. This driver is also available as a module ( = code which can
	  be inserted in and removed from the running kernel whenever you
1643
	  want). The module is called wd33c93. If you want to compile it as
1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657
	  a module, say M here and read <file:Documentation/modules.txt>.

config GVP11_SCSI
	tristate "GVP Series II WD33C93A support"
	depends on ZORRO && SCSI
	---help---
	  If you have a Great Valley Products Series II SCSI controller,
	  answer Y. Also say Y if you have a later model of GVP SCSI
	  controller (such as the GVP A4008 or a Combo board). Otherwise,
	  answer N. This driver does NOT work for the T-Rex series of
	  accelerators from TekMagic and GVP-M.

	  This driver is also available as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you
1658
	  want). The module will be called gvp11. If you want to compile it
1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737
	  as a module, say M here and read <file:Documentation/modules.txt>.

config CYBERSTORM_SCSI
	tristate "CyberStorm SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
	  accelerator board and the optional Cyberstorm SCSI controller,
	  answer Y. Otherwise, say N.

config CYBERSTORMII_SCSI
	tristate "CyberStorm Mk II SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
	  answer N.

config BLZ2060_SCSI
	tristate "Blizzard 2060 SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
	  and want to use the onboard SCSI controller, say Y. Otherwise,
	  answer N.

config BLZ1230_SCSI
	tristate "Blizzard 1230IV/1260 SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
	  say N.

config FASTLANE_SCSI
	tristate "Fastlane SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
	  one in the near future, say Y to this question. Otherwise, say N.

config A4091_SCSI
	bool "A4091 SCSI support (EXPERIMENTAL)"
	depends on ZORRO && EXPERIMENTAL
	help
	  Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller
	  (1993).  Very obscure -- the 4091 was part of an Amiga 4000 upgrade
	  plan at the time the Amiga business was sold to DKB.

config WARPENGINE_SCSI
	bool "WarpEngine SCSI support (EXPERIMENTAL)"
	depends on ZORRO && EXPERIMENTAL
	help
	  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
	  controller. Info at
	  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.

config BLZ603EPLUS_SCSI
	bool "Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)"
	depends on ZORRO && EXPERIMENTAL
	help
	  If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
	  accelerator, say Y. Otherwise, say N.

config OKTAGON_SCSI
	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
	depends on ZORRO && EXPERIMENTAL && SCSI
	help
	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
	  Y to this question.  If you're in doubt about whether you have one,
	  see the picture at
	  <http://amiga.multigraph.com/photos/oktagon.html>.

#      bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
#      bool 'GVP Turbo 040/060 SCSI support (EXPERIMENTAL)' CONFIG_GVP_TURBO_SCSI
endmenu

source "drivers/scsi/pcmcia/Kconfig"