Kconfig 51 KB

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