From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] First Unix that could run on a PDP-11 with QBUS
Date: Mon, 28 Jul 2014 09:27:17 -0400 (EDT) [thread overview]
Message-ID: <20140728132717.73DD218C0B2@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall <dave at horsfall.org>
> I recall that there were other differences as well, but only minor. In
> my paper in AUUGN titled "Unix on the LSI-11/23" it will reveal all
> about porting V6 to the thing.
I did a google for that, but couldn't find it. Is it available anywhere
online? (I'd love to read it.) I seem to recall vaguely that AUUGN stuff were
online, but if so, I'm not sure why the search didn't turn it up.
> I vaguely remember that the LTC had to be disabled during the boot
> process, for example, with an external switch.
I think you might be right, which means the simulated 11/23 I tested on
wasn't quite right - but keep reading!
I remember being worried about this when I started doing the V6 11/23 version
a couple of months back, because I remembered the 11/03's didn't have a
programmable clock, just a switch. So I was reading through the 11/23
documentation (I had used 11/23s, but on this point my memory had faded),
trying to see if they too did not have a programmable clock.
As best I can currently make out, the answer is 'yes/no, depending on the
exact model'! E.g. the 11/23-PLUS _does_ seem to have a programmable clock
(see pg. 610 of the 1982 edition of "microcomputers and memories"), but the
base 11/23 _apparently_ does not.
Anyway, the simulated 11/23 (on Ersatz11) does have the LTC (I just checked,
and 'lks' contains '0177546', so it thinks it has one :-).
But this will be easy to code around; if no link clock is found (in main.c),
I'd probably set 'lks' to point somewhere harmless (054, say - I'm using
050/052 to hold the pointer to the CSW, and the software CSW if there isn't a
hardware one). That way I can limit the changes to be in main.c, I won't have
to futz with clock.c too.
Noel
PS: On at least the 11/40 (and maybe the /45 too), the line clock was an
option! It was a single-height card, IIRC.
next reply other threads:[~2014-07-28 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 13:27 Noel Chiappa [this message]
2014-07-28 22:23 ` Dave Horsfall
2014-07-29 9:46 ` Warren Toomey
2014-07-29 9:56 ` Dave Horsfall
2014-07-29 14:33 ` Clem Cole
2014-07-29 13:10 ` Milo Velimirović
-- strict thread matches above, loose matches on Subject: below --
2014-07-27 5:39 Norman Wilson
2014-07-27 6:02 ` John Cowan
2014-07-27 14:10 ` Bill Pechter
2014-07-27 17:16 ` Dave Horsfall
2014-07-27 3:26 Noel Chiappa
2014-07-27 5:49 ` Dave Horsfall
2014-07-28 22:04 ` Warren Toomey
2014-07-28 22:38 ` Warner Losh
2014-07-29 9:06 ` SPC
2014-07-29 13:28 ` Clem Cole
2014-07-27 2:37 Mark Longridge
2014-07-28 15:57 ` Ron Natalie
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=20140728132717.73DD218C0B2@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).