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 depends on VIRT_TO_BUS 52 help 53 This is a driver for high-speed SCC boards, i.e. those supporting 54 DMA on one port. You usually use those boards to connect your 55 computer to an amateur radio modem (such as the WA4DSY 56kbps 56 modem), in order to send and receive AX.25 packet radio network 57 traffic. 58 59 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis 60 PackeTwin, and S5SCC/DMA boards. They are detected automatically. 61 If you have one of these cards, say Y here and read the AX25-HOWTO, 62 available from <http://www.tldp.org/docs.html#howto>. 63 64 This driver can operate multiple boards simultaneously. If you 65 compile it as a module (by saying M instead of Y), it will be called 66 dmascc. If you don't pass any parameter to the driver, all 67 possible I/O addresses are probed. This could irritate other devices 68 that are currently not in use. You may specify the list of addresses 69 to be probed by "dmascc.io=addr1,addr2,..." (when compiled into the 70 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The 71 network interfaces will be called dmascc0 and dmascc1 for the board 72 detected first, dmascc2 and dmascc3 for the second one, and so on. 73 74 Before you configure each interface with ifconfig, you MUST set 75 certain parameters, such as channel access timing, clock mode, and 76 DMA channel. This is accomplished with a small utility program, 77 dmascc_cfg, available at 78 <http://www.linux-ax25.org/wiki/Ax25-tools>. Please be sure to 79 get at least version 1.27 of dmascc_cfg, as older versions will not 80 work with the current driver. 81 82config SCC 83 tristate "Z8530 SCC driver" 84 depends on ISA && AX25 && ISA_DMA_API 85 help 86 These cards are used to connect your Linux box to an amateur radio 87 in order to communicate with other computers. If you want to use 88 this, read 89 <file:Documentation/networking/device_drivers/hamradio/z8530drv.rst> 90 and the AX25-HOWTO, available from 91 <http://www.tldp.org/docs.html#howto>. Also make sure to say Y 92 to "Amateur Radio AX.25 Level 2" support. 93 94 To compile this driver as a module, choose M here: the module 95 will be called scc. 96 97config SCC_DELAY 98 bool "additional delay for PA0HZP OptoSCC compatible boards" 99 depends on SCC 100 help 101 Say Y here if you experience problems with the SCC driver not 102 working properly; please read 103 <file:Documentation/networking/device_drivers/hamradio/z8530drv.rst> 104 for details. 105 106 If unsure, say N. 107 108config SCC_TRXECHO 109 bool "support for TRX that feedback the tx signal to rx" 110 depends on SCC 111 help 112 Some transmitters feed the transmitted signal back to the receive 113 line. Say Y here to foil this by explicitly disabling the receiver 114 during data transmission. 115 116 If in doubt, say Y. 117 118config BAYCOM_SER_FDX 119 tristate "BAYCOM ser12 fullduplex driver for AX.25" 120 depends on AX25 && !S390 121 select CRC_CCITT 122 help 123 This is one of two drivers for Baycom style simple amateur radio 124 modems that connect to a serial interface. The driver supports the 125 ser12 design in full-duplex mode. In addition, it allows the 126 baudrate to be set between 300 and 4800 baud (however not all modems 127 support all baudrates). This is the preferred driver. The next 128 driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old 129 driver and still provided in case this driver does not work with 130 your serial interface chip. To configure the driver, use the sethdlc 131 utility available in the standard ax25 utilities package. For 132 information on the modems, see <http://www.baycom.de/> and 133 <file:Documentation/networking/device_drivers/hamradio/baycom.rst>. 134 135 To compile this driver as a module, choose M here: the module 136 will be called baycom_ser_fdx. This is recommended. 137 138config BAYCOM_SER_HDX 139 tristate "BAYCOM ser12 halfduplex driver for AX.25" 140 depends on AX25 && !S390 141 select CRC_CCITT 142 help 143 This is one of two drivers for Baycom style simple amateur radio 144 modems that connect to a serial interface. The driver supports the 145 ser12 design in half-duplex mode. This is the old driver. It is 146 still provided in case your serial interface chip does not work with 147 the full-duplex driver. This driver is deprecated. To configure 148 the driver, use the sethdlc utility available in the standard ax25 149 utilities package. For information on the modems, see 150 <http://www.baycom.de/> and 151 <file:Documentation/networking/device_drivers/hamradio/baycom.rst>. 152 153 To compile this driver as a module, choose M here: the module 154 will be called baycom_ser_hdx. This is recommended. 155 156config BAYCOM_PAR 157 tristate "BAYCOM picpar and par96 driver for AX.25" 158 depends on PARPORT && AX25 159 select CRC_CCITT 160 help 161 This is a driver for Baycom style simple amateur radio modems that 162 connect to a parallel interface. The driver supports the picpar and 163 par96 designs. To configure the driver, use the sethdlc utility 164 available in the standard ax25 utilities package. For information on 165 the modems, see <http://www.baycom.de/> and the file 166 <file:Documentation/networking/device_drivers/hamradio/baycom.rst>. 167 168 To compile this driver as a module, choose M here: the module 169 will be called baycom_par. This is recommended. 170 171config BAYCOM_EPP 172 tristate "BAYCOM epp driver for AX.25" 173 depends on PARPORT && AX25 && !64BIT 174 select CRC_CCITT 175 help 176 This is a driver for Baycom style simple amateur radio modems that 177 connect to a parallel interface. The driver supports the EPP 178 designs. To configure the driver, use the sethdlc utility available 179 in the standard ax25 utilities package. For information on the 180 modems, see <http://www.baycom.de/> and the file 181 <file:Documentation/networking/device_drivers/hamradio/baycom.rst>. 182 183 To compile this driver as a module, choose M here: the module 184 will be called baycom_epp. This is recommended. 185 186config YAM 187 tristate "YAM driver for AX.25" 188 depends on AX25 && !S390 189 help 190 The YAM is a modem for packet radio which connects to the serial 191 port and includes some of the functions of a Terminal Node 192 Controller. If you have one of those, say Y here. 193 194 To compile this driver as a module, choose M here: the module 195 will be called yam. 196 197 198