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