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