From: David Laight <David.Laight@ACULAB.COM>
To: 'Xie He' <xie.he.0141@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: RE: [PATCH net-next] net: x25_asy: Delete the x25_asy driver
Date: Thu, 5 Nov 2020 22:35:23 +0000 [thread overview]
Message-ID: <56513ba35a864fce8e27c550b55766a1@AcuMS.aculab.com> (raw)
In-Reply-To: <CAJht_EM6rXw2Y6NOw9npqUx-MSscwaZ54q7KM4V2ip_CCQsdeg@mail.gmail.com>
From: Xie He
> Sent: 05 November 2020 19:35
>
> On Thu, Nov 5, 2020 at 1:10 AM David Laight <David.Laight@aculab.com> wrote:
> >
> > > This driver transports LAPB (X.25 link layer) frames over TTY links.
> >
> > I don't remember any requests to run LAPB over anything other
> > than synchronous links when I was writing LAPB implementation(s)
> > back in the mid 1980's.
> >
> > If you need to run 'comms over async uart links' there
> > are better options.
> >
> > I wonder what the actual use case was?
>
> I think this driver was just for experimental purposes. According to
> the author's comment at the beginning of x25_asy.c, this driver didn't
> implement FCS (frame check sequence), which was required by CCITT's
> standard. So I think this driver was not suitable for real-world use
> anyway.
Yes, you could get transparency by sending 0x7f bytes twice
(a bit like bisync) but you'd want the CRC to check for lost bytes.
I bet this was only ever used by the author and only to talk to itself.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-11-05 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 7:34 Xie He
2020-11-05 9:10 ` David Laight
2020-11-05 19:35 ` Xie He
2020-11-05 22:35 ` David Laight [this message]
2020-11-05 15:06 ` Arnd Bergmann
2020-11-05 20:04 ` Xie He
2020-11-05 20:40 ` Arnd Bergmann
2020-11-05 22:47 ` Xie He
2020-11-06 9:03 ` David Laight
2020-11-06 11:25 ` Xie He
2020-11-06 5:43 ` Martin Schiller
2020-11-07 22:19 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56513ba35a864fce8e27c550b55766a1@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xie.he.0141@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome