linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linuxppc_2_4_devel patch for arch/ppc/kernel/gen550_dbg.c
Date: Thu, 5 Jun 2003 17:25:50 -0500	[thread overview]
Message-ID: <20030605172550.A23648@forte.austin.ibm.com> (raw)
In-Reply-To: <3EDFBA42.3050306@mvista.com>; from mgreer@mvista.com on Thu, Jun 05, 2003 at 02:46:42PM -0700


On Thu, Jun 05, 2003 at 02:46:42PM -0700, Mark A. Greer wrote:
> This patch add in the check to see if the UART already appears to be
[...]
> +	 * We assume that no-one uses less than 110 baud or
> +	 * less than 7 bits per character these days.
> +	 *  -- paulus.

'These days' is a relative term, but last I looked, a few years ago,
I still had a freind who was using a 6-bit airline protocol on a
synchronoous serial port.

Yes, 6-bits means capital letters only.  (26 alpha + 10 num + misc=64)

The protocol was still being used in many travel agencies to support
older terminals.  Our travel agency received it encapsulated in
TCP on top of frame-relay.  The airlines provides a router which
sucks in frame-relay, and spits out 6-bit synch. serial.  We used
a serial cable to hook up a linux box, and converted the 6-bit
protocol into the tcp over ethernet that we wanted.

Thought you might enjoy reading this.  I'll skip over the detailed
description of the four different end-of-message markers in the protocol.


--linas


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-06-05 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 21:46 linuxppc_2_4_devel patch for arch/ppc/kernel/gen550_dbg.c Mark A. Greer
2003-06-05 22:25 ` linas [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=20030605172550.A23648@forte.austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgreer@mvista.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;
as well as URLs for NNTP newsgroup(s).