From: jkunz@unixag-kl.fh-kl.de (Jochen Kunz)
Subject: [pups] Re: A project--buiilding a device to plug into a PDP-11's bus
Date: Thu, 13 Nov 2003 09:51:10 +0100 [thread overview]
Message-ID: <20031113085110.GO3516666@MrPomeroy2> (raw)
In-Reply-To: <200311130130.hAD1UYVZ015853@psychwarp.psych.usyd.edu.au>; from johnh@psych.usyd.edu.au on Thu, Nov 13, 2003 at 02:30:34 %z
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On 2003.11.13 02:30 John Holden wrote:
> DEC didn't use 2901's in central processors,
The VAX 11/730 CPU is build using AMD bit slice chips. It is the slowest
VAX (together with the MicroVAX I) and AFAIK the only VAX that
implemented the complete VAX instruction set.
--
tschüß,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
next prev parent reply other threads:[~2003-11-13 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 1:30 John Holden
2003-11-13 1:48 ` Gregg C Levine
2003-11-13 8:51 ` Jochen Kunz [this message]
2003-11-13 16:17 ` David Evans
2003-11-13 3:42 Carl Lowenstein
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=20031113085110.GO3516666@MrPomeroy2 \
--to=jkunz@unixag-kl.fh-kl.de \
/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).