Lines Matching refs:driver

6 separate drivers as they did not share any code, and the driver
15   This driver supports the SER12 modems either full or half duplex.
19   This is the recommended driver for SER12 type modems,
24   This is an alternative driver for SER12 type modems.
26   are called bcsh0 through bcsh3. Use this driver only if baycom_ser_fdx
30   This driver supports the par96 and picpar modems.
34   This driver supports the EPP modem.
36   This driver is work-in-progress.
45         port, the kernel driver for serial ports cannot be used, and this
46         driver only supports standard serial hardware (8250, 16450, 16550)
71 the driver supports the KISS (see below) fullduplex command. It then simply
83 sethdlc from the ax25 utilities may be used to set driver states etc.
90 Configuring the driver
92 Every time a driver is inserted into the kernel, it has to know which
95 driver from the insmod command line (or by means of an option line in
103 serial port (COM1 under DOS). The * in the mode parameter instructs the driver to use
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
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
144 interface at a time. The serial driver grabs all interfaces it can find at
147 a port owned by the serial driver with 'setserial /dev/ttyS# uart none', where
151 leave it to kmod to load the correct driver depending on the application.