From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Serial communications (was Control-T (was top))
Date: Sat, 2 Jun 2018 08:09:01 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.999.1806020807530.37599@aneurin.horsfall.org> (raw)
In-Reply-To: <1527888911.6660.for-standards-violators@oclsc.org>
On Fri, 1 Jun 2018, Norman Wilson wrote:
> The modems had LCD status displays. In the early samples we had for
> initial testing, I vaguely remember a few spelling errors in the status
> messages; in particular SIGNAL QUARITY IS POOR. The error had been
> fixed in the big bulk order.
Well, they were Japanese modems, after all... :-)
-- Dave
prev parent reply other threads:[~2018-06-01 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 21:35 Norman Wilson
2018-06-01 22:09 ` Dave Horsfall [this message]
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.1806020807530.37599@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).