Lines Matching +full:software +full:- +full:driver

1 .. SPDX-License-Identifier: GPL-2.0
10 separate drivers as they did not share any code, and the driver
20   This driver supports the SER12 modems either full or half duplex.
24   This is the recommended driver for SER12 type modems,
29   This is an alternative driver for SER12 type modems.
31   are called bcsh0 through bcsh3. Use this driver only if baycom_ser_fdx
35   This driver supports the par96 and picpar modems.
39   This driver supports the EPP modem.
41   This driver is work-in-progress.
51 	port, the kernel driver for serial ports cannot be used, and this
52 	driver only supports standard serial hardware (8250, 16450, 16550)
69 EPP     This is a high-speed modem adaptor that connects to an enhanced parallel
78 the driver supports the KISS (see below) fullduplex command. It then simply
90 simple. Once installed, four interfaces named bc{sf,sh,p,e}[0-3] are available.
91 sethdlc from the ax25 utilities may be used to set driver states etc.
98 Configuring the driver
101 Every time a driver is inserted into the kernel, it has to know which
104 driver from the insmod command line (or by means of an option line in
110   sethdlc -i bcsf0 -p mode "ser12*" io 0x3f8 irq 4
113 serial port (COM1 under DOS). The * in the mode parameter instructs the driver
114 to use the software DCD algorithm (see below)::
117   sethdlc -i bcp0 -p mode "picpar" io 0x378
121 hardware DCD, par96 implies software DCD).
123 The channel access parameters can be set with sethdlc -a or kissparms.
127 Hardware DCD versus Software DCD
130 To avoid collisions on the air, the driver must know when the channel is
131 busy. This is the task of the DCD circuitry/software. The driver may either
132 utilise a software DCD algorithm (options=1) or use a DCD signal from
136 ser12   if software DCD is utilised, the radio's squelch should always be
137 	open. It is highly recommended to use the software DCD algorithm,
141 par96   the software DCD algorithm for this type of modem is rather poor.
143 	a reasonable DCD algorithm in software. Therefore, if your radio
156 The serial driver and the baycom serial drivers compete
157 for the same hardware resources. Of course only one driver can access a given
158 interface at a time. The serial driver grabs all interfaces it can find at
161 a port owned by the serial driver with 'setserial /dev/ttyS# uart none', where
165 leave it to kmod to load the correct driver depending on the application.