From: Angelo Papenhoff <aap@papnet.eu>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Will pdp 11/04 run unix?
Date: Fri, 31 Jul 2020 09:10:08 +0200 [thread overview]
Message-ID: <20200731071008.GA33933@indra.papnet.eu> (raw)
In-Reply-To: <20200730213720.109C018C0A5@mercury.lcs.mit.edu>
On 30/07/20, Noel Chiappa wrote:
> > From: Angelo Papenhoff
>
> > I believe 11/20 UNIX also needs the EAE.
>
> Some applications might have used it (the story about the KS11 bug with the
> KW11-A confirms they did use it on that machine), but I found no trace of use
> of it in a quick scan of the entire Version 1 source (the one which is
> extant).
>
> Also, the first file in the OS source:
>
> https://www.tuhs.org/cgi-bin/utree.pl?file=V1/u0.s
>
> lists the addresses of all device registers, and the KE11-A isn't there.
Oh ok. The B runtime uses the EAE so i assumed it was used in other
places as well.
> If the KE11 is needed to run some application on the -11/04, there are
> KE11-B's (program compatible, but a single hex card) available, ISTR. For
> emulation, something (SIMH?) supports it, since the TV -11 on ITS (now running
> in emulation,I'm pretty sure) uses it.
Well the TV-11 is a tough question. I originally wrote an 11/05 emulator
because some document said it was an 11/10 (which is the same thing).
But other sources claimed it was an 11/20. you can build both versions
and both work. My EAE emulation is based on the KE-11A document from
bitsavers. (code here: https://github.com/aap/pdp11 )
aap
next prev parent reply other threads:[~2020-07-31 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 21:37 Noel Chiappa
2020-07-31 7:10 ` Angelo Papenhoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-30 17:20 Noel Chiappa
2020-07-30 13:47 Noel Chiappa
2020-07-30 14:08 ` Ronald Natalie
2020-07-30 16:13 ` Warner Losh
2020-07-30 18:00 ` Heinz Lycklama
2020-07-30 18:55 ` Angelo Papenhoff
2020-07-30 13:16 Will Senn
2020-07-30 13:53 ` Clem Cole
2020-07-30 14:01 ` Clem Cole
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=20200731071008.GA33933@indra.papnet.eu \
--to=aap@papnet.eu \
--cc=tuhs@minnie.tuhs.org \
/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).