The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah via TUHS <tuhs@tuhs.org>
To: segaloco <segaloco@protonmail.com>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: Of /dev/tty8
Date: Mon, 18 Mar 2024 15:39:59 -0700	[thread overview]
Message-ID: <F8A9BF86-8774-40EA-BF8E-E460BF1633FA@iitbombay.org> (raw)
In-Reply-To: <KGhFfv7fJ3_-fDz3w6oR7hwrwY3EgbRUSB1CnqRLdnuWANaSiD1eU9mtdE18pIsGhdOQEOTHiENPn1p29-chyzGKnSIr9icgbd5G5yDuWto=@protonmail.com>

On Mar 18, 2024, at 1:21 PM, segaloco via TUHS <tuhs@tuhs.org> wrote:
> 
> only caveat being the transmitter status register was a dirty filthy liar and wouldn't flip the bit on transmit, so just had to put a delay, which it turns out all of the BSDs currently also do for Ti 16550-family UARTs as well.

NatSemi (later Ti) 16550s have a 16 byte fifo in each direction.
Any delays would be in getc(), putc(), used for system console io,
not general serial io. Ignoring any code for brokenness! The early
16660 versions had a bug preventing use of the fifo but this was
fixed ages ago. At least this is what I remember decades later!


      reply	other threads:[~2024-03-18 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 11:13 [TUHS] " Dave Horsfall
2024-03-18 11:22 ` [TUHS] " Ron Natalie
2024-03-18 19:36   ` Dave Horsfall
2024-03-18 20:17     ` segaloco via TUHS
2024-03-18 13:56 ` Clem Cole
2024-03-18 14:58   ` Paul Winalski
2024-03-18 15:20     ` Larry McVoy
2024-03-18 20:08       ` Ron Natalie
2024-03-18 20:21         ` segaloco via TUHS
2024-03-18 22:39           ` Bakul Shah via TUHS [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=F8A9BF86-8774-40EA-BF8E-E460BF1633FA@iitbombay.org \
    --to=tuhs@tuhs.org \
    --cc=bakul@iitbombay.org \
    --cc=segaloco@protonmail.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).