The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] DH11 flaw Was: pre-more pager?
Date: Wed, 8 Nov 2017 21:49:37 +0000	[thread overview]
Message-ID: <CAC20D2OHMBj8G9vH9Mkq=0Xqffp5Xp2+1wtvk8G3-yhb-xBGbg@mail.gmail.com> (raw)
In-Reply-To: <20171108212753.C800818C0B9@mercury.lcs.mit.edu>

I've forgotten the details now, so I'll have look at the prints when I get
home, but think i remember that Ken had a strap on the DHDM that corrected
this.  But I do remember the discussion.   I have not idea where it was.
 I have a file of 'coms stuff' at home (paper of course).   I'll look to
see if it's in there.

Reading the McNamara interview, sadly he (like many folks) considered the
DZ to have modem control.   It had >>partial<< support, while the DH (with
the DM option) had full.   The difference is important.

Dave Cane (HW lead on the 750) used the DZ as his model for the original
MC-500 serial ports -- what a mess.   Here it is be had a real-time machine
and could not keep the clock straight for the first couple of versions of
the OS because the HW was dorked.  [Later systems did it properly].

Clem

On Wed, Nov 8, 2017 at 9:27 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

>     From: Ron Natalie
>
>     > We actually still had some real DEC DH's on our system.
>     > ...
>     > At least the DZ doesn't loop on the ready bit like the kernel printf
>
> This reminds me of something I recall reading about John McNamara
> (designer of
> the DH11) admitting that he'd screwed up a bit in the DH design; IIRC it
> was
> that if you set the input silo alarm (interrupt) level to something greater
> than 1 character, and someone types one character, and then nothing
> else... you never get an input interrupt!
>
> (Which is why some Unix DH driver which sets the silo alarm level > 1 - to
> get
> more efficient processing by reducing the number of interrupts _if
> possible_ -
> has to call a 'input characters ready from the DH' routine in the clock
> interrupt code.)
>
> IIRC McNamara said he should have included a timeout, so that if the silo
> count was non-zero,and stayed that way for a while, it should have caused
> a timeout, and an interrupt.
>
> I was just looking for this, but couldn't find it. I thought it was here:
>
>   http://woffordwitch.com/McNamaraDH11.asp
>
> but it doesn't seem to be. Does anyone recall seeing this anywhere, and if
> so,
> where? Web search engines didn't turn anything up, alas...
>
>        Noel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171108/75403f86/attachment.html>


      reply	other threads:[~2017-11-08 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 21:27 Noel Chiappa
2017-11-08 21:49 ` Clem Cole [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='CAC20D2OHMBj8G9vH9Mkq=0Xqffp5Xp2+1wtvk8G3-yhb-xBGbg@mail.gmail.com' \
    --to=clemc@ccc.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).