From: bogus@does.not.exist.com ()
Subject: No subject
Date: Fri, 01 Jan 2016 22:42:01 -0000 [thread overview]
Message-ID: <mailman.0.1451688124.15990.tuhs@minnie.tuhs.org> (raw)
runs the same stuff.
> You can find T11 chips in several Q-bus and Unibus peripherals, most notably
> the RQDX1, 2, and 3 (the chip labeled "27-17311-01").
Also used in VT240/241 terminals.
My collection have some marked DEC DC311/es (T-11 engineering samples).
I's a nice chip with a straightforward interface. Anyone that knows 8085,
nsc800 would like interfacing t-11. Instruction set is base LSI11.
Allison
Received: (from major at localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA79855
for pups-liszt; Thu, 11 May 2000 04:16:31 +1000 (EST)
Received: from timaxp.trailing-edge.com (timaxp.trailing-edge.com [63.73.218.130])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id EAA79851
for <PUPS at MINNIE.CS.ADFA.EDU.AU>; Thu, 11 May 2000 04:16:23 +1000 (EST)
Received: by timaxp.trailing-edge.com for PUPS at MINNIE.CS.ADFA.EDU.AU;
Wed, 10 May 2000 14:16:15 -0400
Date: Wed, 10 May 2000 14:16:15 -0400
From: Tim Shoppa <SHOPPA@trailing-edge.com>
To: PUPS at minnie.cs.adfa.edu.au
Message-Id: <000510141615.202009f2 at trailing-edge.com>
Subject: Re: Help: PDP-11 instruction classification (again!)
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk
>> Yes, the 11/53 is a KDJ11-D.
>Not KDF-11B????
The KDF11-B (why are people putting the hyphens in all the wrong places?) is
the quad-height 11/23 with two SLU's and boot ROM.
Tim.
next reply other threads:[~2016-01-01 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 22:42 bogus [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-01 22:42 bogus
2016-01-01 22:42 bogus
2016-01-01 22:42 bogus
2016-01-01 22:42 bogus
2016-01-01 22:42 bogus
2016-01-01 22:42 bogus
2001-04-01 20:30 owner-pups
1998-12-30 15:29 norman
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=mailman.0.1451688124.15990.tuhs@minnie.tuhs.org \
--to=bogus@does.not.exist.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).