From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] [tuhs] PDP-11 and early Unix
Date: Mon, 14 Mar 2022 16:38:14 -0400 (EDT) [thread overview]
Message-ID: <20220314203814.3D97C18C085@mercury.lcs.mit.edu> (raw)
Oops:
> Instructions had a 4-bit opcode ('000'-'054')
'060' was JMP.
> ('060'opcodes were for the optional EAE.)
'064'.
Noel
next reply other threads:[~2022-03-14 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 20:38 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-14 20:22 Noel Chiappa
2022-03-14 16:56 Noel Chiappa
2022-03-14 18:00 ` Clem Cole
2022-03-14 19:03 ` Angelo Papenhoff
2022-03-14 12:58 Nelson H. F. Beebe
2022-03-14 14:59 ` Ron Natalie
2022-03-14 15:13 ` 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=20220314203814.3D97C18C085@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).