From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] PDP-11/70 SPL
Date: Mon, 28 Mar 2016 10:18:42 -0400 (EDT) [thread overview]
Message-ID: <20160328141842.B0DC218C0B6@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall <dave at horsfall.org>
> SPL 7 was only used by the clock interrupt
Err, according to the 1975 Peripherals Handbook, both are BR6. (Sorry, only
interested in accuracy.)
> even the published Unibus spec was known to be wrong, in order to keep
> 3rd-party kit out of it (it was something subtle to do with buss timing,
> so sometimes the card worked, and sometimes it didn't, doing wonders for
> your reputation).
I don't know about that, but we built two UNIBUS DMA networking devices,
relying on the UNIBUS description in the 1975 Peripherals Handbook, and they
both worked fine (one became a product for Proteon).
> Slightly longer? I think it was Lions himself who used to teach us that
> a lost interrupt is nasty :-(
The interrupt isn't lost, it's just that the OS does a WAIT when it should
perhaps return and start up some user process - but that resumption of doing
user computations is delayed by at most 1 clock tick (some other device may
interrupt during the WAIT, before the clock does).
> Anyone here remember overlapped seeks on the RK-11 failing under Unix
I'd be interested in the details of this. The V6 RK driver didn't use them,
but the RK11-D does claim to support them (having spent a modest amount of
time looking at the drawings), so I'd very much like to know what the bug was.
> I know that Kevin Dawson (I think) tried it on my /40 as well
The 11/40 does not have the SPL instruction; see the '75-'76 PDP-11 Processor
Handbook, pg. 4-5. (Again, sorry, just want to be accurate.)
> Christ, but this is starting to sound like some religion or other.
I am only interested in correct data.
Noel
next reply other threads:[~2016-03-28 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 14:18 Noel Chiappa [this message]
2016-03-28 14:44 ` Johnny Billquist
[not found] ` <0BAE4C73-C72B-453E-BEBD-EA34CEEA9853@uwlax.edu>
2016-03-28 16:37 ` Johnny Billquist
2016-03-28 16:52 ` Milo Velimirović
-- strict thread matches above, loose matches on Subject: below --
2016-03-28 13:43 Noel Chiappa
[not found] <mailman.171.1459115387.15972.tuhs@minnie.tuhs.org>
2016-03-27 23:07 ` Johnny Billquist
2016-03-28 13:37 ` Dave Horsfall
2016-03-28 15:18 ` John Cowan
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=20160328141842.B0DC218C0B6@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).