Kconfig 4.0 KB

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