2 menu "I2O device support"
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.
19 If you say Y here, you will get a choice of interface adapter
20 drivers and OSM's with the following questions.
22 To compile this support as a module, choose M here: the
23 modules will be called i2o_core.
27 config I2O_EXT_ADAPTEC
28 bool "Enable Adaptec extensions"
32 Say Y for support of raidutils for Adaptec I2O controllers. You also
33 have to say Y to "I2O Configuration support", "I2O SCSI OSM" below
34 and to "SCSI generic support" under "SCSI device configuration".
36 config I2O_EXT_ADAPTEC_DMA64
37 bool "Enable 64-bit DMA"
38 depends on I2O_EXT_ADAPTEC && ( 64BIT || HIGHMEM64G )
41 Say Y for support of 64-bit DMA transfer mode on Adaptec I2O
43 Note: You need at least firmware version 3709.
46 tristate "I2O Configuration support"
49 Say Y for support of the configuration interface for the I2O adapters.
50 If you have a RAID controller from Adaptec and you want to use the
51 raidutils to manage your RAID array, you have to say Y here.
53 To compile this support as a module, choose M here: the
54 module will be called i2o_config.
56 Note: If you want to use the new API you have to download the
57 i2o_config patch from http://i2o.shadowconnect.com/
59 config I2O_CONFIG_OLD_IOCTL
60 bool "Enable ioctls (OBSOLETE)"
67 tristate "I2O Bus Adapter OSM"
70 Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM
71 provides access to the busses on the I2O controller. The main purpose
72 is to rescan the bus to find new devices.
74 To compile this support as a module, choose M here: the
75 module will be called i2o_bus.
78 tristate "I2O Block OSM"
81 Include support for the I2O Block OSM. The Block OSM presents disk
82 and other structured block devices to the operating system. If you
83 are using an RAID controller, you could access the array only by
84 the Block OSM driver. But it is possible to access the single disks
85 by the SCSI OSM driver, for example to monitor the disks.
87 To compile this support as a module, choose M here: the
88 module will be called i2o_block.
91 tristate "I2O SCSI OSM"
92 depends on I2O && SCSI
94 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
95 I2O controller. You can use both the SCSI and Block OSM together if
96 you wish. To access a RAID array, you must use the Block OSM driver.
97 But you could use the SCSI OSM driver to monitor the single disks.
99 To compile this support as a module, choose M here: the
100 module will be called i2o_scsi.
103 tristate "I2O /proc support"
106 If you say Y here and to "/proc file system support", you will be
107 able to read I2O related information from the virtual directory
110 To compile this support as a module, choose M here: the
111 module will be called i2o_proc.