]>
Commit | Line | Data |
---|---|---|
1da177e4 | 1 | |
04e9aeec JE |
2 | menuconfig I2O |
3 | tristate "I2O device support" | |
1da177e4 LT |
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 | ||
17 | If you say Y here, you will get a choice of interface adapter | |
18 | drivers and OSM's with the following questions. | |
19 | ||
20 | To compile this support as a module, choose M here: the | |
21 | modules will be called i2o_core. | |
22 | ||
23 | If unsure, say N. | |
24 | ||
04e9aeec JE |
25 | if I2O |
26 | ||
793fd15d ML |
27 | config I2O_LCT_NOTIFY_ON_CHANGES |
28 | bool "Enable LCT notification" | |
793fd15d ML |
29 | default y |
30 | ---help--- | |
31 | Only say N here if you have a I2O controller from SUN. The SUN | |
32 | firmware doesn't support LCT notification on changes. If this option | |
33 | is enabled on such a controller the driver will hang up in a endless | |
34 | loop. On all other controllers say Y. | |
35 | ||
36 | If unsure, say Y. | |
37 | ||
b2aaee33 ML |
38 | config I2O_EXT_ADAPTEC |
39 | bool "Enable Adaptec extensions" | |
b2aaee33 ML |
40 | default y |
41 | ---help--- | |
42 | Say Y for support of raidutils for Adaptec I2O controllers. You also | |
43 | have to say Y to "I2O Configuration support", "I2O SCSI OSM" below | |
44 | and to "SCSI generic support" under "SCSI device configuration". | |
45 | ||
46 | config I2O_EXT_ADAPTEC_DMA64 | |
47 | bool "Enable 64-bit DMA" | |
48 | depends on I2O_EXT_ADAPTEC && ( 64BIT || HIGHMEM64G ) | |
49 | default y | |
50 | ---help--- | |
51 | Say Y for support of 64-bit DMA transfer mode on Adaptec I2O | |
52 | controllers. | |
53 | Note: You need at least firmware version 3709. | |
54 | ||
1da177e4 LT |
55 | config I2O_CONFIG |
56 | tristate "I2O Configuration support" | |
f057eac0 | 57 | depends on VIRT_TO_BUS |
f33213ec | 58 | ---help--- |
1da177e4 LT |
59 | Say Y for support of the configuration interface for the I2O adapters. |
60 | If you have a RAID controller from Adaptec and you want to use the | |
61 | raidutils to manage your RAID array, you have to say Y here. | |
62 | ||
63 | To compile this support as a module, choose M here: the | |
64 | module will be called i2o_config. | |
65 | ||
db29e85a ML |
66 | Note: If you want to use the new API you have to download the |
67 | i2o_config patch from http://i2o.shadowconnect.com/ | |
68 | ||
f10378ff ML |
69 | config I2O_CONFIG_OLD_IOCTL |
70 | bool "Enable ioctls (OBSOLETE)" | |
71 | depends on I2O_CONFIG | |
72 | default y | |
73 | ---help--- | |
74 | Enables old ioctls. | |
75 | ||
76 | config I2O_BUS | |
77 | tristate "I2O Bus Adapter OSM" | |
f10378ff ML |
78 | ---help--- |
79 | Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM | |
80 | provides access to the busses on the I2O controller. The main purpose | |
81 | is to rescan the bus to find new devices. | |
82 | ||
83 | To compile this support as a module, choose M here: the | |
84 | module will be called i2o_bus. | |
85 | ||
1da177e4 LT |
86 | config I2O_BLOCK |
87 | tristate "I2O Block OSM" | |
04e9aeec | 88 | depends on BLOCK |
f33213ec | 89 | ---help--- |
1da177e4 LT |
90 | Include support for the I2O Block OSM. The Block OSM presents disk |
91 | and other structured block devices to the operating system. If you | |
92 | are using an RAID controller, you could access the array only by | |
93 | the Block OSM driver. But it is possible to access the single disks | |
94 | by the SCSI OSM driver, for example to monitor the disks. | |
95 | ||
96 | To compile this support as a module, choose M here: the | |
97 | module will be called i2o_block. | |
98 | ||
99 | config I2O_SCSI | |
100 | tristate "I2O SCSI OSM" | |
04e9aeec | 101 | depends on SCSI |
f33213ec | 102 | ---help--- |
1da177e4 LT |
103 | Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel |
104 | I2O controller. You can use both the SCSI and Block OSM together if | |
105 | you wish. To access a RAID array, you must use the Block OSM driver. | |
106 | But you could use the SCSI OSM driver to monitor the single disks. | |
107 | ||
108 | To compile this support as a module, choose M here: the | |
109 | module will be called i2o_scsi. | |
110 | ||
111 | config I2O_PROC | |
112 | tristate "I2O /proc support" | |
f33213ec | 113 | ---help--- |
1da177e4 LT |
114 | If you say Y here and to "/proc file system support", you will be |
115 | able to read I2O related information from the virtual directory | |
116 | /proc/i2o. | |
117 | ||
118 | To compile this support as a module, choose M here: the | |
119 | module will be called i2o_proc. | |
120 | ||
04e9aeec | 121 | endif # I2O |