Kconfig 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  1. menu "I2O device support"
  2. depends on PCI
  3. config I2O
  4. tristate "I2O support"
  5. depends on PCI
  6. ---help---
  7. The Intelligent Input/Output (I2O) architecture allows hardware
  8. drivers to be split into two parts: an operating system specific
  9. module called the OSM and an hardware specific module called the
  10. HDM. The OSM can talk to a whole range of HDM's, and ideally the
  11. HDM's are not OS dependent. This allows for the same HDM driver to
  12. be used under different operating systems if the relevant OSM is in
  13. place. In order for this to work, you need to have an I2O interface
  14. adapter card in your computer. This card contains a special I/O
  15. processor (IOP), thus allowing high speeds since the CPU does not
  16. have to deal with I/O.
  17. If you say Y here, you will get a choice of interface adapter
  18. drivers and OSM's with the following questions.
  19. To compile this support as a module, choose M here: the
  20. modules will be called i2o_core.
  21. If unsure, say N.
  22. config I2O_LCT_NOTIFY_ON_CHANGES
  23. bool "Enable LCT notification"
  24. depends on I2O
  25. default y
  26. ---help---
  27. Only say N here if you have a I2O controller from SUN. The SUN
  28. firmware doesn't support LCT notification on changes. If this option
  29. is enabled on such a controller the driver will hang up in a endless
  30. loop. On all other controllers say Y.
  31. If unsure, say Y.
  32. config I2O_EXT_ADAPTEC
  33. bool "Enable Adaptec extensions"
  34. depends on I2O
  35. default y
  36. ---help---
  37. Say Y for support of raidutils for Adaptec I2O controllers. You also
  38. have to say Y to "I2O Configuration support", "I2O SCSI OSM" below
  39. and to "SCSI generic support" under "SCSI device configuration".
  40. config I2O_EXT_ADAPTEC_DMA64
  41. bool "Enable 64-bit DMA"
  42. depends on I2O_EXT_ADAPTEC && ( 64BIT || HIGHMEM64G )
  43. default y
  44. ---help---
  45. Say Y for support of 64-bit DMA transfer mode on Adaptec I2O
  46. controllers.
  47. Note: You need at least firmware version 3709.
  48. config I2O_CONFIG
  49. tristate "I2O Configuration support"
  50. depends on I2O
  51. ---help---
  52. Say Y for support of the configuration interface for the I2O adapters.
  53. If you have a RAID controller from Adaptec and you want to use the
  54. raidutils to manage your RAID array, you have to say Y here.
  55. To compile this support as a module, choose M here: the
  56. module will be called i2o_config.
  57. Note: If you want to use the new API you have to download the
  58. i2o_config patch from http://i2o.shadowconnect.com/
  59. config I2O_CONFIG_OLD_IOCTL
  60. bool "Enable ioctls (OBSOLETE)"
  61. depends on I2O_CONFIG
  62. default y
  63. ---help---
  64. Enables old ioctls.
  65. config I2O_BUS
  66. tristate "I2O Bus Adapter OSM"
  67. depends on I2O
  68. ---help---
  69. Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM
  70. provides access to the busses on the I2O controller. The main purpose
  71. is to rescan the bus to find new devices.
  72. To compile this support as a module, choose M here: the
  73. module will be called i2o_bus.
  74. config I2O_BLOCK
  75. tristate "I2O Block OSM"
  76. depends on I2O && BLOCK
  77. ---help---
  78. Include support for the I2O Block OSM. The Block OSM presents disk
  79. and other structured block devices to the operating system. If you
  80. are using an RAID controller, you could access the array only by
  81. the Block OSM driver. But it is possible to access the single disks
  82. by the SCSI OSM driver, for example to monitor the disks.
  83. To compile this support as a module, choose M here: the
  84. module will be called i2o_block.
  85. config I2O_SCSI
  86. tristate "I2O SCSI OSM"
  87. depends on I2O && SCSI
  88. ---help---
  89. Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  90. I2O controller. You can use both the SCSI and Block OSM together if
  91. you wish. To access a RAID array, you must use the Block OSM driver.
  92. But you could use the SCSI OSM driver to monitor the single disks.
  93. To compile this support as a module, choose M here: the
  94. module will be called i2o_scsi.
  95. config I2O_PROC
  96. tristate "I2O /proc support"
  97. depends on I2O
  98. ---help---
  99. If you say Y here and to "/proc file system support", you will be
  100. able to read I2O related information from the virtual directory
  101. /proc/i2o.
  102. To compile this support as a module, choose M here: the
  103. module will be called i2o_proc.
  104. endmenu