The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Ron Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Of /dev/tty8
Date: Mon, 18 Mar 2024 20:21:33 +0000	[thread overview]
Message-ID: <KGhFfv7fJ3_-fDz3w6oR7hwrwY3EgbRUSB1CnqRLdnuWANaSiD1eU9mtdE18pIsGhdOQEOTHiENPn1p29-chyzGKnSIr9icgbd5G5yDuWto=@protonmail.com> (raw)
In-Reply-To: <em020ec570-5ac1-42f4-9a99-776ccf7e6dae@921e7d1d.com>

On Monday, March 18th, 2024 at 1:08 PM, Ron Natalie <ron@ronnatalie.com> wrote:

> The other problem with the DZ is it was one interrupt per character if I
> recall.
> Thte DH you could get multiple (output) characters per interrupt.
> Greatly decreased the load on the system.
> 
> I do remember the KL kernel prints were not interrupt driven so the
> system pretty much froze while the kernel printfs were being output.
> There was a comment on the code saying this was “Not for idle chit
> chat.”

Yep, synchronous code that writes a character at a time to the transmit register then spins on a status bit awaiting transmit complete, or something like that.  I adapted the V6 kernel printf to a RISC-V board I was working on the past year to have a trustworthy print mechanism, 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.

- Matt G.

  reply	other threads:[~2024-03-18 20:22 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 [this message]
2024-03-18 22:39           ` Bakul Shah via TUHS

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='KGhFfv7fJ3_-fDz3w6oR7hwrwY3EgbRUSB1CnqRLdnuWANaSiD1eU9mtdE18pIsGhdOQEOTHiENPn1p29-chyzGKnSIr9icgbd5G5yDuWto=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=ron@ronnatalie.com \
    --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).