Linux Audio

Check our new training course

Loading...
Note: File does not exist in v4.6.
  1================================================
  2Comtrol(tm) RocketPort(R)/RocketModem(TM) Series
  3================================================
  4
  5Device Driver for the Linux Operating System
  6============================================
  7
  8Product overview
  9----------------
 10
 11This driver provides a loadable kernel driver for the Comtrol RocketPort
 12and RocketModem PCI boards. These boards provide, 2, 4, 8, 16, or 32
 13high-speed serial ports or modems.  This driver supports up to a combination
 14of four RocketPort or RocketModems boards in one machine simultaneously.
 15This file assumes that you are using the RocketPort driver which is
 16integrated into the kernel sources.
 17
 18The driver can also be installed as an external module using the usual
 19"make;make install" routine.  This external module driver, obtainable
 20from the Comtrol website listed below, is useful for updating the driver
 21or installing it into kernels which do not have the driver configured
 22into them.  Installations instructions for the external module
 23are in the included README and HW_INSTALL files.
 24
 25RocketPort ISA and RocketModem II PCI boards currently are only supported by
 26this driver in module form.
 27
 28The RocketPort ISA board requires I/O ports to be configured by the DIP
 29switches on the board.  See the section "ISA Rocketport Boards" below for
 30information on how to set the DIP switches.
 31
 32You pass the I/O port to the driver using the following module parameters:
 33
 34board1:
 35	I/O port for the first ISA board
 36board2:
 37	I/O port for the second ISA board
 38board3:
 39	I/O port for the third ISA board
 40board4:
 41	I/O port for the fourth ISA board
 42
 43There is a set of utilities and scripts provided with the external driver
 44(downloadable from http://www.comtrol.com) that ease the configuration and
 45setup of the ISA cards.
 46
 47The RocketModem II PCI boards require firmware to be loaded into the card
 48before it will function.  The driver has only been tested as a module for this
 49board.
 50
 51Installation Procedures
 52-----------------------
 53
 54RocketPort/RocketModem PCI cards require no driver configuration, they are
 55automatically detected and configured.
 56
 57The RocketPort driver can be installed as a module (recommended) or built
 58into the kernel. This is selected, as for other drivers, through the `make config`
 59command from the root of the Linux source tree during the kernel build process.
 60
 61The RocketPort/RocketModem serial ports installed by this driver are assigned
 62device major number 46, and will be named /dev/ttyRx, where x is the port number
 63starting at zero (ex. /dev/ttyR0, /devttyR1, ...).  If you have multiple cards
 64installed in the system, the mapping of port names to serial ports is displayed
 65in the system log at /var/log/messages.
 66
 67If installed as a module, the module must be loaded.  This can be done
 68manually by entering "modprobe rocket".  To have the module loaded automatically
 69upon system boot, edit a `/etc/modprobe.d/*.conf` file and add the line
 70"alias char-major-46 rocket".
 71
 72In order to use the ports, their device names (nodes) must be created with mknod.
 73This is only required once, the system will retain the names once created.  To
 74create the RocketPort/RocketModem device names, use the command
 75"mknod /dev/ttyRx c 46 x" where x is the port number starting at zero.
 76
 77For example::
 78
 79	> mknod /dev/ttyR0 c 46 0
 80	> mknod /dev/ttyR1 c 46 1
 81	> mknod /dev/ttyR2 c 46 2
 82
 83The Linux script MAKEDEV will create the first 16 ttyRx device names (nodes)
 84for you::
 85
 86	>/dev/MAKEDEV ttyR
 87
 88ISA Rocketport Boards
 89---------------------
 90
 91You must assign and configure the I/O addresses used by the ISA Rocketport
 92card before installing and using it.  This is done by setting a set of DIP
 93switches on the Rocketport board.
 94
 95
 96Setting the I/O address
 97-----------------------
 98
 99Before installing RocketPort(R) or RocketPort RA boards, you must find
100a range of I/O addresses for it to use. The first RocketPort card
101requires a 68-byte contiguous block of I/O addresses, starting at one
102of the following: 0x100h, 0x140h, 0x180h, 0x200h, 0x240h, 0x280h,
1030x300h, 0x340h, 0x380h.  This I/O address must be reflected in the DIP
104switches of *all* of the Rocketport cards.
105
106The second, third, and fourth RocketPort cards require a 64-byte
107contiguous block of I/O addresses, starting at one of the following
108I/O addresses: 0x100h, 0x140h, 0x180h, 0x1C0h, 0x200h, 0x240h, 0x280h,
1090x2C0h, 0x300h, 0x340h, 0x380h, 0x3C0h.  The I/O address used by the
110second, third, and fourth Rocketport cards (if present) are set via
111software control.  The DIP switch settings for the I/O address must be
112set to the value of the first Rocketport cards.
113
114In order to distinguish each of the card from the others, each card
115must have a unique board ID set on the dip switches.  The first
116Rocketport board must be set with the DIP switches corresponding to
117the first board, the second board must be set with the DIP switches
118corresponding to the second board, etc.  IMPORTANT: The board ID is
119the only place where the DIP switch settings should differ between the
120various Rocketport boards in a system.
121
122The I/O address range used by any of the RocketPort cards must not
123conflict with any other cards in the system, including other
124RocketPort cards.  Below, you will find a list of commonly used I/O
125address ranges which may be in use by other devices in your system.
126On a Linux system, "cat /proc/ioports" will also be helpful in
127identifying what I/O addresses are being used by devices on your
128system.
129
130Remember, the FIRST RocketPort uses 68 I/O addresses.  So, if you set it
131for 0x100, it will occupy 0x100 to 0x143.  This would mean that you
132CAN NOT set the second, third or fourth board for address 0x140 since
133the first 4 bytes of that range are used by the first board.  You would
134need to set the second, third, or fourth board to one of the next available
135blocks such as 0x180.
136
137RocketPort and RocketPort RA SW1 Settings::
138
139            +-------------------------------+
140            | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
141            +-------+-------+---------------+
142            | Unused| Card  | I/O Port Block|
143            +-------------------------------+
144
145  DIP Switches                             DIP Switches
146  7    8                                   6    5
147  ===================                      ===================
148  On   On   UNUSED, MUST BE ON.            On   On   First Card    <==== Default
149                                           On   Off  Second Card
150                                           Off  On   Third Card
151                                           Off  Off  Fourth Card
152
153  DIP Switches         I/O Address Range
154  4    3    2    1     Used by the First Card
155  =====================================
156  On   Off  On   Off   100-143
157  On   Off  Off  On    140-183
158  On   Off  Off  Off   180-1C3       <==== Default
159  Off  On   On   Off   200-243
160  Off  On   Off  On    240-283
161  Off  On   Off  Off   280-2C3
162  Off  Off  On   Off   300-343
163  Off  Off  Off  On    340-383
164  Off  Off  Off  Off   380-3C3
165
166Reporting Bugs
167--------------
168
169For technical support, please provide the following
170information: Driver version, kernel release, distribution of
171kernel, and type of board you are using. Error messages and log
172printouts port configuration details are especially helpful.
173
174USA:
175    :Phone: (612) 494-4100
176    :FAX: (612) 494-4199
177    :email: support@comtrol.com
178
179Comtrol Europe:
180    :Phone: +44 (0) 1 869 323-220
181    :FAX: +44 (0) 1 869 323-211
182    :email: support@comtrol.co.uk
183
184Web:	http://www.comtrol.com
185FTP:	ftp.comtrol.com