Lines Matching refs:the
2 Device Driver for the Linux Operating System
9 This driver provides a loadable kernel driver for the Comtrol RocketPort
13 This file assumes that you are using the RocketPort driver which is
14 integrated into the kernel sources.
16 The driver can also be installed as an external module using the usual
18 from the Comtrol website listed below, is useful for updating the driver
19 or installing it into kernels which do not have the driver configured
20 into them. Installations instructions for the external module
21 are in the included README and HW_INSTALL files.
26 The RocketPort ISA board requires I/O ports to be configured by the DIP
27 switches on the board. See the section "ISA Rocketport Boards" below for
28 information on how to set the DIP switches.
30 You pass the I/O port to the driver using the following module parameters:
32 board1 : I/O port for the first ISA board
33 board2 : I/O port for the second ISA board
34 board3 : I/O port for the third ISA board
35 board4 : I/O port for the fourth ISA board
37 There is a set of utilities and scripts provided with the external driver
38 ( downloadable from http://www.comtrol.com ) that ease the configuration and
39 setup of the ISA cards.
41 The RocketModem II PCI boards require firmware to be loaded into the card
54 into the kernel. This is selected, as for other drivers, through the `make config`
55 command from the root of the Linux source tree during the kernel build process.
58 device major number 46, and will be named /dev/ttyRx, where x is the port number
60 installed in the system, the mapping of port names to serial ports is displayed
61 in the system log at /var/log/messages.
63 If installed as a module, the module must be loaded. This can be done
64 manually by entering "modprobe rocket". To have the module loaded automatically
65 upon system boot, edit a /etc/modprobe.d/*.conf file and add the line
68 In order to use the ports, their device names (nodes) must be created with mknod.
69 This is only required once, the system will retain the names once created. To
70 create the RocketPort/RocketModem device names, use the command
71 "mknod /dev/ttyRx c 46 x" where x is the port number starting at zero. For example:
77 The Linux script MAKEDEV will create the first 16 ttyRx device names (nodes)
87 You must assign and configure the I/O addresses used by the ISA Rocketport
89 switches on the Rocketport board.
98 of the following: 0x100h, 0x140h, 0x180h, 0x200h, 0x240h, 0x280h,
99 0x300h, 0x340h, 0x380h. This I/O address must be reflected in the DIP
100 switches of *all* of the Rocketport cards.
103 contiguous block of I/O addresses, starting at one of the following
105 0x2C0h, 0x300h, 0x340h, 0x380h, 0x3C0h. The I/O address used by the
107 software control. The DIP switch settings for the I/O address must be
108 set to the value of the first Rocketport cards.
110 In order to distinguish each of the card from the others, each card
111 must have a unique board ID set on the dip switches. The first
112 Rocketport board must be set with the DIP switches corresponding to
113 the first board, the second board must be set with the DIP switches
114 corresponding to the second board, etc. IMPORTANT: The board ID is
115 the only place where the DIP switch settings should differ between the
118 The I/O address range used by any of the RocketPort cards must not
119 conflict with any other cards in the system, including other
126 Remember, the FIRST RocketPort uses 68 I/O addresses. So, if you set it
128 CAN NOT set the second, third or fourth board for address 0x140 since
129 the first 4 bytes of that range are used by the first board. You would
130 need to set the second, third, or fourth board to one of the next available
152 4 3 2 1 Used by the First Card
169 For technical support, please provide the following