Kconfig 4.1 KB

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