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