2 tristate "Serial port KISS driver"
6 KISS is a protocol used for the exchange of data between a computer
7 and a Terminal Node Controller (a small embedded system commonly
8 used for networking over AX.25 amateur radio connections; it
9 connects the computer's serial port with the radio's microphone
10 input and speaker output).
12 Although KISS is less advanced than the 6pack protocol, it has
13 the advantage that it is already supported by most modern TNCs
14 without the need for a firmware upgrade.
16 To compile this driver as a module, choose M here: the module
20 tristate "Serial port 6PACK driver"
21 depends on AX25 && TTY
23 6pack is a transmission protocol for the data exchange between your
24 PC and your TNC (the Terminal Node Controller acts as a kind of
25 modem connecting your computer's serial port to your radio's
26 microphone input and speaker output). This protocol can be used as
27 an alternative to KISS for networking over AX.25 amateur radio
28 connections, but it has some extended functionality.
30 Note that this driver is still experimental and might cause
31 problems. For details about the features and the usage of the
32 driver, read <file:Documentation/networking/6pack.txt>.
34 To compile this driver as a module, choose M here: the module
38 tristate "BPQ Ethernet driver"
41 AX.25 is the protocol used for computer communication over amateur
42 radio. If you say Y here, you will be able to send and receive AX.25
43 traffic over Ethernet (also called "BPQ AX.25"), which could be
44 useful if some other computer on your local network has a direct
45 amateur radio connection.
48 tristate "High-speed (DMA) SCC driver for AX.25"
49 depends on ISA && AX25 && BROKEN_ON_SMP && ISA_DMA_API
51 This is a driver for high-speed SCC boards, i.e. those supporting
52 DMA on one port. You usually use those boards to connect your
53 computer to an amateur radio modem (such as the WA4DSY 56kbps
54 modem), in order to send and receive AX.25 packet radio network
57 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
58 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
59 If you have one of these cards, say Y here and read the AX25-HOWTO,
60 available from <http://www.tldp.org/docs.html#howto>.
62 This driver can operate multiple boards simultaneously. If you
63 compile it as a module (by saying M instead of Y), it will be called
64 dmascc. If you don't pass any parameter to the driver, all
65 possible I/O addresses are probed. This could irritate other devices
66 that are currently not in use. You may specify the list of addresses
67 to be probed by "dmascc.io=addr1,addr2,..." (when compiled into the
68 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
69 network interfaces will be called dmascc0 and dmascc1 for the board
70 detected first, dmascc2 and dmascc3 for the second one, and so on.
72 Before you configure each interface with ifconfig, you MUST set
73 certain parameters, such as channel access timing, clock mode, and
74 DMA channel. This is accomplished with a small utility program,
75 dmascc_cfg, available at
76 <http://www.linux-ax25.org/wiki/Ax25-tools>. Please be sure to
77 get at least version 1.27 of dmascc_cfg, as older versions will not
78 work with the current driver.
81 tristate "Z8530 SCC driver"
82 depends on ISA && AX25 && ISA_DMA_API
84 These cards are used to connect your Linux box to an amateur radio
85 in order to communicate with other computers. If you want to use
86 this, read <file:Documentation/networking/z8530drv.txt> and the
87 AX25-HOWTO, available from
88 <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
89 to "Amateur Radio AX.25 Level 2" support.
91 To compile this driver as a module, choose M here: the module
95 bool "additional delay for PA0HZP OptoSCC compatible boards"
98 Say Y here if you experience problems with the SCC driver not
99 working properly; please read
100 <file:Documentation/networking/z8530drv.txt> for details.
105 bool "support for TRX that feedback the tx signal to rx"
108 Some transmitters feed the transmitted signal back to the receive
109 line. Say Y here to foil this by explicitly disabling the receiver
110 during data transmission.
114 config BAYCOM_SER_FDX
115 tristate "BAYCOM ser12 fullduplex driver for AX.25"
116 depends on AX25 && !S390
119 This is one of two drivers for Baycom style simple amateur radio
120 modems that connect to a serial interface. The driver supports the
121 ser12 design in full-duplex mode. In addition, it allows the
122 baudrate to be set between 300 and 4800 baud (however not all modems
123 support all baudrates). This is the preferred driver. The next
124 driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
125 driver and still provided in case this driver does not work with
126 your serial interface chip. To configure the driver, use the sethdlc
127 utility available in the standard ax25 utilities package. For
128 information on the modems, see <http://www.baycom.de/> and
129 <file:Documentation/networking/baycom.txt>.
131 To compile this driver as a module, choose M here: the module
132 will be called baycom_ser_fdx. This is recommended.
134 config BAYCOM_SER_HDX
135 tristate "BAYCOM ser12 halfduplex driver for AX.25"
136 depends on AX25 && !S390
139 This is one of two drivers for Baycom style simple amateur radio
140 modems that connect to a serial interface. The driver supports the
141 ser12 design in half-duplex mode. This is the old driver. It is
142 still provided in case your serial interface chip does not work with
143 the full-duplex driver. This driver is deprecated. To configure
144 the driver, use the sethdlc utility available in the standard ax25
145 utilities package. For information on the modems, see
146 <http://www.baycom.de/> and
147 <file:Documentation/networking/baycom.txt>.
149 To compile this driver as a module, choose M here: the module
150 will be called baycom_ser_hdx. This is recommended.
153 tristate "BAYCOM picpar and par96 driver for AX.25"
154 depends on PARPORT && AX25
157 This is a driver for Baycom style simple amateur radio modems that
158 connect to a parallel interface. The driver supports the picpar and
159 par96 designs. To configure the driver, use the sethdlc utility
160 available in the standard ax25 utilities package. For information on
161 the modems, see <http://www.baycom.de/> and the file
162 <file:Documentation/networking/baycom.txt>.
164 To compile this driver as a module, choose M here: the module
165 will be called baycom_par. This is recommended.
168 tristate "BAYCOM epp driver for AX.25"
169 depends on PARPORT && AX25 && !64BIT
172 This is a driver for Baycom style simple amateur radio modems that
173 connect to a parallel interface. The driver supports the EPP
174 designs. To configure the driver, use the sethdlc utility available
175 in the standard ax25 utilities package. For information on the
176 modems, see <http://www.baycom.de/> and the file
177 <file:Documentation/networking/baycom.txt>.
179 To compile this driver as a module, choose M here: the module
180 will be called baycom_epp. This is recommended.
183 tristate "YAM driver for AX.25"
184 depends on AX25 && !S390
186 The YAM is a modem for packet radio which connects to the serial
187 port and includes some of the functions of a Terminal Node
188 Controller. If you have one of those, say Y here.
190 To compile this driver as a module, choose M here: the module