The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Serial Interfaces (was ^T and Top)
Date: Thu, 31 May 2018 08:46:46 +1000 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.999.1805310839290.13066@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2OsjGoMAm6b0kq4Rqbp0=fiKFb78KzjM1DOaRbDKPE9Jg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On Wed, 30 May 2018, Clem Cole wrote:

> Right - you have to escape things and it is a real mess.  I have seen 
> some of the SI/SO/DLE stuff in mechanical systems like ticker tape.  I 
> never saw a real 8-bit interface try to do it and succeed -- its messy 
> and suspect when data overruns occurs all hell break loose.  By the time 
> of 8 bits and speed of 9.6K protocol's like UUCP, or IP over serial did 
> not even bother.  I suspect in the old 5-bit baudot code times, it was 
> more popular to get a larger character set, but the speeds were much 
> slower (and the UART not yet invented by Gordon Bell).​ 

Actually, the closest I've seen DLE being used was in SLIP and PPP; if you
needed to send a Frame End then it was escaped with (I think) 0xFF, and that
in turn was escaped.  All it took was a finite state machine...  Of course,
those links used RTS/CTS, but you had to flag the end of a frame (packet)
somehow.

-- Dave


  reply	other threads:[~2018-05-30 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 14:39 Clem Cole
2018-05-30 22:46 ` Dave Horsfall [this message]
2018-05-30 23:01   ` Paul Winalski

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=alpine.BSF.2.21.999.1805310839290.13066@aneurin.horsfall.org \
    --to=dave@horsfall.org \
    /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;
as well as URLs for NNTP newsgroup(s).