From: Clem Cole <email@example.com>
To: Roland <firstname.lastname@example.org>, TUHS main list <email@example.com>
Subject: Re: [TUHS] Unix for PDP11/20 w/o mmu or paging option
Date: Fri, 17 Sep 2021 12:14:54 -0400 [thread overview]
Message-ID: <CAC20D2OCXQzR4xByTFLpF5X=DekLX5mg-Q7gRwLKsNfo667Szw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
On Fri, Sep 17, 2021 at 12:04 PM Roland via TUHS <firstname.lastname@example.org>
> There is a KT11B paging option that makes the PDP11/20 a 18 bit machine.
> It looks a bit like the TC11 DECtape controller. I've got the schematics
> from the internet. But I have no idea how it compares to the later MMU
> units from the software perspective.
Love to see them and if you know where you found them.
> The V1 work was for a PDP-7 and is before the first 11/20 was secured.
> The point is that I think there is a hole in the the SW we have.
I just looked again at what Warren has -- it is the 11/20 assembler code
that Dennis scanned. I have forgotten that we still had that. I wonder
if it had the KS-11 stuff in it. I'll have to peek
[-- Attachment #2: Type: text/html, Size: 2895 bytes --]
next prev parent reply other threads:[~2021-09-17 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2021-09-17 14:09 ` Roland via TUHS
2021-09-17 14:33 ` Warner Losh
2021-09-17 15:32 ` Clem Cole
2021-09-17 16:04 ` Roland via TUHS
2021-09-17 16:14 ` Clem Cole [this message]
2021-09-17 16:44 ` Roland via TUHS
2021-09-17 16:13 ` Warner Losh
2021-09-17 16:17 ` Clem Cole
2021-09-17 16:05 ` Roland via TUHS
2021-09-17 15:35 Noel Chiappa
2021-09-17 18:28 ` Phil Budne
2021-09-17 19:43 ` Clem Cole
2021-09-17 19:51 ` Brantley Coile
2021-09-17 20:07 ` Clem Cole
2021-09-17 21:21 ` Phil Budne
2021-09-17 20:18 Noel Chiappa
2021-09-17 20:47 ` Clem Cole
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).