Kconfig 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  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_CONFIG
  22. tristate "I2O Configuration support"
  23. depends on PCI && I2O
  24. help
  25. Say Y for support of the configuration interface for the I2O adapters.
  26. If you have a RAID controller from Adaptec and you want to use the
  27. raidutils to manage your RAID array, you have to say Y here.
  28. To compile this support as a module, choose M here: the
  29. module will be called i2o_config.
  30. config I2O_CONFIG_OLD_IOCTL
  31. bool "Enable ioctls (OBSOLETE)"
  32. depends on I2O_CONFIG
  33. default y
  34. ---help---
  35. Enables old ioctls.
  36. config I2O_BUS
  37. tristate "I2O Bus Adapter OSM"
  38. depends on I2O
  39. ---help---
  40. Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM
  41. provides access to the busses on the I2O controller. The main purpose
  42. is to rescan the bus to find new devices.
  43. To compile this support as a module, choose M here: the
  44. module will be called i2o_bus.
  45. config I2O_BLOCK
  46. tristate "I2O Block OSM"
  47. depends on I2O
  48. help
  49. Include support for the I2O Block OSM. The Block OSM presents disk
  50. and other structured block devices to the operating system. If you
  51. are using an RAID controller, you could access the array only by
  52. the Block OSM driver. But it is possible to access the single disks
  53. by the SCSI OSM driver, for example to monitor the disks.
  54. To compile this support as a module, choose M here: the
  55. module will be called i2o_block.
  56. config I2O_SCSI
  57. tristate "I2O SCSI OSM"
  58. depends on I2O && SCSI
  59. help
  60. Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  61. I2O controller. You can use both the SCSI and Block OSM together if
  62. you wish. To access a RAID array, you must use the Block OSM driver.
  63. But you could use the SCSI OSM driver to monitor the single disks.
  64. To compile this support as a module, choose M here: the
  65. module will be called i2o_scsi.
  66. config I2O_PROC
  67. tristate "I2O /proc support"
  68. depends on I2O
  69. help
  70. If you say Y here and to "/proc file system support", you will be
  71. able to read I2O related information from the virtual directory
  72. /proc/i2o.
  73. To compile this support as a module, choose M here: the
  74. module will be called i2o_proc.
  75. endmenu