Kconfig 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119
  1. menu "Fusion MPT device support"
  2. depends on PCI
  3. config FUSION
  4. bool
  5. default n
  6. config FUSION_SPI
  7. tristate "Fusion MPT ScsiHost drivers for SPI"
  8. depends on PCI && SCSI
  9. select FUSION
  10. select SCSI_SPI_ATTRS
  11. ---help---
  12. SCSI HOST support for a parallel SCSI host adapters.
  13. List of supported controllers:
  14. LSI53C1020
  15. LSI53C1020A
  16. LSI53C1030
  17. LSI53C1035
  18. config FUSION_FC
  19. tristate "Fusion MPT ScsiHost drivers for FC"
  20. depends on PCI && SCSI
  21. select FUSION
  22. select SCSI_FC_ATTRS
  23. ---help---
  24. SCSI HOST support for a Fiber Channel host adapters.
  25. List of supported controllers:
  26. LSIFC909
  27. LSIFC919
  28. LSIFC919X
  29. LSIFC929
  30. LSIFC929X
  31. LSIFC929XL
  32. Brocade FC 410/420
  33. config FUSION_SAS
  34. tristate "Fusion MPT ScsiHost drivers for SAS"
  35. depends on PCI && SCSI
  36. select FUSION
  37. select SCSI_SAS_ATTRS
  38. ---help---
  39. SCSI HOST support for a SAS host adapters.
  40. List of supported controllers:
  41. LSISAS1064
  42. LSISAS1068
  43. LSISAS1064E
  44. LSISAS1068E
  45. config FUSION_MAX_SGE
  46. int "Maximum number of scatter gather entries (16 - 128)"
  47. depends on FUSION
  48. default "128"
  49. range 16 128
  50. help
  51. This option allows you to specify the maximum number of scatter-
  52. gather entries per I/O. The driver default is 128, which matches
  53. SCSI_MAX_PHYS_SEGMENTS. However, it may decreased down to 16.
  54. Decreasing this parameter will reduce memory requirements
  55. on a per controller instance.
  56. config FUSION_CTL
  57. tristate "Fusion MPT misc device (ioctl) driver"
  58. depends on FUSION_SPI || FUSION_FC || FUSION_SAS
  59. ---help---
  60. The Fusion MPT misc device driver provides specialized control
  61. of MPT adapters via system ioctl calls. Use of ioctl calls to
  62. the MPT driver requires that you create and use a misc device
  63. node ala:
  64. mknod /dev/mptctl c 10 240
  65. One use of this ioctl interface is to perform an upgrade (reflash)
  66. of the MPT adapter firmware. Refer to readme file(s) distributed
  67. with the Fusion MPT linux driver for additional details.
  68. If enabled by saying M to this, a driver named: mptctl
  69. will be compiled.
  70. If unsure whether you really want or need this, say N.
  71. config FUSION_LAN
  72. tristate "Fusion MPT LAN driver"
  73. depends on FUSION_FC && NET_FC
  74. ---help---
  75. This module supports LAN IP traffic over Fibre Channel port(s)
  76. on Fusion MPT compatible hardware (LSIFC9xx chips).
  77. The physical interface used is defined in RFC 2625.
  78. Please refer to that document for details.
  79. Installing this driver requires the knowledge to configure and
  80. activate a new network interface, "fc0", using standard Linux tools.
  81. If enabled by saying M to this, a driver named: mptlan
  82. will be compiled.
  83. If unsure whether you really want or need this, say N.
  84. config FUSION_LOGGING
  85. bool "Fusion MPT logging facility"
  86. depends on FUSION
  87. ---help---
  88. This turns on a logging facility that can be used to debug a number
  89. of Fusion MPT related problems.
  90. The debug level can be programmed on the fly via SysFS (hex values)
  91. echo [level] > /sys/class/scsi_host/host#/debug_level
  92. There are various debug levels that an be found in the source:
  93. file:drivers/message/fusion/mptdebug.h
  94. endmenu