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