The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Fwd: Choice of Unix for 11/03 and 11/23+ Systems
Date: Wed, 30 Sep 2020 14:51:20 -0400 (EDT)	[thread overview]
Message-ID: <20200930185120.8E91A18C0B2@mercury.lcs.mit.edu> (raw)

    > It is definite, though, that Q22 memory won't work with an LSI-11/2
    > (M7270) ...  I'll try an LSI-11 (M7264) tomorrow, make sure it's the
    > same; it and the LSI-11/2 are similar enough that it should, but it'd be
    > good to confirm it.

Yes, it too won't work with Q22 memory (tried it, no go - ODT won't even start).


    > Then back to trying to work out why Mini-Unix is so fragile for me.

I tried some changes in the simulator set-up, to see if that would fix my
issue; no luck.

It's quite problematic: if I boot Mini-Unix on a clean copy of the RK pack, cd
to /usr/sys/dev, cp kl.c to nkl.c, and 'cc -c nlk.c', Mini-Unix reliably
restarts (trashing the disk in the process). (If I omit the 'cp', I can 'cc -c
kl.c' 3 times, and Mini-Unix restarts on the third.) Something's seriously
wrong.

I think before I try debugging it directly, I'll try one of the other
Mini-Unix repositories; the one I've been using (from Bob Eager's site) may
have some bit-rot.


    > From: Paul Riley <paul@rileyriot.com>

    > I'm checking with Peter Schranz about whether or not his RLV12/RL02
    > boards can run on the '03.

Dave Bridgham and I discussed whether the QSIC would work with an -11/03, and
that analysis should apply equally to the RLV12. Our conclusion was that it
should; here's our reasoning:

The device registers on the board should work fine on either Q18 or
Q22. That's because when going to the I/O page, the CPU asserts a special bus
line, BBS7 (that says 'this cycle is to the I/O page'). The device doesn't
look at the higher address lines when that's on, just BDAL00-12; so if the
LSI-11 is messing with some of BDAL181-21, it shouldn't matter.

For DMA cycles from the device to memory, since the CPU requires Q18 memory
to work, the device too should be able to read/write to Q18 memory. At least,
that's our theory.


I guess all this PDP-11 hardware detail isn't really on-topic for this list; I
should move it to Classic Computers, or something. Sorry all; it's
intermingled with early Unix stuff, and it was easier to keep it all in one
place.

	Noel

             reply	other threads:[~2020-09-30 18:52 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 18:51 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-03  1:25 Noel Chiappa
2020-10-18 21:36 Norman Wilson
2020-10-12 22:43 Noel Chiappa
2020-10-12 19:27 Noel Chiappa
2020-10-10 23:29 Noel Chiappa
2020-10-11  2:30 ` Jay Logue
2020-10-11 23:24 ` Paul Riley
2020-10-12  0:53   ` Dave Horsfall
2020-10-12  1:56     ` Warner Losh
2020-10-12  2:09       ` Andrew Warkentin
2020-10-12 16:57       ` Arthur Krewat
2020-10-18 20:42     ` Michael Huff
2020-10-08 23:49 Noel Chiappa
2020-10-08 16:06 Noel Chiappa
2020-10-06 23:08 Noel Chiappa
2020-10-07  5:24 ` Jay Logue
2020-10-06 20:34 Noel Chiappa
2020-10-06 19:34 Noel Chiappa
2020-10-06 19:04 Noel Chiappa
2020-10-06 14:46 Noel Chiappa
2020-10-06 16:22 ` jay-tuhs9915
2020-10-02  0:39 Noel Chiappa
2020-10-01 12:51 Noel Chiappa
2020-10-02  0:23 ` Paul Riley
2020-09-30 23:16 Noel Chiappa
2020-09-30 17:58 Noel Chiappa
2020-09-28 23:21 Noel Chiappa
2020-09-30  1:50 ` Paul Riley
2020-09-27 21:07 Noel Chiappa
2020-09-27 21:12 ` Warner Losh
2020-09-28  0:22   ` Pete Turnbull
2020-09-27 20:50 Noel Chiappa
2020-09-29 13:20 ` Paul Riley
2020-09-25 22:08 Noel Chiappa
2020-09-26 14:52 ` John Foust
2020-09-28  0:03 ` Paul Riley
2020-09-28  0:06   ` Paul Riley
2020-09-24 18:56 Noel Chiappa
2020-09-24 13:04 Noel Chiappa
2020-09-24 18:24 ` John Cowan
2020-09-24 11:02 Paul Ruizendaal
2021-02-03  0:12 ` Greg A. Woods
2020-09-24  1:28 Noel Chiappa
2020-09-23 23:14 Noel Chiappa
2020-09-24  1:09 ` John Foust
2020-09-22 21:51 John Foust
2020-09-22 21:36 Noel Chiappa
2020-09-22 21:46 ` Warner Losh
2020-09-22 21:49 ` John Foust
2020-09-22 15:59 Noel Chiappa
2021-02-03  0:07 ` Greg A. Woods
2020-09-22  0:47 Noel Chiappa
2020-09-21 19:37 Noel Chiappa
2020-09-21 23:16 ` devin davison
2020-09-21 18:13 Noel Chiappa
2020-09-21 17:59 Noel Chiappa
2020-09-21 18:18 ` Arthur Krewat
2020-09-20 13:12 Noel Chiappa
2020-09-19 15:28 Noel Chiappa
2020-09-21 10:26 ` Paul Riley
2021-01-24 16:07 ` Tom Ivar Helbekkmo via TUHS
2021-01-25  4:58   ` Gregg Levine
2021-01-25  8:21     ` Tom Ivar Helbekkmo via TUHS
     [not found] <CAD05_j1bc6DDRtfPkd4QVeWXjwSp73bty46D=2ATozUbHThBWw@mail.gmail.com>
2020-09-19  3:22 ` Paul Riley
2020-09-19 14:20   ` Heinz Lycklama
2020-09-21 13:54     ` Paul Riley
2020-09-21 15:30       ` Heinz Lycklama
2020-09-21 23:27   ` Henry Bent
     [not found]     ` <4C35E6D2-8ABD-4DC2-BB2F-F15FA5BF30DD@icloud.com>
2020-09-22  0:22       ` Henry Bent

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=20200930185120.8E91A18C0B2@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).