| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | |
| 2 | menu "I2O device support" |
| 3 | |
| 4 | config I2O |
| 5 | tristate "I2O support" |
| 6 | depends on PCI |
| 7 | ---help--- |
| 8 | The Intelligent Input/Output (I2O) architecture allows hardware |
| 9 | drivers to be split into two parts: an operating system specific |
| 10 | module called the OSM and an hardware specific module called the |
| 11 | HDM. The OSM can talk to a whole range of HDM's, and ideally the |
| 12 | HDM's are not OS dependent. This allows for the same HDM driver to |
| 13 | be used under different operating systems if the relevant OSM is in |
| 14 | place. In order for this to work, you need to have an I2O interface |
| 15 | adapter card in your computer. This card contains a special I/O |
| 16 | processor (IOP), thus allowing high speeds since the CPU does not |
| 17 | have to deal with I/O. |
| 18 | |
| 19 | If you say Y here, you will get a choice of interface adapter |
| 20 | drivers and OSM's with the following questions. |
| 21 | |
| 22 | To compile this support as a module, choose M here: the |
| 23 | modules will be called i2o_core. |
| 24 | |
| 25 | If unsure, say N. |
| 26 | |
| 27 | config I2O_CONFIG |
| 28 | tristate "I2O Configuration support" |
| 29 | depends on PCI && I2O |
| 30 | help |
| 31 | Say Y for support of the configuration interface for the I2O adapters. |
| 32 | If you have a RAID controller from Adaptec and you want to use the |
| 33 | raidutils to manage your RAID array, you have to say Y here. |
| 34 | |
| 35 | To compile this support as a module, choose M here: the |
| 36 | module will be called i2o_config. |
| 37 | |
| 38 | config I2O_BLOCK |
| 39 | tristate "I2O Block OSM" |
| 40 | depends on I2O |
| 41 | help |
| 42 | Include support for the I2O Block OSM. The Block OSM presents disk |
| 43 | and other structured block devices to the operating system. If you |
| 44 | are using an RAID controller, you could access the array only by |
| 45 | the Block OSM driver. But it is possible to access the single disks |
| 46 | by the SCSI OSM driver, for example to monitor the disks. |
| 47 | |
| 48 | To compile this support as a module, choose M here: the |
| 49 | module will be called i2o_block. |
| 50 | |
| 51 | config I2O_SCSI |
| 52 | tristate "I2O SCSI OSM" |
| 53 | depends on I2O && SCSI |
| 54 | help |
| 55 | Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel |
| 56 | I2O controller. You can use both the SCSI and Block OSM together if |
| 57 | you wish. To access a RAID array, you must use the Block OSM driver. |
| 58 | But you could use the SCSI OSM driver to monitor the single disks. |
| 59 | |
| 60 | To compile this support as a module, choose M here: the |
| 61 | module will be called i2o_scsi. |
| 62 | |
| 63 | config I2O_PROC |
| 64 | tristate "I2O /proc support" |
| 65 | depends on I2O |
| 66 | help |
| 67 | If you say Y here and to "/proc file system support", you will be |
| 68 | able to read I2O related information from the virtual directory |
| 69 | /proc/i2o. |
| 70 | |
| 71 | To compile this support as a module, choose M here: the |
| 72 | module will be called i2o_proc. |
| 73 | |
| 74 | endmenu |
| 75 | |