From: Mauro Carvalho Chehab Date: Fri, 1 May 2020 14:44:28 +0000 (+0200) Subject: docs: networking: convert x25.txt to ReST X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=c4ea03fdfd122b4ff293bff643c2369852e9cc1c;p=linux.git docs: networking: convert x25.txt to ReST Not much to be done here: - add SPDX header; - add a document title; - add to networking/index.rst. Signed-off-by: Mauro Carvalho Chehab Signed-off-by: David S. Miller --- diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst index 7a4bdbc111b06..75521e6c473b8 100644 --- a/Documentation/networking/index.rst +++ b/Documentation/networking/index.rst @@ -116,6 +116,7 @@ Contents: vrf vxlan x25-iface + x25 .. only:: subproject and html diff --git a/Documentation/networking/x25.rst b/Documentation/networking/x25.rst new file mode 100644 index 0000000000000..00e45d384ba02 --- /dev/null +++ b/Documentation/networking/x25.rst @@ -0,0 +1,48 @@ +.. SPDX-License-Identifier: GPL-2.0 + +================== +Linux X.25 Project +================== + +As my third year dissertation at University I have taken it upon myself to +write an X.25 implementation for Linux. My aim is to provide a complete X.25 +Packet Layer and a LAPB module to allow for "normal" X.25 to be run using +Linux. There are two sorts of X.25 cards available, intelligent ones that +implement LAPB on the card itself, and unintelligent ones that simply do +framing, bit-stuffing and checksumming. These both need to be handled by the +system. + +I therefore decided to write the implementation such that as far as the +Packet Layer is concerned, the link layer was being performed by a lower +layer of the Linux kernel and therefore it did not concern itself with +implementation of LAPB. Therefore the LAPB modules would be called by +unintelligent X.25 card drivers and not by intelligent ones, this would +provide a uniform device driver interface, and simplify configuration. + +To confuse matters a little, an 802.2 LLC implementation for Linux is being +written which will allow X.25 to be run over an Ethernet (or Token Ring) and +conform with the JNT "Pink Book", this will have a different interface to +the Packet Layer but there will be no confusion since the class of device +being served by the LLC will be completely separate from LAPB. The LLC +implementation is being done as part of another protocol project (SNA) and +by a different author. + +Just when you thought that it could not become more confusing, another +option appeared, XOT. This allows X.25 Packet Layer frames to operate over +the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the +format and behaviour of the protocol. If time permits this option will also +be actively considered. + +A linux-x25 mailing list has been created at vger.kernel.org to support the +development and use of Linux X.25. It is early days yet, but interested +parties are welcome to subscribe to it. Just send a message to +majordomo@vger.kernel.org with the following in the message body: + +subscribe linux-x25 +end + +The contents of the Subject line are ignored. + +Jonathan + +g4klx@g4klx.demon.co.uk diff --git a/Documentation/networking/x25.txt b/Documentation/networking/x25.txt deleted file mode 100644 index c91c6d7159ff8..0000000000000 --- a/Documentation/networking/x25.txt +++ /dev/null @@ -1,44 +0,0 @@ -Linux X.25 Project - -As my third year dissertation at University I have taken it upon myself to -write an X.25 implementation for Linux. My aim is to provide a complete X.25 -Packet Layer and a LAPB module to allow for "normal" X.25 to be run using -Linux. There are two sorts of X.25 cards available, intelligent ones that -implement LAPB on the card itself, and unintelligent ones that simply do -framing, bit-stuffing and checksumming. These both need to be handled by the -system. - -I therefore decided to write the implementation such that as far as the -Packet Layer is concerned, the link layer was being performed by a lower -layer of the Linux kernel and therefore it did not concern itself with -implementation of LAPB. Therefore the LAPB modules would be called by -unintelligent X.25 card drivers and not by intelligent ones, this would -provide a uniform device driver interface, and simplify configuration. - -To confuse matters a little, an 802.2 LLC implementation for Linux is being -written which will allow X.25 to be run over an Ethernet (or Token Ring) and -conform with the JNT "Pink Book", this will have a different interface to -the Packet Layer but there will be no confusion since the class of device -being served by the LLC will be completely separate from LAPB. The LLC -implementation is being done as part of another protocol project (SNA) and -by a different author. - -Just when you thought that it could not become more confusing, another -option appeared, XOT. This allows X.25 Packet Layer frames to operate over -the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the -format and behaviour of the protocol. If time permits this option will also -be actively considered. - -A linux-x25 mailing list has been created at vger.kernel.org to support the -development and use of Linux X.25. It is early days yet, but interested -parties are welcome to subscribe to it. Just send a message to -majordomo@vger.kernel.org with the following in the message body: - -subscribe linux-x25 -end - -The contents of the Subject line are ignored. - -Jonathan - -g4klx@g4klx.demon.co.uk diff --git a/net/x25/Kconfig b/net/x25/Kconfig index a328f79885d13..9f0d58b0b90b8 100644 --- a/net/x25/Kconfig +++ b/net/x25/Kconfig @@ -20,7 +20,7 @@ config X25 You can read more about X.25 at and . Information about X.25 for Linux is contained in the files - and + and . One connects to an X.25 network either with a dedicated network card