The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Noel Chiappa <>
Cc: TUHS main list <>
Subject: Re: [TUHS] Unix for PDP11/20 w/o mmu or paging option
Date: Fri, 17 Sep 2021 16:47:40 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Fri, Sep 17, 2021 at 4:19 PM Noel Chiappa <>

>    I got the impression that the KS11 was more a 'base and bounds' kind of
> thing.
Ditto.  I was under the impression it was modeled after the KA10 scheme.  I
don't remember who told me that, probably somebody from CSS, but I have no
idea whom.  As I think you remember when you asked about it a while ago, I
sent some probes to a few of folks from the 11 group but all of them
disavowed any knowledge of it.

One of the questions I always had was since M[TF]P[IDS] instructions were
not created until the 40 and 45 class processors, how did Ken get the
information to/fr the other address space.   I >>think<< the KT has a funky
memory window (that I never really looked into in any detail), I assume
the KS must have done something similar.

[-- Attachment #2: Type: text/html, Size: 2106 bytes --]

  reply	other threads:[~2021-09-17 20:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 20:18 Noel Chiappa
2021-09-17 20:47 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
     [not found] <>
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
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

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:

* 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).