From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: TUHS@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ]
Date: Wed, 15 Jan 2020 11:46:47 -0500 (EST) [thread overview]
Message-ID: <20200115164647.AA0D218C0A2@mercury.lcs.mit.edu> (raw)
> From: Clem Cole
> So WD designs and builds a few LSI-11 as a sales demo of what you could
> do
> ...
> he put it on the QBUS which DEC could not lock up because they did not
> create it as WD had.
Wow! WD created the QBUS? Fascinating. I wonder if DEC made any changes to the
QBUS between the original demo WD boards and the first DEC ones? Are there any
documents about the WD original still extant, do you know?
(FWIW, it seems that whoever did the QBUS interrupt cycle had heard about the
metastability issues when using a flop to do the grant-passing arbitrations;
see here for more:
https://gunkies.org/wiki/Bus_Arbitration_on_the_Unibus_and_QBUS#QBUS_Interrupts
DEC had previously bent themselves into knots trying to solve it on the UNIBUS:
https://gunkies.org/wiki/M782_Interrupt_Control#Revisions
so it would be interesting to know if it was WD or DEC who did the DIN thing to
get rid of it on the QBUS.)
Noel
next reply other threads:[~2020-01-15 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:46 Noel Chiappa [this message]
2020-01-15 18:35 ` Clem Cole
2020-01-29 20:25 ` Dave Horsfall
[not found] ` <CABH=_VSPTV-rwu202hYuiXViiBG2ReMnshxUAvD9Lb6HqG4tQQ@mail.gmail.com>
[not found] ` <CAC20D2Mr1vqpoAELU3a+4cV7W99uh_76ogGQq28wktJM+onDQA@mail.gmail.com>
2020-02-04 20:26 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 6:17 [TUHS] Spacewar at Bell Labs Lars Brinkhoff
2020-01-15 6:34 ` Earl Baugh
2020-01-15 7:10 ` [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ] Jon Steinhart
2020-01-15 8:05 ` Earl Baugh
2020-01-15 14:50 ` Clem Cole
2020-01-15 23:40 ` Al Kossow
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=20200115164647.AA0D218C0A2@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).