Lines Matching refs:the
5 !!NEW!! (04/98) The drivers for the baycom modems have been split into
6 separate drivers as they did not share any code, and the driver
9 This document describes the Linux Kernel Drivers for simple Baycom style
15 This driver supports the SER12 modems either full or half duplex.
16 Its baud rate may be changed via the `baud' module parameter,
19 This is the recommended driver for SER12 type modems,
30 This driver supports the par96 and picpar modems.
34 This driver supports the EPP modem.
42 is responsible for regenerating the receiver bit clock, as well as
43 for handling the HDLC protocol. The modem connects to a serial port,
44 hence the name. Since the serial port is not used as an async serial
45 port, the kernel driver for serial ports cannot be used, and this
48 par96: This is a modem for 9600 baud FSK compatible to the G3RUH standard.
49 The modem does all the filtering and regenerates the receiver clock.
50 Data is transferred from and to the PC via a shift register.
52 The PC then empties the shift register in a burst. This modem connects
53 to the parallel port, hence the name. The modem leaves the
54 implementation of the HDLC protocol and the scrambler polynomial to
55 the PC.
57 picpar: This is a redesign of the par96 modem by Henning Rech, DF9IC. The modem
59 and can therefore be fed from the parallel port and does not require
66 eppfpga: This is a redesign of the EPP adaptor.
70 All of the above modems only support half duplex communications. However,
71 the driver supports the KISS (see below) fullduplex command. It then simply
73 about DCD, i.e. it starts to send even if there's someone else on the channel.
74 This command is required by some implementations of the DAMA channel
78 The Interface of the drivers
83 sethdlc from the ax25 utilities may be used to set driver states etc.
84 Users of userland AX.25 stacks may use the net2kiss utility (also available
85 in the ax25 utilities package) to convert packets of a network interface
90 Configuring the driver
92 Every time a driver is inserted into the kernel, it has to know which
93 modems it should access at which ports. This can be done with the setbaycom
94 utility. If you are only using one modem, you can also configure the
95 driver from the insmod command line (or by means of an option line in
102 Both lines configure the first port to drive a ser12 modem at the first
103 serial port (COM1 under DOS). The * in the mode parameter instructs the driver to use
104 the software DCD algorithm (see below).
109 Both lines configure the first port to drive a picpar modem at the
114 Note that both utilities interpret the values slightly differently.
119 To avoid collisions on the air, the driver must know when the channel is
120 busy. This is the task of the DCD circuitry/software. The driver may either
122 the hardware (options=0).
124 ser12: if software DCD is utilised, the radio's squelch should always be
125 open. It is highly recommended to use the software DCD algorithm,
127 disadvantage is a slightly higher load on the system.
129 par96: the software DCD algorithm for this type of modem is rather poor.
132 feeds the DCD input of the PAR96 modem, the use of the hardware
135 picpar: the picpar modem features a builtin DCD hardware, which is highly
140 Compatibility with the rest of the Linux kernel
142 The serial driver and the baycom serial drivers compete
143 for the same hardware resources. Of course only one driver can access a given
145 startup time. Therefore the baycom drivers subsequently won't be able to
147 a port owned by the serial driver with 'setserial /dev/ttyS# uart none', where
148 # is the number of the interface. The baycom drivers do not reserve any
149 ports at startup, unless one is specified on the 'insmod' command line. Another
150 method to solve the problem is to compile all drivers as modules and
151 leave it to kmod to load the correct driver depending on the application.
153 The parallel port drivers (baycom_par, baycom_epp) now use the parport subsystem
154 to arbitrate the ports between different client drivers.